Recently i have replaced my touch screen folder. But after that everything was working fine but after encryption, the problem of tap anything on screen with two fingers arises.
In the bootup of the phone, when I enter my encryption key for the storage, I don't have this problem at all. So it must be a software problem. It only shows up inside roms after encryption (every rom).
i have also encrypted before screen replacement but none of this issue happened.
anyone plz help me with this issue
or send me anything to activate fingerprint without encryption on Oreo roms
Similar issue here and I saw that a lot of people encounter issue with touchscreen responsiveness after having changed their screen.
Here are my symptoms :
Most of the time, if screen is left idle for a few seconds (still lit), it needs to be woke up by 2 fingers or a large finger (thumb) of a 2 or 3 single finger taps before being fully responsive again...
The phone stays responsive as long as it is used.
Problem DOES NOT occur in recovery. So it is software related I guess...
I read all comments linked to the screen I bought on Aliexpress (screen was tagged as Original, I could not find any difference having both screen in hands, so it clearly is from the same factory)
One comment stated to do a factory reset if the touch screen was laggy...
But maybe this factory reset must be done on stock rom ?
I also wondered if a kernel could have some specific option regarding touchscreen behavior that could help...
Related
Hi All,
I am using an IMATE Pocket PC 2003 since the last 6-8 months. Over the last few weeks I am facing a problem with the Touch Screen. ALl of a sudden the Touch Screen fails to respond although the buttons are still working.
Sometimes after several reboots, the Touch Screen responds sometimes it doesn't. Sometimes I just keep it IDLE for 2-3 Hours and the Touch Screen starts responding. There is no fixed time of the error also the error is random. Sometimes everything is normal for one week and there is no problem at all. Sometimes the problem persists continously.
I have Hard Resetted it atleast 4 times but the status still remains the same.
If anybody has experienced this, do share your thoughts.
Regards
Jinesh
I read somewhere that if you re-align your screen it may help.
Do your hardware buttons still work? You could try mapping tpenable.exe to a hardware button and select this when the screen locks up.
Touch screen problem
Jinesh,
did you ever manage to fix this?? This is exactly the problem I've been having on my MDA Compact (Magician) for ages: screen unresponsive, buttons still working. I started a thread on this topic as well and got some suggestions, but never managed to sort it out. I'm a bit wary to resort to flashing a new ROM or something like that since it seems to open up a whole new set of potential problems and will cost me my warranty with T-Mobile at the least (Not that they're much help, but still)...
Thanx,
Joost
Maybe the cover
The Qtek9090-screen is sometimes locked (e.g. when it's in a car holder which causes too much pressure on both sides of the display.) The same happens sometimes without any cause - pressing on both sides unlocks the screen.
Hi,
I am using an O2 Mini now and have sold off that Imate. But what I came to know that the touch screen problem was due to the irregularities in the network. The screen stops responding fast when network is weak and the device keeps on searching the network.
I have faced this problem once or twice in my O2 mini also.
Regards
Jinesh, I don't know if you checked out my thread on this, but indeed this is the conclusion I've reached: bad network causes the unresponsive screen. I think it might have something to do with the priority windows gives to the screen routine compared to (searching for) network. As of yet I have been unable to find a way to increase priority for the screen or lower it for network, though I browsed through the registry pretty extensively. Suggestions from anyone on this would be most welcome.
Using the stock ROM for the Galaxy Nexus, Android 4.04 from Google, I'm finding this bug (which has been elsewhere reported, but not acted upon by Google) where the touch screen is unresponsive. You press the 'power' button, the 'slide to unlock' screen appears, but the touch screen doesn't respond to anything.
If I get a call while the phone is sleep, the same thing occurs - can't answer the phone.
I usually have to put the phone to sleep/wake it up 5, 6, or more times before the touch screen again becomes enabled in these situations.
Does anyone know why this happens? There has been much conjecture about this, but I have yet to see anyone say for sure why this would be happening. A disabled touchscreen at such a crucial point in a GUI is pretty horrific.
- Tim
was gonna make a new thread on this but since i found one with the exact same thing happened figured why waste space, but anyway this just happned to me running stock 4.0.4 cdma unrooted. was just charging my phone unlocked it to check twitter and the lock screen was completely unresponsive for whatever reason. I continued to turn the screen off and on several times and then just decided to pull my battery and it worked fine.
This is the first time its happened to me and its kinda troubling as I dont want this to be a recurring thing and was wondering if this continues to happen or its just some single random occurence?
Since 2 days ago, I'm having a screen flicker problem with my Zenfone 2 551ML. At times, the lower part of the screen flickers. It happens when I scroll menus, webpages, basically when I move the screen in some way. This stops if I leave the phone in standby and after that I use it again, but after some time, it reappears.
I read somewhere (forgot if it was on this forum or on Zentalk) that disabling HW overlay in developer option can stop this kind of screen flickering, tried that and it worked.
1. Is it okay to leave it like that? What does that option exactly do? Will it affect the device performance/my experience with the device?
2. I tried wiping cache in recovery mode but it didn't help, the problem came back after a while. What kind of issue do you think this is? Hardware? Software?
did you ever get this resolved?
Hi,
Had my phone a couple of years, no problems, but recently cracked the screen.
Bought three replacement screens and fitted them in phone:
* 1st one touchscreen digitiser worked perfectly all the time but LCD was broken (had lines/artifacts on it) - sent it back.
* 2nd one, same supplier as first, LCD worked, but digitiser works intermittently - it always works immediately after phone reboot, but after the screen locks for the first time, it then has a problem where it registers an input when I'm not giving any, so the screen goes haywire and I can't even enter my pin or restart phone (Have to use red button in sim card bay). Occasionally and randomly when I try it, it sometimes works so I can enter my pin, and then use the phone until the next time the screen locks....but basically phone is rendered unusable, because this is totally random. Sent this one back too.
* 3rd one bought from a different supplier - AFAIK this one is a genuine Sony part (it at least has the Sony logo on it), but have the same digitiser problem as the second. Time has passed to send this back.
Due to the above description I am sure it is not a problem with the phone (1st one digitser worked perfectly & original cracked screen digitser worked for half the screen where it wasn't cracked). I'm also sure it's a software issue, since it works everytime following a phone reset but before the screen is locked. Behaviour seems to be the same at different temperatures. Also inspected the flex connector and ribbon components under microscope at work, and saw no problems.
One think I noticed is that all 3 screens I bought have no insualting backing on the back of the LCD, so the metal back touches the metal shield below - I did not see any screens to buy with the insulating backing - I wondered if this could be affecting the EMC behaviour of the screen (some capacitivie coupling with the digitiser or some type of grounding issue) - but then why would the digitiser of 1st screen work ok, and work for >1hour following a reset but then not after a screen lock?
Tried turning glove mode on/off - no difference in behaviour. Tried using screen while it is not fitted in phone housing (not touching metal shield), same behaviour.
I saw a couple of threads from a while back, but don't know if they are up to date, or if a solution to this problem is now known:
https://forum.xda-developers.com/showthread.php?t=2691849
This one gives a solution, but then says at the top of the thread DON'T TRY THIS FIX, IT IS A HARDWARE ISSUE NOT SOFTWARE.....so I'm worried to try it.
https://forum.xda-developers.com/showthread.php?t=2662457
This one is to adjust the touchscreen sensitivity, but even though I have root access, I get an error message relating to the mount commandwhen trying to copy the edited idc file back to the system\usr\idc directory, "operation not permitted'.
Does anyone know a reliable fix that works? Or how I can get write access to idc folder to try editing the clearpad file? I don't have an SD card for my phone, but not sure it is essential for these methods?
Thanks
Nabla_x said:
Hi,
Does anyone know a reliable fix that works? Or how I can get write access to idc folder to try editing the clearpad file? I don't have an SD card for my phone, but not sure it is essential for these methods?
Thanks
Click to expand...
Click to collapse
Assuming you're on LP 5.1... System rw access is disabled by default, even with root. Flashing dual recovery by NUT is easiest way to get it. Then you should be able to move files in boot or in recovery.
Hi all,
I've recently got this tablet from Google store (and out of stock now).
After installed all things needed, a serious problem has appeared during in use. Its screen unexpectly trembles, pops notification out, runs and closes apps randomly then unable touchscreen at all. These make me crazy even in screen saver, and power button doesn't work sometimes to stop those happenings.
The device hasn't rooted and staying as 'pure' with only afew apps, so I've done erasing system cache partition on recovery mode and factory reset twice to solve this problem.
Nothing happened so far since reset the device but is still unsettling.. and now I just supposed touching screen badly (with sweaty fingers for example) or the screen protect film I affixed since unboxing might cause the problem.
Does anyone faces a problem like this?
Regards,
Allen
If it was greasy fingers my tablet would be completely unusable. Luckily a quick clean sorts any issues that causes.
My first suspicion would be the screen protector, as mine has done similar when there was something touching the screen. Maybe try taking it off and seeing how it goes? You can also turn on show taps in the Developer Options to be able to see what touches the tablet is detecting when it goes mad.
Better than before
The Real Dannilion said:
If it was greasy fingers my tablet would be completely unusable. Luckily a quick clean sorts any issues that causes.
My first suspicion would be the screen protector, as mine has done similar when there was something touching the screen. Maybe try taking it off and seeing how it goes? You can also turn on show taps in the Developer Options to be able to see what touches the tablet is detecting when it goes mad.
Click to expand...
Click to collapse
Thanks for your reply. Now I've used a BT mouse to match with mine and less touch on the screen apparently. Nothing happened so far.
It's not a problem of hardware I supposed and pretty sure that the screen protector interferes a certain touch as you commented. Still my eyes are keeping on what caused the problem.