Related
I'm not sure if this has been brought up before, but I wouldn't be surprised if it was missed. I am the type of user who likes to use the phone at full brightness, as it does not seem to have a huge negative impact on my battery life in day to day operations.
I was looking carefully at the browser on the Galaxy and wondered why the whites looked so dimmed in comparison to other parts of the operating system.
I had already done the following:
1. Turned the OS brightness all the way up.
2. Turned browser brightness all the way up.
3. Disabled the screen power saving mode.
I then downloaded a flashlight application and maxed it to 100% while switching to the browser with the Home key multitask, and going back and forward between the flashlight app and the browser app, it is very clear that the browser is not pushing max brightness. Even though the brightness settings on both the OS and the browser are maxed, it seems as though the browser is capped to 80% brightness or so.
My friend also verified this during his test run, as he has just bought the Samsung Vibrant and noticed the same thing. I understand many will just leave the auto-brightness setting on, but that's not really addressing the issue here.
Is there a way for an XDA developer to correct this issue through a patch or ROM?
thanks
I checked with the shell and when brightness is at 100% it has an absolute value of 255, the same when I'm at the browser set with full brightness, so it seems it's working as it should.
You can check it with this command
Code:
cat /sys/devices/platform/s3cfb/spi_gpio.3/spi3.0/blacklight/s5p_bl/actual_brightness
darksnarfer said:
I checked with the shell and when brightness is at 100% it has an absolute value of 255, the same when I'm at the browser set with full brightness, so it seems it's working as it should.
You can check it with this command
Code:
cat /sys/devices/platform/s3cfb/spi_gpio.3/spi3.0/blacklight/s5p_bl/actual_brightness
Click to expand...
Click to collapse
I don't know, I experience the same thing as the OP. Everything's bright, except when surfing the web.
Same issue here. I use Opera in bright daylight.
Sent from my GT-I9000 using XDA App
If you go in to the brightness settings there is an option at the very bottom called "Power saving mode". I'm not sure if that is having any effect on the browser.
Thanks for the numbers, but I gotta say, just comparing the flashlight app and hitting the back arrow to toggle to the browser, it is beyond obvious that the browser is not as bright as the flashlight application. I used google with it's white background and zoomed in to an area that was just white to avoid other distractions.
This is the best way to test since there will be no transition in between the application toggle and you see the screen dim easily.
As indicated by my original post, I have also turned off the power saving feature so that is not a concern. Someone did say that the Behold 2 has the same cap for their browser and that this is a samsung specific setting that's probably there to save battery. I haven't been able to confirm it on that phone yet but just give the flashlight test a chance and you'll see.
oh one last thing i noticed is, when going from the browser back to the flashlight, sometimes the flashlight app is also dimmed at the same level brightness as the browser, but tapping the screen 'wakes' up the app into full brightness.
TGalaxy browser brightness
To me it's very obvious that the browser is dimmed down, I'd say more than to 80%... Having google as the default homepage couldn't make it more obvious when opening the browser! Samsung obviously thought that no one with a decent eyesight will buy their phone. Or anyone who feels capable of managing their phone's battery life themselves.
It's just one of those niggling things that had to be included, lessening the experience of an otherwise rather breathtaking phone. Another one is the compulsory vibration when charging is finished - makes me wonder when others, or the developers for that matter, charge their smartphones! I charge them overnight, and of course every night... or at least used to, as with the Galaxy S, I can no longer sleep.
I think I've been through every menu possible to change these couple of features, with no success... if anyone knows anything, please share.
It happens on the dim-side, too
I have the same problem, but on the dim side. The browser brightens the screen when it comes on if you have the brightness set to zero. I like it dimmed all the way at night if I'm reading in bed when the lights are out and my partner is asleep, but it keeps turning it up so it's pretty bright in the pitch dark. Arrgh. It's my phone, can't I set it the way I want? Grr.
I've read that there are limitations on how much the screen dims and brightens unless you have a rooted phone and you use an app that's not built into the OS.
I rooted mine and there are some configuration apps that will set it to 0, but I think the built-in operating system slider doesn't go all the way to zero and might not go all the way to 255 when you slide it to the very edges. Supposedly it only goes to 10 on the low side from the notes on some apps.
So, probably it's a similar limitation on the slider for the screen brightness in the browser. We're probably stuck with this problem until someone writes an app that lets you change this setting to any value between 0 and 255 since the default sliders don't allow the low side and I'm guessing not the high side either.
So . . . any android developers out there, it would be cool if you could make an app to change this setting if it's available programatically somewhere.
I tried the "Dimmer" and "Brightness!" apps from the market. But none of them 'Keep' the brightness at the minimum always.
050820121030:
I have use the search button to see how i can lower screen brightness on galaxy note.
i found everywhere mentioning screen filter, it is not i don't like screen filter, but when i take screenshot it will be tinted gray.
so i decide to go to a more elegant way like what atrix 4g user did.
http://forum.xda-developers.com/showthread.php?t=1245332
i tried with my note, i cant find sys/bus/i2c/drivers/lm3532, i decided to check folder with the nearest name, but i can't find it.
so i decided to download linux, mind you i have no idea how to use linux.
i downloaded samsung ics opensource update 4, inside i can't find leds-lm3532.c,leds-lm3532.h,board-mot-lights.c.
so futhur dig found leds-lm3530c, the file structure is different with leds-lm3532.c, but i think it works the same.
any good suggestion from experts?
edit1 050820121203:
I decided to check what AdjBrightness do.
it is modifying the following files
/sys/class/leds/lcd-backlight/brightness
/sys/class/leds/amber/blink
/sys/class/leds/amber/brightness
/sys/class/leds/green/blink
/sys/class/leds/green/brightness
all return errors in note.
further investigation leads to Rootdim:
/sys/class/leds/leds-sec/trigger
/sys/class/leds/leds-sec/brightness
/sys/class/leds/leds-sec/mmc1::/trigger
/sys/class/leds/leds-sec/mmc1::/brightness
/sys/class/leds/leds-sec/mmc2::/trigger
/sys/class/leds/leds-sec/mmc2::/brightness
here all the triggers return error.
next thing i check /sys/class/
i see backlight/panel in it.
i also see lcd, leds and lightsensor.
have no idea, keep digging.
100820120935:
Found s6*aa*.c files inside driver folder.
There will be some info about 5.3inch screen.
Deeper search found that it only suplort 24 stages of brightness
From 0,1 to 30 is 0
Conclusion minimum brightness for galaxy note is 1(more than 30)
Keep digging.
100820121808:
s3cfb_s6e39a0.c contain brightness level from 1 to 24.
100820121815:
AMS529HA01 is samsung 5.3 inch galaxy note panel
s3cfb_s6e8aa0 -- the one we are using.
the following files also related to the above file.
s3cfb_s6e39a0
s3cfb_s6e63m0
s6d6aa1
s6dr171
s6e8aa1
smart_dimming
midas-lcd
setup-fb-s5p
the whole thing means samsung have tried other lcd before hd super amoled 5.3 inch?
keep digging for the brightness
150820121820:
End of research, the brightness for amoled devices only have 24 levels.
lower than that you will need to adjust contrast for better battery consumption.
if you use filter it wont decrease battery consumption, and it will affect your screenshot images clarity.
1609120512:
https://sites.google.com/site/androidnothize/no-dock/input-device-and-backlight
this shows you minimum brightness level is 30
http://forum.xda-developers.com/showthread.php?t=1709686
search for min_bl
http://forum.xda-developers.com/showthread.php?t=1154278&page=617
curve?
http://forum.xda-developers.com/showthread.php?t=1576355&page=222
N.E.A.K
So, what's the verdict? Are we stuck with "too bright in the dark" screens on our Note's?
d210 said:
So, what's the verdict? Are we stuck with "too bright in the dark" screens on our Note's?
Click to expand...
Click to collapse
For that purpose a screen filter works just fine for me.
Frankly it's not doing it for me, it looks like I'm looking through a grey plastic bag.
Andrew0811 said:
150820121820:
End of research, the brightness for amoled devices only have 24 levels.
lower than that you will need to adjust contrast for better battery consumption.
if you use filter it wont decrease battery consumption, and it will affect your screenshot images clarity.
Click to expand...
Click to collapse
So what is conclusion bro?
We can't use brightness below the SYSTEM-MINIMUM?
I also want more battery by reducing brightness to below 10.
AND yes you did well.
Good research.
Hello, i have the 1cm dead touchscreen zone in the top and bottom, not good for the android taskbar...
Can we recalibrate the resolution / screen parameter to reduce a little the screen height to fix the problem ??
Thank you.
same problem here .. heeeelp
yeeeeeeeeeeeee .. after month or more looking for solution and tried everything on web i finally found it broo
download from the play store NOmone resolution changer and use it
our default settings is 1024 768 160
u just change the first number i use 880 768 160
as i have 2 cm below of dead touchscreen :S
i hope this works for u
I7V said:
yeeeeeeeeeeeee .. after month or more looking for solution and tried everything on web i finally found it broo
download from the play store NOmone resolution changer and use it
our default settings is 1024 768 160
u just change the first number i use 880 768 160
as i have 2 cm below of dead touchscreen :S
i hope this works for u
Click to expand...
Click to collapse
Than You, i had no success with NOMONE Resolution Changer, impossible to install for me tough Play Store (not allowed in my country) and the multiple apk found on the net was not good, an error 'probleme with parsing installer' something like this.
I found "Resolution Changer Pro" who work very well, the perfect resolution for me is : 970 x 768.
Or even easier, use a simple adb debug shell command:
Code:
adb shell
wm overscan 0,300,0,400
For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
The above command will shrink the useful screen area with 300px from top and 400px from bottom.
Feel free to experiment those parameters to find the best fit for your situation.
Hi guys! I start to thank you a lot for your suggestions but before making any disaster i should be really grateful if you could give me an help.
I need to resize the screen of my Nexus 7 (2013) in order to fit with the car-dash enclosure where i'm willing to install it.
The enclosure i bought was supposed to fit for the nexus display but regrettably whilst the latter is of abt 15.3cm wide x 9.5 cm "tall" (sorry for my english) the enclosure has a window of 15.3 cm wide but only 8.7 cm tall which would make impossible the access to the softkeys.
In view of the above and considering also that there is no space available to enlarge the window of the enclosure i thought and hoped it would have been easier to resize the screen.
Now the question is: considering that the measures reported are relevant to the device in landscape mode may i kidly ask you the command variables that i have to amend to cut off the 0.8 cm on the bottom side of the screen (again landscape mode).
Thanks a lot in advance for your help!
Hello, Please i need help. I have a Dead Touch Zone (at the bottom 30% aprox.), i installed and i resized screen with ADB (adb shell wm overscan 0,0,0,600) BUT... I can´t use some apps (google play, whatsaap, etc) because it shows like they are behind backgroud.. Check pics attached for understanding.
eric_thefool said:
Hi guys! I start to thank you a lot for your suggestions but before making any disaster i should be really grateful if you could give me an help.
!
Click to expand...
Click to collapse
Did you solve the problem?
davis_llb26 said:
Hello, Please i need help. I have a Dead Touch Zone (at the bottom 30% aprox.), i installed and i resized screen with ADB (adb shell wm overscan 0,0,0,600) BUT... I can´t use some apps (google play, whatsaap, etc) because it shows like they are behind backgroud.. Check pics attached for understanding.
Click to expand...
Click to collapse
Did u get through with this problem..??
i too have the same problem but mine is 25% of the screen so i can use whats app and all other app but the plain box is disturbing me too...
Confirm the adb route works without root!
silvake said:
Or even easier, use a simple adb debug shell command:
Code:
adb shell
wm overscan 0,300,0,400
For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
The above command will shrink the useful screen area with 300px from top and 400px from bottom.
Feel free to experiment those parameters to find the best fit for your situation.
Click to expand...
Click to collapse
A long time since the original post and answers, but I thought it should be noted that this method works well. Thanks silvake.
My Mecer tablet stopped responding in the top 2-3cm after many years of loyal service. Could have been a drop or simply age. It is still useful and wish to give it to someone in need. So searching around and several different sites yielded some results. Note this is not a mainstream device so rooting was not an option nor attempted. Indeed drivers and any info is sparse for this device.
For anyone attempting this, I will outline my method and steps.
1. Enable USB debugging. There are many tutorials. Settings->About->Build number(tap x 7); Developer Options->USB debugging
2. Connect device with USB Cable. Give permission on device. You will need to make sure that windows installs drivers. At first windows failed to install all drivers. Not sure how it managed, but it connected eventually.
3. Download adb: https://android.izzysoft.de/downloads.php. I used https://android.izzysoft.de/downloads.php?file=adb-binaries-windows-29.0.4.zip. Decompress to desired folder. Open cmd to the folder.
4. Run adb.exe with 'adb devices' and confirm device is listed. First attempt showed:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
0123456789ABCDEF unauthorized
I had to give permission on the device. Reconnected USB.
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
List of devices attached
0123456789ABCDEF device
Success! Device is now connected.
Next get the current display stats:
Type 'adb shell'
Confirm connection. Mine showed: [email protected]:/ #
Type: ‘dumpsys display | grep mBaseDisplayInfo’
Below is the capture of the operation:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
[email protected]:/ # dumpsys display | grep mBaseDisplayInfo
mBaseDisplayInfo=DisplayInfo{"Built-in Screen", app 800 x 1280, real 800 x 1280, largest app 800 x 1280, smallest app 800 x 1280, 55.84 fps, rotation0, density 190 (190.0 x 190.0) dpi, layerStack 0, type BUILT_IN, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
This is not really required but helps to determine the current stats to make a guess on the number of pixels to adjust the screen by.
Next is the command to adjust the screen. The 4 numbers are the coordinates. Since mine was the top area I adjusted only that.
Type: wm overscan 0,50,0,0
The update is live and you should see the screen drop 50 pixels from the top.
This was not enough for me so repeat until the pull down of the status bar starts working again.
Here is the whole list to adjust the screen until everything is working again:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
[email protected]:/ # wm overscan 0,50,0,0
[email protected]:/ # wm overscan 0,70,0,0
[email protected]:/ # wm overscan 0,80,0,0
[email protected]:/ # wm overscan 0,100,0,0
[email protected]:/ # wm overscan 0,200,0,0
[email protected]:/ # wm overscan 0,120,0,0
[email protected]:/ # wm overscan 0,140,0,0
[email protected]:/ # wm overscan 0,150,0,0
[email protected]:/ # wm overscan 0,160,0,0
[email protected]:/ # wm overscan 0,170,0,0
[email protected]:/ # wm overscan 0,180,0,0
[email protected]:/ # wm overscan 0,190,0,0
[email protected]:/ # wm overscan 0,195,0,0
[email protected]:/ # exit
So I had to move the screen 195 pixels down until the dead touchscreen area was excluded.
Screen is obviously smaller but the frustration of having to rotate the device 180 to be able to pull down the status bar is removed. Much worth it.
Now a child in need of education can still learn and we have saved the device from landfill and reduced the carbon footprint.
You might have to adjust the pixel density to compensate for the loss, but I left it untouched. Your results will vary so I cannot assist.
Excerpt from another site:
"Additionally decreasing the density through the settings (Display & lights > screen > LCD density) or the wm command helped compensating for the lost display area:
wm density 360"
Hope this helps someone as it helped me.
T
Hello amazing people,
I am looking for your guide/advice for solving a screen resolution issue.
I am using a 4:3 ratio screen with a LCD driver on Radxa Zero.
the poblem is that the screen looks stretched laterally. I think its due to aspect ratio becuase the lcd is of 4:3 aspect ratio.
can anyone help me how can I change the aspect ratio using adb?
I have worked with size and density but failed to produce any results.
Many thanks to this amazing community.
the side of may cellphone is not working
I own a Oneplus 3T, on which the bottom 1cm of the screen does not register any touch. I've concluded the problem to be with the digitizer, but am not in a state to replace the display. So, I was wondering if I could shift the bottom border about 100px upwards. I tried the
Code:
adb shell wm overscan 0,0,0,100
method, but that seems to break a lot of apps. The margin seems to vary for different apps. I also tried the
Code:
adb shell wm size 1080x1820
(original resolution being 1080x1920 pixels), and the apps had no problem adapting to the new resolution. But the resolution-resize resulted in the extra 100px being distributed on top and bottom equally as 50px. Now all that's remaining is to shift the display-area 50px upwards on the y-axis. Is there a command to do that? If not, are there any other alternatives for me to achieve the same result? Please help!
As an additional request, where can I get a list of all available ADB commands?
PS: I've already tried to enable the on-screen navigation buttons and use it to offset the display, but my Oxygen OS 5.0.3 does not allow both hardware and on-screen buttons to be active at the same time.
So I bought my S21 Ultra last Friday. I lie with my mobile in bed late at night with brightness at its lowest with "dark mode". Notice that when I have dark gray backgrounds and open the keyboard, horizontal lines appear (thin light lines). They disappear as soon as I close the keyboard.
Someone who can test if you see the same thing?
So If I sent it back to samsung I can say that i have asked owners and they dont have that problem.
1 set brightness at minimum
2 darkmode on
3 120hz on
4 high contrast on keyboard
5 total black rooms
6 open play store and press search so keyboard appears
7 now I see thin lines (which disappears completely when I close the keyboard)
It looks like this
If it is application dependent (appears only when the keyboard is active), it might be a software alrifact.
Also, please bear in mind that OLED displays, when set to minimum brightness, might have a problem with displaying uniform colors. You might see clusters of tens of pixels that are just a tad bit brighter than the ones around. I've noticed this with every OLED display I have used in the last decade or so.
daniel_loft said:
If it is application dependent (appears only when the keyboard is active), it might be a software alrifact.
Also, please bear in mind that OLED displays, when set to minimum brightness, might have a problem with displaying uniform colors. You might see clusters of tens of pixels that are just a tad bit brighter than the ones around. I've noticed this with every OLED display I have used in the last decade or so.
Click to expand...
Click to collapse
Ok thank you.
Yes it's only showing when i use the keyboard.
My old note 10 plus did not have this problem.
Different screen, different version of Android and Oneui, maybe even different keyboard, keyboard version or theme.
check app named Display Tester https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&hl=en
robalm said:
So I bought my S21 Ultra last Friday. I lie with my mobile in bed late at night with brightness at its lowest with "dark mode". Notice that when I have dark gray backgrounds and open the keyboard, horizontal lines appear (thin light lines). They disappear as soon as I close the keyboard.
Someone who can test if you see the same thing?
So If I sent it back to samsung I can say that i have asked owners and they dont have that problem.
1 set brightness at minimum
2 darkmode on
3 120hz on
4 high contrast on keyboard
5 total black rooms
6 open play store and press search so keyboard appears
7 now I see thin lines (which disappears completely when I close the keyboard)
It looks like this
Click to expand...
Click to collapse
robalm said:
So I bought my S21 Ultra last Friday. I lie with my mobile in bed late at night with brightness at its lowest with "dark mode". Notice that when I have dark gray backgrounds and open the keyboard, horizontal lines appear (thin light lines). They disappear as soon as I close the keyboard.
Someone who can test if you see the same thing?
So If I sent it back to samsung I can say that i have asked owners and they dont have that problem.
1 set brightness at minimum
2 darkmode on
3 120hz on
4 high contrast on keyboard
5 total black rooms
6 open play store and press search so keyboard appears
7 now I see thin lines (which disappears completely when I close the keyboard)
It looks like this
Click to expand...
Click to collapse
What model, carrier and software build do you have?
Software build: (settings > about phone > software information - last 4 digits of SW build number)
Is this happening in all the apps? or just the email as shown in the picture?
try it on safe mode and see if it still happens. maybe you are using a third party keyboard?
AM3000 said:
What model, carrier and software build do you have?
Software build: (settings > about phone > software information - last 4 digits of SW build number)
Is this happening in all the apps? or just the email as shown in the picture?
try it on safe mode and see if it still happens. maybe you are using a third party keyboard?
Click to expand...
Click to collapse
SM-G998B
G998BXXU3AUHB (same problem with older firmware)
It happend in dark grey and some light color, swifty keyboard and stock samsung keyboard, showing must if i use high contrast in stock samsung keyboard.
Here is one more:
Display issue at 120hz and low brightness
My note 20 ultra has vague gray horizontal lines when displaying a gray background at the lowest brightness when running at 120Hz but it disappears at when the brightness increases or when switching to 60hz. Is this normal for AMOLED displays ?
forum.xda-developers.com
Strange no one can test it so when i send it to samsung and maybe get a new phone and the same thing will show on that one to..