Related
Did a search, and didn't find anything regarding this, so I'll point this out. I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Is my KAIS really sleeping, or is there a bug somewhere?
I'm running l1q1d's latest .32 kernel, with Fat Free Froyo build with system/data on NAND.
Battery also only lasts about 8hrs in "standby", and not even 2hrs with full use. With WinMo, I get about 36hrs standby, and about 5hrs full use.
Krazy-Killa said:
I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
Click to expand...
Click to collapse
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
Krazy-Killa said:
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Click to expand...
Click to collapse
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....
albertorodast2007 said:
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....
Click to expand...
Click to collapse
The phone locks like it's suppose too, but the problem I'm having is the CPU of the Kaiser isn't actually falling asleep. I'm getting the same battery consumption as when the screen is off compared to on, and sitting there (no activity on my part, just leaving the screen on for no reason )
Every so often the phone will be asleep, and the only way to bring it back on is by hitting the power button, but about 95% of the time I can press the call button, end button, OK button, IE button, hell even push down on the wheel on the other side of the Kaiser and the screen will come on showing the lock screen.
As far as the battery capacity, I have not done that, but the phone's been auto-learning my capacity, and it will get to the 2160 units, compared to the 2000 it's always set too, and sometimes reach 2377 units.
I have tried several Radio versions, down to 1.65.xx.xx version (which was the original version on my phone), and no changes, and tried different builds and no change either. DZOs kernel doesn't make a difference either, except screw up my battery meter completely. lol
uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...
albertorodast2007 said:
uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...
Click to expand...
Click to collapse
Did some more testing, and found that without it plugged into power it does only respond to the power button, but again it's only about 15-20% of the time, and even those times seem iffy as it just seems like the phone's just slow to respond.
Phone is also somewhat warm as well even when "off", and I do have the phone overclocked to 450MHz, kernel is set to 425 (running a test on speed/stability atm)
At 425MHz it's still reasonably warm, and at 450 the temperature jumps alot.
Anyone else have an issue of the tap sounds when tapping on the screen sometimes not playing? Granted phone quality is great, and GPS is working well, though Camera is broken on my end, even though it was working before.
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....
albertorodast2007 said:
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....
Click to expand...
Click to collapse
Yes that's the one. it needs to be removed, and can be replaced by Fancy Widget.
Sent from my Android on HTC Kaiser/Kaiser/Polaris using XDA App
n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
Ok, I'll give it a whirl, and remove some of the widgets I have running, and see if it does help out. Right now though I'm re-installing /system as I tried messing around with the density as 110 seems to work real well with where things are placed on the home screen (no widgets are overlapping each other), but Market won't work, and the Android Keyboard keeps crashing (on-screen).
But anyways, phone's booting back up, so I'll test out the battery life here again, as I got about 95% charge right now, so should serve as a good test for battery life, and CPU Sleepage.
Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Edit 2 : Figured it out, turns out the ebay app has a service and a process running - even with notifications turned off! Have killed these and see if anything improves
That could very well be part of the problem, although it shouldn't kill it from 66% with just the radio. How much capacity does it calibrate itself to?
cycloid said:
Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Click to expand...
Click to collapse
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.
Krazy-Killa said:
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.
Click to expand...
Click to collapse
yes, i boutght seidio 1600 mAh, and the kernel ended up adjusting it to 3260 units... (about 2000 mAh) maybe the 1.6 factor isnt right just as n2rjt said, maybe its closer to the 2.0
Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next
cycloid said:
Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next
Click to expand...
Click to collapse
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.
Krazy-Killa said:
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.
Click to expand...
Click to collapse
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..
daedric said:
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..
Click to expand...
Click to collapse
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.
Krazy-Killa said:
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.
Click to expand...
Click to collapse
Umh... sad...
We'll wait for you! Bye bye
daedric said:
Umh... sad...
We'll wait for you! Bye bye
Click to expand...
Click to collapse
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.
Krazy-Killa said:
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.
Click to expand...
Click to collapse
Man... that's a sin! You can't do that! You'll be off from the Brotherhood!
Kiddin' ;D
I am opening this thread to talk about kernel Wakelocks. It's a branch of this discussion in the Franco's Kernel thread.
Hopefully we can research what a lot of these wakelocks are and find ways of minimizing them in order to increase the efficiency (and reduce power consumption) on our devices.
What is a Wakelock?
A wakelock is a software method for applications to control the power state of your device. The purpose of a wakelock is in its name, to lock your device in an awake state keeping the CPU running and preventing it from entering Deep Sleep (Think of a music app or video player). A wakelock can also cause your device to turn on (think syncs or notifications).
A poorly coded application can acquire a wakelock and not release it, causing your device to remain on.
A partial wakelock means the CPU is ON, but the screen is OFF.
A full wakelock means the CPU and Screen are ON. (we don't really need to worry about this)
Sources:
http://developer.android.com/reference/android/os/PowerManager.html
http://developer.android.com/reference/android/os/PowerManager.WakeLock.html
How to help:
Install BetterBatteryStats which will show you what the wakelocks are on your device.
If you don't know what a specific wakelock is doing. Google it. Don't just google the wakelock name verbatim. Use part of it. They are usually logically named. But most often they are shortened or turned into acronyms (there are so many in IT) which makes them cyptic.
Kernel wakelocks are low level/hardware wakelocks from the kernel. We can only reduce these by modifying the kernel or reducing the usage of a certain feature of the kernel. By researching these we can improve the battery consumption and performance of the Kernel.
Partial wakelocks are wakelocks from apps. These can be reduced by uninstalling or disabling features in software. We can talk about those here too though it shouldn't be the focus as the answer will be "Uninstall/Disable feature X and talk to the app author". Preferably we should talk about partial wakelocks from Google services like maps and latitude.
psycho2097 said:
I think it would benefit a lot of noobs here,me included if someone started a thread compiling a list of the known wakelocks and how to avoid or get rid of them. For the life of me I can't figure out mipi_link, alarm_rtc,musb_autosuspend and I have no idea how to remove wlan_rx and vbus_tuna_otg. I would highly appreciate some help on these.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
wlan_rx is wireless LAN receive. Turn off wifi.
musb_autosuspend_wake_lock im pretty sure is a kernel powermanagement method to turn off power to the micro usb port and have any attached devices be placed in a power suspend mode. Probably most useful for the USB OTG support on this port.
alarm_rtc is Real-time clock alarm. It isn't the alarm to wake you up, tho it could be used by that. It's more like a scheduler on your phone, to make sure it is not sleeping when an application needs it. "AlarmManager is a universal process that MANY apps use to update time, push you notifications, etc. In most cases, it is a necessity; in other cases, you should really check it out and disable/uninstall things that have invoked it too much."
Sources:
http://developer.android.com/reference/android/app/AlarmManager.html
https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/AlarmManager
vbus_tuna_otg sounds like virtual bus for USB OTG devices. According to Franco this wakelock occurs when your "device [is] attached to the USB." From this I would take it to mean that if your GNex is attached to a computer via USB you will see this wakelock.
mipi_link stands for Mobile Industry Processor Interface but I am unsure of what this does specifically. From googling it it seems highly related to the cameras. Maybe its how we can see a live feed of the camera from the device.
Sources:
http://en.wikipedia.org/wiki/Mobile_Industry_Processor_Interface
PowerManagerService is the kernel wakelock that is a container for all of the partial wakelocks on the device.
Sources:
https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/PowerManagerService
AudioOut_1 AudioOut is used to play notification and system sounds. Putting your device on silent will make this go away.
Sources:
https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/AudioOut_1
Revisions:
2012.01.24 - Added "what is a wakelock" section
2012.01.24 - Initial Post
Awesome. theres also a wiki in the betterbatterystats website that explains some of the more known wakelocks, nonetheless, these will be very helpful to a new user.
https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/_pages
Also, the betterbatterystats thread at XDA has some intro level info.
edit: I just realised you already posted individual links.
These wake locks are beginning to piss me off really. Pardon my frustration. Check the screen shots of better battery stats. I don't have touch sounds checked or nfc enabled. I did use media player to play music in the train. I have these wake locks all over the place and haven't found any solution yet. Anyone any help much appreciated.this is all with stock rooted running Jame bond kernel. Stock kernel was better. Using default UV settings and some profiles.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus using XDA App
vick1377 said:
These wake locks are beginning to piss me off really. Pardon my frustration. Check the screen shots of better battery stats. I don't have touch sounds checked or nfc enabled. I did use media player to play music in the train. I have these wake locks all over the place and haven't found any solution yet. Anyone any help much appreciated.this is all with stock rooted running Jame bond kernel. Stock kernel was better. Using default UV settings and some profiles.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Wakelocks are a normal part of the system. You can't get rid of them, but you can minimize the unnecessary ones for sure.
Yeah its unfortunate that the NFC wakelock occurs even with it disabled. Thankfully its very minimal.
The Audioout_1 wakelock im sure is all audio events. Like notifications and perhaps even music playing. Nothing you can do here.
Modem_USB im guessing is your USB Tethering for data? If you turned that off you might get rid of them as they don't even show up on mine.
Basically I would just be focusing on wakelocks that are proportionately higher than the others. If most wakelocks are 2-3 minutes after a full days use but you see a one or more holding wakelocks that are in the double digits, check those out.
Thank you for a quick response. Where do I turn off USB tethering which I don't have? As you see some of partial locks are very high. Also once you stop using per say audio player or mp3 player shouldn't that audio out wake lock go down or disappear. Off topic question when I flashed Jame bond kernel did I have to wipe cache and dalvik cache?
Are there some apps which can tell which apps are bringing these locks? I can post alogcat logs later from PC as I can't attach from phone as it only allows screenshots from gallery
Sent from my Galaxy Nexus using XDA App
vick1377 said:
Thank you for a quick response. Where do I turn off USB tethering which I don't have? As you see some of partial locks are very high. Also once you stop using per say audio player or mp3 player shouldn't that audio out wake lock go down or disappear. Off topic question when I flashed Jame bond kernel did I have to wipe cache and dalvik cache?
Are there some apps which can tell which apps are bringing these locks? I can post alogcat logs later from PC as I can't attach from phone as it only allows screenshots from gallery
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Settings > More... > Tethering & Portable Hotspot > Make sure everything here is unchecked. You can only check/uncheck USB Tethering if the device is plugged in.
If you stop playing audio I would assume the audioout_1 wakelock to reduce significantly. If you look at your screenshot you see Android Media Player holding a wakelock for 23 minutes, and Audioout_1 for 24 minutes.
So I am assuming that if you didnt listen to any audio, audioout_1 would just say about 1 minute. You may never get it to dissappear fully even if the device is muted. This is something you'd want to try on your own and report back. Remember we're doing research together I'm not doing it for you
As for wiping cache and dalvik after flashing a kernel. Franco says you do not have to. So personally I don't. It definitely doesn't hurt other than wasting time. If you do flash a ROM though you must wipe both caches.
Finally you need to decide how much you want to reduce wakelocks. Like if you are listening to music there is nothing wrong with having your device awake. It shouldn't kill THAT much battery. Esp if you clock down to 350mhz.
You can dramatically reduce the AudioOut wakelock by disabling the following in SETTINGS > SOUNDS:
Touch sounds, dial pad touch tones and screen lock sound.
Disabling these three options eliminated my problem completely.
As for myself:
MIPI_LINK continues to be the #1 destroyer of my battery life, regardless of what ROM or kernel I flash. Even just flashing the ROM, wiping the battery stats and then leaving the phone on my desk untouched for 12+ hours can cut 10-20% off my battery life.
It's ridiculous. There is absolutely something wrong with the battery drain on the Galaxy Nexus, but some people have it, and others don't.
Wake locks
sishgupta said:
Settings > More... > Tethering & Portable Hotspot > Make sure everything here is unchecked. You can only check/uncheck USB Tethering if the device is plugged in.
If you stop playing audio I would assume the audioout_1 wakelock to reduce significantly. If you look at your screenshot you see Android Media Player holding a wakelock for 23 minutes, and Audioout_1 for 24 minutes.
So I am assuming that if you didnt listen to any audio, audioout_1 would just say about 1 minute. You may never get it to dissappear fully even if the device is muted. This is something you'd want to try on your own and report back. Remember we're doing research together I'm not doing it for you
As for wiping cache and dalvik after flashing a kernel. Franco says you do not have to. So personally I don't. It definitely doesn't hurt other than wasting time. If you do flash a ROM though you must wipe both caches.
Finally you need to device how much you want to reduce wakelocks. Like if you are listening to music there is nothing wrong with having your device awake. It shouldn't kill THAT much battery. Esp if you clock down to 350mhz.
Click to expand...
Click to collapse
Opening this thread is the best thing. Can't appreciate enough. So, I always have the phone in vibrate mode but turned to silent mode and checked the better battery stats, the audioout_1 still there but I think it's showing still the same as 25 minutes or so and but % has gone down to 6-7% from 10% and above. Regardless the time is not increasing even though it the wake lock is still there. I'm wondering if it doesn't refresh until after fully charge/unplugged. I checked both kernel and partial wake locks with option since unplugged and since charged. What I will do next is drain the battery fully few times too since it's an extended battery I got last week?
One thing for sure I was getting better battery life with stock rooted rom and stock kernel with some setcpu profiles. I made all the nandroid, titanium backups, what I will do next is flash the stock kernel and monitor the results and report back here for comparison. After then I will be super tempted to flash 4.0.3 franco's ROM and nightly kernel . I'm debating to wait for OTA 4.0.3 or custom ROM. I'm honestly not at all happy with jame bond kernel in terms of battery life. Can you also suggest some good radios to flash? Part of the problem could be the phone toggling between 3g and 4g connection. Most places I do get consistently but sometimes it switches back to 3g. Flashing new radio might improve the signal strength to keep it consistent on 4g so that no toggling required.
Absolutely we are doing this research together no doubt and you are helping a tons
---------- Post added at 01:48 PM ---------- Previous post was at 01:24 PM ----------
Regarding USB tethering, did you mean plugged via outlet or via data cable connecting to computer? When connected via charger cable (not data/charger cable that came with it) to AC outlet, I see usb tethering disable and grayed out. I think you probably meant via data cable connecting to USB port of computer. I will do that tonight once I get home and check to see if these usb related wake locks go away or reduce.
sishgupta said:
Wakelocks are a normal part of the system. You can't get rid of them, but you can minimize the unnecessary ones for sure.
Yeah its unfortunate that the NFC wakelock occurs even with it disabled. Thankfully its very minimal.
The Audioout_1 wakelock im sure is all audio events. Like notifications and perhaps even music playing. Nothing you can do here.
Modem_USB im guessing is your USB Tethering for data? If you turned that off you might get rid of them as they don't even show up on mine.
Basically I would just be focusing on wakelocks that are proportionately higher than the others. If most wakelocks are 2-3 minutes after a full days use but you see a one or more holding wakelocks that are in the double digits, check those out.
Click to expand...
Click to collapse
You are right in the audio wakelock, it happens only when you play something. Its not bad, its not something you should be trying to reduce.
Its not faulty, it happens only when anything is playd, screen lock sounds will significantly increase this, because that does cause a faulty wakelock.
sishgupta said:
Settings > More... > Tethering & Portable Hotspot > Make sure everything here is unchecked. You can only check/uncheck USB Tethering if the device is plugged in.
If you stop playing audio I would assume the audioout_1 wakelock to reduce significantly. If you look at your screenshot you see Android Media Player holding a wakelock for 23 minutes, and Audioout_1 for 24 minutes.
So I am assuming that if you didnt listen to any audio, audioout_1 would just say about 1 minute. You may never get it to dissappear fully even if the device is muted. This is something you'd want to try on your own and report back. Remember we're doing research together I'm not doing it for you
As for wiping cache and dalvik after flashing a kernel. Franco says you do not have to. So personally I don't. It definitely doesn't hurt other than wasting time. If you do flash a ROM though you must wipe both caches.
Finally you need to device how much you want to reduce wakelocks. Like if you are listening to music there is nothing wrong with having your device awake. It shouldn't kill THAT much battery. Esp if you clock down to 350mhz.
Click to expand...
Click to collapse
again, hes right here, if you listen to music continuously for a hour or so, and use only the volume key long-press to skip tracks, the gnex uses an extremely low power DAC to play music, takes only around 60-70 ma. You could play for ages without losing significant battery.
I disagree on the cache clean process tho. I have flashed a lot of roms/kernels, and not observing the correct procedure can cause significant problems.Most kernels use different tweaks, mods and scripts to make your system perform better, and its highly possible for one of the tweaks to just stay over and conflict with your new kernel, causing heavy wakelocks. When that happens, your best bet is wiping anyways. So better safe than sorry.
Thracks said:
You can dramatically reduce the AudioOut wakelock by disabling the following in SETTINGS > SOUNDS:
Touch sounds, dial pad touch tones and screen lock sound.
Disabling these three options eliminated my problem completely.
As for myself:
MIPI_LINK continues to be the #1 destroyer of my battery life, regardless of what ROM or kernel I flash. Even just flashing the ROM, wiping the battery stats and then leaving the phone on my desk untouched for 12+ hours can cut 10-20% off my battery life.
It's ridiculous. There is absolutely something wrong with the battery drain on the Galaxy Nexus, but some people have it, and others don't.
Click to expand...
Click to collapse
There is nothing wrong. The thing wrong here is that people have misconceptions. DONT CLEAR BATT STATS. It has been confirmed to not change anything. That was old battery tech. After flashing a new rom, i always do 2-3 charge cycles. after a new kernel, drain till empty then charge and use. I may be wrong, but I have never experienced any issues by this method. I regularly get 1% per 1-2 hrs depending on wifi/data on standby. Even 1% per 4hrs in wifi &data off.
vick1377 said:
Opening this thread is the best thing. Can't appreciate enough. So, I always have the phone in vibrate mode but turned to silent mode and checked the better battery stats, the audioout_1 still there but I think it's showing still the same as 25 minutes or so and but % has gone down to 6-7% from 10% and above. Regardless the time is not increasing even though it the wake lock is still there. I'm wondering if it doesn't refresh until after fully charge/unplugged. I checked both kernel and partial wake locks with option since unplugged and since charged. What I will do next is drain the battery fully few times too since it's an extended battery I got last week?
One thing for sure I was getting better battery life with stock rooted rom and stock kernel with some setcpu profiles. I made all the nandroid, titanium backups, what I will do next is flash the stock kernel and monitor the results and report back here for comparison. After then I will be super tempted to flash 4.0.3 franco's ROM and nightly kernel . I'm debating to wait for OTA 4.0.3 or custom ROM. I'm honestly not at all happy with jame bond kernel in terms of battery life. Can you also suggest some good radios to flash? Part of the problem could be the phone toggling between 3g and 4g connection. Most places I do get consistently but sometimes it switches back to 3g. Flashing new radio might improve the signal strength to keep it consistent on 4g so that no toggling required.
Absolutely we are doing this research together no doubt and you are helping a tons
Click to expand...
Click to collapse
You are correct in assuming it doesnt reset till fully cahrged. When fully charged, the <since charged> counter resets, however, any time you plug it in, the <since unplugged> counter resets.
I dont know whether u hav LTE/GSM, but kk6 does wonders for me in GSM. For example yest i was in a factory from 8am-3pm, with no signal time showing 70%. Absolutely no signal inside factory. I mean , like my whole battry bar is red, almost. My Captivate would be dead by 3pm. The nexus still had 72% juice left when i reached home at 3:30pm, that too with 40 mins screen on.
Also, 4.0.3 may have some issues, but thats y we r here, thats y we bought a nexus, to play with the latest and greatest.
THIS
IS
NEXUS.
psycho2097 said:
I disagree on the cache clean process tho. I have flashed a lot of roms/kernels, and not observing the correct procedure can cause significant problems.Most kernels use different tweaks, mods and scripts to make your system perform better, and its highly possible for one of the tweaks to just stay over and conflict with your new kernel, causing heavy wakelocks. When that happens, your best bet is wiping anyways. So better safe than sorry.
Click to expand...
Click to collapse
I'm just repeating what Franco said. He was very adamant about the kernel having nothing to do with the caches.
psycho2097 said:
DONT CLEAR BATT STATS. It has been confirmed to not change anything.
Click to expand...
Click to collapse
Correct. here is more information regarding this
http://www.xda-developers.com/andro...-battery-stats-does-not-improve-battery-life/
psycho2097 said:
After flashing a new rom, i always do 2-3 charge cycles. after a new kernel, drain till empty then charge and use.
Click to expand...
Click to collapse
IMHO there is no point to this. What would this achieve?
psycho2097 said:
kk6 does wonders for me in GSM.
Click to expand...
Click to collapse
XXKL1 is out. Check it out, its very good. Link in my sig.
psycho2097 said:
Also, 4.0.3 may have some issues, but thats y we r here, thats y we bought a nexus, to play with the latest and greatest.
THIS
IS
NEXUS.
Click to expand...
Click to collapse
Quoted for truth
psycho2097 said:
You are right in the audio wakelock, it happens only when you play something. Its not bad, its not something you should be trying to reduce.
Its not faulty, it happens only when anything is playd, screen lock sounds will significantly increase this, because that does cause a faulty wakelock.
again, hes right here, if you listen to music continuously for a hour or so, and use only the volume key long-press to skip tracks, the gnex uses an extremely low power DAC to play music, takes only around 60-70 ma. You could play for ages without losing significant battery.
I disagree on the cache clean process tho. I have flashed a lot of roms/kernels, and not observing the correct procedure can cause significant problems.Most kernels use different tweaks, mods and scripts to make your system perform better, and its highly possible for one of the tweaks to just stay over and conflict with your new kernel, causing heavy wakelocks. When that happens, your best bet is wiping anyways. So better safe than sorry.
There is nothing wrong. The thing wrong here is that people have misconceptions. DONT CLEAR BATT STATS. It has been confirmed to not change anything. That was old battery tech. After flashing a new rom, i always do 2-3 charge cycles. after a new kernel, drain till empty then charge and use. I may be wrong, but I have never experienced any issues by this method. I regularly get 1% per 1-2 hrs depending on wifi/data on standby. Even 1% per 4hrs in wifi &data off.
You are correct in assuming it doesnt reset till fully cahrged. When fully charged, the <since charged> counter resets, however, any time you plug it in, the <since unplugged> counter resets.
I dont know whether u hav LTE/GSM, but kk6 does wonders for me in GSM. For example yest i was in a factory from 8am-3pm, with no signal time showing 70%. Absolutely no signal inside factory. I mean , like my whole battry bar is red, almost. My Captivate would be dead by 3pm. The nexus still had 72% juice left when i reached home at 3:30pm, that too with 40 mins screen on.
Also, 4.0.3 may have some issues, but thats y we r here, thats y we bought a nexus, to play with the latest and greatest.
THIS
IS
NEXUS.
Click to expand...
Click to collapse
You guys are amazing. Now I'm seeing some life and some hope . One thing I have researched around which is an obvious thing lol that GSM users are getting much better battery life than LTE ones. Obviously I'm on Verizon LTE after I dumped AT&T's garbage 3g and their hspa (whatever they call it). Their LTE is only in limited right now and I'm in Tri-State area. Verizon blows every one away when it comes to speeds . And Nexus was coming to verizon and I was dying to move to Verizon after testing many of their 4g LTE phones at many different locations and stores which just simply blows my wifi speeds away at home .
By kk6 I'm assuming you mean the baseband radio version you flashed which boosted your signal strength. I haven't flashed roms yet on this, will probably for fun. Are all these radios compatible with stock rom or have to flash 4.0.3 first. OH definitely I love Android to death now. I have been using Apple the crap for few years and missing out the freedom to do anything and everything on the phones. I will never ever never ever go back to Apple and their outdated technology, they come with these new features, technology which has been there for years. What pissed me off the most was iphone 4s what a joke with no 4g and same screen when there are gorgeous looking android devices blow their Iphone 5, 6, 7 probably as they live in stone age . OK let me not divert attention to real issue
I want to correct a misconception. I am not suggesting anyone clear battery stats to improve battery life. I read Google+ like the rest of you. I clear the battery stats so I have a 100% clean battery log to start from before I do any testing.
I do the same just for testing purposes though.
Thracks said:
I want to correct a misconception. I am not suggesting anyone clear battery stats to improve battery life. I read Google+ like the rest of you. I clear the battery stats so I have a 100% clean battery log to start from before I do any testing.
Click to expand...
Click to collapse
Yes the thing which does get jacked up sometimes is the charging 'meter' If you so will.so the drop times for battery levels might not be uniform anymore.say it drops like crazy around 60 and very slowly around 10. As I mentioned in my comment earlier that is why I do one or two charge cycles,not to improve battery but to set the meter straight. In the Google+ post it was said that it doesn't improve battery, I agree completely,as I have never found evidence to the contrary. But setting the scale right? I think it does. Anyways without further proof its futile to discuss this point. Let's get back to the point of discussing wakelocks!
Sent from my Galaxy Nexus
vick1377 said:
You guys are amazing. Now I'm seeing some life and some hope . One thing I have researched around which is an obvious thing lol that GSM users are getting much better battery life than LTE ones. Obviously I'm on Verizon LTE after I dumped AT&T's garbage 3g and their hspa (whatever they call it). Their LTE is only in limited right now and I'm in Tri-State area. Verizon blows every one away when it comes to speeds . And Nexus was coming to verizon and I was dying to move to Verizon after testing many of their 4g LTE phones at many different locations and stores which just simply blows my wifi speeds away at home .
Click to expand...
Click to collapse
Yes I so understand the speeds,I have seen my colleagues bionic. However you must understand that the phone Is maintaining 2 connections at once,because lte is a whole different chip. Its bound to take more battery. Beyond minimizing your wakelocks,using an optimized kernel and staying in a lte area or actively managing lte, you can't do much.
By kk6 I'm assuming you mean the baseband radio version you flashed which boosted your signal strength. I haven't flashed roms yet on this, will probably for fun. Are all these radios compatible with stock rom or have to flash 4.0.3 first. OH definitely I love Android to death now. I have been using Apple the crap for few years and missing out the freedom to do anything and everything on the phones. I will never ever never ever go back to Apple and their outdated technology, they come with these new features, technology which has been there for years. What pissed me off the most was iphone 4s what a joke with no 4g and same screen when there are gorgeous looking android devices blow their Iphone 5, 6, 7 probably as they live in stone age . OK let me not divert attention to real issue
Click to expand...
Click to collapse
Yes its a radio. I do not think its Verizon compatible. Think its just for GSM,but I could be wrong. And you don't want to start a discussion about apple right now,trust me.as you can see from my sig, I am a fan boy. A PUREBRED ANDROID fanatic. I see anything small or bricklike, name starting with an 'i' ,I go "HULK SMASH!"
Sent from my Galaxy Nexus
psycho2097 said:
Yes its a radio. I do not think its Verizon compatible. Think its just for GSM,but I could be wrong.
Click to expand...
Click to collapse
You are correct. The basebands starting with XX or UG (or some other region code) are GSM only.
Verizon basebands for the GNex start with a I515 prefix, such as I515.EK04 or I515.EK06. Also IIRC there are two radios for Verizon phones, a CDMA one and an LTE one.
Still couldn't get rid of modem_usb locks and power management locks. I connected via usb data cable to my laptop and usb tethering got enabled (non grayed out) but it was never checked anyways in the first place so I left the way it is everything unchecked. The moment you take the phone of your charger, these locks go up and around 3-15 minutes consuming each about 2-8% or more of cpu. Yesterday it lost around 12-15% in less than an hour. I will test it out today fully and see what I get.
This is what I got in terms of battery consumption yesterday from a single charge and let it drain fully and automatically shut down the phone. And this is on Verizon LTE which obviously does consume more juice especially when used . I had a screen time of about few 2 minutes shy of 3 hours, battery lasted for 11 hours and some 40 minutes, Android OS - 16%, keep awake about 5 hours 15 minutes. I have had gone about 12-16 hours on stock Kernel but little less screen time of about 2 hours or so.
I will test it today before flashing the stock kernel and test that out completely again too.
@Thracks and @psycho2097
The battery stats are cleared every time you charge your phone and then unplug it as stated clearly in the google+ post. There's no need to manually clear it ever.
Well I managed to sort out my Wakelock issues with Autorun Manager. I went into the "Google Services Framework" and switched off my gtalk services. Also switched off a few others.
You can also turn off widgets that you don't use.
PS. Don't blame me if it crashes your phone.
I switched off a number of things and its running fine for me still. Now only have two major Wakelocks, "RILJ" and "MAIL_SERVICE".
jhericurls said:
Well I managed to sort out my Wakelock issues with Autorun Manager. I want into the "Google Services Framework" and switched off my gtalk services. Also switched off a few others.
You can also turn off widgets that you don't use.
PS. Don't blame me if it crashes your phone.
I switched off a number of things and its running fine for me still. Now only have two major Wakelocks, "RILJ" and "MAIL_SERVICE".
Click to expand...
Click to collapse
Were you able to get rid of modem_usb locks and power management locks? If so, how. Downloading autorun manager as I type this message
A bit dated of a post, but most if not all still relevant. We have a lot of non-TW ROMs for this phone which sacrifice battery life for improved functionality, not by choice, but mainly because Samsung's lack of GPL compliance with regards to sharing kernel sources. Our community devs have done an incredible amount of work with their kernel forks, but Samsung's paid development teams obviously have a lot more time and incentive to work on it, and as such our community devs' graciously find even more fixes once source drops, then merge them into the community kernels we're all using. So as we wait in limbo for them to share their JB kernel contributions to our community:
Anyone that wants to add anything to the list, post to the thread and I'll keep collecting.
Workarounds for D710 battery drainers:
battery saver scripts:rmikulus found this sweet piece of development gold: if you know how to run scripts,"Die Hard Battery Calibrator" will calibrate your battery in only about 20 minutes (must be plugged in that entire time)
Probably better to use the latest and greatest here instead, much easier to install, just a simple CWM zip AIO scripts:
Jelly Bean Tweak Pack for Epic 4G Touch Fixes Various Errors
--appears to help battery life and other various issues.
Voodoo LOUDER (paid) supercurio - Project Voodoo
--not battery-related, probably causing opposite effect actually, but many find an issue with headphone audio being maxed out at lower dB than desired. I'll confirm this works on CM10 nightlies.
WiFi : Turn it off when not in use, just like anything else. Tasker does a great job of automating this process.
raise the network scan interval to reduce background wifi radio usage (Rom Toolbox allows build.prop tweaks such as this,)
change the sleep policy for the wifi to Never While Charging to allow wifi connection to die when phone is off (toggle is in the touchkey menu while viewing wifi settings.)
NOTE: WiFi is a more desirable data connection than 4G as far as batt life is concerned. 4G is auto disabled when wifi is on for most ROMs. 4G (WiMax) is a new technology that still has yet to be perfected, not unlike these latest developments in ICS.
4G Radio: Also turn off when not in use. Use the latest modems available. Note that modems won'tt install from ODIN/mODIN flashes, gotta use CWM zip installs.
Haptic Feedback: Turn off haptic feedback, vibration kills. (Particular to CM9 ROM, haptic is set too strong right now, TouchWiz-based ROMs are fine, but if you can live w/o it...)
LED notifications: Another wakelock offender. Turn them off for now, it's one of the reasons the device stays awake when it should be sleeping. Sleep is good.
Get BetterBattery Stats by chamonix : Take a look at it after a long period of uptime without restarting (quick or full) to allow a greater set of data to parse into stats. Some apps you use may be eating away at your battery from the background. Spare Parts Plus and it's root-friendly brother BladeBuddy is also valuable.
Use the latest kernels available. If you're flashing CM nightlies, you're good to go, kernel modifications are updated in the same process.
Touch sounds and screen lock sound: These still cause partial wakelocks , leading to some amount of battery drain. System Settings>Sound menu to turn these off for now. (thx coiledwire)
The CM9 Team put together a similar list with a few things not listed here. Check the 'Power Saving Options' section on the CM9 Blog
----
Android-specific:
BatteryStats.Bin This little file keeps a record of your battery usage, power amperage, etc. and every time you flash a rom, it gets wiped. The system's ability to track the exact power level of your battery is DIRECTLY dependent on this file, so if you don't allow the newly flashed system a few days to calculate averages over time, it won't really have time to realize how charged it really is. NOTE: this file has NOTHING to do with improving battery life, only calculating what the battery % shows in the statusbar (and in the battery statistics charts in the system settings menus.) I've sat at 5% battery life for an entire hour with screen on surfing the 'net. No way it was really 5% that entire time.
While wiping battery stats won't increase battery life, it will improve the calculation of the charge, if done properly. Stats are saved in /data, when a ROM is installed, initially the stats will not have much data to extrapolate from, and the battery probably isn't entirely full to begin with, therefore making a mess of a new ROM's recognition of the cell's true charge. It's best to wipe stats when your charge is above 4180mV (E4GT stock battery size.) I've seen mine as high as 4202mV. Also, if you've got aftermarket cells that aren't the same mAH rating, the results will be slightly wonky. Battery Calibration app can set a reminder to flush the battery stat counter file when the phone is charged, if you need to charge with your device on.
I notice that flashing roms with a battery @100% and charging will help in this regard, then once the system is fully booted, unplug it and drain it to 15%, then charge to 100%, then do :
Bump Charging is suggested by HTC developers to potentially DOUBLE your battery life.
Battery Tuning: We're running Lithium Ion batteries. Don't kill it to 0%. Ever. Tip: Condition your new cell phone’s battery to make it last longer (but be sure to condition it properly)
Live Wallpapers and other background services: If you can live without them, turn off the services. Many common apps trigger network connections on a periodic schedule, further causing drain. increase sync periods, or just sync manually.
Sync: Yet another form of background services. If your sync is running all the time from frequent emails, gvoice msgs. etc... and the like, try turning off some of your heavier data tranx and refreshing manually when you need it.
Again, please tack on posts for this thread if you have good additions to make, I'm just trying to collect a one-stop shop of battery life savers, and a place to point newbs when they start trainwrecking dev threads with questions about it. This is my humble way of giving back cuz I was one at one point.
Thanks, some of these tips most users may know but the one that helpped me was the notification light when running cm9! I worked 10 hours a day and cant use my phone but my battery was draining like crazy! Much better!
Solid advice. I do everything mentioned here. I also throw in a bump charge to finish it off..old habits die hard
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
so is bump charging still a valid method? I've read that HTC developers suggest it, but you're saying old habits so I'm assuming you're aware of something about it.
[url="http://forum.xda-developers.com/showpost.php?p=25060053&postcount=1] Bump Charging [/url]
Dudebowski said:
so is bump charging still a valid method? I've read that HTC developers suggest it, but you're saying old habits so I'm assuming you're aware of something about it.
[url="http://forum.xda-developers.com/showpost.php?p=25060053&postcount=1] Bump Charging [/url]
Click to expand...
Click to collapse
Well, its just my routine. I charge to full, power down charge to full, unplug, power on, plug back in. When. I open Battery Calibration app, if battery shows 100% but only like 4110mV instead of 4180mV+ I will unplug and plug back in a minute later then wipe stats when it shows anything over 4175mV and 100% charge...confusing enough?! Lol
Sent from either ET4G or NS4G using Xparent Tapatalk 2
Thanks For the Guide.
I was really dissapointed with ICS.
I was still running EL29- Rooted and was running everyday on 14hrs with Wi-Fi always on. so after seeing that most bugs were fixed on FD24 i updated and yesterday i was running on 5hrs tops with Wi-Fi on.
So i did some suggested tweaks.
Wi-Fi off.( only ON when i need it)
GPS- I unchecked the last to option on the location.
Adjust haptic
uncheck some Sync from Google.
by the way what's? "Internet Sync"
and now.... im at 66% after 7hrs of being unplugged.
Internet sync meaning anything that may transfer data in the background like google talk, weather apps, Skype, etc.
Glad to hear those stats ! Take a screen Cap of the battery stats when it gets below 10% and post here
Sent from my SPH-D710 using XDA
Dudebowski said:
We're currently in a lull period between development phases now that ICS is blowing up all of our E4GT's. Samsung's kernels leave a lot to be desired, hence the current work towards a proper aftermarket kernel. ICS roms are very new, especially the custom ones going on in the dev kitchen right now. Software level ROM coding is one thing, the devs will get that fixed, but ultimately they're dependent on a solid kernel... and one of the biggest problems with the kernel, is that ever-elusive battery life.
so:
God-Tier devs, correct me if I'm wrong, and please add your thoughts, additions, and suggestions below. I'll try to keep a live OP post for a universal E4GT battery tweak guide.
Things that eat up our E4GT battery for now, with workarounds:
WiFi : Turn it off when not in use
raise the network scan interval (Rom Toolbox allows build.prop tweaks such as this,)
change the sleep policy for the wifi to Never While Charging to allow wifi connection to die when phone is off (in spare parts).
NOTE: WiFi is a more desirable data connection than 4G as far as batt life is concerned. 4G is auto disabled when wifi is on for most ROMs.
4G: Also turn off when not in use. Use the latest modems available. Flash with odin/mobileOdin because the CWM flashables sometimes don't stick.
Haptic Feedback: Turn off haptic feedback, vibration kills. (Particular to CM9 ROM, haptic is set too strong right now, TouchWiz-based ROMs are fine, but if you can live w/o it...)
LED notifications: Another wakelock offender. Turn them off for now, it's one of the reasons the device stays awake when it should be sleeping. Sleep is good.
Get BetterBattery Stats by chamonix : Take a look at it after a long period of uptime without restarting (quick or full) to allow a greater set of data to parse into stats. Some apps you use may be eating away at your battery from the background. Spare Parts Plus and it's root-friendly brother BladeBuddy is also valuable.
Suggestion, with disclaimer: Use the latest stock or Rogue kernels and modems. sfhub keeps the most updated modem D/L list . Don't forget that you should not flash ANYTHING from ICS kernel/recoveries yet!!! There are known issues with these kernels, and every last one of them is a beta stage leak from samsung along with a custom recovery and some little tweaks to work with the various ICS roms. The flashing HAS bricked MANY phones! There will be great fanfare and notices from the developer teams once we have an ICS kernel that works. It's mostly dependent on Samsung releasing sourcecode, although there are some teams working on porting the source of the other Galaxy II's... the race is on!
Touch sounds and screen lock sound: These currently cause partial wakelocks in Galaxy S2 ICS ROMs , leading to some amount of battery drain. System Settings>Sound menu to turn these off for now. (thx coiledwire)
----
Universally true:
Live Wallpapers: If you can live without electricsheep or the other various animated wallpapers, do so. I can't
Battery Tuning: If you didn't condition your battery when you first got it, good luck. In any event, try to condition it from here on out by burning it out completely (phone won't boot with it) then charge 100%, keep it off charge until it dies again, CWM Wipe Battery Stats, run the battery down again without charge. Repeat the charge/kill cycle a couple times. New kernel or ROM? Start from scratch again. Battery stats are saved in /data, so old stats can mess with a new ROM's recognition of the cell's true charge. Also, if you've got aftermarket cells that aren't the same mAH, you'll only get as good a conditioning as the weakest battery can take. Battery Calibration app can set a reminder to flush the battery stat counter file when the phone is charged, if you need to charge with your device on.
Sync: If your sync is running all the time from frequent emails, gvoice msgs. etc... and the like, try turning off some of your heavier data tranx and refreshing manually when you need it.
EDIT:
Darchstar and the CM9 Team put together a similar list with a few things not listed above. Check the 'Power Saving Options' section on the [url="http://e4gtcm.blogspot.com/p/customization-guide.html] CM9 Blog[/url]
I've also since learned that wiping battery stats does nothing with prolonging battery life. There's numerous articles quoting official Google/Android developers where they explain this flat out It may help your system recognize the true percentage of your charge, but that's about it.
[url="http://forum.xda-developers.com/showpost.php?p=25060053&postcount=1]Bump Charging[/url] is suggested by HTC developers to potentially DOUBLE your battery life.
Click to expand...
Click to collapse
Links in your edit post dont seem to work.
I've found that taking the wifi frequency band off of auto and changing to your desired frequency helped my battery when Im on wifi and the phone is sleeping
Sent from my SPH-D710 using XDA
Dudebowski said:
Internet sync meaning anything that may transfer data in the background like google talk, weather apps, Skype, etc.
Glad to hear those stats ! Take a screen Cap of the battery stats when it gets below 10% and post here
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Ok here are my screencapture for FD24.
I just updated to FD26 using NoData It looks like preserve all my settings so I'm gonna give it a shot tomorrow , I will report back.
CM9 when you finally get phone to sleep nice and soundly
....or just stick with GB roms that work and stop suffering yourself these ICS leaks.
Some of us have flash addiction. Some of us enjoy bring Guinea pigs for development. I for one just left my last phone running cm7 and couldn't bear the austerities of a stock ROM. The GB twiz hacks are alright, but it doesn't feel like home to me.
Sent from my SPH-D710 using XDA
A few of us are actually doing better with battery on ICS. One problem is that we get so many leaks and ROMs that the battery might not be having a chance to settle
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
Beejis said:
Links in your edit post dont seem to work.
Click to expand...
Click to collapse
*fix'd.
im0rtalz said:
CM9 when you finally get phone to sleep nice and soundly
Click to expand...
Click to collapse
w00t w00t!
I get pretty good battery on AOKP:
Good thread, thanks for the tips.
Transmission sent from my slim n trim Galaxy S II.
Agree with just about everything. One thing that I disagree with is letting your battery die at all. It actually decreases the life of the battery in lithium ion batteries. Its an old school method for old batteries. Try never going under 15% if possible. Everything else is correct as far as I can tell.
Sent from my SPH-D710 using xda premium
On the topic of battery calibration, if you know how to run scripts, the creator of V6 Supercharger and 3G Turbocharger scripts has also created "Die Hard Battery Calibrator" which will calibrate your battery in only about 20 minutes (must be plugged in that entire time)
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
LordLugard said:
....or just stick with GB roms that work and stop suffering yourself these ICS leaks.
Click to expand...
Click to collapse
What he said
Sent from my SPH-D710 using XDA
so I flashed the Nexus Rom as well as the newly updated 3.8 version with the battery % feature flashed on my phone. The entire procedure was done as instructed (restore/clear 3+ times on everything as instructed) and I waited well over 10 minutes upon a reboot. So all is set and almost everything is working flawlessly.
There are few issues, however, which I'm curious to know if I'm the only one experiencing this:
1. Battery Drain: Fully Charged at 100%, unplugged the cable at 6AM this morning. The phone has been on its battery power for roughly 7.5 hours now handling a total of 5 minutes of calls, roughly 30 text messages, 5 minutes of non-wifi internet usage, email is being pushed, and flashed 3.8. My display is set slightly below the mid section and I have zero widgets on my main screen except for the search bar. A total of 6 icons on my menu and that's it (only 1 page). My battery is at 40% right now. It's only been a day since I've had this flash and I just flashed on the 3.8 just few minutes ago.
2. From the Status Bar pull down menu, Shutdown and Reboot, Recovery option would hang and freeze the phone until I pull out the battery. I can only enter the Recovery mode manually by holding both +/- volume, power on, and releasing both once the 'samsung' logo appears.
3. Mobile HotSpot freezes for good 1-2 minutes. I cannot use my phone as a Hotspot at the moment.
I absolutely love the Nexus Rom from the looks, performance, looks to looks, but few of the glitches I've mentioned are quite irritating. If I'm the only person experiencing this, I'd want to continue on the search to remedy this issue. Please share some experience, ideas, or resolution if you have any!
1.) That's about right for battery. It's a leak so the battery life is still wanting compared to gb. If you thinks that's bad though, you should have seen uclc4
2.) Known bug. Even though its ucld2 the shutdown bug is still present for a few, and especially manifests itself as soon as you run fix permissions. Although the shutdown hang is "reportedly fixed" on ucld2 i'm running seanscreamz sky ics 4.2D-8 with ucld2 base and i have the same problem as well.
Suggestions, either use quickboot from google play, or reflash following op instructions and DO NOT fix permissions
3.) Hotspot doesn't really work all that well, even with the ultracfg fix. I recommend the "WiFi Tether 3.1-beta12" app, i'm using this instead and it works well.
icenight89 said:
1.) That's about right for battery. It's a leak so the battery life is still wanting compared to gb. If you thinks that's bad though, you should have seen uclc4
2.) Known bug. Even though its ucld2 the shutdown bug is still present for a few, and especially manifests itself as soon as you run fix permissions. Although the shutdown hang is "reportedly fixed" on ucld2 i'm running seanscreamz sky ics 4.2D-8 with ucld2 base and i have the same problem as well.
Suggestions, either use quickboot from google play, or reflash following op instructions and DO NOT fix permissions
3.) Hotspot doesn't really work all that well, even with the ultracfg fix. I recommend the "WiFi Tether 3.1-beta12" app, i'm using this instead and it works well.
Click to expand...
Click to collapse
Thanks for the input. I wish the battery life was better. I'll let it sink in for a few days to see if it'll improve. If not, I'll just have to keep searching for a rom with a better battery life. I've tried Beastmod, Juggnaut and many others which have yet to last for over 12 hours.
I read that the hotspot issue was fixed and with the 3.8 update, I presumed it to be completely polished. The shutdown bug, I can live with - hoping there's an upcoming fix in the works.
This ROM is the sickest looking ROM I've tried so far. I wouldn't call it the smoothest due to it's intermittent force closures and freezes, but when things improve down the road, I think this one will stay on my phone for awhile!
I've been using this rom for about a week and the battery has been working great, better than any stock rom I've had. I'll unplug it in the morning around 745 and it'll last until I go to bed around 11.
Sent from my SAMSUNG-SGH-T989 using xda premium
You should try Mr X' s tweaked Telus stock ROM. This ROM has the best battery life among T989 ROMs period. It is Canadian but works great on T-mobile network. It also does not have much bloatwares as T mobiles stock one. Just Make sure you have wifi sharing, wifi sharing manager and social hub frozen through titanium backup.
As for wireless hotspot, the stock one from Telus works well.
I get about 16 hours use. It may vary for you but battery lasts longest with this ROM.
Sent from my SGH-T989D using XDA
This is a general discussion thread. You can share your Current setup of Robin, it would be helpful for us to know which ROM can be used as Our daily driver.
_____________________________________________________________
I'm currently using OmniRom's last build with Magisk module cross-breeder lite edition.
It's giving me Quite decent performance and Battery life.
Normally on continuous usage, it lasts almost 5-6 hrs on single charge.
_____________________________________________________________
If anyone getting a better Battery life, don't hesitate to post below.?
Post-Credit: @me ?
Thanks for sharing, I cannot give screenshots for everything here. I might have them but have to dig into the folder of screenshots but for now here is my battery experience over all.
I have used PA, Carbon and Omni extensively. So everything below is not a ROM review but its battery usage over all with them.
P.S. : For all ROMs, I use Greenify and Doze mode (within ROM, if not available then via NapTime).
PA for me has always been close to stock nothing great maybe a bit better. But because of its roaming issue I stopped using it. And switched to carbon.
Carbon is far better than PA and has very little standby/idle drain but it started giving me a weird 20-25% battery cut off issue and device used to shut down randomly anytime below 25% so I switched to Omni.
Omni has fared pretty well for me. Unlike other ROMs I get consistent battery life i.e. 3-4hrs SOT over a period of 10-15hrs. The ROM seems far more stable and there aren't any random battery drains. Omni sometimes behaves a bit erratic when using new camera apps i.e. first few times it would drain battery a lot but later it works fine. Its the device or ROM I don't know.
For Duo video calls it isn't so great after 30-40mins of call the battery is down by 30% maybe. But that is fine I guess the video call is on data too. So Robin isn't so great for that sort of heavy use in general I guess.
Here is my most heavy use day (on all ROMs) for which 10-12hrs is most the device can sustain.
Morning (for the device) starts at about 6:30-7am.
Its day starts with 96-100%; no matter how much juice it has I make sure I unplug anywhere above 95%.
My usage isn't heavy but I use data(3G/4G) 90% of the time,
Location/GPS is ON for about 40-80mins,
Voice calls ~30-90mins in total, (Most are cellular, 5-10mins VoIP calls)
60-90mins podcast/music, Podcasts which I listen are downloaded before but music is streamed via NewPipe ,
Mail, Twitter, Excel, Pocket app, Camera is used in between randomly.
I don't watch much YouTube on the device maybe a couple of 2-3mins clips, I mostly scroll YouTube to add them to watch later for watching on desktop,
SOT ~3hrs
I have to plug the device by 6-7pm with all that usage. Because by that time its about 15%. And for me Robin at 15% means about 10-15mins of use.
For not so heavy use days the device lasts from 7am to 9pm with SOT of ~3-3.5hrs + voice calls of 30-60mins + 40-60mins GPS/location.
Since Android N I haven't touched 4hrs+ SOT over a period of 10-15hrs of usage sadly.
That only happens if I unplug the device and use it continuously for 4-5hrs reading maybe with no waste in idle drain or data or wifi or push notifs etc. But that isn't a case of regular use for me so I will disregard that.
I have recently started using interactive governors like GlassFish and FairPark but can't say they have helped much. Standby/Idle drain is as low as 1-2% over 4-5hrs.
If you are getting 4hrs+ SOT over a longer charge time of 10-12hrs, I am all ears and want to know what different do you do.
I use Omni with Unicornblood kernel and Hawktail profile in Ex Kernel manager. I also use greenify and naptime. I'd say on average I can get between 3 and 4 hours SOT. On the lower end will be days where I'm out and about a lot so I'm on data, lots of idling, random browsing, reddit, messenger, etc. Usually have spotify running in my car through bluetooth. On the higher end will be days where I'm playing on my phone most of the day, with little screen off time, I can probably push over 4 hours on those days.
Today I've been off the charger for 10 1/2 hours, I have 1 1/2 hours of SOT. I spoke on the phone for about 15 minutes, browsed the internet a bit, some instagram, messaging, etc. and I still have 54% left.
I've tried Paranoid Android and LOS.
With PA the battery on my Robin drains like crazy and I noticed some heat problems as well.
As for LOS, it gives me quite decent battery life but had issues with the power button, the phone struggles to wake sometimes.
Should I try Omni then?
Luisalejandroqi said:
I've tried Paranoid Android and LOS.
With PA the battery on my Robin drains like crazy and I noticed some heat problems as well.
As for LOS, it gives me quite decent battery life but had issues with the power button, the phone struggles to wake sometimes.
Should I try Omni then?
Click to expand...
Click to collapse
Sadly there is no perfect ROM every ROM has some issue. The only question is if you can live with that issue.
The only reason for me to stop using PA was it won't work on roaming. But if PA has been stable and battery drain was the only issue try using Greenify and Naptime. The combination of both can drastically bring down your battery drain. And then use some interactive cpu governors aimed for battery life it should bring down drain to as low as 1-2%.
If you are looking for a different better ROM to try then surely try omni, Omni has been great for me so far and has no major issues as such.
/root said:
Sadly there is no perfect ROM every ROM has some issue. The only question is if you can live with that issue.
The only reason for me to stop using PA was it won't work on roaming. But if PA has been stable and battery drain was the only issue try using Greenify and Naptime. The combination of both can drastically bring down your battery drain. And then use some interactive cpu governors aimed for battery life it should bring down drain to as low as 1-2%.
If you are looking for a different better ROM to try then surely try omni, Omni has been great for me so far and has no major issues as such.
Click to expand...
Click to collapse
Omni, however, doesn't have Qualcomm's hotplugging solution, so both big cores are always on all the time and draining battery whenever your screen is on. Gandalf also messed something up with the kernel sources and broke NFC, requiring you to flash a kernel from an Omni weekly from around June-ish or July-ish to restore that functionality.
If you're patient enough, javelinanddart and Sultanxda will soon figure out how to fix the wake-on-plug lag in LineageOS. Hopefully, they'll also start on figuring out the power-button-not-waking-device issue afterwards.
EDIT: oops. Though javelinanddart proooobably found what might be causing the power-button-not-waking-device issue? Haven't had it happen on his LOS 15.1 unofficials yet so...
I am currently using Lineage 14.1-14.1-20180321 and eagerly awaiting the 'official' release of 15.1. I typically do not update to every weekly build. I usually watch the change logs and update only when the new security patches are released. Provided that update is stable (i.e. fast, everything works, no crashes) I will continue on with that build until the next security patch is released. More often than not, there are no issues, as I have found Lineage to be stable and fast.
I am running non-rooted, and I re-locked my bootloader. As a result, Google Pay is working well, without the use of Magisk.
I run Nova Prime launcher, and do not have a vast amount of apps installed:
Music - Google Play Music, Spotify, Amazon Music
Email and Calendar - Outlook, GMail, Google Calendar
Assistant - Google Assistant
Office Suite - Docs, Sheets, Drive, MS One Drive, Word, Excel, Google Keep, One Note
Camera - Stock lineage OS camera, Snapseed (editing)
Messaging - stock AOSP / Lineage OS messaging app
Video - YouTube, Netflix, Hulu (I only use YouTube to be honest... have the other two because of Chromecasting)
Misc - Google Home, Amazon Kindle
I list all those apps to say that given the relative few apps I use, I have all day battery life, for the most part. I am not a heavy user, but I check email multiple times a day, as well send/receive a LOT of MMS/SMS messages throughout the day. I generally only watch video on my phone (YouTube mostly) at home, and I generally cast it to my TV so that the Chromecast does the heavy lifting.
Overall, I have been very happy with Lineage. I finally settled on Lineage after growing disgruntled with AOSPA. The stock ROM (I gave it a good, honest shot at one point) could not cut it because of the lack of stability, heat issues, Bluetooth issues, and no updates.
I have only run into one issue (on a previous build) where by no doing of my own, the screen went blank on a full battery and would not turn on. I though the phone was essentially bricked. Held down power + volume down for 60 seconds (actually had to do this a few different times) and all was resolved. Still do not know why this happened.
Hopefully this helps someone...
@sfbest23
Thank you for replying with so much detail. But a bit of numbers would help in terms of battery life you get from your usage and setup.
Typical phone idle time and SOT. Gives a rough idea of the battery drain in standby.
I am running non-rooted, and I re-locked my bootloader.
Click to expand...
Click to collapse
I am more curious about this. So after flashing LOS you flash back the stock recovery and lock the bootloader? But when you flash back TWRP to install the updated LOS do you lose all your data again or what? Can you tell me the process you follow, I would love to do it but I find backing up and restoring everything for every update is tiresome and a little annoying. Even if one opts to only update for major releases once a month or few months I am not a fan of backup and restore process quite often.
/root said:
@sfbest23
Thank you for replying with so much detail. But a bit of numbers would help in terms of battery life you get from your usage and setup.
Typical phone idle time and SOT. Gives a rough idea of the battery drain in standby.
I am more curious about this. So after flashing LOS you flash back the stock recovery and lock the bootloader? But when you flash back TWRP to install the updated LOS do you lose all your data again or what? Can you tell me the process you follow, I would love to do it but I find backing up and restoring everything for every update is tiresome and a little annoying. Even if one opts to only update for major releases once a month or few months I am not a fan of backup and restore process quite often.
Click to expand...
Click to collapse
I do not have any detailed battery metrics, but I will start tracking this and get back to you.
Regarding your question about re-locking the bootloader... I am still running TWRP, just with a locked bootloader. I did not flash back to the stock recovery. After unlocking the bootloader, installing TWRP and ROM of choice, it is simply a 'fastboot oem lock' command. I cannot remember off hand, but I do believe that the OS was reset when I did that.
My setup. Works very well. I think omni is the best ROM available.
EAT_CHICKEN said:
My setup. Works very well. I think omni is the best ROM available.
Click to expand...
Click to collapse
Same ROM version, same Magisk version but I still get the SafetyNet API Error.
/root said:
Same ROM version, same Magisk version but I still get the SafetyNet API Error.
Click to expand...
Click to collapse
Do you have /system modified? Or xposed installed? Those will cause safetynet to fail.
EAT_CHICKEN said:
Do you have /system modified? Or xposed installed? Those will cause safetynet to fail.
Click to expand...
Click to collapse
Not using xposed.
Does using EXKM for CPU governors constitute to being a /system modification? Then I guess that would be the cause.