Develop Bugs

CM Automatic Backlight Settings (explained)

Got fed up with the lack information so I did some googling and made a post on my blog.
My Bloggy
If anyone has any good links or info to add that would be greatly appreciated! I'm still personally trying to find my own settings.
The Automatic Backlight settings (CyanogenMod settings-->Display-->Automatic Backlight) allow you to customize how your phone reacts to changes in ambient light measured by the phone. You can control how many light level ranges you want to monitor, and how bright you want the screen, keys, and keyboard buttons to be at each range. Of course you have to enable Automatic Backlight in the normal Android settings first (Display-->Brightness).
In googling around on this I've found a number of different approaches and preferences, and it really is something that is very subjective - enough light for one person at a particular ambient light level is too much for another, and vice versa.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first three settings: Windows length, Reset threshold and Sample interval control the filter conditions. The Windows length is the amount of time for the average figure, while the Sample interval is how long the system waits to take a sample. Personally, I go with larger figures to reduce system load and save battery life.
There are two primary benefits offered by filtering:
1. It can allow you to set up smoother brightness transitions (assuming you also increase the number of custom levels)
2. It can decrease the likelihood of screen flicker in mixed lighting. ( You may find yourself in mixed lighting conditions that straddle two raw brightness levels. Without filtering, these raw levels may cause your screen to repeatedly shift back and forth between two brightness settings. I've found this can easily happen with artificial lighting as it is more directional than natural lighting. Sitting in your office, for example, you may find that simply shifting the angle at which you hold the phone changes the brightness reading.)
Notice that without filtering, the screen brightness jumps back and forth between 70 and 55, which can be very distracting. The filter, on the other hand, maintains a single value for the screen brightness, even under these fluctuating lighting conditions.
Window Length: Filtered value is the average sensor value during this period. Larger values = slow response.
Reset Threshold: There may be times in which you want the screen to respond quickly to changes rather than slowly ramping. Moving from a dark building out in to broad daylight, for example, you don't want to watch your screen slowly brighten over the course of 30 seconds: those are 30 seconds in which your phone may be unreadable. This is where the reset threshold comes in handy. If a raw reading differs from your current average by this amount, the filtered value is immediately reset to the raw value. Finding the right value for your reset threshold allows you the best of both worlds: a screen that gradually changes based on subtle light changes, but responds rapidly to extreme changes.
Sample Interval: Low value can improve accuracy but uses some more CPU.
Allow Light to Decrease: This is a very simple option. If this is checked, your screen brightness will increase and decrease according to your custom levels. If it is unchecked, your screen will brighten as the light sensor reads higher values, but will never darken, even if the sensor detects that you have moved to a very dark area. I'm not quire sure why anyone would want to uncheck this, but maybe I'm missing something.
Decrease Hysteresis: Reduces flicker when decreasing brightness
In conclusion, if you want a screen that responds very rapidly to changes in ambient lighting, possibly at the risk of flickering, decrease your filter window (or disable the filter completely) and increase your sample interval. If you want a screen that never flickers, possibly at the risk of slow responsiveness, increase your window.
Filter A: 10 second window, 2 second interval
Filter B: 20 second window, 2 second interval
Filter C: 30 second window, 2 second interval
Filter D: Same as Filter C, but includes a reset threshold of 2000
*Note how the inclusion of a reset threshold on Filter D allows for immediate responsiveness under extreme light changes while still preserving the gradual shifts at smaller changes.
As for the light sensor levels, you'll have to play with them yourself. Go to a dark area... and adjust the screen level until it's at a brightness that's comfortable for you. Then gradually increase it up to whatever is fine for outside brightness. Near the bottom you can select more levels as well.
As previously said, I mainly want to collaborate and find the best settings for our phone. Any information to add would be great. Thanks.
Sources:
Numerical explanation of the CM7 automatic backlight settings
CyanogenMod Secrets: Custom Automatic Backlight settings

Very detailed explanation, should be pinned and include in the CM wiki if not already done so!
Thanks!
Sent from my Xoom using Tapatalk 2

Thank you so much for the detailed overview. Very well done. Agreed...should be stickied.

How about you post your settings?

Excellent post. Needs to be a sticky.

And for those that are curious these ROMs (likely others) have the same implementation:
-AOKP,
-Gummy,
-Slim,
-???

CMNein said:
And for those that are curious these ROMs (likely others) have the same implementation:
-AOKP,
-Gummy,
-Slim,
-???
Click to expand...
Click to collapse
liquid
Sent from my Galaxy Nexus using XDA

emd2009 said:
How about you post your settings?
Click to expand...
Click to collapse
+1
Sent from my Galaxy Nexus using xda premium

s4vva said:
Excellent post. Needs to be a sticky.
Click to expand...
Click to collapse
This isn't really my work so I don't think it should be stickied. I just found some old posts and read **** on the internet. lol

wow first time i read this 3ad..very usefull.i always have some doubt about how it works the automatic backlight settings..honestly i have always the phone to max brightness,but now i want to know better how it works this features.thanks for the wonderfull 3ad.

[BOOTANIMATION] Slim ICS for Galaxy S [480x800]

EDIT: View new version (88KB in size, 6 dots "progress bar") on post #8.
Hi guys,
First time poster, long time reader.
I've been using Slim ICS since 3.7 (now on 3.9), and I was very disappointed with the new boot animation on 3.9. Besides looking very choppy, I just didn't like it.
So, I went ahead and made a Slim ICS boot animation that i do like. It turned out to be very clean, superb definition on Slim logo, 1px progress bar at the bottom.
The sample, since it is larger than the actual phone screen, doesn't do justice to the bootscreen running on the phone. I was very surprised by the result myself.
THe progress bar is smooth on the sample, but on the phone, since it is booting, stops momentarily (just like a true progress bar, that gets stuck for a second while the phone is busy doing much needed stuff)
I like Slim ICS so much, I thought I'd give back to the community and post it here for all who want it.
[Thanks krarvind, for a great ROM. If by any chance you want to include this boot animation in any of your future Slim ICS ROMs, you have my permission.]
It is made for SGS @ 480x800, and I can only guarantee that it works on this phone. It might work on others, but I have no way of testing it. Consider yourself warned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to install:
Place bootanimation.zip in /data/local folder. That's it. Reboot and see.
Any comments?

Thanks I will try this B-)
Sent from my GT-I9000 using xda premium

@Jovenitto:
Nice work, can you bring the size down to my current levels? if yes, make one up and post it in my thread, i will look to put it in. As i said before, i would love users to get involved in this if they wish, my only req is BA should be simple and light ( < 100 kb preferred )

Thanks very much Jovenitto,
Nice and simple - just how I like it...

krarvind said:
@Jovenitto:
Nice work, can you bring the size down to my current levels? if yes, make one up and post it in my thread, i will look to put it in. As i said before, i would love users to get involved in this if they wish, my only req is BA should be simple and light ( < 100 kb preferred )
Click to expand...
Click to collapse
I was actually thinking of increasing the number of frames...
I'll try to get the size down.
Maybe by reducing the PNG quality and hope that it doesn't compromise overall image quality.
I could reduce the number of frames (there are exactly 100 frames), but the progress bar will be choppier... each frame "fills" the bar 4 pixels, i can reduce the frames to 50 if I increase the "fill" to 8px/frame.
Or maybe reduce the size of the progress bar. As of now, the bar is 400px wide, with 40px margin on each size. If the bar is smaller, it takes less frames to fill.
Tomorrow is a national holliday here in PT, i'll edit the BA and try to hit the 100KB mark.
EDIT: Small update:
PNG Compression already at max. 9KB each frame.
Reduced to 50frames (progress bar @ 8px/frame)
Result: bootanimation.zip @ 426KB
Maybe i'll be albe to get to 200KB by reducing the size of the bar to 200px or something...
Or change the progress bar completely. Maybe some Ubuntu style dots? Or some kind of glow effect (less frames needed)?
Cogs are turning in my head.

Jovenitto said:
I was actually thinking of increasing the number of frames...
I'll try to get the size down.
Maybe by reducing the PNG quality and hope that it doesn't compromise overall image quality.
I could reduce the number of frames (there are exactly 100 frames), but the progress bar will be choppier... each frame "fills" the bar 4 pixels, i can reduce the frames to 50 if I increase the "fill" to 8px/frame.
Or maybe reduce the size of the progress bar. As of now, the bar is 400px wide, with 40px margin on each size. If the bar is smaller, it takes less frames to fill.
Tomorrow is a national holliday here in PT, i'll edit the BA and try to hit the 100KB mark.
EDIT: Small update:
PNG Compression already at max. 9KB each frame.
Reduced to 50frames (progress bar @ 8px/frame)
Result: bootanimation.zip @ 426KB
Maybe i'll be albe to get to 200KB by reducing the size of the bar to 200px or something...
Or change the progress bar completely. Maybe some Ubuntu style dots? Or some kind of glow effect (less frames needed)?
Cogs are turning in my head.
Click to expand...
Click to collapse
why dont u try something like windows 8 type of round circle http://i.imgur.com/vG0XV.gif

takerhbk said:
why dont u try something like windows 8 type of round circle http://i.imgur.com/vG0XV.gif
Click to expand...
Click to collapse
+1, not necessarily for the win8 circle but for a smaller type of animation, will save you a bucket load of frames

As per krarvind's request of size, here it is:
Keeping it simple, just the way I like it.
Try it and comment, plz.
FYI, I'll keep the previous one available (the one with long progress bar).
@krarvind:
10 frames only, 88KB total zipped size.

Just downloaded - works great and much nicer than the 3.9 animation (not that it upset me!). Thanks.

[BOOTANIMATION] [RED-MOD] Slim ICS for Galaxy S [480x800]
Thank you so very much for doing this boot animation. FYI, still works great in SlimICS 4.2. It's alot nicer then stock animation but still nice and light.
As I have an eternal hatred of the color blue and try to mod it out of every aspect of my phone, I've made a red version of your bootanimation and am uploading it to those who prefer it...
Enjoy!

How to reach the lowest battery-drainage?

Hey folkes,
heres what I did to minimized battery drainage:
- clean install of ARHD 9.1
- Faux 6M
- Autobrightness
- Static backround in dark colours
Any other tips are highly appreciated
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
33 % in 22 h and 19 Minutes
---> Display: 37 % in 57 Minutes --> 13 % per hour.
---> W-Lan : 18 % in 17 hours and 9 Minutes --> 0,34 % per hour.
I spend most of the 57 Minutes surfing, must have been some 40 minutes, the rest on whatsapp, sms and doing random stuff.
I was thinking about doing an actual analysis of the energie consumption factors...maybe it can still be minimized.

Coming from CM10, i was absolutely blown away by how much better the battery life was on ARHD (just as good as my old iPhone 3GS).
BTW, using a dark background won't save power - the LCD backlight output is constant irregardless of what is on the screen.
PS. The 'Captcha' image verification for every post on this forum is ridiculous.

JMCNZ said:
Coming from CM10, i was absolutely blown away by how much better the battery life was on ARHD (just as good as my old iPhone 3GS).
BTW, using a dark background won't save power - the LCD backlight output is constant irregardless of what is on the screen.
PS. The 'Captcha' image verification for every post on this forum is ridiculous.
Click to expand...
Click to collapse
You have that captcha verification because at the time of the above posting you had only five posts. Once you reach a certain number (8/10 I don't remember) it will not be required.
Sent from my HTC One X using xda premium

Lower autobrightness values will definitely reduce battery consumption. Make sure your kernel is based off of the latest base (2.17), and then you can try undervolting and underclocking from there. Use BetterBatteryStats to try and diagnose any unnecessary battery drain. Avoid doing CPU/GPU intensive tasks to really stretch out the battery. Make sure you are using the latest radio firmware for your device. Disable vibration feedback if you can live without it. Disable screen lock sounds, touch sounds, and keyboard sounds.
Install Carat on your phone and use it to figure out if anything is using battery excessively. If anything has very high confidence percentage, either delete or change the settings in the application to try and get rid of the battery drain.
One thing I have noticed is that Google backup can take battery in the background. If you use Titanium backup and do not care about Google's phone backup, you can disable it.

Babydoll25 said:
You have that captcha verification because at the time of the above posting you had only five posts. Once you reach a certain number (8/10 I don't remember) it will not be required.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
That is some relief. Some of those Captcha's are getting unreadable to the point where they'll not only stop bots, but humans as well!

JMCNZ said:
That is some relief. Some of those Captcha's are getting unreadable to the point where they'll not only stop bots, but humans as well!
Click to expand...
Click to collapse
It's better than a forums filled with ads..
BTW, you may checks for any unexpected wakelocks. Though, I reckon that your battery usage is good and is free from inconvenience wakelocks

have u tried stock kernel instead of faux? current faux kernel are oc and suit gamer more. If ur using ur hox for browsing more, try stock kernel, u will get more on screen time. Try it
Sent from my HTC One X using xda premium

Sent from my HTC One X using xda premium

my on screen time
Sent from my HTC One X using xda premium

Portrait Mode Problems???

past 3 days ago i'm purchase Honor 7x. its back camera shows portrait mode is enable but it's not blur the background (bokey mode also enable) even aperture mode blur the background. i'm thing it's only happen in my device or not plz any one clear my daut...

D TheThWr said:
past 3 days ago i'm purchase Honor 7x. its back camera shows portrait mode is enable but it's not blur the background (bokey mode also enable) even aperture mode blur the background. i'm thing it's only happen in my device or not plz any one clear my daut...
Click to expand...
Click to collapse
Before taking photo check on screen portrait mode is enabled. Most important you should touch the object which you want to focus.You will see circle on the object then shoot...You will surely get..

bro i'm also try this but portrait not show any blur.... i think somthing wrong with my device.

D TheThWr said:
bro i'm also try this but portrait not show any blur.... i think somthing wrong with my device.
Click to expand...
Click to collapse
for blur effect u have to use wide aperture which is near portrait mode

vatsal_chandan said:
for blur effect u have to use wide aperture which is near portrait mode
Click to expand...
Click to collapse
Same problem here. I used this wide aperture button and it even blurred things the way I want it to, but when you make a shoot, you got just normal photo without any side effects

I have also faced the same problem with my honor 7x..I have already tired camera data clear and camera app force stop but nothing is working. Anybodys give me the proper solution.?

Just tried this with my Mate SE and it works. The wide aperture does have a scale down at the bottom, to adjust the significance of the effect. Slid it all the way left and it works pretty well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So, it looks like the 'wide aperture' setting is available for the back camera (pic above), but the selfie camera has, instead, the bokeh setting (they both, essentially, mean the same thing).
I verified the selfie camera with the bokeh setting works fine also, on mine. But started to wonder if this is software implemented etc.
So here is the exif data for the above pic (the selfie one is the same in the following important data):
Pretty amazing the exif data indicates the f stop is at 1.0 or even 0.9? Hmmmmm
Properties:
date:create: 2018-03-27T09:29:09-07:00
date:modify: 2018-03-27T09:29:09-07:00
exif:ApertureValue: 0.00 EV (f/1.0)
exif:BitsPerSample: 8, 8, 8
exif:BrightnessValue: 0.00 EV (3.43 cd/m^2)
exif:ColorSpace: sRGB
exif:ComponentsConfiguration: 1, 2, 3, 0
exif:Compression: JPEG compression
exif:Contrast: Normal
exif:CustomRendered: Custom process
exifateTime: 2018:03:27 08:30:31
exifateTimeDigitized: 2018:03:27 08:30:31
exifateTimeOriginal: 2018:03:27 08:30:31
exifigitalZoomRatio: 1.00
exif:ExifImageLength: 1067
exif:ExifImageWidth: 800
exif:ExifOffset: 222
exif:ExifVersion: Exif Version 2.1
exif:ExposureBiasValue: 0.00 EV
exif:ExposureMode: Auto exposure
exif:ExposureProgram: Normal program
exif:ExposureTime: 1/20 sec.
exif:FileSource: DSC
exif:Flash: 0
exif:FlashPixVersion: FlashPix Version 1.0
exif:FNumber: f/0.9
exif:FocalLength: 3.8 mm
exif:FocalLengthIn35mmFilm: 26
exif:GainControl: Normal
exif:GPSDateStamp: 2018:03:27
exif:GPSInfo: 954
exif:GPSTimeStamp: 15:30:29.00
exif:ImageDescription: edf
exif:ImageLength: 3264
exif:ImageWidth: 2448
exif:InteroperabilityIndex: R98
exif:InteroperabilityOffset: 924
exif:InteroperabilityVersion: 0100
exif:ISOSpeedRatings: 500
exif:LightSource: Daylight
exif:Make: HUAWEI
exif:MakerNote: 100 bytes undefined data
exif:MeteringMode: Pattern
exif:Model: BND-L34
exifrientation: Unknown value 0
exifixelXDimension: 2448
exifixelYDimension: 3264
exif:ResolutionUnit: Inch
exif:Saturation: Normal
exif:SceneCaptureType: Standard
exif:SceneType: Directly photographed
exif:SensingMethod: One-chip color area sensor
exif:Sharpness: Normal
exif:ShutterSpeedValue: 29.90 EV (1/999963365 sec.)
exif:Software: BND-L34C567B130
exif:SubjectDistanceRange: Unknown
exif:SubsecTime: 606203
exif:SubSecTimeDigitized: 606203
exif:SubSecTimeOriginal: 606203
exif:thumbnail:Compression: 6
exif:thumbnail:ImageLength: 512
exif:thumbnail:ImageWidth: 384
exif:thumbnail:InteroperabilityIndex: R98
exif:thumbnail:InteroperabilityVersion: 48, 49, 48, 48
exif:thumbnail:JPEGInterchangeFormat: 1150
exif:thumbnail:JPEGInterchangeFormatLength: 5003
exif:thumbnailrientation: 0
exif:thumbnail:ResolutionUnit: 0
exif:thumbnail:XResolution: 72/1
exif:thumbnail:YResolution: 72/1
exif:WhiteBalance: Auto white balance
exif:XResolution: 72
exif:YCbCrPositioning: Centered
exif:YResolution: 72
jpeg:colorspace: 2
jpeg:sampling-factor: 1x1,1x1,1x1
signature: d896a8b6d9c3e6f9247d194042ed22098a5d5156c429b8b3bf8f1bccdd8b9812
---------- Post added at 17:55 ---------- Previous post was at 17:35 ----------
Hahahah, just checked to be sure
Yeah, it's kindof expensive to get a lens that actually opens to an f1 stop
Only about $4,500 for a used one on Ebay
https://www.ebay.com/itm/Canon-EF-5...015944?hash=item2aa17e00c8:g:S6YAAOSw4MxalMgD

Screen dp

So let's talk about the biggest turn off on this phone , not the lack of NFC but the screen resolution , it's not the best and you can learn to adapt to it but here and there the scaling is just bad. Especially for others like my self coming from old flagships with a higher resolution (had an S8 and 720p is quite the downgrade from 1440p).
fortunately enough in developer options there is the option to change how the phone scale by changing the smallest width , mine is set at 480 dp and I like the phone way more than the day I got it ,
share your experience regarding the best settings for the screen scaling !

sounds good, how to do it?
---------- Post added at 01:24 AM ---------- Previous post was at 01:23 AM ----------
... develepor options, didnt read carefully

psycø lucïfer said:
fortunately enough in developer options there is the option to change how the phone scale by changing the smallest width , mine is set at 480 dp and I like the phone way more than the day I got it ,
share your experience regarding the best settings for the screen scaling !
Click to expand...
Click to collapse
Thanks for the sharing man! Love it with 480dp.
It's in Developer Options > Drawing Section > Smallest width

I'm digging 390.

What was the default value ??

360 is default

dragganta said:
360 is default
Click to expand...
Click to collapse
360 seems way to big, makes the phone look like toy, default was 400 something, anyway mine is at 413 and it looks fine

Simran62 said:
360 seems way to big, makes the phone look like toy, default was 400 something, anyway mine is at 413 and it looks fine
Click to expand...
Click to collapse
360 is actually the stock value, it also seems huge to me after setting it at 420

GoelPlz said:
360 is actually the stock value, it also seems huge to me after setting it at 420
Click to expand...
Click to collapse
Ya it was looking huge when i reverted back to 360, so maybe it happened after seeing it at 400+

390 is great.

You can use settings -> display -> GUI size (or interface size, not sure about English term). Values used by system are 320, 360 and 423dp.

now on android 10 increasing the screen's dpi causes the notification bar to cut the battery icon and the clock

Ergeles said:
now on android 10 increasing the screen's dpi causes the notification bar to cut the battery icon and the clock
Click to expand...
Click to collapse
Do you have a screenshot? Maybe it could be solved by increase of the padding.
adb shell settings put secure sysui_rounded_content_padding x

_mysiak_ said:
Do you have a screenshot? Maybe it could be solved by increase of the padding.
adb shell settings put secure sysui_rounded_content_padding x
Click to expand...
Click to collapse
I don't have another phone to show how it looks on the screen, but I've already tried this ADB command, but it looks like it doesn't work on the Mi A3

Ergeles said:
I don't have another phone to show how it looks on the screen, but I've already tried this ADB command, but it looks like it doesn't work on the Mi A3
Click to expand...
Click to collapse
Not sure about Android 10, but it works fine in Android 9.
Return to default value:
Code:
laurel_sprout:/ # settings delete secure sysui_rounded_content_padding
Deleted 1 rows
laurel_sprout:/ # settings get secure sysui_rounded_content_padding
null
Move towards center (experiment with the last number, default is about 8):
Code:
laurel_sprout:/ # settings put secure sysui_rounded_content_padding 10

_mysiak_ said:
Not sure about Android 10, but it works fine in Android 9.
Return to default value:
Code:
laurel_sprout:/ # settings delete secure sysui_rounded_content_padding
Deleted 1 rows
laurel_sprout:/ # settings get secure sysui_rounded_content_padding
null
Move towards center (experiment with the last number, default is about 8):
Code:
laurel_sprout:/ # settings put secure sysui_rounded_content_padding 10
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://imgur.com/s0IUO6C
https://imgur.com/u5w0v8M
(I just realized that I don't know how to add a photo: p)
any number above 423 starts cutting the battery and the clock
and the commands didn't work here

Thanks for this! Screen looks much sharper because of this! Could be placebo lol

480 works fine, my bigger turn off is the pixels you can view on the screen, you can note it when you see brighter shades on screen. add to that I'm using a matte screen protector ...and I feel this screen guard only enhances the pixel problem.

Galaxy Tab A 10.1
Min - 320dp
Default - 901dp
Max - 1600dp

393 dpi is best