Hi, I have a i9020T and just gotten it about 10 days ago.
Long story short the phone was dropped and the screen quickly started changing colors until it completely failed. So I order a new screen replace it, now everything looks good, the phone starts up normally, at this point everything is stock, factory reseted and everything.
Good right, well as soon as I put the phone to sleep it fails to wake up. It seems to function perfectly, buttons work I can unlock, I just can't see anything. Now matter how many times I restart and sleep the phone just doesn't wake up.
So I decide maybe another ROM/KERNEL could fix the problem, I was wrong. I have tried about 2 kernels, and 5 different roms, still nothing.
I am going to try and disassemble to see if there is a possible error, but other than the fact the phone wake up, it seems to work perfectly, CWM everything.
I cannot figure out if this is a hardware issue, but I am sure its not screen related. Hopefully not a motherboard issue.
I have searched google, xda everywhere yet no solution only few cases, but no real solution.
Thanks.
TheLegace.
I'm having the same issue. Then sometimes it randomly starts working again, but soon goes back to not waking up.
Related
Ive gotten it maybe 5 times since I bought it, although the latest updates have been stable. I still got it a few days ago though. Basically if I have the dock, and close the lid and say rotate the whole device or just move it a certain directions, it will make the screen stop displaying when trying to open it again. The lid opens, you hear a noise like it unlocks, but the screen is black. I try unlocking and locking, undocking, but its still black unless I reset the device via power. Anyone having this issue? It's not a serious one yet, but id like to know why it happens in the first place.
I have similar experience without dock.
I put it in carrying bag and drive to subway, when I take it out and the screen is blank and I can reboot it by power button. It happened 3-4 times under same situation.
I updated to 3.2 and problem didn't come back so far.
Hi everyone.. I searched a bit but couldn't come up with any more answers so I'm wondering if I missed something.
I've had my TF since like May, and for as long as I've had it, I've had this issue.
No matter what kernel or Rom or anything, my TF always randomly reboots ONLY when my screen is shut off and the wireless is left on. It doesn't reboot if I'm using it, and the only way to make it not happen is to turn on airplane mode when I'm done with it.
Its not a big deal, but it is annoying, especially if I leave it in the living room and forget airplane mode. Then whoever is in there gets to watch my TV constantly and randomly reboot every few minutes.
Its just more annoying than anything. Id love to just keep wifi active so it automatically connects when I turn the screen on.
Other than this, my TF has been flawless for like 6 months
Thanks if anyone has any information!
I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?
avlon said:
I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?
Click to expand...
Click to collapse
Wow, ill have to give this a try. I've never used the pattern lockscreen.
random reboots
I get this after about an hour of use. If I sitch it off via the button then when I press it again it reboots. If I just let th TF switch itself off (after 5 mins) it switches on normally when I press the start button.
I also had similar problems with my wife's TF, it rebooted randomly just about anytime (not just with screen off), apps crashing randomly. When I returned it to the store where I bought it, they immediately replaced it with a new one that doesn't suffer any of those problems.
If you have such problems, I'd recommend taking it back to the store for repair, because that is definitely not the expected behavior.
unfortunately the lock screen thing didn't work
Can't really take the thing back, I've had it for months.... fortunately this is the only issue I have... I can live with it. Its purely an annoyance that doesn't affect me when using it...
Found some threads mentioning digitizers causing issues with this on other models of hardware, but doesn't sound the same.
Been holding off on rooting my Note that I've had for a week to wait for stock recovery, kernel, etc. to be out in case I had issues.
Rooted no issues, went back to stock just to make sure I could, then rerooted.
Not sure if coincidence, but now if I let the screen time out or manually do it, then wake it up.. my touch screen stops working. I can hard reset and it works until I do the same thing, then stops working again.
Anyone else seen this?
Reseil said:
Found some threads mentioning digitizers causing issues with this on other models of hardware, but doesn't sound the same.
Been holding off on rooting my Note that I've had for a week to wait for stock recovery, kernel, etc. to be out in case I had issues.
Rooted no issues, went back to stock just to make sure I could, then rerooted.
Not sure if coincidence, but now if I let the screen time out or manually do it, then wake it up.. my touch screen stops working. I can hard reset and it works until I do the same thing, then stops working again.
Anyone else seen this?
Click to expand...
Click to collapse
multiple threads:
http://forum.xda-developers.com/showthread.php?t=1849618
http://forum.xda-developers.com/showthread.php?t=1851387
http://forum.xda-developers.com/showthread.php?t=1854665
http://forum.xda-developers.com/showthread.php?t=1848261
http://forum.xda-developers.com/showthread.php?t=1847054
i was not rooted so I returned mine. sounds like some people have been able to get it working again
Hey guys,
So we all know that Synaptics has kinda screwed us over with the touch screen driver. My screen often comes unresponsive; in that case, I just wait it out for a few minutes, and it's back to normal.
Today was not the case.
I'm running CM M9 with AK kernel. The screen stopped working, and after a few minutes of not working, I did a hard reset. One interesting thing though is that the power menu didn't pop up, even though it usually does when the power button is held for ~2 seconds.
I was thinking, 'no big deal, right?' But when I booted up, the screen was responsive for maybe 5 seconds, and then it just shut down. Reboot after reboot after reboot, these results repeated.
So I pulled the stock boot.img from the M9 .zip and flashed it in Fastboot. When I booted up, I didn't even get those 5 seconds of grace time where the screen was responsive. Even after waiting 15 minutes, the screen seemed to be dead.
I decided to re-flash the ROM in TWRP. Even though my touchscreen wouldn't function in the actual Android system, it would always function whilst in TWRP. Again, this was not the case. Only the bottom navigation bar would register touches. Everything else was dead.
I'm going to flash CWM and see how everything goes. But please, can someone point me in the right direction, say, if my touchscreen is still dead after re-flashing? Thank you so much...
I have the same issue here, rebooting a couple of times sometimes works, to get the touch working again in recovery. Makes not difference though if you do a full wipe (system/ cache/ dalvik/ data etc) and flash the 11s stock/ m9 nightlies the problem is still there.
I've had to stop using the phone as the touch screen issues make it unusable most of the time
thelestat said:
I have the same issue here, rebooting a couple of times sometimes works, to get the touch working again in recovery. Makes not difference though if you do a full wipe (system/ cache/ dalvik/ data etc) and flash the 11s stock/ m9 nightlies the problem is still there.
I've had to stop using the phone as the touch screen issues make it unusable most of the time
Click to expand...
Click to collapse
It's weird...I flip back between AK and the stock CM kernel, and the touchscreen works for maybe an hour, then it goes completely dead again (including when in recovery). And the touchscreen is dead no matter which recovery I use, whether it be TWRP or CWM.
Consider going pure stock and resetting tamper flags, if it keeps acting up you should be able to RMA it
demkantor said:
Consider going pure stock and resetting tamper flags, if it keeps acting up you should be able to RMA it
Click to expand...
Click to collapse
I've got it back to working by messing with the kernel a little bit. How's the progress with the LOGO partition going? I saw that in the other thread, you almost bricked your OPO
Yeah it was an unfortunate mistake on my behalf while digging into it deeper, luckily all worked out in the end
Haven't had the chance to make more progress, the wife and I had our first child on Friday and I still have one more week of finals left (until I'm done with college for good!)
I hope to have some more time this next week to figure the rest out, I'm sure its doable but I don't want to risk anything before I know more!
Touch screen unresponsive
Any solution to this problem? Running 11.0-XNPH30O
Android 4.4.4 that was updated two days ago.
The touchscreen becomes unresponsive every hour or two and need to force turn off the phone by holding down the power and restarting.
Have had the phone for a little over a week and annoyed by little issues here and there. The orientation change (when turning phone for auto rotate) on a picture takes too long. Speaker phone was a problem initially, fixed with an update and now this touch screen unresponsiveness.
Doesn't matter if it's Synaptics or not. cyanogenmod and one plus need to figure out a solution and not sell a buggy phone on the most important features of a touch screen phone. ITS TOUCH SCREEN.
If I don't see a fix in 48 hours, I'll be returning the phone or selling it on eBay.
treChoy said:
Hey guys,
So we all know that Synaptics has kinda screwed us over with the touch screen driver. My screen often comes unresponsive; in that case, I just wait it out for a few minutes, and it's back to normal.
Today was not the case.
I'm running CM M9 with AK kernel. The screen stopped working, and after a few minutes of not working, I did a hard reset. One interesting thing though is that the power menu didn't pop up, even though it usually does when the power button is held for ~2 seconds.
I was thinking, 'no big deal, right?' But when I booted up, the screen was responsive for maybe 5 seconds, and then it just shut down. Reboot after reboot after reboot, these results repeated.
So I pulled the stock boot.img from the M9 .zip and flashed it in Fastboot. When I booted up, I didn't even get those 5 seconds of grace time where the screen was responsive. Even after waiting 15 minutes, the screen seemed to be dead.
I decided to re-flash the ROM in TWRP. Even though my touchscreen wouldn't function in the actual Android system, it would always function whilst in TWRP. Again, this was not the case. Only the bottom navigation bar would register touches. Everything else was dead.
I'm going to flash CWM and see how everything goes. But please, can someone point me in the right direction, say, if my touchscreen is still dead after re-flashing? Thank you so much...
Click to expand...
Click to collapse
treChoy said:
I've got it back to working by messing with the kernel a little bit.
Click to expand...
Click to collapse
I've got a touchscreen dead zone at the bottom, just all the navbar area. I wonder if it could be possible to get it back to working by messing with the kernel as you did. Which kernel and tweaks.
Thanks.
Edit: now the dead zone has extended to the hardware buttons. I have to rotate the screen 180° in order to be able to use the navbar.
Thanks
Hi all,
Long story, but the quick version is my home button rarely does anything any more and the screen wakes up by itself from being asleep after anywhere from 3 seconds to 12 seconds.
Now for the long version:
Non-rooted Galaxy S6, by the way. I did a factory reset last week, just because things were getting sluggish. It went well, things were back to speed, and I reinstalled the essentials I wanted. Last night I noticed my phone kept waking itself up over and over again. Then I noticed the home button wasn't doing anything. I rebooted it and it didn't change a thing. After a little more time, the power button also stopped responding. I couldn't even do an emergency reboot with those two buttons disabled. I even tried sticking it in the freezer for a few minutes to see if it was too hot. Google told me about the on screen menu thing to emulate the softkeys so I was able to use that to get around and do reboots.
I hadn't installed any new apps in the last 24 hours, but what the heck, I did another factory reset. I had the option to restore all the apps and settings from 1 day ago, so I chose that. The problem still was there. Dang it, I thought I should not have restored those apps, so I did another reset, this time a totally clean one. The problem not only still happened after the reset, it was doing it during the reset, if the screen went to sleep during a step in the factory reset, the glitch would wake it back up in a few seconds.
I decided last night to just turn it off and charge it fully and hit the Sprint store in the morning. Oddly while charging with the phone powered off, the green battery display would go off and on the whole time it charged.
In the morning I turned the phone on....and NO problems. (of course) For 2 hours not one glitch. So just before leaving for work it starts happening again. Another factory reset at work and a system update from Samsung and still, the problems are there.
I'm just thinking I'll hit the Sprint store tomorrow and swap it out for a new one...but I thought I would tap you guys for any info if you had any.
Thanks in advance, Larry
Sounds like your phone got wet. Factory reset over and over again will not fix this problem ha
Hi,
It seems like a problem with the hardware itself. So yeah, factory resetting all times won't help. Go get a new one .
All the best,
~Lord
Sent from my SM-G920I using Tapatalk
Try to use this method
http://forum.xda-developers.com/showthread.php?p=62872996
_______________________________________
thereassaad
XDA Assist
Thanks for the ideas, I tried the dialer thing, thereassaad, but it didn't help. It does sound like water damage, but there is no way. I've never dropped it or been near any water. I'm heading to the Sprint store tomorrow, too busy today. I'll let you folks know how it went tomorrow night.
Just FYI, they replaced the screen saying that fixed the home button not responding and the screen waking itself up, but said I probably shouldn't restore with my google account, since it's likely corrupting my system... Huh? I said. They said the hardware was fixed, but I should create a new google account. I said no way. I said what does having just my contacts imported (no apps) have to do with hardware failure. I said, open up a new phone and lets put my google account on it and see if it breaks the new phone, they said no.
In the store we added my google account to my "fixed" phone with the new screen and all and it messed up again. They said, never mind, we'll replace it, and it should be there this Tuesday.
I didn't ask if it would be a refurb, but I really don't care as long as it works.
So that's my story. So far.
They swapped it out for a new phone, refurb likely, but I'm not sure how to find that out. (not that I care too much) I'm loving the new phone, it's like unboxing day again. No cost out of pocket for me too, which is nice.