Database Info

"Android OS" keeping phone awake... and using data?!

Hey,
I have a Fido RHD on the latest official ROM (no root or unlock). I have noticed over the past few weeks that the battery life has been a lot worse, but I can't think of any particular app that may be causing it. Strangely, Android OS is using a lot of CPU time and also sending data!
Things I have tried to do:
Stopped all the optiona "location services" for Google apps (e.g. Google Now)
Installed Snapdragon Battery Guru (but it is currently in learning mode)
Uninstalled all unneccessary apps
How can I find out what is hammering the "Android OS" process, and why it is keeping the phone awake? Is there a more advanced battery stats app that could help with this?
{
"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"
}
Thanks,
Suman

Hello Suman,
I have a similiar issue here. Android OS is not heading my battery stats, but it held the phone awake for a reasonably long time. You should try downloading BetterBatteryStats (the apk is available here in xda dev for free, but the developer did a nice work on it and the app is very useful, so I think you should support the developer if you don't mind). For a better understand of what's going on open BBS and set a custom ref before you go to sleep. Save the dump immediatly after you wake up. Post it here. Anyone that understand partial wakelocks will be able to give you a better support.
I have seen another guy here with a similar issue, but still unresolved. Also, I still have the problem, but my ROM is different (Vivo - Jelly Bean).
If you have received the update recently via OTA, you can try wiping data. Not sure if will help, but wiping data after receiving major updates is always a good and recommended practice.
Also, if you have instant upload on, turn it off. A bug seems to cause the instant upload to try syncing every minute so you'll have high times of SyncLoopWakelock keeping the phone awake most of the time. It happened to me. If a cloud backup of your photos is very necessary as it's to me I recommend Camera Uploads feature on the Dropbox app.
Let me know if something helps!
Sumanji said:
Hey,
I have a Fido RHD on the latest official ROM (no root or unlock). I have noticed over the past few weeks that the battery life has been a lot worse, but I can't think of any particular app that may be causing it. Strangely, Android OS is using a lot of CPU time and also sending data!
Things I have tried to do:
Stopped all the optiona "location services" for Google apps (e.g. Google Now)
Installed Snapdragon Battery Guru (but it is currently in learning mode)
Uninstalled all unneccessary apps
How can I find out what is hammering the "Android OS" process, and why it is keeping the phone awake? Is there a more advanced battery stats app that could help with this?
Thanks,
Suman
Click to expand...
Click to collapse

vctrrl said:
Hello Suman,
I have a similiar issue here. Android OS is not heading my battery stats, but it held the phone awake for a reasonably long time. You should try downloading BetterBatteryStats (the apk is available here in xda dev for free, but the developer did a nice work on it and the app is very useful, so I think you should support the developer if you don't mind). For a better understand of what's going on open BBS and set a custom ref before you go to sleep. Save the dump immediatly after you wake up. Post it here. Anyone that understand partial wakelocks will be able to give you a better support.
I have seen another guy here with a similar issue, but still unresolved. Also, I still have the problem, but my ROM is different (Vivo - Jelly Bean).
If you have received the update recently via OTA, you can try wiping data. Not sure if will help, but wiping data after receiving major updates is always a good and recommended practice.
Also, if you have instant upload on, turn it off. A bug seems to cause the instant upload to try syncing every minute so you'll have high times of SyncLoopWakelock keeping the phone awake most of the time. It happened to me. If a cloud backup of your photos is very necessary as it's to me I recommend Camera Uploads feature on the Dropbox app.
Let me know if something helps!
Click to expand...
Click to collapse
Ok, I will give BBS a go, thanks for the recommendation.
I did a factory reset as soon as I received the JB OTA (I always do this after any major software update). The Android OS problem did not start right after the update - it is a fairly recent problem.
I don't have Google+ camera upload turned on (but I do have Dropbox camera upload, as you suggested).
Thanks,
Su

Hey,
Bit of a noob question I think... how exactly do I "use" BetterBatteryStats. I'm not sure how to set it up so it measures what I want it to.
This is what a full day's drain from 100% to nearly empty looks like at the moment:
Can anyone shed some light on my mystery battery thief please??!
Cheers,
Su

Are you forced to restart your phone everyday?

I'm forced to restart my phone everyday ,when I don't it becomes really laggy, the phone stutters when I scroll , when I swipe between the homescreen, when I switch between apps, I'm running stock kit Kat with Franco kernel r33, but I remember well the same used to happen when I had my nexus 4 and everything was stock I just had root .
Just closing all opened apps doesn't solve the problem .
Do you guys have similar issues?
Sent from my Nexus 5 using Tapatalk

I never had to do that with my phone.
Sent from my Nexus 5 using xda app-developers app

Nope. I restart once a week, if that. Never have any lag/stuttering/slowdown issues. Stock rooted.
Sent from my Moto X

Nope. Everything stock at the moment but I've also used Franco r33 and didn't have that problem then either. If you're just using the recent apps screen to close your apps that might not be enough since it'll only list foreground apps and not background services which would more likely be the culprit. If you aren't already, try using an advanced task killer app (I can't recommend any as I don't use them) and try killing services one by one until the lag stops so that you can figure out which app/service is causing it.

There is no reason to use a task killer or to kill all apps.
Sent from my Nexus 5 using xda app-developers app

Kreateablaze said:
There is no reason to use a task killer or to kill all apps.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Not for everyday use, no, but to diagnose which app is being a resource hog what else would you suggest?

I've never restarted my phone due to "lag." My current uptime is about 3 weeks. I'm bone stock.
Sent from my Nexus 5

Never restart. Faux r33 too

Try restoring the factory image and running it for a day or so without any extra apps. At least then you'll know if the phone is faulty. It's likely to be an app or two that are using a lot of memory, but I thought the mighty Nexus could cope with anything!

I have stock ROM, no root, since launch and I've used it everyday 24/7.
No lag problems, never had the need of rebooting it, as a matter of fact sometimes it has been on for more than a month without a poweroff or reboot.

While I've not "had to" restart my N5 due to lag, I have gotten into the habit of restarting it every night when I recharge. I started doing this when google play services (old version) was going haywire and sucking down the battery every now and then.

I only restart my phone when it's really needed (like an app requires reboot and etc)

I restart my phone maybe once every two days or so just to start fresh. Same with your computer restarting it will eliminate processes that you may have started and not ended or background processes running and so on and so fourth.

I only restart when the device doesn't sleep. I find after a day or 2 Google now keeps the device from sleeping. A reboot fixes it right up.
Never experienced lag. Running stock, gravity box, apex launcher and Franco kernel
Sent from my HammerHead

Having to restart your phone that frequently is not normal. Not that it would help a lot, but have you tried switching to ART?

OP, how many apps do you have? Anything else you modified but the kernel? Overclock, underclock, UV, etc.? Give us more infos.

I recently set up my tasker profiles for morning - morning commute - work and home. The last one I have is a nightly reboot at 4am. I just have the tendency to restart my devices daily. Memory dump and fresh start every morning never gives me any issues.
Look into it.
Sent from my Nexus 5 using XDA Premium HD app

This is what I use as my daily driver and only reboot when an app requires it or once every two weeks when I let it die for battery preservation
{
"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 Nexus 5 using Tapatalk

I never restart my phone unless there's a need to flash something (ROM update, kernel, etc.).
Also, I think my phone feels smoother than before, especially when I don't clear anything in recent apps.

So i just flashed back the stock kernel and everything went back to normal, I guess I'm done with custom kernels, I've always had bad experiences with them, I don't know if I'm really picky and other people don't notice it, but I can't believe I'm the only one who experiences lag while on custom kernels, maybe the're too agressive trying to save power?

[Solved] Android OS extreme Data usage.

Hey all,
Anyone noticed any recent abnormally high background data utilisation from Android OS (both wifi and mobile?).
UK XT1032, 16GB stock unrooted Tesco firmware currently on 176.44.1. Hangouts, Migrate, Google+, Google Play Music, Google Play Movies & TV, Google Play Games, Google Play Books, & Chrome all disabled. Google Backup and Automatic Restore are on, all of the other Google Services set to Sync automatically. I use Firefox as my browser (with a sync to my laptop Firefox).
I've looked back on the data records for my phone and it looks like the problem started around the 25th of February. This roughly coincides to the last OTA to 176.44.1 which I'm pretty sure I got on the 26th or 27th. The most recent Google Play Services (4.4.43) installed on 1/3/14. The only other thing I can think of is K9 Mail which I installed on the 24th, although I'm struggling to see how a User app could show data used under Android OS.
I've checked my other half's Moto G (8GB UK version - O2 variant, stock unrooted) and she hasn't got this showing up at all. I've compared Sync/Backup settings between the two phones and they are the same, and other than Chrome she has pretty much the same stuff disabled. She doesn't use Firefox, and uses the stock email app with an exchange account.
Wifi
{
"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"
}
16/1/14 to 13/2/14 - 311MB (so about 11MB day)
13/2/14 to 25/2/14 - 71.2MB ( about 6 MB day)
25/2/14 to 13/3/14 - 0.93GB ( about 55MB per day)
Mobile Data
15/1/14 to 15/2/14 - 70.19MB ( about 2.5MB per day)
15/2/14 to 25/2/14 - 21.14MB (about 2MB per day)
25/2/14 to 13/3/14 - 275MB (about 16MB per day)
Possible solutions to try
1) Get rid of K9 email for a while (I use it because the stock email app appears to be incompatible with my talktalk.net ISP email account - it receives but can't send).
2) Cache Wipe in Recovery (although I'm pretty sure I've done this once since the last OTA)
3) Remove and then re add my gmail account.
4) Factory Reset.
Before I commence anyone else experiencing this problem, or even better has had the problem and solved it!

Indeed I have the same issue, the one thing I believe that fixed it was turning off Google backup but I am not sure if is a permanent fix or a fix at all, since I renabled it. Try it!

Thanks, switched off Google Backup this morning, and that seems to have sorted it. Android OS only used 336KB of mobile data over 10 hours or so. I'll try and re-enable it later and see what happens.
Sent from my XT1032 using XDA Premium 4 mobile app

neu - smurph said:
Thanks, switched off Google Backup this morning, and that seems to have sorted it. Android OS only used 336KB of mobile data over 10 hours or so. I'll try and re-enable it later and see what happens.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Bah!
Turned Google Backup back on just before bed (thinking that 6-7 hours on wifi before going to work would be enough for it to do an initial backup) and then headed for work yesterday- Android OS chewed through another 20MB of mobile data in less than 2 hours.
So a simple disable/re-enable isn't the solution. I'll think I'll go for a Factory Reset. Checked my dates again and the problem definitely coincides with the OTA to 176.44.1 - I got it on the 25th.

Issue solved. Nothing to do with the OTA after all, although the factory reset gave me a valuable clue, when I noticed one of the things restored after a factory reset was my static wallpaper.....so Google Backup and Restore backs up the wallpaper, and I've an automation app installed set up to regularly refresh my wallpaper from the gallery. I created the routines on the 24th. Doh. Backup has been uploading multiple wallpapers everyday.
Tested today with the wallpaper switcher disabled and Backup and Restore enabled - no crazy data use and even better battery life than usual. Wallpaper switcher enabled and Backup and Restore disabled all is also fine. Both enabled gives crazy Android OS data use and noticeably more battery drain.
Sent from my XT1032 using XDA Premium 4 mobile app

Marshmallow and App Data Restoration

This is a simple question, but I'm wondering if the answer is complex...
With Android 5.1 and below, Google backed up Apps, and certain system settings, etc, but NEVER app data itself.
With 6.0, I noticed some apps (depending if they're compatible with google API's) back up and restore app data as well, included with the app restoration.
You may ask, why would this guy not want google to restore app data?
Simple... In my testing for a seperate issue, I ran into a serious wake lock problem. After a full RUU, full wipe, and reinstallation of a Marshmallow ROM on my M8, I am getting constant wakelocks and battery drains after all my apps are restored with their data.
I would like to test to see if it is faulty data possibly restored with an app, but that unfortunately gets restored with Google's App backup now.
Anyone know if there's a way to system wide wipe app data? NOT just the cache? Or just tell Google only to backup Apps and not data?
Thank you!

The answer is simple although it's probably not what you want to hear. Don't let Google restore your apps. Do it the old fashioned way. Start clean and install your apps as you need them.
If you're not willing to do that, I'd suggest using Titanium Backup to restore your apps instead of Google. With TB you can choose to restore apps without the data. If it were me though, I'd just bite the bullet and install them one at a time. Seems to me that in a case like yours, that would be the best way to go.
Make a backup of what you have now with TWRP. Then start fresh. If you figure out what's going on, you could maybe restore the backup and fix what needs fixing on it.
Sent from my HTC6525LVW using Tapatalk

@bigblueshock you aren't by chance using a 5ghz Wi-Fi network are you?
Sent from my Nexus 6 using Tapatalk

@robocuff - Yeah i suppose so. It doesn't take too much more time to install one by one. I guess an extra few minutes.
dottat said:
@bigblueshock you aren't by chance using a 5ghz Wi-Fi network are you?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I am... Bad idea? =/ I can always do 2.4 instead if that makes a difference.
I also made sure wifi scanning is off.

bigblueshock said:
I am... Bad idea? =/
Click to expand...
Click to collapse
There's a hellish 5ghz wakelock bug on MM. Try 2.4ghz or cellular and see if it sleeps.
Sent from my Nexus 6 using Tapatalk

dottat said:
There's a hellish 5ghz wakelock bug on MM. Try 2.4ghz or cellular and see if it sleeps.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Will try this too. Ill just completely turn off 5 GHZ in my wifi options, just to make sure it doesn't try to connect to any.
I will report back if this helps. Thanks again!

Well, just want to provide an update...
It may not be marshmallow causing this after all. I just did a full clean flash into Viper 4.6.1 (android 5.0.2)
During the day and evening phone was fine. Over night is when the wake locks started happening sporadically. In about 6 hours, dropped about 10%. I checked Wakelock Detector app, and it seems google play services is really pumping out those wakes.
I don't really use bluetooth, I only have 1 device even paired with my phone (my car which disconnects when turned off). But I do keep bluetooth Enabled
I just charged my phone to 100%, turned on Airplane mode + wifi. I'm going to monitor during the day. Is there a way to detect within wakelock detector exactly what part of android is causing this? It doesn't seem like an app itself, because the wakes are coming from android system. Or could an app be causing the google play services wake?

dottat said:
There's a hellish 5ghz wakelock bug on MM. Try 2.4ghz or cellular and see if it sleeps.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hey @dottat and others. I ran into something funny I figured I'd share Not sure of the cause, but take a look. I posted in the respective ROM's thread, but I thought I'd share it in the Q&A as well.
{
"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"
}
A day before this, I temporarily went back to a 5.0.1/5.0.2 ROM, found out it was an app or two trying to destroy my battery in the background with high GPS usage. After adjusting and fixing, Phone drained normally, maybe like 4% a whole nights of sleep.
Fast forward, I reflash Marshmallow ROM, set it up, and no more wakelocks/excessive battery drain. I charge the phone with my QC2.0 Charger (QC probably isn't enabled anyway in kernel, but didn't make a difference to me) from about 50% to 100% and unplug, and go to sleep.
This morning I woke up to phone at 86%. I check wakelock detector, and power history, nothing out of ordinary. Scratching my head at this point, I restart the phone, and BAM, phone is at 35%.
Some points below
1) I believe it was the first time I charged the phone fully, not sure if that had anything to do with it. I've never needed to calibrate battery in past...
2) Wifi was strictly on 2.4 Ghz. Cellular coverage is good. GPS is on, but not being used.
This sounds like a longshot, but I'm leaning to the kernel probably not supporting QC2.0, and it being detrimental to charging the phone. Possibly ROM thinking it's enabled, but kernel is disabled. So right now I'm charging the phone to 100% using a computer USB port (500mA max) just for testing purposes.
Have anyone ever seen this before?

System ui memory leak

Do any of you facing an issue of system ui taking a lot of memory? It happens with me daily and only way to a temporary fix is reboot.

mujeeb999 said:
Do any of you facing an issue of system ui taking a lot of memory? It happens with me daily and only way to a temporary fix is reboot.
Click to expand...
Click to collapse
What device? What ROM? What mods? What's running in the background? What makes you think it's specifically a memory leak, instead of something else like a runaway process?
Without details, we cannot help you.

Moto turbo xt1225, stock marshmallow with December security patch. Everything stock, no mods or root. I think it's a memory leak because system ui takes as much as 400-500 mb in couple of days after rebooting.

mujeeb999 said:
Do any of you facing an issue of system ui taking a lot of memory? It happens with me daily and only way to a temporary fix is reboot.
Click to expand...
Click to collapse
mujeeb999 said:
Moto turbo xt1225, stock marshmallow with December security patch. Everything stock, no mods or root. I think it's a memory leak because system ui takes as much as 400-500 mb in couple of days after rebooting.
Click to expand...
Click to collapse
1) What is causing YOUR memory leaks? Could be anything. Lots of apps like to run in the background, even if you are not using them, so that when you do "open" them, they will snap open in an instant. (Since they are already running as a background process.) The developer thinks HIS app is so important it needs priority. Meanwhile all the time you don't have it actively open, it's still running in the background sucking up RAM. Every app developer thinks their app should be your most important app.
Greenify
{
"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"
}
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
This is why an app like Greenify give you control back. Historically it was an app that needed root, but reportedly now also runs without root?
NEW: "Aggressive Doze" and "Doze on the Go" to maximize the battery saving on Android 6+, even without root!
(details explained in settings)
Click to expand...
Click to collapse
I don't know, as I've always been rooted and will always be rooted, but check it out. Anyway at least on my rooted phone Greenify will let you forcefully HIBERNATE all apps on a list of your apps that you choose, so that they will NOT run until you manually open them. Like my flashlight app doesn't need to be running in the background until I NEED my flashlight. HIBERNATE. Until I open the app. Then upon closing the app, will go back into HIBERNATION. Greenify will suggest apps to hibernate, but you can expand to a larger list of ALL your apps to choose from. I have over 200 apps, so I just went down through the list and checked most of them off.
Of course, you don't want to hibernate stuff like your email app or messaging app or weather widget. Those DO need to run in the background. But most everything else, yes.
_________
2) This won't necessarily help you, since you are not rooted, but I also use Auto Reboot to perform a daily scheduled reboot of my phone when I'm not using it. Like 4am, but would depend on each person's preference. Rebooting clears the RAM, prompts app updates, and generally just refreshes your phone. Same speed benefits as rebooting any PC. I have this set on my phone, my wife's phone, as well as all my friends' Androids who I tech support. We're all rooted of course.
Rebooting daily prevents a lot of the lag that seems to accumulate over time. So, I know you are thinking the reboot is "temporary fix", but rebooting daily can prevent any memory leaks from becoming a runaway process.
Auto Reboot (Root only)
https://play.google.com/store/apps/details?id=com.pereira.autoreboot&hl=en
This scheduled pre-emptive rebooting when you are NOT using the phone is better than having to reboot when you are actively using the phone, yes? At work, we have a server that seems to freeze up about once a week. It would freeze up when we were using it, really needing it! Finally our engineering staff got the idea to schedule a weekly reboot of this server during a down time when we were NOT using it, and now it never freezes up!