There has been a lot of posts under the CM7 nightly thread about people not being happy with the auto brightness settings on the Droid Incredible, I was one of these people till I decided to take sometime and figure out how it works and now I would like to share the setup I've came up with. I'm sure that not everyone will like my setup, but I do think it's much better than the current defaults so hopefully it'll make some people happy.
I started out with a list of goals I wanted achieve for my setup and I think I did pretty well.
1. It needed to be easy on battery life
2. It has to work in all lighting conditions. It must be easily read in really dark rooms and in bright sun light.
3. I didn't want the screen brightness to "jump" it had to be subtle.
4. It has to be responsive to changing light conditions.
I want to give credit to byrong because with out his testing that he published here, I'm not sure if I would achieved all of my goals especially when it came to battery life. Also to the entire CM team, you guys are great and its much appreciated that you guys give us such support for the latest android OS.
Below you'll find all my settings, please feel free to comment and let me know how it works for you. Please remember I've only tested these settings in CM7 and that I have an AMOLED Incredible so I'm not sure how these settings work for people with the SLCD Incredible.
Settings>CyanogenMod settings>Display>Automatic backlight
Original:
{
"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"
}
Updated:
[Standard Disclamier: I take no responsibility for any damage your device may incur due to rooting, flashing custom roms or anything else you may do to it.]
Thanks for showing your entire setup. A lot of people have been sharing their levels without sharing their other settings.
I've been meaning to mess around more with the CM7 auto-brightness. The one day I tried it, I became very frustrated: it seemed that the sensor was only detecting a few ambient brightness levels and was especially sloppy in dark areas.
When I get some more time, I want to try out your settings and see how they work for me.
Hm, looks like I'll have to wait until tomorrow to hit the Thanks button; apparently I've already clicked it too many times today
NP at all.
You are absolutely right the sensor itself only picking up a few levels; 160,225,640,1280,& 2600 to be exact, from what I can tell. Thats why having filtering on is so important.
brightness levels have been a pretty frustrating subject for me, keeping the brightness to max is what I usually have to do, but its an obvious battery killer. Giving this a shot. thanks for the info!
Any update guys?? I want to gauge how well it is working for other people. For me its perfect I have not had to tweak it one bit yet.
Sent from my ADR6300 using XDA App
I went back to manual levels.
The filtering definitely helps, but unfortunately only delays the inevitable. They are just averaging the current raw readings against previous raw readings. This creates in-between values as you shift from one ambient lighting condition to another, but since the raw sensor only reads a fixed number of levels, even the filtered value will eventually shift back to one of the fixed raw levels.
userjf and slayher have been experimenting with ways to add more raw light levels via a custom kernel. Seems that the max number of readable levels is 10. Hopefully that will become a more commonplace mod that will make the auto-brightness more usable.
I was wondering how you got all those different levels to display? mine only displays about 5 is that because I am running a SLCD dinc versus an AMOLED dinc
Click the "set number of levels" button at the bottom, then input the number of levels you would like...
I will try these levels out, looks like they may work great, I will report back n let you know...
Sent from my ADR6300 using XDA App
I am giving these a try as well. The automatic brightness has been generally dissapointing on my Dinc with CM7 thus far
These settings are an improvement but they are not as good as they used to be on CM7 RC1 & the early nightlies. In the final version of CM7 they increased the brightness scale, see this thread for more details, you can see it now scales to 10240 instead of 2600 which makes my settings not as effective, it stay brighter longer than they did before but at its still an improvement of the defaults since the levels don't jump and down often. I recently upgraded to a Tbolt, so I don't have my Inc handy, once I do I'll see if I can dig up my modified settings for the final version of CM7 and post them here.
I am running CM7.0.0 if it helps
Nothing in .0.1 or .0.2.1 or .0.3 was compelling enough for me to go through reconfiguring everything.
I have been using these settings for a couple of weeks now and I am very satisifed withe the results . It helps saving the battery by dimming the screen in doors or low light situations and brightens the screen in high light situations making it easier to see the screen in sunlight
Works well for me. Much better than the stock levels.
I agree, these settings are much much better than what's in the latest nightly! Great work!
Sent from my ADR6300 using XDA App
The best settings I've found to date! Works as needed. Thanks for your time and effort figuring these settings!
sent by 1 of the many droids
Ok, I'm going to assume for a moment (yes, I know what happens when you assume) that I have something not set right. I have my settings exactly like the ones in the updated screenshot, yet my back light stays at a very low setting and never changes. I have the auto back light box checked in my settings, but I'm still not getting any brightness changes from one lightning environment change to another. I'm running CM7 RC3, no nightlies (which may be the problem). Not sure which screen I have but I will research how to tell.
Here are my settings on CM7. They seem to work for me pretty well except in bright daylight... This setup keeps my battery for quite a long time, even if I use it a bunch.
ucluglee said:
Ok, I'm going to assume for a moment (yes, I know what happens when you assume) that I have something not set right. I have my settings exactly like the ones in the updated screenshot, yet my back light stays at a very low setting and never changes. I have the auto back light box checked in my settings, but I'm still not getting any brightness changes from one lightning environment change to another. I'm running CM7 RC3, no nightlies (which may be the problem). Not sure which screen I have but I will research how to tell.
Click to expand...
Click to collapse
Make sure Automatic Brightness is checked in Settings->Display->Brightness or Automatic Brightness will not work at all.
PS: This came in handy tonight when I did a clean install of CM7.
Click the "set number of levels" button at the bottom, then input the number of levels you would like...
okey i'll try it help for my battery
thanks
Related
I just realized that this phone doesn't do anything visual when you have notifications, although when my battery got full the screen turned on briefly and made a noise. When I unlocked the phone I saw the "Your battery is fully charged. Unplug it now." prompt.
Does the screen normally turn on briefly for all notifications, or was this an exception? Is there some other visual notification indicator?
I'm only asking because this just seems alien to me, to have a phone that does not blink. Truth be told, I hated it when my G1 would blink various colors at me.
I will kinda miss this but at the same time it won't nag me like my girlfriend.
Sent from my SGH-T959 using XDA App
I know a few people have mentioned they are working on trying to use the soft key back lights for notification but not sure if anything will happen anytime soon. You can use sms popup that turns the screen on.
It is a little unusual, but change can be a good thing. The softkey light mod could be a good first step in the modding of the Galaxy S. I know it has me wanting to try it and get into coding/modding.
Plus, having to turn your screen on to see if you have notifications lets you enjoy that beautiful, vibrant (pun definitely intended) screen!
I think the easiest and pretty efficient way to go about it is like this...
The Super AMOLED wastes 0 energy when displaying blacks...then have a few blinking red pixels light up when there is a notification...
{
"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"
}
This should theoretically waste around the same energy as a real blinking notification light...
i need that on my phone asap lol
gTen said:
I think the easiest and pretty efficient way to go about it is like this...
The Super AMOLED wastes 0 energy when displaying blacks...then have a few blinking red pixels light up when there is a notification...
This should theoretically waste around the same energy as a real blinking notification light...
Click to expand...
Click to collapse
Wow! Super idea
Just make sure the icons are a little better looking, though
That was just to show off the idea in concept (I used the default photoshop symbols)..Icons can probably be improved but for highest battery saving probably best to stick to 1 color with the minimum pixel use as possible..
Sounds like an awesome idea, would LOVE to see something like this. I just picked one up, but will probably on the fence for the next 14 days haha. This is definitely a step towards me keeping it
Just realized there is also no music widget. Lame. Anyone know if Eliot Stocker's will work?
There's no music widget, but you do have music controls in the notif. pull down. I've been wanting that for a long time.
gigantic picture:
make it happen.
I wouldn't use the blue...OLED's blue deteriorate the fastest...not to mention the point of them being small was to conserve energy...
if you want to make it big it has to be in the most efficient form possible...
of course we can always have the user choose his notification picture...but ideally you'd want to use RED with minimum pixels as possible
Edit: Ok, it looks like someone did the Color saving efficiency proof for me on the Nexas One..see IT HAS TO BE RED..for best battery life....you pretty much use 2x less energy using RED over Blue
http://jsharkey.org/blog/2010/07/01/android-surfaceflinger-tricks-for-fun-and-profit/
Here is an example of what a good middle approach would be (for saving battery energy)
well, we just need to know how LONG it takes for the led's to deteriorate, cause we usually have these phones for at most 2 years, and we have to figure out how long the leds will last, i'm guessing they would for sure, last at least 4 years, i wouldn't say using blue is an issue, but you are right that red does use the least amount of energy, but again, we're gonna have to see how much energy these notifications even use on a real-life basis. the best thing would be to allow people to make their own notification images, this way we would have many beautiful notification images to choose from. but i DID exaggerate my notification though to show the higher extreme of a notification if battery life wasn't an issue.
Lieu10ant said:
well, we just need to know how LONG it takes for the led's to deteriorate, cause we usually have these phones for at most 2 years, and we have to figure out how long the leds will last, i'm guessing they would for sure, last at least 4 years, i wouldn't say using blue is an issue, but you are right that red does use the least amount of energy, but again, we're gonna have to see how much energy these notifications even use on a real-life basis. the best thing would be to allow people to make their own notification images, this way we would have many beautiful notification images to choose from. but i DID exaggerate my notification though to show the higher extreme of a notification if battery life wasn't an issue.
Click to expand...
Click to collapse
The phones come with Extra blue...but since blue deteriorates fastest and uses up most of the energy compared to other colors, it would make sense t avoid it if possible...
Ideally I agree it is best to let the user choose their own background while making low energy backgrounds available with information on about how much energy each background takes up on estimate...
Here are the deterioration times for OLED:
Red – 28 cd/A and >100,000 hrs to ½ luminance
Green – 67 cd/A and > 200,000 hrs to ½ luminance
Blue – 10cd/A and >50,000 hrs to ½ luminance
gTen said:
Here are the deterioration times for OLED:
Red – 28 cd/A and >100,000 hrs to ½ luminance
Green – 67 cd/A and > 200,000 hrs to ½ luminance
Blue – 10cd/A and >50,000 hrs to ½ luminance
Click to expand...
Click to collapse
so if the screen was on 24/7 for almost 6 years, your blue LEDs would be half as bright
i think we'll be okay folks.
turbosix said:
so if the screen was on 24/7 for almost 6 years, your blue LEDs would be half as bright
i think we'll be okay folks.
Click to expand...
Click to collapse
I can't risk that, sorry.
turbosix said:
so if the screen was on 24/7 for almost 6 years, your blue LEDs would be half as bright
i think we'll be okay folks.
Click to expand...
Click to collapse
But I like blue
I like all the ideas so far. I think making it customizable (or at least just not limited) would be good, there are those people who have to show off and will just need a new phone in a year any way, so they should be able to have a crazy notification (although you could have a large slow pulsing notification as well Maybe for if you are at a desk so it will be right in front of you and catch your eye quick).
I would like to point out though, are those the "Spec" numbers or the conservative numbers? Lots of reasons those number won't pan out usually, but still, if it was a blinking notification it would still probably go for at least 5 years straight, and at that point you obviously don't need a phone so why do you have blinking notifications?
So I just installed "the impossible game" on my brand new SGS2 and discovered there's some banding on the gradient in this game, which was not here with my Nexus One (AMOLED).
Has anyone else noticed that ? do you think it can be fixed later on (I know supercurio did some work on the first SGS's rendering) ?
edit : I'm only talking about the horizontal banding (the circular moiré is caused by the glass and visible only on the camera). Also I tried changing the brightness and background rendering but nothing helped.
{
"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 I'm the only one experiencing that ?
I hope my phone is not faulty because I've already rooted it so I guess I can't return it anymore :-/
BlueScreenJunky said:
So I'm the only one experiencing that ?
I hope my phone is not faulty because I've already rooted it so I guess I can't return it anymore :-/
Click to expand...
Click to collapse
not got that app i'm afraid...if it was just you then you can always flash back to the standard o2 sortware, removing the root. then using a jig remove the custom binary count...thus restoring your warranty
Rumble
Try checking the loading screen for the XDA app. It should be a nice gradient of brown but I remember it was HEAVILY banded on the Atrix.
Roger should chime in with more info on this =)
No need to use an app to test:
http://www.lagom.nl/lcd-test/gradient.php
I find it hard to believe that they've gone through all that to make the best display in the field and then limited it to 16bit colors (I believe super amoled has 24bit?)
Phew, it's not just me! The two things I'm disappointed with on this phone are the screen issues and the battery life. Other than that, it's incredible.
Let's hope for major firmware upgrades and dev support!
murklor said:
No need to use an app to test:
http://www.lagom.nl/lcd-test/gradient.php
Click to expand...
Click to collapse
Thanx for the link. And of course we don't need to test on an app, I just happened to notice on this particular game, and thought it was best to avoid comparing with the browser or gallery since they could be faulty themselves (the gallery used to cause banding on the Nexus One).
I really hope it can be fixed later... I keep reading the screen is fantastic, but it doesn't look so good now (maybe it's better than pentile Matrix though)
I don't have a SGSII but you are certainly not alone, I've read a lot about this banding issue - remember reading somewhere about the possibility that it may infact be 16bit at the moment.
dinan said:
Try checking the loading screen for the XDA app. It should be a nice gradient of brown but I remember it was HEAVILY banded on the Atrix.
Roger should chime in with more info on this =)
Click to expand...
Click to collapse
heh well i'll give my unofficial opinion is that your nexus one is running the latest 2.3.3 GB which fixed the nexus one's 16 bit color banding issue. did that game show banding on your nexus one last year?
anyway my opinion theory is the super amoled plus screen is still not 24 bit color yet, probably only 16 bit like the n1 was. i cant prove this though, so take as you wish.
the nexus one on the XDA app, the spalsh screen showed lots of banding for all last year. after the 2.3.3 update the banding is finally gone on the nexus one. and google admitted that the 2.3.3 update finally brought the n1 up from 16 bit color.
so my guess is the new amoled+ wasnt finalized yet, like the n1 originally, so the SGS2 is only 16 bit color in its current firmware version.
Very disappointing, I'll stay away from the phone for now and I hope they'll fix this as soon as possible! I feared that something like this would happen when I saw the GLBenchmark data (or something like that, which stated that it's 16-bit anyway). Good to hear that the N1 had the same problem and it got fixed, though!
flooki said:
Very disappointing, I'll stay away from the phone for now and I hope they'll fix this as soon as possible! I feared that something like this would happen when I saw the GLBenchmark data (or something like that, which stated that it's 16-bit anyway). Good to hear that the N1 had the same problem and it got fixed, though!
Click to expand...
Click to collapse
It really isn't that noticeable, you can't see it under normal use when you're holding the phone at a normal distance.
Totally liveable in the short run knowing that it will get fixed. From the speed and quantity of updates, I'm guessing Samsung's trying to repair the black eye they got for pretty much ignoring the SGS.
LarcusMywood said:
It really isn't that noticeable, you can't see it under normal use when you're holding the phone at a normal distance.
Click to expand...
Click to collapse
I disagree, it's very noticeable when you have any image that has a gradient. Every time I load up the XDA app, or fire up Stupid Zombies, it's right there plain as day.
Very annoying.
yeah. it's plain obvious. for that game, i have to set the quality to low, so that the banding disappears
omg, you got to be kidding me... even my android-loaded HD2, which is definitely suffering from a hardware limit of 65536 colors, shows less banding, much less shall I say, than this supposedly 16M colored monster?? :-(
this issue wouldnt stop me from keeping the SGS2. but there were lots of specific test images used on the nexus one to highlight the issue.
in fact here is the article with test images you guys can try on your SGS2. at the time of this article, the pentile pixel matrix was the highlight. but a year later the 2.3.3 update kinda proved that the banding was NOT related to the pixels, since its totally fixed now.
interesting read nonetheless.
http://www.displaymate.com/Nexus_One_ShootOut.htm
After testing a bit more, the photo I took in the first post is THE most obvious case of banding I could find. The gradient in xda, or the one at http://www.lagom.nl/lcd-test/gradient.php are not perfect, but they don't look THAT bad.
edit : And yeah, it's not enough for me to return the phone, and I'd buy it again knowing that, but it's still annoying, especially since they insisted so much on the quality of the SAMOLED+ screen.
It's purely a software bug. I'm almost certain the physical display can handle these gradients.
On my Nexus One/S if I view that sunset on mars photo in the stock android gallery I get all that banding. If I use another gallery like QuickPic, no banding at all.
It's a similar bug when setting home page wallpapers. You get quite a bit of banding doing it the stock way, but using wallpaper set & save to set the background eliminates banding.
It's not the screen, it's the rom, the browser is set/capped to 16 bits. The gallery however actually displays in 24 bits.
This issue can be fixed with a custom rom, it's probably set to 16 bits to allow smoother web browsing, which is totally stupid because the processor is totally capable of handling smooth browsing with 24 bits display.
There is color cap in WP7, currently with some tweak my Focus does display 24bit color in Pictures hub but 16bit in any browser related app. You people may want to try more.
Hey guys,
I've searched these forums quite thoroughly, and I haven't found any kernels/ROMs that allow for the display brightness to go past its minimum brightness settings. If you've had an iPhone, you'll know that the iPhone's minimum brightness is so much lower than the Nexus 4's. It makes using it at night so much easier on the eyes.
In all the threads I've come across, people just suggest to use Lux, or any of the other apps that just put a filter over the screen. These just make the screen grey, and just mute the colours - they don't actually reduce the brightness past 0.
I know that lowering the minimum brightness is possible; at least it is on other devices. On the Nexus 7, M-Kernel has a file that you can edit to change the panel's minimum brightness, and on my old Xperia Play, the RootDim app [https://play.google.com/store/apps/details?id=mobi.pruss.superdim&hl=en] allowed lowering the panel's brightness.
So, has anyone come across any kernels/ROMs that actually allow reducing of the panel's brightness past 0?
Oh, and I emailed the guy who made the RootDim app, and he mentioned something about pwm drivers. Does anyone know more about that?
Thanks!
I think I was able to do this on my old phone (HTC Wildfire) using Cyanogen. But no guarantees. Also, no idea if that is still supported or works on the N4...
If it's purely about using it at night I would recommend Screen Filter. I prefer not to mess with forcing my screen to use values outside the tried and tested boundaries set by the manufacturer.
Sent from my Nexus 4 using Tapatalk 4
For what it's worth, the "lowest" brightness by default is 5%. CM lets you adjust this down to "0%" but it seems autobrightness is a little buggy.
edit: nevermind. The range for autobrightness is 5-100 by default. When manually setting brightness, I believe "0" is possible on stock? I agree there are times a dimmer setting would do. Changing gamma settings can get you deeper colors and result in a dimmer looking display. Opposite of the graying you're referring to.
thank me later
https://play.google.com/store/apps/details?id=com.haxor
K3lthuzad said:
...or any of the other apps that just put a filter over the screen. These just make the screen grey, and just mute the colours - they don't actually reduce the brightness past 0...
Click to expand...
Click to collapse
bodom_hc said:
thank me later
https://play.google.com/store/apps/details?id=com.haxor
Click to expand...
Click to collapse
or never
I'm wondering about this too, in bed at night the screen is too bright on the eyes which makes the reading time much less,
on amoled screens its great due to no backlight which doesn't make the eyes tired,
there must be a way to reduce the backlight, but it may make the backlight flicker if undervolted, which would be worse on the eyes
republicano said:
I'm wondering about this too, in bed at night the screen is too bright on the eyes which makes the reading time much less,
on amoled screens its great due to no backlight which doesn't make the eyes tired,
there must be a way to reduce the backlight, but it may make the backlight flicker if undervolted, which would be worse on the eyes
Click to expand...
Click to collapse
Have you tried playing with the gamma settings and dropping the brightness down to 0 manually (autobrightness only goes down to 5%).
Halfbreed is pretty decent and results in a "dimmer" display without washing/graying everything. Only problem is under daylight, it's not effectively as bright.
I'll try messing with the brightness and gamma settings. It's a shame there isn't a better alternative right now.
Maybe, in the future, a developer makes a kernel with this built in (if possible). Fingers crossed! :/
For what it's worth, I think you'll find 0% brightness and halfbreed to be exactly what you're looking for.
Download twilight and try it. It has an option to lower the screen brightness further...
Sent from my Nexus 7 using xda app-developers app
Bumping my own thread:
I talked to the Nexus 7 (2012) kernel dev who managed to lower the panel minimum brightness, and he pointed me toward this:
https://github.com/CyanogenMod/lge-...ch/arm/mach-msm/lge/mako/board-mako-display.c
I'm hoping a Nexus 4 kernel dev will see this (or someone who knows what to do with it). He said it might be possible to do on our displays. Also, go check out M-Kernel if you still have a 2012 Nexus 7.
So, we just need to chance it and compile the kernel?
{
"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"
}
Sent from my Nexus 4
We can try. I just don't know how to 1. Change it and 2. Compile a kernel LOL
I will try to do it, will post here if it works
Sent from my Nexus 4
Today I compared two Moto G (mine with german KK, the other one from my mother with 4.3). Surprise: minimum/maximum brightness is higher in KK. This means that SOC time will be reduced at the end of the day for most users... Can't complain though, if I got 6 SOT on 4.3 now I get around 5h on KK, which now makes sense because I didn't understand what happened.
It's just to see if anyone else noticed it as well, as it's easy to see.
Sent from my XT1032 using Tapatalk
is this also the case for automatic brightness? and does the brightness slider work together with automatic brightness, or are they separate options like in 4.3? thanks
rioachim said:
is this also the case for automatic brightness? and does the brightness slider work together with automatic brightness, or are they separate options like in 4.3? thanks
Click to expand...
Click to collapse
Automatic brightness is also higher, yes. With respect to 2nd question, it's like in 4.3, you choose whether to use automatic brightness or choose the level of brightness you want:
{
"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"
}
tyrexs said:
Today I compared two Moto G (mine with german KK, the other one from my mother with 4.3). Surprise: minimum/maximum brightness is higher in KK. This means that SOC time will be reduced at the end of the day for most users... Can't complain though, if I got 6 SOT on 4.3 now I get around 5h on KK, which now makes sense because I didn't understand what happened.
It's just to see if anyone else noticed it as well, as it's easy to see.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Correct me if I'm wrong
But
1) On Moto G Kit kat makes the screen brighter > This means the screen is brighter > This will cause battery life OVERALL to fall... right? compared to 4.3 jelly bean
I find the screen brightness perfect for my needs right now at 4.3
Ummm
This is one area where the iPhone definitely wins.
Give users the ability to control the overall level of auto brightness.
Sent from my XT1032 using Tapatalk
That explains some things...
Can anyone check in 4.3 if the power consumption of the screen at the lowest brightness level is lower or the same?
Which app is that, let me know and I will test.
Bear in mind though that to really test you would need to use the same phone on 4.3 them upgrade it to 4.4. The reason is that each phone could possibly have it's screen calibrated slightly differently , ie maybe the OP's two phones would have different brightness even if both running the same android version.
However I do appreciate there is a (perceived) difference in screen time in the for the OP. But maybe its something else other than the screen in kitkat that is draining the battery quicker.
scott_doyland said:
Which app is that, let me know and I will test.
Bear in mind though that to really test you would need to use the same phone on 4.3 them upgrade it to 4.4. The reason is that each phone could possibly have it's screen calibrated slightly differently , ie maybe the OP's two phones would have different brightness even if both running the same android version.
However I do appreciate there is a (perceived) difference in screen on the for the OP.
Click to expand...
Click to collapse
It's called PowerTutor https://play.google.com/store/apps/details?id=edu.umich.PowerTutor&hl=es
I get same results on 4.3, ie its showing figure of 300.
But I don't trust the results. If I switch to auto brightness the graph still keeps churning out the same figures even though my screen brightens. Same if I use full brightness then switch to auto - new stats keep saying the same figure as on full.
??
One word lux
install https://play.google.com/store/search?q=lux&c=apps either lite or paid for
Ian
In GravityBox you can assign a new auto-brightness level.
I don't doubt this is true. But my battery is even better on kk so I'm a little shocked.
Sent from my XT1032 using Tapatalk
t-bon3 said:
This is one area where the iPhone definitely wins.
Give users the ability to control the overall level of auto brightness.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
New Samsung phones allow the same.
Sent from my XT1032 using xda app-developers app
I don't understand again why they have made such a change for the worse in this area if it is true. I cannot detect a difference in brightness at the moment.
ijen0000 said:
One word lux
install https://play.google.com/store/search?q=lux&c=apps either lite or paid for
Ian
Click to expand...
Click to collapse
This ^
Sent from my Moto X cellular telephone...
I have the same impression with my girlfriend phone, but it isnt because the KitKat! Its hardware.
There are some units that the screen looks more pinkish (you can see when is turn off) and there others with a blueish screen.
The fist one has lower brightness,you can see in white pages.
There are probably different screens in different batches of the phone.
I find the screen too bright with auto mode on both JB and KK. I have been using lux (with default settings) for a few weeks now and it's great.
Sent from my XT1032 using xda app-developers app
Hey guys!
If you've been using the LG G3 for a while now you're probably heard of the oversharpening problem. While I'm not sure how many of you care about this, I have seen quite a few discussions about this problem on the forum.
I made a thunderclap petition to hopefully get LG's attention and get them to release an update that either removes the sharpening or allows us to toggle it on or off.
http://pocketnow.com/2014/07/22/lg-g3-sharpening
Thanks in advance to everyone who decides to participate.
This is another one of those 'problems' I fail to see, much like the 'lag'.....
MalekoUK said:
This is another one of those 'problems' I fail to see, much like the 'lag'.....
Click to expand...
Click to collapse
Ya i agree, I think its mostly psychological, one of those once you see it you cant unsee it, like a dead pixel.
I am running my phone on paranoidAndroid and it doesnt have sharpening and I don't see the difference , both look great
Its obviously there, even in TWRP, if you cant see it don't complain when other people can. It IS there.
Not too convinced about this thunderclap site as I dont like to share this stuff on my social accounts, but you have my support.
This sharppening is so stupid I cant even find words to describe it.
I guess it is here to trick clueless people into seing a difference with other screens ? :s
sooti said:
Ya i agree, I think its mostly psychological, one of those once you see it you cant unsee it, like a dead pixel.
I am running my phone on paranoidAndroid and it doesnt have sharpening
Click to expand...
Click to collapse
Id love to see this in a photo, could you please show us a photo of the screen with a sharpen test or black text on grey background?
What sharpening?
Vivasanti said:
What sharpening?
Click to expand...
Click to collapse
That glow/outline you see around, for example, black letters on gray background.
I can't believe there's somebody who can't see it. Check your eyes or maybe there's another display model/manufacturer?
No sharpening no lag here D851. I really dont think a petition would solve this so called issue any way. Good luck though.
denis111 said:
That glow/outline you see around, for example, black letters on gray background.
I can't believe there's somebody who can't see it. Check your eyes or maybe there's another display model/manufacturer?
Click to expand...
Click to collapse
Not everyone have this... Like me and the other guys...
Been looking for that over sharpening effect with no luck... D855 32GB
I am fairly confident that there are different quality display panels out there, the sharpening issue seems to be linked to this (which also appears to be linked to brightness levels).
Those without the issue have displays that can go to brighter levels, those with the issues tend to have dimmer displays (even on max brightness).
Those without the issue only see the issue if they go to 'sub-zero' brightness levels with an app like Lux.
My belief is LG realised that some panels were poor(er) so adjusted the sofware to assist.
If anyone can't see it, use lux to reduce brightness a bit below zero and have a look at a text heavy webpage; its awful.
Try not using lux, maybe thats the issue... Who needs below 0 brightness?
Using LUX is not a problem, it is a very good app.
If you go below 0 then moan that is your own fault, going below 0 is not a function the phone is designed to do and when you "mod" you do so at your own risk.
I do go below 0 for night mode, but you don't see me on here moaning about sharpening issues.
______
That being said, some people (not me) do have issues with sharpening when their phone is above 0, but I believe this is because their phones are naturally darker, so their say 10 brightness might be the same as my -10, which is why they are seeing sharpening in 'normal' conditions when I am not.
What's brightness got to do with it? Its just as obvious at 100% as it is below 0.
All G3s have it, some people just cant see it, if you cant think yourself lucky.
ChrisM75 said:
What's brightness got to do with it? Its just as obvious at 100% as it is below 0.
All G3s have it, some people just cant see it, if you cant think yourself lucky.
Click to expand...
Click to collapse
I'm OCD with anything like this, and It ain't present on my G3
ChrisM75 said:
What's brightness got to do with it? Its just as obvious at 100% as it is below 0.
All G3s have it, some people just cant see it, if you cant think yourself lucky.
Click to expand...
Click to collapse
"all g3's have it"..... no they don't at least not at normal operating levels.
If my display is anywhere between -2 and +100 brightness there is no sharpening effect at all, no glow, no weird text no nothing it is a perfect display - this is a fact, not my eyes.
if I go to around -4 you can see it until I go down to about -10 then it stops again.
I am not questioning the issue, I have seen and compared my display with others who do have the problem and it can be a real issue, but not everyone has it.
As for what does brightness have to do with it, I am trying to find out what the differences are between those that have the issue and those that don't and the only common denominator is the fact that all the displays that have the issue cannot go as bright as those that do not have the issue.
e.g. 100% brightness on my phone will be significantly brighter than 100% on someone who suffers from oversharpening.
This is also why when the G3 was first released there were lots of threads on here about the display being too dim.
Then take a picture and prove it. Its on every variant, every firmware. Its there.
ChrisM75 said:
Then take a picture and prove it. Its on every variant, every firmware. Its there.
Click to expand...
Click to collapse
because variants and firmware doesn't alter the quality of the LCD panel!
are you not reading? There are plenty of people here on XDA who say they have no issue, including quite a few with very high credibility levels, who have nothing to gain from lying.
And sorry I cannot currently take a picture as I am not in the habit of carrying a second camera device around with me.....
Lennyuk said:
because variants and firmware doesn't alter the quality of the LCD panel!
are you not reading? There are plenty of people here on XDA who say they have no issue, including quite a few with very high credibility levels, who have nothing to gain from lying.
And sorry I cannot currently take a picture as I am not in the habit of carrying a second camera device around with me.....
Click to expand...
Click to collapse
Does it appear if you take a screenshot (Power + Vol Dwn)?
I have a rogers D852 and tried to replicate the Black text on gray background and I don't see it. Brightness on 100% but I normally keep it at Auto.
{
"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"
}
Its got nothing to do with the LCD panel quality, its an artificial post processed effect, its nothing to do with the hardware. Ive seen the phones of some people who say they dont have it, they have it! I bet if I saw your phone id see it at all brightness levels. Its less obvious at low brightness, but thats just a natural result of the dim display, its still there.
I don't care about 'credibility'. Just because someone is good at making ROMs or whatever it doesn't mean they have good eyes. They have the effect, they just don't notice it. There is no other explanation for why LG released the phone with this effect, its hideous to those that see it.