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

Root [ROM][ALPHA] Triumph CM9 v0.6.17.0 [FINAL]

Has anyone else notice significant reduction in battery life in 6.3.13? I went from a full day to about 5 hours after flashing. I wonder if the multi-tasking has some task sucking up the juice??

Mine too. I have to recharge once to twice a day. Not total dead but don't want to get caught needing it and it;s dead.
 
Has anyone else notice significant reduction in battery life in 6.3.13? I went from a full day to about 5 hours after flashing. I wonder if the multi-tasking has some task sucking up the juice??

I haven't noticed any difference. I still have 64 percent after having wifi on all day and moderate use. I AM using Auto Memory Manager and Juice Defender so maybe those are helping.
 
I haven't noticed any difference. I still have 64 percent after having wifi on all day and moderate use. I AM using Auto Memory Manager and Juice Defender so maybe those are helping.

My phone has been hitting deep sleep a lot so I think it hasn't had any wake locks so plus 1 :-)
 
Since this new build, I have not been able to get my phone to apply my voltage settings in my init.d file. It was working before the update, but now it always reverts back to default. Normally, this would only happen if the voltages were unstable and cause a force reboot. Now the phone goes straight to the default voltages when the phone first starts.

I am wondering if init.d is broken again. Anyone have any problems setting configurations with init.d after flashing this updated rom?

Thanx.
 
Has anyone else notice significant reduction in battery life in 6.3.13? I went from a full day to about 5 hours after flashing. I wonder if the multi-tasking has some task sucking up the juice??

My battery life has been about the same as in previous builds. Is your phone hitting deep sleep at all? It sounds like something is keeping your phone awake and running even when you think that it's asleep.

As for the multi-tasking, there's a slim to no possibility that it should be causing an issue. All that the sense 4.0 multitasking does is it changes the look of the recent apps from the stock ics. It doesn't actually change the functionality. So changing the look only would not have any or very little effect on battery life. Think of it like a theme for the stock ICS Recent Apps.

Since this new build, I have not been able to get my phone to apply my voltage settings in my init.d file. It was working before the update, but now it always reverts back to default. Normally, this would only happen if the voltages were unstable and cause a force reboot. Now the phone goes straight to the default voltages when the phone first starts.

I am wondering if init.d is broken again. Anyone have any problems setting configurations with init.d after flashing this updated rom?

Thanx.

I still see the memory settings in the 99memory script in the init.d folder being applied so I don't think that it's broken--at least on my phone.
 
Is anyone using this rom with the navigation bar enabled?

If you are, have you noticed if you still get the occasional non-responsive back soft key?

I've been playing with this all day and I happened to have the navigation bar enabled testing some stuff out and I haven't had the soft keys become non-responsive yet, so just wondering if anyone else noticed the same thing or if it is just coincidence.
 
Is anyone using this rom with the navigation bar enabled?

If you are, have you noticed if you still get the occasional non-responsive back soft key?

I've been playing with this all day and I happened to have the navigation bar enabled testing some stuff out and I haven't had the soft keys become non-responsive yet, so just wondering if anyone else noticed the same thing or if it is just coincidence.

I've been using the navigation bar and I haven't had any problems with any of the soft keys.
 
I've been using the Navigation Bar all day (preparing for my move to the Gnexus...lol) and haven't had a problem. I recommend a battery pull, and waiting 1 minute, then booting up again. :)
 
I wanted to add my 2 cents about the battery. It has been draining within about 8 hours over the past few days. I always try to kill tasks that are running before I go to bed. So I am not sure why its not going to sleep.

Also, does anyone else lose service when they turn on wifi? I think its just this stupid replacement phone, but I figured I would throw it out there. I should be receiving a new phone (againx4) today, so I am hoping that that issue is corrected.
 
I wanted to add my 2 cents about the battery. It has been draining within about 8 hours over the past few days. I always try to kill tasks that are running before I go to bed. So I am not sure why its not going to sleep.

Also, does anyone else lose service when they turn on wifi? I think its just this stupid replacement phone, but I figured I would throw it out there. I should be receiving a new phone (againx4) today, so I am hoping that that issue is corrected.

No loss of service here when I turn wifi on.
 
I wanted to add my 2 cents about the battery. It has been draining within about 8 hours over the past few days. I always try to kill tasks that are running before I go to bed. So I am not sure why its not going to sleep.

Also, does anyone else lose service when they turn on wifi? I think its just this stupid replacement phone, but I figured I would throw it out there. I should be receiving a new phone (againx4) today, so I am hoping that that issue is corrected.

Do have your phone set to keep wifi on when screen is off? If not, your wifi will disconnect when your screen goes off.

If you don't know where this setting is, click menu when you are in the Wifi area of settings. Click advanced.
 
I still see the memory settings in the 99memory script in the init.d folder being applied so I don't think that it's broken--at least on my phone.

I think I tracked down the source of the problem. The performance settings in this update seem to be locked. When I try to change the min or max frequences, it always reverts back to 268 min and 1024 max.

Because my init.d file fails to make the cpu changes, it probably skips all settings changes. Or else the same thing that is causing the frequencies to stay locked is locking the voltages too.
 
Yeah the camera would make this complete......patiently waiting in anticipation...you guys are awesome...I for one appreciate all you guys hard work.
 
I think I tracked down the source of the problem. The performance settings in this update seem to be locked. When I try to change the min or max frequences, it always reverts back to 268 min and 1024 max.

Because my init.d file fails to make the cpu changes, it probably skips all settings changes. Or else the same thing that is causing the frequencies to stay locked is locking the voltages too.

I assume that you're using a 3rd party app to oc? Since using the built in performance settings work fine. However, I've actually updated the init.d calls in the next build so it might work better for you.
 
I just updated to 13.3 and I thought the changelog says something about better bt connectivity, but I actually am having worse. I pretty much ONLY use bt to stream pandora to my truck radio. It still is a pecker sometimes about connecting...it's a crap shoot which one to power cycle or reboot, but when it does connect the phone will drop out after about 15 or 20 minutes. The crazy thing is the head unit says lost BT, but it still shows it connected on both. If I make a phone call it is audible thru the stereo so it is still connected, but if I click on Pandora or hit the Pandora button on the head unit, Pandora WILL load and start playing...so the Head unit, via BT told the phone to launch pandora again. The track time and artist info comes up...yeah....BUT it doesn't actually play any music. It thinks it is..it will switch from song to song, but no sound comes out of the stereo or phone. It's almost like bt goes to sleep after 15 or 20 minutes but doesn't wake back up right.

But I walked out after work today after not using my phone much all day, got in the truck and was jumped when Comfortably numb started blasting after about 10 seconds on it's own.

It is like my phone and head unit are a married couple. They get along...they fight....they make up....but not really....and then I have to reboot one or both. It may be time for divorce. :mad:
 
I assume that you're using a 3rd party app to oc? Since using the built in performance settings work fine. However, I've actually updated the init.d calls in the next build so it might work better for you.

Yes, I am using system tuner. However, I was not able to change the cpu settings using the native app.

After more tinkering, this is what i have noticed. I can change cpu and voltage settings manually using system tuner. In the past, I was able to set clock speed using the native app too. Now, I cannot do that. If I try to do that, it just reverts to back to the current settings.

Apparently, system tuner is locking out the internal overclock utility. I didn't notice this behavior with the previous build of CM9.

I suppose this might be a deliberate design feature of system tuner. It would eliminate conflicts if only one app has control over performance settings. As I said though, I did not notice this behavior in the previous build, but it is possible that it was there before.
 
Back
Top Bottom