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)
Related
Greetings.
Today the power switch from my Note stopped working.
I found a website that will replace it for an original Samsung one, but I would like to ask if anyone has a better alternative here on the US.
This is the one I got:
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-power-button-repair/
Also, it is weird that now that the power button doesn't work at all, I have to take out the battery to "turn off" the phone. But when I put the battery back on, the phone turns itself on. Is that normal behavior?
Thank you in advance.
if the phone is working as usual, then instead of removing the battery to switch the phone off, use any widget from the playstore to power off the phone. this way it will power off fine. may be its because the power button is messed up.
After 14 days of having the power switch in a nonworking state, today I woke up, and lo and behold, the damn switch started the work again.
Now I can turn off the phone normally, everything is normal now.
I didn't do anything special, nothing at all.
Before, I couldn't turn off the phone even with apps like QuickOff, thats allows the phone to reboot, turn off and etc, so I had to take the battery out every time.
I have no explanation.
You got lucky there :thumbup:
Sent from my GT-N7000 using Tapatalk 2
So, I think it is just because the power button gets sticky. I was having a similar problem, except that it was working intermittently; sometimes it would turn the phone off, sometimes it would bring up the shutdown screen; and sometimes it would work like it was supposed to. Probably yours started working when whatever was making it stick got dislodged. What I did was just press the button REAALLLY hard for a while while the battery was out. It's been about 24 hours and I haven't had any problems yet, fingers crossed. Another guy in a different thread just wiggled it around. Probably if you take the whole board off you could remove the power button and reinstall it or something, though it seems no one has had to go that far yet. Anyway, if anyone else runs into this problem, just mess around with the button until it starts working again. Though, as always, if you break it, its not my fault.
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.
When going to bed tonight do these steps.
1. Put your phones brightness display on the lowest setting
2. Plug your phone in for an overnight charge, do not "turn off" your phone.
3. Wake up in the morning
4. Click the power button on your HTC ONE M7
Did the screen turn on? Are the Soft Keys the only part that lights up?
I've been able to replicate this problem over and over on 3-4 different HTC ONE M7's. For some reason the phone's display will not turn on in the morning. The only way to get it to is to either hold down the power button for a few seconds and the restart screen will pop-up which activates the screen again. Or, to do a complete restart.
Eventually the screen starts working again like normal after fiddling with it for 15-20 minutes...
I believe this is either a KitKat problem or light sensor problem or both. I do know this issue was never around before the KitKat upgrade months back.
Soul TKR said:
When going to bed tonight do these steps.
1. Put your phones brightness display on the lowest setting
2. Plug your phone in for an overnight charge, do not "turn off" your phone.
3. Wake up in the morning
4. Click the power button on your HTC ONE M7
Did the screen turn on? Are the Soft Keys the only part that lights up?
I've been able to replicate this problem over and over on 3-4 different HTC ONE M7's. For some reason the phone's display will not turn on in the morning. The only way to get it to is to either hold down the power button for a few seconds and the restart screen will pop-up which activates the screen again. Or, to do a complete restart.
Eventually the screen starts working again like normal after fiddling with it for 15-20 minutes...
I believe this is either a KitKat problem or light sensor problem or both. I do know this issue was never around before the KitKat upgrade months back.
Click to expand...
Click to collapse
I#ve never run across that problem but I know when I enable "ScreenOn" the screen stays on all night and if I just let my phone sit with screen on (because I fell asleep texting ) the screen will be off in the morning.
Soul TKR said:
When going to bed tonight do these steps.
1. Put your phones brightness display on the lowest setting
2. Plug your phone in for an overnight charge, do not "turn off" your phone.
3. Wake up in the morning
4. Click the power button on your HTC ONE M7
Did the screen turn on? Are the Soft Keys the only part that lights up?
I've been able to replicate this problem over and over on 3-4 different HTC ONE M7's. For some reason the phone's display will not turn on in the morning. The only way to get it to is to either hold down the power button for a few seconds and the restart screen will pop-up which activates the screen again. Or, to do a complete restart.
Eventually the screen starts working again like normal after fiddling with it for 15-20 minutes...
I believe this is either a KitKat problem or light sensor problem or both. I do know this issue was never around before the KitKat upgrade months back.
Click to expand...
Click to collapse
I can try it out. I'll report in the morning. ?
Sent from my HTC_0P6B using Tapatalk
Anyone?
Nobody?
Sent from my HTC6500LVW using Tapatalk
Beullar.... Beullar?
with my phone its just a 5 second lag sometimes, and i click the power button again to make sure i clicked it and it instead locks itself back. The third click however, everything works fine.
this has been happening to me for the longest its very irritating, i notice it happens whenever i fall asleep, a nap during the day or when i wake up in the morning its really annoying
Well glad to see I'm not the only one.
I have provided this thread link to HTC and reported the problem. Requested that they chime in if they have any questions.
i had that issue
Soul TKR said:
I have provided this thread link to HTC and reported the problem. Requested that they chime in if they have any questions.
Click to expand...
Click to collapse
Yes I had the same issue as the original post.Long story short I ended up sending the device back. The new one didn't suffer from this problem. This was back in October of 2013.
Same issues, it's probably light sensor:
http://forum.xda-developers.com/showpost.php?p=49918380&postcount=9
nitephlight said:
Same issues, it's probably light sensor:
http://forum.xda-developers.com/showpost.php?p=49918380&postcount=9
Click to expand...
Click to collapse
Nope. I already tried the light sensor calibration trick. It didn't work unfortunately. I ended up swapping out 4-5 HTC ONE's before it worked correctly.
yup, I tried the trick as well a few more times and could not wake the screen either. generally I'm tolerant of stuff like this because I assume it is the byproduct of repeated flashing and combo of mods.. but I I recall this happening quite early on in ownership and now it's back. (was AOSP now Sense base). sigh
I have a Note 8 that i have never dropped, had this phone since release haven't rooted. However it is running one of the early Oreo Beta builds CQLB the phone is on Sprint. This has happened once before about 2 months ago and i can almost guarantee it happened in the same fashion as the most recent time a few days ago. It seems while receiving a call i go to reach in my pocket and hit several buttons pulling it out (because of the bulky case) then my screen goes completely black.
(This is where it starts to sound like the normal black screen issue that there are a thousand YouTube videos for)
The phone still makes noises for notifications, rings when calling and other noises like emails and low battery alarm. The screen however doesn't display anything whatsoever and has a blue led blinking.
(This is where it differs)
I've done every button combination i can think of with no avail.
-The regular restart button combination Vol Up + Power and hold for 7-10 secs,
-I've tried to boot into Recovery mode by guessing at what time the Samsung logo should be on the screen and pressing the vol button down several times
-I've tried to boot into safe mode by pressing the Bixby button, power and Vol Up and without the screen displaying anything i can of course not see if i was in Recovery or not.
The screen doesn't display a Samsung Logo, No sprint splash screen NOTHING. The last time this only lasted for about 3 hours and it suddenly came back up when being on the charger and restarted several times. This is now day 3 and after dozens of restarts nothing has worked, on or off the charger. I mentioned the Oreo build because maybe it's linked to that? i haven't had this issue on regular Nougat. ANY help is appreciated and thanks in advance
Try turning off Always on Display. It worked for me..
Actually your problem seems different, so doubt it will work
..
WizP said:
Try turning off Always on Display. It worked for me..
Actually your problem seems different, so doubt it will work
Click to expand...
Click to collapse
nope, i cant get anything to show on the screen at all
winol said:
How did you get an Oreo firmware?
Click to expand...
Click to collapse
By flashing the Oreo beta builds via Odin etc..
go back to a stable build.
bober10113 said:
go back to a stable build.
Click to expand...
Click to collapse
Kinda hard to do without anything displaying on the screen whatsoever, anyway i mailed it off yesterday for repair from Samsung. It was either that or a 2 hour drive to 12 Mile (Detroit) to bring it to the Ubreakifix store.
Unfortunately Sprint doesn't offer loner phones and can't activate any phone that is non sprint outside of some iPhones which sound a bit strange but now I'm out a phone for 9-11 days :silly:
Have you solved this issue? I have the same issue with my phone. It started happening to me even when I was on Nougat. Happens to me several times already. It goes black screen for about an hour to 3 hours then randomly get back to normal (get notification sounds, can receive call, etc). I am now on Oreo. Everything is stock. Never rooted my device as well.
Tried to bring to Samsung but all they did is 'Software Update' the device which is basically reinstalling the firmware and wipe everything. Service Center sucks and doesn't want to claim it is a defective unit.
My note 8 began experiencing this yesterday and after some frustrations and work around, I managed to pinpoint the issue.
Work around was go unlock phone and drag down taskbar, then click on systems and the system interface would open, after which I could press buttons on lower part of phone and clearscfeen to get back to homepage.
Problem was with Google. In my case I realised when I opened Google maps, the screen went black, so I went into applications and cleared the Google cache and Google maps cache. No 0roblems since.
Is it something with Snapdragon?
Recently, I've noticed that my phone's screen completely blacks out while the phone is still working. So, if you plug in your charger, it'll play that charger connect notification sound if you use the fingerprint, it'll unlock the phone but nothing comes up on the screen. It'd be completely blacked out. This has happened to to me twice and has me got worried now. No matter for how long you hold the power button, nothing happens. Right now, it seems that the phone corrects the default by itself after leaving it aside for a good 10-15 minutes. Has anyone of you faced this?
Yep, unfortunately happens, though rarely . Mentioned in few other threads.
Happened to me thrice. Yesterday was the last go. You can reboot with Vol up + power.
It's an annoying bug, I'll admit that.
For me the same, two or three times last two weeks, I think some bug in Pie, because before there was nothing like thies
Gesendet von meinem Nokia 7 plus mit Tapatalk
Have had this phone since its release date here in UK (TA-1055) and have not experienced black screen or any other bug, except the non-appearance of Pie which has still not Ben released in UK OTA.
Sent from my Nokia 7 plus using Tapatalk
Experienced it thrice. The first time I experienced it was last August (Android 8.1 Oreo), then October and today. I didn't think this was the new Android 9 Pie's fault as I experienced it when my phone was on Android 8.1 Oreo. Also one thing I noticed is that even if the screen is not showing up, the touch controls are still active. So I managed to restart it normally my phone by press hold the power for a second and feel the default location of the restart.
schetz said:
Yep, unfortunately happens, though rarely . Mentioned in few other threads.
Happened to me thrice. Yesterday was the last go. You can reboot with Vol up + power.
It's an annoying bug, I'll admit that.
Click to expand...
Click to collapse
Thanks for the help man! I was frustrated with this bug and it kinda scares me.
edwaine said:
Experienced it thrice. The first time I experienced it was last August (Android 8.1 Oreo), then October and today. I didn't think this was the new Android 9 Pie's fault as I experienced it when my phone was on Android 8.1 Oreo. Also one thing I noticed is that even if the screen is not showing up, the touch controls are still active. So I managed to restart it normally my phone by press hold the power for a second and feel the default location of the restart.
Click to expand...
Click to collapse
Mine would just not restart. Or maybe I was touching the wrong portion of the screen... Afterall, it was all blacked out
Same, holding the power button vibrates the phone and touching the screen does make it vibrate sometimes, but Vol up + power does not do anything. Screen is still black.
K.singh said:
Mine would just not restart. Or maybe I was touching the wrong portion of the screen... Afterall, it was all blacked out
Click to expand...
Click to collapse
It happened to me last month for the very first time and hopefully will never again in future!
I can't recall if I was pressing the right key combination but for several times it would just vibrate and then nothing. I had to call customer care from my secondary device to check what can be done who were pathetic to tell me to take it to the nearest service center. Then, I eventually tried the Power button + volume up and then it rebooted and went back to normal.
I was so shook with this incident, I hope it never happens to anyone. I've been using this device since 7 months now and it never happened to me when on Oreo. This device is getting more and more pathetic with each new update!
Hi,
sorry for necromancing the thread. It happened to me today too, for the first time. If anyone else stumbles upon this thread, then this is absolutely easiest solution:
1, Hold down power button until it vibrates
2, The screen is black, but the touchscreen still works. The easiest one to touch is the power off button, because it is right next to the power button So simply tap on the display right next to your power button after you feel the vibration, and you will tap the power off button. Wait a few seconds, then hold power button again to turn the phone on again.
Same happens to me. I hold down the power button until it vibrates, release, take a deep breath, tap button again and it is back.
Happened to me as well ?
Hi,
I just bought this smartphone nokia 7 plus TA-1046 4G/64G dual sim. I could parameter it and after only 2 hours of use: total black-out! I could still feel vibrating keys despite the black screen. I ve been able to force the restart by pression power button + sound level up, but the screen remained desperately black. I tried to charge it well for 1 hour, same ****. Surprisingly, I removed the sim card and the SD card and It restarted normally.
Pretty scary! Will it happen again? What was the pb? A SD card conflict? Shall I format the SD card maybe? Or buy a top quality SD card? A sim card conflict? Shall I keep the phone or send it back to the shop?
Did anyone narrow down a potential SD card cause as well for this kind of glitch?
Thanks.
Arn
Happened to me also couple of times.
One time happened just before I wanted to show off my phone to my friend. I had to keep my phone in my pocket for like 10-15 minutes, lol, I was embarrassed because I praised this phone, and praised Android One, because he was considering this phone to buy, for at the end he went with the P20 Lite.
F***you HMD
Re happened again
Just 1 hour ago my nokia 7 plus re black out again! Had to wait 1 hour to re start it. Then, it worked 5 mins and black screen again. That s enough => I ll ask for a product return and refund.
Btw: i don't have blackout problem using daily N7p for 10months...
Have you guys tried formatting the phone ? I had clearing cache issues when I set font size and screen size small. It will clear the cache very slowly and eventually it will struck. But it was solved after I tried default font size and display size. Looks like every model got its own issues.
saltgirl said:
I set font size and screen size small
Click to expand...
Click to collapse
btw:from day one i have for small font&ui set in developtions "smallest width" to 505
k3dar7 said:
btw:from day one i have for small font&ui set in developtions "smallest width" to 505
Click to expand...
Click to collapse
I used to use 600dp for the tablet UI chrome. For easy tab switching.