Related
Hello,
I've tried searching for an answer on this, but no sucess until now.
My Diamond 2 turns on its screen when it looses and get radio signal back. That is a good feature but the annoying thing is if I enter in a lift with the cell phone in my pocket, it will loose signal, turn screen on and the contact with my pocket will give it "crazy" commands that will mess it up or even call someone.
Is there a way (maybe via Registry Editing) to force it to never turn on the screen unless I press the power button? At least, an option to do nothing in case of signal loss?
Thank you.
Robert
I've just done a few experiements and if I lose signal and it returns, nothing happens. However, perhaps it would help you if you get into the habit of locking your phone before you press power. To do this hold the home button down for a second or so. The phone will buzz and it'll be locked.
Thank you. That's what I will do whenever I put the phone in my pocket. It is still not the best solution, even because I use my D2 to receive emails from work so I am forced to type a password to unlock it after sliding to unlock.
I know there is a Registry key to auto lock, but I prefer doing that manually as you said.
Which ROM are you using? In both original HTC English and now TOM's 2.02.1 it always turn screen on when looses and get signal back.
Thanks.
I'm using the original HTC. I've tried it again, I go to a place where I know I'll lose signal, wait until it does, then press power off. I go back into signal and nothing happens on the device. Only when I press power on does it come back on and show that I have signal. If I do it the other way, press off before I go out of signal, then the behaviour is the same (though I have to just wait and assume signal has been lost, since I can't see it!). Is it perhaps that the phone is set to light up when it receives a certain bit of data (such as a push email), which it's more prone to getting when it comes back into signal? Incidentally, it's 'lose', not 'loose'
I get similar behaviour after setting the phone to stream internet radio and then turning it off and putting in my pocket. Sometimes, after signal loss, I get it out and notice it's turned on and random things have happened due to screen contact.
Funny thing is, I've tried locking the phone too, and exactly the same thing happens. what's the point of a phone lock if it doesn't (lock)!
I've not associated it with a particular event except signal loss. But, when it's not lost the signal, I don't take it out of my pocket, so perhaps it's happening other times without me noticing.
Anybody with an idea to completely lock the phone will be my hero.
And, whilst we're on the subject of annoying traits, is there a way to get rid of the wretched WM "cannot connect with current settings" dialogue which appears after a few failed attempts to reconnect to a 3G network? I find this *really* annoying when all it takes is a few more attempts...
Hi
When the signal is lost or regained the phone is triggered to turn on, but in "unattended" mode. The phone will be on and applications will run however unattended mode is just that, and so no user input is accepted and the screen is not turned on, and the owner will have no idea the phone has switched on. After a short period of time the phone will enter sleep again. In fact many times a day the phone will be turning on in unattended mode without you knowing for one reason or another.
The problem with the phone awaking fully is going to be due to an application or feature you are using. The application will start running when the phone enters unattended mode and is for some reason raising the power state to fully on, this is due to bad programming as it isn't suppose to do this unless it has an alert and needs to show the screen and wait for a response, even then it should give the option for this to be disabled.
Incidently a lot battery problems where the battery doesn't seem to last very long can be due to applications keeping the phone running in unattended mode, so while the phone looks off the processor is still on allowing applications to run, this very quickly drains the battery.
You need to find the application causing the problem then get in touch with the author.
Regards
Phil
Thanks for that, Phil. Understanding is the first step to sorting a problem out. I wasn't aware there was an "inbetween" state.
I have searched this exact title and came up with 10 pages and I never saw anyone else with this problem. Surely I cannot be the only one.
After the Gingerbread upgrade I was getting the tethering message/force close, during that time my phone started to randomly shut off ( settle down Beavis, this isn't the same question thats been asked a thousand times ) and reboot. I lived with the tethering message problem for as long as I could but my phone became more ignorant day by day. I finally found a fix for the tethering issue and haven't had a return problem with that but now my phone either stays in standby mode ( dark screen ) and refuses to respond to the hard button to wake it up OR once on it refuses to go into standby mode and stays on until I pop the battery or I go into settings and time the screen out in 15 seconds ( often times this doesn't shut it down either ). Sometimes I can get it to come on by multiple pressing the power button ( this can't be healthy ) and the lock screen will flash momentarily just long enough for me to unlock the screen. Other times it will go to the lock screen while I'm in the middle of something.
Every day at some point while it's on and I'm using it, the power button option screen pops up ( silent mode, flight mode, power off ). When I'm done with a call I try to go into standby and it just sets there...ON.
The thought has crossed my mind that the button doesn't work or has a short but I really think it's something else ( I hope ). Can somebody help me? I am not very techie although I have updated the phone three times myself. It is unrooted and 2.3.5
Thank you in advance
I would go with the power button. It's a known issue on captivate.
mrhaley30705 said:
I would go with the power button. It's a known issue on captivate.
Click to expand...
Click to collapse
I stopped by the AT&T store the other day to check on insurance (ends up I didn't have it) and told them about my button not working properly and how the Captivate was notorious for this problem and they all said "We've never heard that". So the gadget gal is in there so she offers to take it apart and check it. She claims there isn't anything wrong with it and that it has the same amount of spring as the volume buttons. She then noticed that when she put the battery back in the phone came on automatically, I said it's not supposed to do that and she agreed but fortunate for me since I cannot turn it on. She then says I'm eligible for an upgrade and try's to sell me a new phone. I don't want a new contract.
So should I try and buy a new button and change it or could it be something else? Thank you in advance.
Are you using a case for your phone by any chance? If yes, is it too tight? Maybe the power button gets stuck because of that sometimes? Just a long shot! You stated that power menu pops up once in awhile when you're using it, is it possible that the way you grip the phone causes that? (Just trying to help and not trying to offend you btw.)
You might want to try flashing UCKK4 with bootloader(use it from the one click master collection of stock rom's) just to make sure that there is no issue with the firmware. It is not likely to fix your problem but it's good to have a clean start. At least that's what I would do to begin with.
Since you're willing to change the power button, why not do an experiment? Remove the power button and see if there is any change? If it works fine then it's the power button that's faulty else it's a hardware problem.
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)
Apologies if this is the wrong area for this or if up to date information is available, but I can't find any solutions anywhere.
My daughter has a pre-paid Virgin HTC Desire 510 that she has had for some time, but just started acting up today. Starting from off, it boots up and goes to the home screen fine. Then 35 seconds later (I've timed it several times) it shuts down. No matter what you are doing it goes black, just as if you pulled the battery. Then it boots up again automatically and continues the same cycle indefinitely until the battery is pulled.
I've been searching for the last 3 hours and have tried every remedy I've read, from checking the battery connections, wedging a small piece of paper there to force a better connection, and trying a new battery, to booting it without the sim card, without the sd card, and without both. Makes no difference, the phone is usable for 35 seconds, then power cycles. One interesting note on this though, if I try to manually shut down the phone, as soon as I press "shut down" or even "restart phone", it instantly shuts off the same as at the 35 second mark. Instant black screen with no proper shutdown sequence.
I (and she as well) have conceded to just wiping the phone entirely to attempt to fix the problem. Only that doesn't work either. I found that in order to do a factory reset, the "fast boot" option must be turned off in the power settings. Her's is not. In the 35 seconds I have to go into the menu, I can deactivate the setting, but it always hits that 35 second mark and turns off just after I do. After rebooting (either by letting the cycle occur, or pulling the battery and booting fresh) the "fast boot" section is still valid. In fact, I even went so far as to try to move icons around, change other settings, etc. to see if anything sticks after the boot cycle and nothing does. It seems the improper shut down that occurs prevents any previous changes from being saved. In turn, this prevents the phone from doing a factory reset.
Now, I've tried the factory reset several times and it always reboots with the same normal home screen, 35 second function, then power cycle. I've also tried recovery mode as well but it just stays on a black screen with a red triangle and "!" inside until battery pull.
This is about all the information I can dig up or provide without any further insight. I will say that I'm not that comfortable with my skill at attempting anything that requires downloading and transferring any kinds of files to the phone and installing them manually, as I'm not THAT savvy when it come to things like rooting phones, etc.. So if there are ANY solutions short of "rooting", "unlocking", "bootloader", etc that I just don't know much about, please let me know.
Thanks for any and all help, I will attempt any possible solutions I am able!
Hmmm....this sounds strange. The things you described could be from a bad kernel. But you haven't tried to root it yet so that rules out the bad kernel. I think that you should reinstall the whole system using an RUU. That is your best shot at this moment. If that also doesn't resolve your issue, your only option will be to root your phone and install a custom ROM. If you have any questions, don't hesitate to ask
psycho76384 said:
Apologies if this is the wrong area for this or if up to date information is available, but I can't find any solutions anywhere.
My daughter has a pre-paid Virgin HTC Desire 510 that she has had for some time, but just started acting up today. Starting from off, it boots up and goes to the home screen fine. Then 35 seconds later (I've timed it several times) it shuts down. No matter what you are doing it goes black, just as if you pulled the battery. Then it boots up again automatically and continues the same cycle indefinitely until the battery is pulled.
I've been searching for the last 3 hours and have tried every remedy I've read, from checking the battery connections, wedging a small piece of paper there to force a better connection, and trying a new battery, to booting it without the sim card, without the sd card, and without both. Makes no difference, the phone is usable for 35 seconds, then power cycles. One interesting note on this though, if I try to manually shut down the phone, as soon as I press "shut down" or even "restart phone", it instantly shuts off the same as at the 35 second mark. Instant black screen with no proper shutdown sequence.
I (and she as well) have conceded to just wiping the phone entirely to attempt to fix the problem. Only that doesn't work either. I found that in order to do a factory reset, the "fast boot" option must be turned off in the power settings. Her's is not. In the 35 seconds I have to go into the menu, I can deactivate the setting, but it always hits that 35 second mark and turns off just after I do. After rebooting (either by letting the cycle occur, or pulling the battery and booting fresh) the "fast boot" section is still valid. In fact, I even went so far as to try to move icons around, change other settings, etc. to see if anything sticks after the boot cycle and nothing does. It seems the improper shut down that occurs prevents any previous changes from being saved. In turn, this prevents the phone from doing a factory reset.
Now, I've tried the factory reset several times and it always reboots with the same normal home screen, 35 second function, then power cycle. I've also tried recovery mode as well but it just stays on a black screen with a red triangle and "!" inside until battery pull.
This is about all the information I can dig up or provide without any further insight. I will say that I'm not that comfortable with my skill at attempting anything that requires downloading and transferring any kinds of files to the phone and installing them manually, as I'm not THAT savvy when it come to things like rooting phones, etc.. So if there are ANY solutions short of "rooting", "unlocking", "bootloader", etc that I just don't know much about, please let me know.
Thanks for any and all help, I will attempt any possible solutions I am able!
Click to expand...
Click to collapse
Has she done anything to the phones files? (deleting stuff you shouldn't?).. RUU for Virgin Mobile - Run from a Windows computer. http://dl3.htc.com/application/RUU_A11_CHL_K44_DESIRE_SENSE60_Sprint_WWE_VM_1.49.652.3_Radio_1.47.40.0224_NV_SPCS_1.08_003_release_448617_signed_2.exe
Thanks for the responses. It seems like fixing this phone would be more trouble than it's worth for me, as it wasn't an expensive phone and I have no experience rooting phones, lol! I think she has money saved up and wants a new one anyways. Thanks for taking the time help out!
S21 Ultra, US Factory Unlocked model straight from Samsung. I've had it for a month.
I was in the middle of using it and the screen suddenly went black. It didn’t do any screen off animation or power off animation, it just suddenly turned black.
I know the phone still works because if I hold pwr+vol down I can feel the vibrations as it reboots. I can also use *./adb devices* and it lists the device as connected. It also automatically opens android file transfer when I plug it into my macbook. All these things suggest that the underlying phone works fine.
It’s just that the screen won’t turn on.
What can I do, short of sending it to samsung for a warranty claim?
So I switched to my backup phone, left to take care of some business, and now the s21u is working.............
I'm not sure I can trust it any more. But also, WTF happened?
That's very peculiar... Especially given that you force restarted it with PWB+VOL-UP. I would have expected it to turn the screen on upon restarting.
Maybe back up all your stuff, wipe it and take it to Samsung and see what they would say? Maybe they would find some issue and replace it..
This has happened to me twice since having it since 1/28. Both times I was listening to music. Music stops. Screen goes black....eventually comes back after pressing power button and rebooting. It's almost like Blue Screen of Death behavior
whitehawk66 said:
This has happened to me twice since having it since 1/28. Both times I was listening to music. Music stops. Screen goes black....eventually comes back after pressing power button and rebooting. It's almost like Blue Screen of Death behavior
Click to expand...
Click to collapse
Is your device also a US model? I mean SD888?
This happened to my S10 plus U1 befoce, suddenly blackout (everything still work except screen display) although i used hard restart. Some hours later it become normally. I'm still using it beside S21U U1.
enigmaamit said:
Is your device also a US model? I mean SD888?
Click to expand...
Click to collapse
Model SM-G998U Verizon
i had this issue too in the past with other galaxies - i believe is then it was due to the audio jack - but now it doesnt have one so IDK
finshan said:
S21 Ultra, US Factory Unlocked model straight from Samsung. I've had it for a month.
I was in the middle of using it and the screen suddenly went black. It didn’t do any screen off animation or power off animation, it just suddenly turned black.
I know the phone still works because if I hold pwr+vol down I can feel the vibrations as it reboots. I can also use *./adb devices* and it lists the device as connected. It also automatically opens android file transfer when I plug it into my macbook. All these things suggest that the underlying phone works fine.
It’s just that the screen won’t turn on.
What can I do, short of sending it to samsung for a warranty claim?
Click to expand...
Click to collapse
what's your software version? have you submitted an error report via samsung members app?
I had this same issue on my old S5 where my screen would sometimes go black and still work. As a workaround, I used 'scrcpy' an open-source tool available on Github. I could mirror my phone screen on a PC and control it.