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

Root [KERNEL] TheOC v1.7.20 kernel for MT Isaac & TG based CM7

Thanks for the info. Smartassv2 should be fine nothing was changed for that governor between the two versions.

It was only Interactive using the new code from CM that seems to be having an issue.

And if you're charging, I wouldn't expect the phone to go into deep sleep. Pretty much any time that you have you're phone hooked up to something, I wouldn't expect it go into deep sleep.

Right, deep sleep is not possible when charging. It's only available when screen is off. When screen is on and nothing is happening, it should be at the min freq. When processing (buttons pressed, things happening), it should be at max (or close to it) to get it done as quickly as possible so it can ramp down to save battery again. I find smartassv2 spends too much time at the higher freqs even when nothing is going on. (It's very slow at ramping down compared to interactive, interactiveX, or even ondemand).

I think right now my favorite is classic interactive with 20ms check intervals & 95% ramp-up threshold (old algorithm, newer timing).
 
I'm trying to pinpoint my sudden poor battery life. Is anyone experiencing the same battery life with version 1.6 as they did with version 1.5 of this kernel?
I started getting horrible battery life after trying 1.6 but flashing back to the original kernel found in Whyzor's ROM (which is 1.5) the issue still persists.
The ONLY thing different is that I started using Zeam instead of stock launcher and have started using PimpMyCpu instead of SetCPU and No Frills seeing how PimpMycpu does what both SetCPU and NoFrills do but in one app. I also froze the stock launcher since I won't be using it and figured it might save SOME (if any) battery life. I have been getting consistent battery use of 3& per hour idle. Right now I am getting 10% per hour! Spare parts battery stats as well as CPU spy are not pointing me to anything. Zeam is at the bottom of the list as is PimpMycpu.. Time without a signal is 0% and Watchdog is not showing any background rogue app using excessive CPU.

I'm going to do a FULL factory reset and flash Whyzor's ROM again and restore my apps with Titanium Backup. I just thought if anyone was having battery life issues with 1.6 of this kernel it might help me in my quest to find the culprit in case factory reset doesn't work for me.
 
I'm trying to pinpoint my sudden poor battery life. Is anyone experiencing the same battery life with version 1.6 as they did with version 1.5 of this kernel?
I started getting horrible battery life after trying 1.6 but flashing back to the original kernel found in Whyzor's ROM (which is 1.5) the issue still persists.
The ONLY thing different is that I started using Zeam instead of stock launcher and have started using PimpMyCpu instead of SetCPU and No Frills seeing how PimpMycpu does what both SetCPU and NoFrills do but in one app. I also froze the stock launcher since I won't be using it and figured it might save SOME (if any) battery life. I have been getting consistent battery use of 3& per hour idle. Right now I am getting 10% per hour! Spare parts battery stats as well as CPU spy are not pointing me to anything. Zeam is at the bottom of the list as is PimpMycpu.. Time without a signal is 0% and Watchdog is not showing any background rogue app using excessive CPU.

I'm going to do a FULL factory reset and flash Whyzor's ROM again and restore my apps with Titanium Backup. I just thought if anyone was having battery life issues with 1.6 of this kernel it might help me in my quest to find the culprit in case factory reset doesn't work for me.

No new problems in this kernel 1.6 (other than interactive governor). I just put my phone into airplane mode for 8 hours while sleeping last night, and the battery drain was -2% (it gained 2% :)) probably just an indicator issue since the drain was effectively zero.

You might want to install BetterBatteryStats and look for "partial wakelocks" and "kernel wakelocks" to see what process is draining it. I use Zeam all the time and no issues.
 
I just put my phone into airplane mode for 8 hours while sleeping last night, and the battery drain was -2% (it gained 2% :)) probably just an indicator issue since the drain was effectively zero.

Wow! 1.6 is so good (besides the Interactive governor) that it actually CREATES energy? Damn! LOL. :D

I'm trying to pinpoint my sudden poor battery life. Is anyone experiencing the same battery life with version 1.6 as they did with version 1.5 of this kernel?
I started getting horrible battery life after trying 1.6 but flashing back to the original kernel found in Whyzor's ROM (which is 1.5) the issue still persists.
The ONLY thing different is that I started using Zeam instead of stock launcher and have started using PimpMyCpu instead of SetCPU and No Frills seeing how PimpMycpu does what both SetCPU and NoFrills do but in one app. I also froze the stock launcher since I won't be using it and figured it might save SOME (if any) battery life. I have been getting consistent battery use of 3& per hour idle. Right now I am getting 10% per hour! Spare parts battery stats as well as CPU spy are not pointing me to anything. Zeam is at the bottom of the list as is PimpMycpu.. Time without a signal is 0% and Watchdog is not showing any background rogue app using excessive CPU.

Seriously though. For your issue, I haven't seen any change in my battery performance either.

If you use the NOOP scheduler like I do, you can just use SetCPU now alone since you won't need to change the scheduler anymore now that noop is the default scheduler and so you won't have to use PimpMyCPU--just to see if that makes a difference.

Also, what governor are you using? If you're using the Interactive governor like Whyzor, try a different governor for now until I fix Interactive.

The last thing I would do is try unfreezing the stock launcher to see if that makes any difference--this is a shot in the dark, but who knows, it may help.
 
Thanks guys!! I didn't think there were any other issues besides the Interactive coding from Cyanogenmod.

I just did a FULL factory reset, formatted system, data, and cache. Re-installed the TG-CM7-Reloaded and then flashed 1.6 of this kernel on top of it. Sometimes, it just feels good to wipe everything and start fresh. I have a feeling my battery issue will go away.
I'll take your advice and not freeze ADW after installing Zeam. i just did that initially thinking there was a slim chance that it could save battery and keep it from running in the background.
Titanium is restoring my apps and their data as well as my CM7 settings and contacts. We'll see how this goes :)

In response to the governor, I use ondemand with a 95% up threshold as my default.

As far as the I/O scheduler, will NoOp be the default in both the TG Reloaded ROM and TheOC kernel from now on? if so, that would be great. SetCPU is so much easier to use than PimpMyCPU. I felt like a traitor for switching even though I'm sure they are both great apps.

Thanks again.

EDIT: Wow, everything always feels snappier after a factory reset! =D
 
Using TG Reloaded, 1.6 OC VR Governer and InteractiveX, I've never been able to get into Sleep mode only down to my min CPU state. Since the default is now Noop i'm going to uninstall No Frill CPU Control and use SetCPU with SmartAssv2 to see how it goes.

Edit - I wish that SetCPU had a Governor option!
 
Using TG Reloaded, 1.6 OC VR Governer and InteractiveX, I've never been able to get into Sleep mode only down to my min CPU state. Since the default is now Noop i'm going to uninstall No Frill CPU Control and use SetCPU with SmartAssv2 to see how it goes.

Edit - I wish that SetCPU had a Governor option!

It's all available in Settings - CM Settings - Performance - CPU Settings too.
 
Using TG Reloaded, 1.6 OC VR Governer and InteractiveX, I've never been able to get into Sleep mode only down to my min CPU state. Since the default is now Noop i'm going to uninstall No Frill CPU Control and use SetCPU with SmartAssv2 to see how it goes.

Edit - I wish that SetCPU had a Governor option!

It does have a governor option. It doesn't have an I/o scheduler option if that's what you mean.
 
Something is still eating away at my battery like crazy. Almost 18% drain in an hour while idle.
Here are some screenshots from BetterBatteryStats. Any ideas from someone familiar with this app that may know what this means?

http://i72.photobucket.com/albums/i183/britandkristy/screenshot-13251154582152.png

http://i72.photobucket.com/albums/i183/britandkristy/screenshot-13251153913242.png

I am using ondemand governor min:61/max:1401 with SetCPU.
I performed factory reset, flashed TG-Reloaded and then TheOC1.6 (nothing else)
Battery issue remains.

EDIT: The second screenshot seems to show that with the screen OFF for one out of the two hours turned on, the phone remained awake? Does that mean it never slept during the entire hour the screen was off?

EDIT (2): Under "Process" (which I didn't upload screenshot for) it shows "Android System" to be the number one process using battery.. which could be anything :-/
 
I'll visit a thread on general battery life discussions for further research on my issue, as it is evident this doesn't relate to this kernel or discussions concerning it :)
 
Using TG Reloaded, 1.6 OC VR Governer and InteractiveX, I've never been able to get into Sleep mode only down to my min CPU state. Since the default is now Noop i'm going to uninstall No Frill CPU Control and use SetCPU with SmartAssv2 to see how it goes.

Edit - I wish that SetCPU had a Governor option!

@Prey - Do you have your wifi on? If you do, your phone will never go into deep sleep.

Same question goes for you britton. I notice your screenshots show you have wifi running also.
 
@Prey - Do you have your wifi on? If you do, your phone will never go into deep sleep.

Same question goes for you britton. I notice your screenshots show you have wifi running also.

I use Battery Defender which does successfully turn the WIFI off when the screen turns off. I confirmed this by performing a terminal ping on the IP address of the Triumph's WIFI adapter. I know that with CM there's a bug that won't allow the Wifi to go to sleep when the screen's off and was hoping that Battery Defender would help with the Deep Sleep.
 
I use Battery Defender which does successfully turn the WIFI off when the screen turns off. I confirmed this by performing a terminal ping on the IP address of the Triumph's WIFI adapter. I know that with CM there's a bug that won't allow the Wifi to go to sleep when the screen's off and was hoping that Battery Defender would help with the Deep Sleep.

It's possible that both of you are encountering the bug where the phone can't go into deep sleep mode (even if BT & WiFi are off). I have an experimental fix in my kernel in the new ROM uploaded on my thread (or flashable zip). Let me know if it makes any difference.
 
@Prey - Do you have your wifi on? If you do, your phone will never go into deep sleep.

Same question goes for you britton. I notice your screenshots show you have wifi running also.

Wifi is on.. but what caught me off guard is that I have always left wifi on at work and at home and never had any issues until recently. Phone has always slept and only used 3% an hour when doing so. I have read numerous threads on the net about the "Android System" using high battery. Some say it is caused by Google Maps, others say it is cause by "Wifi Network Based Location" being enabled. I'm hoping Whyzor's fix he has implemented will fix it.. which by the way thank you Whyzor!!! I'll find out in a few minutes and let you know
 
Screen off with wifi on is still rapidly draining battery. Turning wifi off however I have AWESOME battery life! About 2.5% per hour! :)
I am disabling wifi when screen is off as a fix to this battery drain issue.
I also just want to be clear that I'm not blaming this kernel (or Whyzor's ROM incorporating this kernel) for my battery life issue. There are dozens of threads and forums on this wifi/standby battery drain across many devices. This kernel is awesome! (And with wifi off), best battery life yet for this phone!
 
Screen off with wifi on is still rapidly draining battery. Turning wifi off however I have AWESOME battery life! About 2.5% per hour! :)
I am disabling wifi when screen is off as a fix to this battery drain issue.
This issue is not directly related to this kernel or any other kernel or rom apparently. There are dozens of threads and forums on this wifi/standby battery drain. It seems to be a general issue in Gingerbread for various roms according to these forums.
This kernel is awesome! (And with wifi off), best battery life yet for this phone!

Glad to hear, your first screenshot above with the 'MMC' holding kernel wakelocks is what I noticed too and what my fix is supposed to address. Hopefully that won't be happening anymore. The Wifi & BT is another issue. Wifi holding wakelock was an intentional mod TG made so that the phone can still work with wifi when screen is off.
 
Glad to hear, your first screenshot above with the 'MMC' holding kernel wakelocks is what I noticed too and what my fix is supposed to address. Hopefully that won't be happening anymore. The Wifi & BT is another issue. Wifi holding wakelock was an intentional mod TG made so that the phone can still work with wifi when screen is off.

Oh, okay! Great work! I appreciate the continuing development! :)

As for the Wifi wakelock, I don't mind turning it off to allow standby. I'm just glad to finally discover the cause of the battery drain :) Initially I was perplexed since it seemed to come out of nowhere, considering I have left the Wifi sleep policy to "Never" since TG's first Beta release with no idle drain issues.
 
It's possible that both of you are encountering the bug where the phone can't go into deep sleep mode (even if BT & WiFi are off). I have an experimental fix in my kernel in the new ROM uploaded on my thread (or flashable zip). Let me know if it makes any difference.

Awesome! Downloading the latest ROM now and will report what I find...thanks, you guys are amazing!
 
Oh, okay! Great work! I appreciate the continuing development! :)

As for the Wifi wakelock, I don't mind turning it off to allow standby. I'm just glad to finally discover the cause of the battery drain :) Initially I was perplexed since it seemed to come out of nowhere, considering I have left the Wifi sleep policy to "Never" since TG's first Beta release with no idle drain issues.

Try using ES File Explorer or Root Explorer and delete Rom Manager from /system/app. I've noticed that upon startup that it seems to want to try to keep checking for updates. So it's possible that because you had an active wifi connection, that it kept on trying while your phone was supposed to be "sleeping". That was part of why I actually deleted it from my phone as well.

Rom Manager, iirc, was removed by TG in his builds since the MT isn't included in Rom Manager updates but Isaac's repo still has it being included--which means that it is being included in Whyzor's TG Reloaded rom.
 
Yeah, ROM Manager is one of the first things I remove. I also remove the stock browser, e-mail app, and gallery (and a few other things) and use my own replacements.
The issue just arose overnight with no real changes to my daily routine. I literally woke up one morning and noticed a drastic change. I now know the culprit as wifi, but I have yet to discover why it became an overnight problem.

I have USB chargers on every computer at work so leaving wifi on there will not be a problem today :)
 
Back
Top Bottom