I just got a Fire HD 10 9th gen, and I can't root it, so unfortunately I could not install f.lux. I did some googling and it turns out you can turn on androids built in night mode instead with an ABD shell command, I have no idea why Amazon makes you use their crappy blue light filter, which is really just an overlay. So anyways,
1. Plug your Fire HD into your computer
2. Start an ABD shell (I use Fire Toolbox to do this easily)
3. Paste these two commands, one at a time:
"settings put secure night_display_activated 1"
"settings put secure night_display_auto_mode 1"
4. Open settings on your Fire HD, it should say night mode is enabled at the top, click this to change the schedule to sunset to sunrise or to any time range you want.
5. Use your Fire HD at night without being blinded or washing out your screen with amazon's crappy filter.
Thanks, the default night mode is so much better than the Blue shade filter crap they put in.
Oh NightLight does NOT show up on Screenshots!
But yes. it is indeed VERRY much better.
Thanks a lot.
So, the "night mode" in settings isn't shown after reboot? Do we have to run the adb commands every time we want to make changes?
If you leave it on "Automatic" it will show up again at night!
jcp2 said:
So, the "night mode" in settings isn't shown after reboot? Do we have to run the adb commands every time we want to make changes?
Click to expand...
Click to collapse
There isn't a "night mode" setting enabled there. But if you go to settings after pushing those adb commands and go in to settings, there will be a drop down from the top that says something like night mode is enabled. You can click that and set the time to activate it.
any way to make to stick it permanently even when rebooted and messed with? is there way to write these as init when I boot the FireHD?
If you're using Nova Launcher you can simply add a Widget -> Nova Activity.
Go to Settings and select .Settings$NightDisplaySuggestionActivity and you have a shortcut to the settings on the Main screen.
123nate said:
I just got a Fire HD 10 9th gen, and I can't root it, so unfortunately I could not install f.lux. I did some googling and it turns out you can turn on androids built in night mode instead with an ABD shell command, I have no idea why Amazon makes you use their crappy blue light filter, which is really just an overlay. So anyways,
1. Plug your Fire HD into your computer
2. Start an ABD shell (I use Fire Toolbox to do this easily)
3. Paste these two commands, one at a time:
"settings put secure night_display_activated 1"
"settings put secure night_display_auto_mode 1"
4. Open settings on your Fire HD, it should say night mode is enabled at the top, click this to change the schedule to sunset to sunrise or to any time range you want.
5. Use your Fire HD at night without being blinded or washing out your screen with amazon's crappy filter.
Click to expand...
Click to collapse
I tried this on a Samsung Galaxy Tab S8 running Android 12. The display went dark, and luckily I quickly set the first command to 0 instead of 1
When I did the 2nd command, it did nothing, but I'm worried the screen will stop showing anything later tonight if it's based off of automatically turning on at sunset.
I'm wondering if you know a way to do this now, for example maybe adjusting the Night Light settings?
The built in version on Samsung's tablet, which has an LCD display, is awful. No such problem with OLED or AMOLED displays.
https://www.reddit.com/r/GalaxyTab/comments/mu8m5a
That is a link explaining my problem in detail
I am thinking I am halfway there because running
settings put secure night_display_activated 1
Makes the display go dark and changing it to 0 or any other number like 2 or 3 switches it back to working.
I also tested both commands on my Pixel 6 Pro running Android 12 and they work perfectly.
running the second command as 2 or 3 picks either set times to automatically turn on or from sunset to sunrise.
I just need to try modifying the Night Light to be anything other than black
When I run the command, it changes the filter to black, because the screen stays on, and I can tell it's still on because the LCD shows light through a black screen
Yeah, the "eye care" mode is such stupid naive implementation of Samsung LCD tablets. And they also don't let you change the color temperature in the display settings like on Samsung AMOLED devices.
You can change to vivid or natural but no color temperature.
All the thridparty apps use this stupid trick with the color overlay because a app is not able to change the display calibration settings.
BUT Samsung should know better and change the screen color calibration to get the low blue light effect.
They are root users and should have the know how for their devices.
Because vivid and natural also changes the screens color calibration, they should be able to so instead of this stupid orange overlay.
With the extra dim mode I could not find out if they also simply put on a gray overlay or reduce correctly the led backlight to a minimum. But according to their stupid design choices and thinking the customer is dumb and will not notice, this is maybe also a gray overlay.
People are complaining for 2 years now, starting with the Tab S7!
If somebody also thinks that this is a dumb implementation please report this issue to Samsung: e.g. https://www.samsung.com/us/support/contact/
Related
RootDim (formerly known as ScreenDim) lets you set the screen brightness on backlit screens below what the OS normally allows, which is handy for amateur astronomy where the lowest normal OS backlight setting (even with a red nightmode) leaks enough through the black pixels to damage night vision. Moreover, SuperDim lets have several brightness profiles, and to include nightmode settings (enabled by ChainFire3D or Cyanogenmod's render fx) as part of the brightness profile.
Needs root.
Public domain, source code available. In Market (search for RootDim).
Now in Market (free, no ads).
I just uploaded version 1.10, which restores low brightness settings after the screen is turned off and back on (the OS normally was restoring its brighter screen).
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
bobtentpeg said:
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
Click to expand...
Click to collapse
I assume this is when you use the other lights option to toggle these lights, or when you restore a profile, right?
In version 1.11 (just uploaded), I no longer restore other lights when a profile is loaded--this should help with your problem, as long as you don't touch the other lights. Eventually, I may add an option to choose which lights get restored from a profile.
I originally made SuperDim for setting very low backlight settings on LCDs, and so I made it not work on non-LCD screens (e.g., OLED). But I've since realized that the profile feature might be useful for non-LCD users as well, so I've released version 1.20 that supports non-LCD screens. It's in Market. While I was at it, I cleaned up the code a little, made it more javaish (I'm new to java).
My MyTouch 4G just seems to turn the screen off totally if i go below 20 brightness, it dims but then shuts off.
Doesn't work at all with Dell Streak 5
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Awesome, thanks for the Advise!
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Screen filter merely adds a black semi-transparent overlay across the screen, making it look dimmer.
This app adjusts the backlight, which means darker black levels on the screen.
Frosty666 said:
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
Click to expand...
Click to collapse
My eyes don't care. +1 Screen Filter
lownox said:
My eyes don't care. +1 Screen Filter
Click to expand...
Click to collapse
Your eyes would probably care if you were doing amateur astronomy under a dark sky (which is the primary purpose for SuperDim). Screen Filter doesn't turn down the backlight, and on a lot of devices there is enough backlight leaking through even completely black pixels to damage night vision. You can try this experiment. Turn a backlit device to a completely black screen (maybe view a black jpg) and take it to a completely dark room. Let your eyes dark adapt. The "black" screen will in fact probably be quite grey. (If it's really black, that's probably because you have an OLED device.)
When I do amateur astronomy, I am not infrequently looking to see objects way dimmer than backlit black pixels.
I'd like to do something about the screen turning completely off issue.
To that end, I need people to do some experiments for me, and I will be very grateful (I'll also give a free full version of Force2SD as compensation for the first couple of experimenters, if you want it--just email me). The first experiment is this. Download SuperDim 1.22, now up in the Market. Press the menu key, and choose "Turn on safe mode" (you can tell safe mode is on, because next time you pull up the menu, it says "Turn off safe mode"). Now, turn brightness down to 10. Does your screen turn off?
I should warn that very low brightness levels can be very low indeed. For instance, if I am outdoors on a sunny day, I have trouble telling the difference between brightness 4 and off. So you need to be in a dark area--I recommend a room without windows and with the lights off.
If the screen does not turn off at 10, turn it down to 5, and then 1. Let me know if it ever turns off.
I am guessing that in safe mode, it doesn't turn off at all.
What safe mode does is it makes very low brightness settings not persist. So if you are in safe mode and leave SuperDim, you lose your low brightness setting.
I'd also appreciate it if people who can normally turn their brightness down to 1 could do some experiments with safe mode. Specifically, I'd like to know if moving the slider to 1 in safe mode has the same effect on screen brightness as moving the slider to 1 in non-safe mode has. (Again, if you're one of the first few experimenters and want a free copy of Force2SD, email me.)
On my Archos 43, brightness 1 is very, very dim, but the screen is still on. And I can't tell the difference between safe mode and non-safe mode, except that in safe mode, the settings don't persist after I leave SuperDim.
Tried this app on my desire HD.
Great idea, but when I reach 10 and below, the backlight doesn't get lower.
If I use the adb method (don't remember the command), I can set the backlight manually all the way down to 0.
There is no difference with or without safe mode on.
inspire 4g with coredroid V7.0 doesnt work
elmanortega said:
inspire 4g with coredroid V7.0 doesnt work
Click to expand...
Click to collapse
What happens? And does safe mode work?
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
kamranh3 said:
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
Click to expand...
Click to collapse
I found a bug. In fact, the bug is such that I have no idea how it was managing to work on my device at all! In any case, I think I fixed it. Try 1.23 (should be in Market or here) and see if it does the job. If not, I have some more ideas.
Please note, you do these at your own risk, I am not responsible for anything breaking!!
Set your wallpaper to an all black wallpaper, this will save your battery some-what. Turn on adaptive brightness THEN turn your screen brightness all the way down. Turn on battery saver. Enable "DND" and set it to complete silence, you'll still get calls and texts. If you're rooted and want to change your display dentisy, do this:
*needs to be rooted*
Download build prop editor from the play store, grant permissions with SuperSU, edit, go to the bottom of the list and add this:
ro.sf.lcd_density=380
Save the file, close the app, open the app and reboot. Congratulations, your DPI has now been changed.
Go in to your sound and disable all sound in other, change your ring tone and notification to none. Disable sound for media, notification and ring tone.
Enable developer options, turn ON HW overlay. disable all animations to 0. Show all ANR's and background processes to no background apps.
Download BBS FROM HERE (XDA) and wakelock detector, you'll see what is consuming your battery. AMPERE will also tell you your charge rate and discharge rate, very good app.
Go in to your apps, disable everything you're not going to use, movies, music etc. BLOCK notifications for apps you don't want. change your permissions on your apps if you wish to do so.
You can check your battery's capacity with "kernel auditor" and you can underclock your CPU thus saving battery and it doesn't really effect performance.
Turn off vibration, disable account auto syncing, disable now on tap, go in to your Google settings, security and disable all, phone search and disable all. Date and time, disable automatic date and time, set to NOT 24 hours time display.
If you want to root:
Boot TWRP from here:
https://twrp.me/devices/motorolamotog2016.html
Make sure you have your Motorola drivers if you're on windows and fastboot, if you're on Linux (which I am) do this:
"sudo apt-get install android-tools-adb android-tools-fastboot"
You have developer options enabled, enable USB debugging and accept on your phone for auth.
BOOT in to twrp:
adb reboot bootloader
fastboot boot yourdir/twrp-3.0.2-0-athene.img
Wipe your phone, MAKE SURE to have a backup. Create your SuperSU file:
TWRP > Advanced > Terminal and type: "echo "SYSTEMLESS=true" > /data/.supersu" HIT enter, go to: TWRP > Advanced > File Manager and look for your SuperSU file.
Install your SuperSU Stable from here:
https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Make sure it's on your SDCARD. install. Nice, you're rooted.
If you want to install A CUSTOM kernel, download here:
http://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
MAKE SURE it's on your SD card, install. nice.
*!!you will lose your official status!!*
Post your tips and tricks here.
*ROOTING is systemless, you will not lost your official status. IF you install the kernel, your official status will BE GONE!!!!*
bwoiisc0tty said:
Set your wallpaper to an all black wallpaper, this will save your battery some-what. Turn on adaptive brightness THEN turn your screen brightness all the way down.
Click to expand...
Click to collapse
I disagree with this. We have an IPS LCD display. Which means that keeping a black screen INCREASES power consumption, because of the way LCD screens work. This would work wonders for an LED screen, but for our phone, keep the colour towards the whiter sides & keep the brightness low.
Buying 15000rs (225$) and you are telling us to disable all the features and not to use..Should I laugh or ignore ? This is not the right way to tell tricks & tips.
#chill
When i try to change my DPI to 380 or 400....
It breaks my camera...
Camera becomes non-responsive, en doesn't give an image anymore....
Only way to fix it again is to do a restore of my ROM.
coolhead said:
When i try to change my DPI to 380 or 400....
It breaks my camera...
Camera becomes non-responsive, en doesn't give an image anymore....
Only way to fix it again is to do a restore of my ROM.
Click to expand...
Click to collapse
Working fine with 400dpi, non rooted device
Sent from my Moto G (4) using XDA-Developers mobile app
I agree that a black background helps on the MotoX 1st gen that has OLED screen, but will not do anything for our LCD screen.
As for keeping at the minimum the apps that run in background, that's good advice. Everyone can decide if those aps are important to them.
While I had my my AT&T S3 Frontier LTE watch set to "Always On" I was getting something like a "Screensaver" which consisted of just the hour and minutes hands in white on a black background. It came on after the watch display dimmed and after the display time out. This happened while using the Chronograph+ (default) watch face. It was a distinctive + useful screen face that probably saved me some battery life. Now the displays dims after the time out and then it turns completely off (black). After I power cycled the S3 yesterday, I stopped getting this "Screensaver" and can't find the settings combination that will get this "screensaver" back. Does anyone know what I'm talking about and how to get it back?
tamanaco said:
While I had my my AT&T S3 Frontier LTE watch set to "Always On" I was getting something like a "Screensaver" which consisted of just the hour and minutes hands in white on a black background. It came on after the watch display dimmed and after the display time out. This happened while using the Chronograph+ (default) watch face. It was a distinctive + useful screen face that probably saved me some battery life. Now the displays dims after the time out and then it turns completely off (black). After I power cycled the S3 yesterday, I stopped getting this "Screensaver" and can't find the settings combination that will get this "screensaver" back. Does anyone know what I'm talking about and how to get it back?
Click to expand...
Click to collapse
Enable Settings -> Style -> Watch Always On
tamanaco said:
While I had my my AT&T S3 Frontier LTE watch set to "Always On" I was getting something like a "Screensaver" which consisted of just the hour and minutes hands in white on a black background. It came on after the watch display dimmed and after the display time out. This happened while using the Chronograph+ (default) watch face. It was a distinctive + useful screen face that probably saved me some battery life. Now the displays dims after the time out and then it turns completely off (black). After I power cycled the S3 yesterday, I stopped getting this "Screensaver" and can't find the settings combination that will get this "screensaver" back. Does anyone know what I'm talking about and how to get it back?
Click to expand...
Click to collapse
I don't think I've really ever used the default faces. I know in a lot of the Watchmaker faces you can get a toned down face with maybe just the numbers and hands glowing when using AOD mode but I don't know about the default faces. In display settings there's a setting for auto low brightness that may affect that.
10urshin said:
Enable Settings -> Style -> Watch Always On
Click to expand...
Click to collapse
If you read the first sentence of my post you'd see that I'm already using this setting.
tamanaco said:
If you read the first sentence of my post you'd see that I'm already using this setting.
Click to expand...
Click to collapse
Yea i have read it. Not just first sentence but I also read the whole thing, you must admit it is not really making much sense. "Screensaver"? There is no such thing on this watch, only AOD and "Now the displays dims after the time out and then it turns completely off (black)." this sentence perfectly describes the AOD off behavior. So i thought it worth mentioning.
Only other thing that comes to my mind is default analog AOD watchface(attachment) which is something watch shows if the current watchface does not support AOD. But since you stated that you were getting your "screensaver" on Chronograph+ which supports AOD, it doesn't really make sense either.
Anyway hope you'll find your answer.
I also saw this "screensaver" mode in a review video somewhere, but I have not been able to locate it again. Once I find it, I'll post a screenshot of it.
tamanaco said:
While I had my my AT&T S3 Frontier LTE watch set to "Always On" I was getting something like a "Screensaver" which consisted of just the hour and minutes hands in white on a black background. It came on after the watch display dimmed and after the display time out. This happened while using the Chronograph+ (default) watch face. It was a distinctive + useful screen face that probably saved me some battery life. Now the displays dims after the time out and then it turns completely off (black). After I power cycled the S3 yesterday, I stopped getting this "Screensaver" and can't find the settings combination that will get this "screensaver" back. Does anyone know what I'm talking about and how to get it back?
Click to expand...
Click to collapse
Thinking more about it, I don't think the AOD is even supposed to remain on all the time. That has been a major complaint, the AOD mode not being actually AOD. What you're experiencing now isn't normal and there should be no setting to change that. If you want to set up the watch again, you might try resetting it. That's assuming you've already tried just restarting it.
What comes to my mind with "Watch always on" (or "Always On Display", AOD) and having screen completely black is if watch thought at some point that you weren`t wearing it - only in that case should the screen go completely black with AOD set, otherwise it should, well, keep "always on display", that`s the point of the setting
When you take the watch off your hand, then it goes blank even though AOD setting is still active - watch is "playing it smart" to preserve battery life in case where you`re not actively using it.
But, it`s possible for the watch to (wrongly) think that you`re not wearing it even when you do, thus turning the screen off when it should otherwise be in AOD mode (as set). For example, it can happen when your wrist band is a bit loose so the heart rate sensor has issues reading your pulse, or when the heart rate sensor itself is smudgy or otherwise blocked to make the valid reading - some people with tattoos reported that AOD doesn`t really work for them, having the screen constantly turning off (tattoo effectively confusing the heart rate sensor reading).
This is especially troublesome if you`re using "Samsung Pay", where the watch asks for you PIN in order to unlock itself every-single-time, as it`s thinking that you didn`t wear it in the meantime...
All this said, from what you described, it looks like AOD doesn`t work for you at all anymore, as what you seem to call "Screensaver" is actually AOD - a dimmed and more simple version of the watch, whose main purpose is to spare the battery while still providing a bit more realistic feel, having the watchface shown all the time.
There is additional "trick" to trigger AOD mode (once you have the setting configured), besides simply waiting for some (configured) time to pass by - just cover the watch with your palm for a few seconds, and it should fall back to AOD mode. If the screen goes blank instead, you might have an issue with the watch.
It would be good to have some default watchface in use when you`re trying AOD (like mentioned Chronograph+), just to opt out a possibly "broken" third-party watchface, and you could also check if "S Health" heart-rate reading works for you, starting a heart-rate readout manually (you can use a widget for that as well).
If the issue is still there, you may try restarting the watch again, or eventually soft (or factory) resetting might be a thing to go for, too, though you`ll have to setup the watch again, as already mentioned.
I have seen the exact same behavior. My AOD will suddenly become black and white, while normally it is full color, and any app icons that are usually on the AOD disappear. When the watch is active (by turning wrist or touching the screen), the full color face returns and looks normal - it is only the AOD that is always B&W. The difference for me is that I don't like it and I would like to figure out how to get it to stop happening.
I've had the watch for about 2 months and it has happened to me 3 times with different watch faces. It lasts from several hours to more than a day. I have changed every related face setting, changed faces, changed face settings, AOD settings, restarted, and reset the watch completely (and restore), but it still happens. The only thing that I've noticed may help (may be coincidence) is that it will stay indefinitely until I power cycle the watch. After restarting, the AOD remains black and white for a few hours and then suddenly the color AOD will return. Next time it happens I will take a pic.
I'm actually somewhat relieved that I'm not the only one who has seen this because my googling revealed next to nothing. I don't know if I would call this a screensaver, but it would be nice to be able to control it.
annulation said:
I'm actually somewhat relieved that I'm not the only one who has seen this because my googling revealed next to nothing. I don't know if I would call this a screensaver, but it would be nice to be able to control it.
Click to expand...
Click to collapse
I knew I was not seeing things... please take a picture if it happens again, so that we can have a reference image. I'll do the same if it happens to me again. In certain situations... I actually like just having the hour and minute hands in "brightish" white on black background. Like you, I would also like to control it. I thought it was a "screensaver-like" feature as the watch face turns mostly black. But as you say, it might be a glitch... it has not happened to me since I last power cycled the S3.
Low Color AOD
I finally figured it out.
The behavior is called "Low Color AOD" and "High Color AOD". It is controllable by swiping from the right side of the screen near 5 o'clock straight up. This consistently toggles it for me, and a popup message shows a message saying either "Low Color AOD" or "High Color AOD". See pics attached (sorry, don't know how to rotate them).
Pics:
1. Low Color AOD
2. High Color AOD
3. popup message Low Color AOD
4. popup message High Color AOD
Only some faces support this behavior. For me, "Low Color AOD" always means monochrome B&W and no app icons.
PS - this face is called "Stylish Set" and the creator gives free coupons for it if you email him. It is one of the few faces I've found that shows day/date, with temperature and battery.
As mentioned, the function described is dependent on the functionality of each watch face independent of the watch itself. If a given watch face supports it, it can be accessed. The "always on" function also depends on the capabilities of each watch face. Some have customized always on displays, and some do not (generic). The watch will go black if it senses it is not against the skin (the sensor on the back). This will also cause the watch to lock again and require the security code to re-activate. If a band is too loose, the watch can falsely think it has been taken off. The time that the watch face itself is on can be extended with an app called "Flaunt" available from the Galaxy app store. It can extend the original watch face active time to 30 minutes. It can then be re-activated to extend for other 30 minute time periods. Of course it does impact the battery life.
Hello, new user here, I got a Watch 2 Sport after a few years with a LG G Watch R.
I was surprised to see that the screen seems to have 4 modes, instead of the canonical 2 modes (ambient mode and interactive mode): after a few seconds of inactivity in interactive mode, for a second the screen dims while still in interactive mode, then transitions to ambient mode, while still being dimmed. When woken up again, it "undims" itself while still in ambient mode for a second, then transitions into interactive mode. Picture explanation: https://i.imgur.com/0mUcIyb.jpg
The main problem I have with this is that the "dimmed ambient mode" is really dim, and basically makes the ambient mode useless except in very dark environments... Does anyone know of a way to disable the dimming or, at least, set the brightness level of this dimmed mode? It seems to be unaffected by the screen brightness settings...
I use a custom watch face, so even if the solution involves changing some code in the watch face it would still be very welcome; however, I have not found any mention of this "feature" in the android wear documentation...
arklumpus said:
Hello, new user here, I got a Watch 2 Sport after a few years with a LG G Watch R.
I was surprised to see that the screen seems to have 4 modes, instead of the canonical 2 modes (ambient mode and interactive mode): after a few seconds of inactivity in interactive mode, for a second the screen dims while still in interactive mode, then transitions to ambient mode, while still being dimmed. When woken up again, it "undims" itself while still in ambient mode for a second, then transitions into interactive mode. Picture explanation: https://i.imgur.com/0mUcIyb.jpg
The main problem I have with this is that the "dimmed ambient mode" is really dim, and basically makes the ambient mode useless except in very dark environments... Does anyone know of a way to disable the dimming or, at least, set the brightness level of this dimmed mode? It seems to be unaffected by the screen brightness settings...
I use a custom watch face, so even if the solution involves changing some code in the watch face it would still be very welcome; however, I have not found any mention of this "feature" in the android wear documentation...
Click to expand...
Click to collapse
which custom face app do you use? i've used watchmaker, but that doesn't seem to dim - just pauses the second hand. thus, I'm stuck using the stock watch faces, as the dimmed look is classier/more practical, but the regular faces are not very good.
I don't use anything like watchmaker, I use a watch face that I developed from scratch in Android Studio... By the way, I tried installing Watchmaker and I tried one of the free watch faces, and it does, indeed, dim (https://i.imgur.com/q3pGRWi.jpg), so I'm not sure what you mean.
arklumpus said:
I don't use anything like watchmaker, I use a watch face that I developed from scratch in Android Studio... By the way, I tried installing Watchmaker and I tried one of the free watch faces, and it does, indeed, dim (https://i.imgur.com/q3pGRWi.jpg), so I'm not sure what you mean.
Click to expand...
Click to collapse
i'll send some screenshots later this week. but I'd like the watchmaker face to dim like stock.
arklumpus said:
I don't use anything like watchmaker, I use a watch face that I developed from scratch in Android Studio... By the way, I tried installing Watchmaker and I tried one of the free watch faces, and it does, indeed, dim (https://i.imgur.com/q3pGRWi.jpg), so I'm not sure what you mean.
Click to expand...
Click to collapse
so yes, technically, you are correct - it does dim. I guess I meant for it to transition to ambient mode like stock. does the one that you developed to that? i've been looking for a watch face like stock, but with a more legible calendar widget.
I ran diffchecker on the adb system settings output with force 90hz enabled and disabled, and found the setting that switches when you activate "force 90Hz" in the developer settings: "min_refresh_rate=90.0". If you're rooted you can set that with Tasker based on whatever conditions you want, using the shell command function. The code to activate it is "settings put global min_refresh_rate 90.0", and the code to deactivate is "settings delete global min_refresh_rate" (both need "use root" ticked). I've been testing having it triggered on my phone when I'm connected to my home wifi and ambient light is < 15. The home wifi condition is so I don't run into big battery drains when I'm out late at night, and I'm using ambient light rather than screen brightness because as someone pointed out in a Reddit thread, Smooth Display will still run under 75% screen brightness under certain ambient lighting conditions. So far, battery is definitely taking a hit, but it's not a big deal when I'm home and chargers are in easy reach.
tardis_42 said:
I ran diffchecker on the adb system settings output with force 90hz enabled and disabled, and found the setting that switches when you activate "force 90Hz" in the developer settings: "min_refresh_rate=90.0". If you're rooted you can set that with Tasker based on whatever conditions you want, using the shell command function. The code to activate it is "settings put global min_refresh_rate 90.0", and the code to deactivate is "settings delete global min_refresh_rate" (both need "use root" ticked). I've been testing having it triggered on my phone when I'm connected to my home wifi and ambient light is < 15. The home wifi condition is so I don't run into big battery drains when I'm out late at night, and I'm using ambient light rather than screen brightness because as someone pointed out in a Reddit thread, Smooth Display will still run under 75% screen brightness under certain ambient lighting conditions. So far, battery is definitely taking a hit, but it's not a big deal when I'm home and chargers are in easy reach.
Click to expand...
Click to collapse
This is handy, thank you! Quick question though, how do you run an adb system settings output to see the difference when you switch other settings?
TheBobMiller said:
This is handy, thank you! Quick question though, how do you run an adb system settings output to see the difference when you switch other settings?
Click to expand...
Click to collapse
Assuming you have adb running and connecting to your phone fine already, it's pretty easy. Enter adb shell, then run three commands: "settings list global", "settings list system", and "settings list secure". Open up diffchecker.com and copy the results from the shell into one side. Change whatever setting you're interested in on your phone, then run these commands again and copy the output into the other side of the diffchecker window. It'll show you anywhere the output has changed, and that should be your setting - although there might be a couple other differences flagged, eg I think system uptime is in there somewhere.
tardis_42 said:
Assuming you have adb running and connecting to your phone fine already, it's pretty easy. Enter adb shell, then run three commands: "settings list global", "settings list system", and "settings list secure". Open up diffchecker.com and copy the results from the shell into one side. Change whatever setting you're interested in on your phone, then run these commands again and copy the output into the other side of the diffchecker window. It'll show you anywhere the output has changed, and that should be your setting - although there might be a couple other differences flagged, eg I think system uptime is in there somewhere.
Click to expand...
Click to collapse
Thank you so much! I'm not sure how I never knew this but being an avid Tasker user, I should've known this by now. This is gonna really come in so useful for me! Thank you!
How did you find this script <min_refresh_rate> ? Do you max to lock the maximum fps would be <max_refresh_rate>?
Small change to the command; in Android 11 beta 2.5, you have to use "settings put system min_refresh_rate 90.0". Changing the global flag does nothing to the frame rate anymore but changing the system value can force 90hz, even if you have smooth display turned off.
Trixter313 said:
Small change to the command; in Android 11 beta 2.5, you have to use "settings put system min_refresh_rate 90.0". Changing the global flag does nothing to the frame rate anymore but changing the system value can force 90hz, even if you have smooth display turned off.
Click to expand...
Click to collapse
Thank you!
I have been looking for this since beta 2 came out ?