Just got the Oreo 8.1 update on my Project Fi Moto X4 (Motorola Version: OPW28.46-13). The phone does not show up in Windows anymore. No MTP, no ADB. It does charge. I've tried it on two different PCs. It was working seconds before applying the update. The cable does work properly with an S8.
Anybody else seeing this?
I'm a professional Android developer and I was using the phone for development before the update. The other issue is that Developer Mode was disabled after update. I re-enabled it after 8.1 and it didn't work. I've disabled/enabled USB Debugging and developer options several times.
Update:
Tried on OS X now too, same issue. OTG does work.
Work-Around:
https://forum.xda-developers.com/showpost.php?p=76430795&postcount=32
No mention in the release notes: https://mobilesupport.lenovo.com/us/en/Solution/MS127386
Can you help us out with getting the OTA via https://forum.xda-developers.com/moto-x4/how-to/androidone-april-ota-t3784442?
Neffy27 said:
No mention in the release notes: https://mobilesupport.lenovo.com/us/en/Solution/MS127386
Can you help us out with getting the OTA via https://forum.xda-developers.com/moto-x4/how-to/androidone-april-ota-t3784442?
Click to expand...
Click to collapse
It takes some days for the update to show on motoota.
The previous two months became available on there as my phone got the OTA notification. I have yet to see someone who has receive the April, verify they attempted Motoota here on XDA or Reddit.
dburckh said:
Just got the Oreo 8.1 update on my Project Fi Moto X4 (Motorola Version: OPW28.46-13). The phone does not show up in Windows anymore. No MTP, no ADB. It does charge. I've tried it on two different PCs. It was working seconds before applying the update. The cable does work properly with an S8.
Anybody else seeing this?
I'm a professional Android developer and I was using the phone for development before the update. The other issue is that Developer Mode was disabled after update. I re-enabled it after 8.1 and it didn't work. I've disabled/enabled USB Debugging and developer options several times.
Update:
Tried on OS X now too, same issue. OTG does work.
Click to expand...
Click to collapse
I am experiencing the same situation with Project Fi Moto X4 32G (Motorola Version: OPW28.46-13). No MTP, no ADB. It does charge OK. I had no such problems before the upgrade from 8.0 to 8.1. I tried on both Linux and OS X. The same issue. And yes, USB OTG works.
I have the exact same issue and fun fact, this means it no longer works with an Android Auto head unit (it worked flawlessly right up until the second the OTA update was installed).
Factory Data Reset did not fix it. Guess we are hosed unless somebody finds a work-around.
dburckh said:
Factory Data Reset did not fix it. Guess we are hosed unless somebody finds a work-around.
Click to expand...
Click to collapse
This makes me not want to take the update now. What bad news.
Folks, I have this too on my Moto G5S Plus after the April security patch for Nougat. No notification shade when I plug into the PC. No way to access MTP, ADB, etc... I also effects my charging. After the MTP interface fails, I have to reboot the phone before it will charge again.
Post in the Moto/Lenovo forum please. It's a HUGE problem.
dburckh said:
Just got the Oreo 8.1 update on my Project Fi Moto X4 (Motorola Version: OPW28.46-13). The phone does not show up in Windows anymore. No MTP, no ADB. It does charge. I've tried it on two different PCs. It was working seconds before applying the update. The cable does work properly with an S8.
Anybody else seeing this?
I'm a professional Android developer and I was using the phone for development before the update. The other issue is that Developer Mode was disabled after update. I re-enabled it after 8.1 and it didn't work. I've disabled/enabled USB Debugging and developer options several times.
Update:
Tried on OS X now too, same issue. OTG does work.
Click to expand...
Click to collapse
Got the OTA, it does not work and we'll never know why.
Just got the OTA. Don't have my OTG cable, but i can can confirm that I see device in fasboot, but not in ADB.
Neffy27 said:
Got the OTA, it does not work and we'll never know why.
Click to expand...
Click to collapse
Motorola just replied to my support request saying that they are going to replace my phone! I'm hoping it doesn't come to that.
dburckh said:
Motorola just replied to my support request saying that they are going to replace my phone! I'm hoping it doesn't come to that.
Click to expand...
Click to collapse
I am confused... Because of a software update broke ADB?
It would seem so. I will probably try to talk them out of it. I would rather have them escalate a fix.
encountered same issue
dburckh said:
Motorola just replied to my support request saying that they are going to replace my phone! I'm hoping it doesn't come to that.
Click to expand...
Click to collapse
Same here, just got 8.1 this morning on A1 moto x4 and android auto does not work anymore when it is connected to my car HU.
I just got the April 1 8.1 update this morning on my Moto X4 OPW28.46-13. Exactly the same thing. Android Auto head unit doesn't recognize the phone (or vice versa), and the USB options are greyed out and say only "not connected" whether plugged into the head unit or a computer. Project Fi support tells me I need to hard reset the phone. I don't have time to do that at the moment, but they tell me that if it doesn't work (and I very much doubt that it will) they'll "check the warranty options." Which I think is a euphemism for "send you a new phone if it's still under warranty".
What aggravates me about this (aside from the huge waste of time of having to deal with it) is - what if the phone were NOT under warranty? After their update breaks my phone, would they then tell me to buy a new phone?
My stupid X4 will download the 8.1 OTA, start installing, then fail halfway through. Guess there's a bright side after all.
dburckh said:
It would seem so. I will probably try to talk them out of it. I would rather have them escalate a fix.
Click to expand...
Click to collapse
Same response from support. I wonder if anyone that is able to create a TWRP backup, and test if a clean reset fixes issue.
jhedfors said:
Same response from support. I wonder if anyone that is able to create a TWRP backup, and test if a clean reset fixes issue.
Click to expand...
Click to collapse
I made full wipe after the update, nothing has changed.
Related
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
there have been quite a few people with this same issue. i havent seen any direct fix.
if you are locked, i would suggest you wait it out, or wait for the sbf file to get leaked. there is a way to sideload it, but its risky being locked and no sbf to save you if a problem comes up.
if you are unlocked, there are directions in the General forum to sideload the ota. there is no risk if you are unlocked.
if you are locked, the only thing i would suggest to try is re-flashing the stock 9.30.1 with rsd and see if it will pull the update afterwards. there is no guarantee this will work, but your phone will be 100% clean stock after the flash and give you the best chance to grab the ota if available.
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
Did you download it and then said to apply it later? If so, are you rooted? If so, hook up your phone to your PC and adb shell into it. Type "su" and hit enter to go into superuser mode.
Navigate to the /cache directory and you should see the OTA .zip file sitting in there. Copy it to your external SD card and then you can load it manually via the recovery.
If you're not rooted, then you won't be able to navigate into the /cache directory. Or, if you didn't have it download when you got the notice (or couldn't download it), then it won't be there.
More update issues
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
zeb carter said:
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
Click to expand...
Click to collapse
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Factory REst doesn't solve 4.4.2 WIFI issue on Razor MAxx HD
TXKSSnapper said:
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Click to expand...
Click to collapse
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
egutwillig said:
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
Click to expand...
Click to collapse
That's a shame because for me, the FDR fixed the Wifi/Blue-tooth issue as it did for many others. Might have been a hardware issue (faulty radio, etc).
i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!
I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?
seems like noone has this kind of troubles
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?
loth77 said:
i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!
Click to expand...
Click to collapse
geri.st said:
I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?
Click to expand...
Click to collapse
loth77 said:
seems like noone has this kind of troubles
Click to expand...
Click to collapse
nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
J0ch3nK said:
Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?
Click to expand...
Click to collapse
https://jira.cyanogenmod.org/browse/BACON-2822
nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
this is still CM and not oxygen OS
Latest OTA killed my WiFi. I dont have the receipt anymore and I might be screwed even though I only bought this tablet less than 3 weeks ago. Is there anyway to revert back to an earlier build. I'll do anything. Im not rooted or unlocked. Any help to fix this and I will donate to u I promise.
It looks like they are aware of the issue so I would wait a few days before freaking out. You can always push an update from your pc or SD card if it comes to it. My gf has the k1 and hers just has an update tonight that said it was fixing wifi issues. When did you install this update? What version was it?
Sent from my SHIELD Tablet using Tapatalk
TokedUp said:
Latest OTA killed my WiFi. I dont have the receipt anymore and I might be screwed even though I only bought this tablet less than 3 weeks ago. Is there anyway to revert back to an earlier build. I'll do anything. Im not rooted or unlocked. Any help to fix this and I will donate to u I promise.
Click to expand...
Click to collapse
You should be able to get the receipt reprinted at the store you got it from if you used a credit or debit card. Worse comes to worse I'm pretty sure Nvidia would be able to tell how old the unit is.
Im gonna go back to the store I bought it at tomorrow. I used my debit card so hopefully that will work. Thanks.
I just exchanged my K1 for a new one. Staying on 5.1.1 for a while. **** you Nvidia!
Mods please close
I took the OTA last night and had the WiFi problem. I was able to fix it by re-flashing the staging blob (source) and rebooting.
Incidentally, I switched to Bliss 6 and had the exact same issue, and solved it the exact same way. My guess is that the OTA didn't correctly patch the blob, but after all the work I have done today to try and get myself a working tablet who knows whether that was the root problem or not.
jeffober said:
I took the OTA last night and had the WiFi problem. I was able to fix it by re-flashing the staging blob (source) and rebooting.
Incidentally, I switched to Bliss 6 and had the exact same issue, and solved it the exact same way. My guess is that the OTA didn't correctly patch the blob, but after all the work I have done today to try and get myself a working tablet who knows whether that was the root problem or not.
Click to expand...
Click to collapse
Can I ask how you re-flashed this .img, I have had no wifi for 2 days now and am starting to get impatient waiting for a fix. Any help is appreciated, thanks!
roaming4gnome said:
Can I ask how you re-flashed this .img, I have had no wifi for 2 days now and am starting to get impatient waiting for a fix. Any help is appreciated, thanks!
Click to expand...
Click to collapse
I downloaded the file I linked to above, rebooted the tablet into the bootloader, and flashed it with fastboot (`fastboot flash staging blob.img`). There are plenty of tutorials already explaining how to boot into your bootloader and install adb/fastboot on your computer to accomplish this, so I won't fill up the Internet by duplicating it here.
Thanks! ya I'm familiar with the process, I decided to flash factory .img and back and running now
Bliss v6.0 Shield K1
jeffober said:
I took the OTA last night and had the WiFi problem. I was able to fix it by re-flashing the staging blob (source) and rebooting.
Incidentally, I switched to Bliss 6 and had the exact same issue, and solved it the exact same way. My guess is that the OTA didn't correctly patch the blob, but after all the work I have done today to try and get myself a working tablet who knows whether that was the root problem or not.
Click to expand...
Click to collapse
is it working for K1 tablet or original because my k1 have the same problem
I've had the same problem on my K1. (wifi)
A factory reset (launched by the android menu, not from bootloader) solved the problem.
It's long but it's normal.
Of course I had to set everything back, but my tablet was stock so I lost nothing.
Now it's rooted and everything is fine.
Toked, same issue. Was able to work around issue by turning on one of the options in developer mode. Turn on "use legacy dhcp client". Wifi back. Hopefully a permanent fix soon
Not meaning to necropost here, but turned on my shield after a long while off and had this same issue, changing to "use legacy dhcp client" worked! Thanks!
How to fix wifi
Step 1: Turn the Shield tablet off
Step 2: Remove SD card
Step 3: Turn tablet back on
WiFi should now be working
Step 4: Reinsert SD card.
Hey guys,
Not sure when this started, but it wasn't like this out of the box...
At some point via an OTA update, I lost fast charge, I lost stereo sound from the USB c port (only plays left channel) and I can't connect my phone to a computer (yes, drivers etc are all in tact.. it's a software issue with USB on the phones ROM)
I managed to update via OTA to miui10 8.8.4 device ROM after a few tried (had to wipe).. issue still persists.
I've seen a few people mention this issue, but most responses are suggesting hardware replacement. I know for a fact the hardware is unaltered and was fine prior to update.
Anyone know a fix for this? It literally takes 8 hours to charge my phone ATM. Given I can't connect via USB, I can't unlock my phone and go custom ROM (I'm kinda liking miui 10 also)...
Any options asides from waiting for an OTA uodate?
Thanks
Bump!
Still have this issue. Anyone else?
I'm now on MIUI 10 (8.9.20) and problem still exists. Driving me crazy. My mi6 charges in no time at all. This mix 2s takes forever
leighaus said:
Hey guys,
Not sure when this started, but it wasn't like this out of the box...
At some point via an OTA update, I lost fast charge, I lost stereo sound from the USB c port (only plays left channel) and I can't connect my phone to a computer (yes, drivers etc are all in tact.. it's a software issue with USB on the phones ROM)
I managed to update via OTA to miui10 8.8.4 device ROM after a few tried (had to wipe).. issue still persists.
I've seen a few people mention this issue, but most responses are suggesting hardware replacement. I know for a fact the hardware is unaltered and was fine prior to update.
Anyone know a fix for this? It literally takes 8 hours to charge my phone ATM. Given I can't connect via USB, I can't unlock my phone and go custom ROM (I'm kinda liking miui 10 also)...
Any options asides from waiting for an OTA uodate?
Thanks
Click to expand...
Click to collapse
Sounds bad. Some people also have problems with the front camera wich stopped working after an OTA Update.
Have you tried Clean flash a custom rom?
I cant flash custom rom, as i cant unlock bootloader - usb is not detecting. I am literally stuck on stock beta until it is fixed.
Yea sry i kinda failed to notice this point
Would it then be posible to flash a Recovery ZIP of an older Version of MIUI via the official MIUI updater app?.
Ps.. I dont have the Phone myself just trying to bring some ideas in.
leighaus said:
I cant flash custom rom, as i cant unlock bootloader - usb is not detecting. I am literally stuck on stock beta until it is fixed.
Click to expand...
Click to collapse
Maybe you need to change a cable.
I have about 4 official cables abd 4 non official. Makes no difference. My mi6 still works as expected with the same cables.
It is a rom based problem.
Still not fixed . Absolutely ridiculous.i actually hate this phone because of this stupid software issue
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