Related
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.
Hi all,
I've had my HTC sensation for about 9 months. I've flashed the phone twice with HD revolution roms. The last flash was conducted about a month ago and is currently running version 3.6.1. Around 2 days ago the phones screen, short cut keys below the screen, power button and volume stopped responding. Upon rebooting the phone the screen and all buttons will respond perfectly normal however. It is only when you turn the screen off or it goes into sleep state automatically after the reboot the screen, shortcut keys, power and volume buttons stop responding again when powered back on. After this the phone needs to have the battery taken out and rebooted before anything can be used again. In this state the phone is completely useless, only being able to be used once the phone has been rebooted and the screen must be prevented from going into a sleep state.
The last form of any sort of software update I can remember before the problem began occuring was updating facebook
I have not tried super wiping and reflashing a new rom yet.
If anyone could suggest something it's highly appreciated.
Regards,
Samuel
I've had the phone quoted by a repairer saying the touch screen needs to be replaced but I don't see how this can be so.
It works perfectly fine on initial boot. It also doesn't explain why all the other buttons cease to work.
Hi Samuel,
by the sound of it I'd say your touchscreen is working fine, I think its more likely that your Android OS has got screwed up a bit at some point. If it was mine I'd do a nandroid backup of your currunt OS, and then superwipe and reflash a fresh installation of ARHD on it. If that doesnt work you can always go back to the nandroid backup you make.
Probably be worth waiting to see what some other XDA members think though.
Good luck with it.
You might check your SD-card for errors.
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 have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
I
demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
I don't know why your having such an issue with cm. Which is odd because I'm running a rom that's CM based and works fine. I'd say maybe try another rom if for nothing other than to see if CM is truly the issue.
I praise you for having the unlimited data still, I wish I would be been smarter and kept mine because there are months where I'm a little too close to that sad but lack of data with 2gb
And my hometown is Syracuse NY as I see your city is there. I miss the cuse but not the loudness of the city
From my Wicked S3 on SOKP
Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...
BSOD2600 said:
Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...
Click to expand...
Click to collapse
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
From my Wicked S3 on SOKP
ShapesBlue said:
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
Click to expand...
Click to collapse
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.
BSOD2600 said:
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.
Click to expand...
Click to collapse
Yes freeze stock camera. I'm using focal and it works fine but the stock camera won't work at all
From my Wicked S3 on SOKP
demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.
BattsNotIncld said:
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.
Click to expand...
Click to collapse
I think you might be right. Even when it is up and running, I have been noticing lately that I get the power menu popping up sometimes when I wasn't even touching the power button. So last night when it was in one of its constant boot loop fits I took it apart a bit (took the back off, took out the battery sim and sd, and unscrewed the shell) and blew some compressed air all around the power button. It had been rebooting for about an hour at that point and then as soon as I put it back together it came up on the first try. So far so good.
Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])
Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.
Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway
Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...
Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.
CaptainFedora, did you solve the problem? I have the same issue...
Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.
Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.