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

Root [DEV] WIP CM9 (Camera) [updated 2/23/2013]

snoopyboyblue said:
I've only noticed one odd thing so far with the rom. My phone shot down after snapping about 8 pictures the other night saying the battery was on 0% even though it was at about 70% at the time. I charged it and did the same thing the next night with the same result. I thought it was odd that the battery would have drained so fast under any conditions, especially since the phone was not warm at all indicating that something was running wild. After about a 5 minute wait the second night, I re-booted and the battery was back up at 70% where it had started, but 3 more pictures and it was shutting down again claiming that the battery was drained. Any thoughts? Do I need to double wipe and re-install the rom? Great job, by the way, this thing is SWEET!! :)
Click to expand...
You might have my old phone lol.If you try the same thing on different ROMs and get the same result then it's the phone itself.I've had that issue before and I made a post about it months ago like Dec/Jan I think.
 
RolaAddict said:
You might have my old phone lol.If you try the same thing on different ROMs and get the same result then it's the phone itself.I've had that issue before and I made a post about it months ago like Dec/Jan I think.
Click to expand...

No, I don't think it's the phone. it never did this on the stock rom, and I've been running CM7 for the last year and a half, and never noticed it there either. I'll backup and try a few wipes to see if that solves it.
 
snoopyboyblue said:
I've only noticed one odd thing so far with the rom. My phone shot down after snapping about 8 pictures the other night saying the battery was on 0% even though it was at about 70% at the time. I charged it and did the same thing the next night with the same result. I thought it was odd that the battery would have drained so fast under any conditions, especially since the phone was not warm at all indicating that something was running wild. After about a 5 minute wait the second night, I re-booted and the battery was back up at 70% where it had started, but 3 more pictures and it was shutting down again claiming that the battery was drained. Any thoughts? Do I need to double wipe and re-install the rom? Great job, by the way, this thing is SWEET!! :)
Click to expand...

I had the same kind of issue on CM7. boot your phone while plugged in and allow it to fully charge. That reset the battery monitor for me
 
snoopyboyblue said:
No, I don't think it's the phone. it never did this on the stock rom, and I've been running CM7 for the last year and a half, and never noticed it there either. I'll backup and try a few wipes to see if that solves it.
Click to expand...
Ya if it doesn't/hasn't done it before on other ROMs then ya not the phone.Mine was a replacement that was doing that from day 1 so yea.
 
rdoac said:
I get it on PA but not on CM9. Not sure why one but not the other. Leaving the Wifi on kills the batterylife though.. I got about 7 hours from my battery yesterday before I had to swap it over. I normally can get about 14 hours..

Also, Chrome works on PA but not on CM9. I can get to the menus and everything like that on it, but it won't display a web page. That pane is always completely blank. I've tried uninstalling/reinstalling etc, but nothing can persaude it to run.
Click to expand...

An update on the dreaded Roaming no 3g problem. I started getting it yesterday for the first time on CM9. Thankfully I had just done a Nandroid backup before messing around in ClockworkMod. I'd gone into there to try and fix full reboots. I'd done a cache & dalvik wipe, and a fix permissions when I noticed the R problem that I'd had on PA was now in CM9. Went back to the Nandroid it was fine.


Just did a Cache/Dalvik wipe without fix permissions, no R problem. I think, therefore it may have something to do with Fix permissions? I may have used that with PA. I am just about to try PA again from scratch without installing settings using Titanium. Will report back, but I'd be interested to know if anyone else seeing the R problem did Fix Permissions?

Rob
 
rdoac said:
An update on the dreaded Roaming no 3g problem. I started getting it yesterday for the first time on CM9. Thankfully I had just done a Nandroid backup before messing around in ClockworkMod. I'd gone into there to try and fix full reboots. I'd done a cache & dalvik wipe, and a fix permissions when I noticed the R problem that I'd had on PA was now in CM9. Went back to the Nandroid it was fine.


Just did a Cache/Dalvik wipe without fix permissions, no R problem. I think, therefore it may have something to do with Fix permissions? I may have used that with PA. I am just about to try PA again from scratch without installing settings using Titanium. Will report back, but I'd be interested to know if anyone else seeing the R problem did Fix Permissions?

Rob
Click to expand...


I've installed PA and CM9 with and without fix permissions and still received the signal problem.
 
Just did a quick test with PA. I installed it fresh without restoring data, turned off wifi and put it in my pocket for a while. Didn't get the R thing, so assume it's something in my settings or apps which is being restored. Will do a gradual restore with Titanium and see and what point it goes pear shaped.
 
Hmmm, restored apps, account data, sms/mms, call log and wifi settings and got the dreaded R again.. :-(
 
Through trial and error, I would say the problem starts when I restore wireless settings using Titanium Backup Pro. Although they came from CM9 which works correctly.

Still testing mind..
 
I posted this in another thread but it might be more appropriate here:

I'm currently on 20130223. Is anyone else seeing a problem with navigation? I tell my phone to navigate to a location and it locks up. I need to do a battery pull to recover.

I just re-wiped (3x) (dalvic/datawipe) =) and reinstalled the rom along with just maps and the issue is still reproducible 100%.

Otherwise, everything else works great! My games and other apps run a lot smoother and faster.

Regards,
Brandon
 
sobra said:
I posted this in another thread but it might be more appropriate here:

I'm currently on 20130223. Is anyone else seeing a problem with navigation? I tell my phone to navigate to a location and it locks up. I need to do a battery pull to recover.

I just re-wiped (3x) (dalvic/datawipe) =) and reinstalled the rom along with just maps and the issue is still reproducible 100%.

Otherwise, everything else works great! My games and other apps run a lot smoother and faster.

Regards,
Brandon
Click to expand...

I'm not sure when your is locking up but mine works fine. Make sure you wipe cache.
too
Good luck
 
rdoac said:
Through trial and error, I would say the problem starts when I restore wireless settings using Titanium Backup Pro. Although they came from CM9 which works correctly.

Still testing mind..
Click to expand...


Spoke too soon. Got it again when driving home. I am now wondering if this is related to deep sleep mode? Although it's more common (to me) on PA moreso that CM9.
 
sobra said:
I posted this in another thread but it might be more appropriate here:

I'm currently on 20130223. Is anyone else seeing a problem with navigation? I tell my phone to navigate to a location and it locks up. I need to do a battery pull to recover.

I just re-wiped (3x) (dalvic/datawipe) =) and reinstalled the rom along with just maps and the issue is still reproducible 100%.

Otherwise, everything else works great! My games and other apps run a lot smoother and faster.

Regards,
Brandon
Click to expand...

I am using the same rom, and I used the navigation last night without problem, maybe it has something to do with how you are restoring your apps
 
(I originally posted in perhaps the wrong thread.)

I am having different problem with the 20130223 cm9 download....I have done it twice and gotten everything I want to work, ah, except I can't make any calls or texts via my Triumph!

No Service!!!

Any tips for what I am doing wrong???
Is there a different CM9 "Beta" that I should be using?? THX.
 
rdoac said:
Spoke too soon. Got it again when driving home. I am now wondering if this is related to deep sleep mode? Although it's more common (to me) on PA moreso that CM9.
Click to expand...


I am more than convinced the issue is when the phone goes into deep sleep mode. I found this:

Issue 3 - mtdev-cm - radio turning off in deep sleep on CM9 - CyanogenMod by Team MTDEV - Google Project Hosting

Which suggests it was a known issue. What I don't know is how it starts.. I am going to test a clean install again, and see if it's an app setting that nobbles it.
 
adamto said:
I have tried moving the cm7 overlay into cm9. Unfortunately, I don't think this will ever work. The cm7 overlay depends on frameworks/base/libs/surfaceflinger_client in order to allocate and manage the overlay data structures. This has been completely reworked in cm9, which no longer appears to use surfaceflinger at all. So, I can't tie in camerahal to the cm7 overlay, although I have put it in frameworks/lib/ui and hardware/msm7k/display. That much appears to "work" in that things don't blow up, but there is no preview on the camera, and it can't take pictures.

So right now, I'm done looking at overlays unless someone has a brilliant idea about what we can do for this.
Click to expand...

I've looked at the overlay a bit more. My initial impression was not quite right -- a lot of the components of surfaceflinger_client are in frameworks/base/lib/gui in cm9. So, I tried moving more stuff from cm7 over. It is now breaking down because cm7 doesn't have IGraphicBufferAlloc, ISurfaceTexture, SurfaceTexture, nor SurfaceTextureClient. I tried removing some of these completely, but they are rather tied in to system/media/wilhelm and frameworks/base/libs/media/stagefright.

SurfaceTexture looks like it might be used to adapt an overlay frame to an OpenGL texture. The weird thing is it has a dequeueBuffer(), which is one of the main functions in Overlay. Could be unrelated.

Stagefright looks like it's an interface to various hardware codecs, video and audio. It was there in cm7, but looks to be expanded quite a bit in cm9. Since this ties into SurfaceTexture, there's a good chance stagefright needs the overlay connected properly in order to work. It looks like Skype probably uses libstagefright, I'm not sure if recording video in the camera app would as well.

Next time I have a chance to look into this stuff, I may try to back up some of the changes I made, and try to adapt the cm7 surfaceflinger stuff to cm9, while trying to keep the SurfaceTexture pieces, although that will require figuring out how to make the cm7 code use it.
 
adamto said:
I've looked at the overlay a bit more. My initial impression was not quite right -- a lot of the components of surfaceflinger_client are in frameworks/base/lib/gui in cm9. So, I tried moving more stuff from cm7 over. It is now breaking down because cm7 doesn't have IGraphicBufferAlloc, ISurfaceTexture, SurfaceTexture, nor SurfaceTextureClient. I tried removing some of these completely, but they are rather tied in to system/media/wilhelm and frameworks/base/libs/media/stagefright.

SurfaceTexture looks like it might be used to adapt an overlay frame to an OpenGL texture. The weird thing is it has a dequeueBuffer(), which is one of the main functions in Overlay. Could be unrelated.

Stagefright looks like it's an interface to various hardware codecs, video and audio. It was there in cm7, but looks to be expanded quite a bit in cm9. Since this ties into SurfaceTexture, there's a good chance stagefright needs the overlay connected properly in order to work. It looks like Skype probably uses libstagefright, I'm not sure if recording video in the camera app would as well.

Next time I have a chance to look into this stuff, I may try to back up some of the changes I made, and try to adapt the cm7 surfaceflinger stuff to cm9, while trying to keep the SurfaceTexture pieces, although that will require figuring out how to make the cm7 code use it.
Click to expand...

Adamto, this is probably asking for a lot but have you ever considered porting a 3.x kernel to the triumph?
 
QUOTE=sobra;5614438]I posted this in another thread but it might be more appropriate here:

I'm currently on 20130223. Is anyone else seeing a problem with navigation? I tell my phone to navigate to a location and it locks up. I need to do a battery pull to recover.

I just re-wiped (3x) (dalvic/datawipe) =) and reinstalled the rom along with just maps and the issue is still reproducible 100%.

Otherwise, everything else works great! My games and other apps run a lot smoother and faster.

Regards,
Brandon[/QUOTE]


shawndak089 said:
I'm not sure when your is locking up but mine works fine. Make sure you wipe cache.
too
Good luck
Click to expand...

Well I've done full wipes and I've gotten that navigation problem, only twice have I gotten that navigation to work flawlessly. I also wonder if navigation needs some work done or if low signal causes it to crash.
 
Since we're on the subject of Navigation...

I'd been running the 20120223 for about a week & a half, no problems aside from the occasional FC. I'm not too happy with how much memory it takes up compared to CM7 (even with running Link2SD) but I know CM9 is a much larger ROM so I was prepared for it.

Anyway, I always leave "Use wireless networks" & "Use GPS satellites" unchecked in the Location menu unless I am going to use the Navigation. On Thursday morning I switched them on for the first time on CM9 because I had to go to a new job site. I shut my phone off to go to work and forgot to switch off the Location settings. The next time I booted my phone up, I pretty much couldn't use it. Everything - and I mean EVERYTHING - FC'd before even loading. Almost all of my apps (I actually don't have very many) would FC as soon as I clicked on their icon. About the only thing I could use was Messaging and the browser, once I deactivated Swype Beta (even that failed to work).

I don't know if using GPS/Navigation is related to everything going to hell, but it stands to reason since that was the last thing I did with my phone before it went completely haywire on me.

Luckily I am very vigilant about making frequent Nandroid backups, so I was able to backtrack to the previous day. I backed up all my SMS/MMS messages and have since reverted to CM7. If I get the ambition tonight I will wipe everything and give CM9 another shot. All in all, I was very happy with it until it just stopped working. I've said it before and I'll say it again: Thanks to all the devs for your hard work and dedication.
 
calitrippin said:
I am using the same rom, and I used the navigation last night without problem, maybe it has something to do with how you are restoring your apps
Click to expand...

I didn't "restore" any apps to be certain.

What I did:

  • full wipe & dalvic
  • install rom & gapps
  • install google maps
  • run navigation and navigated to: _________

what happens:

  • phone hangs

I've temporarily reverted to G60's Virgin Mobile Revamp. Hopefully I can go back to ICS yummy goodness. Like I said earlier, everything else ran soooo smooth!

-Brandon
 
You must log in or register to reply here.
Back
Top Bottom