The tendency for the GTab to reset to the viewsonic birds screen when awakened is making the the device useless to me. I'm used to using my Droid Incredible for a while, then putting it to sleep, and later picking it up and continuing where I left off.
When I set the GTab down, I have to count on it restarting on waking, which means I might as well power it down. Not every time, but often enough, and the longer it sits, the more likely it is to crash,
What is your experience?
I have run into that with various different roms. I don't know why. I was on VEGAn 3 and it didn't happen. I just updated to VEGAn 5.1 and it's happening. I am thinking about reflashing back to stock and starting over to see if it makes a difference.
I have this issue with VEGAn 5.1 but not stock rom.
I experience it also but not as often as any of you. I'm on vegan 5.1. A fix wild be nice.
Scott
vegan 5.1?
I was also running vegan 5.1. I had tried different kernals, but always 5.1 as the os. Interesting. I am now back to stock (ugh), and it has not reset on wake once. Which roms do not seem to have this issue?
I have been seeing this the last couple of days. Stock 3389 with the performance pack.
Just crashed from overnight on stock. My wife also has one, still on stock that has never crashed. I am strongly suspecting there IS a hardware issue with some of these gtabs.
Mine reset 3 times tonight on wake-up using Vegan 5.1
It seems to happen if left idle for longer periods of times, like maybe more than an hour or so. Now I'm back on Stock 3389 to see if it still happens.
I have the issue everytime on Vegan 5.1, but not 3 or TNT Lite 4. Same issues on two tabs. I love Vegan, but switched back to TNT because it's so annoying. TNT Lite 4 is very stable in my experience.
jmdearras said:
The tendency for the GTab to reset to the viewsonic birds screen when awakened is making the the device useless to me. I'm used to using my Droid Incredible for a while, then putting it to sleep, and later picking it up and continuing where I left off.
When I set the GTab down, I have to count on it restarting on waking, which means I might as well power it down. Not every time, but often enough, and the longer it sits, the more likely it is to crash,
What is your experience?
Click to expand...
Click to collapse
Using VEGAn 5.1, I experience the same problem. If I let the device idle for more than an hour or so, it seems to restart instead of coming out of standby mode.
Hey don't get me wrong, it's better than the old lag-on-wake issue, but it definitely limits the usefulness of the tab.
Out of curiosity I upgraded to Clemsyn's TNT 10.9.8 kernel (http://forum.xda-developers.com/showthread.php?t=895825), but am still having the same issue.
I am now using Vegan 5.1 and Pershoot's latest 2.6.32.28 - VFPv3_FP - Gtab/Zpad kernel, with everything wiped clean, and it has all but eliminated the problem.
Jim
Both my tabs now do it on TNT Lite 4.0. Very frustrating... this is my biggest complaint right now. I guess I need to go back to older roms.
Has anyone tried to debug this or give VS support a call (since I saw it on Stock (w/ the performance pack of course))?
have any of you tried using the volume buttons to wake it rather than the power button. Mine likes to flash on and off when i press the power button to sleep as my fingers like to find the back and home button when im holding it with one hand to press the power.
Also, ive heard that the "power on" length, and reset press and hold length are really short on vegan 5. try just jabbing the power button and not pressing it till you see it do something.
Mines on 5.1 and i dont really ever have it reset, but Im aware of these 2 and usually either jab the power button, or use the volume button
jmdearras said:
I am now using Vegan 5.1 and Pershoot's latest 2.6.32.28 - VFPv3_FP - Gtab/Zpad kernel, with everything wiped clean, and it has all but eliminated the problem.
Jim
Click to expand...
Click to collapse
Thanks for this info. Yesterday I restored my backup of Vegan 5.1 and then installed Pershoot's latest kernel and haven't had the reset on wake problem since. It appears to have fixed the problem for me.
So do you think this could be resolved by going to Vegan or simply Pershoot's kernel?
Could you that have fixed this issue, post the exact version of the kernels you are running? I have tried 4 different versions, but still can't get it to wake without reboot.
Thanks
Gudy
Related
i realize that there are a few threads on here about the gTab having to be powered on after it goes to sleep.
mine on stock and vegan will not resume from sleep ever after about 5 minutes.
is everyone having this issue? i would really like to hear from people and hope that most people do not have this problem.
if i see that it seems to be rare then i am going to get a replacement for mine while i still can from Office Depot.
please respond if you do or do not have this issue and what OS you are running on it.
thanks for the help.
I have two devices, both running the same VEGAn b4 build. One is a first batch from early November (SEARS), the other is a newer device from early December (also SEARS). They are both used.
The older device has a tendency to shutdown or freeze when idle for a long period. I have to hold down the power button for a few seconds and it will power up. The newer device never seem to have this problem - it actually goes to sleep and stays asleep. But, if I manually put the device to sleep, it's OK. I have not been able to figure this out yet, but perhaps the insides are a little different.
i am going to do the following test to see when it does not wake up. i am currently running latest updated stock only because i was trying to eliminate it being a vegan or TNT problem.
for the test i am going to wait 15 minutes or more to try and wake it up with the following:
1. letting it fall asleep by itself which i have set on 10 minutes.
2. power button it to sleep.
3. tap power and hit the sleep in power options widget.
thanks for the reply and some other user results would be great.
UPDATE!!!
well i didnt even have to wait that long. my gTab failed to wake up already from all 3 different ways of putting it to sleep.
i am going to exchange it. though not a deal breaker i wouldnt mind seeing if a new one might work right.
I had similar sleep/shut down issues with the original stock ROM but since the 3053 update, no problems sleeping...
Well after trying everything possible I exchanged it and works perfectly now: )
Does this still happen to anyone else? It happens to me quite often (almost once a day now) and it's getting very annoying.
By the way it's when the screen goes off and sits after about 30mins and when I go back to use it, it wont come back on unless I hold the power button for about 5 secs to boot it back up.
I never had a SOD problem. Not with stock Honeycomb and not with custom roms.
Did you root our Transformer and trie custom rom or do you whant to stay on stock rom?
Sent from my Transformer TF101 using Tapatalk
Not rooted!! Stock since day 1
I had it all the time with my 3.1 stock, 3.1 stock rooted/cwm'd. I have not had it happen since I updated to 3.2, but I also put Prime 1.7 immediately after the 3.2 update, so I can't say if it's 3.2 or prime that fixed it. I'm on day 3 with prime 1.7 so I suspect it's gone, but SOD probably occurred every couple of days. So not 100% sure it's gone, fwiw.
Ugh...it's already happened twice today...I'm beginning to think I have a defective device...I love my tab but its getting annoying. It stopped for a while after 3.2 but it's back with a vengeance
Hey everyone my phones power button started glitching up a few weeks back. When I press it to unlock the phone it dosent work sometimes then other times it will turn on with the power off menu up.
When I try to lock the screen it sometimes will turn off then turn right back on. It is quite annoying. I am currently running Cyanogen 7 but was running AR HD a few days prior. The roms dont seem to change the issue. Any ideas?
this used to happen to me pretty often. might be hardware might be software issue or a combination of both. i dont use cm7 but using faux or stock kernel in the development thread fixed the problem for me. i heard bricked also has the fix as well. you said you tried arhd but you still had the problem? the latest faux kernel and stock kernel have solved the problem for me. never happened since
There has been a lot of talk about the random reboots since ICS, but i have a slightly different problem. Since updating to ICS i've had a few random shutdowns....i think, it might be that it freezes with the screen off, i'm not sure which. ive never seen it happen when i was using it, the battery is never dead, i just try to turn the screen on and it won't. I have to hold the power button down for it to do either a reboot or a boot from scratch not sure what it is.
here is what i have
- stock transformer (rooted in HC to fix left speaker volume)
- upgraded via ota to ICS (seemed to work correctly)
- not overclocked
- no other hacks
- haven't done factory reset (don't want to, but might if it keeps happening)
Has anyone else seen this since ICS ??
I haven't had that problem but I've had a lot of others from bootlooped, to the whole tablet freeze... I'm on stock ics and factory reset didn't help what so ever........
Sent from my ADR6400L using xda premium
http://forum.xda-developers.com/showthread.php?t=1518552
nonoheran said:
http://forum.xda-developers.com/showthread.php?t=1518552
Click to expand...
Click to collapse
I started to read through that thread (lots of pages there), i didn't notice anyone with the random shutdown on there that's why i started this thread, just in case it started happening to other people too.
I will try some of the suggestions on there to see if it goes away.
Same issue here - it is either freezing while the screen is off or shutting down. Only way to get it to respond afterwards is to press and hold the power for 10+ seconds, release, and then again for 5+ to turn it back on.
I've reset to defaults with no success. Running stock rooted ICS.
Same issue!
I've noticed this happening on my tablet too.
Mines completely stock in every way, never rooted or modified in any way from stock.
After the ICS update I've noticed that... probably once a week or so I'll go to turn on my tablet only to find that it's essentially turned off.
There was plenty of battery, and no obvious rhyme or reason for the shut down ?!?!
Same here. Stock TF101, after ICS upgrade device doesn't respond to wake button. Plenty of battery. You have to hold the button for a way longer than just a power on press.
I've started having the same issue after updating to ICS. Sometimes it's random reboots and other times I'm getting this shutdown issue.
I have this problem too.
I try to fix this by changing the ROM but all still get this problem.
Stock ---> RevolutionHD ---> EOS with cornerstone 4
I have had same problem with the random reboot/boot loop problem with ICS and I have tried stock unrooted / stock rooted / Revolver / RevolutionHD. All do the same thing. If I have the screen off for extended periods of time, it reboots and gets caught in a boot loop. The 10+ then 5+ button hold works to get it restarted. I am trying different apps to see if one is the cause. Most of the time I seem to remember that I was browsing just before shutting the screen off.
Will let you know if I narrow this down as I have multiple browsers installed. Note: I mainly use Chrome and FireFox Beta the most, will try removing those and testing.
Sent from my HTC MikEVO
Same here, having random shutdowns and sometimes when I lock my screen it restarts and get stuck at the bootanimation.
Also it often reboots when I use Splashtop remote. It works well, then I touch the screen and it restarts...
I hope Asus will fix this as soon as possible, but i think it will take a while.
I believe this has to do with the power management issue. I've noticed that after being unplugged from the power supply. The tablet will stay on. Once when the power level dips below a certain percent, the tablet automatically shuts down. When it reboots, sometimes the wheel will stay stuck. The only way to keep the tablet powered on is to have the cable plugged in. That defeats the purpose of a portable tablet, might as well get a EP121 then.
I've had my TF300 for a few months now. It's been unlocked since day one, and is currently running CM10 stable (probably going to try a 10.1 Nightly today). Recently it has been randomly shutting down. No warning or anything, I'll just be watching a video or browsing the web and boom, it's off. Screen is black and everything.
This wouldn't be THAT bad but it doesn't automatically reboot, and it's very difficult to get it to boot back up. I've tried holding the power button for over a full minute, every combination of vol+ and power and vol- and power, and most of the time (not every time), nothing seems to do the trick but sticking it on the charger for a while and leaving it alone. Then I'll just hit the power button like normal and it will fire right up. It's done this 3 times now.
So what do you guys think? Hardware or software issue? And despite being unlocked, do you think ASUS would warranty it if I restored the factory image, if it is a hardware issue?
Have you got it overlocked? If so, try turning the tablet down. Watching videos may be too much for the tablet if it's overclocked. Another way to see if it's software or hardware is to switch ROMs and see if it still does it. If so then it very well may be hardware related.
As for the the warranty, from what I understand, Asus will still cover hardware issues even if it's unlocked. I do not know from personal experience, only from what I've read here from other members.
Sent from my LG-LG855 using Xparent Green Tapatalk 2
wetbiker7 said:
Have you got it overlocked? If so, try turning the tablet down. Watching videos may be too much for the tablet if it's overclocked. Another way to see if it's software or hardware is to switch ROMs and see if it still does it. If so then it very well may be hardware related.
As for the the warranty, from what I understand, Asus will still cover hardware issues even if it's unlocked. I do not know from personal experience, only from what I've read here from other members.
Sent from my LG-LG855 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Not overclocked, it was a thought that occurred to me, too, but it's just running the included CM kernel at the stock speeds. I'll give CM10.1 a try tonight and see if that resolves it. Thanks for the advice.
So I think I figured it out. This thing is straight up not reporting battery stats. I let it fully charge last night, and now after unplugging its been at 100% for about an hour of straight use and two (normal) reboots. Tried deleting batterystats.bin but it made no difference. I'm going to run it down and see what happens...
Still no go. It was totally fine until the battery hit about 45%, then shut off and was unresponsive. When I plugged it back in, the light blinked for a few minutes, then I was able to power it up like normal. Has the battery gone bad?
Try Installing STOCK ROM
I have the similar issues with CM10. But it doesn't happen when I am using it(playing games, surfing internet or watching movies).
It happens only when the tab is not being used for more than 2-3 hours. Pressing Power button doesn't do anything and I have to press the power button for at least 1 minutes to get it rebooted.
I installed Stock 10.4.2.18 rooted(http://forum.xda-developers.com/showthread.php?t=2033205) and I don't see that issue anymore.
Now I am trying CleanROM Inheritance 3.0.4(http://forum.xda-developers.com/showthread.php?t=2049322) to see how it goes as it is based on the Stock ROM.
Same exact happened to me yesterday...i was scared for a min or two...it finally booted back and been fine since...im on cleanrom unlocked and rooted no overclock
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I have the same problem, and my non-scientific observation leads me to suspect it was worse on the stock ROM. Also, I have this problem where wifi will not work (upon waking the tablet, it says wifi is off, though I had not turned it off), and I have to reboot it in order to get wifi to connect. I don't know if the issues are related.