Hello there,
My Pocophone died yesterday. I've send it to the retailler. Dunno if there are going to fix or replace me by a new one ?
I bought it in september (first batch) and i've got touchscreen issue with the latest stable miui 10 (10.0.60)
Some have issue, other don't have the issue.
So it's LCD or Motherboard or software (which doesn't fix everything) ?
If they'll fix my phone by changing the motherboard (can't start the phone, it staying black and i can't charge it, no led blinking)
Can i hope better touchscreen ?
Thx
Install latest Pie stable or beta 8.12.10, your problem will be fixed.
hero355 said:
Install latest Pie stable or beta 8.12.10, your problem will be fixed.
Click to expand...
Click to collapse
Not really
Pie stable = touch delay around edges,try type 'q' then 'i' it outputs 'iq' pubg aimiing can't detect small swipes,
8.12.10=touch dela around edges is fixed pubg aiming fixed BUT lots of touches sometimes not registering around the nav area and if your apply so much pressure on the screen lots of ghost touch will happen
I can't install anything, i have no more phone for the moment...
I was on 10.0.60 and i have swap letter when i'm trying iq qi...
And touchdelay when scrooling down and up
Also high sensitivity on touchscreen
I've disabled multitouch screenshot
My phone has been fix by the retailler. I didn't receive it yet but the motherboard has been changed..
I'll see if i'll still have touchscreen issue when i'll get it back
Related
So some of you with white Z5 compact phones might have had this touch sceen bug with repetitive key presses and unstable touch screen behaviour bug which was previously "fixed" by a software upgrade:
http://www.xperiablog.net/2015/10/21/white-xperia-z5-compact-touch-screen-fix-arriving-next-week/
Lo and behold. This bug is back in MM, and there is another guy in the thread which I can see also have the bug come back
It is not always there, but sometimes its just there. I dont know what triggers it. A restart seems to help until it comes back again.
For those of you not familiar with this bug, it usually shows by repetitive touches, and highly unstable touch screen.
For example when i press the key "s", it usually put in "sssssss" like i have pushed that key 5-6 times.
Also the bugs shows, when for example you are scrolling in facebook/internet, it will not let you scroll. Whenever you touch the screen, it will enter, whereever you lay your finger on screen.
Lastly it also shows by the screen becoming completely unresponsive when you press anywhere.
I have clean installed MM and restored my apps via Sony Backup/restore app.
I am so pissed how a phone color (white) can somehow decide the behavior of the phone touch screen, and I believe sony is hiding something.
In the beginning I was thinking that maybe they made different builds for the different Z5 colors, so they might not have included the "newest" touch screen drivers for at launch time for the white version.
But the same bug appearing AGAIN in MM i have a very hard time understanding that should be the case that it was a software bug. I believe there are some hardware bug, they have somehow omitted by a software circumvention, and they forgot to add it to the white version for the MM launch.
Personally I have always had a problem with the "return" key when the phone is placed. Patch or not, this button works once out of 10.
For information, I just bought this phone. I also think there is a hardware problem. This is average for a manufacturer like Sony. I thought for a moment it back in service but when I see the number of dissatisfied with the service Sony in France, I preferred to keep my phone in the hope that a solution comes a day. We have the right to expect in my opinion ...
I did clean install via flastool also and i have/had this problem. Yesterday i did software repair via pc companion and restores apps after that and so far problem has not occured.
I also made a repair with PC Companion but nothing changed.
So there are other people here with this annoying problem.
You all have a white xperia yes?
This bug is so annoying I feel sometimes like tossing the phone into a wall.
If there was an alternative to this phone in this form factor and specs, I would have bought it yesterday.
But unfortunately there isn't
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
hipsterfont said:
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
Click to expand...
Click to collapse
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
I also have Sony Z5 compact white version which had the touch problem from start. Now after the Marshmallow update its back. As said above, it could happen while browsing (or on home screen) e.g. Entering links instead of scolling i.e. It triggers multi click. In these situations all menu keys will also be none responsive. Its starts acting normal again after a quick push of the power button, i.e. puttning the screen to sleep.
As a former developer for mobile software, both for apps and the android platform, i thinking i would agree with the above conclusion that the problem is hardware based, and not due to a difference in the delivery software version, as i was hopping. So the question is; will this always be a problem for these versions of Z5c white, i.e. they are forgotten in new builds?
Unfortunately I'm having the same problem with my white z5 compact...
mcmanuf said:
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
Click to expand...
Click to collapse
it happens that for different colors are used different materials.. probably white ones have different properties..
i can confirm that using bad cable/chargers this kind of bug happens with every device, with random touches and impossible scrolling.. if you have a well-known bad adapter and you note no differences with your white z5c, that's definitively the answer..
i think sony should recall all white z5cs and replace them with newer or different release
What revision of compact Z5 are you? Personally I have a revision 3 (that is written on the box).
I also had a touch of problem before moving to the latest version of Android (6).
My girlfriend also bought white Z5 Compact and funny thing... I put the Panzer Glass on the screen and guess what? Sometimes she can't turn off the alarm clock in the morning and sometimes navigation buttons are not responding. I tried then without the screen and it works without a problem. I am not sure if this is a problem with Panzer glass or sony's bug.
I have Z5 and have no problems, but mine is black edition
Mine is z5c white version as well. The bug started again on MM
And the bug quite annoying.
I bought it on updated lollipop.
And never had this problem before.
This plus Bluetooth is really making me hold off on not moving up from .200 lol
Argh - just saw the visual representation of this bug:
http://www.xperiablog.net/2015/10/06/xperia-z5-compact-owners-reporting-touch-screen-problems/
and it sounds A LOT like the one from the OnePlus One (driver & firmware issue)
easy blame: Synaptics - fix your ****
Anyway:
try enabling the double-tap-to-wake if it's not already enabled, lock the screen - give it some time to settle (~ 30 seconds),
wake it up (double-tap) - do some stuff - disable the double-tap-to-wake and lock the screen again.
Unlock it via power button and see if that improved the "situation".
Sony recommended a few times to boot into Safe Mode,
does this Mode exist on Android Marshmallow ?
Does it make any change ?
Had this in Nougat is there a fix?
It feels like a software problem! You can try to reinstall the system!
First consider whether it is a system problem. You can refresh the system to see if it is back to normal. If it still does not, then you may need to update a new LCD screen. You can go online to find the repaired video as a reference. The witrigs repair video is doing great, you can check it out!
Hi guys,
I have a Redmi Note 4 Snapdragon with a screen replaced recently. The problem is the screen only works after the phone is booted, if I let the screen turn off, it can't be waken up again. There's still backlight, vibration and all and I still hear sound. Which means the touch does work, only the screen doesn't display anything, just black. What can be the cause of this? Thanks everyone!
I have exactly the same problem on a Redmi Note 2. And this problem is not so rare because i found a few posts with same symptoms but i cannot find a fix. If you please find, please let me know.
Can I ask you something cause I'm a technician and I face similar problem not exactly the same. Were your screens bought with frame already glued and you face that issue? Usually such issues occur when they is no duct tape (sorry for my English) at the lcd flex cable where it folds under the frame or where the backlight circuit (I don't know the correct explanation in English I hope you understand). So I needed at my phone to replace the frame as well that's why I bought a lcd with frame (that of course was terribly glued). My issue is blacklight flickering when it wakes from sleep and if I push the edges it's ok. I have replaced a lot of note 3 LCDs without frame and I know that in all of them I had to put duct tape to make them work properly and without issues, I had only one for note 3 pro SE that was properly made. So I believe both your issues as well as mine have to do with that. If you have the broken ones, take apart the new and check side by side the flex cables and if you find exposed connections compared to the original just put duct tape.
Sent from my Redmi Note 4 using Tapatalk
earthscaper said:
Hi guys,
I have a Redmi Note 4 Snapdragon with a screen replaced recently. The problem is the screen only works after the phone is booted, if I let the screen turn off, it can't be waken up again. There's still backlight, vibration and all and I still hear sound. Which means the touch does work, only the screen doesn't display anything, just black. What can be the cause of this? Thanks everyone!
Click to expand...
Click to collapse
Perhaps you might want to enlighten us as to which ROM are you using, and who is the manufacturer of the lcd display?
DarthJabba9 said:
Perhaps you might want to enlighten us as to which ROM are you using, and who is the manufacturer of the lcd display?
Click to expand...
Click to collapse
Hi, I'm using the Ressurection Remix ROM on Android 7.1.2, planning to update to Oreo soon with the Pixel Experience ROM. And the LCD manufacturer is Tralfagar.
earthscaper said:
Hi, I'm using the Ressurection Remix ROM on Android 7.1.2, planning to update to Oreo soon with the Pixel Experience ROM. And the LCD manufacturer is Tralfagar.
Click to expand...
Click to collapse
Well, I don't know about Trafalgar - but if the new display is has an ebbg chipset, then you may have problems. There have been issues with ebbg displays and TWRP (when using custom ROMs - see for example https://forum.xda-developers.com/re...redmi-note-t3716706/post74815338#post74815338). Does everything work properly when you reboot to TWRP recovery? If not, then this may be the problem - and you may need to change your ROM to the latest MIUI releases.
I am facing same problem
I have redmi note5/5+, using custom rom (ion), I am facing same problem, changed lcd two time, tried with other roms, but nothing improved, did you find any solution.
I have a Redmi 5 phone. I had Global Stable ROM than switched to EU Beta. Currently on 8.7.19. I had a problem on both ROM. Randomly my phone slowdowns. Or at least the screen I don't know exactly. I have to press the screen harder and the response can take 1-2 seconds. Locking and unlocking the phone solves it. What can I do to solve this problem?
I have reported the issue. Please confirm it. We need official answers because many people has this. http://en.miui.com/thread-3446668-2-1.html
OK! I'm pretty sure now it's a hardware issue! Flashed TWRP recovery which also had screen freeze problems!!!!!
Than flashed an old firmware 9.2 something and flashed LineageOS over it. Guess what? SCREEN FREEZE!!! It can only mean one thing: it's a hardware issue. It's also explains why they ignore it: because they don't want to admit it! And because this much people has this problem we can say Redmi 5 is a FAILED PRODUCT. Xiaomi should call back this devices and give back my money immediately. But I think we are just ****. They will not care about it. Maybe only the service center can do something about it but it's a long and unnecessarily procedure. I think best option is to sell the phone and NEVER buy Xiaomi again and to stop recommend to anyone to buy it.
{:m016:} {:m016:} {:m016:} {:m016:} {:m016:}
BUG report: http://en.miui.com/thread-3446668-1-1.html
Hi! I have this exact same problem but I ruled out a hardware issue because every time there was slow to none response, if I turned the screen off and on again, it would fix it. I've been looking for a solution and after trying many, many things I've discovered the problem was that I was using the Full Screen option offered by MI, i.e. the option to remove the three main buttons at the bottom of the screen (Back, Home and running apps) and to control the phone with gestures. After going back to the classic three button style, I restarted the phone just in case and I haven't had any more response issues in two days, I think it was a success!!
I also faced this problem for months, specially, after I changed my display as I accidentally dropped my phone a few months ago. Sometimes the screen seems to freeze temporarily, but then -
- turning off and again turning on screen
- swiping the screen (bottom-top) with a little pressure for 1-2 seconds
- slightly bending the device
Any of this three work for me.
What I think:
It's a hardware (display) issue. My newly changed display creates this. But I am quite sure, when my device bends slightly this problem occurs.
Hi, I bought the Poco in January 2019 but it was December batch and it worked great until now , now I see stuck pixels on screen in weird spots like in near the notch and on left of the screen, they are basically a small line of pixel shining. Also there touch freezing or screen freezing , which I have to lock and unlock the phone to get it working. It happens very often and in pubg also and rarely the device freeze and I had to force reboot to get it working. Is it a hardware problem keep in mind I tried custom ROMs and kernels but it didn't fix anything. Also the battery isn't passing 5hrs sot. Please help.
ahmedegypt said:
Hi, I bought the Poco in January 2019 but it was December batch and it worked great until now , now I see stuck pixels on screen in weird spots like in near the notch and on left of the screen, they are basically a small line of pixel shining. Also there touch freezing or screen freezing , which I have to lock and unlock the phone to get it working. It happens very often and in pubg also and rarely the device freeze and I had to force reboot to get it working. Is it a hardware problem keep in mind I tried custom ROMs and kernels but it didn't fix anything. Also the battery isn't passing 5hrs sot. Please help.
Click to expand...
Click to collapse
If you already tried other ROMs and kernels then it is most likely a hardware problem. So, I advise you to go to the nearest service center to check the phone's screen and replace it if needed.
Sent from my POCOPHONE F1 using Tapatalk
OsGhaly said:
If you already tried other ROMs and kernels then it is most likely a hardware problem. So, I advise you to go to the nearest service center to check the phone's screen and replace it if needed.
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
What about battery life?
If hardware problem, it can cause anything like battery drain
Sent by my POCOPHONE F1
ahmedegypt said:
Hi, I bought the Poco in January 2019 but it was December batch and it worked great until now , now I see stuck pixels on screen in weird spots like in near the notch and on left of the screen, they are basically a small line of pixel shining. Also there touch freezing or screen freezing , which I have to lock and unlock the phone to get it working. It happens very often and in pubg also and rarely the device freeze and I had to force reboot to get it working. Is it a hardware problem keep in mind I tried custom ROMs and kernels but it didn't fix anything. Also the battery isn't passing 5hrs sot. Please help.
Click to expand...
Click to collapse
Just scrolling through and saw this. Did you eventually fix your problem. There have been many updates since you posted.
First way to solve the problem is use a custom kernel with the touchscreen fix. I suggestion Optimus Drunk Kernel.
My ROM of choice is really nice. It's the Evolution-X ROM and with the ODK, it runs really well. Regardless what custom ROM you have, try the ODK with the touchscreen drivers.
Hello guys, a friend of mine has a Poco F1 and few months back he had to change the display because the phone fall on the ground. Up until that moment he didn't faced any display problem and he was on custom rom (pixel experience I guess). He bought an eBay screen replacement but the phone started facing random screen freezes (lock/unlock and back to normal), which leads him to buy a second screen replacement from an other seller. The situation got worse with freezes and also proximity sensor wasn't working.
Yesterday he gave me the phone and I found out that it's a known problem with Poco F1 screen. Firstly I fastbooted last Miui global stable 12.0.2 and now the phone seems mostly usable but still some ghost touches are present. Than I checked the LCD type with device info he and discovered to have a fts_ts. Also Proximity sensor works when you press pretty hard on the screen next to the notch.
I think that the proximity sensor is faulty on this screen since with the first replacement prox was fine.
What about display problem?
1) I read about Miui introducing driver update to fix touch month if not 1 year ago so now last official global stable should have all the driver updated?
2) Are there any custom ROMs/kernels which fixed the issue better than Miui? Or did 3rd part developers just include new "screen driver" from Miui in their ROMs?
3) I don't understand the difference among nvt/FTS and EBBG/BOE/Tianma. Last three are display manufacturer but nvt/FTS what does that mean?
Thank you!
P.S. I just tried the proximity sensor test this morning and it was working, than I pressed next to the notch and now back to non working. ?
........ So I found out that Tianma/Ebbg/Boe are the manufacturers of LCD panels while nvt/fts are the manufacturers of touch panels.
I just rooted the phone and from hw info app I can see the combo Ebbg/FTS.
Now I am searching a Tianma/nvt replacement display, if you find one on AliExpress or eBay please link me.
Anyway I still have a doubt about custom ROM behaviour with different panels: does custom ROMs overwrite vendor partition when flashed or is it enough to just flash latest Miui (via fastboot?) before flashing a custom rom to have updated touch driver?
Inviato dal mio POCOPHONE F1 utilizzando Tapatalk
View attachment 5137419