Related
Just thought i would make a threat to address the google maps being laggy / unresponsive.
It can usually be fixed by changing the display to HD+ mode if this was bugging anyone like it was myself.
i actually do have that problem- in hd+ mode :/
marzlol said:
Just thought i would make a threat to address the google maps being laggy / unresponsive.
It can usually be fixed by changing the display to HD+ mode if this was bugging anyone like it was myself.
Click to expand...
Click to collapse
Thanks, that did help but not ideal. We can't not enjoy the FD+ just because it will slow down Google Maps. Come on Google, sort it out!!
I guess Google blames it on Huawei, and Huawei blames it on Google. The fact remains that these problems were also reported on the Mate 10, 6 months ago and no progress has been made.
Don't have this issue. CLT-L09 variant.
Came here from the P20 forum. I have the same problem on my device.
CLT-L09 here, used maps yesterday with no problems or lag
Good to see it's not just me.
It's laggy as hell for me. Far slower than it was on my LG G4 that I just moved from. So slow and jumpy!
Same issue here, hopefully either Huawei or Google will fix the issue over next week or so. (I can use the workaround till then but it is mildly annoying)
Strange how some people have this issue and others not. Maybe it's region dependent? I have a UK P20 Pro (Three network - dual sim) and I have been using it for navigation for a few days now with no issues. It is pretty much running the same as it did on my Galaxy S8+.
Not noticed lag anywhere so far! Scrolling is better than it was on any of my previous Samsung devices.
My only issue is the stock icons and launcher. It looks too outdated. I'll stick Nova on it soon when I have the time to set it all up.
Highspeed123 said:
Strange how some people have this issue and others not. Maybe it's region dependent? I have a UK P20 Pro (Three network - dual sim) and I have been using it for navigation for a few days now with no issues. It is pretty much running the same as it did on my Galaxy S8+.
Not noticed lag anywhere so far! Scrolling is better than it was on any of my previous Samsung devices.
My only issue is the stock icons and launcher. It looks too outdated. I'll stick Nova on it soon when I have the time to set it all up.
Click to expand...
Click to collapse
I have the same phone (P20 Pro Dual SIM from Three), though as per one of the previous comments, mine is a CLT-L29 as opposed to CLT-L09. Could that be the reason?
hitpl said:
I have the same phone (P20 Pro Dual SIM from Three), though as per one of the previous comments, mine is a CLT-L29 as opposed to CLT-L09. Could that be the reason?
Click to expand...
Click to collapse
What exactly is the issue? Is it terrible lag? I want to understand how bad the situation is and when it happens to see if I can reproduce it.
I have the same model as you, so I find it very strange. Are you using a third party launcher or have you done anything else to your device since you set it up?
Highspeed123 said:
What exactly is the issue? Is it terrible lag? I want to understand how bad the situation is and when it happens to see if I can reproduce it.
I have the same model as you, so I find it very strange. Are you using a third party launcher or have you done anything else to your device since you set it up?
Click to expand...
Click to collapse
You can see the glitch here.
I find this strange also as I have never seen it. In fact maps has been super fast for me. I am dual SIM from three UK. CLT-L29 model
It is strange. I have tried to uninstall updates and install it again and they didn't seem to work.
The slowness is in the lag when you try to move the map or even when clicking around or when searching.
With FD+ switched off, it seems to work absolutely fine. Just like it did on my Nexus 6P
Hopefully, it will be fixed soon, so for now I am just going to live with HD+ setting
It's poor if it's been a known issue for 6 months. I'm on EE in the UK (see attached) and I feel cheated if I have to change the screen resolution for a mainstream, hugely popular app to work as it should.
It's made me nearly as unhappy as when I discovered that only one of my P20 Pro's speakers were working.
That's not normal, right?! ?
What software build are you guys on? I am on 8.1.0.103 and I have the maps issue. I saw that an online reviewer at android authority was using software 8.1.0.106 and said they were on "beta" software... lol. Am I on alpha then?
Can anyone confirm if maps works on 8.1.0.106?
jaju123 said:
What software build are you guys on? I am on 8.1.0.103 and I have the maps issue. I saw that an online reviewer at android authority was using software 8.1.0.106 and said they were on "beta" software... lol. Am I on alpha then?
Can anyone confirm if maps works on 8.1.0.106?
Click to expand...
Click to collapse
See attached
Looks like maybe the dual sim works (maybe the firmware version)
I'm on 103 on L 09 (UK single sim) and it took me ages to work out why maps wasn't working.
Hmm, this is even weirder! I am on dual SIM and my firmware version is only 8.1.0.102, which doesn't match with anyone of the versions you are talking above.
I miss my stock android on Nexus already :'(
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
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 love my pixel 3a, even the front camera selfies (even though it has a fixed focus). The phone takes awesome pictures, also with the front camera.
However, during video call (whatsapp or snapchat), the video quality is very very very bad. I mean like there is water in the lens or something or it just can't focus or its trying to smooth out everything till infinity. I don't get how this is possible. I know android doesn't have the best social media camera (compared to iphone, which is better optimized), but my galaxy s8 is doing whatsapp and snapchat video's just fine and in focus.
Other people have experience with this? it's really a pity, because it's the only thing i really dislike at the moment.
Any help would be appreciated.
With kind regards
Bengaal
Bengaal said:
I love my pixel 3a, even the front camera selfies (even though it has a fixed focus). The phone takes awesome pictures, also with the front camera.
However, during video call (whatsapp or snapchat), the video quality is very very very bad. I mean like there is water in the lens or something or it just can't focus or its trying to smooth out everything till infinity. I don't get how this is possible. I know android doesn't have the best social media camera (compared to iphone, which is better optimized), but my galaxy s8 is doing whatsapp and snapchat video's just fine and in focus.
Other people have experience with this? it's really a pity, because it's the only thing i really dislike at the moment.
Any help would be appreciated.
With kind regards
Bengaal
Click to expand...
Click to collapse
HI Bengal
Same issue with me, I'm hoping this issue is software of whatsapp app. should be fixed next update or next update Android 10.
What base model do you used? Mine is QQ3A.200605.002
Thanks!
Regards
Asep
asepuhuybok said:
HI Bengal
Same issue with me, I'm hoping this issue is software of whatsapp app. should be fixed next update or next update Android 10.
What base model do you used? Mine is QQ3A.200605.002
Thanks!
Regards
Asep
Click to expand...
Click to collapse
Thanks for your reply Asep,
I am running the same build number as you. Yes I hope it's fixed in the next update. Have you heard other people have this problem? can't seem to find many people with this problem. I would assume many people would have this issue.
Bengaal said:
Thanks for your reply Asep,
I am running the same build number as you. Yes I hope it's fixed in the next update. Have you heard other people have this problem? can't seem to find many people with this problem. I would assume many people would have this issue.
Click to expand...
Click to collapse
I haven't find same issues from other forums either hope next update can fix this, I have trying to clear cache but still no fixed.
asepuhuybok said:
I haven't find same issues from other forums either hope next update can fix this, I have trying to clear cache but still no fixed.
Click to expand...
Click to collapse
Just updated to the July patch. Unfortunately still have the same problem. I guess we're just unlucky and it's somehow a hardware issue. I can't imagine that the rest of the pixel 3a owners have the same thing but aren't bothered by it. I read on reddit of one guy who was talking about blurry front camera, but after phone was replaced the problem was gone.
I've had the same problem! My build number is QQ2A.200501.001.B2. I just got a new Pixel 3a as the last camera just died, but it was also an issue on the previous Pixel 3a as well.
Any news on this? I've found several threads on Google support sites regarding this issue but they've ve all been closed without a solution. There must be more people with this issue though and I'm not sure at the moment if this is a hardware issue or not.
Since last night we're in a serious lockdown here in the Netherlands and this is becoming a dealbreaker, cause the front camera is our most used lifeline with friends and family.
I'm on RQ1A.201205.003 and using WhatsApp for video calls.
Edit: see for example this thread from Google support: https://support.google.com/pixelphone/thread/63843045?hl=en
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.