Xiaomi.eu 5.9.18 dev, but happened on 5.9.11, too. I don't know about earlier releases.
This happens in the morning, after not using phone for a longer period of time (6 or more hours, ie during the night). So when my alarm goes off, I won't be able to dismiss it. In these cases, I have to hold the power button long enough for the phone to turn off and then power it on again.
Anyone else with the same problem?
Sent from my Redmi Note 2
Did you install the ROm with wipe? Have the same and no problems
Sent from my Redmi Note 2 using Tapatalk
Yes, I did wipe everything. Might be some application that I have installed, but I have no idea which one could cause it and why. I'll have to look up on how to take a logcat from my PC, it seems.
Sent from my Redmi Note 2
I had the problem up to and including 5.9.11, but not since .18 (sorry, I'm also using the xiaomi.EU developer from branch). I did a dirty flash over .11.
Yes, I had the same problem on .18, clean installation.
The alarm was ringing this morning, but display was off and I could not turn it on.
I was too sleepy to use adb logcat.
Flash over TWRP or MIUI Recovery?
Gesendet von meinem Redmi Note 2 mit Tapatalk
And today it happened again when I woke up. Screen didn't light up, buttons didn't light up, when I plugged the phone in the PC the notification LED didn't light up. I couldn't take a logcat because the adb didn't see the phone at all.
Sent from my Redmi Note 2
I have the same issue on 5.9.24 It seems to happen after it has been left idle for a long period of time.
Yes, exactly that. It's like some kind of a sleep of death.
Sent from my Redmi Note 2
sunbriel said:
Yes, exactly that. It's like some kind of a sleep of death.
Sent from my Redmi Note 2
Click to expand...
Click to collapse
Have you found a fix for this issue?
5.10.15 Beta, same issue. Very frustrating. Can make a call to phone from another, hear ringtone, but no matter - screen is black. New phone, couple days of using
Update: install 5.10.22 update weekly from http ://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/ , i'll try it for next day and share result.
5.10.22
5.10.22 weekly beta - three days without "sleep of death" :fingers-crossed: , additionaly battery life improved
Yeah, same here. Looks promising.
Sent from my X98 Air II (HG9N)
Related
Is it normal for the notification light to barely work? Most of the time it barely works, but once in a while it comes on. Same with using light flow... Same condition. I am stock, rooted, Trinity kernel, nothing else. Anyone have a perfectly working light? I've tried factory reset, re flashing, etc. I am hoping this isn't a hardware problem but I think I would take a good screen ice a good notification light.
Sent from my Nexus 10 using xda premium
Mine hasn't worked since I got it last week. Reading around the forum it would appear that it is not uncommon. I think it is a bug within the OS, some folks have had luck forcing it on using some app in the Play Store, while others have not been so well off.
Some people have had success getting the notification light to work by rebooting when charging. This worked for me but I know it hasn't worked for everyone.
Problem must be in Google software. Mine too was the like described above while stock. I just installed AOKP & the rom has a led-light settings control. In it you can set colors, blink time & rate, etc. Works fine for whatever you have set it for.
Sent from my Nexus 10 using Tapatalk 2
hefferman said:
Some people have had success getting the notification light to work by rebooting when charging. This worked for me but I know it hasn't worked for everyone.
Click to expand...
Click to collapse
I've had the same issue with mine. If I boot while plugged in the light works.
Sent from my GT-I9300 using xda premium
mine seems to be working just fine
It's really weird that some people on stock are having problems with the notification lights... I'm assuming you have the settings for pulse notification on... and also that you know that on stock, the LED lights up only when the screen is off...
That said, I've had no problems with the LED notifications with custom ROM (my AOSP+, AOKP, CM10.1 & Evervolv)... haven't use PA, so I can't comment there!!
Only saw this while on stock. No issues with CM10.1
Sent from my Nexus 10 using Tapatalk HD
craigacgomez said:
It's really weird that some people on stock are having problems with the notification lights... I'm assuming you have the settings for pulse notification on... and also that you know that on stock, the LED lights up only when the screen is off...
That said, I've had no problems with the LED notifications with custom ROM (my AOSP+, AOKP, CM10.1 & Evervolv)... haven't use PA, so I can't comment there!!
Click to expand...
Click to collapse
I've gone through three units for various issues. The first two had a perfectly working LED, the one I kept only works when booted while plugged in. So it's random and not a user issue at all.
Sent from my GT-I9300 using xda premium
If it isn't user related then is it faulty hardware or Google software?
Sent from my Nexus 10 using xda premium
Wait a minute. This thing has a notification light? I received mine yesterday and it hasn't worked yet. I charge it and nothing whether it's on or off. Can I turn it on?
Edit: WTF!!!! Just to make sure I plugged it in while the screen was on and nothing. I will give this tablet some credit on the the quality and awesome hardware it has but just from having it since yesterday I'm getting really pissed at the lagging in the browser and gaming. I know I can install the aokp browser and that will fix one issue but to fix the other I'm going to have to install an overclockable kernel to boost things to see if it helps. Then from what I've read, once you do that you might have overheating issues!!!! Geese!!!
Sent from my Nexus 10 using xda premium
The notification light works once you restart the tablet with the charger plugged in
Just throw lightflow on it and be done with it. Mine wasnt working either, but put lightflow on it and it works great now.
Nine kinda does it's own thing. We have an understanding.
Sent from my Nexus 4
All of the units I've had so far have had a working notification light no matter how I've turned it on. If yours only randomly blinks from time to time, RMA it.
wireroid said:
All of the units I've had so far have had a working notification light no matter how I've turned it on. If yours only randomly blinks from time to time, RMA it.
Click to expand...
Click to collapse
Easier said than done. The replacement may have light bleed or dust under the screen. The three replacements after that might have issues too.
Sent from my GT-I9300 using xda premium
Once I switched roms it was fine. It's all in the stock ROM. Cm, pa, etc all have good notification light operation.
Sent from my Nexus 10 using xda premium
Guys don't get me wrong. I love this damn thing. The screen is awesome and I installed ocean browser and disabled chrome and it Friggin FLIES in internet browsing. Was getting very frustrated yesterday though until I installed the new browser. One problem solved and only one more to go with stopping the lag in gaming. I know the hardware can handle it but I guess it's down to the thermal throttling from what I understand. If we can fix that and keep it from overheating this thing would be unstoppable.
Edit: the notification light thing just irritates me a little having spent over 500 on this thing and it everything not working out of the box. I know I could fix it with light flow but I shouldn't have to do that.
Sent from my Nexus 10 using xda premium
Never had a problem with mine? It always seems to work..
Hi,
I have had my nexus 10 for about a month and it's been fine since yesterday I was browsing on Chrome and it froze I couldn't do anything to get back so I locked the screen and it wouldn't come back on. I held some buttons down for a while and the logo came on and all working. I just left it on charge today and I couldn't get it to come back on again, held the power button for 10 seconds and it booted up like it was shut down. Why is this doing this has anyone heard anything similar?
Mine did that once to me yesterday but I was trying to download an apk from a shared drop box. I just chalked it up to maybe I shouldn't be doing that
Sent from my Nexus 10 using Tapatalk HD
Chrome is prone to freezing/crashing. It's rather annoying. On a positive note, the first time it happened to me I was able to figure out that if you hold down the power button for 8-10 seconds it will reboot the tablet.
There is a large thread for this....
http://forum.xda-developers.com/showthread.php?t=1998496
My N10 Keeps freezing and resetting
Sent from my Nexus 10 using Tapatalk 2
Mine also does this ... Google will fix this in time. And being it's a Nexus, you will have the update immediately. This happens to me all the time. . mostly in Chrome, but also in other stuff too...
Sent from my Galaxy Nexus using xda premium
During a call my screen turns off like normal but just recently when it turns off, I can't turn it back on even when pressing the power or home button. There are rare occasions where even when I'm not on the phone, I can't turn the screen on.. It always results in a battery pull then it works fine again. My phone was normal and working perfectly and I haven't done any mods.. Kinda weird, anyone with input on this?
I'm rooted running version 2 Jbomb, 2.3 beastmode kernel, mj4. Could it maybe be these apps that cause this, lux, gravity screen, light flow.. Those are the 3 main apps that are always running.
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
During a call my screen turns off like normal but just recently when it turns off, I can't turn it back on even when pressing the power or home button. There are rare occasions where even when I'm not on the phone, I can't turn the screen on.. It always results in a battery pull then it works fine again. My phone was normal and working perfectly and I haven't done any mods.. Kinda weird, anyone with input on this?
I'm rooted running version 2 Jbomb, 2.3 beastmode kernel, mj4. Could it maybe be these apps that cause this, lux, gravity screen, light flow.. Those are the 3 main apps that are always running.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like you may have some gremlins. I would do a clean install of your ROM and install those 3 apps 1 at a time checking for the problem to repeat. Joshes ROMs are typically very clean. Could be the Beastmode kernel also.
MobDad said:
Sounds like you may have some gremlins. I would do a clean install of your ROM and install those 3 apps 1 at a time checking for the problem to repeat. Joshes ROMs are typically very clean. Could be the Beastmode kernel also.
Click to expand...
Click to collapse
I'm currently trying the lean kernel.. So far it hasn't happened yet.. Hope it stays this way
Sent from my SM-N900P using XDA Premium 4 mobile app
Nope. Most likely dirt in your proximity sensor. Try blowing real hard in the ear piece or use one if those air cans. Mine does the same and it sounds like a lot of people have the same issue
Sent from my SM-N900P using XDA Premium 4 mobile app
I can guarantee it's. Gravity Screen. I use both Lux and Gravity Screen and I'm on a Nexus 4. Google brought me here. I was hoping I'd find something in the gravity screen thread but search isn't picking anyone talking about it.
fwiw I only use it for the Keep Screen On by motion so any the other features are unchecked.
I also use an app called screebl which is more reliable and has been around much longer but I flip between the two.
Screebl also got completely rewritten recently so I'm thinking it's probably the more reliable of the two since it's been around longer.
Aside from that I'm thinking it might be the Running During Call checkbox since it's the only other checkbox checked.
I'd disabled the other settings by moving the sliders to zero (per the developer) and unchecking everything but the 2 checkboxes for keeping screen on by motion-left its slider at 50.
...so either uncheck that ringer checkbox. If that doesn't work it's a bug with the app.
It's inherent to almost any Samsung phone. My SII did it. My S4 did it. My Note 3 does it.
It has to do with the proximity sensor changing too quickly.
Mansevolver said:
It's inherent to almost any Samsung phone. My SII did it. My S4 did it. My Note 3 does it.
It has to do with the proximity sensor changing too quickly.
Click to expand...
Click to collapse
Sometimes it cuts both ways, with the rare occasion of the screen not waking up when a call comes in. If you're running deep sleep app, sometimes that can be the culprit. I still use it, though.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Hi folks, Haven't been here since my HTC tilt days. Wife dropped s3 in toilet and didn't take out battery right away. I took it apart about 10 hours later. Started with screen flicker. Dried it again over night and used hair dryer. I've used the on board diagnostic and all works fine except the dimmer test. Colors come up fine but when I tap to dim it dims and starts to flicker, goes black, flickers back, sometimes stays black or reboots. I've done a factory reset. I haven't seen any general screen flicker since. When it goes into sleep/screen saving mode it must go black for about 15 seconds before it is able to wake it up again.
Anyone know if this is motherboard, screen or software issue?
Thanks
Obviously it's a hardware issue dude. Send it to a repair shop because it may needs a new thing.
Enviado do meu GT-I9300 através de Tapatalk
eskorpiao112 said:
Obviously it's a hardware issue dude. Send it to a repair shop because it may needs a new thing.
Enviado do meu GT-I9300 através de Tapatalk
Click to expand...
Click to collapse
Thanks. figured I can bypass the problem if I don't let it dim. Set it to sleep only after 10 min. As long as you manually set it to sleep mode with the power button all seems good.
doclees said:
Thanks. figured I can bypass the problem if I don't let it dim. Set it to sleep only after 10 min. As long as you manually set it to sleep mode with the power button all seems good.
Click to expand...
Click to collapse
Okay dude.
So it seems that this bypass doesn't hold up. So I used my s3 screen on the wife's motherboard- no problems. Then I used her screen on my motherboard- no problems. Put hers all together - problems start again. Any ideas on that?
update
So to follow up on this. I had to use my wife's water exposed S3 motherboard on my S3. All worked well. I must assume that the wife's screen is bad. I also noticed that this phone drains the battery 2-3 x as fast as it normally would. Anyone have a screen problem do this or is this probable of a screen dysfunction.
Since yesterday I have no screen, it's in a state of black. I havd sound, but can't navigate anywhere? Tried to reset , nothing. If the screen lights up, I have a small brown band across the top, and the rest white? Sometimes flashes? Anybody elsdd have the same or can suggest? Thanks.
Sounds like it needs some samsung tlc. Send it back.
I recently sent my note 4 back due to a bad firmware flash and they sent me a new phone back with a few days. Good service.
Sent from my SM-T320 using Tapatalk
Mine did this to me yesterday. I held the home button for like 30 seconds and it rebooted and now works again.
gingerdude said:
Sounds like it needs some samsung tlc. Send it back.
I recently sent my note 4 back due to a bad firmware flash and they sent me a new phone back with a few days. Good service.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Looks like the option I have to take. No screen makes no watch! Have all the sound and vibration..
dnkeyhnter said:
Mine did this to me yesterday. I held the home button for like 30 seconds and it rebooted and now works again.
Click to expand...
Click to collapse
Thanks for the tip, but tried everything. Reboot, reinstalled gear, but still no change to screen. Only option is to wait for battery to drain and see if any change after charge, otherwise, return is the only answer. Unfortunately...
Screen fail
I had a total screen fail yesterday with no explanation. Screen went 'fuzzy' continuously and couldn't be rebooted. Battery drained, tried to recharge and still same problem. Sending it back unfortunately.