I have the amazfit stratos 2. I installed a custom watchface.
The problem that i'm facing is that the watchface is different when locked and when unlocked. I would like it to be like on the photo from the unlocked screen. You can see a green shade on the unlocked state. When it's locked it's only a sort of green line without any shade.
Usually most watchfaces go into 8 colours mode when screen is locked, it was meant to save battery (?) and increase contrast, but I think it was also some limitation of the initial API used to display watchfaces. Every custom WFZ that is available on SAWFB site will display this behaviour. Some built-in ones won't look as bad if the background is only black or white. To avoid this, without keeping the screen on all the time and killing battery, you can personalise the WFZ by copying the same background to the 8c folder (WFZ is actually a zipped folder) or use a Java (APK) watchface.
lfom said:
Usually most watchfaces go into 8 colours mode when screen is locked, it was meant to save battery (?) and increase contrast, but I think it was also some limitation of the initial API used to display watchfaces. Every custom WFZ that is available on SAWFB site will display this behaviour. Some built-in ones won't look as bad if the background is only black or white. To avoid this, without keeping the screen on all the time and killing battery, you can personalise the WFZ by copying the same background to the 8c folder (WFZ is actually a zipped folder) or use a Java (APK) watchface.
Click to expand...
Click to collapse
Thanks for your answer. I've checked what you suggested. But like you can see in the pictures it was already like this. The weird thing is that the first time i installed this watchface everything was fine. Than i modified it to display the temp instead of the total km. When i installed it , i notified this behavior. So i installed the original one again and still the same weird behavior.
Try using these command on adb, with the watch connected to the computer, this will reset the launcher and watchfaces cache (root not needed):
Code:
adb wait-for-device
adb shell rm -rf /sdcard/.watchfacethumb
adb shell pm clear com.huami.watch.launcher
lfom said:
Try using these command on adb, with the watch connected to the computer, this will reset the launcher and watchfaces cache (root not needed):
Code:
adb wait-for-device
adb shell rm -rf /sdcard/.watchfacethumb
adb shell pm clear com.huami.watch.launcher
Click to expand...
Click to collapse
Sadly that didn't work. I've shared the original file maybe you or someone else can check it out to see if the same thing happens on there watch?
Same thing... And now I realize that I missed one thing: you are using Stratos, that comes with WOS2 (Watch OS 2.0), and it doesn't use the "8c" folder anymore, but some kind of color mapping/dithering in another folder named "26w". Even using a black & white PNG in 8c folder, WOS2 removes the dithering in my tests.
If you are into graphics and want to try to figure out how it works, I am attaching one of the stock WFZ for Stratos, so you can see what I meant above.
This kind of dithering from another stock WFZ seems to work better, but I don't know how to make them.
lfom said:
Same thing... And now I realize that I missed one thing: you are using Stratos, that comes with WOS2 (Watch OS 2.0), and it doesn't use the "8c" folder anymore, but some kind of color mapping/dithering in another folder named "26w". Even using a black & white PNG in 8c folder, WOS2 removes the dithering in my tests.
If you are into graphics and want to try to figure out how it works, I am attaching one of the stock WFZ for Stratos, so you can see what I meant above.
Click to expand...
Click to collapse
Thanks , i'll try this one out. I wish there was an easy programme that we could use to make or edit existing wachtfaces. The one i've send you looks very nice but only when not in locked mode sadly. I would be happy if someone gets this working.
Hi OP, me too interested in this topic... Got Stratos yesterday and cant really understand why they impact screen awesomeness in this way...
Also interested in this topic. If.we can get the lock/standby mode watchfaces look better would be a great win for this cool watch.
Sent from my Redmi 5 Plus using Tapatalk
It can't be done.
The watch in standby switches the display to the 8 color mode and you can't do anything about it.
It is one of the reasons why it used so little energy
fzelle said:
It can't be done.
The watch in standby switches the display to the 8 color mode and you can't do anything about it.
It is one of the reasons why it used so little energy
Click to expand...
Click to collapse
8bit mode is OK - but dont shut off antialiasing....
My Garmin FR935 screen is 240x240, has ****ty colors (64) but looks WAY BETTER due antialiasing constantly on and has 3weeks batt life if connections are off (I just upload stats over wifi when I am home)
So technically 8bit mode is OK but dont shut off antialiasing - as screen really turns crap (until you move your hand to turn antialiasing on)...
phnikola said:
8bit mode is OK - but dont shut off antialiasing....
My Garmin FR935 screen is 240x240, has ****ty colors (64) but looks WAY BETTER due antialiasing constantly on and has 3weeks batt life if connections are off (I just upload stats over wifi when I am home)
So technically 8bit mode is OK but dont shut off antialiasing - as screen really turns crap (until you move your hand to turn antialiasing on)...
Click to expand...
Click to collapse
I wrote 8 color mode, not 8 bit.
Related
FXP045 released, http://forum.xda-developers.com/showpost.php?p=16822404&postcount=4
Current Issues (FXP045) and unofficial fixes
Hardware keyboard layout scrambled - Old keyboard file is no longer in this ROM but appearently just pasting the old stock file (attached) to /system/usr/keychars/ fixes the layout. The included keyboard changer app force closes.
LEDs under soft keys Return and Menu - Replace /system/etc/hw_config.sh with the attached file.
Screen flicker upon turning on - New issue in fxp045.
can this work on Ray?
the flash does not work either
and the keyboard light does not work when use (when charging, it works)
and the max brightness is not very bright
xutienan9520 said:
can this work on Ray?
the flash does not work either
and the keyboard light does not work when use (when charging, it works)
and the max brightness is not very bright
Click to expand...
Click to collapse
I believe these fixes will work on Ray but you should find the stock values from Ray ROM because there probably are some differences.
Basically, only one issue you're having can potentially be fixed using SK17i fixes and that is max brightness by applying the fix for screen flicker. If you can't get a hold of Ray's stock values, try SK17's stock ones, but do a backup in recovery just in case.
thanks～
i changed the light.semc.so in system\lib\hw from stock 2.3.3, now i have the max brightness, but the keyboard light is on for ever! i can't close it!!!!the colour is always pink!
i think i can edit the file, i am in Mac, so is there a way to edit it without linux?
xutienan9520 said:
thanks～
i changed the light.semc.so in system\lib\hw from stock 2.3.3, now i have the max brightness, but the keyboard light is on for ever! i can't close it!!!!the colour is always pink!
i think i can edit the file, i am in Mac, so is there a way to edit it without linux?
Click to expand...
Click to collapse
i'm editting these files on the phone. copy the file to sdcard to edit it, with any kind of text editor. i use edit function of Total Commander. then i copy over the original file in system with Root Explorer. backup original file to sdcard just in case.
dont know about Mac much, sorry.
root explorer is a paid app but i think ES file explorer has the required functionality
LEDs under soft keys Return and Menu on maximum brightness - distractingly bright, in almost all environments. SOLUTION posted here: http://forum.xda-developers.com/show...&postcount=178
can't open it，need help
xutienan9520 said:
LEDs under soft keys Return and Menu on maximum brightness - distractingly bright, in almost all environments. SOLUTION posted here: http://forum.xda-developers.com/show...&postcount=178
can't open it，need help
Click to expand...
Click to collapse
oh, i messed up the links. will be fixed in a moment =)
Per someones suggestion I've added modified files and instructions on how to replace the original CM ones.
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
PoedelPCS said:
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-
0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
Click to expand...
Click to collapse
Thank you good Sir! Testing it later!
PoedelPCS said:
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-
0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
Click to expand...
Click to collapse
Amazing job! I'm gonna test it out now in a super dark place to see if i can check whether it stays on when closed. =)
I'll be updating original post with results and updated files in a bit.
Edit: Unfortunately keyboard lighting stays on and not only when keyboard is closed but even when phone is locked. Which means, its lit at all times. Won't be updating the files yet, because I don't know how much of a battery drain it is, but i'll put in information about it, so people can decide for themselves.
Nice to see process.
Now i need to find the button light for RAY
sulkie said:
Unfortunately keyboard lighting stays on and not only when keyboard is closed but even when phone is locked. Which means, its lit at all times. Won't be updating the files yet, because I don't know how much of a battery drain it is, but i'll put in information about it, so people can decide for themselves.
Click to expand...
Click to collapse
I thought that
Okay, there is a binary called slidercounter that or something similar sets a system var. If you take your dev Tools app and look unter Configuration there it is mentioned:
hardKeyboardHidden=2 <- if closed
hardKeyboardHidden=1 <- if opened
We now just have to find out where it occurs and if not we make a background script that ech0 x (100) or 0 into the node depending on the state.
But there must be a system process watching this we could use.
Don't hide, I'll find you anyway
---------- Post added at 06:16 AM ---------- Previous post was at 06:14 AM ----------
xutienan9520 said:
Nice to see process.
Now i need to find the button light for RAY
Click to expand...
Click to collapse
did you look, if in ray the nodes under /sys are similar to the pro mini?
you can test using adb shell or terminal app cat'ing the node to see what's in it and echo'ing a number to see what happens.
You meant progress, didn't you
as I am using Scriptmanager anyway I made 2 oneliners besides the shebang that echo either 0 or 100 into the node called
liteon.sh
and
liteoff.sh
put the scripts into root of sdcard, start scriptmanager, choose liteon.sh and check run as root and save
Do this either way with liteoff.sh
Go to your Mangos Homescreen, add a widget, choose Script Manager and choose liteon.sh and in the next step liteoff.sh
You´ll have to Widgets, one puts light on, on off.
This is of course a workaround an will be implemented into lights module. Fxp knows about the fact already.
PoedelPCS said:
as I am using Scriptmanager anyway I made 2 oneliners besides the shebang that echo either 0 or 100 into the node called
liteon.sh
and
liteoff.sh
put the scripts into root of sdcard, start scriptmanager, choose liteon.sh and check run as root and save
Do this either way with liteoff.sh
Go to your Mangos Homescreen, add a widget, choose Script Manager and choose liteon.sh and in the next step liteoff.sh
You´ll have to Widgets, one puts light on, on off.
This is of course a workaround an will be implemented into lights module. Fxp knows about the fact already.
Click to expand...
Click to collapse
not the most elegant solution but it'll do until the fix is in =)
good job though
If I had more time I would have searched where the system keeps the var keyboardHiddenState or how it was called and build a condition of if it's open and not bright enough to switch in on/off
But how I understood fxp the fact about the light seems to be enough to get this working ..I hope so
new issue:
km launcher disturbes camera module.
I use the KM Launcher to determine which keyboard to use in which state.
Portrait: swype
Landscape: thumb keyboard
Keyboard open: hardware keyboard
This is a very cool application that worked perfectly on my rooted stock. If it is active the cam works in the cam app, but not in many other apps that use the cam, e.g. barcoo barcode scanner. I have to disable KM Launcher before using these apps. Hope it'll be fixed automatically in the next release.
I just cannot guess why that happens.
Hey guys I still have the problem with the over sensitive lcd backlight, whenever I'm in a brightly lit room the backlight starts going crazy and sometimes goes so dark I can't see the screen, it then goes super bright.
It repeats this several times a day
I've tries the fix in this thread but it doesn't work
Could someone attach the fix to this thread? As I've tried the the fix using terminal emulator
Thanks
EDIT: it started doing this while I was writing this
Sulkie did append the script to the first post of the thread. Did you test it?
send from a fruit called mango using xda app.
I did it before but it didn't work, I found the reason it didn't work was because I didnr change the permissions.
Sorry I got confused
---------- Post added at 12:51 PM ---------- Previous post was at 12:43 PM ----------
Its still going crazy, I followed the instructions properly though,
When I get home ill upload a video of it happening
Hello,
After all, I had a amazfit pace smarth watch and joined you. So, hi everybody.
After a one day usage, i noticed that (i updated to latest version 1.3.3a) screen resolution of watch changes for a while. If you double tab screen it turns normal, for a few seconds later screen turns worse resolution. Do we have any option to keep same good resolution always?
Thanks,
It's not the resolution change, but color pallet change. Once you double tap the screen you wake up the watch and you see the full color watchface. After few seconds watch goes into power safe mode and in this mode screed has only 8 colors to safe energy
qbus098 said:
It's not the resolution change, but color pallet change. Once you double tap the screen you wake up the watch and you see the full color watchface. After few seconds watch goes into power safe mode and in this mode screed has only 8 colors to safe energy
Click to expand...
Click to collapse
Do we have any option to stop that changing? Custom rom or other mod etc can be possible?
No, this is the reason why the amazfit has that amazing battery life.
If you want a watch that has 12 hours of battery life with a full on display buy a Garmin/Samsung/...
fzelle said:
No, this is the reason why the amazfit has that amazing battery life.
If you want a watch that has 12 hours of battery life with a full on display buy a Garmin/Samsung/...
Click to expand...
Click to collapse
It would be great to make an option for that. They could write easily that kind of command into the os.
I think it can decrease battery life but not too much because screen type is not same as Samsung/Garmin etc...
The Bip doesn't have that pattern and has amazing battery life...
At least a way to enable full watchface it when backlight is ON : as a nurse, i use seconds a lot de check pulse of my patients, have to double tap with my nose to see it... =)
If someone with a rooted watch could post result to these commands to see what we can tweak (among all settings) !
Code:
adb shell settings list system
adb shell settings list global
adb shell settings list secure
Thanks, on, 133a, not results...
Can't you go into settings in the watch, and turn "always on" feature?
Swipe down, tap settings, tap common, scroll down, tap backlight, choose "always on".
But then you have to double tap or press button always, to get into power saving mode.
Sent from my LG-G3 using Tapatalk
There is no changing happening by these options. Always 8 color seems. Interesting :/
Hey Guys, happy new Year to everyone !
Maybe i found a soulution for people like me, where facing Red/Pink Issues on there Note 8. Specially for people, that want to use Amoled-Kino Screen mode.
For me, the Issue looks like, when i activate Amoled Kino- My Screen Colors get low down, like when you put out 50 % saturation and contrast plus a Red Tint. Anyway, Samsung offers a Software Fix with Adaptive Mode for Display and you can regulate with 3 Sliders to correct your Color. But how ever i set the Values, the Colors in Adaptive Mode are very cold and its sad when i lay down my Note beside my old S7 Edge. Special with activated Kino Mode.
So i searched a few Days in the Web and found a App called : ''ColorModeChancer''. This simple App does nothing else, then to Set the Values for Red/Green/Blue and Contrast/Saturation manual. When i understand the Dev right, it talks to the Kernel and maybe the Screen Configuration for Colors/Saturation and Contrast is load from Kernel and not for Example from another File or Script from System itself. But im no Dev and maybe i talk Bull**** how it exactly works Ask the Dev by yourself or Read Playstore Description. Maybe you understand it better then me. I just wann guide you all to maybe solve the Red Tint Problem.
Steps to install:
You need to be Rooted.
''To avoid using one App for "setting last saved value without open any window" and another one for "open Settings window" I choosed this App behavior:
1) run the App
2) first run ONLY sets last saved value
3) next launches within 30 seconds will open the Settings
4) subsequent launches within 30 seconds will do #3
5) if 30 seconds are passed, the next launch will do #2'' > Description copied from Playstore
6) (From me): Set Cinema Mode in the App and everything is good, you have now a correct configuratet screen with Amoled Kino Mode how it should work
Bugs :
Maybe you get a little Bit of Lag when you scroll down in Apps like Facebook or Instagram. For me, i solved it with cache cleaning for these Apps. Anyway it works like Charm for me.
The App costs around 50 Cent, was orignal made for non Samsung Stock Roms like Linage, Cyanogen etc. where dont have the Option in Settings, to set the Samsung Screen Modes like Amoled Kino.
I dont Link the Playstore Link here, because the App costs Money and i dont want to make advertising for the Dev or anyone else. Just want to share this Guide/Workaround for interested people with the same issues as me. One more Time, the App calls ''ColorModeChanger'' and it is aviable on the Playstore.
Further i Emaild with Samsung and they swear that the Screen Problem is a Software issue and not a Hardware Problem from the Screen itself. After that, i found this App and now i believe that Samsung tlaks the tings right, before i dondt believe that it is only Software Problem. Anyway, it works for me and the result is AMAZING
Have Fun & Good Luck ! :fingers-crossed:
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.
I unpacked and found something from Original ROM WatchFaces. Then try to understand and to be able to work on (.wfz) for customization Faces.
What can be displayed is customization:
One.wfz file can change:
-Background (we can choose more background image)
-Indicator (can choose more indicator watch)
-TimeHand (can choose more handHour,handMinute,handSecond)
-TimeDigital (can choose more DigatalTimeNumberFont)
-Widget (can choose and change widget info for any position).
I have tried and worked well on my Watch AmazfitPace Stock US version 1.3.6d...
Just copy .wfz to "/WatchFace" folder in Watch Pace...
Download Link: https://www.dropbox.com/preview/ndoko file/WatchFace/Custom All by NdokO.wfz?role=personal
I have customised/ported some wfz watchfaces from Stratos to Pace, what do you want to know? Maybe I can help...
lfom said:
I have customised/ported some wfz watchfaces from Stratos to Pace, what do you want to know? Maybe I can help...
Click to expand...
Click to collapse
Bro can we have your ported wfz file?tia
Maybe you guys can help,
There is a certain default watchface on Amazfit Pace called "Night Run" which on wrist turn displays the hi-res full-color watchface with second hand unless other watchfaces that only turn backlight on while showing low-res 8-bit color watchface.
Question, how to achieve that with custom watchfaces?
renel18 said:
Bro can we have your ported wfz file?tia
Click to expand...
Click to collapse
I will post it on a new thread as soon as possible.
lazizus said:
Maybe you guys can help,
There is a certain default watchface on Amazfit Pace called "Night Run" which on wrist turn displays the hi-res full-color watchface with second hand unless other watchfaces that only turn backlight on while showing low-res 8-bit color watchface.
Question, how to achieve that with custom watchfaces?
Click to expand...
Click to collapse
On my watch it goes to 8-bit too (full black background) and no seconds hand... Anyway, for Pace, there is usually a folder called 8c that holds the 8-bit images used while the watch is with screen locked (backlight off). I don't know if you can remove this folder or simply add full color images there. But for better battery saving, I think it's better 8-bit images with as most as black pixels possible.
my .wfz made...
anyone wanna try... i'm build it with full Customization Background,Indicator,TimeHand,TimeDigital&Widget...
finally i found a way to change customization Indicator...
here i'm new users, sorry i cant show link url download... wait 10 reply...
lfom said:
I have customised/ported some wfz watchfaces from Stratos to Pace, what do you want to know? Maybe I can help...
Click to expand...
Click to collapse
Now i want to know how to show a widget weeks with custom image week.png... (i saw the resources from Stock WatchFace.apk)
lazizus said:
Maybe you guys can help,
There is a certain default watchface on Amazfit Pace called "Night Run" which on wrist turn displays the hi-res full-color watchface with second hand unless other watchfaces that only turn backlight on while showing low-res 8-bit color watchface.
Question, how to achieve that with custom watchfaces?
Click to expand...
Click to collapse
Yes... i saw it too... i want to know how it work too.... and maybe add it to .wfz if i know... (sorry my bad english)
renel18 said:
Bro can we have your ported wfz file?tia
Click to expand...
Click to collapse
Wait, now i cant share the my link Dropbox for my .wfz build...because im is new and noobs ?
So this for my port build .wfz...
one .wfz can change and more customization... please trying and review...
https://www.dropbox.com/preview/ndoko%20file/WatchFace/Custom%20All%20by%20NdokO.wfz?role=personal
But that certain watchface (Night Run) goes low-res 8-bit without second hand when backlight is off - I mean even if you put full-color images inside the very folder of custom watchfaces, it becomes ****ty in standby mode. It's happening when you turn wrist - backlight turns on and Night Run shows hi-res full-color with second hand. When it goes back to standby mode, it goes back to low-res again. There must be some kind of script that does that, because other watchfaces does not do that.
Savvies, please, look into the guts of this watchface, because it is how it actually should be. The app called PaceOn is amazing, but it drains battery very fast - and long lasting battery is the main reason I bought Amazfit Pace.
lazizus said:
But that certain watchface (Night Run) goes low-res 8-bit without second hand when backlight is off - I mean even if you put full-color images inside the very folder of custom watchfaces, it becomes ****ty in standby mode. It's happening when you turn wrist - backlight turns on and Night Run shows hi-res full-color with second hand. When it goes back to standby mode, it goes back to low-res again. There must be some kind of script that does that, because other watchfaces does not do that.
Savvies, please, look into the guts of this watchface, because it is how it actually should be. The app called PaceOn is amazing, but it drains battery very fast - and long lasting battery is the main reason I bought Amazfit Pace.
Click to expand...
Click to collapse
I think you are a bit confused... As I said, most watchfaces have a folder 8c with low res images, so the watch faces that do not go to low res when screen is locked either don't have this folder (older versions, maybe) or the files aren't in low resolution. Either way, to make it compliant just create the folder if it doesn't exist and add the same files in 8-bit color.
About PaceOn, it only uses lots of battery if it keeps the screen or WiFi on all the time... It's the purpose of the app, but you don't have to keep it on, just when you need it, and it works very well.
lazizus said:
But that certain watchface (Night Run) goes low-res 8-bit without second hand when backlight is off - I mean even if you put full-color images inside the very folder of custom watchfaces, it becomes ****ty in standby mode. It's happening when you turn wrist - backlight turns on and Night Run shows hi-res full-color with second hand. When it goes back to standby mode, it goes back to low-res again. There must be some kind of script that does that, because other watchfaces does not do that.
Savvies, please, look into the guts of this watchface, because it is how it actually should be. The app called PaceOn is amazing, but it drains battery very fast - and long lasting battery is the main reason I bought Amazfit Pace.
Click to expand...
Click to collapse
yes I will trying to disassemble and I will find out how it (night run) working... then put in my .wfz files...
Ndoko said:
yes I will trying to disassemble and I will find out how it (night run) working... then put in my .wfz files...
Click to expand...
Click to collapse
Mate, I don't think you can achieve it simply disassembling wfz... WFZ's are very simple to make, uses pixel images... I think this particular watchface was made using Java and installed (flashed) into watch as apk, and can use vector graphics... Need some java programming skills...
lazizus said:
Mate, I don't think you can achieve it simply disassembling wfz... WFZ's are very simple to make, uses pixel images... I think this particular watchface was made using Java and installed (flashed) into watch as apk, and can use vector graphics... Need some java programming skills...
Click to expand...
Click to collapse
I think so too.
Because not only does " Night Run " work, but other STOCK watchface activities work the same.
ex) Power Armor,Prototype-Source,Super Avante ....
There are probably three modes of STOCK watchface.
1. locked screen
low-res 8-bit without second hand when backlight is off
2. turn wrist,backlight On
hi-res full-color with second hand but something is different from the Full Mode mode.
3. Full Mode
Full-color....
I wish User-made watchface would behave like a stock watch.
I am sorry for my poor English.
Hi all, I see on the new Rom for pace based on wos2 that they added the new functionality of wfz to have persistent second timehands with "hi quality when watch time" features. I try to extract a wathface with this feature and see a new format of timehands "26w mode" but I don't understand the file format to make personal graphic timehands, but I try to change in my watchface without this new features, only the timehands extracted from new wfz and is work perfectly so if we found how to use the new format type we can update all the old wfz to the new format.
Sorry for bad English :silly: