Database Info

[Q] [SPH-D720] Back light appears to randomly shutoff

Over this past week the back light for my Nexus S 4G appears to randomly shut off. Right now it has happened about 5 times and when I need to use it right then, preventing me from just stopping to investigate what may be causing this. The screen still comes on allowing me to quickly unlock using the pattern and then restart by holding down the power button. The one time I was able to investigate a little I was navigating into the settings menu when the screen just went blank. I pressed the power button a few times and could see the hardware buttons below lighting up as if the screen was on but that was it.
I'm currently running Slim Bean (Android 4.2.1) Beta and will be trying another rom but wanted to see if anyone else may have encountered this issue before I bring it up with that thread.

Yeah experienced this too in most 4.2 ROMs that I've tried. Some people say it's a bug with the auto- brightness settings but I don't buy it since I don't really use auto-brightness but still get the error. I'm back to 4.1.2

Glad to hear. I was becoming worried I had some hardware that was failing.
I will turn auto brightness off and see how it goes.
Thank you

So it has happened quite a bit since my last post. Even with auto-brightness turned off. I'm blaming this bug for my alarm not continuing after I snoozed it a few times. (I know they are unrelated but its just really annoying).
It happened again about ten minutes ago and I managed to output a bug report feature on 4.2.1. Not sure if it is of any use to anyone. Message me if you would like it.

Slow response after a reboot

So, say I install a new kernel, or update the rom, or just want a reboot or whatever.
Well my phone will reboot quickly, but then will seem to lag really badly when the phone is turned on.
For quite a long time (maybe 20-60 seconds, i havent counted) my power button doesn't do anything. My phone is responsive to touch, etc, but the power button won't put it to sleep.
Then about 20-60 seconds, again I haven't actually counted but it seems like a while, the phone will randomly load settings I have saved on boot from Trickster MOD and Franco's Display Control app. It is at that point that my power button is functioning again.
I'm not sure if it's these settings causing any problems, but it's weird and annoying cause I can't really do anything until the settings apply. It seems like maybe it's stalling on getting SU permissions, because once that toast message appears everything suddenly works.
Anyone ever have this issue? Running Paranoid latest, and Franco 38.
I'll keep messing with stuff to see if I can solve it myself, but just wondering if anyone else has had this issue.

I'm also experiencing a delayed response from trickstermod and franco's display app after reboot (I got used to it); but my power button is functioning well.
Sent from my Nexus 5 using Tapatalk

I actually have noticed the power button not working sometimes, usually with an xposed module that I reset. I always deleted the module and thought it was a bug. Ended up turning me away from xposed. Maybe I should look back into it again lol.
Sent from my Nexus 5 using Tapatalk

I think this delay is different for every rom/kernel. I noticed a serious delay on AICP (with a custom theme) to load widgets and to have all toast notifications at boot and this delay is significantly on SlimKat (power button is immediately functional after entering my PIN code). I've kept the same Xposed modules.

When buttons (and volume knob) stop working

All the buttons, including the volume knob stop working.
It has happened several times on my android 5.1.1/mtcd/joying unit.
When it happens the boot process is strange. It spends a while displaying the car logo, then it displays the desktop for a second or so and then it displays the car logo again. It sort of looks like it boots twice.
Wiping the dalvik cache does not fix the problem. I have to factory reset or wipe everything from recovery to get the buttons working again.
I am currently using malaysk rom for MTCD units but I had exactly the same issue on the stock rom.
I think the problem is related to autostarting apps on reboot.
Today it happened after I installed the Sygic speed camera/traffic alert app. Everything worked fine for a while, until I chose to auto start it (from the settings menu inside the Sygic app), rebooted, and the buttons no longer worked.
To check if the autostart option really caused the problem I installed the app again, chose to auto start from the settings inside the app, and the same thing happened. Buttons no longer worked.
The issue is not specific to Sygic, as I have had the same issue with other apps.
Now I use tasker to autostart the app. It has survived a few reboots. I hope it lasts.
Does anyone understand the boot process on these units well enough to help debug it further?
It would be nice if I could fix it the next time it happens, instead of having to wipe/reinstall everything.

It seemed to be completely random for me... and it stopped happening as randomly as it started.
I posted the process I went through to get them back (reboot, reboot to recovery, reboot again, etc) but very intermittent.

I experience this whenever I reboot from the power icon in the taskbar. It seems to have started after upgrading to Malaysk's version 4. I have verified this on two Joying units. My workaround is to reboot with the reset button when I have to.

I have not had any apps autostart since the last time it happened, but the buttons stopped working again a few days later, and the "double boot" came back also. The reset button did not help.
A factory reset from the settings menu made the buttons work again.
I was using the latest joying rom and MCU. Spotify, iGo navigation (from joying) and the TomTom speed camera app were the only "extras" installed if I remember correctly.
I am about to give up on the (JY-UL135) head unit now. Unless someone has suggestions on what to do.

xdamember2 said:
I experience this whenever I reboot from the power icon in the taskbar. It seems to have started after upgrading to Malaysk's version 4. I have verified this on two Joying units. My workaround is to reboot with the reset button when I have to.
Click to expand...
Click to collapse
xdamember2, i think you are right. Power icon in the task bar is the root of evil.
Today i've had the same experience. But with the buttons, the sound had also disappeared. Pushing hardware reset button had fixed the problem.
So I suggest to remove power icon from the task bar.

This happened to me yesterday, but as well as buttons/steering wheel control, all sound output stopped working! No radio, music or navigation sounds. Tried a reboot, but in the end only a factory reset did the trick as specified previously.
Very frustrating!

This happened to me again today for the second time. While driving the screen turned to white/black static like moving artifacts and the sound cut off. After holding the power button to reset the buttons are not working. I'll update to Malaysk's Rom v5 now but looks like my apps are wiped again...

i've been on v5 for the past few days and i haven't witnessed this behavior.

Any luck with the buttons and sound stop working? It`s the same with version 6 of this ROM which i like way better then the stock ROM. I`v noticed that any other reboot except the standard one, when the HU shuts off by it self, will make buttons unusable and no sound. The first time it happen to me was when i did some changes in the "factory settings" menu that needed to reboot the device. The only way i managed to fix it was to do a factory reset. Tomorrow will try to flash the same ROM (V6) without wiping to see if this will fix it,because they don`t work again now after rebooting from the power icon . Lets hope someone finds solution for this annoying issue.

MY FIX for Volume knob not working on Android Head Unit
Hi All
I updated my generic Ford Focus PX5 android head unit, and after much swearing and reading on here, I still was unable to fix the top left volume and top right tuning rotary knobs as they had stopped responding.
Eventually i started mucking about with Factory Settings and in the "OTHER" section I looked at "Knob Mode"
Experimenting with the various settings I eventually determined that for me, "2 10K/20K ADC Ports" works. I now have fully functioning controls.
I hope this is of some help to you guys!

I had been fooling with the settings of my Android head unit and some days later realized my volume knob wasn't working. That knob was a big factor in my purchase of this unit. After fooling with a dozen or more logical sounding settings, I happened upon the setting which had to do with 'Key lights'. Here's the fix:
From 'Settings' go to 'Factory Settings' and enter code 8888. Go to 'Key Light Settings'. On 'please open the debug button lamps' press 'OK", slide the screen up and turn off 'whether to turn on the colorful lights'. Back on out and the volume should now be working. Hope this helps

Sdgz said:
I had been fooling with the settings of my Android head unit and some days later realized my volume knob wasn't working. That knob was a big factor in my purchase of this unit. After fooling with a dozen or more logical sounding settings, I happened upon the setting which had to do with 'Key lights'. Here's the fix:
From 'Settings' go to 'Factory Settings' and enter code 8888. Go to 'Key Light Settings'. On 'please open the debug button lamps' press 'OK", slide the screen up and turn off 'whether to turn on the colorful lights'. Back on out and the volume should now be working. Hope this helps
Click to expand...
Click to collapse
I recently bought a new android head unit. All are working well except the original volume knob of the car. Sometimes i must turn it 4-5 clicks for the volume to move 1 click, and other times i may turn it 10-15 clicks and the volume does not respond at all. This is very frustrating! I found a solution on youtube which says factory settings-other- and uncheck the wheel3 option, but my head unit doesn't have this option at all. I hope your solution will help me!
Update : I searched for this solution you mentioned but this option does not exist in my factory settings with 8888 code. Only car logo. I dont know what to do....

Help - My new SM-G930W8 S7 hangs on wake

Now this doesn't happen all the time every time, but usually around a notification and the screen is off, I go to hit a button to turn on the phone and it doesn't respond but the touch-keys are backlit. If Always-on Display is on, the screen is black regardless, not even showing the time or notifications. The only fix is waiting ~10 seconds for the phone to respond, which in some cases can be the difference between a missed call.
Now, seeing Always On Display off like that while it should be on made me think back to when I saw some sort of Nougat optimization setting that allowed me to select Always On Display, and as far as I remember, I did. That makes me think this process is killing AoD and it is taking that long to start back up, where the phone won't unlock until AoD (is back on and) can confirm that it's trying to wake up out of that state.
However, I don't believe this is the issue. I have turned off AoD and the issue still happened directly afterward, after a Messenger notification. This is stock firmware, however it is not factory firmware. I believe I downloaded it from Sam-Mobile, and they had the 7.0 Nougat upgrade that I would have gotten OTA with the factory firmware anyway.
Somehow I don't think it's the flashed firmware that is the problem, however please let me know if that's a possibility.
While the phone (or whatever) is hanging, I can still hold down the power button and I will feel haptic feedback as if the power menu has opened, and when the phone responds the power menu will be open, so the phone does still receive input. It just doesn't seem to act upon it or wake the screen properly. Is this perhaps merely a known Nougat bug or is it a glitch with my flashed stock firmware?
I'm sorry I don't have much more information. I do have Greenify, but I don't think that can or is set to disrupt anything that would affect the phone waking, or that would hang the OS, homescreen or whatever it is.
I haven't done other troubleshooting because I don't know what direction to attack this from, and that is why I have come here.
Help please!
Thanks in advance. :good:

UPDATE: It seems to happen directly after my screen shuts off from being on. So, if a notification wakes my phone but I don't interact with it in time and the screen goes off, when I press the power button it won't respond for ~10-15s. That's all I've really noticed... Anyone else have this problem??

BUMP.
Also, the same thing happens if I press the power button on my phone (by accident) and then go to turn it back on almost immediately - it won't respond for a while.

Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset

*Detection* said:
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
Click to expand...
Click to collapse
Won't be factory resetting unless I plan to root or something. I'll fiddle with the keep screen off setting that I do have on, and I highly doubt gestures would affect it but regardless I haven't enabled or used any. Thanks for the reply.

So the "Keep screen off" setting didn't affect anything. I turned Always On Display back on and I see the same issues. However, now sometimes I notice when I lock my screen or it shuts off, sometimes the AOD will appear and then quickly disappear, and stay in this hanging state for 10-15s. Then, if I haven't touched it during that time, the AOD will reappear. Any ideas? :/

So nobody else has this issue? This is still a problem, even if I press the power button and sometimes I'll want to turn it back on again as I just remember something to do before putting the phone away, it hangs on black for too long to be useful in that moment. The only potential solution is a factory reset?

Even if I lock the screen... If I try to turn it back on too soon, and I think it's specific timing... I have to wait 10-20 seconds. Sounds and vibrations still work.

UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.

Kilva said:
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Click to expand...
Click to collapse
This happens for me also as a point of interest.
I am hoping that O solves it, since the monthly updates have never helped.

I haven't had this happen since upgrading to Oreo a week ago, so far so good!

Question LineageOS 19 + microg for OnePlus 9: Screen goes dark every few days and I have to reboot

Basically this, every 3 or 4 days or so my OnePlus screen will go dark. It isn't *crashing*, though - it's happened when I've had headphones in listening to music and the music still plays, responds to headset controls, etc., so I think it's just the screen. Normal reboot will not work (holding the power button), although this might be because that presents a reboot menu rather than just rebooting the device. I have to do power button + volume up to reboot the device, at which point it reboots and everything is back to normal. I'm happy to gather any addition logs/data needed to debug, but I can't find anything in my crash debugging app (because it's not a crash...). Other interesting pieces of info
- I get the "Intent Verification Service stopped responding" issue every reboot
- I originally installed by wiping OOS + Android 12 and trying to install 19.1 and 19.1 recovery; this failed (same problem as here: https://forum.xda-developers.com/t/denying-ota-because-it-is-a-spl-downgrade.4463975/), so I installed 18 instead, which failed, but then wiping and going back to 19 succeeded (because the update was newer and thus no longer a "downgrade", I presume. IDK what really happened there).
- Trying to do Android Beam hard crashes the whole device; I've disabled NFC for now
Other than that the build runs swimmingly. I can live with the other stuff but the screen shutting off randomly is worrying to me - anything I can do to fix this or help you guys help me fix it?

hyve9 said:
Basically this, every 3 or 4 days or so my OnePlus screen will go dark. It isn't *crashing*, though - it's happened when I've had headphones in listening to music and the music still plays, responds to headset controls, etc., so I think it's just the screen. Normal reboot will not work (holding the power button), although this might be because that presents a reboot menu rather than just rebooting the device. I have to do power button + volume up to reboot the device, at which point it reboots and everything is back to normal. I'm happy to gather any addition logs/data needed to debug, but I can't find anything in my crash debugging app (because it's not a crash...). Other interesting pieces of info
- I get the "Intent Verification Service stopped responding" issue every reboot
- I originally installed by wiping OOS + Android 12 and trying to install 19.1 and 19.1 recovery; this failed (same problem as here: https://forum.xda-developers.com/t/denying-ota-because-it-is-a-spl-downgrade.4463975/), so I installed 18 instead, which failed, but then wiping and going back to 19 succeeded (because the update was newer and thus no longer a "downgrade", I presume. IDK what really happened there).
- Trying to do Android Beam hard crashes the whole device; I've disabled NFC for now
Other than that the build runs swimmingly. I can live with the other stuff but the screen shutting off randomly is worrying to me - anything I can do to fix this or help you guys help me fix it?
Click to expand...
Click to collapse
Go into display settings at the bottom and turn off pocket mode.

mattie_49 said:
Go into display settings at the bottom and turn off pocket mode.
Click to expand...
Click to collapse
I don't see anything that says "pocket mode", here are my settings:
Brightness
Brightness level
Adaptive Brightness
Lock Display
Lock screen
Screen timeout
Appearance
Dark theme
Font
Font Size
Display size
Icon Shape
Color
Night Light
LiveDisplay
Colors
Other display controls
Rotation Settings
Display white balance
Smooth display
Full screen apps
Screen saver
Tap to wake
Prevent accidental wake-up
Tap to sleep
Wake on plug
All the "tap to <blank>" settings are on.

hyve9 said:
I don't see anything that says "pocket mode", here are my settings:
Brightness
Brightness level
Adaptive Brightness
Lock Display
Lock screen
Screen timeout
Appearance
Dark theme
Font
Font Size
Display size
Icon Shape
Color
Night Light
LiveDisplay
Colors
Other display controls
Rotation Settings
Display white balance
Smooth display
Full screen apps
Screen saver
Tap to wake
Prevent accidental wake-up
Tap to sleep
Wake on plug
All the "tap to <blank>" settings are on.
Click to expand...
Click to collapse
Prevent accidental wake-up

mattie_49 said:
Prevent accidental wake-up
Click to expand...
Click to collapse
This setting has been turned on, I'll keep my phone running for the next few days and see if it crops up again.

hyve9 said:
This setting has been turned on, I'll keep my phone running for the next few days and see if it crops up again.
Click to expand...
Click to collapse
Ok, it's been about a week and a half, I thought this was resolved but lately the issue has cropped up again, always at inconvenient times. Any logging I can enable or other settings I can tweak?

Had the same issue when I upgraded from C.61, which I now have learned breaks some sensors like light and proximity.
I'm currently back to stock until I have some time on the weekend to experiment again with downgrading to C.47 and then installing LineageOS.

Seems to be happening more frequently as of late. Friendly reminder for those of you experiencing this to not press the power button a bunch of times to try and resolve as (at least on my phone) this calls 911 and then you have to awkwardly explain to emergency services that there is no emergency :/

mattie_49 said:
Prevent accidental wake-up
Click to expand...
Click to collapse
I'm having the same issue continously, basically every time I put my phone into my pocket, it is unable to wake...
It is responsive but it's like the proximity sensor gets messed up.
I used on the proximity sensor tester apps to prove that it is still functioning properly, which I could turn it off at this point as it's certainly causing the issue based that it only happens when I put it into my pocket.
I've tried almost every combination of those settings at this point and it's not working. Might try doing a factory reset at this point..
Edit: I've used SD Maid to clear everything, it helped a bit.
Still having black screens. Going to just downgrade back to lineage os 18 till Twrp comes out for 12