1.3 killed my battery, i could barely make it 5 hours, and that's with me hardly using my phone
Anyone running faux's new 1.2ghz,1.3ghz kernal
- Thread starter Andrew149
- Start date
For those saying its draining your battery make sure u don't blame the kernel before looking at why it's happening. Is it an app u installed? Is something keeping it awake? Did u do a proper wipe with fastboot before installing? Yes this means clearing system, cache, webtop, preinstall,userdata, and boot.
Sent from my MB860 using xda premium
Sent from my MB860 using xda premium
previous faux kernels (tried 1.2, 1.3, 1.6 previously) I'd get around 10% drain per hour with light use, even with a mild undervolt. I hence kept with stock (with alien ROM) kernel where it would be from 50% to 100% less drain with same usage pattern.
With the latest 1.9, I'm actually seeing BETTER battery than stock kernel, so kudos to faux123.
I'm using more or less the same set of apps, and if anything there is more crap running now lol.
now if only I can figure out why my phone wants to OC up to 1.3 even though setcpu is set to 1.2.... lol
With the latest 1.9, I'm actually seeing BETTER battery than stock kernel, so kudos to faux123.
I'm using more or less the same set of apps, and if anything there is more crap running now lol.
now if only I can figure out why my phone wants to OC up to 1.3 even though setcpu is set to 1.2.... lol
Last edited:
Can you use cwm to do a full wipe or does it have to be fastboot?
Sent from my MB860 using xda premium
From what I can tell, fastboot is the most comprehensive/safe way of doing it, some guides recommend running it twice.
However from all accounts if your CWM is v3 or better from Romracer then the wipe is fully equivalent to fastboot wiping. The older CWMs like the old tenfar didn't do it properly or something like that.
I used the Romracer CWM wipe to do full install of Alien v4 and had zero issues
Agreed..I'm running the 1.3 kernel and fastboot wiped everything before install (as well as did a fresh ROM / radio install) and am getting great battery life..even OC'd. I was still at 47% after 15 hours yesterday..with over 2hrs on screen time and 1.5hrs in phone calls.
Yes, same for me. I said to heck with it..let er rip....
Seems very stable..no reboots.
I'm rocking faux 1.9 ocd to 1.3ghz on cm7 prebeta 3 and after adjusting the volatges with appropriate undervolt, I'm getting stellar performance and pretty decent bat life considering the heavy use it gets. Can easily go all day even with the hrs of music listening and gaming done. Everything responds instantaneously
Sent from glorious master race of Atrix users xD
Do you mind sharing your undervolt settings just so I can compare mine. I tried some really aggressive ones but they won't stick.
Thanks in advance.
I've been running 1.3 on Alien ROM for a couple days now and I haven't noticed any battery drain at all (beyond normal). For a 1.3GHz kernel I'm really impressed with its efficiency. I have profiles set up in SetCPU to regulate it at times (screen off, low batt, etc) but it runs at 1.3GHz when under load. Haven't had a single reboot yet.
Like others though, it runs at 1.3 GHz under load regardless of what the main SetCPU screen is set for. You can set up a profile to keep it under 1.3 if you want (i.e. 1.2 or less when batt is < 100%)
Anyway, great job Faux.. can't wait to see the Atrix at 1.5GHz.
Undervolted at -25mV for all but 216MHz which is -75mV. Had more agressive settings on the 1.1GHz kernel but the 100mV step limit makes it more difficult on this kernel
Like others though, it runs at 1.3 GHz under load regardless of what the main SetCPU screen is set for. You can set up a profile to keep it under 1.3 if you want (i.e. 1.2 or less when batt is < 100%)
Anyway, great job Faux.. can't wait to see the Atrix at 1.5GHz.
Undervolted at -25mV for all but 216MHz which is -75mV. Had more agressive settings on the 1.1GHz kernel but the 100mV step limit makes it more difficult on this kernel
Last edited:
I'd like to see a battery usage screenshot with at least 10 hours on battery under typical use as well as an UV screenshot please
DK
I have been running Faux 1.9 @ 1.3 for the last day, still testing UV settings. Here are some screens:
Using Bluetooth to and from work every day (1 hour +/-), 45 mins of GPS, only a few calls (10 mins +/-), a little over 2 hours display time.
Using Bluetooth to and from work every day (1 hour +/-), 45 mins of GPS, only a few calls (10 mins +/-), a little over 2 hours display time.
yeah, I noticed that too. I added a very low priority for battery <100% and set it to 1ghz. When charging, it will go up to 1.3ghz.
I have been running Faux 1.9 @ 1.3 for the last day, still testing UV settings. Here are some screens:
Using Bluetooth to and from work every day (1 hour +/-), 45 mins of GPS, only a few calls (10 mins +/-), a little over 2 hours display time.
How did you choose 750 and 608 as maximums for your profiles? I'm only able to choose 216,456,800,1000, etc. Thanks.
Those were the number steps from the 1.1GHz OC, I haven't changed the profiles since then so the numbers stuck. You'll be fine getting close enough.
CPU not able to goto 216 Mhz setCPU with faux v1.9. In the setcpu program, it shows the Mhz, and the lowest it goes now is 301, wheres before on v 1.7 it would goto 216 Mhz
+1 on the heat...it's not scolding but it's significantly hotter than normal for me at least.
Unless the 100mV step limit has changed, I don't think your undervolt settings would stick like that. I've been having a hard time figuring out a good set now that we're up to 1.3.
Mine goes down to 216 still
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3
Here is a tip to avoid a soft brick in the future. Make a safety profile in SetCPU for a max speed/voltage you know will work. If you put the safety profile for "charging", then you just need to plug your phone in to trigger the safety profile and you can make changes.
I've used this to recover from bad overclocking judgments on other kernels.21Undervolt Settings??
EDIT: I am in the process of retweaking them lower, and running stress test for 10mins on each clock speed.1
mine said 546MHz because that was the clock speed it was running at in the range of 216MHz and 1300MHz.
The reason it shows max level when it opens is because the max "loaded" frequency is 1.3GHz, the lowest being "idle state" is 216MHz. Under operation you would not normally see the processor going to any of the in between frequencies shown in the voltage tables because its either doing work, or it is not. Therefore unless you have specific profiles setup for different frequencies, the only time you will see the other frequencies is probably when its loading, and unloading from the work.
EDIT: @Swiftks - Im an idiot lol, gonna be a little bit for retesting.. I forgot the 100mv rule.
New posts
-
-
-
[ROM][OFFICIAL][redfin] LineageOS 20
- Latest: OttoUsualConsumer
