Related
I'm new to rooting, installed MIUI and loving it so far. My hw is 003. Everything is working so far but i have a few questions -
1. Do you use the default kernel or replaced it? I've seen screen tearing a few times and battery life could be better so I'm thinking of trying a different one. Read a number of threads in the root section.
2. Did you replace the lockscreen? I'm asking because I love its look, but if you enable security there's no slide to unlock and its not so useful.
3. How often do you update the MIUI build - I read it comes out every Fri, do they have major changes?
#3, the official build is done on friday, porting to individual phones is on/around sunday
1. I'm on the 1.1.28 build and using the kernel that came with it. Savage 1.6. It is by far the best kernel I have ever had the pleasure of flashing and I have no reason to use anything else. When I update to a newer build, I will most likely flash this kernel over it.
2. Still using stock lockscreen. I agree that the pattern lock could have been implemented better.
3. What elegantai said.
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
2. Never really noticed that before. Can you pull it down with a Sense ROM? It's been so long I can't remember. You can always hit the home key while in a call and pull the bar down from there.
ECrispy said:
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
Click to expand...
Click to collapse
I actually have the same problem with the app killing. Great feature yes but it always kills the app regardless of how long or short I press it lol. Changing the duration didnt seem to help.
Sent from my PC36100 using XDA App
_MetalHead_ said:
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
.
Click to expand...
Click to collapse
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
ECrispy said:
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
Click to expand...
Click to collapse
That's odd, it works perfectly for me. What MIUI build are you on?
_MetalHead_ said:
That's odd, it works perfectly for me. What MIUI build are you on?
Click to expand...
Click to collapse
Latest - 1.2.11
I dunno, maybe it's a bug with that build.
from my observations the back tap close program happens only when a program is lagging. if you dont have too many things going on at once it shouldnt be a problem
yeahh it is a problem occasionally for me. I normally skip and flash every other week. This week im gonna flash again though, because it seems slow.
So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).
^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.
Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.
@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?
I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96
Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.
This is happening when the screen is on right? Or is the screen turning off and then not turning I again?
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...
Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...
icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?
Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.
Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.
Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!
Specifically Double tap to wake up & sleep.
I realize I am supposed to hold onto the phone but it still does not work.
It's seemed a bit finnicky to me. It seems to work when I need it to, but if I'm just messing around it sometimes doesn't. I just calibrated the G-Sensor in display settings. Maybe that will help?
I did actually, twice, each on different leveled surfaces.
Phone must be held in portrait mode, or with the top slightly elevated when you double tap. I think it also doesn't work in power saving mode
The Helpful Post said:
Specifically Double tap to wake up & sleep.
I realize I am supposed to hold onto the phone but it still does not work.
Click to expand...
Click to collapse
Check your g-sensor if it works
kangconsumer said:
Check your g-sensor if it works
Click to expand...
Click to collapse
my friends htc one m9 is having the same issue.... gestures aren't working when the screen is off. Auto rotation isn't working either
The calibration sensor moving left to right isn't working...
This was after I updated the firmware to 1.32.401.17.. Anyone else having this issue?
I've noticed that my M9 only double taps to sleep if its in the lock screen. Is that what its suppose to do? It won't sleep if it's not in the lock screen.
If the phone is on the desk I nudge it slightly so it rotates a tiny bit to the left or right before double tapping to wake. You have to be in the lock screen to double tap to sleep.
Double tap works fine for me. If you don't move the phone beforehand, triple tap will wake it.
Sent from my HTC One M9 using Tapatalk
motion launch no worky
So peeps, I was having the exact same problem as op, narrowed it down to the latest HTC lockscreen update from play store, go back to stock version of the lockscreen and try it out, mine works now perfectly, left some feedback on the play store for HTC on the update. Try it see if it helps any ?
auto-rotate and double tap not working
jbm76 said:
my friends htc one m9 is having the same issue.... gestures aren't working when the screen is off. Auto rotation isn't working either
The calibration sensor moving left to right isn't working...
This was after I updated the firmware to 1.32.401.17.. Anyone else having this issue?
Click to expand...
Click to collapse
I am having the same issues. My auto rotate does not work even though it is turned on. Also, my double tap to turn on and off does not work. They both worked just fine for the first couple days and then suddenly no longer work. I can't think of anything I could've done to cause this.
Ozzyclaus said:
I am having the same issues. My auto rotate does not work even though it is turned on. Also, my double tap to turn on and off does not work. They both worked just fine for the first couple days and then suddenly no longer work. I can't think of anything I could've done to cause this.
Click to expand...
Click to collapse
It just started working again, we updated the firmware and assumed it was that. But it wasn't it seems... see if you are updated to the latest HTC service pack, etc
I have the same issue, it has started when I updated to the last AT&T Software from the HTC website and I tried reinstalling, resetting to factory setup but it still not working
Same here, it stopped working when I updated to latest AT&T by RUU.
It was working fine without any issues when I was using a custom ROM ViperOne.
Auto-rotate works fine, it's just the double tap to wake and camera launch (landscape + volume up) don't work.
I tried calibrating g-sensor twice, still not working. Factory reset didn't fix.
I am 100% sure it's a software bug. Hope they fix.
Edit: HTC Released an update on the Play Store and has supposedly fixed it.
Same here After update
I am having this problem as well. Gestures stopped working when the screen is off as soon as I installed the newest AT&T firmware update. All of my apps are up to date and the phone is not rooted. I purchased it two weeks ago. I performed a factory reset after I updated firmware to make sure everything was in order.
Android: Stock 5.1
HTC Sense 7.0
Software number 2.6.502.18
Kernal: 3.10
I too have the same problem with the new AT&T update. Has anyone figured out how to pix this? Please share on how to solve this problem, I want double tap to wake on my phone! Thanks for any help.
Adroid version 5.1
HTC Sence version 7.0
Software number 2.6.502.18
Kernel version 3.10
Faders said:
I too have the same problem with the new AT&T update. Has anyone figured out how to pix this? Please share on how to solve this problem, I want double tap to wake on my phone! Thanks for any help.
Adroid version 5.1
HTC Sence version 7.0
Software number 2.6.502.18
Kernel version 3.10
Click to expand...
Click to collapse
That is not the latest AT&T update. It should be 2.11.502.18. Have you checked the Play Store to see if you have the latest version of motion launch? Search for HTC Motion Launch. If you do, I would look into updating the AT&T software to the latest to see if that helps.
on an international phone i had the same problem on first boot, but after a reboot, everything worked fine..
I also..my new m9 (since now stock) wake gesture fail frequently !!!!
In power saver mode totally....incredible!!!
Any solution?
Double tap to wake seems to look at the proximity sensor too to check it isn't in your pocket. Make sure nothing is covering it, such as your case if you use one.
With both the M7 and M8, I could swipe up on the camera (stock ROM) and the camera would launch right away without having to do the pattern unlock. With the M9 (which I just got 2 days ago), when I swipe up on the camera it does not launch the camera app, but it delays for ~3 seconds, then tells me to do pattern unlock. When I do the unlock, it goes to my home screen and still doesn't launch the camera app.
Is this behavior consistent for everyone else on the stock ROM/launcher?
Still investigating what launchers/ROMs I'd be most interested in for this new device or whether it's even worth keeping. Having quick camera access is pivotal and the motion gesture holding the phone in landscape and pushing the volume button is a complete joke (works 1/3 the time... maybe).
I have both m8 and m9 and no software differences at all in this area . try to factory rest your phone and I think the problem will be fixed .
Sent from my HTC One M9 using XDA Free mobile app
hamud.q said:
I have both m8 and m9 and no software differences at all in this area . try to factory rest your phone and I think the problem will be fixed .
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
It couldn't be the same software.
A) M9 is 64 bit OS and M8 is 32 bit
B) Sense 7 hasn't even been officially released for the M8, so if you're using a Sense 7 rom on your M8, then it is a port from an M9 rom.
So...stock it's definitely not the same software and even if you're running the "same" custom ROM on both, they're not really the same, just similar.
I am able to launch the camera from the lock screen with no issues and always have. I agree, do a wipe and reflash; something is borked on your phone.
slmclarengt said:
With both the M7 and M8, I could swipe up on the camera (stock ROM) and the camera would launch right away without having to do the pattern unlock. With the M9 (which I just got 2 days ago), when I swipe up on the camera it does not launch the camera app, but it delays for ~3 seconds, then tells me to do pattern unlock. When I do the unlock, it goes to my home screen and still doesn't launch the camera app.
Is this behavior consistent for everyone else on the stock ROM/launcher?
Still investigating what launchers/ROMs I'd be most interested in for this new device or whether it's even worth keeping. Having quick camera access is pivotal and the motion gesture holding the phone in landscape and pushing the volume button is a complete joke (works 1/3 the time... maybe).
Click to expand...
Click to collapse
Let me see if I understand...So you have camera icon in your docked icons? How are you turning on the screen? Power Button? Then you pull up the camera icon from the lock screen? Then you get a 3 second delay and then you have to enter your pattern unlock? And after you enter your pattern, you get the home screen and not the camera?
That doesn't sound normal. I'm not on a stock rom right now, but when I put the camera icon in my docked icons, turn the screen on and swipe it up, I get the camera immediately (but I'm using smartlock right now and I don't have to enter my pin when I'm in the office).
Good (?) to know I'm just uniquely seeing bad behavior. I'll try factory reset phone under backup & reset. Loving the ability to search settings fluidly now.
Thanks everyone for the info!
jollywhitefoot said:
It couldn't be the same software.
A) M9 is 64 bit OS and M8 is 32 bit
B) Sense 7 hasn't even been officially released for the M8, so if you're using a Sense 7 rom on your M8, then it is a port from an M9 rom.
So...stock it's definitely not the same software and even if you're running the "same" custom ROM on both, they're not really the same, just similar.
Click to expand...
Click to collapse
Man if u read again I said there is no differences in this area ( about launching the camera) . despite it's 64 or 32 or sense 6 or 7 . ok?
Sent from my HTC One M9 using XDA Free mobile app
slmclarengt said:
Good (?) to know I'm just uniquely seeing bad behavior. I'll try factory reset phone under backup & reset. Loving the ability to search settings fluidly now.
Thanks everyone for the info!
Click to expand...
Click to collapse
Have you tried temporarily turning off lockscreen security?
jollywhitefoot said:
Have you tried temporarily turning off lockscreen security?
Click to expand...
Click to collapse
Just tried that to no avail. Even with the setting at "Lock Screen" but no pattern/pin lock, it still delays then goes to home screen regardless of app I attempted to launch.
SW Version 2.6.651.11
5.1
Sense 7
slmclarengt said:
Just tried that to no avail. Even with the setting at "Lock Screen" but no pattern/pin lock, it still delays then goes to home screen regardless of app I attempted to launch.
SW Version 2.6.651.11
5.1
Sense 7
Click to expand...
Click to collapse
What about other apps? Like mail or messages? Do they have the same behavior? I assume they would, but I really know know why that would happen. Did you check in the Sprint forum to see if anyone else is having that issue?
After getting a new device with 5.0.2 that worked fine, I upgraded to 5.1 and saw the issue again. That's when I looked more thoroughly through the Play Store for app updates (probably skimmed through on first device). I'm pretty sure after updating "HTC Sense Home" with its proclaimed "bug fixes" the issue was gone. Camera and other swipe up apps on lock screen behave as expected now.
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.