Related
Ever since I first released an undervolted kernel (can you believe that it actually used to be a new idea? Seems so normal now), its been a mad dash to see how much further down the voltage can be pushed. In light of recent events, there has been controversy regarding whether or not dropping below ~925mV actually begins to negatively impact battery life.
Without getting into the technical details behind why I believe that going that low actually does affect battery life, I'm conducting a blind study. I'm going to produce 3 kernels at three different voltages. I'm then going to send these kernels randomly to people that sign up on the attached spreadsheet in order to collect data for 7 days.
I know that this won't be 100% accurate, but I feel that if we get a large enough sample size, over 7 days, the general trend should emerge.
What I ask for you to do if you want to participate is sign up on the attached spreadsheet and try not to change your rom/usage patterns within these 7 days. Just go about your day and record your values at the end.
You will not know what the voltage of the kernel you are receiving is, so there will have to be a certain degree of trust. I promise I will do my best to not blow up your phone
This truly has to be a community effort. The more people we have, the better. Once the study has been concluded, I will reveal which kernel had the best battery life for the most amount of people.
Please spread the word about this, the more it is on blogs and the like, the greater the sample size and the more accurate the results.
Link: http://bit.ly/9YjM5X
UPDATE:
The kernels have all be emailed to people that gave me an email address. Tues-Sat, please run the kernel that is labeled CONTROL. Do not alter your day to day usage from what you always do. At the end of each day please record how long you were off charger and your percent battery left. Use your best judgement for giving statistics. The more detailed, the better.
Sunday-Thurs we will run the TEST kernel. Again do the same thing and record your usage daily.
It is VITAL that you record the statistics at the end of the day every day.
As an added bonus, I included the memory modification by coolbho3k because I know you all want the latest and greatest
Will it matter what battery we have? Or is stock battery required?
Four Fourty Four said:
Will it matter what battery we have? Or is stock battery required?
Click to expand...
Click to collapse
doesn't matter as long as you post your previous results so we have something to base it against.
This is a fantastic idea. Might actually help me recover from my kernel flashing compulsion. Prolly not though....
Persiansown, what do you mean by "record your values at the end"? Are we to take a log of battery usage or just writing down on the sheet what the usage was like each day?
thanks
jblazea50 said:
Persiansown, what do you mean by "record your values at the end"? Are we to take a log of battery usage or just writing down on the sheet what the usage was like each day?
thanks
Click to expand...
Click to collapse
Its going to be subjective but I'm trying to figure out the best way to record them right now. I don't need any feedback values until I actually send out the kernels though
persiansown said:
Its going to be subjective but I'm trying to figure out the best way to record them right now. I don't need any feedback values until I actually send out the kernels though
Click to expand...
Click to collapse
yeah, i understand that it's not needed until after we start using the kernel; just wanted to know what you were actually looking for, and if it wasn't subjective
thanks and looking forward to this
im really interested in this. would it also be possible to give feedback on reception? because as of late my signal has been worse with all the uv kernels...
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
pjcforpres said:
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
Click to expand...
Click to collapse
Yeah I've been trying to think of a way that would take less time, but I think that way would be best. Anyone have a better suggestion?
persiansown said:
Yeah I've been trying to think of a way that would take less time, but I think that way would be best. Anyone have a better suggestion?
Click to expand...
Click to collapse
We could also look at time spent "running" in spare parts... but that would be much more complicated and less accurate (I would hate to do the statistical break down on that)... but it would be much quicker and would provide some nice info as well... ie 5 hours spent running and 7 hours sleeping used 80% battery... where as 1 hour running and 11 hours sleeping used 50%... but we would also have to factor in so many other aspects and track those to get a truly accurate picture, ie WiFi or 3G or 2G... what is your screen brightness... and so forth.
Hey persian, this is a great idea!!! to get to the bottom of all this.
Can I suggest something though, and hope I don't get flamed for it, or hope you wont take it the wrong way. But will you include, an AVS kernel running 800mV as well? There have been discussions about this also. Thanks!
Each tester would have to test all three kernels and try to maintain roughly the same useage. Was this your plan?
pjcforpres said:
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
Click to expand...
Click to collapse
This is a good approach. But I think for it to be even more standardized one would need to run this completely app and theme free. THe interaction between certain apps and usage is an unknown variable. For example, how much does K-9 mail draw? It goes without saying that themes have some sort of affect on behavior. So IMO, to be as objective as possible you would need to remove all sources of ambiguity to have this test mean something. Just my two cents
pjcforpres said:
We could also look at time spent "running" in spare parts... but that would be much more complicated and less accurate (I would hate to do the statistical break down on that)... but it would be much quicker and would provide some nice info as well... ie 5 hours spent running and 7 hours sleeping used 80% battery... where as 1 hour running and 11 hours sleeping used 50%... but we would also have to factor in so many other aspects and track those to get a truly accurate picture, ie WiFi or 3G or 2G... what is your screen brightness... and so forth.
Click to expand...
Click to collapse
That would be pretty complicated and I think Kmobs would need a grant to run the statistics. I think there would have to be a baseline established like GPS off, brightness set to x percent, bluetooth off etc. And I think as Kmobs knows, each chip was not created equally.
Persiansown, I don't think you need to start with a baseline in order to compare. Once you send out the kernel and we use it for 1 week with normal usage for each user. At the end of the week, you can send out another kernel, exactly the same this time for everyone, and we can use it for few days and we will be able to notice the difference.
Correct . This is how I thought he was gonna do it. And what I think is best.
jblazea50 said:
Persiansown, I don't think you need to start with a baseline in order to compare. Once you send out the kernel and we use it for 1 week with normal usage for each user. At the end of the week, you can send out another kernel, exactly the same this time for everyone, and we can use it for few days and we will be able to notice the difference.
Click to expand...
Click to collapse
pjcforpres said:
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
Click to expand...
Click to collapse
persiansown said:
Yeah I've been trying to think of a way that would take less time, but I think that way would be best. Anyone have a better suggestion?
Click to expand...
Click to collapse
I was trying to think of a good way to get a baseline to compare to for every one and this is my sugestion. Make three kernels at 850, 925, and control/stock. Send everyone on the list two kernels, one of the two UV kernels and one stock/control. Allow them to run the first kernel for a certain number of days, record data, then send everyone the second kernel and do the same. Randomize who gets the control first or the UV first and keep it blind. (Don't tell them which of the two is the control obviously.) This way half test the 850, half test 925, and all test the control/stock, giving you an accurate baseline for everyone's individual phone usage and battery size.
Scientific Method FTW!!!
awesome idea.
Count me in...I will sign up when I get home from work tonight. This is an excellent idea. Ideas lke this is what make xda the number one source for android information.
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
just experiment, start with small increments (don't save your settings!!!) see if it reboots, if its stable for a day or two, increase it, when it starts crashing dial it back a notch.
Just like overclocking except in reverse and with voltage basically.
note I'm not sure re: kernel requirements, I haven't tried it yet with my atrix, and my current ROM runs stock kernel I think.
its hit and miss, for example on my SGTab I can't undervolt at all or else it crashes all the time, others get away with -100mAh across the board (bastards), but mine is happy on 1.1OC.
WTFsandwich said:
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you like cars it seem this will be the best way to explain it
http://forum.xda-developers.com/showpost.php?p=15947019&postcount=643
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Yes, start conservative.
Another way to use setcpu to improve your battery life is to set a screen off profile to restrict the CPU speed to minimum when the screen is off.
I tried that one, but it kept stalling my phone when turning the screen back on when it was at the bare minimum.
EDIT: For anyone wondering, -75 seems to cause frequent freezes.
Sent from my MB860 using XDA App
mramirezusa said:
If you like phones it seem this will be the best way to explain it
Think of it as tweaking the CPU of a phone to use just enough power to prevent it from failing in order to conserve battery life without affecting it's normal operation.
Click to expand...
Click to collapse
Fixed that for ya!
WTFsandwich said:
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Any overclocking or underclocking is always trial and error. Rule of thumb is to only ever change one thing at a time in small increments, then test before adjusting again. Your approach should be methodical and not haphazard, i.e. in a PC change cpu clock speed in small increments until you fail to boot or BSOD, then change voltage in small increments until you boot and are stable again. Monitor temperatures all the time, and add cooling if necessary. If you take a methodical approach, and don't rush things, you can achieve surprising results with hardware/software tweaking.
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
A good test is to just use it as you normally would. If the phone doesn't reboot, you're good to go.
Sent from my MB860 using XDA App
edit: pls delete
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
WTFsandwich said:
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Do something CPU intensive also to see if it crashes, like play a game. You want to stretch the phone to the limits to test it at the most extreme condition you will use it under.
WTFsandwich said:
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
Click to expand...
Click to collapse
Maybe a factory/data wipe?
Other than that I can't think of anything myself.
ddddddddddddd
you may try to use default stock kernel, on wich overcloking do not work.
re: setcpu, sorry I think you have to reflash... thats why you don't save the settings until you're sure
there is no shortcut way.... you may be fine for a day but next day it keeps crashing. Happened to me on my SG tab when I went to 1.2 for example, I thought it was hunky dory then a few days later crashing galore.
the longer you leave it for the better you are, its really your call to make. Some people prefer the extra speed and will live with a crash or two a week (not me, its my phone not gaming pc lol).
not sure how much stress testing you can/should do. Back when I was OCing PCs I would leave stress tests running overnight, but probably not a good idea to 100% CPU a phone overnight lol
I'm a new Galaxy S II (and new Android) user, and am a bit disappointed in the battery life of my new phone. It was running down extremely quickly yesterday, only lasting about 12 hours with relatively normal use (sending half a dozen texts, downloading 2 apps, checking Facebook and Twitter once an hour or so for a couple of minutes throughout the day). I allowed the phone to discharge completely and charged it fully last night, but this morning nothing seems to have improved. I burned up 10% of the battery in half an hour sending 2 texts, checking my emails, Facebook and Twitter and downloading and trying out a couple of apps.
I'm anxious to know if there's a bit of a burn-in time with the battery on this thing - does it get better after a few charges? I see a lot of people saying they can have the phone on for a few days in some cases, but that's definitely not my experience thus far.
I've installed JuiceDefender (balanced profile), AutoKiller Memory and Advanced Task Killer to try to sort things out but none of them seem to having too much effect and to be quite honest I'd rather not have to compromise my experience by running a number of apps like this to try to extend my battery life at all (nor do I want to have to turn the brightness right down to an unusable level, or set black wallpapers for example).
Does anyone have any real advice on this? I'm starting to think that switching ROMs might be worthwhile? I see that the leaked 2.3.4 ROM seems to have better battery life - is this correct? I'm a bit reluctant to switch to any other unofficial ROMs as there are so many I wouldn't know where to start. It seems they all make a lot of changes but I'd want to keep as close to the stock feel as possible, just with better battery life.
no one uses stock roms/kernels nowadays. u should flash a custom rom or kernel since they provided optimizations to batt life.
StevenBX said:
I'm a new Galaxy S II (and new Android) user, and am a bit disappointed in the battery life of my new phone. It was running down extremely quickly yesterday, only lasting about 12 hours with relatively normal use (sending half a dozen texts, downloading 2 apps, checking Facebook and Twitter once an hour or so for a couple of minutes throughout the day). I allowed the phone to discharge completely and charged it fully last night, but this morning nothing seems to have improved. I burned up 10% of the battery in half an hour sending 2 texts, checking my emails, Facebook and Twitter and downloading and trying out a couple of apps.
I'm anxious to know if there's a bit of a burn-in time with the battery on this thing - does it get better after a few charges? I see a lot of people saying they can have the phone on for a few days in some cases, but that's definitely not my experience thus far.
I've installed JuiceDefender (balanced profile), AutoKiller Memory and Advanced Task Killer to try to sort things out but none of them seem to having too much effect and to be quite honest I'd rather not have to compromise my experience by running a number of apps like this to try to extend my battery life at all (nor do I want to have to turn the brightness right down to an unusable level, or set black wallpapers for example).
Does anyone have any real advice on this? I'm starting to think that switching ROMs might be worthwhile? I see that the leaked 2.3.4 ROM seems to have better battery life - is this correct? I'm a bit reluctant to switch to any other unofficial ROMs as there are so many I wouldn't know where to start. It seems they all make a lot of changes but I'd want to keep as close to the stock feel as possible, just with better battery life.
Click to expand...
Click to collapse
It is argued that task killers and memory killers will only make the problem worse. Juice Defender might be useful if you are using it for scheduling sync and turning WI-FI off when the screen is off, but this feature is only present in the Ultimate edition and you can turn off sync and WI-FI manually if you want. Also beware of rogue apps which are syncing all the time. It is normally the main reason of poor battery life.
Other reason, is that whereas powerful tech specs for phones were rapidly developed, battery technology didn't followed the pace. Our simply batteries cannot cope with our beasts.
Also, there is a thing that it's called "new phone battery blues" which is described as poor battery life due to excessive use of a new powerful toy. After you use your phone normally, for the purposes that normally people use a phone, your battery life will became better.
That said, personally I have a spare battery and a spare charger, and when the battery being used is low, I replace it with the charged one. Sometimes it is necessary, sometimes not.
poch_1421 said:
no one uses stock roms/kernels nowadays. u should flash a custom rom or kernel since they provided optimizations to batt life.
Click to expand...
Click to collapse
They also have a tendency to look very tacky I think though. I think Samsung's skin and widgets are pretty nice and don't care too much for the mods I see in the screens of most ROMs. I'm really looking for something very similar to stock, except with better battery life if there are any suggestions? That's why I was thinking of just jumping to the leaked 2.3.4 if it had any noticeable impact on battery life...
Try using better battery stats, link in my sig, to see if you have any wakelocks, the thread has a good howto on using it.
The biggest thing that uses the battery on this phone is the screen, you will get between 4 and 6 hours of screen on time depending on usage and screen brightness.
Sent from my GT-I9100 using xda premium
Get the original samsung 2000mah extended battery kit.
ahh the battery life talk again
brings back memories of the first days of the SGS2
never thought of reading one again
update to the newest ROM
and read the 1000+ threads about this topic
good day sir
StevenBX said:
They also have a tendency to look very tacky I think though. I think Samsung's skin and widgets are pretty nice and don't care too much for the mods I see in the screens of most ROMs. I'm really looking for something very similar to stock, except with better battery life if there are any suggestions? That's why I was thinking of just jumping to the leaked 2.3.4 if it had any noticeable impact on battery life...
Click to expand...
Click to collapse
Fair point - not all of the roms are everyone's cup of tea. My advice, as a starting point is to flash the stock XXKH3 variant for your area, and then flash a custom kernel, such as Ninphetamine's or Hardcore's Speedmod. This will greatly help with battery life, and also give you the ability (via root access) to use Titanium Backup to freeze apps and services you're not using, which is often the major cause of battery drain through 'wakelocks'; apps that prevent your phone from entering Deep Sleep, or continuously wake it up.
Update to the latest version in your area, uninstall those task killers and whatnot or do a factory reset, install the apps that you are going to use normally like facebook twitter and install better battery stats, decrease brightness to your most tolerable level.
use the phone normally and when the battery is low, use the tool provided in android to check if your phone is sleeping when the screen is OFF, if you are having wakelocks, then use better battery stats to find which apps are causing the wake locks.
No need to install battery management apps, or task killers or memory optimization apps (or as custom rom as yet), that would only compound you problem which may be a very small one to begin with
Thanks for the help so far guys. I've installed XXKH3 and flashed hardcore's Speedmod kernel, and am just getting things set back up the way I like them again. I'm going to uninstall the battery saving apps for now and see how the battery lasts the next couple days.
I'll install Better Battery Stats and keep an eye on any wakelocks too.
Thanks for pointing me in the right direction - it was all very simple and quick to get set up; the sheer number of kernels, ROMs, etc. is all a little overwhelming to me right now, being new to Android!
poch_1421 said:
no one uses stock roms/kernels nowadays. u should flash a custom rom or kernel since they provided optimizations to batt life.
Click to expand...
Click to collapse
I'm using stock KH3 with a stock kernel and am perfectly happy with the battery life ...
Im also a noob just got phone. Coming from evo, how do I root,
Sent from my SPH-D710 using xda premium
StevenBX said:
They also have a tendency to look very tacky I think though. I think Samsung's skin and widgets are pretty nice and don't care too much for the mods I see in the screens of most ROMs. I'm really looking for something very similar to stock, except with better battery life if there are any suggestions? That's why I was thinking of just jumping to the leaked 2.3.4 if it had any noticeable impact on battery life...
Click to expand...
Click to collapse
there are other tweaks with custom roms that aren't found in the stock rom (which provides better functionality).
btw, i also suggest u use setcpu to underclock your device to save more batt.
--------
chalid said:
I'm using stock KH3 with a stock kernel and am perfectly happy with the battery life ...
Click to expand...
Click to collapse
wow, good for you
I used HTC Desire before this device, and the roms on there actually hindered battery life, even with all the fancy underclocking, so I am betting, without even attempting to brick my phone, that they are just as overhyped on this phone too.
I get two to three days out of my phone, using it as a PHONE. I can send and receive emails and texts all day, along with phone calls and the occasional browsing and still get at least two days before it dies. I turn off data when I dont want it and stick it in 2G mode and it dares me to kill the battery.
Just let usage settle down and it's fine
Uamore6 said:
Im also a noob just got phone. Coming from evo, how do I root,
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I used this guide to install the latest firmware, and this guide to root it when I was done.
---------- Post added at 03:11 PM ---------- Previous post was at 02:59 PM ----------
poch_1421 said:
there are other tweaks with custom roms that aren't found in the stock rom (which provides better functionality).
btw, i also suggest u use setcpu to underclock your device to save more batt.
Click to expand...
Click to collapse
I've now installed SetCPU too, set to OnDemand. Thanks for the suggestion!
StevenBX said:
I used this guide to install the latest firmware, and this guide to root it when I was done.
---------- Post added at 03:11 PM ---------- Previous post was at 02:59 PM ----------
I've now installed SetCPU too, set to OnDemand. Thanks for the suggestion!
Click to expand...
Click to collapse
Beware using anything that isnt ondemand on samsung phones, can cause stuttering, that's what I found anyway.
As far as undervolting -25 to -50mv is a safe first bet.
Sent from my GT-I9100 using xda premium
poch_1421 said:
no one uses stock roms/kernels nowadays. u should flash a custom rom or kernel since they provided optimizations to batt life.
Click to expand...
Click to collapse
Which ones provide the best battery life?
It's not very helpful if you don't direct this poor guy in any direction.
Cheers!
vlad88667 said:
Which ones provide the best battery life?
It's not very helpful if you don't direct this poor guy in any direction.
Cheers!
Click to expand...
Click to collapse
Use touch x-power 1.0
It is optimized for battery life
Sent from my GT-I9100 using XDA App
stop the madness.... just disable Gtalk autologin and you'll have x3 batt life....
i'm still on KG2 and see no need to update, as i easily get 2d+ battery life now...
EDIT: oh, and custom roms is for nerds. that's it. stock only.
poch_1421 said:
no one uses stock roms/kernels nowadays. u should flash a custom rom or kernel since they provided optimizations to batt life.
Click to expand...
Click to collapse
That is wrong. I used to have a UGKG2 ROM and since I upgraded to XXKH3, the battery is MUCH better while the GPS pinpoints in less than 3 seconds with a 5meters accuracy.
Hi there,
probably that request would make more sense in the developer forum but i didnt post enough yet
Actually i get insane battery batterylife with the bali 1.8.8 UV version, therefore i tried the non UV version with even more lowerd voltages via set cpu. it was stable but drained a lot faster. don´t know why.
so my request would be "pre-undervolted" bali kernels that might have even longer batteryliftime. Any hints on that? Someone who is able to compile something like this?
Best regards,
vibrantoparanto (from germany)
Hint' Bali X+Voltage control app= win !!!
Sent from my SGH-T959 using xda premium
^^ that is your answer....currently what im using
bali-x is what i used before - i lowered the voltages up to -150mv with some frequencies but it still gave me only about half the battery lifetime (less than 24 hours with moderate use) then i get with bali uv. What did you use to manually undervolt and how is your battery lifetime?
vibrantoparanto said:
bali-x is what i used before - i lowered the voltages up to -150mv with some frequencies but it still gave me only about half the battery lifetime (less than 24 hours with moderate use) then i get with bali uv. What did you use to manually undervolt and how is your battery lifetime?
Click to expand...
Click to collapse
i hate to burst your bubble, but youre chasing a ghost. uv'ing will not produce very noticeable changes to your battery life, especially if were are talking baout different versions of the same kernel.
take a look at this: http://forum.xda-developers.com/showpost.php?p=21024393&postcount=8
Cannot agree with that. I tried *a lot* and flashed different roms and kernels for years now. With stock kernels i get up to two days standby with low/moderate use, with bali UV i get almost three days. I have no idead why, but at least the standby time differs dramatically between kernels. At least thats for sure - under load that might be another thing. But probably you´re right and its just a "good standby behaviour" which would hardly benefit from lowered voltages. Would be still interesting to try a hardcore UV kernel
TopShelf, it is funny that you posted that note/post b/c I was just getting ready to PM you that I put part of it in my guide like I mentioned a week or so ago and the apps too.
Take a look at the Guide and maybe you will find some answers to your questions.
If you want to UV to the max, then you will have to test that yourself b/c every Vibrant reacts differently to OC/UV. Step it down -25v each day (don't set on boot until you know they work) and see where it freezes. There are OC/UV examples in the guide but beware, they are both for MIUI kernels.
Is there probably any admin out there who understands what i talk about and can move that thread to the developer forum?
this thread belongs here, you posted in the right section. posting in development will not get you answers from developers, it will only get you yelled at by hall monitors.
it is a common misconception that "developers" ONLY visit the "development" section. this is far from the truth.
sorry to say, the reason you have not gotten answers isnt because you posted in the wrong section, but because requests like these are pretty much never honored. the reason is because if a developer decides to make a slight alteration to a ROM/kernel for a member, he will then get BOMBARDED by dozens of other members who have tiny little tweaks that they would like in their ROM/kernel
Still trying to bring back some life to my request with this argument: I just checked my girlfriends device (using zendroid 2.1.2 with bali 1.8.8uv) and couldnt believe it: 3 days and 14 hours since unplugged with 8% left. The battery is a stock 1500mHa. And as its my girlfriends phone its definity not "overtweaked and calibrated". Personally i care much more about standby time than super heavy usage (guess that should be fine then too).
vibrantoparanto said:
Still trying to bring back some life to my request with this argument: I just checked my girlfriends device (using zendroid 2.1.2 with bali 1.8.8uv) and couldnt believe it: 3 days and 14 hours since unplugged with 8% left. The battery is a stock 1500mHa. And as its my girlfriends phone its definity not "overtweaked and calibrated". Personally i care much more about standby time than super heavy usage (guess that should be fine then too).
Click to expand...
Click to collapse
Since you didn't like the answer you got, for clarification purposes you are basically asking for a dev to use their time for FREE an modified/debug/test a kernel with your requirements just for your own sake ?
i wanted to point out that this is a very interesting kernel with great battery lifetime. if you have a look at all the other threads of people desperatly trying to get 24h of battery then you probably wouldnt consider this request as "wasting free time of others for my own sake".
vibrantoparanto said:
i wanted to point out that this is a very interesting kernel with great battery lifetime. if you have a look at all the other threads of people desperatly trying to get 24h of battery then you probably wouldnt consider this request as "wasting free time of others for my own sake".
Click to expand...
Click to collapse
i can prove to you that UVing does not make that much of a difference. if youre willing to learn, try this little experiment:
-UV your phone using your current settings
-put your phone in airplane mode
-turn it off
-charge it to 100% while its off
-after it boots up, leave it in airplane mode and immediately lock the screen
-let your phone sit idle in airplane mode from full charge to death (record the time)
--------------
Once youve done this, repeat all of the above steps but with STOCK VOLTAGE. record the time.
now compare the two times. i would be willing to bet a large sum of money that it is not a notable difference, if any.
my point is instead of trying to convince yourself that your theory of UVing is correct, why not do a TRUE battery life test, and simply find out for yourself. you cannot run true battery tests while you are actually using your phone becuase phone usage is massively different on a day to day basis, even if you dont think it is, it is. there is background data, text messages/calls, notifications, etc. (which is why i said to put it in airplane mode, that way its just sitting there, with little to no variables)
i guarantee you that you are putting way too much thought into voltage settings. they do not help as much as people want them to. dont say im wrong until you actually try what i said above. although youre probably nto going to.
vibrantoparanto said:
Still trying to bring back some life to my request with this argument: I just checked my girlfriends device (using zendroid 2.1.2 with bali 1.8.8uv) and couldnt believe it: 3 days and 14 hours since unplugged with 8% left. The battery is a stock 1500mHa. And as its my girlfriends phone its definity not "overtweaked and calibrated". Personally i care much more about standby time than super heavy usage (guess that should be fine then too).
Click to expand...
Click to collapse
sorry, but this does not prove anything. what are you comparing it to? your phone? you cant compare her battery life to your own unless you guys have the same exact setup, same exact apps, and same exact usage habits, etc.
you are not going about this battery things the right way. you NEED to be willing to learn more instead of trying to come up with your own reasons in your own head as to why your battery gets a specific lifespan. If getting THAT MUCH more battery life was as easy as UVing your phone, dont you think the manufacturers would incorporate that and use that as a marketing strategy?? "New from Samsung, the Galaxy S III!!! This will revolutionize the mobile industry, curing the battery woes across that smartphone world...now with lower voltage for drastically improved battery life!! Pick yours up today!!"
It's not that easy, you need to read up on what affects battery life.
thank you for your thoughts topshelf, but as i posted earlier i am on that topic for years now and i really tested a lot. not as scientific as running phone on idle with different frequenzies but trust me: I know a whole lot about this topic. Also i share your thought that the voltage is not that important in the end. On the other hand i have to say you guys are quite ignorant about my observations i did earlier:
1. The bali-x kernel with manual undervolting provides (provable) worse battery lifetime than
2. the 1.8.8uv kernel.
Conclusion: As you say it is not that much about the voltage but about the way the kernels work as a whole. On the other hand it would be *very* interesting if the insane battery lifetime of bali uv could be even further improved. And no i wont put my phone to sleep for days in order to do scientific test (whoever is willing to i will donate - battery lifetime almost like astrology)
Last but not least: It is true that different roms provide significantly different battery lifetimes - for whatever reason. Some roms turn your phone into a handwarmer, others give you almost the standby times you were used from the non-smarthpones. And i think even the big companies have a hard time to write device specific code that is highly optimized - i mean you still get new devices with gingerbread instead of ics and so on. conclusion: on the software side *is* much room for improvement if it comes to battery lifetime on most devices.
just my 2 cents
vibrantoparanto said:
i wanted to point out that this is a very interesting kernel with great battery lifetime. if you have a look at all the other threads of people desperatly trying to get 24h of battery then you probably wouldnt consider this request as "wasting free time of others for my own sake".
Click to expand...
Click to collapse
Look at your post, you and "others" are asking for some one to do research and development on their free time and for free ? little selfish on you.
Look at all the kernels thread in the development section and read thru all the comments, I bet there is far more people whining and complaining about this and that, than providing actually constructive and monetary feedback to the developers.
Its not as easy as it seams, ecotox already tried this before with his ultra low power kernels and some reported great succes while others couldnt even boot, it goes down to the quality of the silicon on each particular phone. no dev has the time/money to develop such request considering all the different variables involved.
lastly if you are so fond on this idea, why dont you take the initiative and learn to compile and patch and make your own kernel ?
Diff phone but a good simple guide to read:
http://arighi.blogspot.com/2011/08/howto-custom-kernel-on-samsung-galaxy-s.html
basic read:
http://stackoverflow.com/questions/5529470/how-to-compile-linux-kernel-for-real-android-phone
basic read:
http://igottadroid.com/wordpress/?p=61
For latest source:
http://opensource.samsung.com
"Be the change you want to see in the world." Mohandas Gandhi
Simple: If you want to change the world, start with yourself.
I'll read those links. Thanks for the info.
vibrantoparanto said:
And no i wont put my phone to sleep for days in order to do scientific test (whoever is willing to i will donate - battery lifetime almost like astrology)
Click to expand...
Click to collapse
im not trying to pick on you, but this sarcastic response shows your overall attitude that jrafael is trying to make you realize. you want somebody to take time out of their day/night to do something for you...yet you arent even willing to let for phone sit for a day in order to learn a thing or two...letting your phone sit doesnt even take any effort, compiling a kernel takes a lot more effort than that
i hate to say it, but why should someone help you, if you dont want to help yourself.
thank you jrafael for the links - thats a great read.
@topshelf: still think you overreact here. For one who has developed it and has the workflow it is a matter of a few minutes - and no one is forced to do anything unless he thinks its might be worth it - maybe its inspiring? i am just asking. not everything idea must be done by the one who thinks about it. and the quote about battery life is true i would say - we are really lacking valueable info on battery drain with different setups.
I have been struggling with trying to figure out if the battery life I am seeing is what my Atrix is really capable of. I am occasionally a heavy user, but on weekends I am a very light user. I'll start at 8am with 100% and be almost dead at 6-8pm. I have searched around and seen other Atrix users with 24 hours of battery life and even if I tried my hardest to not use my phone I wouldn't get those kind of numbers. I feel fairly confident in saying i scoured search results and tried everything i could find to extend battery life.
Am I doing something wrong?
Is there something I can do to help?
I know it's been asked before, but I am hoping to get some current answers for this question: what kind of battery life numbers are you getting on your Atrix? Which rom are you using?
Atrix 4G running CM7 RC3. If the answer is "keep it charged as often as possible", it is what it is. It would be great to find an answer to why battery life is so much shorter than others though! Many thanks in advance.
Just noticed CM7.2 stable was released, upgrading to that now to see if battery life improves. Might try a full wipe to see if battery life is better without email, syncs, etc. etc. if the upgrade doesn't help.
i would recommend getting cpu spy and also download and install as a zip 'blue sleep fix' (blue sleep zip can be found in the CM7 thread). This has greatly improved my battery life.
rjbanker said:
Just noticed CM7.2 stable was released, upgrading to that now to see if battery life improves. Might try a full wipe to see if battery life is better without email, syncs, etc. etc. if the upgrade doesn't help.
Click to expand...
Click to collapse
Which kernel? Flash Faux 1.0GHz and undervolt across the board by -50mv. Instant battery life!
Also, use ROM Manager or equivalent to stop all non essential apps from starting on boot.
Sent from my MB860 using xda premium
barry_ said:
i would recommend getting cpu spy and also download and install as a zip 'blue sleep fix' (blue sleep zip can be found in the CM7 thread). This has greatly improved my battery life.
Click to expand...
Click to collapse
There are 2 cpu spy apps on the market, can you let me know which one to use? Bluesleep fix found and downloading now.
CaelanT said:
Which kernel? Flash Faux 1.0GHz and undervolt across the board by -50mv. Instant battery life!
Also, use ROM Manager or equivalent to stop all non essential apps from starting on boot.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Flashed Faux 1.0 no problem. I do not know how to undervolt so I will search around and see if i can find something on it. Ill try stopping some startup apps too. Thanks for the suggestions all! Keep them coming!
rjbanker said:
There are 2 cpu spy apps on the market, can you let me know which one to use? Bluesleep fix found and downloading now.
Click to expand...
Click to collapse
the one by 'STORM717' :good:
Hopefully did the under volt right! Should I set it to take effect at boot?
Sent from my MB860 using XDA
rjbanker said:
Hopefully did the under volt right! Should I set it to take effect at boot?
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Test your settings for a few days. If the phone stays stable THEN you set at boot.
Big thanks to everyone! Battery life has improved a ton (see picts)! It was hard finding the blue sleep fix, here it is for others to easily find: http://forum.xda-developers.com/showpost.php?p=25437046&postcount=436
rjbanker said:
Big thanks to everyone! Battery life has improved a ton (see picts)! It was hard finding the blue sleep fix, here it is for others to easily find: http://forum.xda-developers.com/showpost.php?p=25437046&postcount=436
Click to expand...
Click to collapse
Err, that is not good battery life at all bro. I can tell you barely used the phone. Atrix should be able to provide up to 2 days standby time...
I wouldn't undervolt either, I read on these forums that the battery gained from undervolting barely makes a difference
MB860, CM7.2.0, Faux 026b1 1Ghz
rjbanker said:
Big thanks to everyone! Battery life has improved a ton (see picts)! It was hard finding the blue sleep fix, here it is for others to easily find: http://forum.xda-developers.com/showpost.php?p=25437046&postcount=436
Click to expand...
Click to collapse
You should turn wifi off when not in use, that will save battery life.
Badass battery will let you know how you spend your battery by % and let you know which app takes the most battery. (Lets you get a really readable easily understandable battery read out.)
I can help you get even better battery if you use this app and give me some numbers (it has a share via gmail/etc)
mayhemrules said:
You should turn wifi off when not in use, that will save battery life.
Click to expand...
Click to collapse
Or simply set wifi sleep to screen off
MB860, CM7.2.0, Faux 026b1 1Ghz
Ciloteille said:
Badass battery will let you know how you spend your battery by % and let you know which app takes the most battery. (Lets you get a really readable easily understandable battery read out.)
I can help you get even better battery if you use this app and give me some numbers (it has a share via gmail/etc)
Click to expand...
Click to collapse
turning off wifi is not going to help him that much. I leave my wifi on all the time no problems, make 2 days light usage no problem.
More likely he's got some apps running around in the background. I suggest he pick through what he's got installed and start turning off the things that like to sync all the time in the background.
I think step number 1 would be to install a non-stock ROM and startover fresh.
Blur-based ROMs (Nottachtrix was really good) then the faux123 kernel then slowly start installing the apps he likes to use and monitor battery life. It might take a month but he's definitely got an offender here or there causing these problems.
also install Juice Defender. My mom's Galaxy S2 was having tons of problems with battery life even though she wasn't using it at all, 60% battery life at 3pm without using it at all, installed that and immediately helped her a lot, like 80% by 3pm WITH use.
Also, clear your dalvik cache. After installing lots of stuff and not using it, it just fills up with sometimes poorly written code. Clearing it always makes phone faster in my experience.
Ciloteille said:
Badass battery will let you know how you spend your battery by % and let you know which app takes the most battery. (Lets you get a really readable easily understandable battery read out.)
I can help you get even better battery if you use this app and give me some numbers (it has a share via gmail/etc)
Click to expand...
Click to collapse
I will give that a shot, thanks!
Soldier-2Point0 said:
Or simply set wifi sleep to screen off
MB860, CM7.2.0, Faux 026b1 1Ghz
Click to expand...
Click to collapse
Strangely, I keep setting wifi to turn off when the screen is off...but it keeps resetting itself. I wonder if I found a bug?
rancur3p1c said:
turning off wifi is not going to help him that much. I leave my wifi on all the time no problems, make 2 days light usage no problem.
More likely he's got some apps running around in the background. I suggest he pick through what he's got installed and start turning off the things that like to sync all the time in the background.
I think step number 1 would be to install a non-stock ROM and startover fresh.
Blur-based ROMs (Nottachtrix was really good) then the faux123 kernel then slowly start installing the apps he likes to use and monitor battery life. It might take a month but he's definitely got an offender here or there causing these problems.
also install Juice Defender. My mom's Galaxy S2 was having tons of problems with battery life even though she wasn't using it at all, 60% battery life at 3pm without using it at all, installed that and immediately helped her a lot, like 80% by 3pm WITH use.
Also, clear your dalvik cache. After installing lots of stuff and not using it, it just fills up with sometimes poorly written code. Clearing it always makes phone faster in my experience.
Click to expand...
Click to collapse
I think this is what I will do today! I'll do a nandroid backup, and try Nottachtrix with no extra stuff installed or setup. I will report back! I appreciate all the help to get my phone performing where it should be.
Just wanted to report in. I tried a clean ROM as stated in my previous post with no luck. I just couldn't get past the battery life I was getting with cyanogenmod WITH all of the apps and syncs enabled. Should I try another ROM maybe?
Maybe your battery is just a bit old? After ~2 years, you can expect that battery life drops dramatically. if you are a heavy user this might happen earlier. Maybe check with the battery of a friend of yours whether it's a software or a hardware issue
Nvmd
You could be right, the battery might be dying.
I was on vacation the past few days so I got the opportunity to not use my phone most of the day (job requires me to use the phone a lot). The battery lasted about 12 hours and looked like it had about 4 hours left. So maybe I am expecting too much, but I'm not trolling...no.
If you aren't going to be helpful, go somewhere else. You could have said "Your phone screen was on for probably longer periods than the average user and that's why you can't hit longer hours". Based on your previous comments, I shouldn't expect much from you though.
Many thanks to all who are helping me. You're all awesome.
:thumbup:
Sent from my MB860 using xda app-developers app
11-12 hours.
I also have 11-12 hours with 1 charge. And it is not enough for me. I use only Whatsapp ( a lot usage ), a little bit browsing, 20-30 minutes phone calls. These are all. And 11-12 hours is sooo bad for them i guess.
I have an "suspend linux process" drainage issue. Maybe because of it, I'm getting this result.
How can I extend my battery life. PLEASE Help!