• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ICS/CM9-JB/CM10 Development Thread

Quick question: is it safe to make a backup of this rom to be able to go back and forth between my CTmod backup and this without having to reflash? or is it necessary to reflash this completely?:confused:
 
Quick question: is it safe to make a backup of this rom to be able to go back and forth between my CTmod backup and this without having to reflash? or is it necessary to reflash this completely?:confused:
I've made a backup of CTmod, installed CM9 and went back to CTmod (restore) due to lack of camera. I haven't noticed any problems. I haven't restored CM9 yet but don't see it being a problem, then again I don't know all that much:p
 
I'm not able to get a GPS lock. GPS test shows GPS is on, but no satellites are in view. I saw this in the log, not sure if it's relevant:

Code:
D/gps_BRCM( 1466): gps fd event
D/gps_BRCM( 1466): supl_api: BrcmLbsSupl_processFunc(BRCMLBSSUPL_ONREQLOCATION)
E/GpsLocationProvider( 1466): CDMA not supported.

What I believe to be a side-effect of this is if an app (Maps, a weather widget, etc) attempts to access the GPS, a permanent wakelock is asserted and battery life takes a huge dive.
 
  • Like
Reactions: tdm
Quick question: is it safe to make a backup of this rom to be able to go back and forth between my CTmod backup and this without having to reflash? or is it necessary to reflash this completely?:confused:

Sure, you can backup and restore to switch ROMs.
 
I'm not able to get a GPS lock. GPS test shows GPS is on, but no satellites are in view. I saw this in the log, not sure if it's relevant:

Code:
D/gps_BRCM( 1466): gps fd event
D/gps_BRCM( 1466): supl_api: BrcmLbsSupl_processFunc(BRCMLBSSUPL_ONREQLOCATION)
E/GpsLocationProvider( 1466): CDMA not supported.

What I believe to be a side-effect of this is if an app (Maps, a weather widget, etc) attempts to access the GPS, a permanent wakelock is asserted and battery life takes a huge dive.

This is my experience and I was also looking at the 'CDMA not supported' error for some insight. I wasn't able to get into it much yet, but apparently this has to do with some initial location seeding for GPS lock.

Nice catch on the wakelock.

Does _anyone_ get a GPS lock with alpha1b? I was still trying to get a sense of that to inform chasing after a solution.

I was hoping there might be a /system/etc/gps.conf tweak that might help. I saw a thread here at http://androidforums.com/triumph-all-things-root/386869-gps-conf-mods-via-someone-xda-forum.html that includes some extra config lines including:
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
#INTERMEDIATE_POS=1

...and I'm wondering if that might negate the initial position request and subsequent error. I can't test this out for a bit unfortunately as I had to revert back from cm9. :(

Also, from what I've read the gps.conf file may be ignored in some/all instances, and gps_brcm_conf.xml may be the operative config file.

An interesting post here about p970 gps fix with these files that implies some importance of specific permissions: http://forum.xda-developers.com/showthread.php?t=1458827 Ack, must work unfortunately much as I want to mess with this now...
 
i flashed ics for boost and i wanted to switch back to ctmod how would i do that? i dont have the playstore nor do i got clockwork mod on my phone

nevermind found it
 
Success! :D

root@android:/ # /data/local/getbaseband
LS855ZVC-M6600A-SCAUTSZ-3.0.40T
root@android:/ #
 
Quick question: is it safe to make a backup of this rom to be able to go back and forth between my CTmod backup and this without having to reflash? or is it necessary to reflash this completely?:confused:

I made a backup of CM9 and CTMod and I have been switching back and forth between the two and haven't had any issues. My job sometimes requires me to use Maps and Navigation so I need CT since I can't get a good location with CM9. Great work by the way TDM, and thanks for the banner remover Monster. I'm even using Holo Launcher so I don't get lonely with out my Sammich. :p
 
  • Like
Reactions: tdm
It looks like the GPS lib (gps.omap3.so) is related to the RIL somehow because there are a bunch of AT-commands embedded in the lib.

I initially took gps.omap3.so from FOP, which is obviously not matched to our RIL. The reason I did this is that my Sprint version of gps.omap3.so crashes system_server with a SIGSEGV. I think I need to use the Sprint gps.omap3.so and fix the crash, and then GPS should work. Easier said than done, though...
 
Question for Dev's: Is PowerOn.mp3 still a way to put a startup sound on this rom or is there something special you have to do or a different place to put the file to get a startup sound? I dig the crap out of the intro and had an idea of something that would make it even better but I can't get any sound to play.

Edit: I did everything I know that worked on Gingerbread but apparently ICS or CM9 doesn't want to let me play. I think it may be an issue with the speaker actually playing the sound and not the appropriate placement of the file. My speakerphone does not work either on calls and I don't hear anything when I get a text message.
 
First off, great work, awesome build. I used the alpha 1b build all day and it works great. only thing to report for me is mainly the battery life, with stock cpu settings the battery drained itself fast today. the camcorder really didn't work to well either and calls take about 20 to 30 seconds to start to ring. other than that it looks pretty stable, hoping for a beta soon lol
 
Looked at the cameras today. A lot.

I got the front and back cameras oriented correctly. But the back camera still has funky colors and won't zoom. My current theory is that the libcamera I'm using, from teamhacksung's latona sources, is trying to use V4L2 APIs that don't exist in the kernel. If I replace include/videodev2.h with the one from the actual kernel, compile fails with tons of V4L2 errors.

Not sure what the best course of action is from here. I guess the obvious thing to do is dig up the latona kernel V4L2 code and toss it into the hyperics kernel. But that could get really hairy. So I might also investigate whether it's possible to use the existing V4L2 APIs.
 
Looked at the cameras today. A lot.

I got the front and back cameras oriented correctly. But the back camera still has funky colors and won't zoom. My current theory is that the libcamera I'm using, from teamhacksung's latona sources, is trying to use V4L2 APIs that don't exist in the kernel. If I replace include/videodev2.h with the one from the actual kernel, compile fails with tons of V4L2 errors.

Not sure what the best course of action is from here. I guess the obvious thing to do is dig up the latona kernel V4L2 code and toss it into the hyperics kernel. But that could get really hairy. So I might also investigate whether it's possible to use the existing V4L2 APIs.
Good luck man! The camera for ics has proved to be the biggest hurdle because the entire framework is different from gingerbread. Thanks for your hard work!
 
  • Like
Reactions: tdm
I think tomorrow I'm going to try making the camera libs work with the existing kernel. My thinking is that, since the marquee uses a different camera sensor than the latona, both ways are going to be difficult. So best to go with the vendor kernel since it's known to work with the hardware.
 
I think tomorrow I'm going to try making the camera libs work with the existing kernel. My thinking is that, since the marquee uses a different camera sensor than the latona, both ways are going to be difficult. So best to go with the vendor kernel since it's known to work with the hardware.

You are much appreciated tdm. I follow your progress on a daily basis and I think most everyone on here does the same. Keep up the good work. We're all rooting for you.



Ha Ha "rooting" :p
 
  • Like
Reactions: tdm
182e049a-6085-ea53.jpg


The only true problem with this ics build is the CPU... it only uses two frequencies 300, and 1000, as you can see none of the other frequencies are being used. Fixing that would improve battery life as well as the overall operation of the phone. The camera, and vibrations should be lower priority IMO. This is an awesome stable build though. I am using this as a daily driver with a ctmod backup in case anything goes wrong but other than the aforementioned issue this is great work tdm. :D
 
  • Like
Reactions: tdm
The only true problem with this ics build is the CPU... it only uses two frequencies 300, and 1000, as you can see none of the other frequencies are being used. Fixing that would improve battery life as well as the overall operation of the phone. The camera, and vibrations should be lower priority IMO. This is an awesome stable build though. I am using this as a daily driver with a ctmod backup in case anything goes wrong but other than the aforementioned issue this is great work tdm. :D

Even with the current bug battery life has far exceeded that of the stock ROM, and from my understanding isn't clock speed kernel related? Maybe the kernel's Dev (if not tdm) could focus on that while tdm does his thing.
 
Back
Top Bottom