OK, so I have never owned a Xiaomi phone before, so the following might be perfectly normal, I don't know, that is why I am asking, but it doesn't seem normal to me based on my previous experience. I should say that my bootloader is unlocked and my phone is rooted as that probably makes a difference. This is how my boot sequence runs (all times approximate):
First I get the 'lock bootloader' splash for 6 seconds.
Next I get a static 'Android One' for 27 seconds.
Next up is a scrolling 'Android One' splash (the coloured line going across the centre of the screen) for 9 seconds.
Next is the 'Mi' splash for 3 seconds.
Next is the password entry screen for about 5 seconds.
Next is a completely blank screen for about 23 seconds.
Next is another scrolling Android screen for 20 seconds.
Next is another 'Mi' splash for 3 seconds.
Next I get an 'Android is starting' screen overlaying my home screen for 3 seconds.
Finally I get a home screen.
The total boot time is 1m30 to 1m40 more than double my previous phone's boot time (but that was running Lineage, a considerably lighter OS).
So is this normal or is it just me?
Its ok
bootloader unlocked and root
reboot 46 seconds total with Oreo
Related
In short, the phone is stuck in a bootloop unlike any I've read about before. All on its own, it constantly makes the bootup vibration pattern but it does not boot up. The screen does not light up, it is completely black (backlight is off as well). It is sitting on my desk doing the vibrate patter (bzzz-bz). Then 40 seconds later, again, (bzzz-bz).
If I could see the screen, I imagine it is going past the 1st Asus Logo screen, then trying to load the OS (2nd Asus Logo), but crashing and restarting.
This happened after I flashed fastboot (droidboot), recovery, and boot. All flashed successfully, so I went into Recovery and started to "wipe cache". It was taking too long so I thought it froze and forced a restart. After that, I never saw the screen light up again.
Any ideas as to what is going on? The phone has no damage (at least physically ).
Yes, wiping cache takes a long time you have to wait it out, forcing reboot before it finishes will result in bootlooped, that is covered in many many threads, you will need to reflash entire Rom from bootloader.
Problem is, I cannot get into bootloader. Its still doing the vibrate cycle I described, it's been 8 hours already.
Try holding the power button and volume up toll you get 2 vibrates then release power, if that does not help it sounds like your power button is stuck in depressed mode
Stuck in depressed mode? But I am able to press it, and I hear it click, and click back up. The "spring" seems to be working fine.
Hi guys, I have a Flo here that most times (95 times out of a hundred) will hang on the "Google" bootscreen or in the boot animation that follows, and stay forever in bootloop until I give it a gentle (sometimes more than one) tap on the back. Then it will work fine, although the screen turns unres
Hi everyone,
I have an AT&T Samsung Galaxy S7 Active SM-G891A that just became unresponsive. It began with a vertical pink line appearing and disappearing intermittently down the right side of the screen. After a few times if this happening, the phone froze while playing "Laser Overload," which I had just downloaded, for about 30 minutes. I performed a soft reset and the phone went into a boot loop that lasted 20 minutes or so- sometime it would make it to the AT&T screen and freeze, sometimes it wouldn't make it past the "Samsung Galaxy S7 Active" screen.
Finally, it booted up normally but was running slowly. I powered it down, thinking it may have been overheated, and left it alone for a few hours. Upon starting it back up, it worked fine for about 15 minutes but then froze once again. I performed another soft reset, but this time the screen stayed black- no image and unresponsive to touch, but with the top left LED indicator a steady blue. It stayed like this for an hour or so until I plugged it in; the screen did show the lightning bolt charginf icon but it took about 10 minutes for it to display the battery percentage (0%). The phone had 75% battery when it became unresponsive.
Once it had charged to about 15%, I booted it up (leaving it plugged in) and again it became stuck in a boot loop. I rebooted to the system menu (Home + volume up + power) and cleared the system cache in hope that this would resolve the issue, but again the boot loop. Finally, I performed a factory restore on the phone from the boot menu. This time, the phone booted to the AT&T screen before it froze with a horizontal line of static near the bottom of the screen. I soft reset it and the phone made it through the boot screens to a Wi-Fi login. I logged in to the network and the phone froze again, this time shutting down completely and is unresponsive to being plugged in- multiple cables and chargers being used. There is no top-left LED light when plugged in, and attempting to power on the phone using any method does nothing.
Is it possible that playing a game for a half hour was the final straw in killing a graphics processor? I hadn't used this phone for any thing graphics intensive and this game seems rather simple (2D only, no simulated camera, etc.), but it's a secondhand phone that I've had for a few months now. The phone had been dropped a few days ago- only about 2ft onto a rubber mat with no damage to the phone. Could this have caused it?
Is there any way to verify what the issue could be with the phone unresponsive as it is? Any help would be appreciated.
I have a Note 8 Global Version with MIUI 11. If my phone is locked and screen is off and I press the lock button or even scan my finger, it is taking approximately 4 to 5 seconds for the screen to be lit. A few information if it helps:
1. Let's say in lock screen the screen is supposed to be lit for 5 seconds. I press the lock button. Wait 3 seconds. Then the screen light turns on. But just after 2 seconds the screen turns off. It means the processor does read the button press immediately but somehow fails to turn the screen on immediately.
2. After the MIUI 11 update I was tinkering with the new options. And I found one old option actually - double tab lock button to start camera. I turned that on and checked how that works. That was the first time I noticed the delay of 3/4 seconds. So I thought it was related and disabled it. But still the issue persists.
Never happened to me. How much free RAM do you usually have free? Looks like the device is running slow in elaborating processes.
Do you notice other lags while normally using your phone during the day?
From 2 weeks ago it happened something strange, the phone will be showing for seconds black screen when opening an app
I tried flashing by fastboot and now i get permanent black screen not even showing in fastboot anything (but you can see the screen is on)
So it seems is due to battery not giving enough power when are heavy tasks