I have a Samsung Galaxy A21s phone that I am trying to install Android 12 on. I have unlocked the bootloader, I go into the recovery mode and I select bootloader, however when I get there, it is just some red text saying "Entering fastboot mode..." and then it gets stuck there.
Does anyone know why this is happening, and if there is any way to fix it without carting it off to Samsung?
I have Android Auto installed, but I can't run it:
Is this something with my Android (10) or my gear (DooGee S88 Plus)?
This is the first time, I have such situation. So far, in the past 10+ years of using Android, I could only see apps that I can install and run or that I can't install. I have never seen before an app that I can install, but can't run, since this seems pointless.
BTW: When I tap "Uninstall" in Google Play then, after something that looks like uninstallation process, I don't see "Install" button again, but "Update" instead (which would suggest that application hasn't been actually uninstalled). This is also very weird and also I have this situation for the first time in my Android life. What is this, what is causing this or what am I missing in the above picture?
The issue was solved by using SM-T210's /sbin/healthd file instead. The two share the same SoC and the kernels were quite similar so it worked perfectly.
If I do a factory reset on a rooted Samsung/Android phone will it remove the root? Factory reset will return the phone to its out-of-the-box state, right?
Thanks to @alecxs, I just don't unlock the device bootloader correctly.
I just need to run the command fastboot oem unlock ******** twice. And after that, it's working well.
Here the command and the output I have done to resolve the issue
➜ ~ fastboot oem unlock **********
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.002s] Finished.
Total time: 0.002s
➜ ~ fastboot oem unlock **********
(bootloader) Bootloader is unlocked! Rebooting phone
OKAY [ 0.165s] Finished.
So, I run the command twice, and it works, thanks to all of you in the comments.
I'm using Android 12 on a Google Pixel 3. My default browser is Brave. I sometimes also use Chrome.
For many types of links, such as https://www.linkedin.com/feed/update/urn:li:activity:6883161994237636609/ , my phone correctly opens the content via the related native app (in this case, LinkedIn).
I want all YouTube URLs to open via the YouTube app and thought my settings (shown below) would enable this behavior; what is wrong?
Although many similar questions have been asked before, their old answers haven't helped me in 2022:
You can see that my settings look appropriate here:
P.S. YouTube URLs within email messages in my Gmail app do open the YouTube app correctly.
My Xiaomi Redmi Note 9 Pro on Android 11 was updated to the latest MIUI. When I activate the hotspot or USB tethering, when connecting from my PC or other phones, it does not let me surf or use the internet.
In my Windows 10, I enter the IP config command and everything comes out well configured, either by tethering or by hotspot, but I do not navigate in any way.
Help, please.
The described situation seems to be a bug in Android Auto.
It is true that you cannot use Google Maps app without being logged in to your account. But, in this particular situation it turned out that user was and wasn't logged in in the same time. Or was semi-logged in.
Google Maps worked normally, but when opened up on the phone (not on car's display) there was a strange user-like icon in the right up corner, instead of actual user's avatar. Tapping that icon (opening user menu) immediately changed it into actual user's avatar (no actual re-login was needed). Right after that all user-related features (like saved places) started to work in Google Maps running in connected car mode.
So, after an unsuccessful attempt to get Oppo's support (they suggested a system setting factory reset), I was able to figure out the setting location for changing the toast length time on android 11 and ColorOS 11.2
Everything boils down to the Accessibility menu, particularly this one: Settings->Accessibility->Time to take action.
I basically turned it to 30 second causing the problem above described.
This was done mostly because of the "improper" description following that setting (description available only in the setting itself) as per the screenshot.
Just received a new Motorola E6 phone. It's running Android 9.0. Any time the phone is bumped, moved, or there is any kind of vibration the screen lights up. How can I stop it from doing this?
Internet search suggests I should find a "Sneak Peek" option under Settings - Displays, however, this phone does NOT have "Sneak Peek" or anything similar there. It also does not have an Ambient Display setting.