Couple of things that really bug me on miui, is the inability to change colour sheme with reading mode on and why battery saver forgets that I had 120hz on.
My usual setup is setting color scheme to advanced, reading mode on, battey saver mode in the night,
Every morning I need to,
Turn off reading mode,
set color scheme to auto, and manually turn back on refresh rate to 120hz (for some reason when battey saver is turned off it doesn't go back to the original settings)
Miui doesn't seem to have the capability to do this at the flick of a button let alone scheduled(apart from the battery saver),
Was looking into apps like Automate/Tasker for the same,
Can't seem to find direct settings in these apps to toggle these oddly specific settings for me( reading mode, color scheme, refresh rate)
I figure the only way to go about it is using some scheduling apps to trigger a shell/adb command,
Are there any guides/docs available for what adb commands/shell utilities are available to alter these miui specific settings programmatically?
Alternatively any other approach to make this easier?
Thanks !
[email protected]� said:
Couple of things that really bug me on miui, is the inability to change colour sheme with reading mode on and why battery saver forgets that I had 120hz on.
My usual setup is setting color scheme to advanced, reading mode on, battey saver mode in the night,
Every morning I need to,
Turn off reading mode,
set color scheme to auto, and manually turn back on refresh rate to 120hz (for some reason when battey saver is turned off it doesn't go back to the original settings)
Miui doesn't seem to have the capability to do this at the flick of a button let alone scheduled(apart from the battery saver),
Was looking into apps like Automate/Tasker for the same,
Can't seem to find direct settings in these apps to toggle these oddly specific settings for me( reading mode, color scheme, refresh rate)
I figure the only way to go about it is using some scheduling apps to trigger a shell/adb command,
Are there any guides/docs available for what adb commands/shell utilities are available to alter these miui specific settings programmatically?
Alternatively any other approach to make this easier?
Thanks !
Click to expand...
Click to collapse
Also in my F3 with stock 12.5.3. I can't change the color scheme when reading mode is on.
Instead I verified that the 120hz frequency is set to 60hz if the energy saving is activated and returns to 120hz if it is deactivated (automatically);
It works well even if I schedule automatic activation and deactivation.
It works well even if active or I program the automatic activation of the reading mode.
I assume it's a problem with your software that I can't give a solution to. I am sorry.
Related
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
brian117 said:
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
Click to expand...
Click to collapse
That's one of the main differences between Malaysk and DSA. DSA told me look out the window and figure it's night time. Secondly he told me to go to max at least two or even three times in a row. It will then STAY 100% bright till you reboot.
halloj said:
That's one of the main differences between Malaysk and DSA. DSA told me look out the window and figure it's night time. Secondly he told me to go to max at least two or even three times in a row. It will then STAY 100% bright till you reboot.
Click to expand...
Click to collapse
Whoa, thanks for the quick reply and useful information. Is there absolutely no way to bypass having to do that method? As that would be a chore doing it multiple times after exiting and entering my car multiple times a day. Maybe a simple build.prop edit possibly? Just naming ideas.
There is... Mtc manager has settings in it for brightness settings due to time. You can turn it off there. This didn't work for me so I went another route with changing some file. Its all detailed in the thread as to how.
miffymiffy said:
There is... Mtc manager has settings in it for brightness settings due to time. You can turn it off there. This didn't work for me so I went another route with changing some file. Its all detailed in the thread as to how.
Click to expand...
Click to collapse
You could disable brightness control entirely or just alter the brightness levels.
It's in file /system/etc/install-recovery.sh - at its end, comment out all 14 lines after comment line reading "#Brightness control (last, always)", in order to disable the algorithm.
OR, change line reading "nb=5 ### Night Brightness ###" to a different value for the night brightness (nb), eventually equal to day brightness (db, on next line).
Use a root explorer, or edit a copy of file on PC (with notepad+ if on Windows) and copy it back - with a root explorer or manually, if you can. File mode: 0755, owner & group: root:root.
If script /system/etc/install-recovery.sh gets "damaged", you must reinstall the firmware, but with NO wipe all, so fairly quickly and no loss of settings and apps.
Editing of script could also be done with @devilsoft app (with a name I can't recall).
brian117 said:
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
Click to expand...
Click to collapse
Hi @brian117 !
In fact, there is a simple fix I found lately.
You need to enter factory settings first.
Go to SETTINGS -> Factory settings -> enter code: m123456
When you're there, go to last page, and tick the "Key light" option.
Now press "Apply" and "Exit". Confirm reboot.
It worked with me - now the screen has full brightness regardless of the car lights on or off (in Poland we need to have the lights on whole day, as well). Now you can use a software dimming, like MTC to auto dimm the screen according to actual day time. I did this. Works like a charm! (I set dimming after sunset to 75% brightness)
Hi guys
I was wondering if any of you found a way to automate night mode on our lenovo p2 nougat?
it's called brightness protection under Settings -> display
I want to enable it when the sun goes down and disable it when it's morning., like how similar night mode apps work (cf.lumen, lux etc)
currently I tend to forget disabling the option so the screen stays reddish.
I don't have root but know how to work abd if needed
Hi,
I was also struggling with this till I found out, go to settings, features, smart scenes and create one say for sleeping, you can adjust the time interval and with the plus button you can add a task for brightness protection.
Can anyone tell me if there is a built-in "night mode" on the 2XL? Coming from an S7 Edge there was an option in the settings that at a preset time the always on display would switch to a very minimal display that was only across one edge of the screen, it made for a nice alarm clock without being too bright overnight, then at a preset time it would revert to its normal settings of a large clock, displaying notifications, calendar etc.
I know I could use something like Alarm Clock Plus, but am trying to avoid having to install an app if there is built in functionality to do the same thing.
Thanks.
no
Short and sweet. Thanks. There are definitely a couple things Google could learn from Samsung on just small things like that though.
yep. but in the dark the ambient display is not bright so dont be afraid of burning your eyes.
The closest thing I have to what you are asking is using Tasker to turn off AOD when DND is enabled.
I have a profile to enable DND overnight, which in turn disables AOD.
rickysidhu_ said:
The closest thing I have to what you are asking is using Tasker to turn off AOD when DND is enabled.
I have a profile to enable DND overnight, which in turn disables AOD.
Click to expand...
Click to collapse
That's not a bad idea, I paid for Tasker long ago (run it on my Nexus 7 in the car) so it would just be a case of setting it up on the Pixel.
There is a clock screensaver for when phone is plugged. I don't use always on display but want to be able to see clock without touching phone. You can adjust tue brightness of it via nightmode switch. Under display - screensaver h clock ...
naiku said:
That's not a bad idea, I paid for Tasker long ago (run it on my Nexus 7 in the car) so it would just be a case of setting it up on the Pixel.
Click to expand...
Click to collapse
In case you were wanting to actually implement this, I double checked how I did it, and it's with the paid plugin "AutoTools".
I turn the AOD on when I'm connected to BT in my car since it's on a mount and also off at 10pm. If the task runs when your screen is off you do need to turn your screen on for it to take effect. So I check if my screen is off. If it is I have it turn on and off briefly.
trigger always on using tasker auto tools
New Task
Plugin -> Autotools -> Secure Settings
Configure
Custom Setting
Setting Type = "Secure"
Name = "doze_always_on"
Input Type = "Int"
Value = "0" OFF/ "1" ON
I've done some testing and I can't tell if it even works...not sure if a reboot is required or what each time...maybe someone else can add to this.
The below article might be fine for a stock Rom, but doesn't seem to work on Nitrogen with a kernel/magisk.
You need to have ambient brightness turned on though, otherwise, the default values are used and these overrides don't work.
https://www.xda-developers.com/customize-google-pixel-2-always-on-display-brightness/
If you hit the battery saver before you go to bed that will deactivate always on.
Turn battery saver off in the morning and always on will be back on.
Should solve your problem!
Or just flip the screen over. That deactivates it as well.
Lausterboy said:
If you hit the battery saver before you go to bed that will deactivate always on.
Turn battery saver off in the morning and always on will be back on.
Should solve your problem!
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
I just lay a business card over the sensors, since my thin case has no lip!
The battery saver mode page allows for tweaking four settings:
Max brightness
Always-on-display
Disable vibration
Restrict background data
Now, if you disable(!) all of those you still receive minor savings, at least from what the prediction overview (listing all available battery modes) shows. First question: What remains "tweaked" internally to allow for that?
Furthermore, from enabling the items one by one, adjusting max brightness offers a large impact on the predicted runtime. That's no surprise. However, I would have thought that disabling the always-on-display leads to more savings but, looking at the predicted time, it actually doesn't. The impact is close to zero.
Vibration has a minor impact, more than AOD, while a HUGE gain of additional standby hours can be achieved by selecting the "Restrict background data" option. I wonder how that turns out in the everyday use but I think that, if one app would suffer, I would just exclude it and leave the rest in the "saving" position.
Concerning the (assumed) internal changes, I've logged the CPU frequency for a while with the extended battery mode on and off and can't see that throttling is active like I saw with other phones and their battery saver modes, so that's a nice trait. The chipset still clocks to max when needed, same as with the extended mode off.
How are your experiences with that mode? Does it offer more runtime (namely: are the predictions somehow in line with reality?) or is it leading to added lag or other problems? Currently, it seems like taking a lock at that background data option is worth a shot.
BasicallyCP said:
The battery saver mode page allows for tweaking four settings:
Max brightness
Always-on-display
Disable vibration
Restrict background data
Now, if you disable(!) all of those you still receive minor savings, at least from what the prediction overview (listing all available battery modes) shows. First question: What remains "tweaked" internally to allow for that?
Furthermore, from enabling the items one by one, adjusting max brightness offers a large impact on the predicted runtime. That's no surprise. However, I would have thought that disabling the always-on-display leads to more savings but, looking at the predicted time, it actually doesn't. The impact is close to zero.
Vibration has a minor impact, more than AOD, while a HUGE gain of additional standby hours can be achieved by selecting the "Restrict background data" option. I wonder how that turns out in the everyday use but I think that, if one app would suffer, I would just exclude it and leave the rest in the "saving" position.
Concerning the (assumed) internal changes, I've logged the CPU frequency for a while with the extended battery mode on and off and can't see that throttling is active like I saw with other phones and their battery saver modes, so that's a nice trait. The chipset still clocks to max when needed, same as with the extended mode off.
How are your experiences with that mode? Does it offer more runtime (namely: are the predictions somehow in line with reality?) or is it leading to added lag or other problems? Currently, it seems like taking a lock at that background data option is worth a shot.
Click to expand...
Click to collapse
Only thing I've noticed is when I have my phone set to Extended and I've set Max Brightness to 80%. However, I've seen my Brightness go over 80% on Auto especially when I was outdoors (saw it hit 100% and Boosted). Under Manual Brightness, I can have it go to 100% too. So that 80% is misleading?
Good find. I was wondering too since the prediction page instantly applies a gain in standby hours (and a significant one at that) by just enabling the "max brightness" feature. Since it can not know when or for how long the display will be on and what range the "auto" feature will use in a given situation, it seems like a very optimistic value, especially if you just use a limit of 95% for example.
But regarding your question, it's indeed strange to see "auto" exceeding the max brightness limit. I mean, the limit is there for the auto mode only. Might be a bug, unless we struggle to see the logic behind acting like that.
Personally, I would leave max brightness alone since it's more useful to have the display ramp up to max in order to actually see something when needed. If "auto" generally sets up the display as being too bright, one can still adjust the slider (even in auto mode) to tune the point of optimal brightness. I think it acts as an offset to the actual (internal) value the automatic comes up with. At least, that's how I perceived the feature on this and other phones so far.
Before Do Not Disturb even existed I used quite a few apps (llama, Phone Profiles Plus, Sound Profile) to achieve sound management over night. Unfortunately at some points in time some of these failed to work due to more aggressive battery management of my newer phones or after software updates that broke things.
However now I feel that DND provides more options and is a more elegant solution...if it would do what I want.
I would like to turn it *manually* on, go to sleep, and have it turned off at 8:00 AM. Anyone found a way to do that?
You can set a schedule to turn on and off automatically. You can also turn it on manually then set it to turn off automatically. You select how many hours you want it on.