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.
I've noticed a problem that has happened twice with my new Nexus 5 so far - it will vibrate and then turn off. I don't know if it is going through its full shutdown sequence or not as what has happened is that the phone has not been in use, in my pocket once and I don't remember what the other time, and all of a sudden it vibrates once out of the blue, I go to check the phone and it is off. I can turn it back on again but find it weird that it seems to be crashing and then not even restarting - but being off. It is not rooted but the bootloader is unlocked so I can root in the future, if needed.
Is anyone else experiencing this?
rajax said:
I've noticed a problem that has happened twice with my new Nexus 5 so far - it will vibrate and then turn off. I don't know if it is going through its full shutdown sequence or not as what has happened is that the phone has not been in use, in my pocket once and I don't remember what the other time, and all of a sudden it vibrates once out of the blue, I go to check the phone and it is off. I can turn it back on again but find it weird that it seems to be crashing and then not even restarting - but being off. It is not rooted but the bootloader is unlocked so I can root in the future, if needed.
Is anyone else experiencing this?
Click to expand...
Click to collapse
Hi,
I have the same problem but i don't use the vibrator. My nexus works very good in all aspects but turns off randomly some days....
It's really disgusting and I don't know what I have to do for solve this neither...
Maybe use a manual one over a vibrator
Sent from my Nexus 5 using xda app-developers app
my nexus 5 d820 16 gigs would randomly shutdown for no reason, it wouldn't turn on without plugging it in. i was rooted and running cm11, then i tried carbon ROM, then c-ROM. c-ROM started to give me problems so i factory reset and switched to carbon but the problems remained. then i unrooted, thinking that root was the problem but no signs of improvement, so i re-locked the bootloader but still the problem remained. it would sometimes also shut down if i unplug it and would always forget my WiFi connection for some reason. help me please. thanks in advance.
Well sounds like a hardware problem since you already unroofed and relocked boot loader I would say call lg and get a warranty replacement
Sent from my Nexus 5 using Tapatalk
Sorry to bring this post back after a long time.
I had a similar but not exactly the same problem.
2 nights ago I left the phone on the table, and a few minutes later, when I picked it up, it was off (It had about 60% battery left when I put it down).
Then it would not wake up; I kept the power button pressed for like 20 seconds to force a shutdown, and then tried to power up with no luck, so I'm thinking I'm screwed.
I tried again and it powered up to a graphical noise screen as seen in the attached image, but then it showed the boot animation and came back to life.
This morning it shut off by itself while listening to music (Google play), but powered back on right away...
Rooted 4.4.4, stock ROM, Xposed with Greenify, Amplify and wakelock detector (all latest versions). But no changes for a couple weeks before this started happening.
No specific app running (at least in the foreground).
Any one knows where I can find any kind of log or trace about this, if any at all?
Has anyone experienced this as well?
Thanks
hi im new here
i get samsung I727 dead boot after bad root file flash from customer and after repaire it with RIFFBOX and flash stock rom 4.2.1 the now
work fine with full signal network but the problem is that no audio no mic with jack or handfree nothing all audio and sounds not work
i flashed it with custom rom and nothing upgrade and downgrade nothing still no audio no sound no audion on music youtube nothing
so just i wanna know if is a hardware problem or is flash the customer say that her phone work fine before the bad root flash
sorry for my bad english please i need ur help
flash stock w/odin, if its still not working its a hardware problem
vincom said:
flash stock w/odin, if its still not working its a hardware problem
Click to expand...
Click to collapse
i flashed it with I727UCMC1_I727ATTMC1_ATT flash and nothing same problem
galaxi said:
i flashed it with I727UCMC1_I727ATTMC1_ATT flash and nothing same problem
Click to expand...
Click to collapse
u have ur answer, its a hardware problem, "sounds" like the audio chip is bad, new mobo required
problem solved ( voodoo magic??? )
So first of all i would like to tell you how my problem started.
First of all, my phone was rooted with kinguser.
I was answering calls and in most cases i couldn't hear anybody. That day my i727 was out of power due the empty battery. I left it to charge over the night and in the morning when i tried to power it on, only at&t logo was on the screen and mobile freeze on that point. I didn't want to hard reset because of all the contacts in phone, so i tried to power on about 100 times. I lost patience and hard reset it. After that same problem persisted, phone freezes on at&t logo. I was on a trip so i tried many more times - pull battery, power on, press power button long time, power on, and on and on. After about hour of trying my phone started but again without sound. I tried to plug in phones but it didn't help. tried to play music, restart, install new players, set the sound level nothing helped.
I pulled out my old htc wildfire for use, and took i727 for taking pictures and things like that. I bought bluetooth earphone, and that solved problem, but i wasn't satisfied. I bought new speaker ( about 4 bucks ) and installed it. Unfortunately that didn't solved problem.
I was using my i727 for about 2 months only for camera and games. In that time i tried to put stock firmware to solve problem. That also didn't help. I read on this forum how to put custom rom and i tried. I am not so expirienced so i had many problems, i didn't manage to do that in first place. Tried with odin, CM10 and few custom roms, but failed every time. I thought that 40 bucks it too much for new mobo.
Two days ago i downloaded android 5.1.1, twrp 2.780 and gpapps. i followed steps and manage to install android 5.1.1 on my i727. On first power on android logo ( red green and yellow ball on startup ) looped in infinity. I reset phone with power button and on second time, android was updating. Phone started and new android 5.1.1 was up. First i tried if there was sound, but with no luck. Day after i installed some game, and after few hours of playing, phone turned off because battery was empty. i pluged charger, power on phone and went out. 5 hours later phone was still on startup logo bubbling. I tried to take battery, and power on, again infinite loop on android logo. i tried to reset with power on button, but on power on infinite loop again. I didn't want to lose my save in game so i tried to reset, and try, and try, and after many attempts finnaly phone started, and updates was applying. I waited for updates to finis, and phone started. i put my phone on table, and in few seconds viber ring. i read the message , and after that i realised that my phone had sound again! today is second day with sound. Still don't know how that worked out...
I hope that helps
two days after, my battery went out, and after recharging, there was no soun again
Last few days I've experienced sleep of death. My phone has shut down by itself from standby for 2 times in 3 days. The phone is stock, bootloader locked, running on Oxygen OS 5.1.9. Does anyone have this problem?
bpodnar said:
Last few days I've experienced sleep of death. My phone has shut down by itself from standby for 2 times in 3 days. The phone is stock, bootloader locked, running on Oxygen OS 5.1.9. Does anyone have this problem?
Click to expand...
Click to collapse
No i don't have this problem format your phone or reinstall your os.
nope, thank god i dont have this on my oneplus but i had it on my galaxy s7 so i understand its a pain
bpodnar said:
Last few days I've experienced sleep of death. My phone has shut down by itself from standby for 2 times in 3 days. The phone is stock, bootloader locked, running on Oxygen OS 5.1.9. Does anyone have this problem?
Click to expand...
Click to collapse
What are you doing when it shuts down?
First time when I noticed that phone is off I press power button few times and hold it and desktop showed up. Today I was holding power button and the phone booted from the begining.
bpodnar said:
First time when I noticed that phone is off I press power button few times and hold it and desktop showed up. Today I was holding power button and the phone booted from the begining.
Click to expand...
Click to collapse
Well if your looking for help you need to give more details than "it just turns off". What's the battery level? Where you using it? Was it in your pocket? Are you running the latest version of Oxygen OS? Does it happen when it's plugged in? Have you tried to factory reset it?
battery was 80%, phone was on the table, running Oxygen 5.1.9, not happening when plugged in, didnt try factory reset, bootloader is locked, no root.
So... there are some plausible reasons, because your phone doesn't shut off when plugged in:
The battery simply is faulty and you have to send your phone back.
Something runs in the background, and makes you just believe, the phone shut off. Would explain the long holding power button procedure (simply shuts off the phone the hard way and reboots it).
An app is really draining your battery that fast. Bitcoin mining perhaps. Not that good explanation, because you were at 80% you said.
I'd go for #2. Check your apps - maybe there's one, causing this.
I go with uninstalling few apps I suspect causing this behaviour so we'll see what happens next.
Your not alone and this is definitely not so simple as a "faulty battery" .its something in the kernel causing panic and its happening only to certain chipset revisions .we need to open a ticket on oneplus
Got something similar today. 5.1. 9 unlocked and rooted, battery around 70%, same place, time, location etc like almost everyday). During conversations in Messenger and WhatsApp screen went black. I pressed power and I've seen keyboard to input pin with comment that pin have to be inserted after restart (normal behavior after reboot anyway), this reboot took maybe 2 seconds. But screen hasn't responsed for my attempt to input pin. I couldn't do anything). Hard reset (with holding power) solved problem.
OnePlus 6 @ Tapatalk
Do you think it is issue which can be reason to claim warranty and send the device back to get a new one?
bpodnar said:
Do you think it is issue which can be reason to claim warranty and send the device back to get a new one?
Click to expand...
Click to collapse
If you haven't modified your device (root, twrp, etc) in any way then it's absolutely a reason for a warranty claim.
Device isnt rooted or BL unlocked, all is stock. I will contact Oneplus support service if device goes off by itself again. I've installed latest software update 5.1.11 and all fine for last 2 days, lets hope it will stay like that.
bpodnar said:
Do you think it is issue which can be reason to claim warranty and send the device back to get a new one?
Click to expand...
Click to collapse
No idea, rooted stock here, but happen only once on previous version on OOS. I will contact OP when it happen again.
OnePlus 6 @ Tapatalk
I sent my device back for replacement .definitely a device side issue for me .5.1.11 no good on my end
varund7726 said:
I sent my device back for replacement .definitely a device side issue for me .5.1.11 no good on my end
Click to expand...
Click to collapse
you were on 5.1.11 when it happened?
virtyx said:
you were on 5.1.11 when it happened?
Click to expand...
Click to collapse
Both 5.1.9 & 5.1.11
Yes, I've had this too. Screen goes black and phone dies.
Hmm somethimes fingerprint or face unlock dosent work, and i have to enter password. I think mine reboot somethimes, but haven't caut it in action yet.