Related
After all this framework hack does not work well under too many ROMs and causes lots of confusion about version. I accidentally found a universal solution to Home Button vibration that works with JKay theme and won't break anything. So this method is abandoned.Hi everyone. I have been Hellraising i9100 ROMs since Entropy's release, however was puzzled by the Home button which lags and won't give any feeling of touch when pressed.
After some research I finally figured out how to fix this. I made 2 versions, one for XXKI3 and another for XXKI4
Currently ROMs incorporates JKay theme mods (Sensation) are not working.
(Sorry I was too excited to notice I compiled both file from custom ROMs that were containning extended power menu, the fix is not universal and try at your own risk!).
Installtion Instructions:
1. Place the zip file into your Internal SD
2. Reboot into Recovery and select "install zip from sdcard"
3. Select "install from SD card", choose YES
4. hit return and reboot
You should have haptic feedback on Home now, also the Home button should respond instantly.
Caution:
Only apply to ROMs that are based on supported Samsung builds.
android.policy.jar varies from build to build so can not hybrid with different versions.
Credit:
gtg465x - home button lagfix code reference
DesignGears - home button haptic fix code reference
Ande definitely Entropy512, for the awesomeness of Hellraiser!
Please let me know if anything happens.
Downloads
Currently not working with JKay themes.
For i9100XXKI3 based ROMs:
View attachment XXKI3-hapticfeedbackfix.zip
For i9100XXKI4 based ROMs:
This file is modified from an i9100 ROM with extended power menu and header, might not work if the menu had the header removed!
View attachment XXKI4-hapticfeedbackfix.zip
amtrakcn said:
Hi everyone. I have been Hellraising i9100 ROMs since Entropy's release, however was puzzled by the Home button which lags and won't give any feeling of touch when pressed.
After some research I finally figured out how to fix this. I made 2 versions, one for XXKI3 and another for XXKI4.
Installtion Instructions:
1. Place the zip file into your Internal SD
2. Reboot into Recovery and select "install zip from sdcard"
3. Select "install from SD card", choose YES
4. hit return and reboot
You should have haptic feedback on Home now, also the Home button should respond instantly.
Caution:
Only apply to ROMs that are based on supported Samsung builds.
android.policy.jar varies from build to build so can not hybrid with different versions.
Credit:
gtg465x - home button lagfix code reference
DesignGears - home button haptic fix code reference
Ande definitely Entropy512, for the awesomeness of Hellraiser!
Please let me know if anything happens.
Click to expand...
Click to collapse
Thanks.... can you please post what code is changed within it (FOR HOME HAPTIC FEEDBACK) so I can mod the one for the rom I'm using. I don't want to use a generic one.
Thanks!
EDIT: Its rom specific.....you can't do generic addons.... It broke my rom which is why posting the actual change would be best. It booted but broke JKAY mods
shoman94 said:
Thanks.... can you please post what code is changed within it so I can mod the one for the rom I'm using. I don't want to use a generic one.
Thanks!
Click to expand...
Click to collapse
I think KI4 version works for checkROM. However just forget I modified both from custom ROMs so does not work universally...
There are multiple places in smali that needs to edit. So you might want to compare your original file with the attachment.
It's <decompiled dex folder>\com\android\internal\policy\impl\PhoneWindowManager.smali
View attachment PhoneWindowManager.zip
amtrakcn said:
I think KI4 version works for checkROM. However just forget I modified both from custom ROMs so does not work universally...
It's more than one place in smali so you might want to compare with the attachment.
View attachment 780701
Click to expand...
Click to collapse
I've been doing that but there are so many differences that I can't tell which is which.
Can't you just say which lines were changed....?
shoman94 said:
I've been doing that but there are so many differences that I can't tell which is which.
Can't you just say which lines were changed....?
Click to expand...
Click to collapse
Line 3841 to 4568... actually works just override all differences.
amtrakcn said:
Line 3841 to 4568... actually works just override all differences.
Click to expand...
Click to collapse
errors out.....
to good to be true. I've been messing with this all night and I"m not winning.
shoman94 said:
errors out.....
to good to be true. I've been messing with this all night and I"m not winning.
Click to expand...
Click to collapse
Like what kind of error you are encountering? During recompile or during testing?
I don't have time to poke at this (busy sobering up after a party...) but: I suggest providing the modded version,a nd the original, and diffing them.
Note that according to Mikey, designgears' patch accidentally caught a bunch of changes that weren't related to home-button.
And yes, just copying the smali will cause an epicfail most likely, ESPECIALLY if targeting a JKay theme, as JKay did dome significant mods to that smali file.
FYI, shoman94, you've gotten as far as I ever did - I never got a working mod, but I've been pretty busy this week.
Entropy512 said:
I don't have time to poke at this (busy sobering up after a party...) but: I suggest providing the modded version,a nd the original, and diffing them.
Note that according to Mikey, designgears' patch accidentally caught a bunch of changes that weren't related to home-button.
And yes, just copying the smali will cause an epicfail most likely, ESPECIALLY if targeting a JKay theme, as JKay did dome significant mods to that smali file.
FYI, shoman94, you've gotten as far as I ever did - I never got a working mod, but I've been pretty busy this week.
Click to expand...
Click to collapse
Thanks for pointing out, I recalled many other other modifications to the android.policy.jar after I posted but I cannot edit the title of thread now...
When comparing the 2 smali files (Original and DesignGear modified), except the lines for home button I only saw difference in conditions, which I don't really understand. It was a experiment that I just copyed the whole PhoneWindowManager.smali then compiled. The compiled file worked.
The file I posted is from a KI4 ROM with extended power menu with header, however since header modification is in GlobalActions.smali I think this should not affect compiling.
Tell me if I got anything wrong, first time looking into the bytecodes
Will be very thankful if you have time to look at this
View attachment OriginalPhoneWindowManager.zip
View attachment ModifiedPhoneWindowManager.zip
amtrakcn said:
Like what kind of error you are encountering? During recompile or during testing?
Click to expand...
Click to collapse
Well I installed your file and it booted fine but jkay mods were broken. I've been trying different combination for the last 8 hrs trying to get this to work. Epic fail.
I might have to post a message to JKAY for some help.
shoman94 said:
Well I installed your file and it booted fine but jkay mods were broken. I've been trying different combination for the last 8 hrs trying to get this to work. Epic fail.
I might have to post a message to JKAY for some help.
Click to expand...
Click to collapse
Since JKay moded other places than the Home Button as Entropy mentioned... this should happen.
You'll need precise modification that just target the Home button...
amtrakcn said:
Thanks for pointing out, I recalled many other other modifications to the android.policy.jar after I posted but I cannot edit the title of thread now...
When comparing the 2 smali files (Original and DesignGear modified), except the lines for home button I only saw difference in conditions, which I don't really understand. It was a experiment that I just copyed the whole PhoneWindowManager.smali then compiled. The compiled file worked.
The file I posted is from a KI4 ROM with extended power menu with header, however since header modification is in GlobalActions.smali I think this should not affect compiling.
Tell me if I got anything wrong, first time looking into the bytecodes
Will be very thankful if you have time to look at this
View attachment 781002
View attachment 781001
Click to expand...
Click to collapse
and the differences are attached but don't work with JKAY mods.... some things may need to get incorporated. IDK
amtrakcn said:
Since JKay moded other places than the Home Button as Entropy mentioned... this should happen.
You'll need precise modification that just target the Home button...
Click to expand...
Click to collapse
exactly my friend. I've been trying to get some help from DG but he is preoccupied. He tried a quick patch but resulted in the same issues I was getting myself.
I can confirm that it worked for checkrom2.0 but when I updated to checkrom 3.0 and relflashed the mod my phone would bootloop as soon as the phone booted. The first thing that popped up was a fc on com.android.phone (or something that had phone in it
Sent from my SGH-I777 using xda premium
jgrimberg1979 said:
I can confirm that it worked for checkrom2.0 but when I updated to checkrom 3.0 and relflashed the mod my phone would bootloop as soon as the phone booted. The first thing that popped up was a fc on com.android.phone (or something that had phone in it
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
It worked on 2.0 but broke the jkay mod.... extended power menu was out of whack.... AOSP style lock screen stopped working.... etc
jgrimberg1979 said:
I can confirm that it worked for checkrom2.0 but when I updated to checkrom 3.0 and relflashed the mod my phone would bootloop as soon as the phone booted. The first thing that popped up was a fc on com.android.phone (or something that had phone in it
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
It looks like the new checkrom is kj3 based. That haptic fix is for ki3 and ki4. Probably why is messed up.
Sent from my SAMSUNG-SGH-I777 using XDA App
can you post the fix for sensation 1.9.
would be greatly appreciated
nmandi said:
can you post the fix for sensation 1.9.
would be greatly appreciated
Click to expand...
Click to collapse
Hi, I compiled the file but since I'm not on Sensation ROM I did not try it myself.
Let me know if you run into any problem.
THX!
View attachment 782532
amtrakcn said:
Hi, I compiled the file but since I'm not on Sensation ROM I did not try it myself.
Let me know if you run into any problem.
THX!
View attachment 782532
Click to expand...
Click to collapse
i'm getting com.android.phone force close
hi im currently in process of porting a stock deodexed rom.
i have changed system files and the update script.for out i9305. at moment i am able to install the rom fine and loads up with or without wipe. i also included the ee modem.
my issue is that when the rom starts all is ok and there are no force closes however i get no network and imei shows null. to resolve this i just flash param.tar in odin and stock file and all is back to original with imei restored.
any ideas on whats causing the loss of imei number
in setting imei and baseband showbas unknown
edit whilst restoring to stock i did not have to restore imei backups so am asuming efs part is fine
Sent from my GT-I9305 using Tapatalk 2
Check 9500 partition layout and update install script. Dont rewrite the efn part.
Sent from my GT-I9305 using xda app-developers app
have done that part rom installs fine baseband is unknown
Sent from my GT-I9305 using Tapatalk 2
I think u need to Flash a baseband from our i9305 after flashing The Potter rom
but wouldnt that be the modem file iv tried flashing it on radio partition
Sent from my GT-I9305 using Tapatalk 2
right iv ported wanam lite rom to our device, the aroma works i boot up fine but baseband still unknown so annoyin
Sent from my GT-I9305 using Tapatalk 2
i am really into this thread. I opened a thread similar at the beginning but they moved it, hope this one stays in here otherwise it will get lost in the i9300 section...... this is really good lets all try get into this, like i said I am going to play around on monday when i return home, so far we got everything going exceept the Modem is not connecting to the Imei correctly, We need an experienced dev.
---------- Post added at 09:25 AM ---------- Previous post was at 09:14 AM ----------
Just think how many roms we can have if we get this going
Sent from my GT-I9305 using xda app-developers app
Try merging our system and framework so it picks it up as our xxali5 or xxali9 you have to get rid of there base and put our base instead but leave the edited files so maybe the system apps folder stays the i9300 as the apps are the same i think but change the rest into our firmware hmmmm so maybe a better idea would be to have a blank deodexed and zipaligned xxali5 rom move and overwrite our files with the edited files of the i9300 that way all our efs and imei doesnt get touched
Sent from my GT-I9305 using xda app-developers app
going to check ril today see if that sorts it
Sent from my GT-I9305 using Tapatalk 2
Great thread, wish I could contribute more.
At the moment I'm hanging to see what the more clued up guys around here work out!
added the ril files and qualcom ril files but basebands the same
also the serail number has changed on device tried reflashing modem but doesnt help
chwads2k8 said:
right iv ported wanam lite rom to our device, the aroma works i boot up fine but baseband still unknown so annoyin
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Basically there are some intensely different changes within the services.jar, framework.jar, android-policy.jar and so forth. 4G LTE is sooo much different than the stock i9300. I am not saying it CAN'T be done. But I am saying it is going to be a complete bastard to do. Put it this way, you'd be better off looking into all of the modifications that have been done to create these ROMS and re-doing them to the i9305.
Trust me, I have looked into doing this with a "customised" build to from sources for ICS for the P7320T tablet that I had. It is the only 4G tablet released here in Australia. The closest I could find in sources for being able to make the connection was grabbing settings systemUI and the others I have listed above ^^^ from the S2 4G LTE. Then I was going to have to modify the systemUI specifically for tablet mode.
I no longer have the tablet nor the patience to want to take on anything like it again.
All I can say is good luck. Feel free to check my threads to confirm that my choices are not a conflict of motivation or lack of determination...god I can assure you that much
Just for a tip. I started today with decompiling the android-policy.jar file to see if I could enable the torch app double click home from lock screen feature....this has been done on i9300 right? Go take a look at the full guide on how to do it...go decompile 1 file that I am talking about and you will see just how different the methods are in all of the smali code. JOY!
---------- Post added at 03:34 AM ---------- Previous post was at 03:23 AM ----------
chwads2k8 said:
added the ril files and qualcom ril files but basebands the same
also the serail number has changed on device tried reflashing modem but doesnt help
Click to expand...
Click to collapse
What tools are you using to "port" this ROM to our device?
I have tools that can port ROMs in about 30-40min.
What have you got in the build.prop for this thing? Do you want to upload the ROM for me to take a look at? The least I could do is offer some help before raining on your parade lol.
Have you considered doing maybe a "splice" of the ROM. Rather than porting the full version, you could do a diff/compare of the modded ROM against it's stock counterpart. Then you migrate those changes over to your "stock i9305" base. That is going to be your best chance of doing this I reckon? also you won't be able to copy across the firmware version. That won't work. Your framework and the firmware version are going to be device specific.
The absolute best thing I can think of suggesting is to go with a known base equivilant?? Like it seems that there is a release of XXALI5 (for touchwiz at least?) on both devices. That would be where I would start first and foremost. I would port with that common version using what I described above and then migrating any further or additional functionality (developer made i.e. Wanams mods) that have been done since the XXALI5 release.
That is going to be your best bet.
Or you guys could just wait for me to release my ROM haha...subtle promotion? I think not.
btemtd said:
Try merging our system and framework so it picks it up as our xxali5 or xxali9 you have to get rid of there base and put our base instead but leave the edited files so maybe the system apps folder stays the i9300 as the apps are the same i think but change the rest into our firmware hmmmm so maybe a better idea would be to have a blank deodexed and zipaligned xxali5 rom move and overwrite our files with the edited files of the i9300 that way all our efs and imei doesnt get touched
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Exactly
I have a methodology that does this very easy. I wanted the OP to upload his work so far to save me a download. But I might just go ahead and do it anyway.
Have you guys got permissions from Wanam to use his work? I will ask on your behalf if not. He is a great contributor to this forum, I don't wish to have him offside.
What I mean is that I will go ahead and play, but I won't re-upload any test files to the forum without his consent This shouldn't be too hard
---------- Post added at 12:40 PM ---------- Previous post was at 11:53 AM ----------
Contacted Wanam. I will wait to see what he says and recommends. I have claimed I am not releasing anything of his, so this can be owned by you guys who want it. I am happy to help get the ball rolling to help yous though. I have my own dev team that I work with so that makes me kinda busy. That is why I haven't released my own ROM on here yet lol
Downloaded XXLAI5 Wanam, Downloaded XXLAI5 stock i9300, have already downloaded XXLAI5 stock i9305 and I am currently deodexeding it as we speak.
Will deodex i9300 XXALI5 next and then do a comparison to Wanams. Segregate changed files - > port to stock deodexed base = Wanam i9305 for you guys
That's if Wanam approves of course?
EDIT: Hey Mr OP can you please contact me? I cannot send you PMs? Holy smokes you've been around this place since 09!
Ok Analysis done on Wanam compared to stock XXALI5 and have all the of the files seperated and within their directory structure that had changes.
There is going to be some work needed to be done on these main files:
/system/framework/android.policy.jar
/system/framework/framework2.jar
/system/framework/services.jar
/system/app/systemUI.apk
As I expected
Now the fun n games start I will decompile all of these files and then diff them against the standard i9300 smali coding and then *attempt* (and I say that with all great intension too) to migrate the changes across into decompiled i9305 files.
I can tell this is going to be a head ache!
Otherwise though....I can honestly say that what I have got so far I know for certain will boot and you will not have baseband issues. You won't however have 15 toggle mod as it stands. Services.jar and Android policy.jar both control this feature. I see that this *IS* available as a mod already on this forum but I am not certain that the creators realise that these modifications (mentioned here) actually do need to be performed.
Lidroid-res.apk within framework will have no rights to control the toggle on the systemUI cause it won't have permissions due to conflicting signature checking. note...toggles may appear, but they won't do anything when you touch the widget toggle, it will be non-responsive.
Thanks guys
Thats what i said we should just try copying over the whole system app folder and replacing it with our deodexed rom. Try doing that as the firstt step
Sent from my GT-I9305 using xda app-developers app
btemtd said:
Thats what i said we should just try copying over the whole system app folder and replacing it with our deodexed rom. Try doing that as the firstt step
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
System app is fine, but that isn't where the changes are that make Wanams ROM. You'd have your self a standard ROM otherwise. As in no difference. Or if you just copied the system/app folder ROM would boot but systemUI would force close. You would also have no reboot menu and no USB read from the phone. That would equal disasterous....cause as we all know we don't have SD mount in recovery do we?
Fancy doing an adb push on a phone that doesn't install USB connection files?
See I wouldn't be stupid enough to do that without having at least a clockwork recovery backup lol.
It's ok. for the android.policy.jar they are identical (well for XXALI5 they are anyway) to the i9300. So simple trade in there.
Only 4 more files to go and I will have you guys a port
Wanam still has not contacted me back yet though so I we need approval before anything.
Reset scrolling caches. In framework2.jar
This took a bit of work because my notepad++ kept crashing running compare. If you guys ever have this issue, right click the executable in program files go to properties and compatibility and then check the boxes for:
- disable visual themes
- disable desktop composition
- disable high dpi scaling.
Apply.
No more crashing. Windows 7 aero apparently doesn't like the compare dll?
Anyway not related. I am back on track. last jar file and then it should be ready to package up and it will be the same as Wanam ROM XXALI5
Got approval from Wanam. Just about to test flash now. Will upload it here if everything works out
Well, I had a few mishaps with my own device. Namely no root access and also lost hardware ID...meaning no Android Market. This all happened sometime during my lengthy list of modifications so I was not sure where. That mean flash back to stock and restore my data bit by bit until I was set up again. This take for EVER!
So yeah no real feedback from anyone in here so have decided to finish off my own ROM instead. XXALI9 (newer) and a heap more mods than stock Wanam. So far so good.
I can upload what work I did on getting Wanam's up and running (I have not flashed it yet) but will wait till someone actually wants before I go ahead and do that.
Thanks guys
James
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.
I attempted to ask a few questions in the Project Odex thread but was promply told to "search for it it is easy to find".... Kind of agrivating when you just got done doing just that, especially considering the title specifically states "for those that want mods"...
Anyhow I was hoping I could bug those that do for some ideas of the mods you use for Odex roms etc, and maybe any warnings about mods that do not work so well.
Morkai Almandragon said:
I attempted to ask a few questions in the Project Odex thread but was promply told to "search for it it is easy to find".... Kind of agrivating when you just got done doing just that, especially considering the title specifically states "for those that want mods"...
Anyhow I was hoping I could bug those that do for some ideas of the mods you use for Odex roms etc, and maybe any warnings about mods that do not work so well.
Click to expand...
Click to collapse
That completely depends on the rom and the mods that you want to change. System mods don't matter on odexed or deodexed. The individual app mods will have to be made for the odexed rom though since they need both jar and apk files to work. Hope this answered your question.
I am just not finding much of anything, some of the basic things I would love to find are something to remove the wifi nag, and something like Wanam xposed that will work on 4.1.2
Hi guys,
Just found out Jetstream phone no sound because some missing commands in framework. Can someone recommend a willing framework engineer?
Sent from my GT-P1000 using xda app-developers app
cx5 said:
Just found out Jetstream phone no sound because some missing commands in framework. Can someone recommend a willing framework engineer?
Click to expand...
Click to collapse
You can try copying some of the system/framework/*.jar files from a ROM with a fully working phone? I suggest starting with LeeDrOiD HC Flyer ROM -- link below.
http://forum.xda-developers.com/showthread.php?t=1406851
It should be noted that LeeDrOiD did some pretty significant kernel work as well. You might want to figure out if his kernel was partly or wholly responsible for the phone functionality.
Thanks, will get to it. From observing GT-P1000, it seems kernel is fine, just lacking something in framework, but I haven't managed to ask deep enough. Like which JAR files?
finniest said:
You can try copying some of the system/framework/*.jar files from a ROM with a fully working phone? I suggest starting with LeeDrOiD HC Flyer ROM -- link below.
http://forum.xda-developers.com/showthread.php?t=1406851
It should be noted that LeeDrOiD did some pretty significant kernel work as well. You might want to figure out if his kernel was partly or wholly responsible for the phone functionality.
Click to expand...
Click to collapse
cx5 said:
Thanks, will get to it. From observing GT-P1000, it seems kernel is fine, just lacking something in framework, but I haven't managed to ask deep enough. Like which JAR files?
Click to expand...
Click to collapse
I don't know much about the framework directory. It looks like it contains functionality that is stagnant for a given Android version and flavor -- i.e. Android x and HTC Sense y.
Java .JAR files are linked at runtime which makes them pretty easy to upgrade without problems. I don't know the anatomy of Android .JAR files, however. They are .ZIP compatible so open one up and see.
Often when swapping out software pieces that are dependent on other pieces you have to rely on a lot of trial and error. If you try doing this then expect to run into a lot of boot loops.