-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [KERNEL] mOCk kernel v1.7.14 for MIUI (released)
- Thread starter mantera
- Start date
-
- Tags
- motorola triumph
I just keep my minimum at 245 mhz. You can try going lower but some people were running into SOD (sleep of death) issues at the lower speeds--meaning that the phone would go to sleep and not wake up until you do a battery pull.
It's not in this version at this time. In the OP I was just quoting the results from that other post so you didn't have to read the whole post if you didn't want to...
isaacj87
Android Expert
Because, while I have built OC kernels (and tested them to make sure they work), I never use them myself. At least not long enough to make an assessment on battery life. I wanted to see what kind of impact moderate overclocking is having on battery life in real world usage from other users.
Chairshot215
Android Expert
I generally see about an extra 5% drop an hour running at 1.4. With that said lowering my min/max frequency when the screen is off and profiles set to start incrementally lowering my max frequency at 35c I generally see an actual improvement of about 5% an hour in battery life over using the Roms standard frequencies as is with no profiles set up in setcpu.
rondizzled
Newbie
Klehman what are your settings? What app? I don't get what to set the minmax at.
Chairshot215
Android Expert
I am using the setcpu app with a standard profile of 245 min and 1.4 max. I then have a profile with a min of 122 and 768 max for wen the screen is off and a few temperature profiles that scale the max frequency to 1.3 at 35c, 1.2 at 37c, 1.1 at 38c and 1 at 39c. If by chance it goes up-to 40c I bring the max frequency down to 768 just to try and cool things down a bit faster but it has not yet gotten that hot on me. I have also not had any issues going below a 245 minimum frequency when the screen is turned off. Owe, I also have a profile with the max set at 1 during calls. I hope this helps as I was terrified at first messing around with these settings.
I switch Roms allot and run the same settings on CM7 with about the same results.
This doesn't exactly answer your question but with undervolting at the idle frequencies using my "less aggressive table", it seems to be making a huge difference. Here's a screenshot of my battery usage in the cm7 beta 8 build.
In the screenshot, the first drop is using the stock kernel in the build. Most of that time period is at idle with only 3g on and I checked the internet for about 3 or 4 minutes about 2 times during that time period(where I was had a pretty good signal). Then you see that I charged up to full again and then you see where it starts to go down again overnight at idle again with only 3g on again but this time I had a semi crappy signal. You can see the difference in battery usage.
Oh and btw, I was using the interactiveX governor with min/max of 245 mhz /1.7 ghz when using TheOCv1.1 kernel.
I'm running mine undervolted to the minimum with the max frequency at 1024 GHz. I tested each frequency and each voltage individually,until it locked up the phone, to find out which would be the optimum stable settings for each frequency. It's undervolted to the max, no force closes on anything at all. I've been testing it constantly for about a week now? But with the normal kernel, battery life seems to be better compared to the undervolted kernel. And before you ask.. I always keep my data,GPS,bluetooth,Wifi always off until i need it, along with the screen brightness all the way down. The battery seems to drain extremely fast with this kernel along with it being undervolted. So I'm not sure what the problem could be. I even have my apps autostart values turned off with Gemini App Manager so that they don't start upon bootup. I've always had it like that btw so that's not the problem at all. I'm actually completely stumped for once.
What governor and I/O scheduler are you using?
Sorry, I forgot to include that in there. I'm using the Smartassv2 Governor along with the simple scheduler.
Updated to v1.5. Updated OP and added screenshots.
changelog:
mOCkv1.5-wip-6.zip
- Updated for new MIUI version whenever that is available. Native WIFI AP should work properly.
- added a few more governors: InteractiveX, Scary, smartass, SavagedZen
- memory tweaks
- tweaked vmalloc allocation slightly - not as much as Isaac's HD fix though- so there should still be more available memory
- added Isaac's updated touchscreen driver
changelog:
mOCkv1.5-wip-6.zip
- Updated for new MIUI version whenever that is available. Native WIFI AP should work properly.
- added a few more governors: InteractiveX, Scary, smartass, SavagedZen
- memory tweaks
- tweaked vmalloc allocation slightly - not as much as Isaac's HD fix though- so there should still be more available memory
- added Isaac's updated touchscreen driver
Try the InteractiveX governor. I've had very good results regarding battery life with it--better than Smartassv2.
How's the new touchscreen driver workin' out?
I don't play a lot of higher end run and gun type games so I don't really notice a big difference with the updated driver. However, from what others have reported, they do notice an improvement especially on the dual stick type of games.
Mobstergunz
Android Expert
sorry if this was asked but how'd you get the top bar to say miui?
EDIT: also ive read somewhere that faster processing and getting data faster was proven to save battery life since the processor is working for a shotter amount of time the battery saves some juice even if its cuts time by a hundredth of a second it adds up
That's just the carrier name change. It's part of my power menu recovery option mod here:
http://androidforums.com/triumph-al...covery-option-power-menu-11-9-miui-build.html