Database Users

G1 Doesnt Always Wake Up

Does anyone elses G1 not wake up when Menu is pressed? Sometimes I have to press it like 6 times before the phone wakes up, does anyone know why?

Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.

momentarylapseofreason said:
Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.
Click to expand...
Click to collapse
Yea, i was thinkin the same, i should try runnin a ton of apps and find out if [email protected] the problem

mine does the same things sometimes. gets annoying at times. usually i just open and close the keyboard

Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!

brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
Shop Savvy?

I also started having the wake up problem and quicker then normal battery drain. I have an ADP1 phone which I updated to 1.1 a few days before noticing issue
I think that the theory of something sucking clock cycles is a good one. I noticed my CPU Usage (when nothing was running other then System Monitor) went from 0-40% to 20-70%.
I couldn't be bothered with the finer points of troubleshooting, so I took the thermo-nuclear approach and did a factory wipe.
Just before the mystery CPU cycle and wake up issue, I hadn't installed any new apps, BUT I did update a bunch of existing apps. After the factory wipe, I left off installing the following list:
Watts
StreamFurious
DroidFTP
Telnet
e-VoiceRecorder
VoiceRecorder
Constitution
Barcode Scanner
Astro
RingDroid
SlovoEd Classic English Dictionary
Things are fine now.

both of my g1's do this, and have done this out of the box, anyone turn off there screen with the keyboard out, and then close the screen and the screen comes back on with the lock screen up and then having to turn the screen back off? annoying

try the swapper app?
or turn phone off and back on, it might becuase you are usingahome or openhome or dxtop or sweeterhome, these app may slow down the interface a bit, try downloading droid sans tweak lite and fool around with that..
goodluck i also get this sometimes

brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.

Hmm, im not experiencing any of the above posted issues, it may be a particular app that u have installed. I only have the wakeup issue sometimes, most likely when the phone is running slow from the browser or another memory draining app, but no app in particular.

Hmm, when mine fails to wake up, I never waited long enough for it to come back, just reseated the battery for a reboot.
Of the other problems, I have the "screen-black-for-a-few-before-caller-picture-shows-up" issue.

JayBachatero said:
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.
Click to expand...
Click to collapse
what firmware do you have?
btw, dont count on Locale to turn off your stuff all the time, its not very accurate imo, at times its great, but thanks to the crappy g1 battery, they have a choice, constantly check time/location/.ect and drain the battery in a hour flat, or periodically check it and reduce battery drain, do you have any wifi programs that keep wifi on when phone sleeps (such as wifi lock and so on)? if so use the program on the market that writes up a log of its actions and see if its acting up
as for #1 (sorry im unorganized) my phone does that too, i believe its because i have 2 programs that run when the phone rings, let alone im sure locale is checking to see who is coming since thats a condition, which would make 3, and then i have a mp3 that plays when the phone rings, and i have a class 4 sd card (i know, i know), the way that programs work is that it has to go line by line of the code, if it is slowed down, or it has to execute other items before continuing that are slow to execute, than everything has a delay, but yeah from time to time i have this issue, phoneplus was a program that made me miss a few calls (1/4th of the time)
i think 3 and 4 are directly related, could be wrong

I was having the same problem right after I installed the app "Contact Owner"
No amount of reboots fixed the problem. Uninstalled and everything was back to normal.

@wootroot - I have stock RC30. Haven't rooted yet.

JayBachatero said:
@wootroot - I have stock RC30. Haven't rooted yet.
Click to expand...
Click to collapse
consider upgrading to the rc33 ota update yet? i had better battery life (and my battery didnt get as hot) when i used rc33
also, if youve had your phone since it first came out (rc19 i believe) and your battery used to get very hot, you might of damaged some of the cells (especially of the battery has expanded), if this is the case simply call tmobile and tell them that your noticing even after wiping the phone that your battery life is lasting shorter and shorted, even with out any programs installed from the market, i even went as far as to say that i made sure wifi was off, only 2g was on, gps was off, screen was dimmed, timeout set at 30 secs, and im still only getting a hour of life (none of which is true but it got through all the "well how about trying this and calling back if you still have a problem" bs, with the ota rc33 and the new battery, i noticed a pretty good difference

I have a modified version of this "doesnt always wake up". The phone is less than 24 hours old, it was a refurb they sent me for the last one that went dead. I used it with the rc33 it came with and found the problem, then figured it was hosed so i rooted and installed 3 of the versions of cupcake (The Dude, JF, and Haykuro) to see if they all had the issue- they do. Here is a video, hope you can see the attempted keypresses. There will be lines that appear, like the screen is broke..then, they will go away. Sometimes it takes 5 minutes to get the phone to turn on, however if I leave it on (never goes to sleep) it works flawlessly.
http://www.youtube.com/watch?v=ecQo2Ly2WUM

I get this all the time also...
Uninstalling dxTop doesn't change anything for me...it still acts the same...
I also get the problem that when someone calls me the screen stays blank for about 5 seconds and I can't tell who calling...

wake up issue
I am experiencing the same problem, with a brand new warranty replaced G1, what happens is when the phone goes to sleep it completely locks up, when I try to wake it up via menu, it does not wake. Plugging the phone in and trying ddms or adb does not work, ddms shows the phone as offline, also the device seems to get really hot when this happens, sometimes Call + Menu + Power resets it, and sometimes I have to pull the battery.
I think this may have to do with wifi turned on. Because when the screen goes off your phone switches wifi off and goes to 3G as default setting.
I think we should try leaving wifi on all the time and see if that solves the issue, im about to try that now.
It seems this is a known issue over at tmo forums

A couple questions:
When this happens to you guys is wifi enabled and connected when the phone is shut off?
What Rom, SPL, and Radio is installed?
I noticed this didnt happen to me until I enabled wifi, maybe I didnt wait long enough because its completely random, please send back your results
defcon

[Q] random reboots

Hi, is anyone else getting random reboots on their tablets? im running 3.1 its rebooting like crazy yesterday it did it 3 times one after the other and it just did one right. is their a fix for this? ill greatly appreciate it if you help
~Thanks

the only fix I've discovered is that I have to turn off the wifi before idling for awhile. Mine only reboots after it goes into sleep, never when I'm actually using it.

yea it only does in idle, so theirs no actual fix to this?

I haven't experienced this, but I also put my tablet in Airplane Mode when I know I won't be using it for several hours or a day.
I do this to conserve battery life, but I suppose it's also meant that I don't see this problem -- assuming it's a widespread problem to begin with.
For now -- until we get another software update that might fix the issue -- try getting into the habit of switching to Airplane Mode when you're done using it. It only takes two taps.

Mine did it to me today for the first time while the screen was turned off. It never happened until today or at least I have never witnessed it. I have had mine for just over a week. I also put mine into airplane mode & have been all a long when putting it to sleep. I read in another thread that under wireless setting you can set so wifi goes off with screen off under wifi disconnect policy. I don't think that wifi does turn off though.
The only other thing that has changed is that I installed the Riptide GP Demo last night. I didn't play it until today. Shortly after I was finished I put my Transformer to sleep (screen off). After a few minutes I heard pop & just a single pop. I turned my transformer back on then off. I heard this poping noise a couple of more times. I finally restart my transformer & problem went away. It was a short time later when my transformer rebooted its self.

It does this only when docked to the keyboard. I have stopped using my keyboard for now until there's a fix for this. Lost a long document last week because of the random reboot.

I'm on 3.1 and haven't experienced this. Strange.

Does this once or so every day when sleeping, doesn't matter if docked or not.
Sent from my Transformer TF101

If you have an sdcard plugged in the dock, you can try to remove it.
It worked for me.
more details -> http://forum.xda-developers.com/showthread.php?t=1120185

What did you change? Did you add an app, take an app update, change a setting, insert a new SD card?
I have never experienced a unexpected reboot.
Sent from my Transformer TF101 using Tapatalk

[Q] Nexus 7 screen turning itself on?

Hi all,
I'm experiencing an issue on my stock 4.1.1 Nexus 7. The screen seems to be turning itself on randomly. It normally turns off again but may toggle on/off quite a few times. Then it seems to go for a while whitout turning on. Bit odd.
Anyone else experienced this or have any thoughts on a reason for it?
Thanks

Same problem here, except with a Samsung Galaxy Nexus.
I just updated to 4.1.1 today and this is the first time I've seen it happen. Was previously on 4.02 without issues.

I have had the same problem. It seems to happen in the evening and I wondered whether the case was causing it to overheat. Seems to be OK when I take it out of the case. I phoned Google and was told that it hadn't happened before. I will contact them again if it doesn't get any better.
Sorry. Misread the post. Mine goes to sleep, not turns on
Sent from my Nexus 7 using xda app-developers app

gifton1 said:
Hi all,
I'm experiencing an issue on my stock 4.1.1 Nexus 7. The screen seems to be turning itself on randomly. It normally turns off again but may toggle on/off quite a few times. Then it seems to go for a while whitout turning on. Bit odd.
Anyone else experienced this or have any thoughts on a reason for it?
Thanks
Click to expand...
Click to collapse
Same here but mine is not exactly stock.
I have installed Apex Launcher plus numerous apps. I thought maybe it was the launcher doing it. But at this point... I have no idea. Just noticed it tonight coming on and then going off within 1 sec. but its random. it may do it once within an hour, or it may do it up to 5 times within a min... then go several minutes completely black screen. Crazy stuff. I thought maybe it was getting a message at first but then realized I had the WiFi off on my phone so it was dead to any incoming messages/wifi. I am really curious as to what is causing it and will be following this post as well as others quite frequent. Also.... the latest app that I have downloaded was OSMOS HD. it wasn't waking then sleeping before that app... just my 2 cents.

Hi Qbensis,
By stock, I just mean not rooted and not running any custom firmware. I had various apps and the like installed.
I have actually since rooted my N7 and installed a few custom ROMs and since then have not seen the issue at all. If you want to stay stock, I assume the issue will be fixed in the next update

I have seen this a few times. Middle of the night I look over and the screen is on then off. I check the power usage overnight and I see little blips of screen on when looking at the graph. Not sure whats causing it (I figure a app).

Same Problem over here, any solutions???

I'm on stock 4.1.2 and having the same problem, not rooted. Creeped me out in the middle of the night when it goes on and off.

N7 Random Turn On
Same here on 4.2.1. I carry in front pocket all the time with screen facing leg and feel heat when it happens. Has even done it when in Power Off mode and still does it. I thought that would prevent it for sure. Very irritating and drains battery. We Winter in 55+ community and drive around in golf carts. I am starting to wonder if WiFi spots trigger it. Will continue to track behavior and search other forums. Curious that there have not been any solid suggestions or solutions.

Happens to my rooted but stock 4.2.1. It happens randomly when I recharge using a battery pack (4AA) as opposed to charging using regular AC. It's annoying as heck! I don't know how to get this fixed!

I've been getting this on both SmoothROM and raspbeanjelly, and it's very irritating.
It has to be an app that is causing this. I initially thought perhaps it was GPS Status, because I caught it in the notification bar a few times when the screen turned on.
My device definitely isn't hot when it happens.
I'm suspecting the Email app, Maps, or Facebook.
EDIT - not any of them either. I'll test Beautiful Widgets next.

Okay guys, try this.
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
I'd been suffering from this for weeks, factory reset, reinstalled and changed out ROMs, installed apps one by one over the course of several days to keep an eye on what might be triggering it etc. Nothing worked for more than 2-3 days at most, and the issue always came back in one way or another.
It was causing me to have to turn the Nexus off when not in use because it would be draining battery (15-20% overnight compared to 2-3% when the issue wasn't present).
Then I stumbled upon that guide and using Gemini I disabled Maps from auto-running, turned off Latitude, and so far so good.
If it works for you too, be sure to hit thanks on Karpfenhai's post!

I was having this same problem on my Nexus 7 running stock 4.2.2 rooted with SuperSU. Finally tracked it down to having installed BetterBatteryStats and for some reason, I had not granted it perpetual root. It was causing the device to wake and turn the display on for random times (up to 13 hours, which killed the battery), not always showing the SU request dialogue. I granted perpetual SU privilege to BetterBatteryStats and problem went away.

Try taking out the battery and clean out the USB port with a toothpick. This worked for me. All the dust that accumulates in the post can cause the phone to think it's charging.

First Freeze Issue after JB 4.12 update on GN 8013

I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.

Yeah I think they call it the sleep of death. Happened to my recently updated wifi (8013)note also.

IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry

samir_a said:
IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry
Click to expand...
Click to collapse
I started the thread so we can see if it's happening to multiple units and what models and firmare seem to be affected. If more report the same issue, maybe this thread can be stickied. From what I read when looking for solutions, it seems to occur after firmware updates and has occurred on many of Samsung's tablets.

I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.

BarryH_GEG said:
I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.
Click to expand...
Click to collapse
On my GN 8013, I had to keep a finger on my screen while holding down the power button; that brought up the battery icon screen and from there I could reboot. Holding down the power button alone did not reboot and triggered my panic that drove me to a Google search and a solution to enable rebooting. This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.

mke1973 said:
This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.
Click to expand...
Click to collapse
I kind of look at it as the equivalent of the "blue screen of death" in Windows. My desktop PC throws a shoe every once in a while and it's usually tied to either graphics or memory conflicts based on the dump message. I'm guessing what we're experiencing is the Android version. As a pure guess I'd say it's something to do with memory reads/writes/buffers caused by either a management issue with the OS or an app (or combination of apps) doing something it shouldn't at an inappropriate time. And after playing with the power button I've gotten what you did (the giant battery icon showing up) and other times the Samsung boot logo. And I've had it happen twice in a week and other times once in six months; all without changing anything with the OS or apps. It's just one of life's little mysteries.
P.S. - My N2's done it but it behaves differently. It shows up a spontaneous reboot.

I had same issue frequently since last upgrade to 4.1.2 . I thought the problem is from Mobile VOIP. So I un installed it.
But today, another freeze happened. Ok, today just once. But, what's the problem?
N.b I recover it just by holding power button for 8 seconds.
Sent from my GT-I9100 using Tapatalk 2

mohammedsarhan said:
I had same issue frequently since last upgrade to 4.1.2
Click to expand...
Click to collapse
If it's happening frequently it may be something other than the random event some of us are talking about. A lot of you that upgraded from ICS to JB with all your apps intact could be having compatibility issues as not all apps have been updated/optimized yet. Older apps that are a little less mainstream and/or popular would be a good place to start to troubleshoot. Unless there's something specific to U.S. JB a lot of us have been on it since October and there haven't been any reports of frequent freezes or reboots. That is outside the random one discussed above that's not specific to JB.

mke1973 said:
I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.
Click to expand...
Click to collapse
Pretty much exact same thing happened to me last night, for the first time ever. Took me about 30 seconds to get any response, by holding down the power button for a LONG time. Rebooted, saw the battery was below 20%, which was also odd since I had charged it overnight and had consistently been getting 2-3 days on a charge.
If it happens again, I'll go with Barry's suggestion and try a clean install, then adding apps one by one. Little disappointing though, as I've had no real problems at all with the GNote until this JB update.
Thanks,
JC

Sleep of Death...
I have the 16gb wifi GT8013 model and I am having the sleep issue too. Mine isn't "deathly" that requires the finger on the screen while powering up, or standing on your head and spinning three times while chanting "sleep of death" or any craziness like that, but every once and a while, for no rhyme or reason, I have to start it from a cold boot when I attempt to wake it with the power button. I press and hold the power button for 3-4 seconds and here comes the Samsung boot logo. Once it gets booted and connects to the wifi, I am good to go.
This happens so intermittently, with it not doing it for a couple days, or it might be within the next hour. I think I have narrowed it down to the wifi radio. Reason being...I have done a factory reset and tried running it naked and it still happened. But I have noticed the issue seems to happen when I have left the house and it drops the home wifi and then negotiates a new connection with my SIII hotspot, which I turn on before leaving the house for work, or anything that I will need connectivity for the tablet while away from the house. I don't know if it is due to roaming outside the home wife and dropping the connection, or if it is the combination of dropping the home wifi and then locking into the phone hotspot. I am so busy that I haven't been able to get that far in my troubleshooting. However, I am leaning to just the fact of it leaving a wifi signal and, I guess, it doesn't want to and gets jumbled and kills itself all together. I say that because it has happened when I have forgotten to turn on the hotspot until I got to work and then I open the tablet and its dead.
This has been happening from day one, when I bought the tablet towards the end of January. Unfortunately the Samsung warranty absolutely sucks, due to them wanting me to ship it in and do without it for 3wks and then to boil my blood even more, they want to give me a refurb unit if they can't fix this one. To make matters worse, its been almost a week now and they can't even get the shipping arrangements made yet! Needless to say, with this thing only being barely two months old, I am a little on edge with Samsung and I would love to figure it out and fix it myself. If it were something I knew, without a doubt, would be fixed with rooting and dropping CM on there, then I would. But I see there are still stability issues with most custom ROMs and I really would like to keep the functionality of the S-pen.
I have attempted to pull a log file with aLogCat and they are blank. It appears that the log files disappear when rebooted, which does me no good in figuring out what shut it down, if I can't recall the log from pre-shutdown. I have also tried aLogrec in hopes of accomplishing this, however, something isn't right because I left it recording for hours and days and the log file was only 1kb. Although, it doesn't much matter since the log recorder running in the background keeps it from sleeping to the point of shutdown, so I am assuming it is a sleep issue, due to that discovery.
If anyone has any thoughts that might help me, I am definitely all ears! This tablet is for work and school so it is next to impossible for me to do without it for 3wks...provided Samsung can get their crap in gear enough to even arrange the shipping for the service request. And I sure as hell don't want a refurb!!
Later,
Roger

I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.

mke1973 said:
I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.
Click to expand...
Click to collapse
Unfortunately, I have come to the conclusion it isn't an app issue. I have never used any VOIP service, of any kind, and I have done a factory reset and it happened before I installed any apps. Unless, of course, it is an app or service that is included in the Touchwiz junk and/or bloatware that comes with it. It happened on ICS, which is what came on it, and it happens after being update to JB. However, I only had it on ICS for a couple days and I would like to go back to it for further troubleshooting, but since it has been updated to JB, that isn't possible without rooting and I haven't decided if I want to do that yet.
--Roger

After further observation, it appears my sleep-of-death issues arise when I leave the comforts of my home Wifi. When doing so, apparently losing the Wifi signal causes the tablet to shut down completely... When asleep. If I have LogCatRec running, that keeps the tablet from falling into hibernate and the issue never happens, thus resulting in nothing interesting being logged, aside from the typical tablet activity.
Now the question arises, is it my home Wifi, or just leaving a Wifi range in general? I cannot get it to recreate the issue by simply turning off the Wifi signal it is currently connected to. However, I am now on a new Netgear router, due to the Belkin shooting craps on me, and it happened then, on the Belkin, and it happens now, on the Netgear. So, my presumption is that it has to drop a Wifi connection due to signal degredation, versus simply cutting a decent signal off at the source.
Has anyone else gotten this far with their sleep of death issue? Or is there another thread, that I've missed that I am just repeating? I am curious to see what's out there, before I send this thing off and its gone for three weeks!
-Roger
Sent from my GT-N8013 using xda app-developers app

I have no issues any longer after finding the offending app on my note and uninstalling it. I don't think there's one cause for this issue. Most often, Android OS updates seem to create program instability in some apps that then trigger the sleep of death. It gets hard to track down issues for individuals experiencing the sleep of death on their devices because we all have different apps installed. You might look at apps on your note that require WIFI to sync and are allowed to sync periodically since one of those may be the culprit. Check comments on Google Play to see if any are known to be buggy under JB. Good luck.

Mke1973, with all due respect, I dont think you are reading my post thoroughly.
As I have already said, this is not an app issue. I have done a reset and the issue still happens when I run it without any apps downloaded and installed. Unless it is an issue with a Samsung app that is preloaded, in which case the fix is still out of my hands, since the owner of the tablet can't uninstall crapware at their will, without rooting it.
Sent from my GT-N8013 using xda app-developers app

Actually, I wasn't ignoring your facts it's just that there are 3rd party apps installed by default that, if you decide to use them, require sync. Specifically I'm thinking of Evernote. Once device makers began pushing out upgrades to JB, some Android users began reporting incidents of the sleep of death when using or after closing Evernote in various Android forums. It wasn't a majority of people, but more than a smattering, but that is standard with the sleep of death. Again good luck on your hunt.

Auto shut down issue

I installed some camera apps one day on ZfMP. I usually keep it for charging overnight. To my surprise the phone had shut down by itself. I long pressed power button for some 20 seconds, it opened up. I ignored it as a sporadic issue. But I faced the same issue once again yesterday.
Custom care has only one troubleshoot for all issues, "reset the phone".
Disappointed. Does anybody know what exactly is the issue? Please help me fix it.

[email protected] said:
I installed some camera apps one day on ZfMP. I usually keep it for charging overnight. To my surprise the phone had shut down by itself. I long pressed power button for some 20 seconds, it opened up. I ignored it as a sporadic issue. But I faced the same issue once again yesterday.
Custom care has only one troubleshoot for all issues, "reset the phone".
Disappointed. Does anybody know what exactly is the issue? Please help me fix it.
Click to expand...
Click to collapse
Ive faced this issue once in same conditions[overnight charger connected], and i too had to loooong pressed the power button for about 7-10 seconds to bring it back to life..
I would suggest to not connect the charger overnight.
I am thinking of alerting myself by way of a tasker profile, which i have already prepared. :angel:
Not many would like this solution, tasker being a paid application. But i purchased ages ago and there is no other software like that. And i recommend to have it purchased, and simplify your android life.
I can share the profile that i created, if anyone is interested.

Just install " Battery full notification "from play store and set is to a desired battery level.when the battery charge reached to the desired level the app will start a custom sound,so you will disconnect the charger.
It is a free app and i am using it since android Ginger bread days and my phones battery never damaged by unnecessary charging.

This is not a overcharging issue. Because only yesterday it got shut down at 84%. There seems to be some other bug related to this.

same problem i faced today at 65% of charge i keep my phone beside me and slept when i woke up it was off, I think this is not a charging issue its something else.

Random shutdowns
I'm having a similar issue too. Got the mobile a couple of days back and since it is still in the return period, I placed a replacement request.
After some digging, I realise it is rather common place with Asus smartphones to randomly shut down. Some say it is a battery calibration error. I've tried resetting the battery logs but the issue still persists.
I guess there's only two solutions as such-
1) Get it replaced by Flipkart. And yes, they do entertain return request even out of the ten day period.
2) Visit the service centre and get ready with a backup phone for a couple of weeks. I've visited the service centre and they seemed equally ignorant and dazzled.
PS- I did unlock the bootloader and rooted it. Installed viper, Greenify and YouTube red. I read that some of you had the issue after unlocking it too; That might be the culprit or it is just a manufacturing defect

i have not unlocked my phone and this was the first time i got this problem.
i kept the phone at night and didnt use it for 8hours the phone was on battery only.
morning when i checked the phone was off and i had to press the power button for 1 minute for it to start the battery was 75% so the battery didnt run to 0 and all.

can anyone on custom ROMs report back, if they face this issue or not? Just to know if its a stock ROM issue, or really a manufacturing defect.

It is definitely a manufacturing defect. It randomly switched off at first. Soon got worse and wasn't turning on at all.
I was on AOSP and returned to stock once the issue started. That didn't solve it even though I flashed the stock firmware via fastboot.
However, I tried keeping the phone on recovery and it didn't die then.

iiamaduine said:
It is definitely a manufacturing defect. It randomly switched off at first. Soon got worse and wasn't turning on at all.
I was on AOSP and returned to stock once the issue started. That didn't solve it even though I flashed the stock firmware via fastboot.
However, I tried keeping the phone on recovery and it didn't die then.
Click to expand...
Click to collapse
So how many users are facing this issue? Is this too random and only solution is to get the phone replaced? I like to buy this phone in next sale, but now got in two minds, as I definitely don't want a phone with known hardware/manufacturing defect...

Well, I went all out on the device the moment I got it. Maybe that's why the issues popped up the first day.
Flipkart offers you a 10 day replacement. So, whatever your pace maybe the 10 day replacement should be enough for you.
That said, the mobile is awesome.

ya even my phone just did this once

I bought this phone for my dad on Father's day as his secondary device. He left the phone charging, then after about an hour came to me and said its not turning on, I tried everything, including trying to charge it. I ended upholding the power button long enough for it to start. I can return it to flipkart till 26th. What should I do? And if I'm to return it, which phone should I buy then.

my observation having these phone for 2 days
for the first day, i use it without any problem from 100 percent until run out of the juice. BUT, that time i havent insert my sim card which i only use WIFI to connect to internet. the battery are pretty impressive. In fact, i also updated to the newest software.
ON the next day, i inserted my sim card and use mobile data as internet sources. THEN, the phone started to unresponding whenever i left or away from it more than 5 minutes which i need to force restart and also happened during charging time. i left it about 5 minutes and the same problem happen.
When i eject those sim card, and charge it back, the phone are completely fine. All seems ok.
SO, MY ANSWER OF THESE ISSUE ARE BECAUSE OF SIM CARD RELATED, NETWORK, 4G, VOLTLTE, MOBILE DATA.... ETC.
HOPE THESE REPLY REALLY HELPFUL FOR THOSE WHO CAN SOLVE THESE ISSUE. I AM A FANS OF ASUS PRODUCT AND HOPE CAN USE THIS GREAT PRODUCTS. THE SPECS ARE VERY GOOD AND THE BEST SMARTPHONE I EVER USED IN MY LIFE.
ASUS THE BEST.

I was planning to buy this phone, but this problem is appearing like a deal breaker. Can someone provide me an opinion on whether to buy this or not?
Does the problem happen consistently right from the day you bought it?
(If so, I think the best thing you can do is to buy it, see if the problem happens, return to flipkart if problem happens.)

NagarjunaB said:
I was planning to buy this phone, but this problem is appearing like a deal breaker. Can someone provide me an opinion on whether to buy this or not?
Does the problem happen consistently right from the day you bought it?
(If so, I think the best thing you can do is to buy it, see if the problem happens, return to flipkart if problem happens.)
Click to expand...
Click to collapse
For Russian users it happens usualy on second night, but someone has a problem on 5, 6, 7 or 8 night

I don't have this problem

Everebody who faces with this issue can add some commint on ZenTalk forum for this phone model (i cant insert a link here, cause i am novice).Together we can help ASUS to see our problem faster

asus zenfone max pro ( new)-auto-shut down, not charging/getting on
Hello friends,
my new asus zenfone max pro (less than 1-month-old) was working fine till yesterday, and almost full charged.. but its showing no charging and not on... could it be same problem as discussed in this thread?
It was not shut down, but i think its auto shut down
I for sure know - the phone has been taken care off, and no fall or nothing.
Please help.
Thanks in advance,
Sunshine

I too was astonished to see that the Zenfone max pro m1 was dead after putting it for overnight charging when it was 38% and since the phone did not turn on in the early morning, by long press of "on" button, "fingerprint and on" together also did not turn on, connected to computer via USB, that too could not put it on. I removed SIMs and put into another phone and left for office. Then contacted the service centre, who welcomed for service. Surprisingly, when I returned home after work and tried fingerprint and on button together, it started booting. Then charge was 86%. How can we rely on the phone?