I need to use an app that scans the screen, however it doesn't work properly with changed colours in night mode (read mode).
The problem is that the night mode is turned off by default, but the screen still goes to night mode! I switched it on/off, changed everything I could including colours and the only workaround is to set time back to day (e.g. 3 PM).
On my previous phone I did not have this issue since the "orange layer" was on the top of everything. Now it seems it's "under" everything. No matter how orange the screen is/isn't, every screenshot taken by the app has the same orange colour.
Any idea how to turn it off and where the problem is? Thanks for your suggestions
SOLVED! It was probably problem bewteen MIUI and Google (Android?) default settings.
It's just two steps through debugging:
adb shell settings put secure night_display_activated 0
adb shell settings put secure night_display_auto_mode 0
The orange overlay is gone, yet I still have the night mode. Worked as a charm! Big thanks to lessthanzach
Hi Matt, I am having trouble while turning off the night mode. Even if I turn it off the night mode the screen is still in orange colour. I saw your post in XDA in a browser. It seems you have solved the problem
Could you please help me resolve the issue?
Thanks
Related
Hi all
I've done something stupid to my phone.
Been fiddling with auto-brightness settings, and now the screen won't switch on.
Got CyanogenMod 7.1 stable for the HTC Desire HD, had it loaded for close to a month(been enjoying it).
I've rebooted, pulled battery, SD card, SIM, everything. On boot the display shows the HTC logo, and the CyanogenMod BootScreen, immediately after that, I see the screen off animation, where it would normally go to homescreen. I know the phone is still on, the notification light is flashing, and via USB I can get screenshots of my lockscreen(widgetlocker).
When I click the power button a few times, intervals of ~3 seconds, the screen flashes just quick enough to see my lockscreen, but it really is a split second flash.
I've got Juice Defender Beta, I think the latest, used it for a couple weeks. Today I wanted to test the auto brightness settings it "supports"(beta feature). I noticed no changes, so I skipped over to the custom display settings for cyanogenmod, under Settings/Cyanogen .../display/Auto Brightness.
I fiddled there, as I've so done before, couldn't find the right balance , so I left my phone for a bit, it clicked the screen off, now screen is 'stuck' off.
I understand that this may be Juice Defender's doing, but since I was fiddling with cyanogen settings too, I'm posting here and to JD support, just in case. There might be a conflict.
Anyone know how I would debug this through ADB? I would really like to disable auto-brightness, that would probably eliminate Cyanogen from causing this (as the settings I changed related to Auto-Bright).
I tried this, no luck.
Otherwise, how to reset Juice Defender settings via ADB, or through a USB screenview... thing?
I've got a NANDroid backup, but its a little dusty, I've done a lot of customisation and such since, I'd prefer to avoid using it.
This is, of course, urgent. I can't use my phone at all, so any help is greatly appreciated.
EDIT: Solved it. Booted into safe mode, disabled what I changed, sorted. Still no idea what caused it, but ja, I fixed it. Android has a safe mode? Good to know...
Dear all!
I am really in despair
I notice a strange phenomenon on my Galaxy S 3 (German version).
Sometimes there occurrs a flickering of the screen. It is caused by thin greyish horizontal lines which jitter with high frequency at some parts of the screen. You should not imagine it as some blinking of the whole screen. It's only a partial jittering of thin greyish lines.
It does appear at random, I cannot force this effect to occurr. Most of the times it's subtle, but sometimes it is clearly visible.
I read in some other threads that people noticed flickering in dependence of the power saving options. This I observed as well. But I don't know why. Unfortunately, none of the other threads came to a conclusion. And the problem seems to affect only very few devices.
My S3 was sent into repair twice. Two times the touch screen was exchanged. Last time they also changed "some electrical and mechanical parts". However, the flickering still occurrs.
I now tested for a while and made the following observations:
- it's not related to 3g, wifi or mobile connections in general (occurred while switched off)
- it's not related to "automatic brightness control" (occurred with manually set brightness, 1/3)
- it's not due to the display (they changed it two times)
- it's not related to ambient light (happened both with artificial light and in darkness)
- it's not related to the setting "adjust display color"
- neon light helps to trigger it, as well as switching the screen on or manually changing the brightness
- it's not related to any one of the single settings in "energy saving mode"
- flickering "survives" switching the screen off for a short time
- switching "energy saving" off always finishes the flickering
Can anyone shed light on the reasons for this?
Try unticking the second option in Power Saving mode, which is supposed to lower the FPS in order to preserve power. You can still user PS mode but the flickering should be gone.
iridaki said:
Try unticking the second option in Power Saving mode, which is supposed to lower the FPS in order to preserve power. You can still user PS mode but the flickering should be gone.
Click to expand...
Click to collapse
thank you!
i already unticked all single options there. didn't change it. the only solution is to switch the whole "enrgy saving mode" off as it seems.
paddybear79 said:
thank you!
i already unticked all single options there. didn't change it. the only solution is to switch the whole "enrgy saving mode" off as it seems.
Click to expand...
Click to collapse
I am sorry, I did not read the OP carefully enough, where you stated that
it's not related to any one of the single settings in "energy saving mode"
Click to expand...
Click to collapse
I am using PS mode with all the options checked all the time, I don't think I have ever disabled it, and I haven't noticed the issue you mention. Can you tell us more about root status/ROM/kernel on your device etc? Also, have you tried disabling PS mode and observing the phone for 24 hours or so, to see if it still does the flickering at some point?
I'm having same issue. As for the conditions my result is that it would only appear after wake up when power saving is on with lowest brightness. Also it's not noticeable on dark wallpapers. Any ideas other than "turn off" power saving mode?
Just to add, I'm running stock 4.1.2 version which didn't fix this problem and I was observing phone without PS for a few days without any flicker of this kind.
Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service
I've noticed at night that my screen is redder than during the day. I've checked all my setting and the blue light filter is not on and there is no schedule set. Anyone else notice this? When I turn on my screen it will often be normal colors and then quickly shift to a red hue. If I turn on the blue light filter, it gets even redder.
I've noticed the same thing on mine. Looks like a double filter. First one maybe from native android and second one from Samsung. Can't find the setting for the former one though.
I found these settings to work well and looks great where I set them. You can try that and change to your liking in reference to your eyes.
Did you upgrade from a phone with night mode, while night mode was turned on? I saw a thread somewhere than said even though the S9 doesn't have a night mode setting, if you imported settings from a phone that had it enabled, the S9 will still trigger night mode., with no obvious way to turn it off. IIRC, he had to use ADB to change the night mode setting.
Let me see if I can find that thread again.
Edit: Here it is:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap/
And here's the ADB fix if you don't want to install Nova Launcher:
https://forum.xda-developers.com/galaxy-s9-plus/help/weird-night-mode-type-issue-t3764161
meyerweb said:
Did you upgrade from a phone with night mode, while night mode was turned on? I saw a thread somewhere than said even though the S9 doesn't have a night mode setting, if you imported settings from a phone that had it enabled, the S9 will still trigger night mode., with no obvious way to turn it off. IIRC, he had to use ADB to change the night mode setting.
Let me see if I can find that thread again.
Edit: Here it is:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap/
And here's the ADB fix if you don't want to install Nova Launcher:
https://forum.xda-developers.com/galaxy-s9-plus/help/weird-night-mode-type-issue-t3764161
Click to expand...
Click to collapse
That was it. Thank you very much for that. I didn't even consider that native android night light was different from the Samsung blue light filter. Excellent work. I appreciate it.
Funny thing was I would use nightlight/blue light filter, it was just the fact that I couldn't turn it off if I wanted to.
I have a Xiaomi Redmi Note 9S which has the following behaviour: it works normally until the moment it goes under the sun, then (apparently only) the backlight of the screen is turned off and never turns on again until I restart the smartphone, where it works normally until the very moment it "detects" a bright light like under the sun, then the screen goes black. When this happens, sometimes you can still see the shape of what was on screen, but most times it only goes totally black.
When the screen is black, the telephone keeps working normally (music keeps being played, receives calls, vibration responses keep working, etc...(confirmed it using scrcpy and all is working normally)), only that the backlight is turned off and it keeps totally black. During the night, i.e. with artificial light, the telephone works normally (I was able to replicate the error using a strong flashlight above the telephone, the screen also went black the very moment I turned it on).
What I tried to resolve: restarted many times, disabled every auto brightness (also one that I think is a Xiaomi MIUI only, sunlight detector, something like this) settings that are in the configuration menu, restarted using vol up + power button. Factory reseted the smartphone. Disabled pocket mode before and after factory reset.
Any idea how to proceed? What is killing me is that it seem to be a software issue, like, why the screen don't turn on back after a while, but every time you restart it, or why the phone works all night long (i.e. there no strong light on it)?
How to capture the telephone log (logcat perhaps?) and be sure of what is the exact event that is disabling screen? Maybe I can manipulate it to prevent from happening, or to make screen goes back to normal after a while, as I work as a software developer.