Tonight my G1 displayed some very odd behavior. It was running normally and I pressed the power button to make it sleep and I set it aside. About half an hour later I picked it up and tried to turn it on by pressing menu. The phone gave no response other than lighting up the five buttons on the bottom. I tried sliding the keyboard out and the keyboard lit up as well, but the display remained black. Plugging it in via USB to my computer did absolutely nothing (no sounds, no notification light, etc.), and I got the same result when I plugged it into the charger. I finally decided to take the battery out in order to turn the phone off, and then put it back in and pressed the power button. The phone booted up normally, and now everything seems to be working in proper order. I am slightly concerned, however, as I have never had this behavior in the year that I have owned my G1. I am running Cyanogen 4.1.999 with the Hard SPL boot loader. I am unsure whether this behavior has anything to do with the mod and I am wondering if anyone else has experienced anything similar. I do realize that if my phone is bricked it is my fault, and I want to determine if this was simply a freak accident or if I need to do something differently with the phone.
first of all if your phone was bricked you wouldn't be able to use it. as for your problem it doesnt sound too serious so if i were you i wouldn't worry about it. but if it does happen again reflash your phone and if it happens after that, pitch it to cyanogen to see if there is a problem with the rom.
I do realize that it isn't bricked now, but I am worried that this behavior could mean that I am pushing the phone too hard. I am mostly curious as to whether or not anyone else has experienced similar behavior from their G1.
Turn off compatibility mode in spare parts.
don't worry this is a common problen It happens to me all the time any hero I flash plays nice for about a day. and then boom no problems with cyan!
I had the same problem, but unfortunately my G1 is still not working properly.
In the morning, turning off the alarm I left the phone for 5 minutes. An attempt to turn it on did not work: there was no reaction on display, although the buttons were lighting up. I restarted phone taking the battery out and now I have following:
- keyboard fully closed: no reaction/black display, buttons are lighted up
- keyboard open: I can do everything: change ROM/make call/write messages/Internet/GPS/... - everything what is possible to do with rooted G1
- keyboard partially open (visible only lowest row with such buttons as ALT, SHIFT, SPACE): similar to 'open' but with changed orientation
Can anyone help/advise? Did almost everything: ROM changed, full wipe, recovery
These are rare issues I have but I just thought I'd pose the question and see if anyone has any fixes. I have workarounds but still a nuissance and could be an indicator of a deeper problem (perhaps).
Back Button Looping
Sometimes when I hit the back button i begin looping and never get to the homescreen. It usually loops Go SMS --> Go SMS (again) --> Widget Locker in edit mode) then back to GoSMS. If i hit the home button then it brings me back to LauncherPro but does this mean the Launcher crashed? Why does it do this same sequence every time? (It has happened when leaving Plume, Camera, Titanium Backup...basically random apps, always does the same loop sequence when hitting the back button). Anyone else see this issue?
SOD
I had this issue on my TP2 and no one found a definitive solution. Random people experienced it no matter what, some saw it stop, some never saw it at all. Well it seems to have plagued my D3 in a much rarer form. After owning the phone for a few months it has only happened 3 times, and I have to battery pull for things to come back to normal. However the other day it happened while on a phone call...when i moved the phone from my ear the screen wouldnt come back on no matter what. I waited for the call lost tone and still the power button had no effect. Of course i still had the notification LED for an unread SMS which was more taunting me at this point, so again battery pull.
Everything I read dealt with Underclocking or Undervolting but I haven't installed any apps for this. Does LibertyROM or MonsterROM include any of that in their scripts? Are there any other causes out there?
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!
Hi Guys,
I have a frustrating situation whereby my Galaxy Note powers on but the screen appears to be in permanent sleep mode - I get nothing but black on the screen.
You can here the Samsung chime as the phone powers up, I can adjust the volume button and hear audible tones. I can also call the mobile from another phone so the underlying phone/OS is working fine.
I can also connect the device via Kies USB and copy images/music with no issues.
I have tried removing the battery and replacing, I have also tried giving the device a full charge however I still get nothing on the screen.
Does anyone know if it's possible to perform some kind of hardware reset to get the screen to power back on? If not I guess i'll need to return the unit
p.s. Stock Galaxy Note
Thanks v much
Jeremy
Same problem for me , i have test many ROM and kernel but i still get the black screen. it's generally when i haven't use my phone during a couple hours.
Same issue here. The screen remains black and not responsive to front button or power button. I still am able to hear notifications (e.g. calendar reminders, plug in power, etc.).
Long press of power button to reboot is the only solution I have found in order to clear.
First occurrence yesterday after owning note for 1 month.
Second occurrence today.
Stock device. No root. KL7.
No newly installed apps prior to first occurrence. I will cross-check to see if any apps updated yesterday.
I have also disabled Green Power.
guys i have been owning note since past 45 days
and suddenly i faced the same problem today
when phone is in sleep and i receive a notification and press the home button
to wake the phone
i see only a black screen with a minute pink dot at top right
and the phone wont respond
however pressing the power button it brings the menu to switch and etc
so i can select power off and then again switch on the phone
guys this is frustrating
please help
Hi all.
My note was replaced yesterday.screen now turns on fine however I'm greeted with a lively green hue and banding! Ha
Sent from my GT-N7000 using XDA App
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)