My daughter's TF300T started acting strange recently. Sometimes it will just stop recognizing any touches from the screen. To unlock I often have to turn touch the power on/off button several times before the touch screen will respond. It sometimes reacts very slow. The tablet is several years old so no warranty. Device is not all original on the most current version of stock. No root as of yet.
So if I root and install a custom rom (thinking crombi-kk) would this possibly recalibrate and fix the touch screen?
Looks like hardware issue to me. Seems to be common with the tf300. I had it with a brand new machine, swapped for another.
Related
I'm using Fallout v5 ROM from a month without any problem, but lately I have seen a really irritating touch screen glitch which I know is not ROM related.
Problem:
I'm seeing some random screen clicks and swipes (as though a ghost is operating my phone) and during this my phone touch screen becomes un-responsive. But I can turn the screen off using the power button and after turning the screen on sometimes the problem does reappear. I did some googling for this problem and found that many android users have seen this but none have a solution or know the root cause of the problem.
The guesses as to the Root of this problem floating around are:
1. Caused by erroneous charger (I charge from PC or from htc charger only)
2. Caused by high temperatures or humidity (I have seen this problem other wise too)
Lately the frequency of the problem is increasing and sometimes the phone is unusable. My theory for the behavior is that the battery needs replacement as my phone is already 1.5 years old. Willing to try any suggestions you guys suggest. I have already done a full wipe and tried 2 ROM but the problem re-appears.
Any help is appreciated.
I have a strange occasional problem with my sensation, sometimes very stubborn and persistent. While unlocking the phone, i don't get the lock screen but a snowy white screen (as on old tv when there is no signal) The phone is not frozen though, it reacts to finger movements and i can unlock it, i could even execute operations if i knew where the icons were, but the screen remains that white. Only after some locking unlocking, or pressing the soft buttons (no rule) i get the normal lock screen or home screen. Sometimes i have to turn the phone off/on.
Does anybody have similar experience, is it a hardware issue or could it be some app issue or what else?
It could be a hardware issue. I've never seen that with any rom or in any situation! Have you by chance tired flashing a different rom to see if the issue goes away? I'd do some experimenting and see if the issue continues on different roms. If yes it's likely a hardware issue. It does look like it but it wouldn't hurt to do some experimenting. Is your device still under warrantee ? I might look into replacement. Has the issue gotten worse? Sadly it seems to be hardware related but it wouldn't hurt to experiment and see if issue still persists. I wish you the best and hopefully you can get a repair or replacement to solve this problem. Best wishes.
Sent from my HTC Sensation using xda premium
The phone is under warranty and it is not rooted, so, I would not experiment with other roms. Several months ago I had the phone's mother board replaced under warranty because the first one died. The problem described above started after the mother board replacement but not immediately, it happens occasionally and not related to any special condition. It does not happen when the phone is unlocked and I work on it, it happens only when it is locked, i.e, when i try to unlock it and press the power button to unlock, it is then that this screen sometimes appears.
Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.
Something similar ....
I had a similar experience on the 15th .... took my N5 off the Qi charger and the screen froze when i tried to unlock it.
I hit the power button and was able to unlock and get a few touches in before it froze again.
I was finally able (after much screen off/on cycles) to get down to the developer options and turn on show touches & show cpu usage.
... background processes looked fairly normal when the screen was frozen(touches showed as frozen) ...
I was rooted, stock rom except for xda user Jishnu Sur's N5 camera mod and running a couple tried & true root apps(Stickmount & QuickBoot). Thought some software issue might be jamming up the digitizer i/o causing it to freeze.
Reverted entirely to stock (the Team Win recovery was also experiencing screen freeze - buttons worked fine) including removing TRWP and re-locking the boot loader!!
The screen freezing problem persists ... my conclusion is that it's a hardware issue. :crying:
It's possible you are seeing the same thing, but I haven't seen anything in the forums to indicate it's a widespread problem.
Returning it for a replacement phone ... :fingers-crossed:
Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.
biggiephat said:
Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.
Click to expand...
Click to collapse
Freezes tend to happen on custom kernels specially if you under-volt it too much. have you done that?
Screen Freeze
canaillou2k5 said:
Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.
Click to expand...
Click to collapse
Last week I had the same problem with my new NEXUS 5. IT’S TOTALLY A HARDWARE ISSUE.
LG products are however not so bad in the JAPAN market but still we are expecting a lot from LG technology.
LG services suck.
I am facing the same problem with my Nexus 5. Unrooted, bought 7 months back from India itself, was working fine till around two weeks back,when the lags, screen freeze, blacking out n all appeared. Got it repaired twice at the LG centre. They changed the front display touchpad as well as the charging connector strip. The problem still persists.
Hello there,
I've had several issues with my tf300t that really annoyed me. Well, first off, all of a sudden the touchscreen stopped working. I tried a hard reset, then a cold boot, no success. Then i had it sent to be fixed. After one entire month i got my tf300t back and verified if everything was back to normal. The touchscreen was working properly but after just one hour i noticed that i have ghost touches once again. I know what ghost touches are, i did a lot of research.
I had ghost touches before i had my tf300t sent to be fixed. Is it really a hardware issue? Because theese annoying ghost touches stop everytime after i do a cold boot. Sadly, they come back after a while, mostly after i turn my wifi on. Everything goes haywire.
What should i do? Send it back? The thing is that i rooted my tf300t and this kinda voids my warranty.
Sometimes i even experiment dead zones on my touchscreen. They go away everytime after i do a cold boot but this thing is really starting to piss me off. How did you guys manage to get rid of theese ghost touches?
You could try to update the digitizer firmware. Check out the threads about digitizer replacement. Basically you just need to run the touch_fw_update command. Either with the firmware already installed or download the 4820 version. Could also be a loose cable. Before messing with any cables, turn off your service switch.
I have a nexus5 as well as a TF300T and have noticed on the N5 that when charging you can get ghost images its like the digitizer goes a little mental when charging. It is a known bug (various reports to google) and something they are working on. Could the TF300T have a similar bug?
I recently revived my TF101 from the dead after deciding the other day to buy a new charger - last time I used it, it had a slow charge issue which a new charger fixed perfectly! It's probably been off for ~1 year.
After turning it on, I noticed after a while that the responsiveness of the touch screen was awful - I flashed the latest version of KatKiss thinking it would fix it. Turns out this problem occurs even when in TWPR Recovery, but I want to be sure that it's a hardware issue before going through the hassle of replacing the digitizer. I would be awful to replace it and still have the same issue
Exact symptoms:
When the tablet is first powered on, touch screen works as intended.
As time goes on, the tablet becomes less and less responsive, eventually reaching the point where no touch is registered!
Advice on this would be greatly appreciated - is this a software (kernal?) issue or do I need to get a new digitizer?
EDIT: Just figured out it was because I was using it while it was charging - apparently this makes a difference! I feel a bit silly