My screen randomly turns on and sits at the lock screen for a few seconds for no apparent reason. There are no pending notifications, etc. I assume there might be a rogue app causing this, but I don't have that many installed and even less apps doing any background tasks. Any idea on how to find the culprit?
I found this bug report where some apps are mentioned, but I'm not running any of them.
https://code.google.com/p/android/issues/detail?id=39625
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
I noticed that the phone wakes up whenever it reconnects to Wi-Fi. I was changing some router settings last night and I constantly saw the phone waking up shortly after the router rebooted. However, this is not the only scenario where it does it.
Mine has done the same, no idea why, only seen it the once, but it certainly happened, sitting three feet away from me, and suddenly Bingo! its on.
Mine wakes every few minutes. Certain apps (tasker, facebook etc) and syncing seem to cause it to happen more often but even if I disable most apps it still happens. I've been unable to identify the source with better battery stats. It happens bone stock and on CM10.1. I'm still getting better battery life than my GNexus but it's maddening.
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
ludovicien said:
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
Click to expand...
Click to collapse
So my Nexus 4 doesn't want to go to sleep.
- I have sleep set to 15 seconds
- Dream is off (just in case)
It just stays on. It doesn't matter if it's on the the lock screen or at the home screen. I'm guessing some app is keeping it awake. It just started last night, but I don't think I have installed any new apps. Maybe it from an update.
solved
My phone's screen also used to wake up randomly. it was very annoying, especially at midnight
finally, I found out the reason by using "Wakelock detector" app which is freely available in market.
here is XDA thread about WLD: WLD at XDA Thread
the cause of problem was ad Notification, it was holding "full wakelock" (you can see it in screenshot)
good Luck!
Refer Wakelock Detector at XDA
Ramdom screen wake up issue solved
Dear all,
I was experiencing random screen wake issue in my XOLO PLAY smartphone.
The problem was with the AppLock software. After upate is this issue appreard. Earlier AppLock was there and no issue was experienced.
I am writing to AppLock team to fix the bug.
:angel:
All the best
Regards
nitin5062
hcedillo said:
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
Click to expand...
Click to collapse
U made an account to post THIS only?
I have the screen off, and every 15 or 20 minutes, the screen will turn back on to the lock screen until the sleep timer goes off again. How can I figure out what this is? I thought it was a lock widget updating (Agenda Widget) but even with no lock widgets it sometimes comes back on. I thought it was location services from some app (Prey, etc.) because sometimes immediately upon wake there's a little location notification icon but I turned that off and no help. Sometimes there's a Gmail icon, but I've tested it where I clear all my notifications, and then on my laptop, I send an email and I get the audio notification, but no wakeup. I'm stumped and it's quite annoying, can anybody help?
I do think it's location-based. I've turned off location pinging in as many apps as I can see (Prey, FB, etc.) even though global location was already off and now it's about once every 40 minutes that it wakes on its own.
anybody?
I would download https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats
If you don't want to buy it (and I really recommend you do) search on this forum about how to fix partial wake locks. There's a lot of info on how to fix this.
dmot7291 said:
I would download
If you don't want to buy it (and I really recommend you do) search on this forum about how to fix partial wake locks. There's a lot of info on how to fix this.
Click to expand...
Click to collapse
Thanks, I have that installed now, and am monitoring, I'll update with more info later, but thanks for the lead. I'm supposed to be looking for partial wakelocks since unplugged, right?
So I get these wakelocks for some reason, about 2-10 minutes of Audioout_2 and Audioout_3 per hour when idle, with screen off.
And they seem to show up as wakelocks, even if I have my phone active. So I get like 47minutes of this wakelock, but awake time is 56:27minutes and screen on 54 minutes. And this is not the problem until you see how much of this wakelock has kept your phone awake after 24 hours, I had like 3-5 hours. Should I be worried?
APP - Wakelock Detector, BetterBatteryStats.
What I have tried - Uninstalling Viber, no difference. Disabling all lock sounds, touch sounds, dial pad tones, not much difference either.
I didn't have this before, what could it be?
Android 4.3 Stock, not rooted
I seem to be having the same issue. I'm running on stock 4.3, no rooting, I do not have Viber, and while I do have Skype installed, I almost never use it. I have haptic feedback disabled as well as touch sounds.
Rebooting the phone seems to fix the issue, but that's obviously a bit of a pain to do every time.
Other than maybe blaming Poweramp for keeping the wakelock going, I can't think of any other apps that could be causing the issue.
apu95 said:
I seem to be having the same issue. I'm running on stock 4.3, no rooting, I do not have Viber, and while I do have Skype installed, I almost never use it. I have haptic feedback disabled as well as touch sounds.
Rebooting the phone seems to fix the issue, but that's obviously a bit of a pain to do every time.
Other than maybe blaming Poweramp for keeping the wakelock going, I can't think of any other apps that could be causing the issue.
Click to expand...
Click to collapse
After you reboot when does the issue seem to come back? What apps are you usually using?
Do you have any of these apps - Light Manager, DashClock Widget, Smart Wifi toggler.*
*These apps have no deal with audio wakelocks whatsoever, but still, maybe 4.3 has caused one of those apps to use the audio wakelocks somehow.
Yukicore said:
After you reboot when does the issue seem to come back? What apps are you usually using?
Do you have any of these apps - Light Manager, DashClock Widget, Smart Wifi toggler.*
*These apps have no deal with audio wakelocks whatsoever, but still, maybe 4.3 has caused one of those apps to use the audio wakelocks somehow.
Click to expand...
Click to collapse
My main apps are Gmail, Chrome, Facebook, Twitter, BaconReader and Poweramp. After rebooting the length of the wakelock time definitely isn't as long. And yes, I do have DashClock Widget. I didn't consider that one to be a potential culprit.
Yukicore said:
So I get these wakelocks for some reason, about 2-10 minutes of Audioout_2 and Audioout_3 per hour when idle, with screen off.
And they seem to show up as wakelocks, even if I have my phone active. So I get like 47minutes of this wakelock, but awake time is 56:27minutes and screen on 54 minutes. And this is not the problem until you see how much of this wakelock has kept your phone awake after 24 hours, I had like 3-5 hours. Should I be worried?
APP - Wakelock Detector, BetterBatteryStats.
What I have tried - Uninstalling Viber, no difference. Disabling all lock sounds, touch sounds, dial pad tones, not much difference either.
I didn't have this before, what could it be?
Android 4.3 Stock, not rooted
Click to expand...
Click to collapse
I have the same problem.
I noticed that audioout_2 only runs when my screen is on.(most of the time)
The audioout_2 run time and SOT are always close.
The audioout_2 and audioout_3 will not run (very minimum) when your cell goes into deep sleep.
I have mostly Google apps installed.
Edit: After searching on internet,Many users told these wakelocks can be caused if there is a corrupted mediafile (picture,music,video)..
Need a solution for this.
l33ttroll said:
I have the same problem.
I noticed that audioout_2 only runs when my screen is on.(most of the time)
The audioout_2 run time and SOT are always close.
The audioout_2 and audioout_3 will not run (very minimum) when your cell goes into deep sleep.
I have mostly Google apps installed.
Edit: After searching on internet,Many users told these wakelocks can be caused if there is a corrupted mediafile (picture,music,video)..
Need a solution for this.
Click to expand...
Click to collapse
What do you mean corrupted mediafile, like unsupported MP3 file? Could that be a problem? God dammit, this is too complicated.
I have only a few pictures that I have taken with the phone, no videos. Only music could be related.
So I yesterday turned on location services, the results I got were pretty bad. I am not 100% sure that the issue is location services, but I did not have this bad screen_on - awake ratio before. Here are some screens.
I didn't do anything unusual, I might report back tomorrow about results w/o location services.
I left only GPS setting active in location settings. Here are the results.
6hours phone on, Battery left 87%.
55:31min awake, 38min screen on.
1013 wakelock usage 32:12min.
I played a few games, made some calls for the time when screen was awake.
I would call this a success, because usually I could barely make through a day, almost 3hours screen on in 12hour period. And the battery is dead.
Yukicore said:
I left only GPS setting active in location settings. Here are the results.
6hours phone on, Battery left 87%.
55:31min awake, 38min screen on.
1013 wakelock usage 32:12min.
I played a few games, made some calls for the time when screen was awake.
I would call this a success, because usually I could barely make through a day, almost 3hours screen on in 12hour period. And the battery is dead.
Click to expand...
Click to collapse
What was your solution? So far my current one is to reboot when I wake up in the morning.
apu95 said:
What was your solution? So far my current one is to reboot when I wake up in the morning.
Click to expand...
Click to collapse
I disabled Wi-Fi & mobile network location in Location access settings. But I am not entirely sure that this is a solution.
I am very confused with all this Android and Nexus 4 problem amount and uncertainty, I am not even sure what to believe anymore. I am starting to wish I had bought an iPhone. Maybe it was because I was at just at home and in a city mainly, and the cellphone just didn't have to look for different cell towers, I am not sure what should I even think anymore.
But currently this has helped me, I guess. Disadvantages of this might be that the phone will not be able to select the best server available when indoors... I'm just so tired of Android.
I can't shake off this stupid wakelock, it keeps my phone awake, Android is soo annoying, I would probably never notice this if it weren't for the battery usage apps, but I would notice the horrible battery life on Nexus 4.
Has anyone had this problem and made it go away? Or is still having, and just got through with it and ignores it? Please help me!
I think I had 0 amount of this wakelock in the first few days I got these battery status apps, I had only a few Media, Caldendar, Gmail etc. wakelocks
The wakelocks are caused by the touch sounds that are enabled by default.
Everytime you touch a button on your phone it will make a sound, which will initiate the wakelock. Turn off these sounds in:
Settings -> Sound -> Touch Sound
You can also 'hear' the wakelock, because when you hold the back speaker of the phone to your ear when a sound was just played, you will hear some static noise for ~2-3 seconds after the sound finished playing.
When you listen to music or watching a video you will also get these wakelocks, but that's completely normal.
Sent from my Nexus 4 using xda app-developers app
mumaster20 said:
The wakelocks are caused by the touch sounds that are enabled by default.
Everytime you touch a button on your phone it will make a sound, which will initiate the wakelock. Turn off these sounds in:
Settings -> Sound -> Touch Sound
You can also 'hear' the wakelock, because when you hold the back speaker of the phone to your ear when a sound was just played, you will hear some static noise for ~2-3 seconds after the sound finished playing.
When you listen to music or watching a video you will also get these wakelocks, but that's completely normal.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
+1 to that
Even if u have ur dialpad to sound off. Go ahead and type numbers in like crazy then check the wakelocks!
Even if u have turned that option to OFF.
Sent from my Nexus 4 using XDA Premium 4 mobile app
WasifSal said:
+1 to that
Even if u have ur dialpad to sound off. Go ahead and type numbers in like crazy then check the wakelocks!
Even if u have turned that option to OFF.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Right, did You have that before? Or it just turned up recently, I don't remember having this much wakelocks, and why are ''wakelocks'' wakelocks when you are using your phone and the screen is on?
I noticed that if I don't have internet access, the wakelock doesn't come up as much. It's some kind of app, maybe, it very much could be one of Google's, It ain't Viber (for me), I have tried disabling, turning it off, no change in wakelock amount.
Yukicore said:
Right, did You have that before? Or it just turned up recently, I don't remember having this much wakelocks, and why are ''wakelocks'' wakelocks when you are using your phone and the screen is on?
I noticed that if I don't have internet access, the wakelock doesn't come up as much. It's some kind of app, maybe, it very much could be one of Google's, It ain't Viber (for me), I have tried disabling, turning it off, no change in wakelock amount.
Click to expand...
Click to collapse
I just checked that now
To be honest i'm in the same condition u are in. I don't know whats causing these. Try greenifying Google+, Google Now etc. They have helped me a bit in saving some... Google+ updates/syncs, and that makes a wakelock as well.
Sent from my Nexus 4 using XDA Premium 4 mobile app
WasifSal said:
I just checked that now
To be honest i'm in the same condition u are in. I don't know whats causing these. Try greenifying Google+, Google Now etc. They have helped me a bit in saving some... Google+ updates/syncs, and that makes a wakelock as well.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have set syncing and updating google apps to the minimum already. Google Now is not active.
Does other android phones like Galaxy S3, S4, HTC One also have this bad battery life, or is it Nexus 4 specific?
apu95 said:
What was your solution? So far my current one is to reboot when I wake up in the morning.
Click to expand...
Click to collapse
Do You have Flash Player installed on Your Android device?
This is really weird, I restart the phone, use gmail, and some other apps, turn off screen, check for wake locks, no Audio wake lock at all, I open Chrome, use it a little and then check for wake locks and it has appeared and is at at the top, also other wakelocks have increased count.
Also another matter, I notice a little pop in the speakers sometimes, even though I have set to vibrate only mode.
EVERY TIME I TOUCH THE SCREEN THE SPEAKER TURNS ON, it is just quietly hissing, you need to be in complete silence to hear this. This is definitely causing a big battery drain, I need to fix this ASAP. Anyone has a clue?
Turned off touch sounds, hissing has disappeared. But it literally started hissing after I press anywhere on the screen, even though only a few buttons make a touch sound.
Got to stop typing now, my hands are burning when I'm using Google chrome on my nexus 4...
I disabled Google+ Notifications through Google+(app) > Settings > google account > notifications
And I turned off all Sounds, from Dial pad touch tones to screen lock sound and vibrate on touch. Now I had tried this before the Google+, but I still had the issue with the wakelock.
I get little to none of this wakelock, also turned off google+ backup feature. Disabled some sync options in google account.
But basically I get a lot less of this wakelock now, I am not entirely sure it was Google+, but I have been using the phone casually, as usual for 30+ Hours, charged once, and I get better battery life and much less of this wake lock, phone is mostly in sleep mode when screen is off, about 1-4 Minutes awake.
Now I don't guarantee anything, maybe it's some service that didn't start up this time, but I'm pretty sure that I had opened every app that I was using when I had the problem, this seems to have fixed the problem, see if it helps, if you are experiencing the same issue, and please let me know, thanks!
Oh and I have been using the phone's speaker indeed, for games, Youtube app, Chrome etc. and Received calls, messages, notifications.
Any solution? I'm still having this 1013 wakelock without apparent cause..
Hello!
I'm running a stock Verizon HTC 10 with the latest OTA updates. This phone seems to have a problem with push notifications after it has been "sleeping" or idle for awhile. I don't know exactly what that time period is, but it seems to be about 30 minutes. Once the screen goes black and the phone has been idle in this state for this time period, the phone stops getting (or checking for-however that works) push notifications. There is no blinking LED or sound notification that mail has come for gmail or Outlook. The phone will still answer calls and notify upon receipt of text messages. Usually within a few seconds of turning the screen on from the idle state, the gmail and Outlook notifications come. When the phone screen is on, or within a few minutes of turning the screen off, the push notifications will still come, but then stop.
I googled about this, and there seems to be quite a bit of discussion about it. I have tried the suggested remedies, but they don't work (unsync/sync gmail, clear data/cache for the apps, turn battery optimization off, delete/re-add accounts, along with some others). For work, I have a Samsung Galaxy S7, and it doesn't have this problem. Furthermore, my wife also has an HTC 10, and her phone doesn't seem to have the problem either (although I have not tested it thoroughly).
I've been through various settings, checked the do not disturb settings, but I can't seem to figure this out. I am probably missing some setting. It seems that the phone is going into some deep sleep mode after a period of time and disabling these apps, but keeping others, like the phone and SMS functions, alive.
Any suggestions?
Thanks!
jbhtexas said:
Hello!
I'm running a stock Verizon HTC 10 with the latest OTA updates. This phone seems to have a problem with push notifications after it has been "sleeping" or idle for awhile. I don't know exactly what that time period is, but it seems to be about 30 minutes. Once the screen goes black and the phone has been idle in this state for this time period, the phone stops getting (or checking for-however that works) push notifications. There is no blinking LED or sound notification that mail has come for gmail or Outlook. The phone will still answer calls and notify upon receipt of text messages. Usually within a few seconds of turning the screen on from the idle state, the gmail and Outlook notifications come. When the phone screen is on, or within a few minutes of turning the screen off, the push notifications will still come, but then stop.
I googled about this, and there seems to be quite a bit of discussion about it. I have tried the suggested remedies, but they don't work (unsync/sync gmail, clear data/cache for the apps, turn battery optimization off, delete/re-add accounts, along with some others). For work, I have a Samsung Galaxy S7, and it doesn't have this problem. Furthermore, my wife also has an HTC 10, and her phone doesn't seem to have the problem either (although I have not tested it thoroughly).
I've been through various settings, checked the do not disturb settings, but I can't seem to figure this out. I am probably missing some setting. It seems that the phone is going into some deep sleep mode after a period of time and disabling these apps, but keeping others, like the phone and SMS functions, alive.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Are you using power saver mode? What about the boost+ app?
Also a lot of people started having similar issues after the first update to Nougat for U.S Unlocked. Later updates fixed the issue, but it sometimes still happening with Gmail for me.
Tarima said:
Are you using power saver mode? What about the boost+ app?
Also a lot of people started having similar issues after the first update to Nougat for U.S Unlocked. Later updates fixed the issue, but it sometimes still happening with Gmail for me.
Click to expand...
Click to collapse
I am not using power saver mode, and the Verizon version doesn't have the boost+ app installed.
Has anyone else experienced sporadic notifications since updating to 8.1? Unrooted, and ever since the update, my notifications will only vibrate when the screen is off, but will go audible if the screens on.... or ill get a few hours of normal functionality, then back to whatever it wants to do... Ill get delayed text notifications or even doubling them up. Ive never had this issue before. Any help or direction would be greatly appreciated
Lemmiwinx said:
Has anyone else experienced sporadic notifications since updating to 8.1? Unrooted, and ever since the update, my notifications will only vibrate when the screen is off, but will go audible if the screens on.... or ill get a few hours of normal functionality, then back to whatever it wants to do... Ill get delayed text notifications or even doubling them up. Ive never had this issue before. Any help or direction would be greatly appreciated
Click to expand...
Click to collapse
I have the same issue. Orea 8.1 unrooted.
Have you tried removing the apps that need immediate notifications from battery optimization? Oreo is more aggressive stopping the background activity of apps than Nougat was. it's an intentional battery saving feature.
Lemmiwinx said:
Has anyone else experienced sporadic notifications since updating to 8.1? Unrooted, and ever since the update, my notifications will only vibrate when the screen is off, but will go audible if the screens on.... or ill get a few hours of normal functionality, then back to whatever it wants to do... Ill get delayed text notifications or even doubling them up. Ive never had this issue before. Any help or direction would be greatly appreciated
Click to expand...
Click to collapse
I've noticed this too, and literally just came on XDA to post this same question!!
It seems to take away notification sounds for most apps until I restart the phone. Based on the timing, maybe it has to do with going into a deeper sleep mode or something. Seems more like a glitch than a feature to me, since the notifications don't come back until I restart.
I'll try the battery optimization thing mentioned above, but I don't want WhatsApp draining my battery.
jhs39 said:
Have you tried removing the apps that need immediate notifications from battery optimization? Oreo is more aggressive stopping the background activity of apps than Nougat was. it's an intentional battery saving feature.
Click to expand...
Click to collapse
Good tip, Thanks. I was unaware they automatically optimized the apps for battery in the update. what a pain in the a$$. Ive changed the setting for messenger and telegram, Ill report back if i see an improvement.
Hmmm. I changed my battery optimization do exclude Google Voice and Android Messages... it worked for a small amount of time, now I just get vibration, but no sound for notifications.
Oreo 8.1 release.
Rick
I was using Nova Launcher when I had this issue. I switched to the default launcher and haven't had the issue since.
priyamjani said:
I was using Nova Launcher when I had this issue. I switched to the default launcher and haven't had the issue since.
Click to expand...
Click to collapse
The hero we needed