Hi everyone, just got the tablet today and set it up at work, played with it for bit and everthing was working fine.
Got home about 2 hours ago and now when I wake it from Sleep, the touch screen is not responding at all. Have tried everything, power is 98%, plugged into a PC, did the hard reboot, even wiping the data to start setup again. But all to no avail.
The screen isn't responding at all. Its very frustrating as I want to play with it some more!!!
Hope someone has experienced this and can help.
had the same issue once...i turned it off and left it for about 5min...turned it on and the screen works again...
this hasn't occured since then..probably just a system glitch..
Happened to me once, reset the device and it worked. Now it happened again and its been unusable for a day. If it doesn't work tonight, the $hit is going to hit the fan...
Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.
Have you guys contacted ASUS support? They will probably have you RMA it. How long did you guys have it before this happened? Now I'm worried that mine will do the same thing.
ASUS support did want to RMA my TF that was having this problem. However, after leaving it off for a couple hours, I went to turn it on to wipe out all my account settings and the touchscreen started working again.
I have no explanation for why it started working though. The last thing I did before it was magically fixed was go through the normal shutdown procedure by answering the 'do you want to shut down' using the dock's mouse instead of just holding down the power button. Maybe that made a difference?
Blue_Man said:
Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.
Click to expand...
Click to collapse
This is what happened to me. Stuck at the lock screen, no touch at all. After 4 days of waiting for Asus to reply to my email and several disconnected phone calls, I have returned it to newegg. Since this item is still out of stock I expect to receive a full refund. Which is fine by me. June 8th, here I come.
Same thing happened to me, just returned it to fry's and was able to avoid the restocking fee. Going to get the galaxy tab come june 8th now instead.
Sent from my Xoom using XDA Premium App
I have weird little quirky things like this happen from time to time with my TF, such as having to hit the power button or lock button twice before it works. I think it might be more of a software issue than anything to be honest. Hoping that future updates will correct all of these issues.
I hope its a software issue....
Found a solution that worked for me. I booted into recovery mode by holding vol down and power. then I selected vol up to enter recovery. Then the exclamation point came up with the android robot. I left it like that for a few minutes then held down the power until it resarted.
It booted up like normal, no data lost. I then restarted for good measure. Came right back up like normal, touch screen and all.
Thanks jdmnash. I followed your instructions and it worked like a breeze. Should make this part of a sticky help thread.
Found a solution
Update: Tried every fix I could identify on the forums as I was also draining the battery as suggested on several forums. After 4 days waiting for the battery to drain, I was able to restart the TF and get active responses to the touchscreen. Unfortunately I had performed a reset and wipe earlier so I am having to reload everything. I am happy to have a functioning TF again, but have serious concerns about this failure and this awkward repair method. Additionally, I have still not had a response from ASUS support from 5 days ago.
Mine is constantly doing this. Randomly.
Its as if the daemon for screen touch detection crashes. The rest of the unit is fine but that stops and the only fix is a power button off, then on.
Something is not right here. Its vanilla out of the box, no extra software just the 13 FW update.
Will 3.1 fix this? Hopefully, as it stands, this will have to be returned. It is not fit for purpose, constantly failing.
same problem
Just picked up mine. Out of the box at a cafe it worked just fine. Brought it home and same problem as everyone else in this thread. Have tried all of the suggestions in this thread (except waiting for the battery to die). Even installed the 3.1 update via SD. Still no joy. Guess I'll try a few more things before returning it. My guess is a problem in the supply chain with the capacitors that detect screen touch. Doubt that it can be solved solely through a software update (or if it can it definitely didn't make it into 3.1)
my touch screen stopped working a week ago while i was at school. and i got really pissed and just kept on rebooting it and after like 5 or 6 reboots it started working. Havent had same problem since.
Hmm... thanks for suggestion. Tried booting it about 5 times but still borked. Draining the battery now as my last attempt before taking it back.
Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.
Unstable touchscreen
obi-nine said:
Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.
Click to expand...
Click to collapse
Hi , After the battery is zero and then 30 minutes charging, in order to make it work , did you discharge it right after 30 minutes or still you keep it charging ?
I got same problem with my TF which is really a disappointment.. I tried to factory reset, reboot ... but still can't make it work. I have to try this trick by draining the battery to zero. Hopefully, I get advise from all of you for this problem ?
Thanks a lot
Can you guys try using ADW launcher and see if things improve?
I think it did for me.
I've been running CM 10 on my phone without issue (besides the whole touchscreen thing that wasn't a big problem for me) for several months.
I went to cm10.1 last week and my phone started having graphical artifacts on occasion (like an overheating gfx card) and eventually started shutting off randomly and restarting with 50% less battery than it had. I did a full wipe and put back on CM10, but it's still doing it, and has gotten progressively worse.
For the past couple of days my phone would work for about an hour, and then shut off and either come back on with 50% less battery, or not at all until I plugged it in for several hours (even if it had just been plugged in all night). Now, my phone has been plugged in for 24 hours and I can't get it to turn on at all. I've held the power button for 30 seconds, held power+down, etc.
When it was on it's last legs I wanted to do S-OFF and then go to stock so I could do the warranty, but the S-OFF process hanged when trying to push the first file.
Any help?
Thanks
slash178 said:
I've been running CM 10 on my phone without issue (besides the whole touchscreen thing that wasn't a big problem for me) for several months.
I went to cm10.1 last week and my phone started having graphical artifacts on occasion (like an overheating gfx card) and eventually started shutting off randomly and restarting with 50% less battery than it had. I did a full wipe and put back on CM10, but it's still doing it, and has gotten progressively worse.
For the past couple of days my phone would work for about an hour, and then shut off and either come back on with 50% less battery, or not at all until I plugged it in for several hours (even if it had just been plugged in all night). Now, my phone has been plugged in for 24 hours and I can't get it to turn on at all. I've held the power button for 30 seconds, held power+down, etc.
When it was on it's last legs I wanted to do S-OFF and then go to stock so I could do the warranty, but the S-OFF process hanged when trying to push the first file.
Any help?
Thanks
Click to expand...
Click to collapse
If it won't power on, screen won't turn on, power led doesn't light up even when plugged in, it's bricked. Sounds like you've got some serious hardware issues.
A few days ago, my phone got pretty hot while I slept. But everything seemed fine until last night. I only bring up the heat because that's literally the only thing I can think of that might have caused this problem, even if there were a few days between that event and when the phone started behaving strangely.
Status:
Verizon SGS3. On CM11 nightly from about a week ago with the kernel it came with.
Issues:
I can't boot the phone. It'll quickly show the Cyanogen logo and then shut down again. Even if I'm on the charger, it'll just shut down. The battery will sometimes show 0% and charging, then I'll try it again a couple of minutes later and it'll show 87% and charging.
I did manage to boot the phone a couple times. It lasted long enough until I was able to get to the main screen. After a couple minutes, the power menu started flashing on and off showing the reboot/screenshot/power off menu. Like very quickly. Then the screen started turning on and off rapidly.
One of the times I managed to boot the phone, I was able to do a factory reset from settings. I reset it. The problem persists. I've tried two different batteries. Both batteries work fine in another SGS3 I have, but not in the one that's causing all the problems.
Any ideas?
Picked up my phone off the charger today (1 week old 128g pixel 3) and it just shutdown. Almost like the battery died, but it was 100%.
Turned the phone back on, booted "normal", ran about 30 - 60 seconds and shut off again!
Turned on a 2nd time, actually started ringing immediately after boot, was able to complete a full phone call then it shut down after the call was completed.
Turned on a 3rd time, made a phone call - same behavior, lasted for the whole call then shutdown.
Tired safe mode - same thing.
Went to bootloader - seems to stay alive for a long time (~1 hour) - thinking it's not hardware... tried factory reset. Reboot phone and it makes it 30-60 seconds and shuts down!
Anyone else seeing MAJOR hardware issue like this?
Same problem for myself. Started yesterday morning. Phone was just went dead after using it a couple of minutes. Called Google Fi support and getting a new phone. Phone was dead to the world. The PC would not recognize the phone when plugged in. After the phone sat for several hours I got it to power on. Started that bootloop thing so I tried restoring using twrp. The was a no-go. Then reflashed the stock image (with out the -w). No go as well. Unfortunately the phone went dead again before I could just overwrite the phone. Going to try again this morning if the phone powers on again. If not back to Google.
[UPDATE] Nuked the phone(flash-all with -w), and reloaded the Nov. firmware. So far so good. Currently going through (slowly since my WiFi is slow as molasses) the updates and restore now.
I have a HTC 10 (new old stock) that I have been using for 2 months, on stock Oreo.
Everything was fine until last week when suddenly in the middle of reading an email the screen froze, a few seconds later the screen went black and would not boot up. Nothing at all, not even with a hard reset VOL DOWN + POWER or VOL UP + VOL DOWN + POWER. Tried holding it for A LONG TIME like 5 minutes, no luck. The phone had a hard brick and that's it.
Occasionally, after a few hours, I would try to reset it just for the hack of it. Or connect it to a charger (no charging light) Eventually after about 20 hours, it booted up again after I held all three buttons for a few seconds. Then it worked like nothing has happened.
It kept running for several hours, I charged it up to 100%, ran down to about 80%, then the screen froze again and died. Same thing happened, won't boot up at all. But if I wait another day or so, kept trying, it will boot up again.
I know the HTC 10 is known for it's horrible battery drain issue, and I have experienced that myself with another HTC 10, this is not it. The battery is running fine on this one. This is something else.
After doing this for a few iterations, I was able to figure out a pattern.
When the screen froze and the phone dies, it will not boot up no matter what you do. But for some reason something is still going on as the battery is still being consumed, a day or so later, when the battery is completed depleted down to 0%, and as soon as it hits 0%, whatever causes it to not boot unlocks and allow it to boot again, as long as you have it on the charger, the charging light will come up at that time, and as soon as it gets a little bit of juice, it will boot up again normally. Except when it does boot up, the date is reset to December 31, 1969 7PM.
After testing this for two more iterations, I am reasonably sure this is what's going on. Then I did a factory reset.
Once it's factory reset, I did nothing except turned on WIFI and didn't do any further setup except surf the internet a bit on WIFI, and about 10 hours later, it died again. Now I know, if I leave it alone for 20 hours, then plug it in for a few minutes, it will boot up again.
So here are my questions.
(1) The phone appears to have bricked during the 20 hours that is was totally non-responsive. What is happening that's consuming the battery?
(2) Does this seem like a hardware issue or software issue?