Related
Twice now ill be using my phone and it will kinda stop responding and then my trackball will start pulsing, it then reboots gets to the lockscreen and reboots again. It will do this until I pull the battery. Any ideas why it does this? Is my SD card going bad maybe?
-------------------------------------
Oh I forgot to mention I am running cm 5.0.7.1
---------------------------------
I don't know if that's the cause, but it did the exact same thing to me today too. Also running 5.0.7.1.
I was reading a book using Aldiko. I wasn't touching anything at the time (I was in the middle of a page) and the phone just reset.
Except that when it reset, it didn't fully reboot.
It didn't give that little vibrate pulse and show the colored X and the unlocked icon, it just started into the boot animation.
It got to the lock screen, but even before I could unlock it, it started over.
After I pulled the battery, it was fine.
Last few days i have been having these same boots, not going as far as the X+padlock screen, and continuous reboots until i do a battery pull, i am running froyo+cyanogens kernel.
I find i always have the headphones in when this happens.
liam.lah said:
I find i always have the headphones in when this happens.
Click to expand...
Click to collapse
No headphones here. It has only happened to me while reading an ebook with Aldiko, but I'm guessing that's just because it's a long period of phone activity.
It's probably less likely to do it when it's sitting locked and idle.
it happened to me also for the first time yesterday, just as you describe...phone reboots, gets to lock screen, and reboots again.
i had pandora on pause for a while...and thought that might have been the cause...since pulling the battery and rebooting i have not had the issue repeat itself...yet.
I have experienced three similar strange reboots since upgrading to Froyo. All three occurred while the phone was charging and i was using an app. Once the reboot loop begins the green charge light on the phone never goes away until i pull the battery.
Hello everyone. I have had my Droid Bionic since day one and I have never had an issue with it. It has been wonderful.
Until today. I am on the stock OS. I had a Live Wallpaper that showed a little Android figure that melts based on the percentage of my battery. I went into my Gallery and clicked on "Set As Wallpaper" on an image I took with my camera on the phone.
At the bottom of the phone, a small popup showed up that said "COMPLETED". When I went to the home screen, there was no wallpaper in the background. It was just black, though the icons were still there and it was responsive. I thought maybe the image was corrupt, so I went and tried another image.
This caused the phone to reboot. When it rebooted, there was a notification bar, the time, the lock screen, and a thing that said No Signal. I tried to unlock it, but the phone was unresponsive.
Then I got a text message, even though I had no signal. The notification light was blinking. I could not unlock the phone. I hit the sleep button, and it went to sleep. I tried hitting it again, and it would not wake up.
I tried pulling the battery and putting it back in, and now it won't properly boot. Right when it boots, it goes to sleep (the little shutdown animation). I texted myself from my sister's phone and the notification light blinks, the phone vibrates, and the screen turns on and shows I have a text on the notification bar. The screen and the buttons are completely unresponsive, however.
I tried calling myself from my home line and I could pick up the call just fine and end the call. I could not, however, go back to the home screen while on the call. The capacitive buttons on the bottom were completely unresponsive. When I hung up the call (by touch), it went to a completely black screen with the notification bar showing that I had some text messages and the time and my service, etc.
I have rebooted the phone five times now by removing the battery and it keeps going to this. I have never rooted the phone (I wouldn't even know how to) and I am concerned because of all of the information that I have saved on the phone.
Yes I have tried removing the SD card. Didn't help.
Any suggestions? :/
UPDATE: Now the phone doesn't even boot, it gets stuck at the Red Eye spinning logo. It vibrates twice and the notification light begins blinking, meaning it is letting me know that I have received text messages... but it isn't actually booting to the Android home screen. Really strange...
You should fxz back to stock
It will wipe your application data but not you're sdcard info or internal storage
Sent from my DROID BIONIC using xda premium
Hard reset using all three external buttons
Try doing a hard reset - it's one of those things they only tell you about at the Verizon store when you're stuck:
Once you have the phone on and at least responsive, press and hold BOTH volume keys, then hold the power button down for 10 seconds (it's really about 6, but 10 will do it for sure). This procedure can also be done to force a reboot when you load a gnarly application that sux and locks your phone up - without having to disassemble everything and pull the battery.
Hopefully with any luck, you're phone will do a back-flip and come up!
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
apollohay said:
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
Click to expand...
Click to collapse
it was at ten percent brightness and the screen was completely unresponsive as far as i could tell. doing the power + volume up press made it reboot and return to normal.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
kingwaffle said:
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
Click to expand...
Click to collapse
exactly the same here. felt like i had dropped a baby on it's head haha. i wish i knew a way to figure out what caused it.
My wife and I have been having the same issue, and I'm surprised that there's not more reports of this behavior The worst part is that I use my phone as an alarm, and the alarm won't go off if this happens in the night.
It has happened to me 3 times now, and 2 times in one day for my wife. Holding down the power button for ~20 seconds will cause the reboot, which is the good news. This morning after holding down the power button I noticed the notification light flashing red.
The phone appears to be still on, because if it happens overnight I will still see the white notification light flashing even though the screen won't turn on.
I had this problem on faux123 kernel on the second day after I got my Nexus 4.
Doesn't encounter it on franco.Kernel...
Sleep of death brozillas! Happens to all android phones. Happened to all my phones listed in my signature. You can reboot the device and you should be good. For the dude that's missing his alarm you should do a factory reset if you are stock or if you have root do not set your min cpu values to less than 3xx MHz.
Sent from my Nexus 4 using xda app-developers app
Same thing happened to me on my N4. Did a hard reboot and it came back on. Has happened at least twice since then, usually after being plugged in.
Sent from my Nexus 10 using XDA Premium HD app
Change chargers, cables. Make sure the charger is 5v 1.2a. Factory reset to stock.
If all that fails, RMA if you can.
Sent from my Nexus 4 using xda
I observed the same issue (going to standby, then cannot switch on within an hour) with my [just bought] Nexus 4 (latest 4.2.2 firmware OTA updated, nothing special in setup, second day of use).
Certainly must be difficult to say if it's hardware of software (that is, JB/drivers, since I cannot see how such issue can be caused by any virtual machine application) and when/if the latter will be fixed. I have another such great device already -- ASUS TF700 transformer, with similar "everything works, just reboots occasionally", which I think is enough for me
As with the ASUS Transformer case, I have trouble understanding: if it's the issue with all devices/firmware, although not too frequent -- then why everybody does not complain/return the units massively: the phone is pretty unusable if it cannot be relied upon. If it's just some isolated cases with particular units -- then what happened to QA/testing at LG...
So I guess I am going to return it while I can.
Too bad, good model otherwise, will have to see other phones or wait/observe.
My point is, I understand: fairly new device, can have quite a few faults to be fixed later -- now everybody seem to work that way, for better or worse.
It can have more or less beautiful (or ugly) designs, more or less features, larger or smaller batteries/working time; it can have problems with data connectivity, it can have better or worse browser (or the lack thereof completely). I'm fine with the lack of text reflow in Chrome although that was surprising.
One thing a phone/communicator/PDA absolutely cannot do, provided its battery is not empty, is going into "sleep of death"-like states -- it just cannot serve its purpose then, I cannot see how people sell it at all...
I have had a similar issue before, but i have experienced it when my phone has been through one of 2 sets of scenarios.
1 - It gets really warm and the screen becomes unresponsive, dead if you will. The hard reboot fixes this.
2 - When the signal to my phone is sporadic. An example of this would be my recent trip to London. I was on the underground quite a lot, and I'd lose signal quite often whilst travelling. On a couple of occasions i had to reboot my phone the hard way to get it going again.
Hope this helps?
In my case the device was lying near me on the sofa, the time between its going to standby and my attempt to switch it on was something within 1 hour. Nothing especially intensive had been done before.
BTW, while the phone was in that state, trying to call it resulted in long tones, i.e., apparently the radio/cell was online.
Hope this will help somebody, I returned mine.
Good evening. First post but long time lurker. My N4 is unrooted and on 4.2.2. I'm troubled with this as well especially so when the alarm doesn't ring in the morning after it's crashed overnight and I'm late for work!
Not sure if this is relevant though. I don't listen to music frequently on my N4 but the 3 times it had crashed overnight I had been listening to music before going to bed. Twice using Google music being streamed via my home wifi and once using poweramp with music on internal memory. I remember on 2 occasions the phone feeling rather hot as I was plugging the charger in as I was about to turn in.
I suspect there's a process that's causing the the phone to overload/ overheat and then switch off as a result. Because it's plugged in, it'll just continue to charge overnight and present you with a 100% battery in the morning once you've got it to reset again.
I have also found that doing a soft reset before going to bed prevents this from happening.
Just my observations.
Hi all, I got my Nexus 4 a week ago to replace a broken HTC One X (The cost of repairs was almost equal to the cost of a new Nexus 4). Since I got it, SoD happened twice, both times when I left it to charge overnight. The weird thing is that I have this LED application that blinks the notification light when charging with screen off. When I unplugged the phone, the LED was still blinking as if charging, so the phone is definitely not dead. I will try to set it to day-dream while charging and see if it helps. If it does, it might be considered a way of Google encouraging developers (like myself) to create more daydream apps .
Good morning from beyond the pond,
had the same thing happening as described in the first post solution (pressing POWER+VOL UP) helped to reboot my device.
Only thing that was showing was the led, flashing a blueish white light.
Now runs again on rasbeanjelly. Thanks to OP.
EDIT: since this happened the first time, I thought about what I had altered in my setup.
Only thing that was new was "Greenify". Maybe it sent the APEX launcher into standby?!
Having same problem on my 1 week older n4, my friend having the same problem . only thing in commune we have is the WHATSAPP app that once the phone restart it give a notification that the phone date is wrong,once I look at the date settings yes it is wrong, it says 1970 ,so I have to reset it. It does it every time the problem happens ,can this be a clue???
Sent from my Nexus 7 using xda app-developers app
guinnes.s said:
it says 1970
Click to expand...
Click to collapse
UNIX equivalent of Pol Pot's year zero
I'm having similar problems.
The first time I believe it was just an issue of slight overheating. I turned off the screen but left Google Maps running & put it in my bag. It didn't actually turn off, but the screen didn't want to come on when I took it out later. I did notice it was hot, and after it cooled for a couple mins, it worked fine again. I haven't done this again, and so far, so good.
However, now, on occasion the phone won't respond to the power button. I've never had to actually do a reset - it will eventually decide to work after a couple of presses.. but when it does, it will be slow to come on. The screen will be backlit (but black) for a few seconds, then it will load and respond as normal.
Since the light comes on prior to the screen, it seems like a software rather than hardware issue to me. If the screen was damaged, I don't think it would act that way. I don't know phones, but that's my intuition. I'm going to try and remember to turn it off on occasion and see if that helps. I don't think it's been reset since the last push update.
(I'm rooted, but stock)
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
IIRC the Xperia Z1 has a hard reset button under the sim flap, it's a small red button, give it a shot.
remove sim card and sd card and try again, if it's still not responding do an update repair using SUS or PCC
BTW there is a known fault with the XZU and it could also be on the Z1 as they use similar Firmware, what people have found is that the phone will start up eventually and then they go into the display setting and untick the auto backlight option and that fixes it
I also reboot my Z1in this way when it blackout.
Sent from my C6902 using xda app-developers app
Had the same issue called Sony, push hard reset button all is fine in the world. Known issue Sony is working on it
Sent from my C6903 using Tapatalk 4
Managed to hard reset using power and up volume .
Put it on charge overnight but it doesn't see,m to have taken any charge at all....just trying again using diff PSU and cables but it doesn't want to charge. It recognises that I've out a cable in as I played with the smart connect setting. When it is off completely I get a red light (presumably meaning its charging ) but not in android
Any ideas?
Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)
Sometimes phones have issues. I got one once that had no speakers or Mic inside... it happens lol
Try to go exchange it, and see if the next device gives you issues.. if not then you're good, if it does pick a different phone..
Do it soon though, most carriers only have a 14 day exchange period, and then after that will charge you all sorts of fees and try to fix your phone rather than just giving you a new one....
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
thefunkygibbon said:
Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)
Click to expand...
Click to collapse
sounds like a similar problem I had with my 64gb SD card - as I mentioned above remove all cards then start from there - a reflash of the firmware might help also
thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.
LadFromWales85 said:
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.
Click to expand...
Click to collapse
yeah i've been trying to reproduce it and failing to. very odd. maybe its something to do with the first time you use youtube and do something specific?
gunna phone o2 up tomorrow and see what they say about all my issues. seems to have been fine this last 24 hours though and in their eyes that is prob reason enough not to issue a replacement.
I've had mine since Monday and this happened to me yesterday. I was troubleshooting sending MMS with T-Mobile tech support (not a phone issue as it was happening on previous phones too) and had to restart the phone several times. I noticed upon restarting that the backlight seemed to be on but the phone was not booting up. Had to perform several hard resets (both with the red reset button as well as the power/volume up buttons) before it FINALLY rebooted and stayed on. While trying to figure this out I ran a Google search to see if others were having this problem. One solution was to make sure the backlight option is checked. I had been messing with settings the night before and must have unchecked it. Since I rechecked it I haven't had the same issue.
Hello all,
I got this phone about a month and a half ago, and since I got it I've noticed a lot of freezing and crashing (more so after the 5.1 update).
Some examples:
-I try unlocking the phone from active display and the screen goes black. The only way to get out of it is to hold the power button to restart.
-Sometimes the phone freezes on the lock screen randomly, and when I pick up the phone to look at it, the time is wrong and I can't physically unlock the phone, only turn the screen on and off, leading to me having to hold the power button down to shut off and restart.
-When on some apps, like twitter for example, the phone freezes, and I cannot do anything except turn off the screen by pressing the power button. When I try waking the phone, it stays black or sometimes theres a flash of the screen I was on before, and then it goes black again. Only thing I can do here is hold the power button down until "Power Off" shows up on the screen, and I press that to shut the phone off.
Today I cleared the cache, and since then the phone has froze once, causing me to do a hard reset. What should I try next? Any idea what the problem could be?
Thank you for the help.
I have pretty much the exact same thing going on. It started last night... I first noticed I had some charging issues where the phone wasn't charging very quickly after the battery died (after a day of heavy use). I let it sit for awhile, then it booted up, and it showed the motorola splash screen. It gets all the way to the lock screen, although I'm unable to unlock the phone. The screen goes dark. It appears to still be getting texts and the like- although this screen blackness issue makes it so I can't unlock the phone. The one thing I can do is hold down the power button and turn it off. I've tried loading fastboot and doing a factory reset, although nothing appears to happen and it boots the same way. The other thing about it is that it appears to be running hot- way hot. Any ideas? I'm running stock rom, Verizon network, just updated to 5.1 when it came out last week.