Related
I've put this in the Development section because whilst it is almost fully functional, it still needs a lot of development. Please be aware of this when you download it. I am not to be held responsible for anything that may happen as a result of running this app.
Requirements:
Root Access & a Custom ROM (StreakDroid 1.8.0 recommended (CONFIRMED WORKING ON 1.8.0))
Built under a 2.2 framework. If you are running anything pre-2.2 please be aware it may not work.
Please remember to remove all previous versions of the app before installing.
Simply open the app and press the "Menu" button. I hope you can figure the rest out! Enjoy!
"LED Notification FREE" has been uploaded in the Market. It has full functionality and it Ad Supported.
Please be aware that this version includes an "AdBlocker Check". This will block the app from opening if you have an adblocker installed on your phone. Sorry about this but i hate adblockers Alternatively, you can just remove all instances of Admob from your Hosts file.
Code:
[I][B][COLOR="blue"]QUICK HANDCENT FIX[/COLOR][/B]:
Open Handcent, press 'Menu > Settings > Notification settings > Popup settings'.
[B]MAKE SURE[/B] 'Screen on for popup' is [B]UNCHECKED[/B].
Handcent wont interfere with my app from then on :D[/I]
NEW TO 2.0.1
Asks for SU Access when the app first loads Fixes some weird error that happens every now and again.
Completely re-coded the SMS receiver. Much smoother now!
SMS and Gmail Notifications can be turned on or off
New settings page - done properly now, wont save anything to sdcard [you can delete your STREAKLED folder now!] Press the 'menu' button when you open the app for settings.
Permissions tweaked (should be less LED problems)
KNOWN BUGS
Changing orientation during the pattern causes problems. Just don't do it!
Notifications overwrite each other. So if an SMS message arrives and then a Gmail, only the Menu button will be lit, and vice versa.
Services cannot be stopped (only by uninstalling) FIXED - 2.0
Sometimes all the buttons will end up being lit, not sure why. [SHOULD BE FIXED]
TODO
Add options for turning the SMS and Gmail notifications on and off DONE - 2.0
Have different patterns for each DONE - 1.3
Improve the UI (sort of) DONE - 2.0
Improve the pattern flashing sequence (sort of) DONE - 2.0
Clean up the code (WIP )DONE - 2.0
Fix orientation issue
This will ALWAYS be available for free on here, on Modaco and on my website (see sig) but i have uploaded a 'donate' version on the Android Market Place priced at £1.50, just incase you fancy buying me a beer
Enjoy
Meltus said:
I've put this in the Development section because it is not fully functional and still needs a lot of development. This is basically a proof of concept app.
Requirements: Root Access (tested on 2.1 but build under a 1.6 framework so it should work on 1.6)
All you have to do is run the application, hit the home button and receive a text (or send yourself one). If your phone is locked it will wake up and dim the screen and flash the home/menu/back LEDs in a nice pattern and then keep the screen dimmed until you unlock the phone manually.
The only problem is that you will receive a Force Close error message and you will then have the re-open the app for it to work again. I am trying to fix this but will not be able to look into it for a few days so i thought i would release what i've done so far.
I will be adding settings and more patterns as soon as i can fix this FC error.
Enjoy
Click to expand...
Click to collapse
Well... GREAT!!! Thanks! It works... Was searching this kind of app for weeks. Thanks again!
Great little app. Can't wait for thenext update
Nice work.
Just out of interest though, what's the dangers of having the screen on dim all night if I get a text message at stupid o'clock?
Wouldn't want to burn anything on my screen if that is possible.
Amdathlonuk said:
Nice work.
Just out of interest though, what's the dangers of having the screen on dim all night if I get a text message at stupid o'clock?
Wouldn't want to burn anything on my screen if that is possible.
Click to expand...
Click to collapse
Screen burn is an issue on LCD screens, hence why i set it to do a dim wake lock instead of a full brightness one. Saying that, i have absolutely no idea whether screen burn would still occur but ill test it tonight and report back
On a positive note i have fixed the FC error and will release the fully working version tomorrow!!
Nice work dude ! Look forward to a full release tomorrow.
Any way to make this compatible with non rooted steaks on 1.6?
Sent from my Dell Streak using XDA App
jdmnash said:
Any way to make this compatible with non rooted steaks on 1.6?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
No, i'm afraid not.
Without Root Access it will probably just force close.
Currently in the process of adding more LED patterns
It also now wakes the phone, unlocks the phone and displays an "SMS Message Received" popup which it then hangs at until you close it.
Do you guys think this is better or should I make it lock the screen instead?
What else should i add/change?
Meltus said:
Do you guys think this is better or should I make it lock the screen instead?
What else should i add/change?
Click to expand...
Click to collapse
I'd prefer it stayed locked, also if I read this thread correctly, it leaves the screen on (but dimmed?) is that true? I would need it to kill the screen, because as noted, it could kill your battery if you went a long time w/o clearing the alert.
Nice work so far though...
a042349 said:
I'd prefer it stayed locked, also if I read this thread correctly, it leaves the screen on (but dimmed?) is that true? I would need it to kill the screen, because as noted, it could kill your battery if you went a long time w/o clearing the alert.
Nice work so far though...
Click to expand...
Click to collapse
Yeah, that's the only problem.
unfortunately, killing the screen freezes the LEDs in whatever state they're in, completely defying the point of the app
What i could do though, is wake up the screen, flash the LEDs but leave one on and turn the screen back off. This would turn everything off apart from that 1 LED and you could use different LEDs for different notifications. I'll try that out later.
Yeah, that seems like a good idea. Maybe the Back LED for missed SMS, the Menu LED for missed call. Something like that.
That would be cool, I'll await your work and give it a try.
Well, it turns out that works miles better than what i was trying before.
Basically, it now turns the screen on, keeps it locked, flashes the LEDs, turns the screen back off and leaves the home LED on.
Give me about 10 mins and i'll put up a working version. No FC error this time
Can't wait for this!
Sent from my Dell Streak using XDA App
First post updated with a working version
None of the options work on the main screen yet, but they will.
Enjoy
I haven't tried this yet, but I just want to say THANKS! No notification light was driving me crazy! I'm gonna install it now. I like that it would kill the screen but leave the LED light on. That's perfect!
**EDIT**
Well, it didn't work perfectly. Here's what happened on my Beta Streak....
With locking disabled (I use the 'NO LOCK' widget), it turned the screen on and said 'SMS received' and the home LED was on, for about 1-2 minutes, then both went off. When I turned back on the screen and read the msg, the LED went out.
With locking enabled, like most people would be using the app, the screen turned on for a few seconds while the LED pulsed, then both went out. No notification. When I unlock and read the msg, the home LED stays on. I have to 'clear' the app in the notification tray and lock then unlock the screen to make the home LED go out.
Seems like they're little tweaks that could be needed. If you can make this work and be functional, I'll donate to your Paypal! Again, thanks for your work on this project!!
Yeah, it's still pretty much in it's 'Alpha' stage
Cheers, for the feedback, i'll look into the errors.
I know that if the screen is unlocked the Home LED will stay on until you lock/unlock the screen, but that should be an easy fix (hopefully), and i've not set up the Thread's quite right i don't think which could be causing the timing errors.
I'll be spending all of tomorrow getting this thing working so i'll report back
Awesome! You are the man!
A thought for down the road development:
Earlier today when I was thinking about this, I imagined an interface where the user could "record" their own flash sequence for each type of notification they had - email, sms, mms, missed call, etc. Just choose which notification they want to specify, click record, then tap the capacitive buttons in the sequence you want them to light up, then end the recording. Interval timing could be recorded or specified manually. Just a few ideas!
Thanks so much for this. I'll give it a run soon.
Awesome work. Wanted something like this. I hope you will be able to add notifications for misssed calls and gmail as well. Keeping my fingers crossed.
I have been having an issue with my device recently. I am not sure if it is ROM related or a defective device, but it only seems to happen when auto rotation is enabled. I first noticed the issue last week when I flashed Beans 16 then 17. When the screen would auto rotate, the device would sometimes lock up and I would need to do a battery pull to restart the phone. This was happening over 5 times per day.
The strange part is, I never had this issue before when I was on Beans 14, or its just possible I didn't have auto rotate on, not sure.
I have tried everything - loaded stock firmware back and ran casual again, flashed Beans 14 and set my entire device back from a fresh install.
Again, tonight, screen froze twice and I had to to a battery pull
Does anyone have any idea what's going on? I never has this issue before and it's driving me nuts - having flashbacks of blackberry battery pulls
Clean or dirty flash? This happened to me the other day, froze out of nowhere for no reason
jcastagnino said:
I have been having an issue with my device recently. I am not sure if it is ROM related or a defective device, but it only seems to happen when auto rotation is enabled. I first noticed the issue last week when I flashed Beans 16 then 17. When the screen would auto rotate, the device would sometimes lock up and I would need to do a battery pull to restart the phone. This was happening over 5 times per day.
The strange part is, I never had this issue before when I was on Beans 14, or its just possible I didn't have auto rotate on, not sure.
I have tried everything - loaded stock firmware back and ran casual again, flashed Beans 14 and set my entire device back from a fresh install.
Again, tonight, screen froze twice and I had to to a battery pull
Does anyone have any idea what's going on? I never has this issue before and it's driving me nuts - having flashbacks of blackberry battery pulls
Click to expand...
Click to collapse
Do you have ripple effect, ink color or any of the TW features enabled while using AOSP Lockscreen?
Because if you do, and your phone times out, your phone will freeze and you will need to do a battery pull.
If you use AOSP lockscreen, you have to disable any of the TW lockscreen features.
jcastagnino said:
I have been having an issue with my device recently. I am not sure if it is ROM related or a defective device, but it only seems to happen when auto rotation is enabled. I first noticed the issue last week when I flashed Beans 16 then 17. When the screen would auto rotate, the device would sometimes lock up and I would need to do a battery pull to restart the phone. This was happening over 5 times per day. The strange part is, I never had this issue before when I was on Beans 14, or its just possible I didn't have auto rotate on, not sure...
Click to expand...
Click to collapse
You will get more input if you post in the Beans thread
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
trentb12 said:
Do you have ripple effect, ink color or any of the TW features enabled while using AOSP Lockscreen?
Because if you do, and your phone times out, your phone will freeze and you will need to do a battery pull.
If you use AOSP lockscreen, you have to disable any of the TW lockscreen features.
Click to expand...
Click to collapse
Wow, I didnt know the AOSP lockscreen would casue those issues....so turned it all off, and so far so good!! Guess I never had those options selected before.
I have not had a single lockup/freeze yet. I wonder why Beans does not gray those options out when the AOSP lockscreen is selected.
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
luizlee86 said:
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
Click to expand...
Click to collapse
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
shimp208 said:
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
Click to expand...
Click to collapse
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
luizlee86 said:
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
Click to expand...
Click to collapse
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
shimp208 said:
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
Click to expand...
Click to collapse
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
luizlee86 said:
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
Click to expand...
Click to collapse
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
shimp208 said:
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
Click to expand...
Click to collapse
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
luizlee86 said:
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
Click to expand...
Click to collapse
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
shimp208 said:
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
Click to expand...
Click to collapse
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
luizlee86 said:
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
Click to expand...
Click to collapse
Unfortunately a factory reset would probably be the best thing to do.
shimp208 said:
Unfortunately a factory reset would probably be the best thing to do.
Click to expand...
Click to collapse
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
luizlee86 said:
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
Click to expand...
Click to collapse
You could also try re-flashing the stock ROM to see if that fixes it, another suggestion that could possibly work is running a fix permissions utlity.
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
EDIT: found what was causing it! It is the latest version of Floating Notifications (when show on lockscreen is enabled)!
Thanks a lot shimp!
luizlee86 said:
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
Click to expand...
Click to collapse
That's wicked bizarre that even after all those things the problem still persists. You could try bringing it in to Verizon to see if they can do anything otherwise a hardware issue may have arisen.
Sent from my SCH-I535 using xda premium
So I got my T-Mobile S9+ on Tuesday. I got everything loaded up and restored and at 10pm, I noticed the color shift on the screen into a night mode type color scheme. Whites were turning a yellowish hue. I'm running Nova Launcher as my main launcher and checked all the settings in the phone itself, and nothing is enabled for Night mode. I ended up having to reboot the phone and it was back to normal.
It happened again the last two nights at 10pm EST. No idea why. I've tried everything short of rebuilding the phone (I know most will suggest this, but I'm trying to avoid it for the time factor). Rebooting seems to reset the clock on whatever is doing it and it goes back to normal.
My wife has the same phone and similar setup with Nova and hers doesn't do it. I've tried going back to the stock Samsung launcher when it is happening and nothing seems to fix it.
Anyone had this happen? I don't see any third party apps that would cause this that I have installed. the only app I can think of that even has a night mode is Nova, but that just effects menus and turns them black, not yellow.
*Edit* Sorry, I meant to put this in the Q&A Section.....
settings - display- blue light filter - custom schedule
vivilxw said:
settings - display- blue light filter - custom schedule
Click to expand...
Click to collapse
Blue Light filter is disabled and schedule is disabled as well. I've tried turning ON the blue light filter when the issue happens and it actually kicks in on top of the other issue and makes it even MORE yellow.
Seems unrelated to that.
Have you checked the sunset to sunrise toggle..?
Anyone having this blue light issue...blue light is enabled. When I turn on phone from sleep mode it takes like a second to switch to blue. Very weird
Sent from my SM-G965U1 using Tapatalk
zeebone said:
snip.
Click to expand...
Click to collapse
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
(ORIGINAL, not needed, left for posterity)
This needs more attention. I know EXACTLY what this is. You came from a more recent Android device that uses Google's own "night mode" settings. I know, because I did too. I came from the Razer Phone and had night mode enabled on that on schedule. After my screen turned a real dank orange color at night, I started looking for the setting and discovered Samsung's "Blue Filter" setting and that enabling it made the orange color even more dank. So I immediately knew that the setting must have carried over when I logged into my google account and carried over my settings.
I have a workaround, but it is just that, it's not a permanent fix and I'm still trying to figure out how to fix it permanently. You need to install System UI tuner from the playstore. Follow the instructions to make the app work by granting permissions using ADB while connected to a PC. This is not root and will not void your warranty as such. From here, you can either just disable "Night Mode" under the miscellaneous tab or you can go to the playstore and install "Nougat / Oreo Quick Settings" which will allow you to add the toggle for "Night Mode" to your quick settings pull down bar. Unfortunately, you have to do this every night to get rid of the ugly orange color.
I've tried disabling the setting on my Razer and syncing everything in my google account from that phone, then restarting my galaxy and hoping that the settings would transfer over, but it hasn't worked. My fear is that I will have to factory reset the Galaxy, go back to Razer, toggle the night mode on and back off. Sync settings, then sign back into my galaxy and hopefully the settings will not come back this time. I just haven't because I don't want to set EVERYTHING back up again, ugh.
If anyone is aware of how to disable the "Night Mode" schedule feature in a different way without factory resetting the device, please let me know. Thanks!
There's an easy solution to this, if you hadn't switch off the night mode on your previous phone before transferring to the S9:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap
cawith said:
There's an easy solution to this, if you hadn't switch off the night mode on your previous phone before transferring to the S9:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap
Click to expand...
Click to collapse
LOL. Jesus. My long-winded solution above yours looks barbaric now. Good thing I wasted a good evening sifting through ADB commands. Good on you for finding this and posting this. Nova saves the day again.
lessthanzach said:
LOL. Jesus. My long-winded solution above yours looks barbaric now. Good thing I wasted a good evening sifting through ADB commands. Good on you for finding this and posting this. Nova saves the day again.
Click to expand...
Click to collapse
Wish I had waited a little bit longer and had done this. I ended up backing everything up to my SD Card using Smart Switch and then wiping and rebuilding the phone yesterday afternoon. However, I didn't choose to restore from Google and only from Smart Switch, so the night light setting didn't end up carrying over again.
Good to know I wasn't crazy and that my phone wasn't defective.
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
I was all ready to get adb working and use the above workaround, and / or install nova launcher and fix this issue but THIS WORKED.
THANK YOU it has been bugging me for WEEKS.
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
You are amazing! It was the Google play books settings.
Thank you so much! It just started happening last week so I knew that it didn't come from my smart switch settings. Google play books was on night light settings from 10p-6a. I can see my phone again at night without my screen being yellow or without having to restart my phone. Thank you so much!!! I NEVER would've looked there.
Works like magic on my S7. Thanks a lot!
Perfect!
This fixed my problem, so thank you!
Google play book... who would have guessed..
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
zeebone said:
So I got my T-Mobile S9+ on Tuesday. I got everything loaded up and restored and at 10pm, I noticed the color shift on the screen into a night mode type color scheme. Whites were turning a yellowish hue. I'm running Nova Launcher as my main launcher and checked all the settings in the phone itself, and nothing is enabled for Night mode. I ended up having to reboot the phone and it was back to normal.
It happened again the last two nights at 10pm EST. No idea why. I've tried everything short of rebuilding the phone (I know most will suggest this, but I'm trying to avoid it for the time factor). Rebooting seems to reset the clock on whatever is doing it and it goes back to normal.
My wife has the same phone and similar setup with Nova and hers doesn't do it. I've tried going back to the stock Samsung launcher when it is happening and nothing seems to fix it.
Anyone had this happen? I don't see any third party apps that would cause this that I have installed. the only app I can think of that even has a night mode is Nova, but that just effects menus and turns them black, not yellow.
*Edit* Sorry, I meant to put this in the Q&A Section.....
Click to expand...
Click to collapse
You might have your blue light filter turned on to a specific time. Mine is set to come on at 6 pm and go off at 6 am. Check that in settings.
lessthanzach said:
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
Did you tripped your knox warranty, when using this ??..... I want to disable night mode on my note 9.....did adb trigger knox ??? Please advice sir... And thank you
Click to expand...
Click to collapse
If nothing solves your peoblem then just download systemuituner app from playstore and give it some permission using adb commands and then turn off the night light option in the app.
It helped me .:fingers-crossed:
Buddy ur basically a lifesaver. Note 10+ fixed too, can confirm!
Buddy the workaround just saved me at least one trip to SES which is like 30 mins away from my house in Long Island, saved me from erasing the phone and restore it which would definitely be a nightmare and also u just saved my one big annoyance with this phone for the first week of usage!! U are the man!!
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
Vinay_sandy said:
If nothing solves your peoblem then just download systemuituner app from playstore and give it some permission using adb commands and then turn off the night light option in the app.
It helped me .:fingers-crossed:
Click to expand...
Click to collapse
I tried it, both options switched off.
lessthanzach said:
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
Click to expand...
Click to collapse
Huge thanks as you saved me from factory resetting my new Mi 9 Lite. That's why I love the internet.
Can anyone tell me how to change the screen timeout/sleep time on the M5? I've tried display, battery and security settings but it doesn't appear to be in any of them. It's a real pain trying to read emails, news, flipboard etc with the standard (30 seconds?) timeout.
mickrick said:
Can anyone tell me how to change the screen timeout/sleep time on the M5? I've tried display, battery and security settings but it doesn't appear to be in any of them. It's a real pain trying to read emails, news, flipboard etc with the standard (30 seconds?) timeout.
Click to expand...
Click to collapse
If it's not under >Display>Sleep, you are in trouble!
Should be there, try again!
kupa said:
If it's not under >Display>Sleep, you are in trouble!
Should be there, try again!
Click to expand...
Click to collapse
Just discovered it is under Display/Sleep. But Sleep option is greyed out.
*UPDATE* Aha! Power saving mode was on. It must be enabled by default because I can't think why I would've enabled it. Sorted now.
mickrick said:
Just discovered it is under Display/Sleep. But Sleep option is greyed out.
*UPDATE* Aha! Power saving mode was on. It must be enabled by default because I can't think why I would've enabled it. Sorted now.
Click to expand...
Click to collapse
I've had the CMR-W09B for a week now and found that when I change the sleep time it always reverts to the default 30 seconds after a while. Power saving mode not active. Installed Screebl Pro to manage timeout, but unlike my many other devices using the app, it seems to be overridden by the system and doesn't work. Whether Screebl is active or not, or what I set the timeout to, the timeout returns to 30 seconds.
This happening to anyone else, or am I just special?
I got it just turn off your battery savers
How to change the battery in Huawei P 10 lite?