Related
I found the perfect app! Its called, "Screen Filter" in the Market. It puts a virtual filter over the whole display to make it dimmer without impairing functionality.
This is perfect for our Amoled screens because power use is directly proportional to overall screen brightness not backlight brightness like lcds.
Also, don't set it on minimum or else you won't be able to see anything and have to wildly press the screen in a frantic attempt turn it off like me
HAHA this is exactly what I needed for my late night Pocket Legends sprees.
Perfect! This is exactly what I've been looking for, hate disturbing the GF when I can't fall asleep and need to check XDA
I used Screen Filter for about 3 days, and it seemed like the battery drained faster with it on than with it off. I think it's because it runs as a background application instead of simply modifying the brightness.
i haven't seen any complaints about ghosting so it may just be my phone but i have it really bad.
it's very visible when i scroll through my home screens because i have a near black background and use the red and white data widget.
it also makes text and such look horrid when i scroll through menus or web pages
deyna said:
i haven't seen any complaints about ghosting so it may just be my phone but i have it really bad.
it's very visible when i scroll through my home screens because i have a near black background and use the red and white data widget.
it also makes text and such look horrid when i scroll through menus or web pages
Click to expand...
Click to collapse
You probably have the brightness set extremely high or extremely low.
Whenever CM7 comes out for the D3, you can try adjusting render settings to improve the overall gamma of the screen. I'm guessing you're just more sensitive than most to a high-persistence screen, unless you have found a way to monkey with your refresh rate
rynosaur said:
You probably have the brightness set extremely high or extremely low.
Whenever CM7 comes out for the D3, you can try adjusting render settings to improve the overall gamma of the screen. I'm guessing you're just more sensitive than most to a high-persistence screen, unless you have found a way to monkey with your refresh rate
Click to expand...
Click to collapse
i've got a friend who has the same phone so i'll see if his is the same.
i haven't messed with the screen settings at all and have it set to auto brightness.
my last phone was the Nexus S with it's s-amoled screen. does this screen have a lower refresh rate then it did?
i know normal monitors have about a 60hz refresh rate but i know nothing about smart phone screens.
deyna said:
i've got a friend who has the same phone so i'll see if his is the same.
i haven't messed with the screen settings at all and have it set to auto brightness.
my last phone was the Nexus S with it's s-amoled screen. does this screen have a lower refresh rate then it did?
i know normal monitors have about a 60hz refresh rate but i know nothing about smart phone screens.
Click to expand...
Click to collapse
You've got me on the specs. I know desktop LCDs/LEDs are capable of higher refresh rates, but those aren't necessary for regular applications (read: non-bluray, non/gaming). Not sure where a smartphone like the D3 would land in the gamut between 29mhz and 120mhz.
deyna said:
i haven't seen any complaints about ghosting so it may just be my phone but i have it really bad.
it's very visible when i scroll through my home screens because i have a near black background and use the red and white data widget.
it also makes text and such look horrid when i scroll through menus or web pages
Click to expand...
Click to collapse
I've got a little...not exactly ghosting, but similar...on mine. It seems to me that the display controller for the pentile screen isn't outputting all of the color channels at the same time, so i end up with a red fringe or bloom around objects scrolling across the screen. Hopefully, a firmware update for the chip can fine-tune things.
rynosaur said:
You've got me on the specs. I know desktop LCDs/LEDs are capable of higher refresh rates, but those aren't necessary for regular applications (read: non-bluray, non/gaming). Not sure where a smartphone like the D3 would land in the gamut between 29mhz and 120mhz.
Click to expand...
Click to collapse
hmh i wish.
29mhz would be 29,000,000 refreshes per second XD
on computer monitors 60hz has been the norm for a long time. all my old CRTs use it. the newer 3d tvs and such generally need a 120hz refresh rate at the least.
even my dell inspiron 1420 has an lcd with a 60hz refresh rate and it can play bluray.
i remember there being one phone not too long ago that was limited to 30hz and most didn't like that one bit.
Xenoproctologist said:
I've got a little...not exactly ghosting, but similar...on mine. It seems to me that the display controller for the pentile screen isn't outputting all of the color channels at the same time, so i end up with a red fringe or bloom around objects scrolling across the screen. Hopefully, a firmware update for the chip can fine-tune things.
Click to expand...
Click to collapse
you may be right. i'll check another phone or two and if they have the same problems i'll just hope that an update or rom can fix it.
FYI: this has not that much to do with refresh rate, but more with response time. Response times are displayed in milliseconds most of the time.
For example, my uber-gaming-tft-display has a 2 milliseconds response time, which is very low and has almost no ghosting.
So, the question is: what is the response time of the qHD display in the droid 3.
I noticed the ghosting is way more visible on black backgrounds than on white. Good thing motorola changed the background in the android menu's from the default black to white.
I have noticed the ghosting too but have to admit that I actually like it. Especially while playing Emulators like FPSE and Gameboid it brings back the real PSP feeling. I know, its a weird oppinion.
rvschuil said:
FYI: this has not that much to do with refresh rate, but more with response time. Response times are displayed in milliseconds most of the time.
For example, my uber-gaming-tft-display has a 2 milliseconds response time, which is very low and has almost no ghosting.
So, the question is: what is the response time of the qHD display in the droid 3.
I noticed the ghosting is way more visible on black backgrounds than on white. Good thing motorola changed the background in the android menu's from the default black to white.
Click to expand...
Click to collapse
It's definitely got a slower rise-time than fall-time. You can see it on monochromatic icons when scrolling the app drawer in a launcher that uses a black background -- the leading edge is a blurry mess, while the trailing edge is fairly crisp. I'm guessing that the display controller simply isn't using any kind of overdriving to improve response time.
Also, to clarify my previous characterization of the blurring, it appears not so much that the red channel specifically is updating faster, as it is that the white channel is updating slower than all of the RGB channels.
Refresh rate has nothing to do with ghosting. Nearly every TV is actually 60, but they are falsely advertised at 600(plasmas) or use frame interpolation to achieve refresh rates above 60hz(LCD.) The only exceptions are 3D TVs. They actually refresh at 120 hz in 3D mode. Each eye sees 60hz. If they stayed at 60hz, each eye would see 30hz, and there would be noticeable flickering.
What effects ghosting is response time-the amount of time it takes a pixel to respond to a change in state. In layman's terms, how quickly it can go from one color to the next.
Plasmas and CRTs have near instant response times-it takes just nanoseconds for a pixel to change(actually, green phosphors take about 1 millisecond to change, blue and red phosphors change in nanoseconds). Nonetheless, plasmas and CRTs simply don't ghost(which is one reason why I prefer Plasma TVs). Part of this is because the pixels produce their own light. There is no backlight like an LCD.
But on LCDs, it takes the pixels many milliseconds to change. Though they are advertised between 2-6ms, the true response time of an LCD is usually at least 20 milliseconds. The Retina Display and qHD displays ghost because they have response times of 25-30ms. I can't recall why right now, but when you pack in a ton of pixels on a small screen, the response time is extremely high.
The refresh rate on phone screens is 60hz, which is actually why most are capped at 60fps, or you would probably see screen tearing.
GoogleAndroid said:
Refresh rate has nothing to do with ghosting. Nearly every TV is actually 60, but they are falsely advertised at 600(plasmas) or use frame interpolation to achieve refresh rates above 60hz(LCD.) The only exceptions are 3D TVs. They actually refresh at 120 hz in 3D mode. Each eye sees 60hz. If they stayed at 60hz, each eye would see 30hz, and there would be noticeable flickering.
What effects ghosting is response time-the amount of time it takes a pixel to respond to a change in state. In layman's terms, how quickly it can go from one color to the next.
Plasmas and CRTs have near instant response times-it takes just nanoseconds for a pixel to change(actually, green phosphors take about 1 millisecond to change, blue and red phosphors change in nanoseconds). Nonetheless, plasmas and CRTs simply don't ghost(which is one reason why I prefer Plasma TVs). Part of this is because the pixels produce their own light. There is no backlight like an LCD.
But on LCDs, it takes the pixels many milliseconds to change. Though they are advertised between 2-6ms, the true response time of an LCD is usually at least 20 milliseconds. The Retina Display and qHD displays ghost because they have response times of 25-30ms. I can't recall why right now, but when you pack in a ton of pixels on a small screen, the response time is extremely high.
The refresh rate on phone screens is 60hz, which is actually why most are capped at 60fps, or you would probably see screen tearing.
Click to expand...
Click to collapse
very informative, thank you! i knew what response times are but for some reason didn't draw the line between that knowledge and ghosting.
that would also explain why it's so noticeable to me after using the Nexus S for 9 months. hopefully (though unlikely) a new phone will come out here soon with a keyboard and high res screen with good response time.
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
dbozam said:
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
Click to expand...
Click to collapse
I don't have the flickering when not on auto and lowest setting.
However some apps can dimm the screen while loading.
On the TF700 the stock browser did that when loading a page but on the TF701 the brightness doesn't do that.
You have an ambient light sensor built into the device. It adjusts the brightness based on the lighting in your environment. It can't be turned off either.
Sent from my Transformer Infinity TF701T using Tapatalk HD
xRevilatioNx said:
You have an ambient light sensor built into the device. It adjusts the brightness based on the lighting in your environment. It can't be turned off either.
Click to expand...
Click to collapse
It can't be turned off? So when you turn on automatic brightness it just changes the brightness more drastically? This doesn't sound right.
Based on the other poster's response, I think I need to return this unit. The screen dimming/brightening happens to often and randomly to be part of my apps and I even noticed, in some apps, that just touching the screen causes a brightness change.
Even if this is by design, it is far too distracting.
dbozam said:
It can't be turned off? So when you turn on automatic brightness it just changes the brightness more drastically? This doesn't sound right.
Based on the other poster's response, I think I need to return this unit. The screen dimming/brightening happens to often and randomly to be part of my apps and I even noticed, in some apps, that just touching the screen causes a brightness change.
Even if this is by design, it is far too distracting.
Click to expand...
Click to collapse
Read it and weep my friend. Proof is in the pudding..
Sent from my Transformer Infinity TF701T using Tapatalk HD
dbozam said:
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
Click to expand...
Click to collapse
My 701 is doing this as well. Turned off auto brightness, turned off power saver, rebooted. When it comes back up the device acts like auto brightness is on, with screen brightness fluctuaating randomly. Turning power saver on and off again seems to solve it, but that behavior is very annoying - it's why I turn auto brightness off in the first place.
US SKU running 4.3 installed via ota, no root or unlock or anything - straight stock. Its also my second device, my original had a bad cable and wouldn't charge. Serial number ends in 072259.
Sent from my K00C using Tapatalk 4
Aaroneious said:
My 701 is doing this as well. Turned off auto brightness, turned off power saver, rebooted. When it comes back up the device acts like auto brightness is on, with screen brightness fluctuaating randomly. Turning power saver on and off again seems to solve it, but that behavior is very annoying - it's why I turn auto brightness off in the first place.
US SKU running 4.3 installed via ota, no root or unlock or anything - straight stock. Its also my second device, my original had a bad cable and wouldn't charge. Serial number ends in 072259.
Sent from my K00C using Tapatalk 4
Click to expand...
Click to collapse
I also tried turning power saver mode on and off and for me it seemed to improve the situation but not eliminate it. I am going to return the tablet and wait for the nexus 10.
Ugh, mine has been doing this, too. Can't believe there isn't a setting somewhere...
Mine is doing the same thing... glad that it's not just me, but this flickering is very annoying
Driving me nuts
I'm having the same problem and it's driving me nuts!
I'm quite convinced it's a software "feature" but currently there seems to be no way to turn it off?
It's one of those "Adjust brightness of the screen based on content" or "Changing LCD refresh rate and colors for power saving" but sadly it does it the wrong way around (This has been going on for a while now, manufacturers don't really get it). When there is a lot of bright content the brightness will rise and when there is mostly a dark screen it will fall.
Of course, this should happen exactly the other way around. When there is a lot of bright/white on my screen it should lower and when there is mostly black it should become brighter thus giving you more contrast but keeping the overall lux that comes off your screen the same...... My Intel graphics notebook does this too and it's very irritating. There they do it by manipulating the LCD screen and lowering the refresh rate and other tricks to save battery. First thing I turned off.
However way it goes though, you should be able to turn it off!
Quindor said:
I'm having the same problem and it's driving me nuts!
I'm quite convinced it's a software "feature" but currently there seems to be no way to turn it off?
It's one of those "Adjust brightness of the screen based on content" or "Changing LCD refresh rate and colors for power saving" but sadly it does it the wrong way around (This has been going on for a while now, manufacturers don't really get it). When there is a lot of bright content the brightness will rise and when there is mostly a dark screen it will fall.
Of course, this should happen exactly the other way around. When there is a lot of bright/white on my screen it should lower and when there is mostly black it should become brighter thus giving you more contrast but keeping the overall lux that comes off your screen the same...... My Intel graphics notebook does this too and it's very irritating. There they do it by manipulating the LCD screen and lowering the refresh rate and other tricks to save battery. First thing I turned off.
However way it goes though, you should be able to turn it off!
Click to expand...
Click to collapse
I'm having the same issue. I think it's the smart dimmer option Asus have used before but they forgot to include it in the Asus customised options. I'll have a dig through the ROM to see where it is stored.
I'm having this problem as well.
I have my brightness set to about 80%, Auto-Brightness Off, Power Save Off.
It is very annoying when reading magazines that have a lot of white background. My screen will be stable for minutes then, often on a touch, will change the screen brightness, seemingly by 5-20%.
I was just getting ready to return it, and thought I would check here to see of anyone else has this problem. Has any actually called Asus with this complaint? I would be interested to know if they see this as a hardware defect, software bug, or working as designed.
PS - I just placed a technical support request about this on the Asus Website. Here is my problem description:
Even with automatic brightness & power saving turned off, the brightness of the screen will change over time, often seemingly in response to a touch. (Reading Mode is Off as well.)
The period between changes can vary from several minutes to 30 seconds. It happens both while docked and undocked. It happens with apps and just at the launcher.
The amount of brightness change is 5-20% and it will often seem to step through some values before it stops at a particular one.
Given how fantastic looking the screen is, this unwanted fluctuation is particularly annoying.
I also own a TF201 and have not experienced this problem on that product.
Click to expand...
Click to collapse
sschlosnagle said:
I'm having this problem as well.
I have my brightness set to about 80%, Auto-Brightness Off, Power Save Off.
It is very annoying when reading magazines that have a lot of white background. My screen will be stable for minutes then, often on a touch, will change the screen brightness, seemingly by 5-20%.
I was just getting ready to return it, and thought I would check here to see of anyone else has this problem. Has any actually called Asus with this complaint? I would be interested to know if they see this as a hardware defect, software bug, or working as designed.
PS - I just placed a technical support request about this on the Asus Website. Here is my problem description:
Click to expand...
Click to collapse
I have this issue too but not a real biggie as the connection problems between dock and tablet.
Same problem!
dbozam said:
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
Click to expand...
Click to collapse
Thank you very much for creating this topic, because I was worried for my tablet too!
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
Snah001 said:
I have this issue too but not a real biggie as the connection problems between dock and tablet.
Click to expand...
Click to collapse
I heared a lot of people say I about this, but happily I seem to don't have it or I don't detect it. What is this dock problem about?
I suspect this is the same "smart dimming" feature that the 700 had.
improvius said:
I suspect this is the same "smart dimming" feature that the 700 had.
Click to expand...
Click to collapse
Yep me too and as soon as I root I'm going to see if the same fix will turn it off
There seems to be no way to disable this. Some believe it's the light sensor, but I've taped over mine with black electrical tape and tested and I don't see any difference in the behavior. Check our my Youtube video if you are a user who doesn't see the issue (look for threads in this same XDA forum).
I've finally been able to get someone at Asus to look into this and it's been sent to TW for review. I haven't heard anything back yet. I strongly recommend that other people who are annoyed by this (I find it tremendously distracting) to search on "asus escalation" which will bring up a special mailbox. Here is the link (although I do not know if the link will work for you). This should get looked at by someone with at least some ability beyond reading a script. If enough people do this, I think that they will fix it. Since you can temporarily override it by toggling smart saver on/off, it has to be fixable by software.
http://www.service.asus.com/#!escalation-mailbox/c1scx
derekk1 said:
There seems to be no way to disable this. Some believe it's the light sensor, but I've taped over mine with black electrical tape and tested and I don't see any difference in the behavior. Check our my Youtube video if you are a user who doesn't see the issue (look for threads in this same XDA forum).
I've finally been able to get someone at Asus to look into this and it's been sent to TW for review. I haven't heard anything back yet. I strongly recommend that other people who are annoyed by this (I find it tremendously distracting) to search on "asus escalation" which will bring up a special mailbox. Here is the link (although I do not know if the link will work for you). This should get looked at by someone with at least some ability beyond reading a script. If enough people do this, I think that they will fix it. Since you can temporarily override it by toggling smart saver on/off, it has to be fixable by software.
http://www.service.asus.com/#!escalation-mailbox/c1scx
Click to expand...
Click to collapse
I returned my tf701, waited for cyber Monday, and bought the Samsung note 2014 since the nexus 10 2 is so elusive. I put in an escalation request anyway and included a link to this thread in my complaint.
improvius said:
I suspect this is the same "smart dimming" feature that the 700 had.
Click to expand...
Click to collapse
I also saw this issue on my TF701. This seems a "feature" of Tegra SoC
Since Android Wear has the screen on all the time, and the Gear Live is AMOLED wouldn't burn in be an issue? the galaxy gears on display at retail stores have a bit of a burn in problem.
nolandynamite said:
Since Android Wear has the screen on all the time, and the Gear Live is AMOLED wouldn't burn in be an issue? the galaxy gears on display at retail stores have a bit of a burn in problem.
Click to expand...
Click to collapse
From what I've read, the watches are "always on" in the sense at the screen stays on, but the lighting is turned off. So instead of having to refresh the UI every time the watch is seen, it just turns the light on. Similar to a backlight for a laptop. Display models are usually always lit so they burn in due to the display being lit 24/7.
mitch27 said:
From what I've read, the watches are "always on" in the sense at the screen stays on, but the lighting is turned off. So instead of having to refresh the UI every time the watch is seen, it just turns the light on. Similar to a backlight for a laptop. Display models are usually always lit so they burn in due to the display being lit 24/7.
Click to expand...
Click to collapse
As far as I am aware, AMOLED has no backlight...that's sort of the point...every pixel "burns" individually.
CommanderROR said:
As far as I am aware, AMOLED has no backlight...that's sort of the point...every pixel "burns" individually.
Click to expand...
Click to collapse
I said similar because not everyone is familiar with the way AMOLED's work. But the same thing occurred at his Best Buy as would any modern portable display, device is constantly lit, and resulted in burn in.
I'm sure the user has an option to turn off the display if they choose to.
Sent from my SM-N900T using XDA Premium 4 mobile app
they also have dark mode and dim (holding palm over the screen) don't they?
hopefully there'll be something within all this to prevent issues.
Only LG G Watch has "Always-on" display, Gear Live and Moto 360 have a button to turn it on and yes in the Setting you have an option to adjust the brightness.
Hreidmar said:
Only LG G Watch has "Always-on" display, Gear Live and Moto 360 have a button to turn it on and yes in the Setting you have an option to adjust the brightness.
Click to expand...
Click to collapse
After watching like, 40 videos, I'm pretty sure that they all have always on. The button on the Gear Live and the 360 are to act as a physical way of turning off the display entirely as LG allows by covering it with your palm. But yeah, from what I've seen, the Gear Live goes into the same low power greyscale mode that the G Watch goes into, and both support wrist flicking to activate the display.
DrawnToLife said:
After watching like, 40 videos, I'm pretty sure that they all have always on. The button on the Gear Live and the 360 are to act as a physical way of turning off the display entirely as LG allows by covering it with your palm. But yeah, from what I've seen, the Gear Live goes into the same low power greyscale mode that the G Watch goes into, and both support wrist flicking to activate the display.
Click to expand...
Click to collapse
I did watch about 40 videos too lol and LG G Watch was the only advertised as "screen always on" as Gear Live has Super AMOLED display and even greater resolution than LG G Watch so the Gear Live would burn out in matter of hours.
LG G has 400 Mah battery, IPS display and lower resolution so it can withstand being "always-on" for at least 36 hours as advertised.
Hreidmar said:
I did watch about 40 videos too lol and LG G Watch was the only advertised as "screen always on" as Gear Live has Super AMOLED display and even greater resolution than LG G Watch so the Gear Live would burn out in matter of hours.
LG G has 400 Mah battery, IPS display and lower resolution so it can withstand being "always-on" for at least 36 hours as advertised.
Click to expand...
Click to collapse
Except, you know, on the official Google page, and in the videos that I've seen, the screen also just times out to a low power, black and white screen (referring to the Gear Live). Super AMOLED is more power efficient in idle / dark screens due to the nature of individual pixel lightning, so I don't really understand what you mean by the Gear Live would burn out in a matter of hours (they should be relatively the same from what I can tell).
Always on = standby (i.e low brightness, dark screen). It does not mean full brightness, always coloured watch face. No way in hell. If that was the case, why would the displays time out in what appears to be 5-10 seconds?
Yeah.. I'm going to wait on conclusive battery testing before making my purchase. I've got like a week anyways, might as well.
Also, I'm legitimately concerned about screen burn in now, given the nature of AMOLED.
DrawnToLife said:
Except, you know, on the official Google page, and in the videos that I've seen, the screen also just times out to a low power, black and white screen (referring to the Gear Live). Super AMOLED is more power efficient in idle / dark screens due to the nature of individual pixel lightning, so I don't really understand what you mean by the Gear Live would burn out in a matter of hours (they should be relatively the same from what I can tell).
Always on = standby (i.e low brightness, dark screen). It does not mean full brightness, always coloured watch face. No way in hell. If that was the case, why would the displays time out in what appears to be 5-10 seconds?
Yeah.. I'm going to wait on conclusive battery testing before making my purchase. I've got like a week anyways, might as well.
Also, I'm legitimately concerned about screen burn in now, given the nature of AMOLED.
Click to expand...
Click to collapse
i've been concerned about screen burn in from time to time as well (most recently with the gnex). but then i realized it is highly unlikely i'll have the device for long enough to achieve burn in and/or notice
I've been playing with my Gear Live for a couple of days, so here's what I can tell :
- The screen is "Always On" by default, which means it will get dimmer and switch to a black background on most watch faces (and for AMOLED, black means "off").
- You can set it to turn off completely.
- In order to dim it (or turn it off depending on the settings) you can either wait, cover the screen with your hand, or use the physical button... The button is not really practical and seems to serve absolutely no purpose since you can use the screen.
- I haven't noticed any burn-in at all yet
- I think I noticed that from time to time the facewatch (I'm using the one with the digital hour in the center and analog minutes, I think it's called "digitalog" ) switches a few pixels to the right or to the left. My guess is it is to prevent burn in, I know most plasma TVs do that too.
- I had a Galaxy S2 for several years before switching to a Nexus 5, and yes, the toip of the screen where the notification bar usually is was burnt-in (or rather I think the whole screen was burnt except for this black bar). It was noticeable on full screen apps but never bothered me. Even if it happens on the Gear Live I can't see it bothering me... It's not like I'll be watching movies on it...
So my guess is you should be fine... But if you're really worried you can always disable "Always On".
BlueScreenJunky said:
I've been playing with my Gear Live for a couple of days, so here's what I can tell :
- The screen is "Always On" by default, which means it will get dimmer and switch to a black background on most watch faces (and for AMOLED, black means "off").
- You can set it to turn off completely.
- In order to dim it (or turn it off depending on the settings) you can either wait, cover the screen with your hand, or use the physical button... The button is not really practical and seems to serve absolutely no purpose since you can use the screen.
- I haven't noticed any burn-in at all yet
- I think I noticed that from time to time the facewatch (I'm using the one with the digital hour in the center and analog minutes, I think it's called "digitalog" ) switches a few pixels to the right or to the left. My guess is it is to prevent burn in, I know most plasma TVs do that too.
- I had a Galaxy S2 for several years before switching to a Nexus 5, and yes, the toip of the screen where the notification bar usually is was burnt-in (or rather I think the whole screen was burnt except for this black bar). It was noticeable on full screen apps but never bothered me. Even if it happens on the Gear Live I can't see it bothering me... It's not like I'll be watching movies on it...
So my guess is you should be fine... But if you're really worried you can always disable "Always On".
Click to expand...
Click to collapse
How is the battery though? Think you can get through a solid day with heavy notification flow? That's all I really care about.
BlueScreenJunky said:
- I think I noticed that from time to time the facewatch (I'm using the one with the digital hour in the center and analog minutes, I think it's called "digitalog" ) switches a few pixels to the right or to the left. My guess is it is to prevent burn in, I know most plasma TVs do that too.
Click to expand...
Click to collapse
I have a Gear Live, and can confirm this is true. I've seen it on multiple watch faces.
DrawnToLife said:
Except, you know, on the official Google page, and in the videos that I've seen, the screen also just times out to a low power, black and white screen (referring to the Gear Live). Super AMOLED is more power efficient in idle / dark screens due to the nature of individual pixel lightning, so I don't really understand what you mean by the Gear Live would burn out in a matter of hours (they should be relatively the same from what I can tell).
Always on = standby (i.e low brightness, dark screen). It does not mean full brightness, always coloured watch face. No way in hell. If that was the case, why would the displays time out in what appears to be 5-10 seconds?
Yeah.. I'm going to wait on conclusive battery testing before making my purchase. I've got like a week anyways, might as well.
Also, I'm legitimately concerned about screen burn in now, given the nature of AMOLED.
Click to expand...
Click to collapse
I own a Gear Live and can confirm that it does indeed have an always on display (which can be toggled from settings) that dims to gray scale when not in use just like the G Watch.
At the same time I can also confirm that having my watch now just around 3 weeks has already showed some very minor signs of burn-in. Typically when in apps or settings. As I said though its very minor and not really noticeable unless you're looking for it. That said though it is there.
Also to clear up battery life the Gear Live can withstand 36hours of always on screen. While I typically charge my watch each night I have tested it and can get it to run from one morning through to the following night before the battery reaches 5%. This is with the Always-on display option enabled.
Are you guys leaving the screen on all night when you're sleeping? I know its not lit up all the way but like the dimmed version of the screen. Like I'm using the simple clock. You think its okay to leave that on all night? I'm thinking it'll be okay cause it'll gradually change over night so it's not technically sitting on one time for 7 hours.
Sent from my XT1060 using XDA Free mobile app
tu3218 said:
Are you guys leaving the screen on all night when you're sleeping? I know its not lit up all the way but like the dimmed version of the screen. Like I'm using the simple clock. You think its okay to leave that on all night? I'm thinking it'll be okay cause it'll gradually change over night so it's not technically sitting on one time for 7 hours.
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
I am a little worried about burn in myself so I turn the device off at night when I charge it. Even though the pixels should shift with the default watch faces I just think it's a safer bet to power it off.
When I put my nexus to charge, screen flickers like it needs more power. But when I increase the brightness it goes away or I can't see it. Tried a different power outlet as well. And I'm using the turbo charger.
Anyone experiencing this?
I just received my Nexus 6 and I notice a lot of screen flickering if I have the brightness set to low or up to 25% ...I see more flickering when I have the ambient lighting option enabled in settings. If I put the brightness to 50% or more it kind of eliminated the flickering...I am worried because I'm starting to question if this might be considered a defective display. Thanks
Yep, I got mine on launch day with T-Mobile. The screen flickers at lower brightness levels, at first I thought it was my eyes or I was just going crazy.
But it definitely is flickering, kinda similar to filming a fat old CRT TV with your video camera for your Halo 2 Super Bounce Montages (too a much lesser extent).
I'm a bit worried that it might burn out one day...
Also, my display is uneven.
I haven't looked into it yet, but maybe someone here could tell me -- should I contact Motorola or T-Mobile for a replacement? I have a feeling T-Mobile will charge me for it.
I get this too. Is it something we just have to live with?