Database Users

[Q] (Q) Why is my xperia play "awake" when the screen is turned off ?

Hey forum ! , I was an iphone 3gs user and made the jump to android when the play came out.
Ive noticed my battery is draining 2-3% an hour and looking at the "battery use in setting and then looking at the graph it show the phone is randomly awake even when the screen is off.
My play is rooted using gingerbreak 1.1 and has mostly all the bloatware removed.
non of the apps i have installed ask for permissions to prevent standby, I only have tune in radio, mobo player, facebook, twitter adobe pdf viewer, fpse, snesoid, gameboid google maps youtube imdb touch calendar es file explorer unit convertor and ringdroid installed.
i have 12 processes running using 86mb of ram
all apps are closed properly, wifi is off, background data is enabled ( but no applications i use in the settings allow auto refreshing of data)
The battery life of my xperia play has never been great (lasts about 24hrs with just checking facebook, twitter and xda forums using the built in browser)
I just wonder what is causing the phone to keep waking up randomly, is this the culprit of the battery drain?
I have a couple of theorys .... i did install desktop visualiser to change the icons then once they were changed i deleted the app (i read this app causes battery drain) maybe this could be a cause i thought deleting the app would fix,
2nd i travel around as part of my job so i wonder if the phone is going through areas where there is poor connectivity and its constantly trying to connect to different networks causing the drain.... but does anyone know of any efficient lightweight apps that disable this when the screen is off.
lastly I think the could it be widgets i only use the built in ones with the phone, the wifi on/off gps on/off and data on/off
do you guys turn data off during the day to save battery and do you turn background data off ? i think its anoying have to change all these settings off to sqeeze a tiny bit more of juice out the phone, it probably uses more turning them on and off avery 1hr or so
any suggestions or setups of how other people have got there phone up and running with good battery life would be a real help
cheers !

Deleting all widgets certainly saved my some battery, also deleting the SE launcher with launcher pro seemed to save me a lot of battery but I'm not sure about this.

2 to 3% an hour isn't bad with radios on at all. When you say awake, do you mean the screen is on, or that it's just in standby? There is nothing in battery stats that say "awake" you need to be more specific on what the system says, not what you think it's doing.
If the screen is coming on "randomly" then it could be an incoming txt, email, phonecall or something like that. Lower your screen timeout in the settings to help there.
If its phone idle or standby, then again 2 to 3% is nothing. That's 30 50 hours of standby receiving emails, txts and what not. Nothing to complain there.
Sent from my DROIDX using Tapatalk

reboot fixed my stay awake problem
by stay awake he means no lockscreen/passcode/slide to unlock

blickmanic said:
reboot fixed my stay awake problem
by stay awake he means no lockscreen/passcode/slide to unlock
Click to expand...
Click to collapse
That's not what he means. Reread his 2nd paragraph.
Sent from my DROIDX using Tapatalk

Click on settings then about phone then battery use then at the top of that screen there should be a set of numbers saying how long the battery has been used since the last charge, click that an it displays a graph , on the graph page it shows when the phone is "awake" by awake I mean the screen is off the phone should be in standby mode but its being acessed by something i.e a program , like its woken up to perform some action. Anyway im wondering if anyone elses phone is awake randomly when the screen in off and in standby mode. When I factory reset I neget had this issue but its after installing apps I think or some setting im missing any ideas

I have the same problem. My Xperia Arc is "awake" all the time. Screen is locked, turned off but in battery usage I see that the phone is awake even with screen off. The culprit seems to be the native messaging app as it consumes the most battery. I'm not sure what is going on, what is the messaging app doing or which process is using it.
Any ideas anyone?

New phenomenon: location based battery drain

Im currently on XXJVS with Semaphore 1.7 kernel, but i have experienced the same behaviour the last weeks (or maybe i just started noticing recently): traveling starts a battery drain
Update: see post #22
Some background:
I suffered from the Android Process battery drain up to XXJVR. Flashing XXJVS seems to have improved things (after numerous reflashes of XXJVR and XXJVQ which didnt help. My phone's cpu keeps between 1% and 3% when sleeping, but i have noticed that Cpu rockets to like 30% as soon as i leave my house to go to work, or leave work to go home. Its as if the phone keeps trying to connect to some network all the time, but only while in motion (and trying to lock in from tower to tower?). The problem is however that Systempanel nor the log give great clues where to look.
Examples:
In this first example, my phone is hooked to the charger during the night, and the alarm clock is running (hence the steady 10% cpu load). As soon as the phone is disconnected, cpu drops to low levels. On the exact minute i leave home, cpu rockets. And yes,i arrived at work around 07:50.
Home environment:
- connected to wifi
- good 3G coverage
- 3G, Bluetooth,GPS enabled
- no Bluetooth profiles present
Work environment
- wifi network present but not connected
- average 3G coverage
In this second example, i'm at work, hardly using the phone. Without touching the phone, stepping into my car and driving off, the cpu kicks in again. Notice there is no Device Usage whatsoever at the moment the CPU climbs. Bluetooth profiles active at this point and paired & connected to the carkit.
This last screenshot shows the typical clues (or lack thereof) that SystemPanel shows: just the System process using the most CPU.
Also the logcat doesn't provide much clues (or too many maybe) either. I have found that some applications couldn't contact GoogleAnalystics because i have AdFree installed, so i uninstalled those apps.
Frankly, i don't know where took look further. The damn android 'System'process just doesn't give enough clues. I have formatted internal & external SD, deleted cache & Dalvik cache, flashed & factory resetted to no avail. I'll try to have a log running tomorrow morning just before leaving the house to see if i can find what log entry corresponds to the system process kicking in. In the meantime, has anyone ever seen this behaviour, or any hints where to look?

adb bugreport > c:/report.txt
look there maybe

Install System Tuner pro it has option to record processes(+analyzer ) better than System Panel.
..try freze Maps or turn off network localization -Uncle Google likes to locate phone very often .
Sent from my GT-I9000 using xdapp

Hi,
Same phone and ROM, same problem.
Keep us updated!

Hmm, I have heard Galaxian kernel is battery sucker too...
Regards

wingg said:
Install System Tuner pro it has option to record processes(+analyzer ) better than System Panel.
..try freze Maps or turn off network localization -Uncle Google likes to locate phone very often .
Click to expand...
Click to collapse
in short words - bull****
i have not touched (freezed/deleted) any app
yet still i have not noticed a drain, any kind of drain
let him determine what app is causing the 100% cpu usage first
prior to advising him to freeze or delete anything - that is wise you have to agree
also localization service would not provide such high cu usage
think please

Hi,
It might be facebook 1.7.1. There are several complaining comments that "upload manager" process is running in the background and prevents phone from going into deep sleep mode.

i got data connection active all the time with all apps syncing (gmail, twitter, facebook)
and phone got no problem sleepin =)

pwhooftman said:
Im currently on XXJVS with Semaphore 1.7 kernel, but i have experienced the same behaviour the last weeks (or maybe i just started noticing recently): traveling starts a battery drain
Some background:
I suffered from the Android Process battery drain up to XXJVR. Flashing XXJVS seems to have improved things (after numerous reflashes of XXJVR and XXJVQ which didnt help. My phone's cpu keeps between 1% and 3% when sleeping, but i have noticed that Cpu rockets to like 30% as soon as i leave my house to go to work, or leave work to go home. Its as if the phone keeps trying to connect to some network all the time, but only while in motion (and trying to lock in from tower to tower?). The problem is however that Systempanel nor the log give great clues where to look.
Examples:
In this first example, my phone is hooked to the charger during the night, and the alarm clock is running (hence the steady 10% cpu load). As soon as the phone is disconnected, cpu drops to low levels. On the exact minute i leave home, cpu rockets. And yes,i arrived at work around 07:50.
Home environment:
- connected to wifi
- good 3G coverage
- 3G, Bluetooth,GPS enabled
- no Bluetooth profiles present
Work environment
- wifi network present but not connected
- average 3G coverage
In this second example, i'm at work, hardly using the phone. Without touching the phone, stepping into my car and driving off, the cpu kicks in again. Notice there is no Device Usage whatsoever at the moment the CPU climbs. Bluetooth profiles active at this point and paired & connected to the carkit.
This last screenshot shows the typical clues (or lack thereof) that SystemPanel shows: just the System process using the most CPU.
Also the logcat doesn't provide much clues (or too many maybe) either. I have found that some applications couldn't contact GoogleAnalystics because i have AdFree installed, so i uninstalled those apps.
Frankly, i don't know where took look further. The damn android 'System'process just doesn't give enough clues. I have formatted internal & external SD, deleted cache & Dalvik cache, flashed & factory resetted to no avail. I'll try to have a log running tomorrow morning just before leaving the house to see if i can find what log entry corresponds to the system process kicking in. In the meantime, has anyone ever seen this behaviour, or any hints where to look?
Click to expand...
Click to collapse
i think you should go out and do some thing better with your life then watching what a battery uses

i think its a waste of space to quote WHALE post
and well if he got battery drained overnight it is important to determine why
it should not happend

Just a quick question, where is the phone when you are in the car? I have noticed that if I keep my phone in my trouser pocket while driving, I loose signal frequently, shown on Bluetooth unit, and over a 3hour journey I can loose 30% battery, but if I put the phone in my shirt pocket I do not loose signal and my battery loss is about 20%.
My theory is that the phone signal finds it easier to penetrate the glass windows of the car rather that the metalwork.

Similarly to Geryatrix, when I leave my phone beside my bed (=~~, best place for alarm), my battery drains because the phone stays with a very low network signal and keeps searching for better antennas, I guess. But then at "Battery Usage" I could see that "Cell Standby" was eating my bat, not the "Android System".

battery drains from wifi staying connected in idle state - thats a bug in my opinion from samsung - it should not use such ammount of energy
data connection in idle is almost unnoticable in battery use

When I had facebook 1.7.1 installed, "Android System" was consuming 20% battery.
After I uninstalled facebook 1.7.1 and the problem is gone, "Android System is back
to normal, about 4%.

got-petrol said:
i think you should go out and do some thing better with your life then watching what a battery uses
Click to expand...
Click to collapse
I think you should learn not to quote an entire long message for the sake of making 1 stupid remark
Start post will be updated in a few minutes with some new information.

seems like one of apps you use is trying to connect somewhere
have you made bugreport - i think you will find the culprit there

Have you tried disabling fast dormancy? Maybe these wakelocks are caused by incompatible 3g cell.
Use *#*#9900#*#* to find option to disable it.
Sent from my GT-I9000 using xda premium

$omator said:
think please
Click to expand...
Click to collapse
No comment...
Sent from my GT-I9000 using xda premium

wingg said:
No comment...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
and what is your problem to start oftop whining?
use report button if you do not like my post or tone of it
and freezing/deleting apps is not and never will be an issue solver
system works perfect with none of stock apps touched
using memory killers and altering system with such freeze options
is on the other hand source of 9 on 10 problems

$omator said:
battery drains from wifi staying connected in idle state - thats a bug in my opinion from samsung - it should not use such ammount of energy
data connection in idle is almost unnoticable in battery use
Click to expand...
Click to collapse
Hi,
I have opposite experience. Keeping Wifi enabled causes almost no battery drain for me, keeping 3G enabled does big time. My Galaxy Tab 10.1 Wifi version is set to never let the wifi connection sleep, and still battery drains no more than 1% or 2% a day is the tablet is not used.
I tested today with Wifi disabled. Still the Enter Dormancy messages appear each 5 seconds, altough the CPU hit is less. The Fast Dormacy messages seem purely cell-tower related, and wifi-unrelated. The Dormancy messages start as soon as i start moving, and stop when i'm home. I will update the startpost agan tonight.
---------- Post added at 06:55 PM ---------- Previous post was at 06:52 PM ----------
Kurre said:
Have you tried disabling fast dormancy? Maybe these wakelocks are caused by incompatible 3g cell.
Use *#*#9900#*#* to find option to disable it.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Hi,
I entered this Sysdump menu, the button read ""Enable Fast Dormancy" so i guess that means it was disabled all along. I enabled fast dormancy and will continue to test.

GPS drains battery!

Here is my findings about battery drain caused by gps.
If I turn on gps and then open any app that use gps (iGO and GPS TEST in my case) it works as it should. But problem is when I turn off gps (and close apps) phone can't go to standby mode and it has high battery consumption about 3-6 % per hour.
I noticed that in this situation if I want to unlock my phone, i can activate screen by pressing back button (it should be activated with middle button and power button, only).
If I turn on gps, again, battery drain stops, and it seems there is no battery drain untill I turn it off, again.
I tested this with two roms: GC 8.5 and aticmv2, both with naa08b kernel.
Please let me know Do You guys have this problem, too.
If not, let me know which rom/kernel do You use.

I have the same issue with GingerDx v020 , when i turn gps on and after a while i turn it off it still drains battery so i need to restart the phone to fix that.I dont know if there is any permanent fix .

I guess this is the same on all roms.
By the way, I tested battery life when gps is turned on (but not used by any application) and it seems that it doesn't consume battery at all. after 3h it was 1% consumption in standby.
So, I will left gps turned on all the time, rather than restart phone everytime I use navigation.

Nlpwakelock causing device to stay awake

Google services is to battery consumer because it keeps phone awake. Something to do with location services causing it based on screenshot below. I'm latest nightly CM and seems to be the only one affected by this issue since nobody else complained about it
Sent from my SGH-I337 using Tapatalk 4 Beta

Same crap here as well. As u can see I'm on a totally different device. There was another thread on it with no solution I think.
---Sent from a viperx-ed OneX

Turn network location off. You really don't need it on all the time. That's the only way I know of getting rid of that wake lock.

I just realized. Location reporting turned itself back on, on maps app
I turned it back off. Will see if that helps.
When it was off I'd probably get 1min of that wakelock for the entire day.
---Sent from a viperx-ed OneX

mibtnt said:
I just realized. Location reporting turned itself back on, on maps app
I turned it back off. Will see if that helps.
When it was off I'd probably get 1min of that wakelock for the entire day.
---Sent from a viperx-ed OneX
Click to expand...
Click to collapse
If its of from boot, I don't get any.

jd1639 said:
Turn network location off. You really don't need it on all the time. That's the only way I know of getting rid of that wake lock.
Click to expand...
Click to collapse
x-actly.
NLP stands for Network Location Provider I would guess as it appeared to me first when Google Location Services asked me to switch on the WLAN location detection for "more accurate results".
Might be helpful if in some building where you don't get GPS locked but isn't really needed that much otherwise.

i have location access OFF and have HUGE DRAIN on Nlpwakelock

I had a similar problem on my Nexus4 - after I turned location services on and off again, the NlpWakelock would keep my phone awake and not go to deep sleep.
However, I found a fix for this issue. The culprit service is called GoogleLocationManagerService, and the solution is to disable this service only (I have no idea what other complications may arise from this, but at least my phone now goes to deep sleep). This service can be disabled with ROM Toolbox or a similar app.
In ROM Toolbox you go to App Manager, find Google Play Services and select Advanced Freeze. Now find the service (has a red border) called GoogleLocationManagerService and disable it. Now I can switch on and off location and still go to deep sleep, and location IS working.

ameinild said:
I had a similar problem on my Nexus4 - after I turned location services on and off again, the NlpWakelock would keep my phone awake and not go to deep sleep.
However, I found a fix for this issue. The culprit service is called GoogleLocationManagerService, and the solution is to disable this service only (I have no idea what other complications may arise from this, but at least my phone now goes to deep sleep). This service can be disabled with ROM Toolbox or a similar app.
In ROM Toolbox you go to App Manager, find Google Play Services and select Advanced Freeze. Now find the service (has a red border) called GoogleLocationManagerService and disable it. Now I can switch on and off location and still go to deep sleep, and location IS working.
Click to expand...
Click to collapse
i've been searching for a solution for ages and even followed the advice of another thread to disable location finding on both maps and google now and for some reason the nlpwakelock is still showing up. i'm going to try your fix but i was wondering if you've encountered any issues ever since disable googlelocationmanagerservice?

I often noticed nlpwakelock being the main culprit for Google Services battery usage. I even saw that it kept my phone awake for hours some days...
I tested some fixes and found that disabling the "use wireless networks" in the location services settings completely removed that wakelock.
Personally, I'd rather have that feature than save the little battery it uses. Despite keeping my phone awake for 1-2 hours on most days, as reported by GSAM Battery Monitor and Wakelock Detector, it uses a pretty small amount of battery:
Typically my phone's battery monitor will report about 20-30% of the battery used by Google Services. GSAM Battery Monitor seems to break that down into two parts: about 10% Google Services and 15% kernel, on average. However, these numbers are deceiving. That 10% that Google Services is only 10% of "App Usage" as reported by GSAM. Furthermore, App Usage is often only about 50% of my battery usage.
If my battery is at 50%, that means Apps only usage 50% * 50% = 25% of my 100% battery. Then, Google Services only used 10% of that 25%...so 2.5% of my overall battery capacity. I found this quite surprising considering the report that the wakelock keeps my phone awake for 1-2 hours...
So while Google Services is often shown as my #1 or #2 battery user in the App Sucker page, at 10-15% usually, that's only like 2-5% of the total 100% battery capacity each day. If I'm really going to be pushing my battery limits I might disable it to save some juice, but generally I find it's not worth disabling the feature to save such a small portion of my battery.

ender127 said:
i've been searching for a solution for ages and even followed the advice of another thread to disable location finding on both maps and google now and for some reason the nlpwakelock is still showing up. i'm going to try your fix but i was wondering if you've encountered any issues ever since disable googlelocationmanagerservice?
Click to expand...
Click to collapse
Hi. No, I've not had any issues,*but unfortunately the fix doesn't always work - but if the wakelock still persists, shutting down the service or location service again removes the wakelock, but it takes the manuel action of re-disabling the service again. Still better than having a wakelock though..

Terrible battery life? What gives?

Hey guys...
Just here to say that I unplugged this phone at around 5 in the morning, and around 5 hours later its already down to 74%.
What did I do? Only about 10 minutes of mobile hotspot, a 2 minute phone call, and three text messages. The rest just idling...
1/4th of my battery life for just that?
What the heck?
Everything is disabled and the screen brightness is low... Whats the matter with this phone?

Looks like something is keeping your device awake.
Can you please add some screenshots of your battery graph?
In addition, you can try to boot into safe mode. If your problem is gone in safe mode, a third party app is interfering.

If you're rooted, try installing Wakelock detector or BBS (Better Battery Stats) and check out what is waking up your device.

If you use Gas Buddy, it was known to be causing massive bluetooth wakelocks. Either uninstall it or update it to the latest version.
Set your wifi to 2.4 ghz only. On 6.0 and 6.0.1, the 5 ghz band has been causing abnormal battery drain and keeping phones from entering doze mode. Here's the issue being reported: https://code.google.com/p/android/issues/detail?id=197460
If neither of these make a big improvement, you'll have to use your battery stats (and if rooted, use Better Battery Stats or Wakelock Detector) to specifically see what's keeping the phone awake. In either of these apps, filter the view by "Alarms" or "wakeup triggers" and you'll see what the heavy hitters are.
Be sure to go into Location>Settings and turn off wifi and bluetooth scanning.

Hi.the maps app isvuding WiFi and gps even though both are disabled and I'm not using it... Any ideas?