Related
Often touch is not recognized by this device. Rest of time touches work normally.
Clearing cache or factory reset is not working.
Touch is not recognized after some long pause or any time too.
Fix this bug Asus.
Touch issue i m also facing. We have to tap 3 times to open any thing. I have updated to latest december patch but problem still exists. Hanging slow interface.
rajatv89 said:
Often touch is not recognized by this device. Rest of time touches work normally.
Clearing cache or factory reset is not working.
Touch is not recognized after some long pause or any time too.
Fix this bug Asus.
Click to expand...
Click to collapse
If still within the warranty period, please ask for a replacement. I faced the same problem and flipkart dragged their feet for a few days rejecting replacement requests, till they finally sent a new handset. This problem is not there in the new handset. If out of replacement period, only option is to take it to the service centre. They will need to do a deep flash of the firmware which may solve they issue.
But this is really poor of Asus to release Buggy handsets with touch issues.
balaji345 said:
If still within the warranty period, please ask for a replacement. I faced the same problem and flipkart dragged their feet for a few days rejecting replacement requests, till they finally sent a new handset. This problem is not there in the new handset. If out of replacement period, only option is to take it to the service centre. They will need to do a deep flash of the firmware which may solve they issue.
But this is really poor of Asus to release Buggy handsets with touch issues.
Click to expand...
Click to collapse
Its not handset issue. It was reported after the first update. They updated the touch fw in that update which messed up the touch sensitivity. The issue will get resolved in future updates.
Although it is a software issue, it's not resolved with these OTA updates. When I got the phone,I was on stock firmware. I was facing the same issue. Post the 1st update, 177, I still faced the issue.
it's possible for some cases, touch was giving problems after the update, not for me it was going on since I bought it, and still continued even after the 1st update.
i've been facing touch issues for the last 3/4 months...
it's very annoying..sometimes lock and unlock makes it normals...but after like 10 minutes i t happens again..i looked up in the sony xperia sites and some people were also complaining about the issue but no reply from sony officials.i thought it was a software problem as some of the other consumers also have this touch issue so i decided to go back to oreo from the latest update..
but the problem stills exists even after flashing back to oreo.
anyone have any idea about this issue?
You wrote quite a few words, but you failed to describe the issue itself.
So, what is the problem?
MichaelMeier said:
You wrote quite a few words, but you failed to describe the issue itself.
So, what is the problem?
Click to expand...
Click to collapse
suppose i'm playing games for around 10 minutes
suddenly if i touch in the middle of the creen it registers at the corner
if i touchat corner it registers elsewhere
when i close the game and swipe on menu
it pulls down the notification bar
even closing the game becomes hard as it continuously registering falut touches
murshed.hasan said:
suppose i'm playing games for around 10 minutes
suddenly if i touch in the middle of the creen it registers at the corner
if i touchat corner it registers elsewhere
when i close the game and swipe on menu
it pulls down the notification bar
even closing the game becomes hard as it continuously registering falut touches
Click to expand...
Click to collapse
Maybe hardware damage?
Maybe heat?
murshed.hasan said:
suppose i'm playing games for around 10 minutes
suddenly if i touch in the middle of the creen it registers at the corner
if i touchat corner it registers elsewhere
when i close the game and swipe on menu
it pulls down the notification bar
even closing the game becomes hard as it continuously registering falut touches
Click to expand...
Click to collapse
I have experienced these same issues from time to time. I don't have a fix for it other than to restart your phone. That seems to fix the problem for a while.
One other thing I have done is to just close out of everything, lock the screen then rub it against my shirt to clean the screen a bit. These aren't very scientific approaches but it does seem to work in my case.
SludgeFactory said:
I have experienced these same issues from time to time. I don't have a fix for it other than to restart your phone. That seems to fix the problem for a while.
One other thing I have done is to just close out of everything, lock the screen then rub it against my shirt to clean the screen a bit. These aren't very scientific approaches but it does seem to work in my case.
Click to expand...
Click to collapse
i do the exact same thing.lock my phone then rub it on my clothes and unlock
it fixes the problem for a while
I have it too. Usually turninhg the phone on and off again works. But it's quite annoying
Having the same issue!
When touching in the bottom half of the screen (for example when typing on the keyboard), it starts to pull down my notification bar.
Also happened yesterday: was typing sth in WhtasApp, and suddenly I got asked, if i really want to start a phone call. The button for this action is on a upper area, of the screen.
I think it started with a update, a while ago. Cant really say wich one.
For me, it works to lock and unlock the screen. The issue is gone for at least 10 minutes. So i think its a software bug. I am hopeing best for the future android 10 update in Q1 2020.
But for me, such software bugs should not occour. And its weak from sony, they dont release a patch to fix it. Probably my last sony phone...
1fsaf said:
Having the same issue!
When touching in the bottom half of the screen (for example when typing on the keyboard), it starts to pull down my notification bar.
Also happened yesterday: was typing sth in WhtasApp, and suddenly I got asked, if i really want to start a phone call. The button for this action is on a upper area, of the screen.
I think it started with a update, a while ago. Cant really say wich one.
For me, it works to lock and unlock the screen. The issue is gone for at least 10 minutes. So i think its a software bug. I am hopeing best for the future android 10 update in Q1 2020.
But for me, such software bugs should not occour. And its weak from sony, they dont release a patch to fix it. Probably my last sony phone...
Click to expand...
Click to collapse
i also think it is a software bug but i went back to oreo after this problem but the problem still exists.i don't really know what to do and sony didn't even release a statement regarding this issue.
murshed.hasan said:
i also think it is a software bug but i went back to oreo after this problem but the problem still exists.i don't really know what to do and sony didn't even release a statement regarding this issue.
Click to expand...
Click to collapse
I assume the problem is in the firmware of the touch screen.
A small OS operating with the kernel touch driver
And I assume you can't downgrade it, unless you allow it in the kernel(defconfig)
I have a same problem. When I tap the lower part of screen, it starts to pull down the notification bar.
Same touch issue + accelerometer
I've had the same issue with the touchscreen - inputs along the bottom half pull the notification shade down. Also, my accelerometer fails the xperia test in the support app. Can anyone provide experience with Sony warranty claims? I sent my device in for repair and they literally just sent it back with no comments or remarks on the device or issues : /
Dont think the problem is Software related but Hardware. mine is like that since it got underwatter. problem is that changing the LCD panel can or not fix the issue, the investment alone of the panel 100€ and the hand work 75-100€ is nearly a 2/3 of a new one to not surely fix the problem. What I mean is, without a oficial stand from sony itself we cannot trust/invest money trying to fix and thats a shame.
The issues is happening in my phone too, yesterday sony bring the android 10 update, and i think its fixed, because after i updating the phone, im not experiencing that issues anymore
Fikri Nouval said:
The issues is happening in my phone too, yesterday sony bring the android 10 update, and i think its fixed, because after i updating the phone, im not experiencing that issues anymore
Click to expand...
Click to collapse
let's just hope that they fixed it.i haven't received the update yet
let's see
Fikri Nouval said:
The issues is happening in my phone too, yesterday sony bring the android 10 update, and i think its fixed, because after i updating the phone, im not experiencing that issues anymore
Click to expand...
Click to collapse
Is it really fixed?
That would be awesome.
I still have touch problem on Android 10, not fixed
Did anybody solved this problem? if does how? what was replaced?
android 10 didnt, with make me 80% sure it is Hardware.
Fikri Nouval said:
The issues is happening in my phone too, yesterday sony bring the android 10 update, and i think its fixed, because after i updating the phone, im not experiencing that issues anymore
Click to expand...
Click to collapse
does android 10 really fix it? I still don't receive any update and not so very keen to update, but if it really fix the touch issue then I will do it with newflasher in no time
same exact problem here
PHP:
Can anyone help me replicate this bug?
I am on Android Version: 10.
Security Patch: April 5, 2020.
Google Play System Update: March 1, 2020
Build number: QQ2A.200405.005
Basically what happens is that when I'm using the "Gesture Navigation" from the System Navigation settings, whenever I swipe up to open the app drawer and exit out swiping from the right of the screen. The 5 main icons on the home screen become unresponsive and do not respond accurately to touch at times. When I do the same thing but exit out swiping to the left part of the screen instead, the issue never happens. Also, this is one way of fixing the issue whenever it happens.
I've recorded videos to help visualize the issue. They're basically the same, but I made one while on safe mode and after a reset.
https://www.youtube.com/watch?v=URGlfZlnCvw&feature=share - safe mode with show taps enabled
https://www.youtube.com/watch?v=1r9LNINohHA&feature=share - factory reset
Any help is appreciated. Thank you in advance.
Same exact thing happened to me on Android 10!
I've since opted into the Android 11 beta and am currently on DP3! Sadly, however, this issue is still there and has gotten WORSE as now touch responsiveness breaks completely whilst in the app switcher - not just for the bottom row of apps.
I submitted a bug report yesterday and was told that this was a duplicate issue that should be fixed in one of the upcoming Android 11 internal builds (which could mean the second release candidate build, unless they meant the last Dev Preview Build - DP4). So it will either be fixed next month, or 2-3 months from now when that second release candidate build drops for Android 11!
Status: Won't Fix (Obsolete)
Thank you for reporting this issue.
We were able to reproduce the issue on the reported build. However, the issue is not reproducible on our internal development build (which is ahead of the public release). Please test it on the final public release and let us know if you are still having issues.
Click to expand...
Click to collapse
NippleSauce said:
Same exact thing happened to me on Android 10!
I've since opted into the Android 11 beta and am currently on DP3! Sadly, however, this issue is still there and has gotten WORSE as now touch responsiveness breaks completely whilst in the app switcher - not just for the bottom row of apps.
I submitted a bug report yesterday and was told that this was a duplicate issue that should be fixed in one of the upcoming Android 11 internal builds (which could mean the second release candidate build, unless they meant the last Dev Preview Build - DP4). So it will either be fixed next month, or 2-3 months from now when that second release candidate build drops for Android 11!
Click to expand...
Click to collapse
Great! At least I'm still not alone in this. I tried talking to support a couple of days back and they basically told me it's a hardware issue, and apparently "no one has ever reported it" and send it back for warranty which I refuse to believe. Thanks, hopefully, they do fix it.
asurabp said:
Great! At least I'm still not alone in this. I tried talking to support a couple of days back and they basically told me it's a hardware issue, and apparently "no one has ever reported it" and send it back for warranty which I refuse to believe. Thanks, hopefully, they do fix it.
Click to expand...
Click to collapse
If you end up getting sick of dealing with the issue, I'd suggest installing the "Lawnchair 2" launcher from the Play Store. It's basically a 100% rip of the stock Pixel Launcher app, but with additional customization options. Also, ironically enough, it's like twice as stable as the current Pixel Launcher as well.
If you go into the Lawnchair settings, you can even choose to enable the Google Feed - so it's a good way to circumvent the issue for now without changing the interface that you're used to at all.
This is what I just did on my phone and it seems to be working well at the moment as so far I haven't run into the bottom-row touch responsiveness issue! There are, however, still some issues with the gesture navigation - but those should be isolated to my device as I'm running the new app switcher from the Android 11 Developer Preview.
Ok all, I'm getting quite frustrated with my P6P. Was on A12 and sideloaded the OTA for 13 Beta 4.1. I didn't want to lose any data but also didn't want to enroll in the beta program which would have pushed the OTA anyway.
Beta was working but definitely noticed a hit to battery life at first and some weird things like running warmer, phone being warm just sitting on the pixel stand fully charged, just generally not feeling right. The good news was, it seemed to have gotten a little better over the next few days of use but still not great so when I saw stable A13 released last week, instead of going back to 12, I committed to using the Android flash tool and fully flashing A13.
After flash, I chose to restore my Google One / Drive backup and omg the battery life was completely abysmal and running hot. We are talking losing 20% per hour of light usage, standby was losing 10%+ per hour and wasn't going into deep sleep at all. I thought at first it was my Galaxy Watch4 and the Samsung health app causing the majority of the issues but when I disabled "activity tracking" on the app, it didn't fully resolve the issues.
Other issues include: taking phone out of my pocket, screen sometimes doesn't wake up (I remember this was an issue with A12 but G eventually acknowledged and fixed but I guess it's back), connected via Bluetooth to my car (no Android auto) the ring tone is no longer playing when I get a call, generally feeling not as smooth, weird system usages showing up in accubattery and the Android battery manager as using good chunks of battery, etc.
At this point I got another idea: reflash A13 but don't restore from backup (which I hate doing because then I have to go through every single setting to find stuff I changed and set it again both in the system and on apps). It seems like that helped a little with stand by battery drain but still seems to be draining at a higher level while in use. The issue of screen not waking up sometimes is still present and now, I just saw this morning that I tap on the Google Play System Updates within the security menu and it does nothing. I was able to get into it yesterday morning and it found an update (still says July 1 though) but I didn't reboot to complete it until this morning. Now I can't get into it anymore at all. I also found some weird folders in my DCIM folder and another one that referenced icloud and iphone transfers but I've never been an iphone user.
I'm so frustrated with this phone lately and it seems like no matter what I do, I cannot get it to work right with multiple little things as well as battery drain.
Am I the only one? And if not, anyone have any ideas on how to fix my issues? Is it time to contact Google for an RMA? I was one of the launch day orders so I don't know if my specific hardware is the issue. I am now locked in to 13 bc of the bootloader thing, I didn't manually flash the BL to both slots, only used official flash tool which you'd think of this was a critical thing, Google would do that with the flash tool but I guess they can't get their left hand to recognize what the right hand is doing.
Just typing this post on Chrome browser for 10 mins, burned through 4% battery.
You're not the only one...
https://www.reddit.com/r/GooglePixel/comments/wddk1s
nomisunrider said:
You're not the only one...
Click to expand...
Click to collapse
Thanks for that reddit article but that's not exactly answering my questions. Yes I know I'm not the only one who's had battery issues and I've gone through all those steps up to and including reflashing cleanly and wiping.
What about the other stuff I'm having issues with? Anybody else experience any of those issues? Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Essentially I'm debating on wiping again and/or reloading the OS again but if others are having the same or similar issues then it may just be Google being Google and releasing a buggy build (yet again).
Side note, I also just got a notification that Google One backup is currently running and to tap for more info but yet, I don't have it plugged it nor is the phone idle. It is on wifi though but I tapped the notification and nothing was happening. It said the last backup was at 3:37am. Also, I am now down another 10% of battery since posting this with barely any usage.
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
jrg67 said:
Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Click to expand...
Click to collapse
I've had no issues with 13 but didn't have any on 12 either. Day one phone too.
roirraW edor ehT said:
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
Click to expand...
Click to collapse
I did what I thought was starting fresh the last time around (Sunday). Used the official flash tool and didn't restore anything from backup. All I did was add my Gmail accounts and then manually downloaded every app I use and then tried to set all the settings again in both system and apps to how I like them. Is there something I'm missing? Is there a difference between the pixel repair tool and the Android flash tool? What about the settings that are flash tool? I have them set to wipe, lock, and force flash everything. Not sure if that exists on pixel repair tool. I've also noticed a fairly large reduction in size of the backup that occured last night with the apps section showing only 44 apps at about 11.7MB in size when my previous backup was 60 apps at about 48.2MB. I'm thinking of just wiping/reflashing again for the 3rd time but restoring from backup this time since it really didn't make much difference.
How about the Google play system up bug thing? Can someone tap on it and see if it comes up checking for an update or if it does nothing like me. And when I say nothing, just the menu option to tap on just lights up but doesn't open anything. How about the issue with the screen not waking up if taken out of your pocket?
For what it's worth, I haven't started from scratch since I accidentally did last December (after originally setting my phone up in late October or in November). I used the Android 13 factory image over top of my existing install without wiping.
I'm under the impression that yes, there is a difference between the Pixel Repair Tool and the Android Flash Tool, but I've never actually used the Pixel Repair Tool. I know the first several months, at least, the Pixel Repair Tool hadn't yet been updated to work with the Pixel 6 Pro. It may have been updated since then, I just don't know for sure.
When I have wiped/factory reset in the past six years (starting with my Pixel 1), I always restore all or almost all data from Google's backup. I do have Swift Backup do automatic nightly backups as well, but I only restore data (through Swift Backup) for the apps that I really need to - definitely not very many.
Your settings for the Android Flash Tool sound fine.
Is the "Google Play System Up(date) bug where clicking on it doesn't do anything? If so, it doesn't do anything for me, either. Mine doesn't even light up, but I have dark mode on, plus using Pitch Black theme from AOSP mods.
I rarely have my phone in my pocket, so it probably just doesn't come up often enough for me to have noticed, so I can't confirm one way or the other.
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
roirraW edor ehT said:
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Click to expand...
Click to collapse
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Google Play Store v31.9.20-21 is rolling out and will fix that Play System Updates "bug".
jrg67 said:
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
Click to expand...
Click to collapse
Here's another weird one.. apparently now I can't keep my phone on vibrate while in the car. For a test, I turned my ringer on and then tested it again.. low and behold, it rang through the speakers in my car. This is trash. I know Android enabled in-band Bluetooth audio years ago and I recall this same thing happening way back with my nexus 6p and each pixel I've had but this one. There was a setting in developer settings to turn that off which fixed it and allowed it to work correctly but with this phone, it worked out of the box so I never thought twice about it. I just checked the dev settings and it's nowhere to be found. I have no idea what A13 could have done to screw that up nor do I know if the dev setting even existed on this phone prior to A13. I just don't get it. I guess I could see if there's any updates to my car's multimedia system but I have an Audi and any software updates come from the dealer for a price. How dumb. I guess I'll be scouring the Audi forums for a fix on that.
Meh, the Google Play Store updates are irrelevant to me. So no worries there on my part, haha. But this phone's battery life has been rather questionable. I have, however, noticed that after being on the full A13 build for around a week or so and disabling 5G from the get-go that my battery now lasts MUCH longer. My phone does not seem to generate as much heat either - which is always a plus. But I also seem to have more phone/messaging reliability than I have had in the past with this device.
I am beginning to think that the modem and 5G has had the most to do with this phone's imperfections.
Also - for OP - but I have noticed that my phone often doesn't wake up with a single tap either - but only when the gyroscope stays mostly stationary for a longer period of time. When I pull the phone out of my pocket, it usually comes on with one tap. But if it has been sitting on a table or other mostly flat surface for a while, it takes two taps to wake the display.
Ultimately, I won't be getting the Pixel 7 Pro. I will, however, be getting the Pixel Fold which should launch at around the same time =).
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
96carboard said:
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
Click to expand...
Click to collapse
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
jrg67 said:
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
Click to expand...
Click to collapse
Well, aside from the bugs issue, as time goes on, more and more you need something besides what it ships with in order to actually have security and privacy. Google has fallen a very long way from the openness and respect that they once promised. The final straw for me was when they started working with governments to include and share covid contact tracing functionality.
Update:
Apparently the 4th complete wipe and OS flash was apparently the trick to fix the majority of my phone's issues. I did restore from my backup this time because the last time that I started from scratch, it made no difference. I figured if it's still going to be buggy, I may as well have all my info and settings correct. It's now been about 24 hours. See below for status of my issues.
1. Massive battery drain - fixed for the most part. Still have to restrict Samsung Health app but for the most part, it seems to be back to normal.
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
3. Play system update button broken - already found this wasn't an A13 bug. I still haven't gotten the fixed update of playstore but before this latest wipe and OS flash, I sideloaded the latest version and it fixed it.
4. Connected to Bluetooth in car no longer plays ringers out loud. - Weird one as I think this is part A13 because Google baked in a new BT stack that's been in development since A11 called gabeldorsche https://www.androidpolice.com/android-gabeldorsche-bluetooth-stack/ and partly my infotainment system in my car. I am not on the current version of the car's infotainment but since my car is a '14 Audi, it doesn't have OTA updates.
5. Heating up during normal use - seems to be fixed
6. Warm while on the pixel stand and fully charged - haven't been able to observe this one bc last night, I put the phone on the stand and by morning it was at 72% and not charging. No clue if that's a new bug or if it was just not sitting on there just right. Didn't really look into it but we'll see what happens tonight.
So that seems to be the majority. Overall the phone doesn't feel "weird" anymore and most things I was having trouble with appear to be resolved. Sort of ridiculous that I had to wipe and reload the OS 4 times though.
jrg67 said:
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
Click to expand...
Click to collapse
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
96carboard said:
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
Click to expand...
Click to collapse
This one still may be around for me but perhaps not as severe as it was during the first 2 times I loaded 13. I just experienced it about an hour ago. Took phone out of my pocket to place on my desk at work and screen was black but the AOD did eventually come on by itself after about 10 long seconds. We'll see what happens.
So, I opted in for the close beta program in my iqoo 9 that vivo provides with its funtouchos and after some day I got an update which was funtouchos 13 based on Android 13 and I installed it real quick but boy it was buggy! First thing I noticed was the lagging then came the strangest thing, the lower portion of the screen was not responsive to some specific actions like the "clear all" tab in the notification shades was not responding and had to be tapped several times to trigger the func., Instagram suffered a lot for its tabs are at the bottom and it was annoying to tap 5-6 times just to get from one tab to the other.
Initially I thought my touch screen is at fault but then I figured out my dock apps were all good and the touch response was okay so I downgraded the device and now it's working fine.
But then even after downgrading I am getting the same update version: PD2136BF_EX_A_38.8.12 , i haven't even agreed to the beta program.
Now am confused whether I should update again and take the risk or shall I wait for further updates?
Even I had the same issues.