-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root JellyBean - JELLYTIME for DHD/Inspire4g
- Thread starter ivicakc
- Start date
-
- Tags
- htc desire hd
ral
Android Expert
Found this on XDA this morning on the GPS issue:
Ok, I solved my problem, I have flashed my old rom (seraphic GB), opened Maps and activated GPS (yes it was back :fingers-crossed, waited for a fix and then reflash to R28. Then my GPS is now working correctly under JB :victory:
ral
Android Expert
Spent 16 hours on JellyTime last weekend doing some stress testing (gaming) before reverting to Blackout ICS 3.1.1. Today I tried a fix for rosie sensitivity on Blackout 3.2.0, which unfortunately did not work.
Instead of flashing back Blackout 3.1.1, I decided to give JellyTime another go for a few days at least. Been almost two months since I spent a significant amount of time on this ROM.
I opted to go for a "stock" look with this one.
Instead of flashing back Blackout 3.1.1, I decided to give JellyTime another go for a few days at least. Been almost two months since I spent a significant amount of time on this ROM.
I opted to go for a "stock" look with this one.
Attachments
ral
Android Expert
20 builds... but I really don't see all that much change.
Chrome is still buggy (but there is only one DHD ROM I now of where Chrome is not buggy). HW overlay still needs to be disabled. I get a lot of wake time when the screen is off. Feels like what I remember of R8. I don't know if it is faster than R8. It feels about as fast as aospX.
Other than that, everything seems to be working fine. A bit disappointing. I get the impression RB is synching it with the latest CM10 release... not sure which one. The latest CM10 release is probably being updated to fix bugs on a different device.
But it has been a long time since I used R8... what are the tangible improvements over earlier versions of JellyTime?
Chrome is still buggy (but there is only one DHD ROM I now of where Chrome is not buggy). HW overlay still needs to be disabled. I get a lot of wake time when the screen is off. Feels like what I remember of R8. I don't know if it is faster than R8. It feels about as fast as aospX.
Other than that, everything seems to be working fine. A bit disappointing. I get the impression RB is synching it with the latest CM10 release... not sure which one. The latest CM10 release is probably being updated to fix bugs on a different device.
But it has been a long time since I used R8... what are the tangible improvements over earlier versions of JellyTime?
The only things wrong with r23 that im aware of are that clock crashes if you use countdown timer and that GPS is occasionally a little unreliable (though still better than stock!). R24 and up have added some polish but more bugs/less stability based on my experience (which may not be typical).
DHD is old now... devas may soon move on to more devices and rightly so.
DHD is old now... devas may soon move on to more devices and rightly so.
ral
Android Expert
Only if I learned how to make a Kernel, and I am sure many Dev's have tried. Now if HTC or Qualcomm open sourced their drivers, someone could probably fix the issue.
ral
Android Expert
aospX. It is a fully working ICS AOSP ROM. The headset buttons work. Chrome works on it as well as it does on a Galaxy Nexus. Not much awake time when the screen is off.
Bugs. So far Edomondo Sports Tracker is buggy on it.
Is there a catch. Yes. It is based on the older 2.x kernel used on Gingerbread, patched to be compatible with Ice Cream Sandwich. Not certain what the long term implications of this with new apps are.
Every two weeks or so I go back to this ROM when Sense gets boring... Thank I suffer Sense withdrawal and go back
ral
Android Expert
Installed fairness R8 was very good. Could make for a daily driver. Than it was pretty bad for a few builds after that and I stopped following the ROM somewhere around R12 I think. Before you flashing Ii would check XDA and find a reason not too. Between 28 builds maybe it is more of picking the best rather than the latest.
ral
Android Expert
It seems to be limited to some devices. Our DHD's are identical specifications wise but sometimes different components are used. With the camera, some phones have a Samsung sensor others have a Omnivision sensor. Hence, the incompatibility of some phones with DHD ROM's.
When the 720p video issue on the camera was fixed it worked first on the Samsung sensor, and an Omnivision fix came a few days later.
existz with his aospX ROM keeps a detailed bug tracker and tries to squah each issue, even if his phone is not suffering on the issue. But he has been working on this project since January 24, 2012.
Depending on who you ask it only became daily driver ready in July or August 2012, after 6 or 7 months in development.
JellyTime is only 4 months old, so it would take time before all the bugs are fixed.
The reality is that Randomblame and Synergye will like move unto Android 4.2 before 4.1 is done.
Looking at the change logs and user feedback R24 looks like it might be the most stable, with the builds after that focused on bringing in Android 4.2 features to 4.1.2.
When the 720p video issue on the camera was fixed it worked first on the Samsung sensor, and an Omnivision fix came a few days later.
existz with his aospX ROM keeps a detailed bug tracker and tries to squah each issue, even if his phone is not suffering on the issue. But he has been working on this project since January 24, 2012.
Depending on who you ask it only became daily driver ready in July or August 2012, after 6 or 7 months in development.
JellyTime is only 4 months old, so it would take time before all the bugs are fixed.
The reality is that Randomblame and Synergye will like move unto Android 4.2 before 4.1 is done.
Looking at the change logs and user feedback R24 looks like it might be the most stable, with the builds after that focused on bringing in Android 4.2 features to 4.1.2.
Ewoedo
Well-Known Member
aospX. It is a fully working ICS AOSP ROM. The headset buttons work. Chrome works on it as well as it does on a Galaxy Nexus. Not much awake time when the screen is off.
Bugs. So far Edomondo Sports Tracker is buggy on it.
Is there a catch. Yes. It is based on the older 2.x kernel used on Gingerbread, patched to be compatible with Ice Cream Sandwich. Not certain what the long term implications of this with new apps are.
Every two weeks or so I go back to this ROM when Sense gets boring... Thank I suffer Sense withdrawal and go back
I might give aospX a go. I am the opposite and suffer aosp/aokp withdrawal.
Xmas can't come fast enough
ral
Android Expert
For those on R24... in case you are missing the JellyBean clock... I have found a JellyBean clock at Google Play that looks better than the one on JellyTime.
I've been using Pacman as my daily driver for weeks now and really like it. As for GPS, just tested it by starting 'gpstest' whilst indoors. Got the first satellite within 5 seconds and another 5 saw 7 in total in view.
I have used 'fasterfix' to set up a local ntp server but your problem may be hardware. The gps antenna is located on the back of the cover where the LED flash is; you could try pressing on this to see if it picks up satellites quicker. See this thread for ideas how to fix it ... http://forum.xda-developers.com/showthread.php?t=1318892 ...
HTH
Dave
Thanks for your help, I'm pretty sure it's a software issue though as it works fine when I revert back to r23. I'm now investigating baseband versions!
Have just soldered in a new mk1 bit-o-wire GPS antenna! Seems to make a lock a bit faster on r23, haven't tried it on r28 yet but gut feeling is it'll make no difference as the system isn't recognising GPS. Have posted another thread looking for help on basebands, hopefully this'll solve the issue!
