Please help me guys... my xoom , i bought it new,its about 2 weeks ago, and i've just installed adobe reader and evernote from playstore, but.... now, after i press the power button in the back, it goes off, and i want to turn it on again, so i press the power button in the back again, but its "too long to turn on", i have to wait about 3 mins, i'm getting frustated with it now, so how can i make it right??
please help me guys... very need your help...
I'm afraid there probably isn't anything wrong with your Xoom.
Newer Android devices have a feature, lets call it "Quick Boot"...which allows a device to be turned on in seconds! But what is actually happening is, the device is never properly off. The RAM is stored, and when the device is turned on again, it resumes...sort of like your computer hibernating.
You can check this out by comparing the boot times of turning a device off and on, and rebooting...where everything is shut down. Rebooting should take about 50 to 100% longer.
The Xoom however is ever so slightly too old to have this Quick Boot feature. When you turn the Xoom off, it is off properly. And when you turn it on, it has to load everything fresh.
Give it a chance though. The Xoom might be getting on a bit now, but it is still a great device. And if the boot time is annoying you so much...simple...don't turn it off!
I got a used HTC sensation XE with audio beats, with WiFi not working (GB was installed). Wifi & Teathering services always remained on "Error" when wifi turned on. Bluetooth, SIM services all were doing good. Used it in this condition for 2~ days, all went fine exept I once found it powered off while it was on wall charging.
Then I upgraded it to ICS downloading Stock ICS ROM from this thread. Which was isntalled successfully and the WiFi started to work.
It worked fine for 2 days, except my phone restarted on its own once or twice. At that moment i was using 340 MB of internal storage for apps and 750 was free. One night i was playing "Cut the Rope" and my phone prolonged a game sound and turned off, I removed battery and replaced it and turned on, but nothing happened, it remained off. Attached it to charging but no response. I left it there and after about an hour charging light turned on and it powered on.
From that moment, Phone often shows message "Low Storage Space", Hangs and then turns off. And fails to turn on again, sometimes for 24 hours. I did a "Factory Restore" from boot loader (power + voluem dwn), but its still behaving same.
Lattest: It turns on by pressing power button for 20 to 30 sec. Sometime goes upto lock screen and turns off, sometimes turns off on first screen and most of the times dies at audio-beats screen (after or before change is screen brightness). Remains dead for some time then again to same position.
Any expert openion/ experiance/ etc....
I don't have option of replacement. What to do? :crying:
khaled_j_k said:
From that moment, Phone often shows message "Low Storage Space", Hangs and then turns off. And fails to turn on again, sometimes for 24 hours. I did a "Factory Restore" from boot loader (power + voluem dwn), but its still behaving same.
Lattest: It turns on by pressing power button for 20 to 30 sec. Sometime goes upto lock screen and turns off, sometimes turns off on first screen and most of the times dies at audio-beats screen (after or before change is screen brightness). Remains dead for some time then again to same position.
Any expert openion/ experiance/ etc....
I don't have option of replacement. What to do? :crying:
Click to expand...
Click to collapse
But it never turns off just sitting at the bootloader or fastboot screen? Doesn't turn off while doing a factory reset? Only when trying to load software and activate hardware booting into the OS?
MS Gray Man said:
But it never turns off just sitting at the bootloader or fastboot screen? Doesn't turn off while doing a factory reset? Only when trying to load software and activate hardware booting into the OS?
Click to expand...
Click to collapse
Yes it didn't turned off sitting idle in bootloader. But it completed its factory reset in 3 restarts; 1st right after loading stock, 2nd configuring apps 10/36 and 3rd at 23/36. Then 4th time it died on fresh Lock Screen.
NOTE: I removed SIM, SD Card in the very beggining of the problem.
khaled_j_k said:
Yes it didn't turned off sitting idle in bootloader. But it completed its factory reset in 3 restarts; 1st right after loading stock, 2nd configuring apps 10/36 and 3rd at 23/36. Then 4th time it died on fresh Lock Screen.
NOTE: I removed SIM, SD Card in the very beggining of the problem.
Click to expand...
Click to collapse
I would try replacing the battery... it's about all that's left as it appears your phone is locked and more or less all stock..
Cuts down your options for things. Any sign of moisture exposure?
MS Gray Man said:
I would try replacing the battery... it's about all that's left as it appears your phone is locked and more or less all stock..
Cuts down your options for things. Any sign of moisture exposure?
Click to expand...
Click to collapse
Haven't tried out any other battery, I tested it on voltage meter and it showed ok, BUT you have got a point; I must check it with some other battery of working phone.
Moisture:: Well there was Mist/ Fog a few days back but mostly I stayed at warm place + I kept it in fromt of fan heater after ealry episodes..
This has happened 2 times lately, at least once for sure while on the charger over night.
I wake up,and have notifications from over night so the light is flashing. I try to open the phone,and nothing happens . The phone is very hot also. So I long press the power button and up volume at the same time,and phone vibrates 3 times , then shuts off. I can then turn the phone back on ,and after a few min it cools down, and operates normally.
I purchased this device from a sony store in Thailand where I live ,and is is unlocked. Please Please help me figure this out. Thanks in advance. Everything is up to date also. The phone has onboard diagnostics, if turned on it can send information to sony to help find problems. Should I use that system to help?
Thanks again, B
Check what apps you have given permission to provide notifications. Sounds like one is possibly looping.
Looping app??
augie7107 said:
Check what apps you have given permission to provide notifications. Sounds like one is possibly looping.
Click to expand...
Click to collapse
I hope this screen shot attached. Check these usages for me please. What do you think? Thanks.
Doesn't look like anything there would cause an issue. I don't have any issues and I don't use stamina mode. Possibly try it a couple nights without stamina mode?
I'll try it. Thanks
Phone: Pixel 3a
This sounds like a very specific problem I have, however I can't describe it with any other words. Usually, I turn on airplane mode before I go to bed. Almost every morning, when I deactivate airplane mode, the phone freezes completely and I have to do a hard reboot with long pressing the power button.
I am running Android 11 with the latest update. The problem, however, started with the first Android 11 update. There were no such weird problems happening on Anroid 10. I even did a clean flash of the system rom, which did not fix the problem. When I wiped the internal storage as well, it worked for about two days, but now I am back to the freezing.
I still have warranty on the phone and thinking about RMAing it, because I can't find any other person having this problem.
The weird thing is that the freezing does not happen, when airplane mode is only turned on for a short time. Like, right now, I could turn it on and off without a problem. You see, I am a bit lost and don't know what to do!
And maybe something to add: When I turn off airplane mode in the morning, I am able to receive messages for a split second before it freezes completely. When I do a reboot, these messages are just gone. So, they are not getting saved properly I guess ... Really annoying.
What happens if you turn airplane mode on, use another phone to send a few messages to yours then turn off airplane mode?
What happens if you turn airplane mode on, use another phone to send a few messages to yours then turn off airplane mode?
Click to expand...
Click to collapse
It works like normal. It annoys me that I can't really reproduce this issue right now, but I believe it has something to do with the reconnection to the mobile network. Maybe it could even be a mobile provider related problem? But that is just a wild guess ...
https://support.google.com/android/answer/7664448?hl=en-GB
Press power then keep pressing on "restart" and activate safe mode. Check if the problem persists for a week in safe mode. If it doesn't then an app you're using is probably the origin of the problem.
N3utro said:
https://support.google.com/android/answer/7664448?hl=en-GB
Press power then keep pressing on "restart" and activate safe mode. Check if the problem persists for a week in safe mode. If it doesn't then an app you're using is probably the origin of the problem.
Click to expand...
Click to collapse
Thank you, I am going to try this then.
EDIT:
Seems like the Battery Charge Limiter app from the play store was causing the problem. It worked well with Android 10, but not so well on Android 11.
Hello, so about 2 days ago from now, my device, while waiting for the bus started to bootloop for no known reason. Skipping into this weekend, I have tried almost everything to get it working without the risk of any data loss, unsuccessful I am here.
Right, so the main problem of the device is that it's very unpredictable, that being said, the device doesn't really have a consistent bootloop. First it started off with the usual, constant bootloop, and then when it got enough of that, it shut off, or I just put it into Fastboot mode to shut off, because it wouldn't stop bootlooping. The power button would always restart it. The loop would start at the start of the booting process(MI Logo) and end when the device would turn on the Lock Screen and then about 3 or 5 seconds later it would crash. Meaning that I can change any setting in the top UI, like wifi settings, bluetooth and whatnot(not that it meant anything since I only had about 5 seconds). Then I left it shut off overnight, and the next day I turned it on, and it actually booted... This gave me a lot of time to back up every photo and video in a panic, and I still had a bit of time. First I thought it was bootlooping because the storage was full, so I uninstalled a lot of apps, and moved about 7GB of data onto my PC. Since the problem kept going, I left it overnight once again to retrieve any more data I needed(right now there's still data on it that I need like 2FA tokens and passwords).
By the way the amount of time I was able to spend in the device was about 5 or 8 minutes before it shut off.. Maybe even more, I had time to move the whole gallery onto my PC and still had time. And the second time I had access to it was just recovering more data, that time I also thought of enabling "OEM Unlock" but I decided not to(like an idiot).
This time though I did not wait till the phone restarted on its own, rather the battery fully discharged at 0%. And that put a somewhat permanent "Empty battery logo" on my recovery UI(the one that uses ADB). I can still access ADB, like the menu works it's just that I'm going blind into it, I can click volume down and select options, it's just that I can't see what I'm clicking. I tried booting it the 3rd time, now in even worse condition than before and now it's fully bricked the whole battery system, because meanwhile I was waiting for it to "do it's thing again" so I can access it I decided to charge it. It 100% had enough time to charge to full battery, yet the phone still thinks the battery is empty and wont show me the Recovery UI. And when I manage to get to the Lock Screen the battery shows 2% and there's absolutely no way it's that low. I slept a good hour waiting for it to charge, and that should be at least 70 - 90%.
Right, so I'm thinking it's either a bad battery connector or a faulty temperature sensor that's making the phone crash, because I can only access it once and that's when it fully cools down, since there's nothing going on in it anyway when it's dead. And later when it heats up it crashes.?
But then again, accessing it like 10 or 20 minutes after it naturally shuts off only gives me about 2 or 3 extra seconds when it fully boots even though being cool to to the touch. And leaving it overnight gives me minutes of time.(if)
Right now I have no idea if I will be able to access it ever again, so if I do I'm backing up my tokens and turning "OEM Unlock" on so I can flash it or factory wipe it. And if I don't, my question is.. Is there anything I can do to save this mf phone? Since I don't even know if I have the right idea to why it could be doing this in the first place, and if I can't turn on "OEM Unlock" I can't even factory reset it properly.
I've tried using ADB to pull files, and just use shell, but I can't due to Errors, I also can't boot a custom recovery without OEM. Shutting it off before it shuts off also doesn't do anything.
Tex2083 said:
Hello, so about 2 days ago from now, my device, while waiting for the bus started to bootloop for no known reason. Skipping into this weekend, I have tried almost everything to get it working without the risk of any data loss, unsuccessful I am here.
Right, so the main problem of the device is that it's very unpredictable, that being said, the device doesn't really have a consistent bootloop. First it started off with the usual, constant bootloop, and then when it got enough of that, it shut off, or I just put it into Fastboot mode to shut off, because it wouldn't stop bootlooping. The power button would always restart it. The loop would start at the start of the booting process(MI Logo) and end when the device would turn on the Lock Screen and then about 3 or 5 seconds later it would crash. Meaning that I can change any setting in the top UI, like wifi settings, bluetooth and whatnot(not that it meant anything since I only had about 5 seconds). Then I left it shut off overnight, and the next day I turned it on, and it actually booted... This gave me a lot of time to back up every photo and video in a panic, and I still had a bit of time. First I thought it was bootlooping because the storage was full, so I uninstalled a lot of apps, and moved about 7GB of data onto my PC. Since the problem kept going, I left it overnight once again to retrieve any more data I needed(right now there's still data on it that I need like 2FA tokens and passwords).
By the way the amount of time I was able to spend in the device was about 5 or 8 minutes before it shut off.. Maybe even more, I had time to move the whole gallery onto my PC and still had time. And the second time I had access to it was just recovering more data, that time I also thought of enabling "OEM Unlock" but I decided not to(like an idiot).
This time though I did not wait till the phone restarted on its own, rather the battery fully discharged at 0%. And that put a somewhat permanent "Empty battery logo" on my recovery UI(the one that uses ADB). I can still access ADB, like the menu works it's just that I'm going blind into it, I can click volume down and select options, it's just that I can't see what I'm clicking. I tried booting it the 3rd time, now in even worse condition than before and now it's fully bricked the whole battery system, because meanwhile I was waiting for it to "do it's thing again" so I can access it I decided to charge it. It 100% had enough time to charge to full battery, yet the phone still thinks the battery is empty and wont show me the Recovery UI. And when I manage to get to the Lock Screen the battery shows 2% and there's absolutely no way it's that low. I slept a good hour waiting for it to charge, and that should be at least 70 - 90%.
Right, so I'm thinking it's either a bad battery connector or a faulty temperature sensor that's making the phone crash, because I can only access it once and that's when it fully cools down, since there's nothing going on in it anyway when it's dead. And later when it heats up it crashes.?
But then again, accessing it like 10 or 20 minutes after it naturally shuts off only gives me about 2 or 3 extra seconds when it fully boots even though being cool to to the touch. And leaving it overnight gives me minutes of time.(if)
Right now I have no idea if I will be able to access it ever again, so if I do I'm backing up my tokens and turning "OEM Unlock" on so I can flash it or factory wipe it. And if I don't, my question is.. Is there anything I can do to save this mf phone? Since I don't even know if I have the right idea to why it could be doing this in the first place, and if I can't turn on "OEM Unlock" I can't even factory reset it properly.
I've tried using ADB to pull files, and just use shell, but I can't due to Errors, I also can't boot a custom recovery without OEM. Shutting it off before it shuts off also doesn't do anything.
Click to expand...
Click to collapse
ADB is useless at this stage, through the stock recovery.
By enabling OEM unlock, but not binding your Mi account, to start the unlocking process, it´s also useless, per se.
You can´t flash any partition through fastboot, if the bootloader is locked, by enabling OEM unlock, it´s not enough to.
Try booting to stock recovery, you can wipe your data/factory reset, in case this may help.
But, probably, the issue is with the battery or the battery connector, pay attention to the charger time, and test if the charge level is correct.
Just in case you need to power off your device, you may connect to the PC while you press the volume down button, you´ll get fastboot mode, then disconnect the cable to the PC, device will shut off itself, when the connection time expires, it may takes only seconds.
Tex2083 said:
Hello, so about 2 days ago from now, my device, while waiting for the bus started to bootloop for no known reason. Skipping into this weekend, I have tried almost everything to get it working without the risk of any data loss, unsuccessful I am here.
Right, so the main problem of the device is that it's very unpredictable, that being said, the device doesn't really have a consistent bootloop. First it started off with the usual, constant bootloop, and then when it got enough of that, it shut off, or I just put it into Fastboot mode to shut off, because it wouldn't stop bootlooping. The power button would always restart it. The loop would start at the start of the booting process(MI Logo) and end when the device would turn on the Lock Screen and then about 3 or 5 seconds later it would crash. Meaning that I can change any setting in the top UI, like wifi settings, bluetooth and whatnot(not that it meant anything since I only had about 5 seconds). Then I left it shut off overnight, and the next day I turned it on, and it actually booted... This gave me a lot of time to back up every photo and video in a panic, and I still had a bit of time. First I thought it was bootlooping because the storage was full, so I uninstalled a lot of apps, and moved about 7GB of data onto my PC. Since the problem kept going, I left it overnight once again to retrieve any more data I needed(right now there's still data on it that I need like 2FA tokens and passwords).
By the way the amount of time I was able to spend in the device was about 5 or 8 minutes before it shut off.. Maybe even more, I had time to move the whole gallery onto my PC and still had time. And the second time I had access to it was just recovering more data, that time I also thought of enabling "OEM Unlock" but I decided not to(like an idiot).
This time though I did not wait till the phone restarted on its own, rather the battery fully discharged at 0%. And that put a somewhat permanent "Empty battery logo" on my recovery UI(the one that uses ADB). I can still access ADB, like the menu works it's just that I'm going blind into it, I can click volume down and select options, it's just that I can't see what I'm clicking. I tried booting it the 3rd time, now in even worse condition than before and now it's fully bricked the whole battery system, because meanwhile I was waiting for it to "do it's thing again" so I can access it I decided to charge it. It 100% had enough time to charge to full battery, yet the phone still thinks the battery is empty and wont show me the Recovery UI. And when I manage to get to the Lock Screen the battery shows 2% and there's absolutely no way it's that low. I slept a good hour waiting for it to charge, and that should be at least 70 - 90%.
Right, so I'm thinking it's either a bad battery connector or a faulty temperature sensor that's making the phone crash, because I can only access it once and that's when it fully cools down, since there's nothing going on in it anyway when it's dead. And later when it heats up it crashes.?
But then again, accessing it like 10 or 20 minutes after it naturally shuts off only gives me about 2 or 3 extra seconds when it fully boots even though being cool to to the touch. And leaving it overnight gives me minutes of time.(if)
Right now I have no idea if I will be able to access it ever again, so if I do I'm backing up my tokens and turning "OEM Unlock" on so I can flash it or factory wipe it. And if I don't, my question is.. Is there anything I can do to save this mf phone? Since I don't even know if I have the right idea to why it could be doing this in the first place, and if I can't turn on "OEM Unlock" I can't even factory reset it properly.
I've tried using ADB to pull files, and just use shell, but I can't due to Errors, I also can't boot a custom recovery without OEM. Shutting it off before it shuts off also doesn't do anything.
Click to expand...
Click to collapse
Hey there. Was you issue fixed? I had somewhat of a similar issue. My phone did the same bootloop in two different days. First I thought it was some error after update. I didn't bother. It happened once again and after few times of crashing at lockscreen, it actually booted and I was able to use it for a day. I thought of backing up my stuff but didn't give much attention. Now it have happened once again and this time it is never getting into usable boot. If the battery is sufficient enough, it'll go into lockscreen and crashes repeatedly. Then soon it just crash after the MI Logo and the three loading dots. Safe mode does the same. It boots into lockscreen at times but the safe mode symbol is not seen.
I read you were able to get your data out of it. Did you resolve the issue?