Hello dear xda community, this is my first post here, so please be gentle
I own a Xiaomi Mi A2 Lite 4/64GB version (Model Nr. M1805D1SG), and lately all of my sensors stopped working. I am quite sure, though not 100%, that this is related to the recent July update, as I did not perform any other major system changes or even app installation in the time period since I've noticed the sensor malfunction.
I first noticed the proximity sensor not working any longer as the screen kept staying on while I was taking calls, which caused me to mute myself a couple of times during phone calls, by accidentally pressing the mute option with my check. Then it became apparent that auto rotation also was not working any more, and after a while I also noticed that my brightness was not adjusting itself any longer. I confirmed the faulty sensors by going into the hardware testing menu (by dialing *#*#6484#*#*).
Now since all sensors malfunctioned at once I highly suspect that this is an issue related to software and not a true malfunction of the physical sensors. Has anyone else experienced similar problems since the July updates, this an issue known to appear at times after an update? I'd be very thankful for any directions and/or help in this regard. Thanks for any input on this issue, cheers!
EDIT: The problem still persists after a factory reset.
Android version: 9
Build number: PKQ1.180917.001.V10.0.12.0.PDLMIXM
bluesheep13 said:
Hello dear xda community, this is my first post here, so please be gentle
I own a Xiaomi Mi A2 Lite 4/64GB version (Model Nr. M1805D1SG), and lately all of my sensors stopped working. I am quite sure, though not 100%, that this is related to the recent July update, as I did not perform any other major system changes or even app installation in the time period since I've noticed the sensor malfunction.
I first noticed the proximity sensor not working any longer as the screen kept staying on while I was taking calls, which caused me to mute myself a couple of times during phone calls, by accidentally pressing the mute option with my check. Then it became apparent that auto rotation also was not working any more, and after a while I also noticed that my brightness was not adjusting itself any longer. I confirmed the faulty sensors by going into the hardware testing menu (by dialing *#*#6484#*#*).
Now since all sensors malfunctioned at once I highly suspect that this is an issue related to software and not a true malfunction of the physical sensors. Has anyone else experienced similar problems since the July updates, this an issue known to appear at times after an update? I'd be very thankful for any directions and/or help in this regard. Thanks for any input on this issue, cheers!
Android version: 9
Build number: PKQ1.180917.001.V10.0.12.0.PDLMIXM
Click to expand...
Click to collapse
Restore factory settings.
If you do not resolve, assistance
IlSaro said:
Restore factory settings.
If you do not resolve, assistance
Click to expand...
Click to collapse
Thanks, this would have been my first approach, but I first wanted to see whether this was a common issue, hoping for a possibility to prevent the time-consuming task of reconfiguring my phone after the factory reset. Probably I'll just have to bite that bullet and set aside a couple of hours to customise my phone again afterwards.
Just performed a factory reset, my problem unfortunately still persists.
How about the touch sensitivity? Is it affected too?
toolpost said:
How about the touch sensitivity? Is it affected too?
Click to expand...
Click to collapse
I did not notice any deterioration in the touch sensitivity during my everyday usage, so I would like to say no. However I do not know how to quantify the quality of it, or how it test it, so if you can provide steps for testing the touch sensitivity I might be able to give a better answer. Either way, thanks for replying!
bluesheep13 said:
I did not notice any deterioration in the touch sensitivity during my everyday usage, so I would like to say no. However I do not know how to quantify the quality of it, or how it test it, so if you can provide steps for testing the touch sensitivity I might be able to give a better answer. Either way, thanks for replying!
Click to expand...
Click to collapse
Ahh.. then there is no difference in your touch sensitivity. If I handover my phone to you, you will definitely feel it within a minute. My situation is that worse! Please check the "July update" thread in this same forum if you want to know more.
Interesting, i had similar issue previous month. I thought it is hardware issue - but after july update sensors are working. Maybe wait for august update.
Did you try reflashing your phone bone-stock with the latest firmware?
Maybe some data got messed up in the OTA update process and of course resetting won't help you, because the data was being modified permanently in the system image.
When you reset your phone, it places the "bug" again in the system because the system was altered with a corrupted/buggy/damaged file/files.
After the July update I have a big problem with the fingerprint sensor!
TheoXSD said:
Did you try reflashing your phone bone-stock with the latest firmware?
Maybe some data got messed up in the OTA update process and of course resetting won't help you, because the data was being modified permanently in the system image.
When you reset your phone, it places the "bug" again in the system because the system was altered with a corrupted/buggy/damaged file/files.
Click to expand...
Click to collapse
I was about to go down this route, however yesterday the August security update came OTA and it seems like everything is working again! Thanks for the tips everyone. I will probably wait with the next update and see if any new problems pop up on this forum, lesson learned!
Same problem with me
Happening same with me I returned to stock rom also reset device 2 times updated every security and system OTA. Proximity, accelerometer, gyroscope,compass everything stuck and not working. ?
Related
I upgraded to Nougat yesterday, currently facing many stability issues. Any help would be appreciated on the below problems.
* Sound is unstable, screen lock does not produce any sound
* Incoming calls are often silent, no sound comes out for some reason
* HTC Live Wallpapers disappeared, I cannot locate them
* Double tap to wake problem persists, I had this problem on 6 and still cannot fix it despite many attempts including sensors, wipe clean and 3 hard reset attempts // I had this issue when I purchased my phone back in September. After many trial and errors it somehow worked on its own. Then I got a problem on my screen and took it to the HTC Service. They told me they replaced the screen and did a software update and my DT2W no longer worked
Also missing the live wallpapers over here.
NFc is working for you? Reading any NFC tag?
sloaxleak said:
NFc is working for you? Reading any NFC tag?
Click to expand...
Click to collapse
Nfc is not working either
No live wallpapers either from UK Nougat update but not encountered stability issues yet.
My Xperia keyboard was playing up but reinstalled and seems to be OK now.
Are you guys on the latest 2.41.xxx update?
comstockload said:
Are you guys on the latest 2.41.xxx update?
Click to expand...
Click to collapse
Yes, the update has brought many challenges though
cengizbey said:
Yes, the update has brought many challenges though
Click to expand...
Click to collapse
I guess that's why there's a new firmware 2.41.401.4 leaked. Would explain why they halted the Roll-Out of 2.41.401.3, and seems they already working on a fix.
Sent from my htc_pmeuhl using XDA Labs
I guess so, in any case I am very disappointed by lack of stability of many features in #HTC10
cengizbey said:
I guess so, in any case I am very disappointed by lack of stability of many features in #HTC10
Click to expand...
Click to collapse
My HTC 10 is an unlocked US version and it seems pretty stable. After initial roll out of Android 7 on Nov 25th, we then got 2 updates(Dec and Jan) which contained bug fixes and security patches.
I guess my #htc10 has hardware issues out of the box
After the UK Nougat update my Sandisk SD card is not being recognised as external storage. Was ok before the update. I've removed & reinserted a couple of times, still no joy. Anyone experienced this?
Sent from my HTC 10 using Tapatalk
I had the same problem. I had to remove it and reinsert into the phone.
Hey guys,
None of the issues above I ran into....Has OP tried a factory reset? Always recommended to Android devices after a big version upgrade.
Speaking of factory reset, well, I did it, and I have some other issues :
1. Camera in Pro mode, under long exposure duration, the image quality drops significantly...I am an photography amateur, so I know what I am talking about.
2. Sometimes the phone app does not recognize saved contacts. (It seems that this would be solved with 2.41.401.4)
3. Battery drains...much quicker than 1.95...before I can get 5h or + screen on time, now barely passes 4h.
I've also noticed a batterydrain. Although I've done a fresh install. Yesterday I did a complete wipe again without backup recovery. Battery seems stable now.
Since the OTA Nougat update i've had issues with instagram videos not playing whilst pictures work fine (on both 4g and wifi).
Also gmail no longer syncs automatically and i have to manually refresh to get mail.
Wiping cache partition and wiping app cache/ reinstalling the apps didn't work. I do feel like the update has somehow caused this as it was fine before.
Anyone else having these issues?
To comment on issues others have been having, my battery drain feels normal. And I have always has issues with gestures and double tap to wake not working
Unlocked USA 2.41.617.3 is stable here
Unlocked USA 2.41.617.3 is stable here. It brought the January security patch and also fixed all of my battery drain issues I had since the September, 2016 Android 6.1 update. I lost 2-day battery life in September, 2016.
I am finally back to 2-day battery with doze acting normally since January, 2017 update.
No extra updates or fixes yet for us in the UK. Also noticing apps will won't auto update correctly now. Getting a google play is not responding message. HTC need to sort this out asap
cengizbey said:
Nfc is not working either
Click to expand...
Click to collapse
Got it... is it a known issue?
Same, no nfc either
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
v12xke said:
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
Click to expand...
Click to collapse
I didn't have the issue on Pie and haven't installed any additional apps. It mainly happens after I haven't used the device for a while. It feels like it won't wake up so I have to hold the power button to force a reboot.
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
Yes.
I was just peaking to a buddy with a 2xl and he is having the same issue since 10.
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
bobbyphoenix said:
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
Click to expand...
Click to collapse
I just had a random reboot while taking my dog for a walk. Was only listening to SiriusXM. Think I'm going back to Pie until Google gets the kinks ironed out on 10.
https://support.google.com/pixelphone/thread/14074635?hl=en
Booted into safe mode last night and had to force a reboot this morning to get the screen to respond. This is definitely an issue with 10 and not an app. I'm going back to Pie since having my phone turn off every night is unacceptable, especially since my phone is my alarm clock.
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
droidstyle said:
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
Click to expand...
Click to collapse
I flashed the A10 Oct factory image and wiped data. Still have the issue. The only thing that fixes it is going back to Pie.
So this happened to me twice now since being on 10. My screen would go black while using the phone, and then the phone would be unresponsive, so I would need to force a reboot, but after the Google splash screen it goes into recovery, and this message shows "Could not load Android OS. You can try again, or factory reset.". I did "Try again" both times, and it booted fine. Really irks me since I can't afford to do a factory reset since I use a lot of apps that have special info in them (Like Google Auth App that has many devices I need, and resetting I would have to redo every device). I hope Google can fix these issues with the next update.
I think my issue is due to the sensor bug that was introduced in 10. I have disabled the sensors on my phone and it hasn't froze since!! Hopefully Google fixes on the Nov update.
I'm having the issue that after my screen turns off, after a certain amount of time, I cannot get it to turn back on. The phone is still on, but is unresponsive to my input. I have to hard reset.
I have tried reflashing, and tried disabling sensors. I did not have an issue with the 10 September updated, but since updating to the November update, I had the issue non-stop all day.
Platform-Tools fully updated, not using gesture navigation, but the 2-button.
@MeetFace, yes! Same here since the November update. Something isn't right.
I'm still dealing with the black screen issue. Nov update didn't fix it.
https://issuetracker.google.com/issues/143288447
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
MeetFace said:
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
Click to expand...
Click to collapse
Can you share the tasker script? I love darkmode, but have never used tasker.
darkstar73 said:
Can you share the tasker script? I love darkmode, but have never used tasker.
Click to expand...
Click to collapse
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
How can you tell this is working? I've got it setup ??
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
Thanks for this! Phone hasn't gotten a frozen black screen since I loaded the script!
Hey guys, I have updated to Android 10 from quite a sometime now(was a beta tester) and was noticing that device practically become usable after a few days of usage. Keyboard stops popping up, apps get killed in background and so on..
This issue gets fixed by a restart though. Has anyone else noticed something similar?
I am also facing issues after Android 10 update. Please let me know if you find permanent fix or solution.
Yes, same here. I reverted back to Pie. I thought I was the only one!
Sent from my SM-G960F using Tapatalk
Nope, you are not alone :crying:
i can confirm the exact same issue since OTA update to Android 10 on S9 (DBT). currently with second minor Update to DTAD build problem still there. Tried different things to work around but yet nothing helped. i assume it has something to do with memory leak on swap partition. memoryinfo & swapcheck app always show 0 byte free swap memory which cannot be freed again when this occurs. As stated before, only reset phone helps, but after 24h its the same. struggling with this since the first Q Update Version. Any suggestions highly appreciated.
Olioaglio
Auto-restart every morning
I didn't find any issue, and I didn't factory reset my device after installing the update. My phone runs quite smoothly, no issues whatsoever.
The only minor bug is that the transition animation of the clock from the lock screen to the always on display is laggy, and sometimes the instructions like "hold your phone more upright" get stuck on the always on display. I hope this will get fixed in the next update.
@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio
Olioaglio said:
@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio
Click to expand...
Click to collapse
Well I am still researching about this issue. I reported this issue couple of times to Samsung during beta testing; they said, they are unable to reproduce this issue neither they are able to see it on logs which I have sent. For me, the issue starts to appear after 91 hours of usage without a restart. Weirdly, using any keyboard other than Samsung Keyboard seems to help somewhat. I tried using Gboard and the issue somewhat mitigated but still annoying enough.
Did you guys tried reflashing the firmware using Odin?
icoolguy1995 said:
Did you guys tried reflashing the firmware using Odin?
Click to expand...
Click to collapse
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
I have reflash the firmware because it was getting unbearable. It's been 3 days, no issues yet. Will keep you guys updated.
I just cleared the System Chache and my phone is working fine now.
Same issue here. After android 10 update it's laggy as hell. Android auto crashes randomly. Spotify stops working..
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
No effect of reflashing. Same issue popup up after 4-5 days. I wonder if this is more like a hardware related issue then software?
No, i don't think so.
Got a new update, it made issue worse. Now, instead of 90 hours free of system killing spree I am getting 70 around-ish hours with good ram management. So my workaround for this is now to set auto restart in 3 days interval.
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
Did you change your default keyboard?
icoolguy1995 said:
Did you change your default keyboard?
Click to expand...
Click to collapse
yeah, i use SwiftKey since ages.
Two updates passed (currently on G960FXXS9DTD7), so far so good (despite no mention in the changelog).
Hi everyone,
So I just got my screen replaced by UBreakIFix, and now, the fingerprint sensor is getting the "Enrollment was not completed. Can't use fingerprint sensor" message. Since I remember reading about Google releasing a calibration tool, I just tried it. I tried in fastbootd (which gets stuck on downloading) and fastboot (gets stuck at installing). I was wondering if root might be an issue? Or if anyone knows any way to get it working?
Please note that I am trying to avoid factory resetting, but if it really seems like my final option, then I will try it out since I read that people still could not get the fingerprint sensor working after the factory reset.
I don't know if this still applies: Official Google Pixel Install fingerprint calibration software
I think I remember reading in this section about various users saying they couldn't get it to work on their P6P, either.
roirraW edor ehT said:
I don't know if this still applies: Official Google Pixel Install fingerprint calibration software
I think I remember reading in this section about various users saying they couldn't get it to work on their P6P, either.
Click to expand...
Click to collapse
It still does. I have been lurking around the Google Pixel community, and it seems the issue still persists, with no one able to figure out how to get the tool working. The article does say that it would require users to factory reset their phone after, but I have been reading that people still had the same issue after running the calibration tool and factory resetting. I am just questioning if it is only happening to users with root. I am even considering reflashing the official Feb OTA update and then try without root (pray that it is the issue), but if that does not work, I might have to factory reset and pray that it works.
This was happening to me recently but I got it to work on my third try. The only thing I did differently on my third try was press my finger on the sensor harder with each scan and then it worked without issue.
*Edit* - @NelsonTheMoron I couldn't tell if you were joking or not due to your username, haha (and I guess my username is pretty goofy as well lol). But I added a few words to my comment in case there was some confusion.
NippleSauce said:
This was happening to me recently but I got it to work on my third try. The only thing I did differently was press my finger on the sensor harder with each scan and then it worked without issue.
Click to expand...
Click to collapse
Did you just keep trying it until it worked on your third try? Or did you do something different?
I've been digging through my logcats late;y. I pushed the current build a bit too far and certain apps now refuse to accept the fingerprint as a authentication method. The ones that are throwing the errors always come with CA cert errors. The biometrics is tied into the security od the device. Being root is making that more janky one way or the other.
Redid my phone, stock (for me) with bare essentials as far as
S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?
Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that
blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...
I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.
Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.
If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.
Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.
Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.
no such issues here with the eu version. definitely an upgrade in every way.
After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?
xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.
blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?
xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.