Database Info

[Q] Screen not responding to touch

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.

[Q] Nexus Fails to Stay Powered in System

Background: I had my completely stock Nexus 5 on the charger for around an hour. When it got near 100%, it locked up for about 5 seconds and powered off. It wouldn't charge or power on again until 2 days later where it would power up but not charge. It could go to the bootloader/recovery but it would still shut down. The charger used won't charge anything anymore, it may have been a power surge that messed it up.
I replaced the battery and the system is still unable to maintain power but recovery and the bootloader are stable (just formatted the cache and the phone did not power off, took around 15 minutes). Now it won't power up again.
Any idea what the issue could be? Could it be corrupted data?

First, try another cable and charger.
Also, make sure you have enough juice on the device first, reflash stock firmware with fastboot and see if the issue remains.
If you successfully flash your stock firmware and use another known working cable and charger and it's the same.... Then unfortunately it could be a hardware issue.

Thanks for the reply.
Unfortunately, that didn't bring my N5 back to life. I'm think a circuit may be fried on the motherboard but I don't have a real way of judging that at the moment.
Any chance you might be able to guess what the hardware issue could be? I'm mainly trying to save the data on my phone and I'm not against taking the phone apart to do that.

Update: I took the phone to a Sprint store and a technician looked at it. When the tech plugged it into the charger, the phone LED was flashing red with no charging screen. It eventually booted up and shut down. Later that day, I could see my notifications (Pushbullet is a wonderful app) and noticed the phone stayed on consistently. He said everything was fine and their formal report didn't mention any sort of damage to the phone that they could find. Later that same day, it died again. Today, I decided to completely wipe and load 5.1 to the phone. It stayed powered on through the whole flashing process (bootloader unlock and individual partition flashes) but shut off during "optimizing apps". Considering it powered off in the system, I'm thinking the issue is with the RAM or the CPU possibly being fried due to a power spike while on the charger. It seems like it only happens during heavy operations.

Something hardware it seems. Not sure what, but if a component on the mb is bad then it is a replacement.
I like the title though, doubt anyone has a device that stays charged while in system. Sorry about your phone, but made me chuckle. I really can't think of a better way to describe it, not trying to pick on you.

HTC One M8 reset itself?!

The other day, my phone died midway through a call. When I tried to turn it on, the 0% sign showed up meaning it was completely dead. I had to urgently make a call so 30 mins later, I held the power button again, turned it on, and the phone went to the white HTC screen and then turned off. I finally got home and connected to my phone to my charger after. I let it charge for a bit then turned it on. I knew something was wrong when my phone was hung on the red Verizon boot logo for a while. Minutes later, it went past the Verizon logo and a pop-up appeared that said optimizing app 1 of 44. I thought this was odd because I already got the MM update about 2 weeks ago and since it updated, I never saw that message ever until now.
Once my phone gets past that and finally boots to the homescreen, I realize that a lot of things have gone wrong. First, I got signed out out of all my accounts (Whatsapp, Spotify, Instagram, Facebook, etc). On top of that, my call history was cleared, all my text messages were cleared, and all my contacts that were saved on my phone storage were gone. In addition, I also had to re-update a lot of apps including the HTC ones that you have to upon the MM update. Finally prior to those whole thing happening I had 10.7gb of free space. After this episode, I lost exactly 1 gb of storage and only have 9.7gb free.
I don't understand what could have caused this or why I lost all this data on my phone. Moreover, it doesn't seem like anything was deleted but my phone is just not reading anything that was already there.

mine just did this exact same thing after shutting off from a drained battery. It's like the data partition or whatever got wiped. Right now trying to log back in to everything and set EVERYTHING back up again. This sucks.

baune7 said:
mine just did this exact same thing after shutting off from a drained battery. It's like the data partition or whatever got wiped. Right now trying to log back in to everything and set EVERYTHING back up again. This sucks.
Click to expand...
Click to collapse
i came here for the same thing. mine happened around the same time. only thing i can add here is that my storage is almost maxed out on the phone. makes me wonder if that had something to do with it. but then this happened to two other people around the same time. very weird.

The exact same thing happened AGAIN! I was at the gym listening to music and texting some friends while my battery was at 15%. Went from 15% to 10% in a matter of mere minutes and then from 10% just shut off. Couldn't charge it until I got home so I just kept it in my pocket. Got home about an hour later, put it to charge and then turned it on when battery hit about 10%. Same damn thing, got stuck on the Verizon boot logo and then the dreaded Optimizing Apps message showed up. Once it finished, I was logged out of all accounts, updates to system apps were gone, and widgets/BlinkFeed were gone/reset. And just like last time, suddenly 1GB of storage was gone.
Literally un-freaking-believable. I dreaded that it would happen when my phone shut off and yep, my fears were right. Going to do a factory reset once I backup everything. From there, I am debating whether to replace the battery or replace my phone. While it sucks that it happened to you guys as well, I am somewhat glad its an HTC issue and not just an issue with my personal phone.

Same thing happened to me at 40%

This was recently brought up in the viper rom thread, could be of help.
TidusWulf said:
Your battery needs to be reset. Hold down POWER + VOLUME (can't remember if it was up or down. takes about 10 seconds)and let it keep resetting and keep holding it for 3 minutes. then let go.
It'll fix your battery so that it drains to 0 instead of 13, but it doesn't fix the weird pseudo-reset problem. It's a known issue and many people are struggling with it. My advice is to set EXTREME POWER SAVER to auto-on at 10%, and if you ever see it that low, just turn it off yourself until you get a chance to charge it.
Click to expand...
Click to collapse

Same thing has been happening to me since the MM upgrade. Before that I had NO issues with my battery so I find it hard to believe that my battery is the problem.
After the third time of this happening I finally decided to to a factory reset. This did not help, phone continues to die anywhere between 15% - 30% and revert some of my settings back to stock.
This is driving me insane as I rely on this phone for personal and work use.
Decided to call HTC support today, I did not expect a solution but wanted to make sure it was reported. Of course they had no idea and claimed to have never heard of this issue.
I am guessing that since the M8 is over two years old we wont be seeing and fix pushed out for this issue. I really like my phone and dont want to upgrade at this time.

Finally somewhere where people are actually having the same issue. I've tried factory resetting the phone, doing a fresh install of the OS (with firmware recovery tool) all with no avail. I note lose all my settings and app configurations every time the phone dies, shuts down or restarts. I hope there's a fix, otherwise it looks like a custom rom is the only way.
Has anyone tried wiping the dalvic cache? I can't get into the recovery on my phone so I can't try it, but heard I it might help.

Had the same issue last week
I was at about 20%, phone shut down. I plugged it in to charge, went to boot it up, and it got stuck on the Verizon bootup screen.
I waited a while and did a hard reset, and it came back on, but was completely wiped. So I had the same problem, which is a real pain, because I use the GOOD app for work, and each time that re-installs I have to get a new PIN. And I have had to re-install the app a few times in the past month for a variety of reasons...

Teevan said:
I was at about 20%, phone shut down. I plugged it in to charge, went to boot it up, and it got stuck on the Verizon bootup screen.
I waited a while and did a hard reset, and it came back on, but was completely wiped. So I had the same problem, which is a real pain, because I use the GOOD app for work, and each time that re-installs I have to get a new PIN. And I have had to re-install the app a few times in the past month for a variety of reasons...
Click to expand...
Click to collapse
I feel your pain. I use Mobilepass for work and every time my phone resets it deletes my token and I have to request a new one.....
Here is what I did two days ago that seems so far to be working for me. I calibrated the battery. I have tried this in the past but could never get the calibration to work properly. Each time I tried I had the phone plugged into the charger. This time I didnt and the phone went through the battery calibration process like it is supposed to.
Since I have done this my phone will stay on until it gets to 8 or 9% and then shut down but when i charge and turn back on all of my setting are still in place.
To calibrate the battery I held the up volume, down volume and power button (all 3) for a full 2 minutes without the phone being plugged in. During this time the phone will start and get to the HTC splash screen then shut back off, start again to the HTC splash screen then shut off, repeat, repeat, repeat.... after 2 minutes release the buttons and let the phone boot up, plug it in and let it charge to 100%.
I hope this helps,

This happened to me today. I let the battery get a little lower than usual last night, around 13% before shutting it down and plugging it in for the night. Turned it on this morning and it booted up normally. Didn't lose any apps or data, but every time I did something on the phone it gave me those little hints like its a brand new phone. I went to settings and it says it was factory reset at 6:46 a.m. this morning (about the time I turned it on).

Parakaleo said:
This happened to me today. I let the battery get a little lower than usual last night, around 13% before shutting it down and plugging it in for the night. Turned it on this morning and it booted up normally. Didn't lose any apps or data, but every time I did something on the phone it gave me those little hints like its a brand new phone. I went to settings and it says it was factory reset at 6:46 a.m. this morning (about the time I turned it on).
Click to expand...
Click to collapse
Did it reset your ringtone and notification tone settings? Thats what it always has done to me.

I would just like to say that the same thing happens to me as well on my HTC one m8. Battery suddenly dies, now even at 25%, even after a calibration which is just a temporary solution, and when I turn the phone again, SwiftKey settings erased, everything went to stock, messages and contacts are preserved, but the apps start updating itself even though they are not allowed to and I have to manually set a lot of things. It is a total confusion and I literally can't believe HTC allows themselves to not issuing a fix for this disaster.

Was it cold?
Same issue. With mine it seems to be when it gets cold. I was skiing today in 20F but inside my pocket this really shouldn't be an issue. It has turned itself off and refused to restart several times when it has been used to take pictures in cool weather (I live in western OR, it doesn't get COLD, by cool I mean <35F but >20F, usually > 25F). This is the third time it has totally screwed up the phone when it has happened. On another occurrence it reset under normal conditions too. I'm getting pretty sick of it as it is quite a process to get all my VPN tokens reset, get all the apps back etc. Of course it waited until the warranty was out to start acting up.
This time is especially bad, the phone will not restart properly and important processes just constantly flag as stopping so that I can't even get past the initialization screen. It looks like I will have to do a full factory reset. If anyone from HTC is reading...Not acceptable and I won't be buying another phone from you.
Unfortunately I've reached the point where I wouldn't be surprised if it is a programmed planned obsolescence function, but whether or not, this is really annoying behavior.

Sorry to hash up an old thread but I put up with this crap for 5 months before I finally punched and broke the screen out of rage during an important business tech support call when I was at the clients location trying to service their security equipment, it was so embarrassing having to tell them I have to come back especially since it was a remote location.
Mine would wipe contacts, texts etc regularly. I ended up installing Super backup or something and saving my backups on google drive and just restoring everything everytime it happened.
I decided to fix up the phone and replace the battery, broken charging port and smashed screen and unlock bootloader and root but flashing superSU didnt work, got stuck in a bootloop. Anyways through all this I wiped all the caches (including Dalvik cache) flashed the correct stock rom and did the battery calibration and that seemed to have solved the random shutdown and memory leaking issue.....but I guess I wont know for a while.

I have a HTC One 610, and like every once in a while it well automatically reset it self whenever I am in the middle of a text message, on facebook, or even sending an email on phone. Its getting annoying when my cell reset its self.
what needs to be done to it? and should I do.

PRINCESS2017 said:
I have a HTC One 610, and like every once in a while it well automatically reset it self whenever I am in the middle of a text message, on facebook, or even sending an email on phone. Its getting annoying when my cell reset its self.
what needs to be done to it? and should I do.
Click to expand...
Click to collapse
try a factory reset

I know its old but people are having the same issue still so I'm gonna paste this everywhere i find this problem.
There is a Modified stock rom named "Android_Revolution_HD-One_M8_53.1" and its almost the stock M8 without bloatware and so much more stability improvements. So hear me out and flash it with a custom recovery (i did it with twrp) and it seems to be working fine so far. Give it a go before you trash your -still so good- phone to the open seas.

Well, this issue is still happening. my phone has been doing the same for about a week now. ive made several attempts to reset the battery and had to reinstall back ups every time its happened also. the only difference i think now is that its happening at 90% instead of the usual 15%. ive been following instructions to hold volume up, down, and power (with the phone off) for about 2 minutes and then letting go. i have my extreme power saver set to come on at 15% but Im not even getting that low before it shuts off and resets. i have however noticed that recently that if you plug the phone on charge after it first dies you can avoid the phone resetting.. this may be a fluke but its allowing me to deal with the battery problem now without the loss of my data, contacts, etc.

This is exactly the reason why HTC One M8 is the last HTC phone I will ever purchase. Imagine the hassle of phone factory resetting on its own. Horrible.

Phone died, battery still charged

Had a weird issue with my S7.
Despite being at 95% battery, the phone suddenly died. Wouldn't turn on at all. As I was near a Best Buy store, I brought it in and they plugged it into a charger. It showed 95% and charging, and they were able to power on the phone. As soon as they removed the charger however, it would shut off again. If they removed the charger during the startup process, the phone would shut off right when the lock screen would normally appear.
Brought the phone home, charged back up to 100% (which took maybe 5 minutes), and everything appears to be working again. The weird thing is that my theme was reset to the default one, and my default keyboard reset itself to the Samsung one.
Not sure what's up... Any ideas?
Sent from my SM-G930W8 using Tapatalk

Hmmm, seems very strange. I would factory reset and try using it again. Make sure to clear cache before factory reset and afterwards. If you find it reoccurring, definitely take it in for repair or a new one.
---------------------------------------------------------------------------------------------------------------------------------------------------
If I helped, please hit the thanks button or buy a beer, which ever satisfies you!

Rooted Pixel 1 won't turn on, isn't responding

I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?

alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
See if you still can get your phone into download, fastboot or recovery mode. Here you can see the button combos: https://m.youtube.com/watch?v=YFaq4g-oa2Q
If you can get to recovery mode, click on wipe cache and reboot. If your phone still is stuck afterwards, go to recovery again. There is an option to wipe and reset the phone. Note that your data will be lost!!! Do it at your own risk. But a reset often is the last working choice when your phone behaves strangely.
If you get none of the three mentioned modes to work, I think your Pixel has a hardware fault.
Hope this helps.

check the charging port first....whether it is charging or not......try to connect to PC
i guess the phone is not charging

So the bottom line is this is still somewhat ongoing, though I’ve confirmed the phone is definitely bricked. I brought it into UBreakIFix and after taking it apart (noting that the device seemed physically in great shape) that there wasn’t anything obviously wrong with any of the particular hardware (they mentioned that replacing the motherboard would likely do it, but it would be about as expensive and effective as buying a new phone anyway...).
I ended up writing back to Google and am in back and forth talks with them now. I’m not sure what they can or will do, but my final answer will have to be getting a new phone one way or the other.