The display size option within Display inside Settings, at its smallest setting, is not small enough for my liking. The display is not being used efficiently with such a high density setting. Also, this setting seems to change UI elements independently of the "wm density command."
Using ADB since I am not rooted, and as I have done on many phones in the past, I send "adb shell wm density ###" where ### is my preferred setting (340 looks good to me). Keep in mind this display will use lower numbers to display the same amount of content as a 1440p display. 360 on this resolution seems to match 580 on my Pixel XL.
The problem is, after a reboot, the phone resets to its standard DPI setting, and I can only change this with access to a computer. This seems ridiculous - is there something I'm missing here, or a way to prevent it from changing on startup? As I said, if you set display size to small, normal, or large, some UI elements are actually sized differently even at the same DPI setting after you manually change it... most noticeably, the navigation button sizes are noticeably different, and I don't think I've ever noticed this before.
Still haven't figured out how to make it stick after a reboot, but in developer options, "Smallest width" is configurable (### dp) which appears to do the same thing, but the bigger the number, the smaller the UI. The bonus here is you can change it without needing ADB and a computer. It still resets after a reboot which is ridiculous, but at least you can change it any time like I mentioned.
Thank you man for this Info, was searching for the same thing on PD Mate9 , helped me a lot, maybe we find something to keep it small in future...after reboot
Related
It is my understanding that AMOLED screens consume no power for pixels that are set to black. It is also my understanding that phones are being released without a notification light on them (such as the Nexus S). It is also my understanding that Android phones expect to spend some time in the Idle state and do various update tasks, reduce overall power consumption etc. while in such a state so not allowing them to ever idle would not be a solution for any problem.
Assuming my above understanding is correct, how difficult would it be to make a change to Android such that notification information could be displayed on-screen in a few pixels (say, in the center of the screen) so that the majority of the screen is consuming no power (black pixels) but you still have a few colored pixels for notifications. These pixels could be set to black when there are no notifications so that the small power they do consume is only used when a notification needs attention.
A step beyond this would be to create an interface that would allow other developers to create various themed idle screens that would be customizable by the user, or at least by a variety of developers. This may be as simple as changing the colors, rate of flashing (if any), number of notification pixels used, etc. Also, different apps could notify in different parts of the screen to give further feedback as to what needs attention without having to touch your phone (just a quick glance).
My background is that of a C++ Software developer who has dabbled a bit in Android, writing various small apps for it. I have never worked with the OS itself before so I am uncertain if this would be a trivial task or a very complex one. Perhaps it is even something that could be done without any OS changes (though to my understanding this is not the case).
Check this thread/app: http://forum.xda-developers.com/showthread.php?t=730692
Sent from my GT-I9000 using XDA App
OK I was going through settings like I occasionally do since I sometimes find something interesting and I did today under the screen settings and the mode selection.
There are three settings:
Dynamic
Standard
Movie
The default I'm pretty sure (since I can't remember after messing with it) was standard. I'm curious as to what dynamic is. Movie seems fairly obvious to me since it adds a slight yellow hue to the screen. Dynamic seems to brighten colors it seems but why is it referred to as dynamic.
I haven't seen the screen adjust itself or anything upon using it either.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1229470
From what I've observed, dynamic gives out brighter and better colors at the expense of battery life. Standard is pretty much "standard". Then movie mode uses the least battery and would not strain your eyes as compared to the other two.
Ah thank you for that!
I customized a luminosity curve for my surface rt, just edit the registry keys.
Download extract and run the attached .reg file and confirm the insertion of the Keys, then reboot the system.
Alert to make a backup of the old keys if you want to restore the previous state.
This change is compatible with all windows 8 but I have tested only on the surface.
Adaptive brightness varies proportionally to the user manual brightness, I suggest to manually adjust the brightness bar to about 20%, if you place the bar at 0 the brightness will be minimal with no automatic adaptation.
Appreciated thanks
New version v2
New improved version.
Try it and tell me if it's okay.
In the zip you will find the normal version and one with more brightness in the dark
I suggest to manually adjust the brightness bar to about 25%
So you have a fix, that's great. But to what? You didn't state what the problem is. Neither did you way what you are doing differently over the default values. Why would me, or anybody else for that matter, want do download this?
Amax said:
So you have a fix, that's great. But to what? You didn't state what the problem is. Neither did you way what you are doing differently over the default values. Why would me, or anybody else for that matter, want do download this?
Click to expand...
Click to collapse
In my surface the luminosity curve does not satisfy me.
The display seemed to have only three levels of brightness, setting an average value (ie on the desk in the room in the morning) adaptivity did not fit values for low-light (night) and lots of light, that is to say the brightness in the dark was not a minimum making it annoying for the view and unnecessary consumption of battery, instead with shaded light levels brightness became easily maximum, with again a waste of battery.
This forced me to move often the brightness bar manually, but now with my calibration does not touch more because it adapts automatically to any light condition.
Also the adaptation of brightness occurred after 3 seconds by the change of light, whereas now changes instantly in 0,1 seconds (100ms).
I like it a lot, just what I was looking for.
I use mostly in low light conditions my surface so it is very useful.
Just one remark: it is too sensitive so it is changing screen brightness very quickly even when I just touching the upper part of the screen and making a little shade on the light sensor...
So I think instead of 1 msec. would be better 3 msec.
Would you please and make a 3. version of the settings with 3 msec.?
Alapar said:
I like it a lot, just what I was looking for.
I use mostly in low light conditions my surface so it is very useful.
Just one remark: it is too sensitive so it is changing screen brightness very quickly even when I just touching the upper part of the screen and making a little shade on the light sensor...
So I think instead of 1 msec. would be better 3 msec.
Would you please and make a 3. version of the settings with 3 msec.?
Click to expand...
Click to collapse
100ms not 1ms! However, this file will change only the time in 300ms
antys86 said:
100ms not 1ms! However, this file will change only the time in 300ms
Click to expand...
Click to collapse
You are right, 100 ms. I was in a hurry. Thanks for the fast response and update
Your v2 seems to be working fine for me. Before applying it I could really tell when my surface was adjusting the screen, after applying it the transitions seems smoother and less abrupt.
I have been looking for documentation about how all of these things really work and the closest thing i could find was this link http://superuser.com/questions/644538/customize-adaptative-brightness-in-windows-8
but they seem to be using a different registry location than what you are and different registry names
regardless your settings seem to work immediately after restarting the sensor service
This just a simple little thing for people that want to fix the GIANT/BLOWN UP resolution when connected to a display (TV or Monitor etc.) there is an app for that lol it's called secondscreen
(https://play.google.com/store/apps/details?id=com.farmerbb.secondscreen.free)
You can change the resolution to whatever you want for your connected display and then revert back to the phones screen resolution when you disconnect pretty much automatically. Change the dpi to around ~180 when your connected display is on also as there is a tablet like ui that looks better imo.
Activate desktop mode in secondscreen for Chrome to have it on for a better internet experience. If you don't use chrome then just turn it on in the settings of the browser of your choice (firefox for example).
All in all, playing/viewing and doing pretty much anything is alot better now I have to say personally. Try it and tell me what you think.
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/