Hey everyone - just a little thing I'm curious about.
How come the choice of launcher changes my battery life in standby?
I've been using different kernels and roms lately. Mostly CM7 variants (nscollab etc) and trinity or netarchy kernels.
And no matter where I am and what I use: flashing UD launcher almost halves my battery drainage in standby. Which is why I use it: The point is I don't understand how that can be because I would like to use other launchers. I really enjoy the extra comfort adw and go launcher offer and the stock launcher is still the smoothest of all.
So what are they doing in standby that's draining battery? When comparing them of course I always use the same widgets, the same sync settings, juice defender config etc.
Atm I'm using cm7.0.2 with UD launcher flashed on top of it and morfic's trinity UV kernel with 1.1 Ghz.
According to battery monitor widget history standby drains around 5mA averaged over 5 minutes with adw in it's cm7 variant and stock launcher. with ud launcher it's around 2-3.
you would really have to do a do a controlled study and test the different ones and dig into source code, where possible. i dont know, i've always stuck with launcher pro and never tried any other to see a battery issue.
my nexus one in deep sleep hovers at 6mA idle power draw over night during 8 hours. i'm surprised the nexus s sees 5mA as well, for some reason i thought the better CPU hardware would have dropped idle power even lower, to around 2mA or so.
the HTC inspire for example is the best i've seen on any android phone so far. it can hit 2mA idle and stay there.
i do an 8 hour battery test every night while i sleep, and check the logs when i wake up. i'm weird.
Related
I am running Faux-AOSP-1.3.1 with the Trinity kernel 2.6.32.45 overclocked to MHz. I turned auto brightness off. I have profiles setup in setcpu for calls, screen off, charging, battery temp, and battery level all set to 1000MHz. I have a crap ton of apps installed and no live wallpaper. Yesterday I used my phone to make phone calls, text, emails, xda, download some apps, picture messaging, and Facebook. I woke up this morning and I had almost 20 hours on that charge. I think that is excellent battery life for a 2.3.5 ROM that is not Miui. I know Miui gets awesome battery life because I have used that before but I could not believe that I got this kind of battery life out of this ROM overclocked so much. The quadrant scores are between 4500-4900. I have yet to have a screen of death, reboot, or freeze on this ROM and I have been using it for the past 4 days. I just thought that I would share this with everyone.
tidewaterns said:
I am running Faux-AOSP-1.3.1 with the Trinity kernel 2.6.32.45 overclocked to...
Click to expand...
Click to collapse
I've always experienced outstanding battery life on Faux's AOSP 1.3.1 (he mentions there's a 1.3.2 in another post but i've been unsuccessful in tracking it down). I don't get those screaming quadrant scores you get but Faux's AOSP is a battery sipper!
EB 2.3.3 version 1.0.7
I got over 18 hours of battery life with charge, moderate use, and didn't have to do anything other than flash ROM.
Its about the only thing that sucks about CM7 based ROMS, battery life just terrible and a bunch of modifications are needed just to extend battery life.
Stock 2.3.3 based ROMS aren't so bad, except that Netflix don't work, Lock Screen doesn't have music widgets, and music player widget sucks.
I generally get around 20 hours with faux, too bad his kernel wont work in the new nightly yet
I am playing a bit with underclocking my DS (Using UNITY v4 kernel atm, will update to v9 later).
However, I'm figuring out the usefulness of it (to extend battery life mainly).
Does it really save battery life? I'm already using JuiceDefender, and its SetCPU function.
Or is it not very useful since the most batterydrain comes from radios anyway.
What are the best values for it?
What's the standard clockspeed for the DS? And what is the best Max IDLE clock speed?
Well, i wont underclock at all.
First of all there is no need to do that to get good battery life. You can do lot other stuff to do so.
Under-clocking is risky as it might now have enough power that needed to the phone. that means that some stuff might not get processed like calls and stuff.
Right now with me using miui i get life for about 3-4 days.
Standard clock speed is 1,000mhz.
I have mine underclocked to 600mhz during idle times and it's perfectly fine.
Never had any issues at that speed and it keeps my Desire S much much cooler which can only be a good thing.
As for it's ability to extend the battery, I don't think it does so much in my case. I typically run WiFi overnight and G/3G/H during the day and my display usually chews up 60-70% of my overall battery usage even on a very dark screen.
I'd pick a setting that you feel comfortable with but have low expectations of the benefits.
The only time I use underclocking is for using Google Navigation.
On a hot day using Navigation for over a couple of hours, my DS would over-heat and restart (usually as I was approaching my motorway exit). So I have Tasker dialing back CPU to 768Mhz when using Navigation, and it does seem to help the phone run a little cooler. I no longer have to take it out the case for example.
Using the smartass governor (I believe) automatically knocks the CPU back to 240Mhz when sleeping. Not 100% on that though.
I'm currently testing a new kernel, and I spent an entire charge cycle on 'Smartass' and then an entire charge cycle on 'Powersave'. Aside from lots of lag on the latter one, the battery life was pretty much the same!
I'm running nscollab 1.60 with Franco kernel and was wondering if anyone's got some good custom voltage settings I can test out for a stronger battery life?
Essentially I'm a data user. Usually on the screen 4+ hours of the days, running market, fb and browser and of course texting.
Currently I'm messing around with smartassv2 200/800 deep idle off, BLN off, and kernel default voltage and I'm about to run my first battery calibration ...
Thanks on advance
EDIT: another side note is I've noticed my screen gets pretty hot now. When I'd run stock GB it wouldn't do that.
Hello,
i'm new on the Nexus S. I had a Milestone and tried pretty much every custom rom, as the Milestone stock rom was slow, unstable and outdated.
I read many times "great battery life" within the description of Nexus S custom roms (e.g. Codename).
BUT, is it better than the stock-kernel battery-life? And how much better (guess)?
I ask, because most of the Roms are overclocked and perhaps the "great battery life" is relative to those speed-optimized roms.
For me the speed of the stock rom is totally okay and it seems totally stable. I would only "custom-ize" it, if the battery life would be (significant) better – else: "Never change a running system!"
AK
p.s. Links are welcome, as i didn't find any comparison like this.
I have found stock GB rom was a battery hog. I tried a few roms but loved that CNA will pull all your apps from the market for you(I didn't have to download them all manually)
With a custom rom you can change more settings, you can change governors, you can change the cpu speeds and voltage. With deep idle sleep working your phone sips power when in your pocket. I like the Air Kernel,3.x with the scary setting, seems to use lower cpu frequencies more often.
you can find roms that are stripped down to next to nothing, these should give you better battery life then stock, to fully loaded roms that most likely will not give you better battery life.
I have my cpu set to 200 min and 1400 max running air kernel with the scary governor. scored around 2500 on Quadrant and battery last pretty good as when I just have the screen on, not doing much the cpu is running 200Mhz and the phone goes in to deep sleep right away.
try CPUspy and cool tool, CPUspy lets you see the states the cpu is using for a given time and cool tool can display cpu/power details in the top bar.
Through my ROM testing with ICS, most ROMs give very comparable battery life. Battery life relies very little on the ROM itself assuming there is no wakelock or similar issue which is because of the ROM, which in a good ROM there won't be. There may be some settings which are added or changed that have some effect, but likely nothing very major, especially in my experience.
Normally the bloatware is what drains battery with unused apps opening in the background.
Custom ROMs omit and give the option of certain bloatware.
Also some ROMs have great idle compared to stock.
But overall if u control ur mobile data, wifi, gps and sync then u can better or great battery life on any ROM just as long as its not a newer ROM that is still testing. And most custom ROMs have the pull down notifications that make it easier to control all of them.
I personally use SLIM ICS and its comes simple enough that u customize it.
Vs Nexus S 4G
Hi all,
I have been using the ONDEMAND CPU governor for quite a while on my SGS4G running CM9 (Team Acid's version, the final herring one), and I have just gotten used to the 12-14 hour battery life that I have had ever since I switched from GB back in August 2012. However, most of the frequent users here recommend the SMARTASSV2 governor, so I tried to use that yesterday to see if battery life was enhanced.
If anything it seems that my battery life got worse (see attached picture). I am a moderate phone user in general; I use my phone for texting mostly, and sometimes I'll look something up on the Internet, but no music, WiFi and GPS are always turned off, no overclocking/undervolting. I recently purchased a new battery as my old one died about two months ago.
I was wondering, is there any governor for the CM9 ROM that is particularly good with battery but doesn't completely drain performance?
(Also, I tried to use the LZ kernel before, but it seemed to cause many more problems than it fixed.)
You've got some pretty bad wakelocks going on there. See how your phone is awake even though your screen is off? That is an issue. Also how much screen on time did you have on that run? Get Better Battery Stats(free on XDA) then fully charge and look at what wakelocks are occurring. You might also want to consider UVing if you want better battery life.
Also, if you're a fan of ondemand, I highly suggest moving to ondemandX, which actually does deep sleep when the phone is off.
But that will only help if you fix the wakelocks first. So follow hechoen's advice and your phone should be way more awesome.
Downloaded BBS today, we'll see how it goes.
Sent from my SGH-T959V using xda app-developers app