Related
I just got ota update released again, it is 1.15 GB, i will wait with update.
I am located in Eastern Europe. Good luck
Have received the notification.
Can confirm the size.
Will not install it for now.
I am on Android Pie, so i don't know what's up with people who have Android 10 already installed.
underdoq said:
I am on Android Pie, so i don't know what's up with people who have Android 10 already installed.
Click to expand...
Click to collapse
I'm also on Pie. I have received the notification am the size is what you mention (1.15gb) but since is brting problematic, I will not install for now.
I just got it too, should i update?
Just installed!
Everything is fine not any big bug that worth mentioning!
It can lag a bit if you wont make a factory reset afterwards
Came directly from pie 10.0.20.0 everything is fine i think ots safe to install
AnonymousAL said:
Just installed!
Everything is fine not any big bug that worth mentioning!
It can lag a bit if you wont make a factory reset afterwards
Came directly from pie 10.0.20.0 everything is fine i think ots safe to install
Click to expand...
Click to collapse
Is it the same update as few days ago?
11.0.4? If yes ,then I wonder why they stop the OTA just to start it over without changing/fixing anything...
It's like xiaomi devs are a bunch of amateurs who doesn't own this device therefore unable to test their updates and just hope for the best when they release one...
Yes it's the same 11.0.4.0
AnonymousAL said:
Yes it's the same 11.0.4.0
Click to expand...
Click to collapse
Thanks for the reply!
gonna update until they pull it back again
I'm on Q from the first update - 11.0.2.0 - which is running without major bugs, just a bit worse battery usage and less maximum brightness They don't offer me any update yet.
digitri said:
I'm on Q from the first update - 11.0.2.0 - which is running without major bugs, just a bit worse battery usage and less maximum brightness They don't offer me any update yet.
Click to expand...
Click to collapse
There's a process for applying the OTA or a fastboot image you can use to upgrade.
I expect you'll get a OTA offer soon anyway. I just missed it last time but got it now. OTA from 10.0.20.0
Thread closed
Please use existing threads like this
strongst
Forum Moderator
Just read this german article where they are saying what I put in the title.
Source: https://www.notebookcheck.com/Amazo...ate-auf-Fire-OS-7-und-Android-9.482412.0.html
This isn't new. The newer Hd10 and hd8 are both Android 9
Michajin said:
This isn't new. The newer Hd10 and hd8 are both Android 9
Click to expand...
Click to collapse
The claim is prior gen variants of 7" and 8" models (eg: 2018 HD8) will see an OTA upgrade to FireOS 7.
Last time Amazon attempted an OTA FireOS upgrade (vs update) was with the 3rd gen HDX line (FireOS v3 -> v4); lots of bricked devices in that debacle.
Seen these reports before. I have my doubts.
DB126 said:
The claim is prior gen variants of 7" and 8" models (eg: 2018 HD8) will see an OTA upgrade to FireOS 7.
Last time Amazon attempted an OTA FireOS upgrade (vs update) was with the 3rd gen HDX line (FireOS v3 -> v4); lots of bricked devices in that debacle.
Seen these reports before. I have my doubts.
Click to expand...
Click to collapse
According to the Amazon developer site it is happening: https://developer.amazon.com/docs/fire-tablets/ft-identifying-tablet-devices.html. We'll have to wait and see, but this should be possible without re-partitioning the device. The bogus upgrade of some tablets from Fire OS 5 to 6 would have required a much larger system partition.
Hopefully it will be possible to upgrade and keep an unlocked bootloader and TWRP.
MontysEvilTwin said:
According to the Amazon developer site it is happening: https://developer.amazon.com/docs/fire-tablets/ft-identifying-tablet-devices.html. We'll have to wait and see, but this should be possible without re-partitioning the device. The bogus upgrade of some tablets from Fire OS 5 to 6 would have required a much larger system partition.
Hopefully it will be possible to upgrade and keep an unlocked bootloader and TWRP.
Click to expand...
Click to collapse
Wow, nice! Might be useful for the developers for the lineage roms of the fire 7 (2019) and fire 8 (2018).
hope no one is waiting for an OS update on older devices...
the original promised date of 7/28 comes n goes...all we get from Amazon is that now it says:
"Will uplevel from Fire OS 6 to Fire OS 7 at a future time."
newnewcomputer said:
the original promised date of 7/28 comes n goes...all we get from Amazon is that now it says:
"Will uplevel from Fire OS 6 to Fire OS 7 at a future time."
Click to expand...
Click to collapse
I just noticed that, too. Blame it on Covid-19. People working from home not getting it done fast enough.
If this gets me stock Android on my hd10 2019 I care if not , what does it really matter what it runs on ... The functionality is still limitedly the same ...
olaf2k4 said:
If this gets me stock Android on my hd10 2019 I care if not , what does it really matter what it runs on ... The functionality is still limitedly the same ...
Click to expand...
Click to collapse
It probably won’t help on your 2019 HD10, as it already has FireOS based on Android 9. This update will bring the Pie-based FireOS to older devices.
Seems to be no planned update for the Fire HD 10 7th Gen although it has similar hardware as the Fire HD 8 8th Gen. It will stuck on FireOS 5 which is based on Android 5 and which is already out of support. Shame on you Amazon!
BeniS98 said:
Seems to be no planned update for the Fire HD 10 7th Gen although it has similar hardware as the Fire HD 8 8th Gen. It will stuck on FireOS 5 which is based on Android 5 and which is already out of support. Shame on you Amazon!
Click to expand...
Click to collapse
Not at all. Amazon never promised major firmware (version) updates. Similar and identical are not the same thing.
Any expectation of investment in a 3 year old budget platform is pure fantasy.
Fire OS 7.3.1.5 is now avaliable for download for the Karnak (HD 8, 2018) and Mustang (7, 2019) tablets on the Amazon software download page.
I tried to flash the new version through TWRP. To be on the safe side, as when I updated to OS 6.3.1.5 through TWRP my recovery was overwritten, I edited the updater script. Flashing seemed to go OK (I re-flashed Magisk afterwards) but it bootlooped on the Amazon logo after rebooting. I could not even turn the tablet off by holding down the power button. I opened the case, disconnected the battery and booted into TWRP recovery after reconnecting. I then wiped and restored the backup I made just before flashing. The tablet is working fine again but I now have a vendor partition. I hope will be possible to keep an unlocked bootloader/ TWRP and upgrade to OS 7/ Pie.
My HD 8 is still mostly stock (just have Google's services and Play Store on it). So I downloaded the OS, and it's installing on its own right now.
It's a wait-and-see as to what it does. I know the UI is the same, but there are some notifications that the thing just would not show. I'm hoping this will work better.
MontysEvilTwin said:
I tried to flash the new version through TWRP... but it bootlooped on the Amazon logo after rebooting... I hope will be possible to keep an unlocked bootloader/ TWRP and upgrade to OS 7/ Pie.
Click to expand...
Click to collapse
thank you 4 trying n report! i dl the bin file but was too chicken to flash. i guess for a major update like this, Amazon may have to re-write the recovery, bootloader n everything else but my tin-foil hat is saying otherwise :laugh:
Pie will be nice on the HD8 but im not giving up TWRP or BL unlock 4 it!
It would be good to know if anyone has got this to work. After getting a bootloop with the modified updater script, I flashed the original update, on its own and with GAPPS (arm 9.0 nano) and Magisk (20.4). There were no error messages in either case, but the same bootloop. I tried an adb sideload with the same result. I also used amonet to flash the OS 7.3.1.5 preloader and TZ files. This alone is enough to bootloop. I have not tried flashing the new LK but this would probably cause problems with the unlock as the necessary LK exploit is likely to have been blocked (it has been with OS 6 since version 6.3.0.1).
Hopefully if you have a stock tablet and the update downloads and installs this will proceed correctly and the upgrade problems are caused by some incompatibility with the unlock exploit. If not there are going to be a lot of bricked tablets out there.
Mine updated just fine from stock setup. Even the added Google stuff still worked.
However, running through all the settings, I went to the factory reset page. As I was bringing my finger over to hit cancel, I was apparently too close to the screen, and it picked up the OK button instead. Did not know it would be THAT easy. It started wiping, and there was no stopping.
It did give me a chance to redo everything. Used the Fire Toolbox to install the Google Play stuff this time (manually did it before). That worked well.
Maybe it was the reset, but the whole UI seems a little smoother. Also, after a full day, the battery seems to be lasting longer than I expected given all the re-downloading and setting up I've been doing.
joeldf said:
My HD 8 is still mostly stock (just have Google's services and Play Store on it). So I downloaded the OS, and it's installing on its own right now.
It's a wait-and-see as to what it does. I know the UI is the same, but there are some notifications that the thing just would not show. I'm hoping this will work better.
Click to expand...
Click to collapse
@joeldf - plz let us know if ur stock update to fire OS 7 works out okay. seems like it wont work w/ unlocked bootloader which would turn a lot of ppl away from install.
MontysEvilTwin said:
It would be good to know if anyone has got this to work...
Hopefully if you have a stock tablet and the update downloads and installs this will proceed correctly and the upgrade problems are caused by some incompatibility with the unlock exploit. If not there are going to be a lot of bricked tablets out there.
Click to expand...
Click to collapse
it is a good free major upgrade (a first for any fire device in recent years). i use fire OS 7 on my HD10 2019 n it is better than OS 5 n 6. u would think that it works out-of-box for a stock tablet but i remember reading about the last time Amazon did it, there WERE a lot of bricked tablets out there
thanx again for ur tests! i will pass on this update. hopefully someone can extract some useful things from this Pie release for the LOS 16 custom ROM.
edit: @joeldf - thanks for the update! so the update works for stock ROM. since factory reset gave the same ROM, the update did rewrite the recovery. basically will have to give up BL unlock, TWRP n root for the OS 7 update. u MAY get 'em back by opening up the tablet (im not up-to-date on unlocking latest OS.) For me, I will pass.
Looks like there is a kernel patch required. It's possible the new TZ can work with the old LK, where the unlock sits. If you have yours open to do amonet, try replacing TZ as well! You can recover via contact shorting.
The
MontysEvilTwin said:
It would be good to know if anyone has got this to work. After getting a bootloop with the modified updater script, I flashed the original update, on its own and with GAPPS (arm 9.0 nano) and Magisk (20.4). There were no error messages in either case, but the same bootloop. I tried an adb sideload with the same result. I also used amonet to flash the OS 7.3.1.5 preloader and TZ files. This alone is enough to bootloop. I have not tried flashing the new LK but this would probably cause problems with the unlock as the necessary LK exploit is likely to have been blocked (it has been with OS 6 since version 6.3.0.1).
Hopefully if you have a stock tablet and the update downloads and installs this will proceed correctly and the upgrade problems are caused by some incompatibility with the unlock exploit. If not there are going to be a lot of bricked tablets out there.
Click to expand...
Click to collapse
bibikalka said:
Looks like there is a kernel patch required. It's possible the new TZ can work with the old LK, where the unlock sits. If you have yours open to do amonet, try replacing TZ as well! You can recover via contact shorting.
The
Click to expand...
Click to collapse
I am having problems getting this version working at all. I tried downgrading the version of TWRP and flashed the new software with a modified updater script (to change the paths and make it work with this TWRP version). This also overwrites the PL, TZ and LK plus recovery. I didn't get a bootloop but it would not progress past the Amazon logo screen on boot.
I downloaded it. Went to local upgrade, installed it.
Went to Magisk and did install to inactive slot like normal. And it reboots. Then a small bootloop for a second. Then goes straight back to normal. Like I never installed anything.
Any thoughts?
I tried to root by patching new boot.img but get bootloop which not fixed except after msmdownload tool
All data wiped
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
illusiveairforce said:
I downloaded it. Went to local upgrade, installed it.
Went to Magisk and did install to inactive slot like normal. And it reboots. Then a small bootloop for a second. Then goes straight back to normal. Like I never installed anything.
Any thoughts?
Click to expand...
Click to collapse
Same here. If you dont install magisk to the inactive slot it will go through and you will be in oos12. Problem with mine, it wont read my flaking sim card. Tried it 5x all same problem. Also, every reboot, your dpi goes back to 360 lmao.
I patched boot.img by canary magisk and it is working good, but no option for safetynet passing
sbute said:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
Click to expand...
Click to collapse
I used this guide but patched with magisk 23.0. still have all my modules and passing safety net. Using latest stable magisk 23.0 righteous. Thank you for this. I tried for 3 days killing my device flashing boot img. At least I know my downloaded msm tool works. On latest A12 build out for the global op9
I wouldnt recommend it tbh if its your only phone. Its buggy AH.
mattie_49 said:
I used this guide but patched with magisk 23.0. still have all my modules and passing safety net. Using latest stable magisk 23.0 righteous. Thank you for this. I tried for 3 days killing my device flashing boot img. At least I know my downloaded msm tool works. On latest A12 build out for the global op9
Click to expand...
Click to collapse
Would you or anyone else mind sharing the boot img for the OnePlus 9: OOS/Android 12 ?
I have the Global / NA version.
It would be greatly appreciated!
Zethiel said:
Would you or anyone else mind sharing the boot img for the OnePlus 9: OOS/Android 12 ?
I have the Global / NA version.
It would be greatly appreciated!
Click to expand...
Click to collapse
I have on my PC I will upload soon. Away from it currently. You really need 3 partitions to make work. Boot,vendor_boot,vbmeta
Geesh the battery is so much better on A12 after debloating how I see fit. Passing safety net, all banking apps working and still using old modules !! Score
mattie_49 said:
I have on my PC I will upload soon. Away from it currently. You really need 3 partitions to make work. Boot,vendor_boot,vbmeta
Click to expand...
Click to collapse
That would be greatly appreciated Sir!
0p9 partitions..A 12 - Google Drive
drive.google.com
All three are in here. Make sure to use magisk 23.0 to patch boot and vendor boot so you don't loose modules and magisk hide. Then you disable verity before boot with vb_meta img. You have to do from sdk platform tools folder though. Will not work just putting in a folder on desktop and pulling cmd window from there. Enjoy , follow the above guide to a T
Zethiel said:
That would be greatly appreciated Sir
Click to expand...
Click to collapse
infamousvincci said:
I wouldnt recommend it tbh if its your only phone. Its buggy AH.
Click to expand...
Click to collapse
Only issue I have is no advanced reboot menu what-so-ever. Battery is much better,stable af,modem is better as well. I would recommend .
File above edited. Correct images
mattie_49 said:
File above edited. Correct images
Click to expand...
Click to collapse
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Zethiel said:
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Click to expand...
Click to collapse
I have the correct msm tool for device. This is the forward route for you. Takes you to 11.4. Stock A11
Does anyone else have the issue of their touchscreen not functioning when they install the A12 update? Ive tried installing twice and both times my screen would not register any touches only the volume and power buttons functioned?
EDIT: NVM I MSM'd back to stock and upgraded to OOS 12 before unlocking the bootloader.
Zethiel said:
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Click to expand...
Click to collapse
if you are looking for performance, look into kernels and/or just use a kernel manager.
out of all the Roms I've tried (all but the latest havok release) crDroid is the best performance option I get from a ROM on O09. that piared with optional GApps and frequent OTA updates, its the best thing out so far. the OTA even works perfectly at retaining root without any user input. (but do a backup before reboot, its still technically a dirty flash so play safe)
sbute said:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
Click to expand...
Click to collapse
I don't want to get too off-topic, but figured I'd save a MSM wipe to some people, I can confirm this works, but only using the latest version of Magisk (v24), temporary boot will not work with v23 (the last one with MagiskHide), it caused Qualcomm crashdump and no recovery or fastbootd.
If anyone looks into other root spoofing solutions with the newer version v24, from Magisk settings use Zygisk, select apps using Enforced Denylist, and Universal SafetyNet Fix, there is also Shamiko, which I haven't tested personally.
From my own experience, DenyList+Universal SafetyNet fix+Selinux Switch if you need to switch between permissive and enforced Selinux are enough. Apps won't get to know there is root, safetynet is passed, and selinux checks are passed (that one took me a long while to figure out)
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
If the bottled version is higher on Android 12, it probably is, then you can't downgrade. In the build number, I believe it's the 5th number from the right might want to check that it with Google. If the new firmware has a higher number there NO going back...
robotov said:
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
Click to expand...
Click to collapse
Yes, it's possible, and I've done it.
robotov said:
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
Click to expand...
Click to collapse
I confirm that I also downgraded from Android 12 / One UI 4.0 (January 1 patch) to Android 11 / One UI 3.1 (November 1 patch) without problems. There were several aspects of the new version that were bothering me a lot, now I'm happy both versions are binary 3, but it will cease to be in the following versions for sure...
Hi can you help me with guidelines to upgrade to android 12? I'm using Note 20 ultra n985f/ds. It was previously a Live demo unit but is now fully functional on android 10. My csc is OXM WWD... looking forward to your help
Also I'd like to know which is better, should I just change my csc so I can receive the push for update via OTA or just follow a guideline for flashing with Odin, thanks in advance
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