Related
Hi
So I have a rooted Nook Color with CM7 Nightly Build 41 and Dalingrin's OC Kernel running at 1.1Ghz max / 800Mhz min. I have not disabled Cell Standby and i use Launcher Pro. My Nook's battery life seems to be less than 5 hours while i have seen other people get 10+ hours in the same situation. I have been using it considerably but i would think that my battery life would be greater.
One thing to note is that i did NOT fully charge the nook before using it like it said. Would this be the cause of such a low battery life? If so are the batteries replaceable?
Thanks
Moriarty
B_Moriarty said:
Hi
So I have a rooted Nook Color with CM7 Nightly Build 41 and Dalingrin's OC Kernel running at 1.1Ghz max / 800Mhz min. I have not disabled Cell Standby and i use Launcher Pro. My Nook's battery life seems to be less than 5 hours while i have seen other people get 10+ hours in the same situation. I have been using it considerably but i would think that my battery life would be greater.
One thing to note is that i did NOT fully charge the nook before using it like it said. Would this be the cause of such a low battery life? If so are the batteries replaceable?
Thanks
Moriarty
Click to expand...
Click to collapse
And what are you doing for those 5 hours? Games?
B_Moriarty said:
Hi
So I have a rooted Nook Color with CM7 Nightly Build 41 and Dalingrin's OC Kernel running at 1.1Ghz max / 800Mhz min. I have not disabled Cell Standby and i use Launcher Pro. My Nook's battery life seems to be less than 5 hours while i have seen other people get 10+ hours in the same situation. I have been using it considerably but i would think that my battery life would be greater.
One thing to note is that i did NOT fully charge the nook before using it like it said. Would this be the cause of such a low battery life? If so are the batteries replaceable?
Thanks
Moriarty
Click to expand...
Click to collapse
its because you have 800mhz min, set it to like 300
Well thats including standby but i have been running emulators for N64 and NES etcetera, But it seems like even without running games the battery drains rather quickly
Heres my Battery Statistics:
Display: 57%
Phone Idle: 9%
Cell Standby: 8% (Yes i know this can be disabled)
Android OS: 7%
Market: 5%
Dolphin Browser HD: 4%
Bluetooth: 3%
Wi-Fi: 3%
Cordy: 3%
Will setting it to 300 affect any performance negatively? Whats the benefits of having a higher min?
B_Moriarty said:
Will setting it to 300 affect any performance negatively? Whats the benefits of having a higher min?
Click to expand...
Click to collapse
it will not make the performance worse. setting it to 300 means that when the nook is doing nothing it will be at 300mhz which uses less power and battery.
EverythingNook said:
it will not make the performance worse. setting it to 300 means that when the nook is doing nothing it will be at 300mhz which uses less power and battery.
Click to expand...
Click to collapse
^this, instead of idling at 300, with your settings you are running at 800 all the time, thus your battery life is terrible. also set governor to interactive. if you have it at performance it would be running your nook at 1.1 all the time.
I think the default governor on Dalingrin's kernel is set to ondemand. Is interactive batter with battery life?
d00med said:
I think the default governor on Dalingrin's kernel is set to ondemand. Is interactive batter with battery life?
Click to expand...
Click to collapse
Conservative is better with battery life. Dal recommends interactive, since when the screen sleeps it drops to the min cpu setting and can go up to max if necessary. If you want a little more power he recommends setting interactive min to 600 although this will hurt battery life some. He never recommends performance as that keeps cpu running at max only.
There is a new testing 4/24 OC with max of 1300 for most and 1200 if 1300 does not work for your nook. He say that this has little effect over 1100 as the majority of battery life is determined by the display. I am using 4/23 OC at 1300 max, 300 min, governor interactive. The 4/24 OC kernel has the additional 1200 setting plus other improvements. I will probably upgrade to it.
B_Moriarty said:
Well thats including standby but i have been running emulators for N64 and NES etcetera, But it seems like even without running games the battery drains rather quickly
Heres my Battery Statistics:
Display: 57%
Phone Idle: 9%
Cell Standby: 8% (Yes i know this can be disabled)
Android OS: 7%
Market: 5%
Dolphin Browser HD: 4%
Bluetooth: 3%
Wi-Fi: 3%
Cordy: 3%
Click to expand...
Click to collapse
erm... how do you disable cell standby?
edit: nevermind, i found it
bradputt said:
erm... how do you disable cell standby?
edit: nevermind, i found it
Click to expand...
Click to collapse
You don't. It's pointless and just causes other problems, such as your volume keys won't work..
So how is battery life with the latest stable or nightly build?
I'm going to take the plunge and install CM7 tonight coming from an autonootered Nook running 1.1.
I've read that the devs have found a fix, just wondering if they have filtered into the newest builds.
GSUBass05 said:
So how is battery life with the latest stable or nightly build?
I'm going to take the plunge and install CM7 tonight coming from an autonootered Nook running 1.1.
I've read that the devs have found a fix, just wondering if they have filtered into the newest builds.
Click to expand...
Click to collapse
I've been getting verily bad batter life with my Nook (7.03 stable) and SetCPU at 1200/1300Mhz with interactive. I've played with it for 2.5 hrs and it has dropped 30%. Mind you, I watched one 30 min tv show, played two games for maybe 20-30 minutes, and browsed online and taptalk the rest of the time. Display settings are very low at 20%.
You aren't supposed to run SetCPU with CM7. Use the built in OC function and/or install an OC kernel.
Sent from my PC36100 using XDA Premium App
ramiss said:
You aren't supposed to run SetCPU with CM7. Use the built in OC function and/or install an OC kernel.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I am using the OC kernal and then setting it with SetCPU. AM I suppose to set the OC through CyanogenMod settings instead?
Sent from my Atrix 4G using Tapatalk Pro
ramiss said:
You aren't supposed to run SetCPU with CM7. Use the built in OC function and/or install an OC kernel.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
So, how would you set your low value (i.e. at 300) without SetCPU? I don't recall the default CM7 settings having this option (just the high OC).
crea78 said:
I've been getting verily bad batter life with my Nook (7.03 stable) and SetCPU at 1200/1300Mhz with interactive. I've played with it for 2.5 hrs and it has dropped 30%. Mind you, I watched one 30 min tv show, played two games for maybe 20-30 minutes, and browsed online and taptalk the rest of the time. Display settings are very low at 20%.
Click to expand...
Click to collapse
Only had battery drain 2% from 12:30 to 7 am. I am really liking this build.
dohturdima said:
So, how would you set your low value (i.e. at 300) without SetCPU? I don't recall the default CM7 settings having this option (just the high OC).
Click to expand...
Click to collapse
CM7 allows you to set Min/Max CPU Frequency as well as governor from within its own menus.
Settings -> CyanogenMod settings -> Performance -> CPU settings.
GSUBass05 said:
So how is battery life with the latest stable or nightly build?
I'm going to take the plunge and install CM7 tonight coming from an autonootered Nook running 1.1.
I've read that the devs have found a fix, just wondering if they have filtered into the newest builds.
Click to expand...
Click to collapse
The fix isn't in the stable or any of the nightlies yet. The most recent nightlies have a different fix, which prevents the speaker from running constantly, so the battery life will be better than it used to be, but nowhere near as good as you would get with real deep sleep.
The real deep-sleep fix is in the CM7.1-RC0-beta3.1 build. Its still a beta, and a few people have had some glitches, but it is running fine for me. And my nook now has the kind of battery life it had on rooted stock (before being unable to prevent an auto-update nudged me to CM7).
ramiss said:
You aren't supposed to run SetCPU with CM7. Use the built in OC function and/or install an OC kernel.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
you can run setcpu actually. the thing you can't do is run profiles on pre-beta kernels with setcpu.
set your minimum to 300mhz no matter what you use.. anything else is overkill that will result in battery kill..
in addition phone, mms, and telephoney apks have been proven repeatedly to have no impact on battery.
occasionally after flashing a new rom, recalibrateing your battery stats will do wonders.. ie. charge to 100% go into CW and reset battery stats, let it drain to below 10% then charge back to 100%. This is true of most Android devices.
The new beta build and kernels have improved battery a ton, they say these fixes will be incorporated to nightlys then stable CM7 eventually.
Please recommend me kernel for long battery life. Some time ago I had Cyanogen nightly with very good battery life, but then I decided to try ICS ROM, which appeared very laggy for me. So I installed fresh nightly (April, 6) and its drying battery very fast.
I'll try to install fresh nightly, but maybe it's better to install some other kernel?
By the way which governor do you guys prefer?
HWA is a battery hogger. Use juice defender (paid) or green power (free) for extra battery life. I use green power and i get one day with normal usage. BCM and Texas ice roms use kernels based on tiamat kernel. That's the only ICS kernel available as of now. Smartassv2 governor with oc max 1113, min 384
Sent from my icy cool nexus
For Gingerbread, try a kernel from Tiamat, Pershoot, or Wildmonk. Search on Nexus One Dev forum for more info.
Use smartassv2 governor. Try min 128 Max 998 for good battery life with good performance (set in cm7 performance settings, or use setcpu).
If your phone is hard to wake then try increase the min upwards from 128. Personally I have no issues running my phone using 128mhz min.
Up the Max if you want to experiment with overclocking, but I don't advise going above 1113.
Hope this helps.
Sent from my Nexus One using XDA
Which combination of governor and scheduler gives the best performance for ICS Stock ? And which one for better battery life ?
Akilesh said:
Which combination of governor and scheduler gives the best performance for ICS Stock ? And which one for better battery life ?
Click to expand...
Click to collapse
Other said it is pegasus and devs say it is all the same just a little difference.
jonpaslim said:
Other said it is pegasus and devs say it is all the same just a little difference.
Click to expand...
Click to collapse
I was told by the majority it goes in this order:
1) Pegasusq
2) Lulzactive
3) SmartassV2
4) Ondemand
5) Hotplug
6) Interactive
... and the rest.
And for IO Scheduler:
1) VR
2) CFQ
3) SIO
The truth is that, this is a Dual Core Phone with 1GB RAM, and improved Android 4.03+ kernel. So the previous hardware and software limitations NO LONGER applies. Coming FROM the DEVELOPERS of governors and schedulers the best ones seem to be:
1) InteractiveX2
2) HotplugX
3) Ondemand
... then lulzactive ~ pegasusq > smartassV2
And for IO Schedulers:
1) SIO
... then the rest
The truth is you should use the DEVELOPER recommended governor and sio scheduler, for an extensive period (1-2 days) and compare them. Finding what works best for you. After that's done, then you should go further stability testing with Voltage Control. Eg, UC your lowest frequency, OC your highest frequency and UV each step to the NEEDS of your device, each device is UNIQUE and functions DIFFERENTLY.
I think doing so you should extend your battery life by 1 or 1.5hour per cycle, while maintaining or increasing performance.
it all depends on the ROM + Kernel and more importantly the user and how they use their Note.
For me, I use Performance + Noop.. But ive had good results with pegasusq + sio
The only way to get the best combination is to try them all, But give them time to perform, Dont make a decision after 5 mins of usage, Test them heavily, Do some serious Gaming + Multitasking and chose one that outperforms the rest !
I'll start testing and post results from time to time.
Sent from my GT-N7000 using xda premium
azzledazzle said:
it all depends on the ROM + Kernel and more importantly the user and how they use their Note.
For me, I use Performance + Noop.. But ive had good results with pegasusq + sio
Click to expand...
Click to collapse
But the performance governor never scales down but always runs at maximum frequency. How is battery life with that? Must be horrible?!
Kangal said:
I was told by the majority it goes in this order:
The truth is you should use the DEVELOPER recommended governor and sio scheduler, for an extensive period (1-2 days) and compare them. Finding what works best for you. After that's done, then you should go further stability testing with Voltage Control. Eg, UC your lowest frequency, OC your highest frequency and UV each step to the NEEDS of your device, each device is UNIQUE and functions DIFFERENTLY.
I think doing so you should extend your battery life by 1 or 1.5hour per cycle, while maintaining or increasing performance.
Click to expand...
Click to collapse
I agree, governors even if they have the same stock names(i.e ondemand) has been heavily tweaked by the kernel dev so that you maximize performance and batt life. Start off by using the kernel/scheduler suggested by the kernel dev.
The only thing I care about is running out of juice when I don't have access to something that can charge my phone, as long as i get 10-15hrs off batt life and solid performance I'm good. Still I always bring a wall charger/usb cord with me if i really needed the extra juice.
Remember you can charge the battery but you can't charge performance
Coxeroni42 said:
But the performance governor never scales down but always runs at maximum frequency. How is battery life with that? Must be horrible?!
Click to expand...
Click to collapse
I get around 24 hours from my battery and I'm happy with that, besides I'm always somewhere where I can charge my phone should by battery run out
Sent from my GT-N7000 using Tapatalk 2
chickentuna said:
Remember you can charge the battery but you can't charge performance
Click to expand...
Click to collapse
This sentence doesn't make sense at all.
Unless you mean you can change or recharge the battery, which is straight-forward.
But you can "change" (increase) the performance. Just clear all background tasks, go to Voltage Control and overclock the cpu frequency upto 1.704GHz (with +1400mV) and keep it at that frequency by using the Performance governor. Also overclock your gpu upto 400MHz (with +1,000mV).
Though I don't recommend that, stability issues, warming issues and possible physical damage to your processor. But use the same concept, just not Overclock too much!
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
azzledazzle said:
I get around 24 hours from my battery and I'm happy with that, besides I'm always somewhere where I can charge my phone should by battery run out
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
That's simply NOT true.
Otherwise you have your phone in deep sleep/idle far more than the average user, barely using your phone.
Other possibility is that you've severely underclocked your maximum frequency, and have a long time in idle.
Performance governor = Always on maximum frequency.
NOTE's maximum frequency uses 1300+ mV. The NOTE's battery size is 2,500 mAh. Simple maths will tell you 24hrs is impossible ; )
But it is true I'm not saying my phone will be awake for 24 hours I'm saying I charge it roughly every 24 hours, I know performance keeps the phone at max speeds but I am human I will sleep for about 8-9 hours, so in result so will my phone.
And I don't use my phone every minute of the day I do have work to do so my battery life is what I say it is. What I consider 'average use' might be absolute minimal use to you so maybe that's why you doubt me,
I personally don't mess with voltages and things cause I don't understand them but I use note core kernel which is highly tweaked and one of the best kernels for battery life
Sent from my GT-N7000 using Tapatalk 2
My recommendation is lulzactive.
i use hotplug+sio on maclaws slim bean,, awesome battery life
Hi guys!! I was thinking about opening a thread where everyone can specify what's the better kernel setup, according to her/his own necessities, and share that configuration with all p880 community. Also, it can be submitted the relationship between the kernel and the ROM an user is running on the device, to compare performances and make each other more conscious about kernel tweaking. I think it's better to open it in general section, so everyone can write, without being scared by submitting something not related to developing.
This thread won't to be in any way a substitute of the "Battery life!" thread, so if anyone wants to post specifical results or screenshots about battery duration, please post them here:
http://forum.xda-developers.com/showthread.php?t=2478514
Said that, the idea is to post a message like this:
KERNEL: name of the kernel you are using
ROM: the name of the ROM you are running
SETTINGS: the kind of settings you applied to your kernel (example: Governor=interactive, Scheduler=Sio, Multicore Power Saving=2,CPUquiet=balanced, LP Core uV=-15 mV, MPU uC=+20, and so on)
GOOD: the benefits you experienced with your configuration (the more specific possible)
BAD: the badness you experienced with your configuration
Of course, if the thread begins to grow up, is recommended to read everything before posting a configuration too much similar to another which have been posted yet.
If you think this is a good idea, press thanks, if you want, and let's begin posting, otherwise report it to moderators, like @laufersteppenwolf, and they will close this thread as soon as possible
If someone like @JoinTheRealms is interested to, I'd appreciate very much to create a section dedicated to the scripts, as a second post of the thread, maintained and refreshed by the author.. Let me know, and take your own space here, if you think it's good for you!
So, I'm starting posting my own last configurations:
1)
KERNEL: iodak v9.95
ROM: Beanstalk 4.4.2
SETTINGS: Governor=interactive, Scheduler=Sio, CPU max speed undercloked to 1300 Mhz, CPU max screen off frequency=370 Mhz, Multicore Power Saving=1 ,CPUquiet=balanced, LP Core uV=-30 mV all frequencies, MPU uV=-75 mV all frequencies
GOOD: this configuration improve battery life, without decreasing overall smoothness - suggested to the users who don't mainly use the phone for hard gaming and want to find a compromise between battery durability and overall performance
BAD: some little lags, here and there, randomly happen - I suggest to apply underclock, before changing cpu freq voltage, because this configuration is good for 1300 Mhz undercloked device, but it may cause system freezes on some cpu variants, if you set cpu clock up to 1600-1700 Mhz (tested)
2)
KERNEL: iodak v10
ROM: Beanstalk 4.4.4
SETTINGS: Governor=interactive, Scheduler=Sio, CPU max speed undercloked to 1300 Mhz, CPU max screen off frequency=620 Mhz, Multicore Power Saving=1 ,CPUquiet=balanced, LP Core uV=-100 mV all frequencies, MPU uV=-100 mV all frequencies
This configuration is very battery friendly, more than the last one I was using on iodak v9.95. Nothing is slowing down, btw
@JoinTheRealms reserve a post to yourself, if you liked my idea to dedicate some space to scripts explaining
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Saved!
Lol, I'm using almost the same config.
Kernel: Iodak 9.9.5
Rom: Beanstalk 4.4.2
Settings: I haven't changed anything
Good: Very fluid and stable
Bad: battery life, Antutu 3D test score
Sent from my LG-P880 using xda app-developers app
Kernel: 9.95
Rom: CM11 official
Settings: Max Frequency 1150 Mhz Cpu governor:interactive
mpu undervolt -100 on every freq (cpu variant 2, some hangs while waking the smartphone and I need to tap on the screen sometimes, if I press the power button the device won't wake up anymore until I restart it).
Congestion: westwood
Cpu quiet: runnable
Cpu max screen off freq: 475 Mhz
Good: less heat, more battery life, smooth experience
Bad: If I put 1300 Mhz as max freq the battery life will decrease.. And without 1300 Mhz as max freq I feel like cutting this smartphone's cpu potential.
Still bad battery life even with these tweaks, still disappointed, but so far this is my best configuration with Cm11 official.
peppethustra said:
@JoinTheRealms reserve a post to yourself, if you liked my idea to dedicate some space to scripts explaining
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The scripts i posted earlier, really shouldn't be take too seriously, mainly because they are written for ubuntu and require input. But when i get some time ill modify my post and give some examples of init.d scripts, or more specifically, the commands inside them. That should be somewhat more helpful i guess
JoinTheRealms said:
The scripts i posted earlier, really shouldn't be take too seriously, mainly because they are written for ubuntu and require input. But when i get some time ill modify my post and give some examples of init.d scripts, or more specifically, the commands inside them. That should be somewhat more helpful i guess
Click to expand...
Click to collapse
Take the time you need, the thread seems beginning to live, so we'll read your post for sure, when you will bring it to evolution!
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Kernel: Optimus Play v2.53
Rom: CM11 official
Settings: Max frequency 1200 Mhz (sometimes I tried to put it at 1100 Mhz or even lower, 1000 Mhz, resulting in better battery life)
Congestion: cubic (since there's no westwood implementation in this kernel)
Cpu quiet: not implemented (I think it's put on runnable or balanced as standard)
Cpu governor: interactive
Multi-core battery saving: 1
Gpu frequency scaling: on
Good: awesome perfomances, the games and all the apps are very smooth and compared to the earlier configuration with iodak v9.95, this is very much better, but be aware that I'm trying to have perfomances and battery life balanced, and on iodak v9.95 I undervolted the cpu of -100mv resulting in some cases of hangs and crashes. Battery life is still good, but a bit worse than the iodak configuration.
Bad: Battery life's not very good, it goes harder on deep sleep when the display's off, iodak v9.95 is the best with deep sleep; in fact it takes a while before entering that state, it usually stays on low frequencies but it still consumes the battery.
An other aspect I noticed is that even when the smartphone is on charge, when I'm using it, it doesn't charge much, if ever it looses energy, which is explained by the very good performances of this kernel.
A small bug present in this kernel, and not in iodak, you usually need to double press the power button to wake the smartphone, but it's much better than risking to have your smartphone crashed while waking it up.
Overall: A very good kernel for performances, I don't know if it's the best but it's very good, battery life's "good" if not using the smartphone, otherwise it drains quite fast, I think faster than the undervolted configuration with iodak.
If you're looking for smoothness with games and apps I'd suggest this kernel, if you prefer battery life I'd suggest iodak more, but I remind you the hang problems on it if you decide to undervolt up to -100mv.
I tested both kernels with the same Rom and apps and use more or less, so I'm quite positive it's a good test.
I hope it helps and you can give us tips or suggestions to improve this smartphone's battery life, without losing perfomance. I think this is the thread's goal.
and yeah, every LG Optimus 4x hd possessor's dream is to have a good battery life so well, let's help each other and get the best out from this device, it's not **** yet in my opinion, it just really has a bad battery usage.
@KrisJoe Very good review! I hope many people will follow your example..comparing user's kernel usage and customizations is the better way to help everyone to find the needed configuration, and to let them make whatever they want, with their phone, on the best possible way
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
I just noticed something going back at iodak v9.95 to try peppe's configuration; on iodak v9.95 the temperature of the cpu is higher, there's a difference of at least 20° C more or less. Problem was that I went back to iodak because charging with optimus play v2.53 was a pain since instead of charging it wasn't. (Of course I mean while in use)
With iodak charging is flawless (I activated the fast charge option, which isn't present in Optimus Play).
Is it because of the fast charging option that's making the difference?
I'n trying the cpu undervolted by -75mv MPU and -30mv LPU, and it seems a bit laggier than the optimus play one, I can feel the difference just typing with the keyboard on the browser, but it's charging despite me using the smartphone.
What do you think it's the cause of the slow charge in optimus? And maybe more important thing, how is it possible that the cpu has a 20° C of difference between optimus and iodak but I keep the same frequency? I even undervolted with iodak, and in theory it should be the opposite situation, with iodak having lower temperature.
KrisJoe said:
I just noticed something going back at iodak v9.95 to try peppe's configuration; on iodak v9.95 the temperature of the cpu is higher, there's a difference of at least 20° C more or less. Problem was that I went back to iodak because charging with optimus play v2.53 was a pain since instead of charging it wasn't. (Of course I mean while in use)
With iodak charging is flawless (I activated the fast charge option, which isn't present in Optimus Play).
Is it because of the fast charging option that's making the difference?
I'n trying the cpu undervolted by -75mv MPU and -30mv LPU, and it seems a bit laggier than the optimus play one, I can feel the difference just typing with the keyboard on the browser, but it's charging despite me using the smartphone.
What do you think it's the cause of the slow charge in optimus? And maybe more important thing, how is it possible that the cpu has a 20° C of difference between optimus and iodak but I keep the same frequency? I even undervolted with iodak, and in theory it should be the opposite situation, with iodak having lower temperature.
Click to expand...
Click to collapse
So, talking about charging, on iodak's kernel you have to consider two situations: if you are charging through USB port, you may experiment slow charging and battery consumption even while charging, if you use the phone in the meanwhile (so, using fast charge solves the problem, but it is recommended to do not use it too many often, if you want your battery to have a longer life)..the problem doesn't exist if you charge the phone through AC adapter, so the phone should charge at a normal speed, even if you use it, whit no fast charge necessity.
Talking about my configuration, yes, you may have some little lags, here and there, 'cause this is a battery saving configuration, more than a gaming performance one..
Finally, temperature: maybe the difference between the kernels is due to a different overall cpu voltage, or the temperature is not really precisely shown, honestly I don' t know for sure
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
I'm using the ac adapter and with optimus play charging was a bit hard and slower than with iodak. With -75mv it seems I don't have problems with waking up the smartphone and it seems a bit smoother, maybe a placebo effect, but I think that it could be the limit of undervolting with variant 2 cpus.
Now that I didn't use the smartphone for while the temperature is lower (49-51° C), the high temperature was due to the 1500 Mhz used at the beginning because I deleted cache and dalvik before installing iodak again (to avoid problems). Let's see how it behaves in these days, but I'm a bit confident iodak's config is better for battery saving, even though with antutu benchmark I did 13000 with iodak and, and 12800 with optimus play (with battery saving and performance balanced). It may be a wrong test but I still wanted to give it a try.
Yep, I tried to uV MPU frequencies at -100 mV, and it freezed my phone, after some seconds or minutes..so, I also think CPU variant 0x2 has this uV limit..maybe it's possible to uV a bit more single frequencies, without causing freezes, but I had not the time to try to individually uV any single frequency
Sent from my ME301T - Beanstalk 4.4.2 - Geass Kernel - using xda app-developers app
I was thinking that we should specify what runtime we're using, if Dalvik or ART because I actually felt some differencies. What about you? Do you feel any difference with using one or an other? Sorry for the off topic, but I thought we could talk about the runtime also since we'll looking for the best performance/battery life.
O.T.: Don't activate ART Runtime on the latest cm nightly (3rd of April 2014), it will force close some apps like uicall, dialer, ecc. I had to return to dalvik by installing an older version in which ART was working... quite unconvenient.
This is the best thread ever guys.
I am using iodak 9.95 in Zaiben RC8.
Max 1000 mzh, interactive, no undervolting, Multi core savings 2
The only bad thing is that if i want to wake a the device it doesn't wakes for the first time and I have to press twice the power button.
KrisJoe said:
I was thinking that we should specify what runtime we're using, if Dalvik or ART because I actually felt some differencies. What about you? Do you feel any difference with using one or an other? Sorry for the off topic, but I thought we could talk about the runtime also since we'll looking for the best performance/battery life.
O.T.: Don't activate ART Runtime on the latest cm nightly (3rd of April 2014), it will force close some apps like uicall, dialer, ecc. I had to return to dalvik by installing an older version in which ART was working... quite unconvenient.
Click to expand...
Click to collapse
Yes, everyone is free to talk about ART or Dalvik, of course, it's related to Rom customization, using or not using it! Personally, I'm not using ART, considering it's on an early, experimental stage, and I have no time to switch between the two runtimes, if something should go wrong with ART (I need this phone as my really daily driver, and I haven't too much time to experiment, ATM).. But every single accurate review, also explaining how runtimes work, with a specifical kernel and a specifical Rom, is appreciated here!
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
XxXDarknessXxX said:
This is the best thread ever guys.
I am using iodak 9.95 in Zaiben RC8.
Max 1000 mzh, interactive, no undervolting, Multi core savings 2
The only bad thing is that if i want to wake a the device it doesn't wakes for the first time and I have to press twice the power button.
Click to expand...
Click to collapse
Try multicore powersaving=1, and a little undervolt, you should have benefits in terms of smoothness, without losing battery
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
KERNEL: Iodak 9.5 (I know 9.95 is newest but I prefer 9.5 as I think it's performance/battery ratio is better.)
ROM: CM 03/30 nightly
SETTINGS(variant1): CPU max: 1500 lowest freq.: 620 screen off max: 475. GPU freq max: 564 mhz
MPU undervolted by -122 mV and LP core undervolted by -10mV but lowest freq. voltage is on default and max freq is on 1230 mV due to 564 mhz GPU freq. ART enabled and Multicore powersaving is set to 2.
GOOD: A lot smoother than 9.95 and with these undervolting I've done, it can survive heavy gaming without throttling.I can say this setup is the best for gaming if you've got variant 1.
BAD: Battery life is a bit worse compared to stock kernel.But with ART enabled it's difficult to notice the difference.Plus if you underclock to 1300 mhz your phone will still be smooth while giving you better battery life.
ottomanhero said:
KERNEL: Iodak 9.5 (I know 9.95 is newest but I prefer 9.5 as I think it's performance/battery ratio is better.)
ROM: CM 03/30 nightly
SETTINGS(variant1): CPU max: 1500 lowest freq.: 620 screen off max: 475. GPU freq max: 564 mhz
MPU undervolted by -122 mV and LP core undervolted by -10mV but lowest freq. voltage is on default and max freq is on 1230 mV due to 564 mhz GPU freq. ART enabled and Multicore powersaving is set to 2.
GOOD: A lot smoother than 9.95 and with these undervolting I've done, it can survive heavy gaming without throttling.I can say this setup is the best for gaming if you've got variant 1.
BAD: Battery life is a bit worse compared to stock kernel.But with ART enabled it's difficult to notice the difference.Plus if you underclock to 1300 mhz your phone will still be smooth while giving you better battery life.
Click to expand...
Click to collapse
I have double press to wake bug with iodak 9.5 how did you solve it ?
CrazyWinner said:
I have double press to wake bug with iodak 9.5 how did you solve it ?
Click to expand...
Click to collapse
I use volume rocker to wake the phone up as a workaround.Easy to reach it with your midfinger once you have the phone in your hand.Plus you get to press the power button less, extending it's life.
Edit : Incase you didn't know official CM and most of the custom ROMs have volume rocker wake option in settings > button or under some other category.
I've been trying to achieve the best battery life without sacrificing performance on my Spice Dream Uno A-1 phone. After trying many custom kernels and ROMs I've developed a sweat spot for Zeus Kernel by Swapnil Solanki. As it provides many governors plus I/O schedulers with dt2w.
After using many CPU governors and apps like Amplify and Greenify. I found out this guide on xda: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557. Explaining advanced tweaking interactive governor.
Default settings of interactive governor used to spike up my phone's CPU to Max freq. I also tried using Monarch kernel with min clock speed of 200 mhz. But it was laggy.
Here are my (sprout4) settings with interactive governor (Zeus Kernel and RR build):
Go to 'CPU governor tunables'
1. above_hispeed_delay:
10000 747000:60000 1040000:20000
2. target loads:
98 747000:35 1040000:60 1300000:90
3. timer_rate:
25000
These settings will get you amazing CPU performance with max battery life possible.
You can also turn on 'Thunderplug' from kernel settings. I personally use it with 35% load threshold. I'm Getting best battery ever. What about you ?
Try and tell me.
@sumeet240
What do you mean by best battery? Atleast provide screenshot and tell Screen On time.
And BTW this should be in general thread
I'll post screen shots tomorrow I'm away from charger. Sorry for posting this here. You should try tweaking it; it'll take 15 min maximum.
Sent from my Spice Mi-498 using XDA Free mobile app
BTW on what brightness should i test my battery life. I generally keep brightness on medium (no auto). I think I'll be able to get three and half hour SOT (3G usage Twitter+Movie) on brightness set to almost center of the slider. Using resurrection remix latest nightly.
5-5.5 hours on decent brightness; 3G usage
sumeet240 said:
I'll post screen shots tomorrow I'm away from charger. Sorry for posting this here. You should try tweaking it; it'll take 15 min maximum.
Sent from my Spice Mi-498 using XDA Free mobile app
Click to expand...
Click to collapse
I am trying it on CM13 Snapshot. Will report later
sumeet240 said:
I've been trying to achieve the best battery life without sacrificing performance on my Spice Dream Uno A-1 phone. After trying many custom kernels and ROMs I've developed a sweat spot for Zeus Kernel by Swapnil Solanki. As it provides many governors plus I/O schedulers with dt2w.
After using many CPU governors and apps like Amplify and Greenify. I found out this guide on xda: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557. Explaining advanced tweaking interactive governor.
Default settings of interactive governor used to spike up my phone's CPU to Max freq. I also tried using Monarch kernel with min clock speed of 200 mhz. But it was laggy.
Here are my (sprout4) settings with interactive governor (Zeus Kernel and RR build):
Go to 'CPU governor tunables'
1. above_hispeed_delay:
10000 747000:60000 1040000:20000
2. target loads:
98 747000:35 1040000:60 1300000:90
3. timer_rate:
25000
These settings will get you amazing CPU performance with max battery life possible.
You can also turn on 'Thunderplug' from kernel settings. I personally use it with 35% load threshold. I'm Getting best battery ever. What about you ?
Try and tell me.
Click to expand...
Click to collapse
First of all you should learn not to post discussion threads in Android One Original Development forum. This post belongs to general forum.
If you don't understand what i am saying refer to forum rules first. Just wait it will be posted on where it belongs.
I apologize.
https://www.youtube.com/watch?v=JmvCpR45LKA
Can someone tell me what's wrong ? I attached the ss .
DarkHeart Z said:
Can someone tell me what's wrong ? I attached the ss .
Click to expand...
Click to collapse
I don't know if this will work for you. But you should not be using dark theme for better battery life. Dark theme needs more brightness than white ones. And LCD displays are always backlit.
sumeet240 said:
I don't know if this will work for you. But you should not be using dark theme for better battery life. Dark theme needs more brightness than white ones. And LCD displays are always backlit.
Click to expand...
Click to collapse
I too thought dark means less bright screen and hence more battery
I'm getting worse battery life after a year of usage. What can we expect from a 1700mah device. 4 hrs+ is still good though :angel: