A quick search turns up the same question for different devices. Most the answers dealt with rooted devices, mine is not. The screen will fire up on its own, randomly. I do have Greenify and grant certain apps to close once the screen is off. That doesn't appear to be my issue. No apps are running (well, no apps that aren't system). It's a strange occurrence that drains battery because I have screen off set to 10 minutes. How do I determine what is triggering wakes? Anybody else notice this, I can't be the only one? Samsung issue or Android O/S issue?
My fiance has the same issue, mine doesn't. If you move the phone it wakes.
Related
Any idea why my replacement GNex reboots randomly, many times a day? It will be sitting in my pocket, screen off, and I will feel it vibrate. Look at the phone, it's at the Google logo rebooting. Also, if I'm outside on cell data, streaming music with the screen off, it will die in a few minutes.
I did some digging and someone said there is a location bug in 4.2.2, and it is causing certain GNexs to act like this. This morning I shut off all location services and disabled Google Now. My phone lasted the whole day without a single reset, and I was able to stream music.
Is anyone aware of a fix for this? It seems to be an issue on my phone in stock 4.2.2, stock+franco kernel, and CM 10.1.
Thanks!
Hey all, so I'm having a very annoying and strange issue: My Moto 360 will wake up (i.e. screen turns on) randomly and without reason, ranging from within seconds of each wake to minutes, but it absolutely kills the battery (I can't make it more than 10-12 hours with absolute minimal usage). This is with tilt to wake off, theater mode on, all possible apps except the Android Wear app uninstalled. and the watch sitting completely still on a table. It was happening with Android 5.1 and 5.1.1 on my Nexus 6, and is still happening with the recent 5.1.1 Android Wear update.
The only way to "fix" the waking up issue is if I turn on airplane mode on my phone, which obviously disconnects the watch. So clearly my Nexus 6 is waking up the watch remotely, be it through the AW app or through the connection itself somehow. One other note: when I reset the watch and pair it with my 2013 Nexus 7, the issue doesn't occur, so clearly it's not a problem with the watch's hardware or software, but with the way the Nexus 6 communicates with the watch.
Really would appreciate any insight or guidance as to what's going on - I'm truly at a loss, and the only explanation I can possibly come up with is an issue with my phone's internal hardware (maybe something bluetooth-related)? I've even reset my phone on multiple occasions and that won't fix it.
The only other reference on the internet I can find to this issue is here, where this guy seems to be having the same problem, albeit with a different Mororola-produced phone: https://productforums.google.com/forum/#!topic/android-wear/5vB-dKc5IGI.
Searched the forum and did some google searches but only came up with one thread somewhere else that never went anywhere. This may be glitchy apps (although I have both on my Droid Maxx as well with no issues) but I thought I'd ask anyway.
So the problem is the tablet(SM-T700, Android 5.02) will seemingly go to sleep while actively using an app (so far it's common in 8 Ball Pool and has also happened during Beach Buggy). I don't know if it's app related or a setting somewhere. I have power saving modes turned off (as well as auto screen brightness). Anyone else experience this?
Well it may be a combination of the app not telling the screen to stay on (twitch app had this issue for about 3 days then it got an update) any you having the auto screen off timer set too short.
The permission used is under others and is called quite simply (prevent tablet sleeping). With out that mode set if you do not touch the screen in (insert screen shutoff timer length here) the tablet will turn the screen off to save power.
Thanks, I'll check that out. I'm going to run a few more apps and see if it happens with them also.
So lately I've been noticing my phone hasn't been locking when it should be and while my phone was sitting next to me I watched the display turn on and off twice within ~45 seconds by itself.
Haven't changed any settings and this had never occurred/been a problem before.
Already cleared cache in recovery no help.
Any help would be appreciated thanks!
Mine does this as well because I have greenify installed, if you look very closely after it turns the screen on, you can see that it's force closing apps, but it turns the brightness all the way down while it does this. If you don't have greenify installed then I am not sure what might be causing your phone to do this.
Dear Experts,
Long time lurker here.
I'm currently in a dispute with the dealer on whether or not the Samsung Galaxy Note 2 i bought has a hardware or software issue. If it's a hardware issue it can be repaired under warranty. The device is completely stock with no modifications what so ever, as well as no root access. If you can help me provide a sufficient explanation of why it's a hardware related issue, perhaps I do not need to purchase a brand new phone, and hopefully it could help others with similar issues.
The issue arises when the phone is under heavy load and the screen is turned off. This normally seems to happen when the phone has multiple applications running background processes at the same time while updating applications (usually when the device has been left alone for a while). The device will then crash/freeze (i.e. screen will remain off and no response on any buttons). The only way to fix this is to hard reset the phone, by either long hold the power button, or pop out the battery. It will continue to drain power and heat up in this "frozen" state, as if it is still under load, until the battery dies.
The issue will persist after doing factory resets. However, the symptoms will not occur unless it has been used actively for a while (i.e. installing apps, enabling background updates etc.). This makes it harder to replicate the issue. However the symptoms can be seemingly replicated by using Stability Test 2.7 (a stress/burn-in test available on the Play Store), buy running the Classic Stability Test (CPU/RAM) and then turn the screen off for about 20-60sec, where it will crash. The issue will not occur when running heavy loads when the screen is turned on (i.e. when using it).
From my uninformed perspective, I suspect there could be an issue with a memory component of the device, as this only occurs when the screen is turned off. Which would probably mean that (I assume) the "snapshot" of the devices' current state, which the phone saves when turning off the screen, is somehow bugged because of heavy load, and thus crashes the device. Hopefully you could make a better sense of it than me.
Yours sincerely