Instead of asking Xiaomi or the POCO team for more features, we should ask them to fix the basic issues such as touch issue(now it is only on the edges on my device with 8.12.27 firmware), and fix the notifications and hide notch options before moving onto new features like 60fps videos and such. It seems like the whole MIUI forum is filled with people asking for new features instead of making it stable.
Also can anyone comment on whether the touch is a hardware issue or a software one? Can it be fixed by devs of XDA?
itscooltime said:
Instead of asking Xiaomi or the POCO team for more features, we should ask them to fix the basic issues such as touch issue(now it is only on the edges on my device with 8.12.27 firmware), and fix the notifications and hide notch options before moving onto new features like 60fps videos and such. It seems like the whole MIUI forum is filled with people asking for new features instead of making it stable.
Also can anyone comment on whether the touch is a hardware issue or a software one? Can it be fixed by devs of XDA?
Click to expand...
Click to collapse
it's hardware related, can be fix by software but the fix for some it's not equal to others, so hard to make a universal fix...
Can you clarify please ?
TioCareca said:
it's hardware related, can be fix by software but the fix for some it's not equal to others, so hard to make a universal fix...
Click to expand...
Click to collapse
Hi, can you please guide to more info regd it's HW-related ? Thinking of buying one, but quite unclear what exactly going on with this issue.
Thanks in advance
maczpiku said:
Hi, can you please guide to more info regd it's HW-related ? Thinking of buying one, but quite unclear what exactly going on with this issue.
Thanks in advance
Click to expand...
Click to collapse
Not really got an announcement for you to read, but if you search here in the forums you can see that different batches of the poco ( month of fabrication)(first batch even got screen bleeding) work better with some firmware versions and others work better with different firmware version, that is related that xiaomi is trying to fix the ghost touches by changing the way screen reacts to touch, but some batches work better in a way that make lag or ultra sensitive touch in others, that happens because the screen is not build the same way hence the "different" screens ...
Depending for what you will use the phone, that's not a really serious problem, noticeable more in some games...
Hope i explained myself good...q
Here are some testimony from users with different batches:
yoprateekyo said:
Touch issues are there in all the pocos except the latest batches now.
Touch issues are not severe are usable.
Some builds fixed half issues other created half.
If you wanna buy just buy you won't regret.
If touch gets perfect i am more than happy if not i can still live with it happily.
Rprpprrp ( i typed pr pr pr pr) this is issue.
But you will become habitual within a day or two. big deal.
Click to expand...
Click to collapse
RohanAJoshi said:
Tp firmware is same for all.
But you have different touch panel than others.
Most of us have novatek which is sh*t.
You are lucky user.
Click to expand...
Click to collapse
RohanAJoshi said:
Guys : Touch issue is real, face it or go for another model.
As per this thread suggest, even if you get newer touch screen panel, there is no 100 % guarantee that touch will work fine.
.
Because : old panels all issues fixed from 8.11.23 beta to 8.12.20 beta, and in this period newer panels got issues.
So they reverted that fix in 8.12.27 beta. But then again same issues are back for old panels. And newer panels are good now.
Now old panel users are waiting for new update which includes 8.12.20 touch firmware.
.
So Xiaomi has fix for everyone but they don't know proper way to implement it. ( recognising both users and applying fix upon it)
In coming days they will find it.
And everyone will be happy.
In worst case, you need to go service center for flashing new firmware with new bootloader which can recognize which panel you have.
.
So, waiting is best way for it.
Click to expand...
Click to collapse
mario123m said:
Oh that's interesting. Some people here claim that newer batches don't have the touch problem yet you seem to have the exact same issue as my unit which was assembled in July 2018. Full four months and the issue still there... That is why I don't believe there are Poco users who don't have this problem.
Click to expand...
Click to collapse
rudge79 said:
Some things are a pattern: it involves all Poco f1 made in August 2018.
8.12.27 is the latest firmware we can use.
Any firmware which is more recent gives the black screen. So we must have a different display manufacturer.
The only solution I see is to update vendor and firmware without the display drivers.
Click to expand...
Click to collapse
jineshpatel30 said:
From what i understood and feel by flashing almost every Pie beta & stable is, there are atleast 2 set of touch screen that Xiaomi used in POCO F1, so we are getting conflicting results/reviews in term of touch response.
So, if you try to satisfy ones for whom touch is good enough with Pie stable of current beta build other segment will cry-out loud with issue, if you go with older beta build like 8.12.20 then people like me whose device work good enough on stable Pie will face touch issue.
So, it's never ending game and Xiaomi should accept the hardware issue, replace & be done with it.
Click to expand...
Click to collapse
Related
10.0.0 (QP1A.190711.020.C3, Sep 2019)
Seems like it was posted today..
Anyone flash it or know what it's for?
https://developers.google.com/android/images
Perhaps a fix for sensor issue?
I'd flash and see but ugh.. I have my phone set up perfectly including Google Pay.. May still do it, I'm sick like that!
i know right i didn't wanna flash it since we are a week away from the October build but will there even be an october build now?
masri1987 said:
i know right i didn't wanna flash it since we are a week away from the October build but will there even be an october build now?
Click to expand...
Click to collapse
Pretty sure there will be. The C3 indicates it's a hotfix release so that shouldn't impact the normal schedule.
So....did anyone flash it yet? Lol
Got it via OTA toda, 1335 MB on C3.
haven't seen anything different, lol.
Can confirm that this build has fixed the swipe up issue for unlocking not working properly - but still suffering from the screen goes blank when on a call (to ear) and then does not turn on again when viewed unless various buttons pressed!.
Got a new update as well
I got it this morning. I have not noticed anything new.
jimjamyaha said:
Can confirm that this build has fixed the swipe up issue for unlocking not working properly - but still suffering from the screen goes blank when on a call (to ear) and then does not turn on again when viewed unless various buttons pressed!.
Click to expand...
Click to collapse
I have that issue, and I'm still on 9.0.
I was chatting with the Pixel team yesterday about something unrelated and was trying to get any info about the C3 update. Instead, I got very evasive runaround about how there is no approved communication. He didn't act like he didn't know what I was talking about but just wanted to change the subject since he wasn't going to say what the "hotfix" was for. I guess this their new strategy after still not disclosing the difference between .19 and .20.
sliding_billy said:
I was chatting with the Pixel team yesterday about something unrelated and was trying to get any info about the C3 update. Instead, I got very evasive runaround about how there is no approved communication. He didn't act like he didn't know what I was talking about but just wanted to change the subject since he wasn't going to say what the "hotfix" was for. I guess this their new strategy after still not disclosing the difference between .19 and .20.
Click to expand...
Click to collapse
Yeah, they used to be very up front with what the differences are in the builds. Usually they were carrier specific. If I had to guess, this new update fixed some huge security issue that they needed to fix ASAP before the bad guys could take over our phones.
jmartin72 said:
Yeah, they used to be very up front with what the differences are in the builds. Usually they were carrier specific. If I had to guess, this new update fixed some huge security issue that they needed to fix ASAP before the bad guys could take over our phones.
Click to expand...
Click to collapse
Just take the OTA like good "sheeple." Don't worry about when it will get there, and of course you'd never need to root and block all of those glorious ads.
I flashes this new release yesterday and I may say it is big...I'm still going deep into what's new but haven't found anything relevant yet.
mgp53 said:
I have that issue, and I'm still on 9.0.
Click to expand...
Click to collapse
Is that the issue of swiping, or the proximity sensor info not causing the screen to reactive during a call?
jimjamyaha said:
Is that the issue of swiping, or the proximity sensor info not causing the screen to reactive during a call?
Click to expand...
Click to collapse
Proximity.. I wish that while on a call, no other involuntary touch action could activated... Until hanging up or pressing a deliberate action.
Apparently a hotfix for the sensor bug went out 5.5MB for other pixels... (see the stickied sensor bug thread) Makes you wonder if someone made an oopsie in our case?
I noticed my phone a little bit colder after this update.
It's a pretty big update! It's the same size as the official Android 10 image. Weird.
Any of the 10 features that we haven't gotten yet in there? Like the customization app or whatever? New AOD clocks? I can't remember what all else we were supposed to get. I don't have time today to check it myself.
(I don´t own this phone yet)
I don´t mind using OOS, but once the support from OnePlus is dropped and the time for a nice custom ROM arrives, is this going to be a problem ? Personally I find it a very annoying bug.
Scrolled through multiple forums for the OP6 as it also has in-display fingerprint sensor and it has the same issue, although someone partially fixed it. Is it possible for OP 7 Pro ?
Thank you for your answers and hopefully I can soon join this awesome community.
Limetak said:
(I don´t own this phone yet)
I don´t mind using OOS, but once the support from OnePlus is dropped and the time for a nice custom ROM arrives, is this going to be a problem ? Personally I find it a very annoying bug.
Scrolled through multiple forums for the OP6 as it also has in-display fingerprint sensor and it has the same issue, although someone partially fixed it. Is it possible for OP 7 Pro ?
Thank you for your answers and hopefully I can soon join this awesome community.
Click to expand...
Click to collapse
I think the devs are working on it. Just relax and wait for new releases
Hello guys, I recently got my new Oneplus 8T, and, whilst the device is amazing from what I could use it, it has an annoying flaw that I couldn´t find any information of.
When I press a whatsapp, telegram, etc notification, there´s a bit of delay inbetween the press and the start of the app opening. The phone does it the majority of times, as you can see in the video below (at the 10 second mark it opens it right):
Do you have an idea on what could be causing this? Does any of you have the same issue I do? I tried turning off everything related to battery saving, even factory reseting. Any help is much appreciated, thank you in advance!
Avrammm said:
Hello guys, I recently got my new Oneplus 8T, and, whilst the device is amazing from what I could use it, it has an annoying flaw that I couldn´t find any information of.
When I press a whatsapp, telegram, etc notification, there´s a bit of delay inbetween the press and the start of the app opening. The phone does it the majority of times, as you can see in the video below (at the 10 second mark it opens it right):
Do you have an idea on what could be causing this? Does any of you have the same issue I do? I tried turning off everything related to battery saving, even factory reseting. Any help is much appreciated, thank you in advance!
Click to expand...
Click to collapse
I have exact same issue and I guess all might be having same issue, just that they don't notice it..quite annoying to be honest...
ram4ufriends said:
I have exact same issue and I guess all might be having same issue, just that they don't notice it..quite annoying to be honest...
Click to expand...
Click to collapse
I've come across some people with this specific flaw, I contacted Oneplus and they told me to factory reset the phone and if that didn't help (which did not, since I've gone wayy further with it, installing HydrogenOS and older versions of OxygenOS and didn't solve the issue), it "might" be a software issue and it "might" be solved in the next software update.
For how much have you been with the phone?
What is bugging me is that this problem is too specific for it to be a hardware issue.
Avrammm said:
I've come across some people with this specific flaw, I contacted Oneplus and they told me to factory reset the phone and if that didn't help (which did not, since I've gone wayy further with it, installing HydrogenOS and older versions of OxygenOS and didn't solve the issue), it "might" be a software issue and it "might" be solved in the next software update.
For how much have you been with the phone?
What is bugging me is that this problem is too specific for it to be a hardware issue.
Click to expand...
Click to collapse
I have the phone for a week...I don't remember having this issue in my earlier OnePlus phones..it might be OOS 11 issue...
ram4ufriends said:
I have the phone for a week...I don't remember having this issue in my earlier OnePlus phones..it might be OOS 11 issue...
Click to expand...
Click to collapse
Yes, I still have my Oneplus 7 Pro and it works flawlessly. I think I found something crucial.
The problem lays whitin the "Notifications" apartment. I'll explain myself.
As you can see in this new video I recorded
that weird delay shows when I open a notification coming from the tab "Notifications". BUT, when I open the SAME APP (Play Store) from a notification coming from "Other notifications" there's no delay at all, the phone works flawlessly, see how I press to see how my download is going, there's no lag. It would be wonderful if you could try it yourself, and see if that's the case on you unit too.
Taking this into account, I'm almost 100% sure this is a software related problem, and has nothing to do with hardware, probably a bug.
I'll report it to the bug reporting section of Oneplus and see if they can work on it.
Avrammm said:
Yes, I still have my Oneplus 7 Pro and it works flawlessly. I think I found something crucial.
The problem lays whitin the "Notifications" apartment. I'll explain myself.
As you can see in this new video I recorded
that weird delay shows when I open a notification coming from the tab "Notifications". BUT, when I open the SAME APP (Play Store) from a notification coming from "Other notifications" there's no delay at all, the phone works flawlessly, see how I press to see how my download is going, there's no lag. It would be wonderful if you could try it yourself, and see if that's the case on you unit too.
Taking this into account, I'm almost 100% sure this is a software related problem, and has nothing to do with hardware, probably a bug.
I'll report it to the bug reporting section of Oneplus and see if they can work on it.
Click to expand...
Click to collapse
Were you able to find any fix to this? Quite annoying issue...
ram4ufriends said:
Were you able to find any fix to this? Quite annoying issue...
Click to expand...
Click to collapse
No, I coulnd't. But I confirmed it to be a software related problem. I flashed LineageOS and PixelExperience ROM and the phone worked flawlessly. So we might have to wait for Oneplus to fix the problem in next OTA.
Avrammm said:
No, I coulnd't. But I confirmed it to be a software related problem. I flashed LineageOS and PixelExperience ROM and the phone worked flawlessly. So we might have to wait for Oneplus to fix the problem in next OTA.
Click to expand...
Click to collapse
Yes, I am on Pixel Experience ROM and it doesn't have the problem..I will be on this ROM for sometime..
ram4ufriends said:
Yes, I am on Pixel Experience ROM and it doesn't have the problem..I will be on this ROM for sometime..
Click to expand...
Click to collapse
Yes, I was really satisfied with these ROMS performance, the only downside was getting Widevine security level down to L3, so i can't watch netflix on the phone anymore... Kinda sad we have to do this in order for the phone to work correctly.
Avrammm said:
Yes, I was really satisfied with these ROMS performance, the only downside was getting Widevine security level down to L3, so i can't watch netflix on the phone anymore... Kinda sad we have to do this in order for the phone to work correctly.
Click to expand...
Click to collapse
I remember there was an APK to watch Netflix..
ram4ufriends said:
I remember there was an APK to watch Netflix..
Click to expand...
Click to collapse
Oh, I might try that one, thank you man! Just updated to the newest OTA that was released today, and didn't fix the issue whatsoever... This is pretty sad.
Avrammm said:
Oh, I might try that one, thank you man! Just updated to the newest OTA that was released today, and didn't fix the issue whatsoever... This is pretty sad.
Click to expand...
Click to collapse
Ah..I was wondering if the latest OTA fixed it...I don't think they will fix it anytime soon
ram4ufriends said:
Ah..I was wondering if the latest OTA fixed it...I don't think they will fix it anytime soon
Click to expand...
Click to collapse
The latest OTA kinda did something for me. I get the delay 5 out of 10 times I press a notification. Used to be 9 out of 10 times lol. It's not completely fixed but it's an improvement. What I did was send a bug report to the Oneplus bug reporting site and they said that they will be working on it.
I'm on miui version 12.5.3 RJUINXM. I have been getting lots ghost touches lately and its really annoying. This is mainly the reason i have decided to install Arrow OS.
Anyone out there getting ghost touches on arrowos? Will changing the ROM fix the problem or, should i just wait for another miui update?
Nothing fixes the ghost touch issue, I tried every rom and every version of MIUI. Totally pointless. If you have warranty, use it, and send back this piece of c**p.
0b4 said:
Nothing fixes the ghost touch issue, I tried every rom and every version of MIUI. Totally pointless. If you have warranty, use it, and send back this piece of c**p.
Click to expand...
Click to collapse
Did you use pixel plus ui? I hear its quite stable
hameem3105 said:
Did you use pixel plus ui? I hear its quite stable
Click to expand...
Click to collapse
I did. Didn't solve ghost touch for me.
0b4 said:
I did. Didn't solve ghost touch for me.
Click to expand...
Click to collapse
So, did you claim your warranty?
hameem3105 said:
So, did you claim your warranty?
Click to expand...
Click to collapse
The store disappeared where I bought the phone from so I don't have warranty...
Wait for the new firmware, that might solve the issue.
AxisKiku said:
Wait for the new firmware, that might solve the issue.
Click to expand...
Click to collapse
It won't.
There's a rumor at the 4pda portal that ghost ghost touch issue could fixed by setting tight connection between display cable and motherboard.
Another rumor is connection between case usage and ghost touch.
0b4 said:
The store disappeared where I bought the phone from so I don't have warranty...
Click to expand...
Click to collapse
I contacted xiaomi's local office rather than the store, they asked for proof of purchase but issued the RMA. Just waiting to get it back fixed (hopefully)
Ghost touch is related to display panel, tianma or huaxing, tianma got ghost touch...
It may be hard to fix because fixing tianma ghost touch may cause huaxing to became buggy, i saw that on poco f1 as rom devs needed to make 2 version of the roms to each panel until a middle term could be reached...
Xiaomi got that bad habit to get 2 different panels to same phone...
I never experienced ghost touch in any factory or custom ROM
12.5.3 has been complained about by several, including me. I switched back to 12.0.6, perfect ever since. On the other hand, several people confirmed by telegram that 12.5.4 is good.
i have the same problem... i dont have warranty of the phone so, i have a piece of ****... i need to buy a new phone... i cant wait to another version of miui... itso so annoying for me
For me, it has helped now to set the refresh rate and the screen to 60 Hz. We'll see for how long. All other activities did not help, including the game turbo exclusion.
Unfortunately, but with the 60 Hz refresh, the touch has gone crazy once, but it probably happens less often
Thanks. I checked my tianma. I found such a coincidence "MDPPLATFORM_PANEL_TIANMA_NT36672C_J20S_LCD_VIDEO" How do you think to advertise the phone?
fudi2002 said:
12.5.3 has been complained about by several, including me. I switched back to 12.0.6, perfect ever since. On the other hand, several people confirmed by telegram that 12.5.4 is good.
Click to expand...
Click to collapse
Same experience here also. Although after 12.5.4 tried custom rom. Ghost touch is like my neighbor now. Any custom rom u trying now after 12.5.4 ???
hameem3105 said:
I'm on miui version 12.5.3 RJUINXM. I have been getting lots ghost touches lately and its really annoying. This is mainly the reason i have decided to install Arrow OS.
Anyone out there getting ghost touches on arrowos? Will changing the ROM fix the problem or, should i just wait for another miui update?
Click to expand...
Click to collapse
Update to 12.5.5 it solves it
Hi, I bought a few days ago an X3 Pro 6GB and it also has the Tianma panel . So far, no issues, but I'm reading bad experiences everywhere...
I would really love to try custom roms, but in that case isn't warranty voided? Or how do you manage to try custom roms and then claim warranty?
Thanks!
Alright, so currently im dealing with some Multitouch issues on my Pixel 4a. The repair place i went to UBREAKIFIX said they'll have to do the whole repair they did preciously again and charge me (because of 2 small dents at the side of the screen). Would not recommend. I wanted to get a poll of everyone with this exact issue Here is some steps to test:
1. Enable Developer Options (Go into build number click however many times and get developers options
2. Go to Developer Options in System settings,
3. Scroll down to Input and enable "Show taps" and "Pointer Location.
4. Put two fingers down and see if multiple pointers are shown (If not, Multi-touch does not work)
Also some other Notes:
Downgrading to Android 10, Makes multitouch work for some reason :/
Also would like to know if you've gotten your phone repaired before.
Any help figuring this whole thing out is appreciated
Can I ask what was the repair they did the first time to fix your touch problem?
hammered58 said:
Can I ask what was the repair they did the first time to fix your touch problem?
Click to expand...
Click to collapse
The first time, it was just a broken screen, had to replace it
fbievan said:
The first time, it was just a broken screen, had to replace it
Click to expand...
Click to collapse
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand
fbievan said:
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand
Click to expand...
Click to collapse
That's sucks, hard to prove if there right or wrong without putting a known good screen on
hammered58 said:
That's sucks, hard to prove if there right or wrong without putting a known good screen on
Click to expand...
Click to collapse
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)
fbievan said:
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)
Click to expand...
Click to collapse
I honestly cant say if its the hardware or software, maybe it might be a combination of both? I'm not entirely sure, however downgrading to android 10 from googles flash tool does seem to have it work. I had what i would guess is a full screen replacement from UBREAKIFIX, due to shattering the entire screen. Honestly, spending 140 dollars just to see if it might work is not worth it to me, so I'm really not sure what to do.
Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay
hammered58 said:
Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay
Click to expand...
Click to collapse
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here
fbievan said:
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here
Click to expand...
Click to collapse
idk,, maybe the sensitivity is setup diff
hammered58 said:
idk,, maybe the sensitivity is setup diff
Click to expand...
Click to collapse
After looking for a while seems the entire drivers are different in the kernel. But that is my brief look at. If anyone who knows kernel drivers would like to take a look at it. Would be helpful
LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.
I'm on stock but rooted. I've been slack so still on October patch. Multi touch working fine. Never had a problem with it.
(Finally updated to December patch and it's still working.)
LionDGem said:
LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.
Click to expand...
Click to collapse
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703
fbievan said:
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703
Click to expand...
Click to collapse
Wonder how this actually fixes the issue. Sounds strange.
LionDGem said:
Wonder how this actually fixes the issue. Sounds strange.
Click to expand...
Click to collapse
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little
fbievan said:
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little
Click to expand...
Click to collapse
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?
qqBenji said:
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?
Click to expand...
Click to collapse
I have LineageOS 19.1 here. So android 12. i'll try that android 10 approach
I can confirm now that downgrading to Official Google Pixel 4a Stock Rom Android 10 fixed the issue. I try to go back to LOS 20 now and see what happens.
PS: Using internal updater to update to Android 13 broke it again. Taking the long route now.
PPS: That chromium based flash tool is really handy. Would be awesome to have something like that for LineageOS.
PPS: As soon as I install anything above Android 10, multitouch stops working. I'll sell this stupid thing as is (will let te buyer know of course). Its a shame.