We have all seen the side by side web browsing comparisons between the S4 and the HTC One. Because of the screen reviews, which measured brightness at 300cd/m² and higher, we were a bit dubitative.
{
"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"
}
Well, it turns out the poor results are due to brightness throttling on white or near white content, which will vary depending on the power saving options that are activated. In Chrome and in the Stock Browser, this is further aggravated by the undefeatable activation of the Power Saving mode.
The measurements below were conducted with an i1 Pro 2 spectrophotometer and a profiled i1 Display Pro (for dark readings).
Maximum Brightness (Adapt Display/Dynamic/Standard Mode)
Even without any Power Option engaged, white levels on white or near white content will be 15% to 20% below peak brightness (290cd/m² from 355cd/m²)
Auto-Tone will clip whites further above 60% Average Picture Level
Power Saving reduces brightness by 25%
In Chrome and in the stock browser the Power Saving mode is activated as a default (surely in an attempt to fool battery tests into overestimating number of browsing hours on battery) - and cannot be defeated. It is therefore recommended to switch to another browser (e.g. AOSP) for better outdoor viewing.
The graph below outlines the brightness throttling mechanism in Dynamic/Standard/Auto Mode at maximum brighness.
As we can see, web browsing is the activity that will take the most serious hit, seeing as web browsing average picture levels typically falls within the 70% to 90% APL range. Although the throttling is to conserve battery life, this a bit sneaky from Samsung, as this tricks reviewers into overestimating battery life and consumers into believing they have the best of both worlds (brightness and battery life). There is a choice that can and has to be made.
Auto-Brightness (Adapt Display/Dynamic/Standard Mode)
Using auto-brightness instead of maximum brightness will actually enable a boost mode, which will activate under prolonged exposure to extremely bright light (I had to use my HTC One's flash at close range to simulate this).
Summary
The boost mode offers a 35% brightness gain, however this gain starts to plummet at around 60% APL, which means that the gain for web browsing and Google Maps will only be 5 to 15%
The peak brightness under prolonged sun exposure at 1% APL level is 478cd/m² (displaymate measured this at 475cd/m²). whereas the maximum brightness for pure white ends up at the unboosted level of 383cd/m²
Without Boost Mode, the brightness curve in a birghtly lit environment is exactly the same as the maximum brightness captured in my earlier graph.
The auto brightness -5/+5 radio button has no impact on the maximum brightness achievable - it will go full throttle if it has to. Only brightness at lower ambient light levels is impacted by this fine-tuning...
There is no Power Saving mode override in auto-brightness, and those browsers even benefit from the Boost Mode.
Just to put the graphs into perspective, I am showing the maximum reachable brightness for various Android applications:
Android Menu: 5% APL | Maximum Brightness: 465cd/m²
Android Menu with radio buttons: 10% APL | Maximum Brightness: 455cd/m²
OLED fiendly web site: 15% APL | Maximum Brightness: 445cd/m²
Random Gallery Picture: 40% APL | Maximum Brightness: 410cd/m²
Google Play: 60% APL | Maximum Brightness: 395cd/m²
Anandtech with zoom on picture: 70% APL | Maximum Brightness: 350cd/m²
Google Maps: 75% APL | Maximum Brightness: 320cd/m²
Whatsapp: 80% APL | Maximum Brightness: 305cd/m²
Android Contact List: 85% APL | Maximum Brightness: 295cd/m²
Google Results page: 90% APL | Maximum Brightness: 290cd/m²
Google: 95% APL | Maximum Brightness: 285cd/m²
Greyscale and Color Gamut (Film Mode)
RGB balance has a discernible green push above 50% brightness (less exposed in Anantech's review because Brian measures at 50% brightness rather than maximum)
Color Space is oversaturated even in film mode (consistent with Anantech's and Displaymate's findings)
Gamma will also get worse on content that has a high proportion of bright content, with brightness compression happening at the top end of the spectrum. For videos, it is therefore recommended to use 50% of maximum brightness or auto-brightness
White point color Temperature:
6410cd/m² in Film/sRGB Mode - again, this is at maximum brightness, the green dominance will be different at different brightness levels (as can be seen on the curves below)
6940cd/m² in Standard Mode, Dynamic Mode and Auto-Adjust Mode (I personally prefer that color temperature because it is more consistent across the whole scale, so the picture looks more harmonious)
Gamma is improved versus previous iterations but there is still a slight black crush and white crush happening at the extremities (nothing too major). The white crush will not be observed with smaller test patterns but will be worse for bright content! The black crush will be worse with Auto Tone on (to conserve battery, the transition into blacks is quicker).
Color gamut as expected is oversaturated. But what is more surprising is that it is oversaturated even in Film mode, although to a smaller extent. I went back to Brian's review, and this was also what he found. I believe two other reviews had different findings - but I may remember this incorrectly
Measurements in Film Mode
Color Space (Adapt Screen/Dynamic/Standard Mode)
Viewing Angles (Film Mode)
Summary:
Viewed directly, the display exhibits a green push in spite of near perfect color temperature
Viewing at an angle reduces green and red and increases blue
The most neutral white balances (Delta E of 2.8) can be obtained by viewing the screen at a 15° angle (you can do the test and notice how the green push disappears!)
The color temperature at this angle is further away from the 6500K standard than for direct viewing but it is still more neutral (shows the importance of RGB balance)
The following charts shows the RGB balance, correlated color temperature and Delta E for viewing angles of 0° to 40°.
This is an important lesson: sometimes it is preferrable to calibrate at a somewhat higher color temperature to improve the RGB balance (generally a blue push is less perceptible than a green push). However in this case, Samsung's calibration was most certainly to improve the overall brightness of the screen (green has a stronger luminance than red or blue).
Throughts and Recommendation to Devs for Kernel Calibration
Essentially, the adaptative brightness without power saving options is to fool regular gamma testing and make it look flat even though it isn't - again to conserve battery!
Using Average Picture Level patterns, to keep brightness constant across the greyscale, we can clearly see that the gamma is too high (2.4).
By reducing brightness as IRE levels increase, the display conceals the fact that brightness increases too slow across the full IRE spectrium - because the final brightness ends up being lower, regular test patterns will say that brightness at each IRE level is where it should be when in fact it lags behind. It only catches up with target brightness at 100 IRE because brightness is being throttled more with each IRE level.
For example, at 50 IRE, the theorectical brightness should be 21.46% of white brightness, except the white brightness at 50% IRE is higher vs. 100% IRE. What is important is not the 100% IRE brightness, though. because it is throttled and has no impact on intra-picture gamma.
What is important is the 50% IRE brightness, which is higher. So while regular test patterns lead you to believe brightness is where it should be and gamma is 2.2, in fact it is lagging behind for the full brightness spectrum.
So in conclusion:
We need to recalibrate gamma on this display by using APL test patterns - they are the only ones that should ever be used on displays with adaptative brightness where brightness is a moving target.
OR
We need to deactivate the adaptative mechanism (which would have the secondary effect of improving overall brightness)
But as long at the adaptative mechanism exists, we will never be able to have perfect gamma at all APL levels. If we choose to have perfect gamma at 50% APL, we will have brightness below target for low APL levels (since the 50% APL brightness will be lower than at lower APL) and it will be ahead of target for higher APL levels (since the 50% APL brightness will be higher than at higher APL levels).
So in essence, because of the adaptative mechanism, we can never have a perfect intra-picture gamma that works equally well at all APL levels.
The standard error will be smaller at lower brightness levels because the peak brightness range will be more narrow. But in boost mode the max brighness will be 70%higher than minimum brightness, so the standard gamma error at low APL and High APL levels will be higher, so black crush will be quite big for low APL and white crush will be quite big at high APL.
In a nutshell, if we want perfect gamma, we will have to acccept lower intra-picture contrast at lower APL and equalize brightness on the maximum achievable non-thottling 100% brightness. Since the display is very linear, this should yield us perfect gamma and RGB balance for all brightness levels that the user chooses between 0 and max user-selected brightness.
On plasma displays, throttling typically only happens above a certain brightness level. and it is enough to stay within that comfort range But the fact that brightness is being modulated for different APL levels on the S4 makes a good calibration that works at all APL levels impossible...
I can't believe how imaginative Samsung is when it comes to fooling reviewers. The display has potential, I just know that calibrating this thing with undefeated adaptative brightness will not yield perfect results - unfortunately.
The most pressing issue at the moment is the green push though and oversaturated colors, though. I am pretty sure that reducing color saturation will also impact greyscales and brightness on this display...A lot of fun coming our way
So basically the s4 is claiming a longer battery life through web browsing by dimming its screen automatically? I could already tell this, which is when I first bought a galaxy phone I downloaded another browser. I can't stand how Samsung handles the web in terms of the screen. Really annoying.
coming from the og one x
Isn't part of this issue due to thermal throttling? As amoled screens work at maximum load on while backgrounds, so could it therefore heat up more and thereby have to adjust the brightness?
Sent from my HTC One using xda app-developers app
Ddot196 said:
So basically the s4 is claiming a longer battery life through web browsing by dimming its screen automatically? I could already tell this, which is when I first bought a galaxy phone I downloaded another browser. I can't stand how Samsung handles the web in terms of the screen. Really annoying.
coming from the og one x
Click to expand...
Click to collapse
This is not only in web browsing, so this affects all browsers (though there may be different treatment for video, I would have to test using video patterns).
The really annoying thing is that the throttling mechanism can't be defeated, so let's say you want to check something really fast while in the sun, you can't even temporarily make your browser go brighter. But you're right that with the Stock/Chrome browser this is actualy worse.
I must say that I did not have other Samsung devices except the S2. I am interested in other user views on the S3 and Note II. Was the same observed? Was the clipping that bad? Those who installed the Perseus Kernel on their Note II, was this circumvented or was only the color temperature and color accuracy fixed? I heard from one user I met at the shops that when he used the Persus Kernel to correct the screen, his battery would get depleted.
A brightness cap at 250cd/m² is not acceptable for web browsing. But then a battery life of 3 hours screen time would not be acceptable either. It is a trade-off. Still, one would wish the user had a choice to boost the brightness for short periods of time.
Jme369 said:
Isn't part of this issue due to thermal throttling? As amoled screens work at maximum load on while backgrounds, so could it therefore heat up more and thereby have to adjust the brightness?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No thermal throttling is indicated with a message. This is more of an adaptative brightness mechanism, but much more aggressive than what can be observed on the HTC One (the One will vary between 400cd/m2 and 530cd/m² depending on the content).
This is the regular behavior for bright content handling.
You can actually observe this on your browser while browsing and when scrolling from content that is bright (text) to content that is less bright (darker picture) and vice versa, you will clearly see how suddenly the brightness increases and decreases (in real time). The same can be observed when you launch your browser. Coming from a less bright picture level into the browser will cause it to clip whites, so you will see it dim within the first second.
No such thing on my 9500, even compared to a HTC its bright in browser.
You must have a faulty unit or some setting that prevent full brightness in browser.
DocRambone said:
No such thing on my 9500, even compared to a HTC its bright in browser.
You must have a faulty unit or some setting that prevent full brightness in browser.
Click to expand...
Click to collapse
The pictures were not from me! They all behave the same. This is something I had observed in 4 different shops. This is something that others have reported. It can be observed in Anandtech's readings on the S4 review.
All I am doing is quantifying what users and testers, including myself, have observed. It is a generalized mechanism.
You can actually observe this on your browser while browsing and when scrolling from content that is bright (text) to content that is less bright (darker picture) and vice versa, you will clearly see how suddenly the brightness increases and decreases (in real time). The same can be observed when you launch your browser. Coming from a less bright picture level into the browser will cause it to clip whites, so you will see it dim within the first second.
Note that on mixed content with only patches of bright colors/white (e.g. page with pictures or video), white point brightness will be more around 300cd/m². This happens when the average picture increases.
puremind said:
The pictures were not from me! They all behave the same. This is something I had observed in 4 different shops. This is something that others have reported. It can be observed in Anandtech's readings on the S4 review.
All I am doing is quantifying what users and testers, including myself, have observed. It is a generalized mechanism.
Click to expand...
Click to collapse
Still, some setting/unit is clearly wrong. The brightness with a full white webpage is very high. Check settings again, turn off the adaptive screen settings etc.
Uh yea, turn off Auto Adjust Screen Tone in the screen settings.
Otherwise this is the CABC / content aware brightness control on the AMOLED controller. I'll have to check it later in the kernel.
AndreiLux said:
Uh yea, turn off Auto Adjust Screen Tone in the screen settings.
Otherwise this is the CABC / content aware brightness control on the AMOLED controller. I'll have to check it later in the kernel.
Click to expand...
Click to collapse
Yes the Auto-Adjust off improves the white clipping but does not solve the issue. It is still a 20% loss. Thanks for showing-up Andrei, as you are probably the most knowledgeable person in this forum regarding the trade-offs between brightness and battery on those AMOLED devices. My short testing on this device makes me worry that with Auto-Adjust and Power saving turned off, the S4 will run out of battery after 3 hours of web browsing (average white level at 250cd/m²)....Does this sound about right?
To what brightness level was the Perseus Kernel calibrated on the Note II?
That would be a high price to pay to have an equivalent browsing experience as on competing LCD devices!
This is the detailed analysis for all settings combinations (except auto-brightness, which would vary depending on environment light).
puremind said:
My short testing on this device makes me worry that with Auto-Adjust and Power saving turned off, the S4 will run out of battery after 2 hours of web browsing....Does this sound about right?
That would be a high price to pay to have an equivalent browsing experience as on competing LCD devices!
Click to expand...
Click to collapse
No, wrong, with all power savings off i loose 10% battery for each 45-50 min web-browsing session. (autobrightness +5)
No problem to get 6+ hours out of one charge
DocRambone said:
No, wrong, with all power savings off i loose 10% battery for each 45-50 min web-browsing session. (autobrightness +5)
No problem to get 6+ hours out of one charge
Click to expand...
Click to collapse
Auto-brightness+5 is very aggressive battery saving - it caps brightness at 145cd/m² in the sun! In terms of brightness, this is equivalent to having both power saving and auto adjust ON and run maximum brighness.
I agree that with this setup you can probably reach 6 hours, but this is quite conservative. Suppose you increase brightness to 250cd/m² (screen not completely white), would this then translate into 4 hours of battery?
The Galaxy S4 performs very well in high ambient lighting in spite of its typically lower screen brightness because it has one of the smallest screen Reflectance values of any display we have ever tested, and its more saturated colors can help cut through the reflected light glare. When Automatic Brightness is turned on, the screen brightness increases considerably at high levels of ambient lighting as mentioned above. The Galaxy S4 is then comparable or brighter than most LCD Smartphones.
http://www.displaymate.com/Galaxy_S4_ShootOut_1.htm#Table
DocRambone said:
No such thing on my 9500, even compared to a HTC its bright in browser.
You must have a faulty unit or some setting that prevent full brightness in browser.
Click to expand...
Click to collapse
One of this comparison pics was mine. And I had several S4 devices to test. They all behave the same way.
BoneXDA said:
When Automatic Brightness is turned on, the screen brightness increases considerably at high levels of ambient lighting as mentioned above. The Galaxy S4 is then comparable or brighter than most LCD Smartphones.
Click to expand...
Click to collapse
Tried that with three different units. In the most direct sunlight possible they increased brightness only a bit, not even remotely close to the ONE I'm afraid.
puremind said:
Auto-brightness+5 is very aggressive battery saving - it caps brightness at 145cd/m² in the sun! In terms of brightness, this is equivalent to having both power saving and auto adjust ON.
?
Click to expand...
Click to collapse
No, i use s4 without any problem outdoors, its much brighter than 145cd/m2
The brightness is rather high, much brighter than my Note2 in same conditions.
In direct sunlight all screens have poor visibility.
In the shadows the s4 behaves as good as the htc one.
And my findings is that 6+ hours screen on in well lit (outdoor) conditions is rather normal.
DocRambone said:
In direct sunlight all screens have poor visibility.
In the shadows the s4 behaves as good as the htc one.
Click to expand...
Click to collapse
Tested that on sunday and have to disagree completely. HTC ONE: Watching the VERGE Videos with sunglasses worked perfect in direct sunlight.
S4: Not even remotely possible without sunglasses. And the difference even in shady surroundings is very real.
slind said:
Tested that on sunday and have to disagree completely. HTC ONE: Watching the VERGE Videos with sunglasses worked perfect in direct sunlight.
S4: Not even remotely possible without sunglasses. And the difference even in shady surroundings is very real.
Click to expand...
Click to collapse
Lol, why would you look at videos in direct sunlight with sunglasses?
A more normal scenario is in the shadows and there the s4 behaves as good as the htc one.
DocRambone said:
Lol, why would you look at videos in direct sunlight with sunglasses?
A more normal scenario is in the shadows and there the s4 behaves as good as the htc one.
Click to expand...
Click to collapse
Because it was still very enjoyable on the ONE and not as stressful on my eyes. Don't mean to be rude, but did you actually had the chance to look at S4 and ONE at the same time in the shadows? I really doubt that.
And a normal scenario for me would be in the park, at the beach, shopping outside etc. as well as in shady areas.
I still got both devices here for today, might do some additional photos to prove the S4s lack of brightness outside (in every situation).
slind said:
Because it was still very enjoyable on the ONE and not as stressful on my eyes. Don't mean to be rude, but did you actually had the chance to look at S4 and ONE at the same time in the shadows? I really doubt that.
And a normal scenario for me would be in the park, at the beach, shopping outside etc. as well as in shady areas.
I still got both devices here for today, might do some additional photos to prove the S4s lack of brightness outside (in every situation).
Click to expand...
Click to collapse
I have access to a htc one also and even if it brighter in direct sunlight, its not better in the shadows, high brightness is not the only factor, low reflectance is as important.
BoneXDA said:
The Galaxy S4 performs very well in high ambient lighting in spite of its typically lower screen brightness because it has one of the smallest screen Reflectance values of any display we have ever tested, and its more saturated colors can help cut through the reflected light glare. When Automatic Brightness is turned on, the screen brightness increases considerably at high levels of ambient lighting as mentioned above. The Galaxy S4 is then comparable or brighter than most LCD Smartphones.
http://www.displaymate.com/Galaxy_S4_ShootOut_1.htm#Table
Click to expand...
Click to collapse
Yes, we all read that, but unfortunately that only true outside of web browsing, where you mainly see more mixed conent The Displaymate reflectance tests were conducted on color patterns which had much dimmer average picture level and therefore do not create white clipping. Also correct me if I am wrong but I believe they used a market app. which does not have as much clipping as the browser for some reason (well we know it's to put down a good web browsing battery test...).
So the Displaymate results cannot be transposed to most Smartphone applications, such as texting, Whatsapp. GPS Nigivation, Web Browsing. In those situation white point brightness gets severely clipped and this is what we see clearly in all the pictures. That's exactly the problem.
Smartphone manufacturers have become incredibly shrewed and inventive when it comes to thwarting poor benchmark results. Measuring brightness and battery life used to be so simple. Nowadays displays behave in ways that most reviews do not have the time or patience to study, so it is easy to be mislead.
Related
I was trying to lower the brightness very low to test how it would affect battery drain and it seems that the phone won't let 3rd party apps lower the brightness lower than what you can set it to, in the phone's settings. I tried an app called timerrific that lets you schedule various settings changes, but the phone seems to be overriding it. When I set the brightness to go down to 15% via the app, it does go very dim, but then immediately bounces back up to lowest level the phone's settings let's you set it at. Also, I had auto brightness off and the power saving mode off.
Has anyone been able to get the phone to go to very low brightness?
Thats a good question and would like the answer too... to me, the lowest brightness which must still HOG the battery as sometimes it seems to drain very fast with usage (and I have it on the lowest setting)... seems overly bright. I would without a doubt use it at a lower brightness to conserve energy depending on what I was doing at the time.
hey maybe its just the screen that makes it look bright
labbu63 said:
hey maybe its just the screen that makes it look bright
Click to expand...
Click to collapse
Not sure what you mean? For example, if I set the brightness to go down to 5% through the app Timeriffic, the screen will dim down to where I can barely see anything, but then it immediately raises back up to the lowest setting you can set in the phone's normal settings, which seems to me to be about 25-30%.
Yep
labbu63 said:
hey maybe its just the screen that makes it look bright
Click to expand...
Click to collapse
This is actually correct, the screen is what makes the "Automatic" brightness setting on the SGS phones look brighter than their LCD brethren. As we all know, currently all AMOLED displays use some kind of Pentile Matrix. All HTC devices (The N1 included) currently use RG:BG Pentile Matrix.
Do a google search on: "RGBG Pentile" and Samsung's site details it.
The SAMOLED display Samsung has made uses a new Pentile Matrix called RGBW:
Do a google search on: "nouvoyance" and it's the first site (sorry for the odd instructions, won't let new users post links )
Using the new RGBW, a white subpixel is introduced on top of the standard RGB stripe. From my reading, this allows the screen to achieve the same resolution to the eye with 33% less subpixels and is a brighter display in the process.
Asori said:
This is actually correct, the screen is what makes the "Automatic" brightness setting on the SGS phones look brighter than their LCD brethren. As we all know, currently all AMOLED displays use some kind of Pentile Matrix. All HTC devices (The N1 included) currently use RG:BG Pentile Matrix.
Do a google search on: "RGBG Pentile" and Samsung's site details it.
The SAMOLED display Samsung has made uses a new Pentile Matrix called RGBW:
Do a google search on: "nouvoyance" and it's the first site (sorry for the odd instructions, won't let new users post links )
Using the new RGBW, a white subpixel is introduced on top of the standard RGB stripe. From my reading, this allows the screen to achieve the same resolution to the eye with 33% less subpixels and is a brighter display in the process.
Click to expand...
Click to collapse
Good explanation, but are saying that no you can't dim it to low levels because it makes it look brighter than it is? If so, I don't buy it. I see it being dimmed to a low level. It just doesn't stay there.
Aldiko reader can get the screen even more dim
Sent from my SAMSUNG-SGH-I897 using XDA App
Also since there is less air gap in the new display, it is brighter.
Sent from my SAMSUNG-SGH-I897 using XDA App
This is just me speculating, but I'm thinking maybe the brightness setting is universal to android devices, except that it's calibrated to normal lcd. So the same voltage(or however they regulate the display brightness) on an LCD will look brighter on the Super AMOLED. For me, the dim setting on the auto-brightness seems too bright.
One thing I've noticed is I can take the brightness down to its lowest setting and it still seems bright..however on almost every phone I've used its like this.
The weird thing is on the Captivate I can open the browser, men then scroll down to settings and it has a brightness toggle there that takes it lower.
nbohmer said:
One thing I've noticed is I can take the brightness down to its lowest setting and it still seems bright..however on almost every phone I've used its like this.
The weird thing is on the Captivate I can open the browser, men then scroll down to settings and it has a brightness toggle there that takes it lower.
Click to expand...
Click to collapse
Yeah that does take it down lower than the home screen by a small amount. I put the browser brightness on the lowest setting and the global brightness on the lowest. Both auto brightness and power save are off. When I switch from the browser to the home screen, it brightens up a touch. So, it does go lower, but not all that much though, and it's only for the browser.
pjs2004 said:
Good explanation, but are saying that no you can't dim it to low levels because it makes it look brighter than it is? If so, I don't buy it. I see it being dimmed to a low level. It just doesn't stay there.
Click to expand...
Click to collapse
You can totally dim it more. In doing so, it will use even less power than an LCD screen at the same brightness setting.
Asori said:
You can totally dim it more. In doing so, it will use even less power than an LCD screen at the same brightness setting.
Click to expand...
Click to collapse
Yeah, that's what I thought was cool about this type of screen, but I still don't know how to to dim it below the the lowest setting in the phone's control panel (which isn't very low). 3rd party apps I've tried don't really work, or they work, but the phone immediately raises it back up. Are you saying you've dimmed it down to where you can barley see the screen, like 5-10 percent? That's what I'm looking for confirmation on. If so, what app did you use?
pjs2004 said:
Yeah, that's what I thought was cool about this type of screen, but I still don't know how to to dim it below the the lowest setting in the phone's control panel (which isn't very low). 3rd party apps I've tried don't really work, or they work, but the phone immediately raises it back up. Are you saying you've dimmed it down to where you can barley see the screen, like 5-10 percent? That's what I'm looking for confirmation on. If so, what app did you use?
Click to expand...
Click to collapse
I have used this app and seems to be pretty good, makes the brightness lower than system brightness.
http://www.androlib.com/android.application.com-curvefish-widgets-brightnesslevel-jDiB.aspx
i use brightness level too but the brightness goes back to the highest level when you plug the phone in and you cant use the presets on the widget anymore
sfernandez said:
I have used this app and seems to be pretty good, makes the brightness lower than system brightness.
http://www.androlib.com/android.application.com-curvefish-widgets-brightnesslevel-jDiB.aspx
Click to expand...
Click to collapse
I tried this app, and while it's a good app, it still doesn't make the screen go super dim. It looks to me like the lowest level (0%) is the same as lowest setting from the control panel. Zero percent should really be totally black.
Screen Filter
Here is your 100% working solution.
It doesn't work with the bright level, it applies a shade/filter to the screen. No matter what app you're using.
Set the bright to the lowest with your default system settings, because if you use a third party that goes below normal, with some apps like explorer, it set it to minimum allowed be system or whatever you set and then you will notice a setp up, shaded but a change.
I'm using it weeks ago and I found it's the best choice to suft the web at night. Also you can turn off softkeys lights
http://www.appbrain.com/app/screen-filter/com.haxor
flash speedmods new kernel.
Apparently the max brightness the phone can go is application dependent, in Chrome it's 600 nits and in photos or its 550 or something. Can we expect a mod or anything to make it even that is 600 across everything in the future?
I believe GSMArena mentioned there is CABC enabled, that will adjust the brightness dynamically based on the content onscreen. I suppose it is done to preserve battery life with "less" noticeable changes in brightness.
So far I havent really ´run into brightness issues outdoors on my device.. its not the brightest but isnt bad either.
Hi guys,
I have a cheap Chinese Cube T8Plus that I use exclusively to read comics and books at night.
It works really well for that use, but has 2 very annoying problems with backlight brightness that makes it less than ideal for low light use:
- with manual brightness, the minimum brightness is very high, and even with root and a software like brightness tweak, it stays the same (I can actually increase the minimum brightness, but not decrease it).
- with auto brightness, surprisingly on low light the screen gets a lot dimmer than with manual brightness, it makes a huge difference. But here too there is a big problem; the brightness does increase whenever I the tablet is exposed to higher light, but doesn't decrease back on low light, no matter what I do.
The only way to reset it back is to fully reboot the tablet.
I tried different roms to try fixing the issue, they all have the same behavior sadly.
Of course I know there are screen filter solutions like the twilight app, which I actually use, but it's not always enough, and kills the contrast a little bit too much sometimes.
So is there any other way to force the manual brightness to go lower, that might work for me?
If not can I override the auto brightness in some way?
Thanks
Hello ,
I observe that, my s22ultra in the same conditions (light intensity) make darker screen than my old note10+.
In my old phone (note 10+), the adaptive brightness works very well for my eyes (maybe excluding reaction speed - but never it wasn't too bright or too dark (in my opinion), never had to change any settings.
S22Ultra always make's screen too dark for me (in all lighting conditions) and i compare works of with my old note10+ and approved my suspicion that s22u makes screen darker than note10+ in the same conditions.
In general, the "jump / scale" of switching from light to dark and vice versa is good, but I would have to move the "threshold / level 0" action to a slightly brighter - if anyone understands what I mean - you can do something about it, someone has an idea ? Can I fix working of this function ?
What do you think about adaptive brightness in S22U?
Are you satisfied with its functioning?
See the differences compared to your old phone (what mobile it was)?
Thank you very much for any suggestions
I have two N10+'s and as far as I'm concerned adaptive brightness never worked right. Maybe better than my S4. I disable and use manual control, easier on the battery, display and retinas. It also varies in spite of not seeing huge changes in lighting conditions when sitting, I find this very distracting.
Best practice to limit display on in direct sunlight to seconds not minutes. Avoid using in direct sunlight whenever possible.
I try to limit brightness to less than 50%, 30-40% is typical. As a result after almost 3 years of heavy usage my original N10+'s display is still perfect with no signs of wear.
If I know I'll need to use the phone in bright conditions I will temporarily enable auto brightness sometimes. Otherwise I find it useless and generally too bright.
OLED displays gets burn-in almost exclusively in places where there are a lot of elements that stay completely white all the time. Most notoriously, status bar and navbar. For some people who text a lot, I have seen burn-in for the call and video call buttons, as well as individual keyboard letters.
My question is, is there an app, or a theming engine to be precise, that would allow the user to set a time interval, during which those high persistence elements of the picture could be dimmed over time? For example, user unlocks the phone and starts typing a message - navbar, statusbar, keyboard letters are all 100% white. They remain white, then after 60 seconds they start to dim, and after 120 seconds they are at 30% brightness. So when you're having long texting sessions, keys would be dim enough so you can make them out, but since they are not leaving your muscle memory you can type just as well as if it was at 100% brightness - but you save a lot of energy and thus substantially reduce the potential for burn-in. And if you're outdoors and can't make out what the time is after those 180 seconds, you gently pull down the notification bar and it resets to 100%. Something like that.
I can't be the first person to think of this. Moreover, I think AOSP devs realized this at around version 9 and dropped the overall brightness of the status/navbar to 80%, but it remains like that the whole time. What I am proposing would be infinitely more efficient. Anyone here knows something that's able to do that?
Avoid use in direct sunlight. Seconds not minutes if you do. Use manual brightness control and keep below 50%. Typically I comfortable use 30-40% indoors. Excessive brightness prematurely kills AMOLED displays needlessly. Excessive heat with the display on ie again direct sunlight should be avoided.
Use dark mode. The red pixels are longest live, blue the shortest; heavy blue or white usage will degrade the display the fastest.
Use icon packs and layouts that support pixel conservation. Rotate widgets and icons periodically.
This heavily use N10+ has over 8k hours on its display. There is no detectable fading, failed pixels, color inaccuracies, nothing; it remains perfect. It's a mirror image next to my new N10+ with less then 50 hours on it.
AMOLED displays can be very long lived. Everything on this homepage gets rotated slightly from time to time, even the page number icons ie 3 instead of 2.
{
"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"
}
johnnyboy041 said:
OLED displays gets burn-in almost exclusively in places where there are a lot of elements that stay completely white all the time. Most notoriously, status bar and navbar. For some people who text a lot, I have seen burn-in for the call and video call buttons, as well as individual keyboard letters.
My question is, is there an app, or a theming engine to be precise, that would allow the user to set a time interval, during which those high persistence elements of the picture could be dimmed over time? For example, user unlocks the phone and starts typing a message - navbar, statusbar, keyboard letters are all 100% white. They remain white, then after 60 seconds they start to dim, and after 120 seconds they are at 30% brightness. So when you're having long texting sessions, keys would be dim enough so you can make them out, but since they are not leaving your muscle memory you can type just as well as if it was at 100% brightness - but you save a lot of energy and thus substantially reduce the potential for burn-in. And if you're outdoors and can't make out what the time is after those 180 seconds, you gently pull down the notification bar and it resets to 100%. Something like that.
I can't be the first person to think of this. Moreover, I think AOSP devs realized this at around version 9 and dropped the overall brightness of the status/navbar to 80%, but it remains like that the whole time. What I am proposing would be infinitely more efficient. Anyone here knows something that's able to do tha
blackhawk said:
Avoid use in direct sunlight. Seconds not minutes if you do. Use manual brightness control and keep below 50%. Typically I comfortable use 30-40% indoors. Excessive brightness prematurely kills AMOLED displays needlessly. Excessive heat with the display on ie again direct sunlight should be avoided.
Use dark mode. The red pixels are longest live, blue the shortest; heavy blue or white usage will degrade the display the fastest.
Use icon packs and layouts that support pixel conservation. Rotate widgets and icons periodically.
This heavily use N10+ has over 8k hours on its display. There is no detectable fading, failed pixels, color inaccuracies, nothing; it remains perfect. It's a mirror image next to my new N10+ with less then 50 hours on it.
AMOLED displays can be very long lived. Everything on this homepage gets rotated slightly from time to time, even the page number icons ie 3 instead of 2.
View attachment 5721937
Click to expand...
Click to collapse
johnnyboy041 said:
OLED displays gets burn-in almost exclusively in places where there are a lot of elements that stay completely white all the time. Most notoriously, status bar and navbar. For some people who text a lot, I have seen burn-in for the call and video call buttons, as well as individual keyboard letters.
My question is, is there an app, or a theming engine to be precise, that would allow the user to set a time interval, during which those high persistence elements of the picture could be dimmed over time? For example, user unlocks the phone and starts typing a message - navbar, statusbar, keyboard letters are all 100% white. They remain white, then after 60 seconds they start to dim, and after 120 seconds they are at 30% brightness. So when you're having long texting sessions, keys would be dim enough so you can make them out, but since they are not leaving your muscle memory you can type just as well as if it was at 100% brightness - but you save a lot of energy and thus substantially reduce the potential for burn-in. And if you're outdoors and can't make out what the time is after those 180 seconds, you gently pull down the notification bar and it resets to 100%. Something like that.
I can't be the first person to think of this. Moreover, I think AOSP devs realized this at around version 9 and dropped the overall brightness of the status/navbar to 80%, but it remains like that the whole time. What I am proposing would be infinitely more efficient. Anyone here knows something that's able to do that?
Click to expand...
Click to collapse
I think you could look into immersive mode, It has many different names Another option talk in developer forums fr your phone , otherwise its hidden somwhere in your settings
Click to expand...
Click to collapse
Galaxy store>Good Lock family of apps>Quickstar
Is there a way to prevent burn in when using the phone in a bright environment? My job requires a bright environment.
Fytdyh said:
Is there a way to prevent burn in when using the phone in a bright environment? My job requires a bright environment.
Click to expand...
Click to collapse
No other than the mods I already mentioned. AMOLEDs have a finite lifespan that's proportionately shorter or longer dependant on brightness level. The brightest stars burn the fastest...
All you can do in that case is use at minimum needed viewing brightness and try to use in shaded areas.
Maybe use a work phone so you don't burn up your personal phone.
I am under the impression that none of you even read what I asked in full. I asked a very precise question regarding a particular way to mitigate burn in, nothing on HOW to to mitigate it, as I hinted in the name of this thread.
1. "Avoid use in direct sunlight." Excuse me? Phones are meant to be used outdoors, and they have been since the birth of the idea of a mobile phone.
2. I don't have a Samsung phone. What I meant was something more universal, like a Magisk module, or a root theme engine.
3. With due respect sir, everything you mentioned is more of a paranoid hassle than an automated instant-fix. What I proposed, on the other hand, is.
johnnyboy041 said:
I am under the impression that none of you even read what I asked in full. I asked a very precise question regarding a particular way to mitigate burn in, nothing on HOW to to mitigate it, as I hinted in the name of this thread.
1. "Avoid use in direct sunlight." Excuse me? Phones are meant to be used outdoors, and they have been since the birth of the idea of a mobile phone.
2. I don't have a Samsung phone. What I meant was something more universal, like a Magisk module, or a root theme engine.
3. With due respect sir, everything you mentioned is more of a paranoid hassle than an automated instant-fix. What I proposed, on the other hand, is.
Click to expand...
Click to collapse
Welcome to the planet. The more you run it in direct sunlight the higher the risks including outright failure. That sound better?
This isn't a backlight LCD* or a LED display. OLEDs are less robust than LEDs.
Due respect my mass... prudence isn't paranoia.
8+k hours here and no detectable damage of any kind.
* direct sunlight can fry LCDs too.
blackhawk said:
Welcome to the planet. The more you run it in direct sunlight the higher the risks including outright failure. That sound better?
This isn't a backlight LCD* or a LED display. OLEDs are less robust than LEDs.
Due respect my mass... prudence isn't paranoia.
8+k hours here and no detectable damage of any kind.
* direct sunlight can fry LCDs too.
Click to expand...
Click to collapse
Dude, nobody sets their phones to sunbathe for no reason. If the situation requires me, I'm using it the open sun. That hasn't damaged any OLED screen I used in the past 10 years. You ain't gonna convince anyone to rearrange widgets every week giving a meteor strike argument, especially with that attitude. Now please, are we over useless internet forum fights? I'm not negating any technical point you made, and what you did is certainly a way to deal with the issue, but it is objectively not practical for 99% of users.