When I have my phone plugged in over night and then hit the unlock screen button, the screen doesn't turn on.
I have to hard reset to get the phone on then everything is fine.
What is causing this and how do i stop it?
Running totally stock rom 4.3
Which apps do u have installed on your Nexus? I saw the freezing issue with touch control. If U had no apps it could have just been a bad flash
Have you got any overclocking apps?
Sent from my Nexus 4 using Tapatalk 4
I have been dealing with this for a while. It has made me late to work since I use my phone as my alarm and the alarm does not go off when this occurs. I've tried everything. Toggled daydream mode to ensure it was off, done a factory reset and installed no apps, done a full factory image flash to make sure there was no issue with the system files, tried a different charger, tried not charging, etc... it still occurs about once a week. I plan to call Google to ask if this is a warranty issue.
kthejoker20 said:
When I have my phone plugged in over night and then hit the unlock screen button, the screen doesn't turn on.
I have to hard reset to get the phone on then everything is fine.
What is causing this and how do i stop it?
Running totally stock rom 4.3
Click to expand...
Click to collapse
Download and install Safe Charge from Google Play https://play.google.com/store/apps/details?id=com.sash.sodeliminator. Open Safe Charge after installing the app and click the Enable Safe Charge check box. The developer has an explanation at http://forum.xda-developers.com/showthread.php?t=2226698 of how his app prevents the Nexus from entering deep sleep while the phone is plugged in. I installed his app after experiencing two sleep of death episodes in my first week with the Nexus and have not had one since.
I tracked it down that it only happens when wifi is enabled. When it's not enabled the phone doesn't freeze.
Try disabling location access? Wifi might have connection with that. No harm trying right?
Wifi on at night isn't good for human deep sleep anyway so I off it.
Related
First of all, I'm running cyanogenmod version 10.1.0-RC2-mako on my Nexus 4 and the only app that I have on it with root privileges is AFWall+. I'm very careful about what I install on it from the android market, I don't have many apps on it anyway. I do have a call recorder app that runs while I am on the phone with someone (Auto Call Recorder). Basically what happened was, I got off the phone with my boss, and set my phone down. Then about 5 minutes later I picked it up and turned it on only to find out that it wasn't on. I tried to turn it on and it wouldn't do anything. Battery was more than 90% full. I plugged it in to my charger and tried to turn it on, it still wouldn't do anything. After about a minute the "battery charging" icon on the LCD appeared saying the battery was nearly full and at that point I was able to unplug the phone and turn it on. I only had it plugged in for about 2 minutes tops. It came on as it normally does after I unplugged it and turned it on.
My first thought was that it was a problem caused by the call recorder app, but I haven't had any problems with this app before (I've only been using the app for two weeks though). But if it was the call recorder app causing the problem, the phone would still have turned back on after I tried to turn it on, right? Also, how is it that the phone came on after I plugged it in to charge it and then unplugged it?
Has anyone seen similar problems with this? Should I change out ROMs? Delete the call recorder app? I glad I was able to get it back on, but I didn't like how there wasn't a reset button on it like I had on my HD2, Sensation, and other phones.
match417 said:
First of all, I'm running cyanogenmod version 10.1.0-RC2-mako on my Nexus 4 and the only app that I have on it with root privileges is AFWall+. I'm very careful about what I install on it from the android market, I don't have many apps on it anyway. I do have a call recorder app that runs while I am on the phone with someone (Auto Call Recorder). Basically what happened was, I got off the phone with my boss, and set my phone down. Then about 5 minutes later I picked it up and turned it on only to find out that it wasn't on. I tried to turn it on and it wouldn't do anything. Battery was more than 90% full. I plugged it in to my charger and tried to turn it on, it still wouldn't do anything. After about a minute the "battery charging" icon on the LCD appeared saying the battery was nearly full and at that point I was able to unplug the phone and turn it on. I only had it plugged in for about 2 minutes tops. It came on as it normally does after I unplugged it and turned it on.
My first thought was that it was a problem caused by the call recorder app, but I haven't had any problems with this app before (I've only been using the app for two weeks though). But if it was the call recorder app causing the problem, the phone would still have turned back on after I tried to turn it on, right? Also, how is it that the phone came on after I plugged it in to charge it and then unplugged it?
Has anyone seen similar problems with this? Should I change out ROMs? Delete the call recorder app? I glad I was able to get it back on, but I didn't like how there wasn't a reset button on it like I had on my HD2, Sensation, and other phones.
Click to expand...
Click to collapse
The app may not be compatible with android 4.2.2. The reboot can be done by holding the powerbutton for more than 10 seconds. There is also a safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl to be able to boot without 3rd party apps.
gee2012 said:
The app may not be compatible with android 4.2.2. The reboot can be done by holding the powerbutton for more than 10 seconds. There is also a safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl to be able to boot without 3rd party apps.
Click to expand...
Click to collapse
Thank you! ( I also clicked your "thanks" button). I can't say my question was completely answered, but it was definitely helpful. I didn't know there was a safe mode, very handy indeed! I don't believe any of my other phones have had a safe mode. I have seen other little problems with the app, like only recording my voice and not the other end, but no problems have shut off the phone before. I will check up on the app to see if it is compatible with 4.2.2 and also if it is on auto-update and if it updated itself recently. And I don't think I held the power button after the phone call, if I did it would have rebooted, unless somehow my protector case held the power button when the call ended and caused a glitch in the software since it couldn't store the recorded call.
match417 said:
Thank you! ( I also clicked your "thanks" button). I can't say my question was completely answered, but it was definitely helpful. I didn't know there was a safe mode, very handy indeed! I don't believe any of my other phones have had a safe mode. I have seen other little problems with the app, like only recording my voice and not the other end, but no problems have shut off the phone before. I will check up on the app to see if it is compatible with 4.2.2 and also if it is on auto-update and if it updated itself recently. And I don't think I held the power button after the phone call, if I did it would have rebooted, unless somehow my protector case held the power button when the call ended and caused a glitch in the software since it couldn't store the recorded call.
Click to expand...
Click to collapse
Look here for callrec. http://forum.xda-developers.com/showthread.php?t=1998812&page=8.
gee2012 said:
Look here for callrec. http://forum.xda-developers.com/showthread.php?t=1998812&page=8.
Click to expand...
Click to collapse
thanks again! But the problem I was talking about was with the internal mic on the Nexus 4. Sometimes it doesn't pick up the other end of the conversation but it records me fine. I don't use any external mics or bluetooths with it. The app seems pretty solid, both my voice and the other persons voice are pretty close in volume, which has been an issue with recorder apps that I have used in the past. Thanks though. Is there an application error log in the android or 3rd party software for an error log to help determine the cause of problems?
match417 said:
thanks again! But the problem I was talking about was with the internal mic on the Nexus 4. Sometimes it doesn't pick up the other end of the conversation but it records me fine. I don't use any external mics or bluetooths with it. The app seems pretty solid, both my voice and the other persons voice are pretty close in volume, which has been an issue with recorder apps that I have used in the past. Thanks though. Is there an application error log in the android or 3rd party software for an error log to help determine the cause of problems?
Click to expand...
Click to collapse
You can only make logs if you are rooted. There are several apps in Play available for that.
gee2012 said:
You can only make logs if you are rooted. There are several apps in Play available for that.
Click to expand...
Click to collapse
mine is rooted, I'll check that out. Thanks again!
For some reason my screen won't shut off when I press the power button or by itself after any amount of time. I made sure all of the settings were set right that might keep it on. I know it's not hardware damage because I've pretty much never dropped it or handled it hard. The power button still works because it will get the turn off, restart, etc screen to go. Any idea how to fix it? I already did a factory reset.
JollyGreen527 said:
For some reason my screen won't shut off when I press the power button or by itself after any amount of time. I made sure all of the settings were set right that might keep it on. I know it's not hardware damage because I've pretty much never dropped it or handled it hard. The power button still works because it will get the turn off, restart, etc screen to go. Any idea how to fix it? I already did a factory reset.
Click to expand...
Click to collapse
Dial *#0*# check some test for dimming, sleep etc.
JollyGreen527 said:
For some reason my screen won't shut off when I press the power button or by itself after any amount of time. I made sure all of the settings were set right that might keep it on. I know it's not hardware damage because I've pretty much never dropped it or handled it hard. The power button still works because it will get the turn off, restart, etc screen to go. Any idea how to fix it? I already did a factory reset.
Click to expand...
Click to collapse
Download wakelock detector and see which app is keeping your screen on.
Dialed that number, the dimming worked, but the sleep button didn't do anything. I'll try that app out and see what it says.
In my understanding *#0*# dialing is for hardware check, if sleep is not working from there means it has nothing to do with any app & better to take to service centre.
Sent from my SM-N9005 using XDA Free mobile app
It didn't do it until after I tried to change my boot screen. Know if that would do anything? No boot animations go off besides the galaxy note 3 one (no Tmobile or samsung animation, and no shut off animation). I also rooted it so would they still help me even though the knox counter is 0x1?
Any help? Using the wakelock app it says that system manager application is used a lot more than anything else. Not sure what it does.
JollyGreen527 said:
It didn't do it until after I tried to change my boot screen. Know if that would do anything? No boot animations go off besides the galaxy note 3 one (no Tmobile or samsung animation, and no shut off animation). I also rooted it so would they still help me even though the knox counter is 0x1?
Click to expand...
Click to collapse
Try to flash complete stock ROM & clear Data & Catch before & after flashing from recovery may HELP.
That fixed it. I'm not sure why I didn't already try that since it seems kinda obvious. Don't know what made it do that though. Do you happen to know if modifying the boot animations can mess other things up?
Mine its not rooted still stock and all of the sudden started acting up with the screen ....i did the *# test and when i went to sleep it went straight to the lock screen ...any idea what could cause it
help
JollyGreen527 said:
That fixed it. I'm not sure why I didn't already try that since it seems kinda obvious. Don't know what made it do that though. Do you happen to know if modifying the boot animations can mess other things up?
Click to expand...
Click to collapse
how do you do that cause I'm having same problem s
scooby 777 said:
how do you do that cause I'm having same problem s
Click to expand...
Click to collapse
Mine does this every time I reboot my phone. I have to press and hold the home key, pick the pie chart, pick RAM and pick "Clear Memory". Then it's fine til the next time I reboot.
I had my note 3 with the same problem and solved it recovering the original system/media/bootsamsung*.qmg files.
to solve the problem plug the charger and unplug it immediately and plug it back in again. This is also the reason why the problem is caused. So doing it again will solve the problem.
So, here's my issue: I started to notice that bluetooth audio, which was usually good, started to suddenly cut in and out. At the same time, my battery life went to pot, and the top battery sucker was the Bluetooth share. I also noticed that the phone got really hot and very slow when charging when all of this was happening (usually I don't have to worry about the phone getting super hot when charging and using bluetooth).
I installed BBS and GSAM, and they both basically told me that the phone was not going to sleep because the bluetooth share was keeping it away. I even tried installing Naptime, and the phone still refuses to go into deep sleep, and the bluetooth share keeps sucking battery.
So here's what I've done so far...
- Uninstalled recent apps, no change
- Clear Bluetooth share, restart phone, no change
- Unpair all bluetooth devices, no change
- Restart phone (several times), no change
- Start the phone in safe mode, phone behaves normally....
In the course of trying to figure out what's going on, I basically uninstalled every app and the bluetooth share was still keeping my phone awake.
The only way I've found that fixes this issue is to completely format the phone and reinstall stock firmware. And I don't mean just to fastboot flash system system.img, I mean I have to fastboot erase system and then flash the system in order for bluetooth to behave. After I do this, and reinstall all my usual apps (I allow Google to download them, then I use titanium backup to restore the data on apps that don't sync their own data), the phone works brilliantly for about a week and a half, then the ordeal starts all over again.
The only thing I haven't tried is going bone stock... when I reinstall my phone I root and put Frankenclar on it. I used to use Xposed, but I tried going without to see if that made a difference... and, nope. Even without Xposed the bluetooth share keeps the phone awake.
I've started going through the steps to contact Moto, but they may balk because I've unlocked my phone (even though the warranty says valid).
Any ideas??
Oh, I'm on Verizon, so my choice of roms are limited... and I really like the wake on approach, twist for camera, chop for flashlight, and being able to call to my phone when the screen is off and it's not charging.
Thanks for your time!
Okay, so for anyone else who may be having an issue like this... here was my problem:
After doing a lot of searching online, I discovered that the CVS app was causing the issue. Apparently CVS uses bluetooth beacons to discover your location and push "deals" to your phone. Only, this causes the phone to never go to sleep and causes the bluetooth to stay active and scanning.
So I uninstalled the CVS app, restarted the phone, and have been happy ever since. The app was handy, and some people have said that disabling the location ability in the app permissions may fix it, so I might try that later.
In addition, the Gasbuddy app has also caused similar issues, so if you have random battery drain and have either Gasbuddy or CVS installed, try uninstalling those and see if it helps.
when turning my wifi off it seems it goes into some weird loop of turning on and off constantly by itself, it doesn't seem to be trying to connect just flipping the wifi switch on and off none stop.
noticed it because i had a huge battery daring overnight and while trying to fix it i saw the switch going off and on all the time.
when turning it back on it seems to connect normally .
did a network setting rest but it did nothing ...
I'm guessing a factory rest will fix the problem but I'm hoping to avoid such a overkill solution :crying:
does anyone else had this problem and can help me fix it?
thanx!
avivzamir said:
when turning my wifi off it seems it goes into some weird loop of turning on and off constantly by itself, it doesn't seem to be trying to connect just flipping the wifi switch on and off none stop.
noticed it because i had a huge battery daring overnight and while trying to fix it i saw the switch going off and on all the time.
when turning it back on it seems to connect normally .
did a network setting rest but it did nothing ...
I'm guessing a factory rest will fix the problem but I'm hoping to avoid such a overkill solution :crying:
does anyone else had this problem and can help me fix it?
thanx!
Click to expand...
Click to collapse
This was on a new custom rom ?
Or did it just happend on a rom that have worked perfect for days?
And have you seen which app or system app been casuing the drain?
LyLu said:
This was on a new custom rom ?
Or did it just happend on a rom that have worked perfect for days?
And have you seen which app or system app been casuing the drain?
Click to expand...
Click to collapse
original samsung rom.
just happened (i have the device for a a while everything was fine) its the android system that drains the battery in the battery status.
when i leave the wifi on it stops and works fine ...
Have you turned off ''Keep Wifi During Sleep''? I know this can drain battery.
It's not so easy to troubleshoot on an orginal none rooted phone.
You can try clearing dalvik and cache.
Turn it off and then on holding power and vol down button, then clear cach/dalvik and restart.
Try uninstall update beaming service for samsung then restart
If still persistent try uninstall update microsoft onedrive and skype then restart, just in case
I found it after factory reset (forgot internal data backup :crying and update all apps, this problem occuring after the last 3 updates (beaming, onedrive, & skype) which more suspect beaming service update make that problem
Your not alone
You're not the only one who suffer from this exact problem, on Friday or Saturday the same problem started occurring with my phone too, WiFi turns on and off in a loop and huge battery drain!
I saw an increase of 6% of battery drain per hour, so I ended up on 9% total drain every hour. :crying:
I have original Samsung Rom and phone worked prefect until now, no settings or apps installed before this happened either.
What rom version are you guys on?
I'm having the same issue. However, I'm on PhoenixX Rom. Major battery killer and has only just started happening within the past few days.
Since my phone has been unplugged, 3 hours ago, looking at BetterBatteryStats, It is showing com.google.android.gms as having quite a LOT of wakeups. 40 per hour (everything else is about 2). Don't know if this is normal as I don't remember it before the Wifi issue.
Looking into what the wake ups are caused from, Location and heartbeat were the major culprits. So i have turned of WIFI scanning when not on and also the body sensors for Google Play. We shall see.
LyLu said:
What rom version are you guys on?
Click to expand...
Click to collapse
See attachment.
Easy fix. Just disable Wi-Fi scanning.
the_scotsman said:
Easy fix. Just disable Wi-Fi scanning.
Click to expand...
Click to collapse
its not a fix at all . it dosnt scan for wifi , just turning it on and off non stop.
like pressing the light switch agin and agin
I had this after installing "GoodLock" software from Samsung! Uninstalled and everything is ok
same here, just noticed I wasnt on Wifi and the switch is just flicking on and off by itself. Standard S7 with all the updates installed
Been struggling with the same for some days (4 - 5) I haven't been able to get exactly whats triggering this. I'm on stock rom with root. I've reinstalled firmware clean again and re downloaded my apps but it is still happening randomly. Some times after a few attempts to switch wifi on (even when it is toggling by itself) it manages to keep on. Sometimes restarting makes it work again. One thing I'm almost certain its that this usually happens after I turn wifi OFF and then try to turn it back on.
It's been crazy and the phone starts to overheat after a while off this on-off loop.
Any ideas?
its very wierd it started to all of us in the past few days-weeks . seems like samsung has a bug they need to hurry up and fix.
AT&T just pushed out the October Security update for the S7 family, I'm guessing something that came along with it is creating the problem.
mine did a software update last week and I've been away in airplane mode so it could have started then. I've just disabled scanning and that seems to have got round the issue and I'm now connected to WifI
I'm not sure whether it is a Samsung Issue or a Third party one... It is true that something recently affected all of us, but as far as I know, it could be a third party app that wasn't well developed for our phone.
I've noticed the same problem on my phone and it's also only started up in the last few days. On stock Sammy rom, unrooted. Will be monitoring this thread to see if the experts here can narrow down the culprit.
I had the same issue and I was able to stop the toggle by turning off the wifi scanning in Location - Improve Accuracy - WiFi scanning. It's a fix for now. I think it may be an app that may have been updates that is persistently looking for location updates.
I just got my g5 plus yesterday. I've been having this annoying issue where the screen goes to sleep randomly while I use the phone. I'm using my commonly used apps and the screen just dims and a second after it goes to sleep. I've also notice that if I leave the phone idle for at least 7 seconds, it also happens. I've tried power cycling the phone, changing settings in safe mode (had set it up for auto sleep after a minute), resetting app preferences and even tried 3rd party apps to try to override the stock settings for the screen's adaptive brightness. I asked the Moto Tech Support team and they said that I had to factory reset the phone, and if that didn't work, I had to turn it in for warranty. Is there a way to solve this?!
P.D. The issue doesn't persist while using the camara app. This is the reason I think the issue is more of a software issue that a hardware issue.