I bought this phone, I think 7-8 days ago. Since I lost/stolen my older phone Kenzo, I had to buy a new phone.
I am facing issues with touchscreen (I will try to explain the problem in simple)
I downloaded Critical Ops, it works great even in Ultra mode but the problem is in middle of matches
For a few seconds the touch screen becomes laggy, to check I enabled that touch show option in Dev settings (let's call my touch - ball), I saw that even the ball doesn't even appear when the screen touch lags (it does appear but for like 0.5 secs in between those 5 secs). But after some time it starts working perfectly.
Please I don't want to go to service center, I don't know if this is a hardware problem or a software
Just please tell me how to fix it
Sorry for bad english.
Related
Hi
something weird happened to me. My Note2 (TW rom + root) fell from my pocket and hit the ground, while I was driving my scooter, and I realized only a few KMs later...
After :crying: I was lucky enough to find a nice person that gave it back to me. So I was happy even if the screen was broken. The weird aspect is that since this damage, the phone is not working very well. It hangs (temporarily) and stutters, the battery is consumed more than normal, when you slide down the notification it get stuck in the middle of the screen. It is still usable and generally when you launch an app it works almost perfectly but the system is weirdly behaving. Another example is that when playing Google Music songs I have gaps.
It SEEMS that the processor is busy or has spikes of power that makes the other apps to behave slower.
So the question is: could be that a damaged screen impacts the sw behaviour (just an educated guess: maybe it's receiving lots of touch inputs due to the breaks...). If i repair the screen, will it go away?
Thanks
Hi guys I have a problem with the touch response on my G4 (H815)
Basically when I use multi touch (and sometimes just normal scrolling) in certain apps the phone will recognize screen taps at the bottom of the screen at the home and back buttons and sometimes other areas, I have used the 'multi touch app' from the play store to confirm that this is indeed the case. This is extremely annoying as apps exit by themselves because of this. It doesn't happen every single time either, just sometimes but often enough for it to be annoying and so may be hard to prove to my carrier or LG if i send it back cause they may say there's nothing wrong with it.
It seems like a hardware issue and in that case the phone should still be under warranty right? I got it in August and haven't rooted or done anything invasive.
There are many people having issues with the G4 touchscreen. Check with your carrier and see if you can exchange it or what your options are.
Hi,
Same problem for me, the back and home button seems possessed. Se this video dropbox.com/s/540ozmvdnhemv8f/MOV_0005.mp4?dl=0 for an example. I bought the phone Thursday last week and it have been this pretty much since unboxing. After a factory reset the phone acts normal for a couple of minutes or hours, but goes back to that stage were I can't use the phone at all. I've managed to update to the latest software but the problem didn't go away. I'll try to contact the supplier I bought the phone from and exchange it tomorrow.
Since I do not have enough posts to post external links you have to figure out for youself what to type infront of the "link" I included.
Hello everyone,
I have a Z2 plus since 2 month now and in the last few days I am experimenting big problems with the touch screen,
after some test I decide to download and try a touch tester from play store and I discover that almost allover the screen, if I touch it very gentle then the screen works flawlessly, but if I do a little pressure (more on the right part of the display, but if I try a little harder also on the left side) the screen detect, more then my finger's touch, 1-2 or some times even 3 touchs just on the very bottom of the display.
Obviously, when this happen during normal use the phone just doesn't response for a second or act weirdly (ex. open multitasking or other things).
I have searched on the web but doesn't seems to be a common problem.
I have also contact the chinese seller (bang00d) but actually I really don't count on them
I also tried to deactivate the bottom of the screen using "wm overscan" from terminal, but even if the part of the screen where the wrong touch are detected became escluded, the touch are still detected
I really don't know if overscan resize just the display and don't effect the touch ....
Any help is appreciated :highfive:
psmaniaco-androidiani said:
Hello everyone,
I have a Z2 plus since 2 month now and in the last few days I am experimenting big problems with the touch screen,
after some test I decide to download and try a touch tester from play store and I discover that almost allover the screen, if I touch it very gentle then the screen works flawlessly, but if I do a little pressure (more on the right part of the display, but if I try a little harder also on the left side) the screen detect, more then my finger's touch, 1-2 or some times even 3 touchs just on the very bottom of the display.
Obviously, when this happen during normal use the phone just doesn't response for a second or act weirdly (ex. open multitasking or other things).
I have searched on the web but doesn't seems to be a common problem.
I have also contact the chinese seller (bang00d) but actually I really don't count on them
I also tried to deactivate the bottom of the screen using "wm overscan" from terminal, but even if the part of the screen where the wrong touch are detected became escluded, the touch are still detected
I really don't know if overscan resize just the display and don't effect the touch ....
Any help is appreciated :highfive:
Click to expand...
Click to collapse
hey there,
Did you try a stock rom may be zui 2.5?
If you haven't try and reply?
My message is 16 months old!
I ended up replacing the display Assembly.
Wow just wow !
psmaniaco-androidiani said:
My message is 16 months old!
I ended up replacing the display Assembly.
Click to expand...
Click to collapse
How did you still manage to reply ? its kinda funny
samartht said:
How did you still manage to reply ? its kinda funny
Click to expand...
Click to collapse
I am subscribed to this thread
I have a HTC One m8 and the top half inch of the screen does not respond but occasionally it does sometimes for a little while. The top half inch generally tends to work when the battery is charged to 100% but sometimes that doesn't happen either. if it helps I use a tempered glass as a screen protector and the screen does not have any physical damage and it doesn't help when u boot into safe mode. I have also tried a hard reset.
Coincidentally i am working on a phone with the same problem (not mine). After a lot google research the owner decided to use another Launcher (Smart Launcher). This did not fix it entirely, if you are in Apps you can use the statusbar, but its not working on homescreen. I dont know why it behaves like that, but surprisingly many people get problems like that. I tend to believe that there is some software problem involved, because changing Launcher or using custom rom has been reported helpfull/fixing the problem (not allways tho..).
Now he had some other troubles with this phone and in the process i did a reset, that did not fix things as you said. I will install a custom rom next and will report back next week.
So i was wrong with saying a new lauchner solved the problem. Statusbar(sb) was accessible in home screen but not in app, said it wrong in the other comment. Now i had some time to test this and i can say that at least the phone i was working on is broken.
The top part does not recognize any touch input. The reason the sb showed some reactions is, that the launcher had a bigger trigger area (i guess), so you could pull it down. But still the top part was not responding. I tested it with stock, S-Rom and one Nougat Rom (dont remember), none of that showed an input in the top part.
Solution for now is different launcher or app that pulls down the bar. There are still some problems in daily usage, that this will not fix, so i guess its time for a new phone.
I am facing same problem. Is it any update which was pushed by HTC which makes the top 1 inch unresponsive ocassionally.. Indirectly, a marketing gimmick to push us by a new phone. So if it is really like that, who would buy a HTC phone again anticipating same problem again. Might go for Samsung (my own preference). huh !!!
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
It seems the problem is more severe than just Android.
Because even in TWRP, I noticed the display need to wait ~1 minute from the last time I turn off the display (push the power button) to reactivating it.
If I try to turn it on, the display will give black color, but I still can actually interact with the system.
ArcOnFire said:
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
Click to expand...
Click to collapse
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Shimizux said:
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Click to expand...
Click to collapse
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
ArcOnFire said:
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
Click to expand...
Click to collapse
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Shimizux said:
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Click to expand...
Click to collapse
I don't think it's a battery problem. I see that I can play game for 1hr+ fine. A game that require exact timing of 2 touches on top of that. So that ghost touch really doesn't appear.
But yeah, it's really 2 contrasting sign
- In one hand, it seems an OS problem because I can simulate an environment where the screen definitely won't be frozen for hours, while on specific other environment, the screen freeze can happen very quickly between release and re-occurence.
- On the other hand, the problem seem doesn't stop on OS level because it can be found in TWRP.
If I read an answer on Quora that shows GIF image on the section I read, the screen freeze 100% won't happen. I tried the same thing on imgur too, the screen freeze won't happen.
So it seems that as long as the screen is showing dynamic content, it won't freeze (that's why game and YouTube doesn't show this kind of problem, but reading a web full of text/static images can)
A bit of update : I have left my phone in off state for 4-5 days. And I have been using it again, albeit, less extensively since my main phone has changed to K20 Pro.
Long story short : I haven't encountered screen freeze again. But this is just after 2 days playing with less intensity.
I wonder what really went wrong.