Power button problem? - G Tablet Q&A, Help & Troubleshooting

Ok, I just got this Gtab from woot a few weeks ago
and like the next day, flashed Vegan 5.1 and the suppliment
and whenever I plug it in to charge, the screen shuts off and on and off maybe three or four times before settling on one or the other
It only does this when it's charging
also, when I wake it up from sleep, the reboot/shut down menu pops up
like I've been holding the power button 5 seconds
I'm not sure if this is a hardware problem or software, but I can't find any information anywhere
I suspect it's the button, but the button feels pretty solid, and it's not wiggling or anything and it only seems to do this when it's charging
Any advice? Since I got it from Woot, there isn't a store that I can exchange it for another one if it is a Hardware problem...

Did you do a master data reset after flashing the rom? I had some weird behavior in my home and search buttons before I did that.

Gendo3 said:
Ok, I just got this Gtab from woot a few weeks ago
and like the next day, flashed Vegan 5.1 and the suppliment
and whenever I plug it in to charge, the screen shuts off and on and off maybe three or four times before settling on one or the other
It only does this when it's charging
also, when I wake it up from sleep, the reboot/shut down menu pops up
like I've been holding the power button 5 seconds
I'm not sure if this is a hardware problem or software, but I can't find any information anywhere
I suspect it's the button, but the button feels pretty solid, and it's not wiggling or anything and it only seems to do this when it's charging
Any advice? Since I got it from Woot, there isn't a store that I can exchange it for another one if it is a Hardware problem...
Click to expand...
Click to collapse
This happens to me (and others), as well. I've just learned to live with it.
Check Clemsyn's kernels.. it seems as if they are working on trying to tackle some of these issues..?

This happened to me on Vegan 5.1.1. Im using Vegan GB experimental now and no longer have the issue.

It is definitely something with Vegan. I have found that if you press the button briefly (1 second) and then wait.. it will usually wake up cleanly. Sometimes, when yo do this it will flash the unlock screen, and then go dark again.. so you may have to repeat. However, if you hold the button a long time like you are doing, you run the risk of rebooting the thing if you hold it too long, so the short press technique seems to work better.
I am experimenting to see if running something like captivate keep alive will fix the problem.. but I think the answer may be "no".

Update for people searching for a solution;
Clemsyn's kernel seems like it did the trick. it hasnt done that since installing the kernel two days ago

Related

My Galaxy TAB 10.1 wont turn on, I need help!

I tried the different methods or hard reset, Power + Volume buttons, Power + touch screen, still nothing; I let it charge for several hours still nothing, blank screen. The product IS under warranty but I have received it as a gift and don't have the receipt, plus the person who bought it paid by cash and can not obtain the receipt from the store, what can I do , ? Thanks
I have experienced thos with my SGT on several occasions. I just let it charge a while, then press the power button down for a minute plus. It usually starts up. If not, I let it charge a bit longer and try again. Seems to be happening ever since I put pershoot's kernel on my tab. Maybe I need to update it?
Sent from a distant planet with the aid of my towel.
ButtonBoy said:
I have experienced thos with my SGT on several occasions. I just let it charge a while, then press the power button down for a minute plus. It usually starts up. If not, I let it charge a bit longer and try again. Seems to be happening ever since I put pershoot's kernel on my tab. Maybe I need to update it?
Sent from a distant planet with the aid of my towel.
Click to expand...
Click to collapse
The "sleep of death" is an issue in honeycomb itself. Pershoot's kernel should fix this not cause it. You should always use the latest version of his kernel, he works hard to fix these issue for us. Since kernel flashing takes all of two minutes there is not reason not too.
This thread is a double post.
I have experienced it two times with 10.1 Wifi and stock rom. It just would not turn on. Tried all combination. I've then waited five minutes, tried again, and it worked. It booted and the battery was at 98%. This is a really scary bug!
this happened to me before
unplug it from the charger and keep pressing on the power buttons until you see the samsung galaxy tab logo

Screen won't turn on

Hi I have been having this tablet for almost a month now. I have been experiencing when I press the power button to wake the device up, the screen won't turn on to the unlock screen. Its random but it happens to me at least 4-5 times a week. Any of you have the same issue? Is this a known issue cause I'm seriously thinking of returning this device and get an ipad instead.
I have only had my tab for a couple of weeks now, but I have had this happen to me once so far. Was slightly concerning, as I thought it had died for a moment.
EDIT: running version 3.2
Happend to me when I was still on 3.1. Update to 3.2 solved it.
my tablet came with 3.2. i have just written an email to sony. will let you guys know how it goes
happened to me three/four times in total and I had it since the launch. I used reset pin hole to fix.
Hi. I have the same problem. It can happen for 10 times a day. It's really annoying, and I don't know what to do.
Tried hard reset, but problem still remains, even when using only pre-installed programs.
Please help
Yep, I have had mine for about 2 months, never had an issue, went to go turn it on yesterday..... nothing.... so i figured the battery was dead, plugged it in.... nothing.... let it charge all night..... nothing.... tried to reset.... nothing... the light by the power button comes on when plugged in... orange charging, green ready, flashes orange when i reset it, but when i hit the power button, nothing, and the screen doesnt come on. I have had it with Sony and their piece of **** equipement, everything they have came out with since the PS3 has been junk!
I have had my tablet since it launched and this has only happened to me once. Using the reset pinhole fixed it right away. I would exchange it if this happens frequently.
After two months, this just happened to me for the first time about an hour ago... Odd. Pin hole reset fixed it.
Yeap sony suggested me to do the same it's been going ok so far. Another small issue happens to me is that it sometimes hiccup from sleep I had to press the power button twice to turn the screen on
I went to store and just ask for replacement. Now, with the new device it seems everything to be fine
The help guide is very useless yet useful for the Tab S because it says "You must access this page from your tablet." <-- It's broken, so how are we supposed to do that Sony?
But you can find a version of the help guide through loads of 404 errors, and it says prod the reset button with a paperclip (not a needle, a paperclip) and the power button will flash. Then boot up the tab like normal.
This worked for me, which is good because I thought the screen broke as I dropped my alarm clock on it. No physical damage so if I wanted to, the warranty would've covered it
I finally got my tablet back from Sony.... they said they found nothing wrong with it, but it works now, so far no issues. (this is after 2 days of me trying to get it to turn on, and about 3 hours at the store with the repair tech trying to get it to work, hence why they sent it in, and magically Sony found nothing wrong)
Try turning the screen brightness down to 98-99% and not 100% I found that worked for me

Anyone had Issues with the Display not Turning On?

I found a couple posts about this but people seemed to just return or RMA it. Thought maybe my experience might help others and was curious if anyone else has this problem.
A few times I have picked up the Prime and hit the power button and the display would not come on. If I plugged it in I would see the green light on the power button come on and go off when unplugged. It appeared to still be attached to the WIFI. If I held the button down it would buzz, but nothing else.
I found out that if I held the button down, waited for it to buzz then continued to hold it down for another 30 secs or so (seems like it takes forever) the Prime would then reboot and I would get the Eee Pad boot screen.
I have been storing my Prime in the box to keep it clear of kids and cats until I get a case. My wife ended up picking up this cheap case from Walmart which used rubber bands around the corners, and this triggered the problem by holding down the volume up button. I have not been able to reliably reproduce it, but it seems like holding down the volume button (or combo of power and volume button) puts the device in some diagnostic mode or something that shuts off the screen.
The natural tendency to release the power button immediately after the buzz while trying to reset made the device seem like it was broken. Luckily I figured out how to start it back up so I did not return it or RMA; however I wonder how many others experienced this problem.
This appears to be a software problem and not a hardware issue. I have not had this happen since I started being cautious about the volume buttons, but have not tried to reproduce on the last firmware update.
I have had no other issues with the Prime. It runs great, WIFI works for me and I could care less about the GPS issue. However, this display thing has scared me a handful of times until I figure out how to reset it.
Anyone else have this kind of issue? I was going to wait for ICS and then see if I could reproduce it before calling ASUS, but it has not been crippling especially once I figured out that when all else failed just hold down the power button until the screen came back on.
I've had this problem as well, three or four times so far. Actually, it happened to me on the first full day I had mine, and was really freaking me out. I've been using the pinhole reboot button to get it working, but it sounds like you were more patient with the power button than I was.
I can't replicate it either, exactly, but I've noticed that it's only happened after extended periods (6+ hours) of inactivity without charging. I also looked at my battery usage last night, and saw that my device constantly is awake; maybe somethint's happening when it tries to sleep?
Anyway, I feel the same way you do - I'm waiting for it to happen on 4.0(.3?) before I really worry.
I've had this happen twice. held down the power button to reboot. I can't reproduce it either, but I don't have any problem with the device sleeping. I'm at 50 hours of uptime now (15 on current charge) and have not run into it. Mildly glad to see its not just me though.
TF201 | XDA Premium
Only once tonight. Scared me until I saw the boot screen. Interesting since it has been rock solid until this. No other problems just didn't turn on. Glad to be back working.
Sent from my Transformer Prime TF201 using Tapatalk
never had that issue...have used it quite a lot in many different situations
This morning it didn't wake up. I got it to turn on by holding get down the power and volume down button. Hopefully it doesn't happen again.
Sent from my Transformer Prime TF201 using Tapatalk
happened to me tonight freaked me out for a while - had to use the reset pin hole
I've had the same exact problem andthe funny thing is I also have a case from Walmart with the rubber bands. Is yours the case logic? Since reading this post, I've removed the upper left band. I wish my case would ship already!
guys if you're familiar with transformer 1 and hacking\custom ROM tegra devices power + vol up = apx mode kind of download mode blank screen, nothing wrong with the device just working like it should. now just a blank screen with sound when u plug in could be defective screen has happened to me
Awesome to know this is expected behavior.
I didn't have the original transformer, and googling has just led me to people who can/can't get into the mode, so I'll ask here: what exactly is apx mode? I get what it's for, sort of, but what is it?
also happened to me while it was in a case. maybe the power button was pressed too long or something...
this happened to me yesterday, except the screen is still off....tried everything mentioned and it wouldnt turn back on, its fully charged...i get no buuz sound or anything...
LOL, I was just searching for a thread like this.
Mine has been working flawless for the last 4 days. This morning, would not turn on. I tried every combo and button push I could think of.
No LED charging lights, nada.
I finally reverted to the paper clip in the reset hole. Booted right up.
Don't know what the issue is.
reset button wont even work for me...
Yes It happend to me yesterday twice... i think if we leave it for an extended period without out charge , the screen is getting locked somehow... both the times i have held the power button till the buzz.. then it rebooted....
Same behavior here, was fully charged in the Morning, and plugged in, when i got home Both LED's (Dock and Tab) were green but the Screen won't turn on, pressing the Power button for 10sec rebooted the device, maybe some kind of power saving feature... hopefully it will be fixed with ICS
Okay, rockstatus90's problem seems different, but the rest of us, pceasar explained that we're likely entering APX mode, right? It's designed behavior? Now I just want to know what APX mode is, and if there's an easier way to exit than rebooting.
Happened twice for me so far.
chinly43 said:
Okay, rockstatus90's problem seems different, but the rest of us, pceasar explained that we're likely entering APX mode, right? It's designed behavior? Now I just want to know what APX mode is, and if there's an easier way to exit than rebooting.
Click to expand...
Click to collapse
Yes this is normal. Although most other Android devices seemed to give some sort of on screen message.
It is mentioned here as a process of rooting the original TF:
http://eeepadhacks.net/transformer-hacks/how-to-root-your-eeepad-transformer/
Basically, this is a mode that outputs to your PC and is supposed to blank your screen. You are supposed to reboot afterwards, so there is no other way out.
I have not had the problem since being sensitive about pushing volume+ and power at the same time.
rockstatus90 said:
reset button wont even work for me...
Click to expand...
Click to collapse
Unfortunately it looks like return or rma is your solution. I would try to call Asus and see if they can troubleshoot it. Best case they can reset it for; worse case its dead.
Really wish you could pull the battery. Thats the sure fire reboot.

Rooted Nook Completely Dead

I used Indirect's method, and everything was fine for two days. It was good this morning, but when I tried using it just now, I get nothing. Nothing at all. Completely dead. It's fully charged.
I read through some of the posts, but I'm confused about the different kinds of resets/restores, which buttons to press and hold down and what wipes what. Everyone seems to have a different version of which buttons to press, in varying combinations, to accomplish different things.
I'd like not to have to re-root this thing, so I'm hoping not to have to wipe everything out.
Does anyone have any suggestions?
UPDATE: Okay, I tried holding the power button and the two volume buttons (because I'd read that somewhere), and it started up normally and is fine... still rooted.
Weird.
for future reference if you need to do a hard factory reset hold the N button along with the power button till u see the n on your screen then let go...then do it again repeat the process 8 times
But I am glad to hear you got it working!
I had something similar happen to me last week. It reminded me of the sleep death that early GB ports were causing on cellular devices. The NT would not come out of sleep mode for about an hour, I plugged it into the charger and held down both volume buttons and the power button and it booted up -- like nothing had ever happened.
I have been unable to reproduce this behavior.
yes is just a very nasty annoying sleep death issue
I have had that issue only once so far had to just hold the power button down for a good minute to get it to boot back up for me.

Strange sleep issue after .13 update

So all seemed to be fine and dandy after the update, but I went to check something on my tablet and it wouldn't wake up. Pressing the power button, or even holding it didn't do anything; the screen was black. I held volume up and power and it vibrated, then I held it again and it vibrated again. The third time I did this, it finally booted up again.
Dunno what this means.
EDIT: Just happened again, although now I can't seem to get the thing back on. The screen is just off and vol. up + power only makes the thing vibrate after a few seconds. I simply left the prime on the lock screen and came back and it was stuck again.
Prime BT tether lockups
XHolyPuffX said:
So all seemed to be fine and dandy after the update, but I went to check something on my tablet and it wouldn't wake up. Pressing the power button, or even holding it didn't do anything; the screen was black. I held volume up and power and it vibrated, then I held it again and it vibrated again. The third time I did this, it finally booted up again.
Dunno what this means.
Click to expand...
Click to collapse
Mine does the exact same thing when I tether it to my Sensation with BT.
I'm still on 2.11.1 though
UPDATE
I just manually updated my pad to .13 this morning. It did NOT alleviate my problem but it didn't make it any worse. Unlike many other user who report the lockups when sleep now, mine still only occurs when I tether BT and it goes to sleep. On the upside, I've tested my wifi and do confirm an improvement ~20% increase in signal strength and quality.
According to dd-wrt on my router signal increased from about ~49% to 63%
and Wifi analyzer signal strength ~77-68dB to ~54-47dB. I have not tested GPS.
Apparently the build variance between pads are reflected by the variance in the effects of the update
nattylite said:
Mine does the exact same thing when I tether it to my Sensation with BT.
I'm still on 2.11.1 though
Click to expand...
Click to collapse
How do you get it back on? I can't seem to power it up now.
EDIT: Nevermind, I just held power and it turned back on after about 5-7 seconds. I think it might be a "Wifi off during sleep" issue..but idk.
XHolyPuffX said:
So all seemed to be fine and dandy after the update, but I went to check something on my tablet and it wouldn't wake up. Pressing the power button, or even holding it didn't do anything; the screen was black. I held volume up and power and it vibrated, then I held it again and it vibrated again. The third time I did this, it finally booted up again.
Dunno what this means.
EDIT: Just happened again, although now I can't seem to get the thing back on. The screen is just off and vol. up + power only makes the thing vibrate after a few seconds. I simply left the prime on the lock screen and came back and it was stuck again.
Click to expand...
Click to collapse
same thing is happening to me after the update. My prime never used to do that but something in the update screwed with it. is there anyway we can revert back?
Doubt this is an update issue as I haven't seen it yet or most others. Or they all would be posting about it. That is strange though. You all didn't root n go messing around with stuff did you? Lol. If anything I'd try a fresh reboot. Maybe even clear out all the caches. Something else is seeming to cause this. By any chance did you install chrome beta? Some users reporting strange things since installing it. I don't think its the app but it is strange though or coincidence.
demandarin said:
Doubt this is an update issue as I haven't seen it yet or most others. Or they all would be posting about it. That is strange though. You all didn't root n go messing around with stuff did you? Lol. If anything I'd try a fresh reboot. Maybe even clear out all the caches. Something else is seeming to cause this. By any chance did you install chrome beta? Some users reporting strange things since installing it. I don't think its the app but it is strange though or coincidence.
Click to expand...
Click to collapse
no I didn't root. I may factory reset if it keeps doing it and see if that works. I got a decent working prime and it would suck if this update is giving me problems. yes I did install chrome beta but this issue happened before I even installed it so that can't be it.
Ok, this has to do something with the update.
My perfectly fine from before prime wouldn't unlock. I couldn't get it to respond. (I thought it was dead..) I tried to unlock and pressed volume, did nothing.
I just read this thread and tried holding the power button and it vibrated and booted after the hold...
Asus needs to stop the patch roll out untill this is fixed...
Same problem for me. And after a short sleep, it wakes up, but there is a delay of about one half second that didn't used to be there.
-gary
After that one sleep, it has not yet repeated since last night for me
not only did mine do the same thing but it also killed my battery life while my Prime was sleeping... epic fail asus its time to return for a refund and never look back.
Maybe try reverting back and see if the problem goes away.
This hard-to-wake-up issue happened to me once after the update, but my Prime did finally wake up. Have not had the issue since. There was a lag in the wake up yesterday also, as others have mentioned, but even that seems to be gone now (or I'm just used to it).
Possible fixes for this situation:
1) Hard reset (stick an open small paper clip into the little hole just below the microSD) -- I'm sure most of you have tried this already...
And, if that doesn't work:
2) Hard reset, then reapply the .13 firmware update manually right after (assuming that is possible)
My tendency is to always do a hard reset just before any firmware updates -- makes me feel a little more confident. I was lazy and did not do that yesterday, but it won't happen again.
enough with this crap
Dude, you really gotta stop trolling, this is the third thread you are spewing this crap in in the last three I read.. You obviously are not returning it, you just like to *****.
PrimeTimeBro said:
not only did mine do the same thing but it also killed my battery life while my Prime was sleeping... epic fail asus its time to return for a refund and never look back.
Click to expand...
Click to collapse
unsure if this is the right thread, but mine's been acting up since the update as well. when i'm actively using it and turn off the screen, it boots up as quick as before to the unlock screen. however, after letting it sit for a few hours, it seems to have shut off where i'll have to hold the power button on for a few seconds (after 2 or 3 tries) to get it to boot up again as if i reset the tab.
Having the same issues with mine as well. I have installed Chrome Beta, but had it running for a few days pre-update without issue.
I almost always keep mine in the dock, but haven't had a chance to determine if it only happens in the dock or not.
i have seen this occur in the past ..before the update.. i thought the battery was dead but plugging in the charger didnt do much.. held the power+vol up 3 times finally woke up .. and said 36% battery left... i m on the verge of returning this after 2 weeks of use.. just cant get over these silly silly issues
Mine just did the same thing. I'm on the newest update. Had to hold power button 10+ seconds for it to come back.
Sent from my Transformer Prime TF201 using Tapatalk
Mine died over night with a charge of 36% in balanced mode. Had to hold the button down for 10 seconds to get it to turn on today after it was plugged in the charger for 20 minutes. Now when i wake it out of sleep there is a .5/1.5 second delay for the screen to come on.
Same issue
Had absolutely no issues with my tablet prior to this update - no random reboots, but now if it's off for a minute or more, I have to hold power in for 7-12 seconds to boot up the system.
Hey, just a thought.
Maybe also include the first few of your tablet's serial number to see if the problem is consistent with some batch(es) and not others? May help others that's going to update...

Categories

Resources