Searched for related threads but no luck ... anyone experiencing this problem?
-Google
#Team MiNCO
I sit with mine on my desk while I work and Ill sometimes look up and the screen will be on when I know its been locked for a while. it doesnt seem to matter if its plugged in or not.
I was thinking it might have to do with my ROM (paranoidandroid) but if other people are experiencing this it might not be.
its an app or process waking the device. or a bad power connection that connects and disconnects(if plugged in).
Mine isn't even unlocked or rooted... soooo who knows what it can be lol
-Google
#Team MiNCO
I'm having the same issue, but only when my N7 is being moved (even gently!). Several times, I've manually put the device in standby (with the power button), or I let it idle and then go into standby, but when I pick it up, the screen turns on. I haven't noticed the screen turning on while it's sitting still on a flat surface, but then again, I haven't really hawked the device while it was sitting still. This wasn't an out-of-the-box problem. It just started happening on my 3rd day of use.
Anyways, this gets pretty frustrating when I have my tablet in my bag or pocket. I checked to make sure I wasn't accidentally hitting the power button to wake the tablet back up by putting the device on standby and then gently tilting the tablet. That was enough to trigger the screen to turn on.
The power button doesn't appear to be visibly loose either. (My tablet doesn't go into standby when I jostle it, if that matters?)
By the way, I haven't really moved my N7 while charging, so I can't verify whether or not this issue occurs during charging as well. But I guess I can rule out charger issues. Maybe something's loose?
Side notes: I AM unlocked and rooted; did this on day 2. Haven't gotten any new apps between the time my tablet last acted normally and the time when it started turning on during sleep (during day 3).
Any help would be greatly appreciated!
Might be the smart case magnets. Putting magnetic stuff near the screen turns it on.
Sent from my One X using xda premium
This almost always is caused by a rouge app. Use watchdog (there is a free version in the market) this can help pinpoint what app is misbehaving. Also, if possible try to get a logcat of this, of course if it feels random it may be hard to capture the information needed but if you do you will no exactly what the problem is
Oh and as a side note, wakelock issues can happen to nonrooted phones/tablets just as easy as with rooted ones
Sent from my Nexus 7 using xda premium
I'm having this issue as well... But I can't figure out what the heck is causing it! Anyone find a solution? I'm using Paranoid Android... could that be an issue?
No one find the solution yet? In stick and rooted and having the same problem.
Why is the door on the right always locked?
Fully updated stock not rooted on 4.2.1. I first noticed this issue after updating to 4.2. Screen wakes every 3 to 5 minutes and stays on for @30 seconds each time. I left it sitting on the couch next to me while watching TV last night.
So it is affecting the stock ROM as well.
Sent from my Nexus 7 using xda app-developers app
Trying not to get aggravated but it's annoying the heck out of me that i can't track down the source of the issue.
Why is the door on the right always locked?
Have you pulled a logcat?
Sent from my HTC Vision using xda premium
I actually haven't yet. This was going took be next. Just as soon as i have time. Any tips on what I'm looking for?
Why is the door on the right always locked?
cat /proc/last_kmsg
What the last things that happened before shutdown
Any errors in general
Feel free to post a copy here
Sent from my HTC Vision using xda premium
I'll look tonight if i have time. Thank you
Why is the door on the right always locked?
had the same problem. It was an calendar widget app that cause the all 30sec screen on. I have deleted the app and it's all fine now.
Which app?
Why is the door on the right always locked?
Quick Agenda. Replaced with Simple Calendar Widget.
I have neither. Too bad
Why is the door on the right always locked?
Spolier alert! This is the plot of Paranormal Activity 5. Possessed N7s. At the end it turns out it was iOS the whole time. It would have gotten away with it too if it weren't for us meddling XDA folk.
Serious note I have had this happen before and as previously stated it was a rogue app accessing background data.
Sent from my Nexus 7 using xda premium
Related
So I got my thrive yesterday and I love it, out of all the tabs out, it just feels like it is the smoothest, graphically and strongest, hardware wise. I haven't had any problems until this morning when I woke up and tried to wake up my thrive, and unfortunately it would not wake up, so I had to do a hard reboot by holding down the power button until it shutdown, but it booted right back up. So here's where I think I went wrong, I turned on the GPS yesterday and didn't know I had left it on overnight, thought it would turn off when you stopped using maps, for what reason? I don't know why, but I did. Either way I think that there are certain programs that cause problems with the sleep of death, and that's the reason it may have happened to me. But if anyone has any ideas as to why this happened, then I would like your input.
Sent from my AT100 using XDA Premium App
bken620 said:
So I got my thrive yesterday and I love it, out of all the tabs out, it just feels like it is the smoothest, graphically and strongest, hardware wise. I haven't had any problems until this morning when I woke up and tried to wake up my thrive, and unfortunately it would not wake up, so I had to do a hard reboot by holding down the power button until it shutdown, but it booted right back up. So here's where I think I went wrong, I turned on the GPS yesterday and didn't know I had left it on overnight, thought it would turn off when you stopped using maps, for what reason? I don't know why, but I did. Either way I think that there are certain programs that cause problems with the sleep of death, and that's the reason it may have happened to me. But if anyone has any ideas as to why this happened, then I would like your input.
Sent from my AT100 using XDA Premium App
Click to expand...
Click to collapse
Actually, GPS is not active unless an app is accessing it. You can leave it on. As for the SOD issue, Toshiba released a fix today and it should fix it.
Thanks, and I got that update, it fixed it.
Sent from my AT100 using XDA Premium App
This is my first nook. I did some trading to get it. It had cm9 on it when I got it but it a tad laggy so I put mirages cm7 on it using from manager. It has been running great ever since and today I put it on the counter(battery was around 60%) I took it to my room a little later to charge since I have to work tonight but before I plugged it in I tried to wake it up but the screen would not come on. It will not do anything at all. Never owning one I have no idea how to diagnose it.
Sent from my Galaxy Nexus using xda premium
Welcome to the Sleep of Death - I have this happen occasionally too.
Hold the power button for ~10 secs, the screen will get noticeably darker when it actually turns off. Let go and press for another ~8 secs to cause it to reboot - you'll get that distinctive flash from the back-light.
I find this happens more often when I leave the wifi on and it goes to sleep, so I'm pretty obsessive about turning that off before sleeping the nook.
What ROM are you running? Stock CM7 or Phiremod / Mirage / etc.?
HumanXv2 said:
This is my first nook. I did some trading to get it. It had cm9 on it when I got it but it a tad laggy so I put mirages cm7 on it using from manager. It has been running great ever since and today I put it on the counter(battery was around 60%) I took it to my room a little later to charge since I have to work tonight but before I plugged it in I tried to wake it up but the screen would not come on. It will not do anything at all. Never owning one I have no idea how to diagnose it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That was probably Sleep of Death (SOD). Read about it in my tips thread in my signature link.
Sent from my Nook Color running ICS and Tapatalk
Worked like a charm, thanks a lot. I'm running mirage now and sometimes back to miui. Debating on going back to cm9.
Sent from my Galaxy Nexus using xda premium
Bought a refurbed 32GB WiFi from sears on Jan 2nd and had no issues except for a screen flicker. I was running a CM10.1 build from around Jan 26th and the latest Motley Kernel.
Yesterday I was using the tablet as usual, but I hadn't charged it in a couple of days
so the battery was getting low. After I got home from work I went to use it but the screen wouldn't come on. I figured the battery had died so I went to charge it, but I never got the powered down battery animation. I've tried holding down all 3 buttons for at least a minute and nothing is happening, and when I connect to my computer I get a USB not recognized error.
I have about one day to return the device to sears with the 30 day warranty, but I just thought I'd check to see if anyone else was able to resolve a similar issue before I do so that I don't lose all of my data, and the fact that if they do get it running again that its rooted and running CM.
Any suggestions, or should I just take it back?
Sent from my Galaxy Nexus using xda app-developers app
Sounds like the Nexus has had it, take it back is most likely the best option
Sent from my Nexus 7 using xda app-developers app
AW: Tablet bricked itself?
One thing I learned from here, is that I never ever should let the nexus 7 run out of juice. Seems to be a death sign..
Jup, take it back.
Sent from my Nexus 7 using xda premium
Not a death sign.
You just need to let it sit on the charger for about 1/2hr, then it should boot right up. People panic when the device doesn't respond or screens start flashing, but it won't boot and they start mashing buttons and posting about their 'I think I bricked my device'. After a device has run down it might take a long press of the power button to get it to boot and/or sit on the charger for a bit.
Running the battery down should not be confused with the Sleep Of Death (SOD). The fix for an SOD is also a long press of the power button.
Sent from my N7 using XDA Premium
Dirty AOKP 3.5 <&> m-kernel+ a34(t8)
try connect to charger at least a half an hour, then press just power button for 1 minute. i had similiar issue, and it worked for me. if dont work, maybe you got battery connector loose problem. try search in general section about that.
Hi All,
I was browsing the web a couple of hours ago and my N10's screen started flashing on/off and after around 10secs the thing crashed/turned itself off. Being an N10 this was not an unusual event! However when I try to turn it back on nothing happens. I can hold the power button / power button with volume buttons pressed and nothing happens. If I plug it in to charge I do not get even get a charging icon.
If it makes any difference I was running the latest Rasaber with Franco's r11 kernel and I know I had at least 40% battery left when it died. I have left it plugged in to the stock charger for around an hour hoping that something might happen but still nothing.
Has anyone ever experienced anything like this?
There was not a sad enough looking Emoticon to convey my sadness over the possibility my lovely Manta is dead......
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Something similar happened to me but I'm totally stock. I Googled and the solution was to recharge the unit via my PC USB instead of plugging it into an outlet. I have no idea what happened but after a few hours of being connected to my PC it was back and working. Hope that helps.
I'm running the same rom and kernel combo. No problems or anything weird happened. It must be hardware related.
Did you try the holding-the-power-button-for-a-minute routine?
I would try to leave it plugged in on the charger for a while and see if it gets fixed. That usually solves all sorts of "wont turn on" problems
samwheat said:
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
You seem upset
i seem realistic
another nexus 10 with problems
Sent from my Nexus 10 using xda app-developers app
is it possible for the tablet to get overheated?
I have had that happen on stock.
My theory: it is linked to the 'battery status not updating'-bug. Your Nexus thinks the tank is still half full, while in fact you are running on fumes. It does not realize this, so no dimming of screen, no low power warning, it just goes full steam ahead, until the battery is totally and utterly and completely depleted.
Then, obviously, it won't start but it will also have trouble charging. You need to charge it for quite some time, sometimes try a different charger, and sometimes keep the power button depressed for a full minute for it to come back to life.
Now when I use my Nexus, I keep an eye on the battery status. If it does not go down, I know I need to reboot for the battery status to be read properly again. It is a bit of a bother, but not too much. The bug only kicks in after the tab has been lying around for a while sleeping. So if I want to watch a movie, I first reboot. As long as I keep using the tab (i.e.watching the movie), the bug won't 'activate' and the tab will shut off properly when it senses the battery is low, in stead of continuing and deep depleting the battery.
Sent from my Nexus 10 using XDA Premium HD app
My experience with my S4A has been amazingly flawless up until yesterday, when it started experiencing one of the issues that killed my experience with the HTC One- random freezes. And what's strange about it is that they are the same type of freezes that my One experienced, only when browsing the web or using an internet based app like Pulse. It has happened 3 times since yesterday and is so bad that I've had to pull the battery to even get it to reboot. Which brings me to one of my suspicions...
The only thing that has changed between me getting the phone set up originally and when the freezes began was the fact that I started swapping batteries instead of charging the phone. Now, phone batteries nowadays are not just like your average AA cell, it has circuitry in it and NFC stuff... is it possible that a defective battery could be the culprit of my woes? I just put in my original battery and am gonna just wait and see if it happens. The other battery that I've been using is a Samsung OEM battery and not a cheap one. I did root and freeze a bunch of stuff, but nothing exotic, and it was fine until yesterday. I doubt anything I did caused this.
Has anyone else experienced any freezes like this? Help me solve this, I really want to keep this phone (at least until the next latest and greatest comes out). TIA
_MetalHead_ said:
My experience with my S4A has been amazingly flawless up until yesterday, when it started experiencing one of the issues that killed my experience with the HTC One- random freezes. And what's strange about it is that they are the same type of freezes that my One experienced, only when browsing the web or using an internet based app like Pulse. It has happened 3 times since yesterday and is so bad that I've had to pull the battery to even get it to reboot. Which brings me to one of my suspicions...
The only thing that has changed between me getting the phone set up originally and when the freezes began was the fact that I started swapping batteries instead of charging the phone. Now, phone batteries nowadays are not just like your average AA cell, it has circuitry in it and NFC stuff... is it possible that a defective battery could be the culprit of my woes? I just put in my original battery and am gonna just wait and see if it happens. The other battery that I've been using is a Samsung OEM battery and not a cheap one. I did root and freeze a bunch of stuff, but nothing exotic, and it was fine until yesterday. I doubt anything I did caused this.
Has anyone else experienced any freezes like this? Help me solve this, I really want to keep this phone (at least until the next latest and greatest comes out). TIA
Click to expand...
Click to collapse
Mine started Sunday. All it would do is hang at the ATT logo on reboot. I ended up doing a factory reset and it hasn't happened since. Certainly made me suspect the rooting I did...
kbmapper said:
Mine started Sunday. All it would do is hang at the ATT logo on reboot. I ended up doing a factory reset and it hasn't happened since. Certainly made me suspect the rooting I did...
Click to expand...
Click to collapse
What did you do to your phone after rooting?
A couple of times now my active has become unresponsive. The power button doesn't seem to work and the home key doesn't do anything. The led is flashing blue and the battery is still about 35%. The only thing I can do is pull the battery.
Not sure if this is related to your question but I'm going to try to get it replaced...
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Didn't really do anything drastic- Titanium Backup and froze some att crap. Nothing even remotely close to system apps.
dinglayne said:
A couple of times now my active has become unresponsive. The power button doesn't seem to work and the home key doesn't do anything. The led is flashing blue and the battery is still about 35%. The only thing I can do is pull the battery.
Not sure if this is related to your question but I'm going to try to get it replaced...
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Click to expand...
Click to collapse
My LED never starts flashing but like yours, none of the buttons respond and I have to do a battery pull. I really don't want to have to get it replaced, and I really don't want to wipe and start over, just don't have the time right now to do either. Did you do anything to yours? Root?
kbmapper said:
Didn't really do anything drastic- Titanium Backup and froze some att crap. Nothing even remotely close to system apps.
Click to expand...
Click to collapse
Same here. Nothing I froze should have any affect on system stability.
I Haven't had any issues since I've had the phone, going on 3 weeks. I've been rooted and have froze apps in TB with no problems since geohot gave us root. Also have done some other root mods, and have not experienced any issues.
Sounds like just some bad hardware circulating.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
I've modded mine a good amount and haven't had any lock ups. I have just about every root app out there. Xposed with nottach, dark phone and contact apk, and cm10.1 messaging app. Froze a lot of bloat too
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4 Beta
Man I REALLY hope it's not a hardware issue. I'm so tired of doing the repeated exchange thing. I went through 5 One X's before I found a suitable one, saw that pattern emerging with the One (had 2, both with same issues) and was really hoping the S4A was going to be the answer to my woes. I really love this phone but if it ends up being a hardware thing, I will be incredibly disheartened.
Sent from my SAMSUNG-SGH-I537 using xda premium
Any way to tell the build dates of our phones? Maybe we could narrow it down to a certain production date.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
echonc said:
Any way to tell the build dates of our phones? Maybe we could narrow it down to a certain production date.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Click to expand...
Click to collapse
I dunno... My box is in another state so I won't be able to check it for a few weeks. I bought it on the very first day it was available if that helps any. On a side note, I put my original battery in last night and it hasn't locked up on me since. We'll see what happens by the end of the day.
Sent from my SAMSUNG-SGH-I537 using xda premium
I am rooted but that's pretty much it.
The only thing I know I was doing at the time was watching a YouTube video then pressed pause.
Next thing you know I picked it up hit the power... Nothing. Hit menu... Nothing. The blue LED was just the normal notification indicator, so I knew it hadn't powered off... Resulted in a battery pull.
I also know that I didn't get any messages or new notifications while the screen was off.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
I ALWAYS have issues restoring from titanium backup, esp going from one phone to another. My suggestion is to factory reset and start with a clean slate, cas only then can u verify a hardware issue.
_MetalHead_ said:
I dunno... My box is in another state so I won't be able to check it for a few weeks. I bought it on the very first day it was available if that helps any. On a side note, I put my original battery in last night and it hasn't locked up on me since. We'll see what happens by the end of the day.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
I know on the Captivate the Build Number could be found under the battery (can be found there on the S4A as well) and it was the year/month that the phone was built, or so they say. My S4A Build number is 1306 so I'm guessing it was built the beginning of June...
_MetalHead_ said:
I dunno... My box is in another state so I won't be able to check it for a few weeks. I bought it on the very first day it was available if that helps any. On a side note, I put my original battery in last night and it hasn't locked up on me since. We'll see what happens by the end of the day.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
I would like to know if you have had any more problems since you put your original battery back in? If you could give a update I would really appreciate it. I really think the active is a great phone and I truly like it but if people are having a lot of issues with it, I'll just return it and get something else to save myself a headache down the road. I have a week left on my return date so that's why I was wanting to know.
Sent from my SAMSUNG-SGH-I537 using xda premium
gf has had similar issues; heres what fixed it.
battery pull
factory reset/restore
reboot
battery pull
reboot
root/etc/restore from there. check to make sure you dont have custom CPU voltage/speed mods enabled; i believe this was the initial culprit, though even after resetting them to stock it would still lock up. it only did it 3 times, and usually right after a new mod, but ONLY if CPU values were changed. after the above procedure, she redid all her cpu values but only AFTER all mods were installed, rebooted, and everything works great again.
tmease1 said:
I would like to know if you have had any more problems since you put your original battery back in? If you could give a update I would really appreciate it. I really think the active is a great phone and I truly like it but if people are having a lot of issues with it, I'll just return it and get something else to save myself a headache down the road. I have a week left on my return date so that's why I was wanting to know.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
The only "issue" I've had with mine is that it's too bright when the brightness is set to max
tmease1 said:
I would like to know if you have had any more problems since you put your original battery back in? If you could give a update I would really appreciate it. I really think the active is a great phone and I truly like it but if people are having a lot of issues with it, I'll just return it and get something else to save myself a headache down the road. I have a week left on my return date so that's why I was wanting to know.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
Same problems no matter which battery. It seems to happen most when I'm using Chrome so I deleted the updates but it's still doing it. It happened while playing a game today which it's never done before. Next step is to freeze Chrome and see if that helps. If not, then I'm gonna factory reset and if that doesn't work, I'm gonna have to exchange it. I really did not want to have to deal with this. With my ridiculous work schedule I don't have the time or the energy. I might just start looking for a different phone because I'm sick of having issues like this.
Sent from my SAMSUNG-SGH-I537 using xda premium
_MetalHead_ said:
Same problems no matter which battery. It seems to happen most when I'm using Chrome so I deleted the updates but it's still doing it. It happened while playing a game today which it's never done before. Next step is to freeze Chrome and see if that helps. If not, then I'm gonna factory reset and if that doesn't work, I'm gonna have to exchange it. I really did not want to have to deal with this. With my ridiculous work schedule I don't have the time or the energy. I might just start looking for a different phone because I'm sick of having issues like this.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
I would say if the factory reset does not work than it is the phone itself. I had issues like this in the past with my old infuse and I did a factory reset and it took care of it. Hopefully that will help you out so you can keep your phone. Thanks for replying.
Sent from my SAMSUNG-SGH-I537 using xda premium
tmease1 said:
I would say if the factory reset does not work than it is the phone itself. I had issues like this in the past with my old infuse and I did a factory reset and it took care of it. Hopefully that will help you out so you can keep your phone. Thanks for replying.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
Yeah bud, I really hope a reset works. I might do it tomorrow, I should have enough time. I'm just frustrated that I'm having identical issues with the S4A that I had on my One. I was really hoping to find a phone that just works. I don't think I've had a problem free phone since my Epic 4G Touch. My One X had issues (though my 5th one was near perfect), my iPhone 5 was horrible, both my Ones had problems, and now this. I'm just venting now but I'm seriously tired of it. I've got my eye on that new Sony i1 that's coming out in a couple months, I really love their current design choices and I've never tried a Sony before. Or maybe the next Nexus. Who knows. I just don't want to deal with this crap anymore.
/rant
Sent from my SAMSUNG-SGH-I537 using xda premium