So I upgraded to JB via OTA yesterday with no problems. Today I'm reading an article on Chrome and the tablet screen shuts off and after a few seconds it looks like it's in the process of rebooting so I set it down and leave thinking it'll be booted up again when I come back but I was confused why it rebooted in the first place.
Anyways, about an hour and a half later I come back and my tablet is super heated to the point that it burns to touch it. The screen was blank but it looked like the backlight was on or something because it wasn't the same as if the screen was actually turned off. I held the power button down several seconds until it powered off and rebooted and then I set it down by my AC so that it could cool off. After a minute or so it booted up like normal to the main screen and it showed that the battery had drained from 95% when it first happened to 37% so it was obviously stuck doing something very CPU intensive during that hour and a half.
Does anyone have a clue what happened and if I should do something? I just bought this tablet from Best Buy yesterday without their additional warranty but should I either take it back there or possibly contact ASUS of a replacement or something? I know how bad that kind of heat is for computer components and it bothers me it was like that even for 1.5 hours. Also my tablet has not been rooted so it was completely stock save for the few apps I've installed so far.
Thanks in advance!
Had the exact same thing happen to mine about a month ago. Was worried afterwards that the excessive heat would have caused damage but so far have not seen any ill effects.
Falchion17 said:
So I upgraded to JB via OTA yesterday with no problems. Today I'm reading an article on Chrome and the tablet screen shuts off and after a few seconds it looks like it's in the process of rebooting so I set it down and leave thinking it'll be booted up again when I come back but I was confused why it rebooted in the first place.
Anyways, about an hour and a half later I come back and my tablet is super heated to the point that it burns to touch it. The screen was blank but it looked like the backlight was on or something because it wasn't the same as if the screen was actually turned off. I held the power button down several seconds until it powered off and rebooted and then I set it down by my AC so that it could cool off. After a minute or so it booted up like normal to the main screen and it showed that the battery had drained from 95% when it first happened to 37% so it was obviously stuck doing something very CPU intensive during that hour and a half.
Does anyone have a clue what happened and if I should do something? I just bought this tablet from Best Buy yesterday without their additional warranty but should I either take it back there or possibly contact ASUS of a replacement or something? I know how bad that kind of heat is for computer components and it bothers me it was like that even for 1.5 hours. Also my tablet has not been rooted so it was completely stock save for the few apps I've installed so far.
Thanks in advance!
Click to expand...
Click to collapse
I would just take it back. Doesn't seems normal at all!
Ok well I feel a little bit better that I'm not the only one to experience this problem. It makes me nervous that this happened so I'll probably contact Asus and see what the deal is.
Related
So over the last few days my phone seems to have settled into some sort of weird pattern with reboots. Although there are outliers, in general it always seems to reboot between 19-24h of uptime and nearly always at like 45 or 50 mins past the hour. It's the most bizarre thing in the world and why I think there's some funky software doing it. I don't have true random reboots, but I can't figure out what it is that is doing this. Very odd.
In all cases my phone is sitting with the screen off (I've NEVER had a reboot while using the phone/screen on) but it doesn't matter what radios are on, WiFi, BT, GPS (can be off or on).
Last time I ran "CatLog" a logging app from Market and had it write to SD logs and a reboot happened but it only by default writes every 200 lines so the last line in the file was probably not the last line in the log. I'm going to try again later and set it to write every line or few lines so I can see the last entry in the log before a reboot. Might shine some light on it.
Just find it very strange since it's a very stable and capable phone for about 18hrs and then it just craps on itself. Very strange.
finally. I too just think it is some weird software or driver bug because I was running EB 1.0.4 FINE for like 3-4 days and loving it... then it started resetting almost hourly. I didn't install any other apps past my initial normal set of apps.
Even CM7, seems like it is fine for a few days, then gets crazy. As long as I put a new nightly rom on it every day, it's good.
I didn't have any issues with stock though and didn't seem to have issues with CM7 for a while until lately.
The leaked GB rom causes lockups immediately out of the gate seemed hourly.
I use CM7 as my main daily driver now but I think you are on to something. We are talking about the Screen of Death right? I don't think mine ever reboots, but gets stuck at the lockscreen where the the display comes up, swiping to unlock vibrates then the phone but doesn't change screens to desktop. The buttons and click/drag widgets work even though you are looking the lockscreen.
I've never had my phone powered off in my pocket or noticed it "rebooting". Mine just has the SoD that seems to follow your pattern idea. They may be related. Stock roms may reset once it locks up, where CM7 just keeps running in its locked state.
I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.
I just hope that update gets here sooner than later.
Sent from my LG-P999 using XDA App
I dunno. The tmobile jingle is pretty loud and I never hear it. CM7 has a silent one so possibly there but I dunno.
I use my phone pretty often and never had the suspicious that it reboots. My phone stays very cool during my usage compared to my nexus and other phones
My uptime was 4 hours since I reset it last. I'll monitor it with results. It'll be hard not to flash but I'll keep track and see how far I can keep it online.
i have not had any reboots or waking up to a dead phone ....with the only fix is a battery pull.... ever since I started.
1) my over night charging / long term charging to 100%... only on the LG charger that it came with. Only short term...maybe. less than an hour and not to a 100% charge on a non LG charger (car charger etc...)
2) I restart my G2x every morning when I take it off the LG charger..(after I take it off..I did it once while on the charger and had an issue... (there is definitely an issue related to when it charges to/ around 100% charge)
Just my 2 cents.
Pattern to my reboots - do yours have a pattern?
Hold Power and volume up simultaneously for about 10 seconds.
I've had my phone since Friday, but the only time I had the rebooting problem was this past Saturday when it rebooted four times within 15 minutes or so. Before the rebooting began, the phone had slowed down to a crawl, so I went ahead and rebooted it. After that, I sat it down and watched it reboot a few times on its own. Luckily my iPhone 4 owning co-worker was completely unaware of this issue since we tease and bicker with each other every day over Android and iOS .
mobilehavoc said:
I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.
Click to expand...
Click to collapse
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.
smashpunks said:
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.
Click to expand...
Click to collapse
What bloat did you remove? I've removed most but not all of it. Can you list it?
mobilehavoc said:
What bloat did you remove? I've removed most but not all of it. Can you list it?
Click to expand...
Click to collapse
Everything other than smart share, tegra zone and qik. Of course have nova and need for speed also.
Oh also have car home froze..
Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).
player911 said:
Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).
Click to expand...
Click to collapse
Yes I know the battery driver is part of the problem as can be seen on CM7 builds but what's odd is my time varies so for a long time it would reboot every 17-20 hours, now all of a sudden it goes to 36 hours before it usually reboots. Looking at logs it doesn't appear to throw any major errors before a reboot which implies that it's a a kernel panic or low-level fault. At this point I've given up on trying to find the issue since it's been repeated over and over that T-Mo and LG are releasing an update. Might as well enjoy the phone and wait for that to come out
Amen. Just keep flashing CM nightlies and you'll never worry about it.
I really don't know if this is possible or not.... but I might need to get some new corduroys after a case of the brown adrenalin with my new sensation.
Got it Friday as could see progress on the rooting and sure enough Revolution came up with the goods same day. Rooted it Saturday.
Fully charged it, switched it off and went back to the HD2 - flip case and car kit arriving today. Really don't wanna damage my new boy toy by pocketing it with car keys etc.
Stone me though I thought I bricked it. Wouldn't switch on this morning - just a dark flicker of the screen. Sweat pouring off my forehead. Never bricked a device and flashed my HD2 & TP2 a million times and my £450 unlocked handset is 3 days old and dead..
Long and the short of it is plugged in the charger again and a few minutes later it powers up - 3% battery.
Is it possible it could drain switched off? Or should I blame the kids for messing with it and deduct my dry cleaning bill from their pocket-money?
After I rooted, I had to do a battery pull until I was able to turn my phone on again, although this doesn't really replicate what problem you had...
The battery does not drain if the phone is turned off.
Question is, was it definitely turned off?
Even if it wasn't, there's no way a full charge is going to drain overnight... Unless you had a Satnav running...
Sent from my HTC Sensation Z710e using XDA Premium App
You're right - it SHOULDN'T... I'd rebooted no problems several times after the rooting. Some OTA update came over and didn't install successfully though.
It'd be very odd (and a warranty issue, get ready to go into rooting reverse) but for now I'm inclined to just blame the kids. Unless anyone else has has similar experiences.
I guess time with it will tell.
EDIT: Apparently it's a known issue and has been fixed with the new CWM update! See: http://forum.xda-developers.com/showthread.php?t=1192300
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
EDIT: Good man. Thanks for the update. Better get onto that right away.
Yup.. that's the same experience... except I'm still on stock rom with tweaks.
What do you reckon - flash back to stock and see if it still happens? Really don't want it turning into permanent paperweight with an iffy bootloader for someone at warranty to find with their JTAG.
Morsolo said:
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
Click to expand...
Click to collapse
Hello friends. Having lots of issues with my tablet.
A while ago i noticed that my tablet was running a bit sluggish, and the brightness of the screen was flickering when on auto-brightness. I didn't think anything of it, but the next morning when I unplugged it after it was charging all night, it was at 30% after a few minutes. Every time I plugged it in it would say "charged", but a few seconds after I unplugged it it would go back to 30%. It's gotten to the point where I can't use it because it won't turn on. It's plugged in, but I press the power button and the screen lights up for a half second and then dies (i'm assuming).
I've tried other cables, etc, anyone have any ideas? I haven't been able to use my tablet the past 2 days because of this.
Sounds like it's time to RMA...
jaredmorgs said:
Sounds like it's time to RMA...
Click to expand...
Click to collapse
Was afraid of this...Kinda was hoping it would be a software issue
Think they'll care if I rooted it?
Rooting it would not cause this and I'd get in to a massive argument with anyone that claimed otherwise.
Laggyness
Credit Clown said:
Hello friends. Having lots of issues with my tablet.
A while ago i noticed that my tablet was running a bit sluggish, and the brightness of the screen was flickering when on auto-brightness. I didn't think anything of it, but the next morning when I unplugged it after it was charging all night, it was at 30% after a few minutes. Every time I plugged it in it would say "charged", but a few seconds after I unplugged it it would go back to 30%. It's gotten to the point where I can't use it because it won't turn on. It's plugged in, but I press the power button and the screen lights up for a half second and then dies (i'm assuming).
I've tried other cables, etc, anyone have any ideas? I haven't been able to use my tablet the past 2 days because of this.
Click to expand...
Click to collapse
Mine also was having the same issue. I searched high and low for a fix and finally came across a thread here on XDA that suggested deleting a corrupted jpg image that is created by the default camera 'Camera Awesome'. The corrupt jpg image sends the media scanner into an endless loop that taxes the CPU nonstop. The folder location is Android/data/com.smugmug.android.cameraawesome. I would delete any subfolders also. Hope this does the trick for you. Another tip is to stop the Blake_wakelock wakelock created by the Shield Wireless Controller which drains your Wi-Fi continually. Download the 'Disable Service' app from the google play store and once it is installed scroll over to the system apps and long click the 'SHIELD Wireless Controller Service'. From there you can disable the 'BlakeManagerService'. You can always turn it back on if and when you need to use it but that will stop your wakelocks for now. Hope everything works out for you. I was having the same trouble as you but was determined to figure it out as I did not want to send mine back cause it is my first tablet and has a lot of potential. Let me know how it goes.
Thanks for the suggestion, but the problem is I can't get it to turn on at all. Oh well, my replacement has already shipped and gets here Monday
Mine as well
Mine was working fine for 4 days. Set it down then went to power on to read book and nothing. I take it I have no recourse but to call Newegg and RMA?
Hi, i have an s6 (non edge), i do have it insured so not sure if i would be best trying to get it swapped or see how it goes?
I have had no problems up to now, been using it most of the day fine, the last time i looked at my phone was probaby about 30 mins before this happened and it had about 75% battery.
before i took my phone out my pocket and it was completely off, i kept pushing the power button in and getting no response at all, i plugged the phone into the mains and nothing happened, no charge light etc..
So i just left it connected to the mains with nothing happening for about 15 mins, then out the blue i pressed the power button in again and it come on, at it was starting i noticed it said android is updating an app (as it does when you have just installed a new fw) but this was only for 1 app by the looks, i hadn't installed anything new i can think of, not sure if thats related or not important?
Anyway my phone seems ok at the moment but now im not sure if i should just take it back the shop and get it changed seems i have it insured anyway, the phone is around 3 months old now.
Sorry, i am just editing this, i have just remembered one main point which i forgot i done earlier when reading that it can help your phone, i did go into dev options and i changed the 'limit background processes to 4' as i read this can help it, not sure if this was a bad idea?
Any advice?
Thanks
James
Possibly a defective battery.
I have a P900 that was left in a drawer for 2 or 3 years, never getting charged even once in all that time. Turning it on, I immediately realized something was wrong because it took forever to boot. The lock screen was so slow that the entire machine locked up for a few seconds, scrolling between pages on the launcher stuttered hard or locked up and everything else with the machine was generally the same. The web browser is unusable, even typing in a URL locks things up. The device is unusable.
So I thought the battery was obviously damaged, even charged at 100% it would be flat for sitting for maybe 2 hours with the screen off. I tried several cycles of charging to 100% then discharging and back up, but nothing seems to help. I don't have much money so I took at stab in the dark and got a cheap battery from ebay and it didn't help. I don't know if this battery is new, but it does seem to hold a charge like the device did when it was new but it's just still so slow that you can't use it.
However, one thing that I've noticed is that apps that don't touch the storage seem to work OK. I have a Spectrum TV app that once it starts up seems to be okay, but not great. Netflix seems to be okay as well after starting up. They both stutter a bit and rarely freeze. I don't know if this is relevant at all.
I'm at a loss of what else could be damaged or how to fix this. I'm in the process of cycling this new battery up and down, though I don't know if this would actually help. I just don't know how to diagnose this problem.
Okay, the problem was the battery, it just took a few hours of charging. I guess now that it can see it has a fully functioning battery that it's running as it should now. Android really should give you an error message about that instead of just slowing the whole thing down to a crawl, leaving you scratching your head.
This strange thing happened to me also.
I was given a tablet that was not in use couple of years. It takes about one hour on charger to start booting at all, I was thinking that it don't working at all.
Then it sits on Samsung Note Pro logo about 15 minutes, then logo changed to Samsung and it took about 15 more minutes to boot in home screen.
Then i realized that it's very slow and unresponsive, I charged it to full and reset, but it's remain the same, very sluggish.
Tried everything, reset it couple of times, flash rom with Odin, nothing helped.
After couple of charge-discharge cycles it starts to work like new!
I would never have thought that the battery could do that, but there it is.