I got a bug in nokia5.3 after the android 11 update, any scroll that was broken, the keyboard didn't respond, even though the android keyboard, the game that was touched didn't respond, very sorry to update to android 11
Switch back to Stock ROM.
jwoegerbauer said:
Switch back to Stock ROM.
Click to expand...
Click to collapse
this is stock rom
adiepribumi said:
I got a bug in nokia5.3 after the android 11 update, any scroll that was broken, the keyboard didn't respond, even though the android keyboard, the game that was touched didn't respond, very sorry to update to android 11
Click to expand...
Click to collapse
Me too!
I read a lot about the after android 11 update problems.
I have no idea how to fix the upper left touch screen problem.
It simply freezes after a while until I reboot it.
Related
Android 11 full release upgrade is available OTA now... downloading as I type this, just check for updates in Settings - System.
Anyone able to get chat bubbles working?
Also screenshot from the apps menu does not work unless full gesture or 3 finger btw..
Upgrade went ok in the end, but after an hr or more I had to reboot a couple of times to get it to complete. Was stuck 3/4 of the way up the progress bar. Stock/unroooted.
You need google Android messaging beta app to get bubble chats working. Currently using it now.
Launcher settings are not sticking with gesture navigation again. Lawnchair is my default launcher, but it is still trying to open Pixel Launcher. This issue went away a while back in 10, but seems to be back in 11. This alone is enough to have me switch back.
Anyone get root working? I tried magisk canary and patching the boot.img from the latest update aka Android 11 final but it wouldn't boot
adm1jtg said:
Anyone get root working? I tried magisk canary and patching the boot.img from the latest update aka Android 11 final but it wouldn't boot
Click to expand...
Click to collapse
No problems here. Used latest Canary to patch 11 boot.img. Flashed 11 full image. Let it boot up once. Rebooted to bootloader, flashed magisk patch boot.img. Booted up fine.
stompysan said:
Launcher settings are not sticking with gesture navigation again. Lawnchair is my default launcher, but it is still trying to open Pixel Launcher. This issue went away a while back in 10, but seems to be back in 11. This alone is enough to have me switch back.
Click to expand...
Click to collapse
I had this issue too, but I was using the traditional 3 button navigation. Every hour or so when I pressed home button it would want me to choose between Nova and Pixel launcher even though I already set Nova as default. Also after clicking the nav bar buttons, they would stay highlighted which was slightly annoying.
On top of these two minor bugs I just don't like Android 11 overall. I went back to AOSiP lol and I won't even bother updating past 10 custom ROMs until some custom ROMs based on 11 are available.
DriveEuro said:
No problems here. Used latest Canary to patch 11 boot.img. Flashed 11 full image. Let it boot up once. Rebooted to bootloader, flashed magisk patch boot.img. Booted up fine.
Click to expand...
Click to collapse
Would you mind uploading your patched boot image? For some reason it's not working for me. either and also did it the same way you described. Says the boot file is corrupted. Can boot with older patched kmages fine just no root though.
Edit* Nevermind I got it working. Took a few reboots and a couple more trys at patching and the patched boot image no longer was read as corrupted.
Still can't get it to work. Boots to Google screen then just goes back to bootloader screen. So far not liking 11 at all wanted to root it to make backups and maybe load aosip
Can someone link me to the canary build your using maybe i have an older one but it says it's for Android 11
Hello guys, I present the following problems: Bubbles WhatsApp does not work, internal audio in screen recording does not work, notification bar or navigation bar does not hide when opening Applications like fb or cod Mobile.
I cant save photos sent to me inside Facebook messenger & any screengrabs I edit vanish when I try to move them to another folder in Gallery, maybe this is more to do with the apps needing updating by developers? stock unrooted
had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that
I briefly tested Android 12 as well as Android 13 GSIs on my TB-Q706F, with necessary and hopefully up-to-date vendors flashed for the purpose.
While most of the OS functionalities work fine, I noticed there are major issues with touchscreen, as when gaming, from time to time touchscreen would stop responding altogether, disrupting gameplay. I originally noticed this when I started using A12 GSI, but it appears the issue persists with A13 GSI as I have tested recently.
I'm not sure if other users on A12/A13 GSIs are also having the issue. In my case, the issue with touchscreen doesn't appear to manifest in Android 11 GSIs. When I reverted my tablet back to Android 11 GSI, the issue went away and touchscreen is now working fine.
So far I've only tested GSIs, so I don't know whether stock ZUI 14 is also affected like any other A12 GSI. I can't really test too much about this as I need the tablet to be in a usable state, and that touchscreen-related issues are not trivial to capture and inspect.
It's strange that no one else reported this issue. I encountered the same when I recently flashed to the official global Android 12L via Lenovo rescue assistant and encountered intermittent unresponsive touchscreen during gaming also.
Over the course of using this tablet on Android 11 for more than 1 year and I had never encountered such issues.
When I encountered this issue, I just quickly press the power button to put it on standby and wake it up again.
NSC779 said:
It's strange that no one else reported this issue. I encountered the same when I recently flashed to the official global Android 12L via Lenovo rescue assistant and encountered intermittent unresponsive touchscreen during gaming also.
Over the course of using this tablet on Android 11 for more than 1 year and I had never encountered such issues.
When I encountered this issue, I just quickly press the power button to put it on standby and wake it up again.
Click to expand...
Click to collapse
Touch screen works fine with no major issues when using Android 11. It's only when using Android 12 and onwards that the touchscreen would intermittently stop responding.
The problem is, touch-related issues may not be noticeable if not doing any intensive gaming, and are very hard to pinpoint.
I recall Lenovo was aware of some touch-related issues at least according to the official A12L Developer Preview image at some point. Not sure if the issues have been resolved by the time ZUI 14 came out.
Had Lenovo ever released kernel sources for our device (Q706F/Q706Z)? I don't know where one can request kernel sources from them...
EDIT: So turning off the screen then turn it back on would restore the touchscreen functionality? If this works 100%, then logcats during the moment when you turn the screen off, as well as the moment when you turn the screen on, may contain hints.
Hello ! I have Q706F (wifi only) can I get a clean Android 11 on it ? or some custom A12 rom ? I reallly want to be stock to android as possible. You guys mostly use A11 ? Thanks
bernek said:
Hello ! I have Q706F (wifi only) can I get a clean Android 11 on it ? or some custom A12 rom ? I reallly want to be stock to android as possible. You guys mostly use A11 ? Thanks
Click to expand...
Click to collapse
If you want a clean Android you can try Phh's AOSP GSI. You should be able to find an A11 build there.
My Fold2 5G(Indian) phone screen freezes(or becomes irresponsive) in every app screen when inactive for some seconds after the latest One UI 5.0 Update in February last week.I have to go back to home screen and come again to the app screen for for further activities.My Android version is 13.How to solve this issue? Anybody please help.
Waiting with Thanks...
pnsdhrn said:
My Fold2 5G(Indian) phone screen freezes(or becomes irresponsive) in every app screen when inactive for some seconds after the latest One UI 5.0 Update in February last week.I have to go back to home screen and come again to the app screen for for further activities.My Android version is 13.How to solve this issue? Anybody please help.
Waiting with Thanks...
Click to expand...
Click to collapse
Are you install lately new app?
If not in my opinion try factory reset.
I have A13 and everyting is fine.
_GRIZZLY_ said:
Are you install lately new app?
If not in my opinion try factory reset.
I have A13 and everyting is fine.
Click to expand...
Click to collapse
Thank you Grizzly for your response.I got the latest February Update.But before this, when I installed the January Update this screen inactive arised.When I installed the February Update,I thought that this problem would have been solved.But it didn't solve.
@pnsdhrn Read your PMs, please.
I can't buy a new phone. And EMUI sucks badly. Furthermore, i can't install custom recovery or ROM thanks to bootloader lock.
Emo19 said:
I can't buy a new phone. And EMUI sucks badly. Furthermore, i can't install custom recovery or ROM thanks to bootloader lock.
Click to expand...
Click to collapse
That doesn't sound good at all You'll have to endure it.
Emo19 said:
I can't buy a new phone. And EMUI sucks badly. Furthermore, i can't install custom recovery or ROM thanks to bootloader lock.
Click to expand...
Click to collapse
Look here:
Speed up a slow Android device - Android Help
Try the steps on this page if your phone: Runs very slowly Lags Takes a long time to respond After each step, restart your phone to see if it fixed the issue. Important: Some of
support.google.com
jwoegerbauer said:
Look here:
Speed up a slow Android device - Android Help
Try the steps on this page if your phone: Runs very slowly Lags Takes a long time to respond After each step, restart your phone to see if it fixed the issue. Important: Some of
support.google.com
Click to expand...
Click to collapse
I know the basics. Over the top, i also debloated my EMUI too.
It's never Android OS - in the state it comes with phone out of the box - what lags, but what user added.
jwoegerbauer said:
It's never Android OS - in the state it comes with phone out of the box - what lags, but what user added.
Click to expand...
Click to collapse
Yes, it is not Android's fault. It is Huawei's. LOS or AOSP would make this device very good. But at now with just few apps, even youtube UI lags.