Database Develop

My Nexus One has Screen Burn In of Notification Bar

i just noticed that my 1 month old nexus one has the notification bar burnt in. go to landscape view in the browser, load a white background like google.com, and sure enough i can see very faintly the notification bar.
i've always kept the display on auto brightness. i'm very curious to hear if anyone else checks their screen if they have the same issue. the phone is only 1 month old, maybe 2 at the tops, so its very strange for this to happen. anyone else?

Had mine since end of March. No burn-in or any type of ghosting. I have my screen time-out set to 30 seconds. I wonder if that's got anything to do with it.

that's weird. my time out has always been at the default of 2 minutes. surely that isn't too much different though. 1.5 minutes shouldn't make or break it.

RogerPodacter said:
that's weird. my time out has always been at the default of 2 minutes. surely that isn't too much different though. 1.5 minutes shouldn't make or break it.
Click to expand...
Click to collapse
how bad is it? Is it possible to show us a picture?

its not too bad, but definitely there. the concern is how new this phone is. what happens after 6 months?
I'll try to take a pic later, but don't have a good camera on me.

RogerPodacter said:
its not too bad, but definitely there. the concern is how new this phone is. what happens after 6 months?
I'll try to take a pic later, but don't have a good camera on me.
Click to expand...
Click to collapse
Definately, you should give htc a call and tell them whats up. No rush on a picture.

AMOLED displays are worse for burn in than old CRT's, so br interesting to see how these fair
Got mine in late Jan and no sign of it.

RogerPodacter said:
that's weird. my time out has always been at the default of 2 minutes. surely that isn't too much different though. 1.5 minutes shouldn't make or break it.
Click to expand...
Click to collapse
Can't say either way if 1.5 minutes more of screen-on time can create the burn-in. But compared to the standard 30-sec time-out on most phones (some have 15 sec), 2 minutes is pretty long. You may want to set it to a shorter time-out duration.

you REALLY have to look close to see it. I tried it on black screen and you can't see it all. except in landscape the notification bar switches so at the very left inside the bar you can see the small faded line of the portrait bar.
i don't care enough to call HTC for any type of exchange or repair. I've heard the horror stories of their service too!

I have slight burn in on mine too. It's expected and I doubt the screen time out has anything to do with it. Keep in mind that any use of the phone the notification bar usually stays in the same place. Sometimes I have maps nav going on and that alone keeps the display on for the length of a car trip.
Also you guys can test by getting Dead Pixel Detect from the market and cycling through a few different colors.

well I'm not gonna get all worked up about it. sucks it happened so soon, hopefully it doesn't get worse. I'll try that dead pixel app just to see.
I'll take a pic shortly, but I don't know if it will actually be visible from a photo.

thats bad if its true....still a new phone with this problem already? wow..mine is less than a week old ...I will keep an eye out for it though, and if anyone has a solution that would be nice...

Drawing white on AMOLED requires much more than drawing black.
One more reason for using Desire (or a black notification bar theme)

I have two Nexus One's. The first was the Tmobile version which I used on ATT EDGE. That device has the purple tint issue and also has some burn in(uneven wear)where the notification bar is. Unfortunately I ran it with the brightness at 100%, 24-7. Now, it is very slight, but it is there.
I also have the 3G ATT version and it has no purple tint and has no burn in(uneven wear) yet and I've used it more now that I did the EDGE version. BUT, I never run this one with 100% brightness unless I have to.
Also, it is better to run at very low brightness for the first say hundred hours because there is a sharper dropoff in brightness half life during that time, making burn in(uneven wear)detectable with the human eye more likely to occur.
At the end of the day, for my situation, I blame myself for running at 100% brightness. I should have known better. LCD, with as long as they have been around, have innovated to the point of having very long half lives making burn in possible, but very rare. I was operating the way I always had with mobile devices. BUT, with these new screens, new care must be taken until AMOLED matures with higher brightness half life.

100% brightness I understand, but auto setting and this still happened in a month?
that pixel detector app definitely shows the burn in. I can see the icons too for 3g, signal meter, M from the pm time stamp, etc.
I guess there's no way to fix other than replace the screen? cause I'll change my notification bar to black if I had known this could happen.
I wonder what I should do...repair, HTC warranty, live with it, etc

I have the same problem. t-mobile nexus one. Happened about 2 months after I first got it. HTC replaced it. And it happened again on the new one. I keep it on 100% brightness pretty much all the time except at night. Doesn't bother me much though. I hardly use my phone in landscape and it's only on white backgrounds.

RogerPodacter said:
100% brightness I understand, but auto setting and this still happened in a month?
that pixel detector app definitely shows the burn in. I can see the icons too for 3g, signal meter, M from the pm time stamp, etc.
I guess there's no way to fix other than replace the screen? cause I'll change my notification bar to black if I had known this could happen.
I wonder what I should do...repair, HTC warranty, live with it, etc
Click to expand...
Click to collapse
If you get a new one just remember that even with a black notification bar, you're at risk. You will also need to run dark or black backgrounds to stay even with the black bar. Otherwise you will end up with a very bright bar and the rest of the screen will look yellowish/grey compared to it. It's always about making sure all the pixels are as evenly worn as possible. Another thing you can do is switch to a black notification bar now and run bright backgrounds and you can reverse some damage. It will never be perfect but you can get the wear more even again thus making the issue even less noticeable than it already is.
I agree about auto setting should have prevented this. At least you would think, but I'm no expert.
Several more things that can be done to help prevent this issue: if browsers or apps you use have the option to turn off the notification bar, use it. The more you can keep that notification bar off the screen, the more evenly you can wear the screen. Also, set your screen timeout to a shorter level. I used to use two minutes but now I use 30 seconds. The time that the screen is on and the bar is on the screen add up and can eventually contribute to uneven wear, and it's just wasted time waiting for the screen to timeout.

i'm seeing some faint burn in too

I don't feel so bad since I'm not the only one.
even with a black notification bar you would prob need white letters which would still burn in the white letters.

why the hell did I read this thread... lol mine is slight but I have some and I didn't notice it before because the only time I'm in landscape is in navigation most of the time.

Effect of battery life if I use an app like NoLED 100% of the time?

Ever since I met the LED notification, I've fallen in love with it and I'm sad to see that the Nexus 6 is leaving it out. Since it has an AMOLED screen, I'm thinking what would it be like battery life wise if I left the display on to always show notifications (if there is one)?

well.... with Ambient Display, the screen will pulse on every so often with just enough pixels to show the notifications you have (or at least that's how i'm understanding it'll work).

elementaldragon said:
well.... with Ambient Display, the screen will pulse on every so often with just enough pixels to show the notifications you have (or at least that's how i'm understanding it'll work).
Click to expand...
Click to collapse
i think that's how it works as well but most of the time, i'm not near my phone and i just want a quick glance over to see if there are any notifications.

It's hard to say, really. I'm running one of the AOSP Lollipop builds on my Nexus 5 right now... but can't exactly compare that to the Nexus 6, since the N5 doesn't use an AMOLED screen. Every time i see Ambient Display turn on, the entire backlight is on, too.
With that said.... even with an AMOLED screen, i can't imagine leaving the screen on constantly being a good thing for battery life.

Hopefully there's at least a charging led someone can hack to use as regular led. Worked before...

frigidazzi said:
Hopefully there's at least a charging led someone can hack to use as regular led. Worked before...
Click to expand...
Click to collapse
Does someone have information about that? Is there any charging LED?

Dabarr said:
Does someone have information about that? Is there any charging LED?
Click to expand...
Click to collapse
I went through a bunch of videos, but none of them show charging so far..

frigidazzi said:
I went through a bunch of videos, but none of them show charging so far..
Click to expand...
Click to collapse
I don't believe it does, at least by default. The Moto X has an LED behind the earpiece, which you can see a picture of here but it isn't a charging light by default. With root you can change that.
If this holds true for the Nexus 6, I don't know. No teardowns of the Nexus 6 yet, or hands on with the device showing this functionality. Even if it doesn't have this light. I am sure there will be a way to use the display to get this info across.

cupfulloflol said:
I don't believe it does, at least by default. The Moto X has an LED behind the earpiece, which you can see a picture of here but it isn't a charging light by default. With root you can change that.
If this holds true for the Nexus 6, I don't know. No teardowns of the Nexus 6 yet, or hands on with the device showing this functionality. Even if it doesn't have this light. I am sure there will be a way to use the display to get this info across.
Click to expand...
Click to collapse
Yeah I was reading this about the Moto x also. Hopefully it kept that design too.

[Q] Ambient Display Randomly Turns On

What is everyone experiencing? I have a T-Mobile Nexus 6. I am running stock and not rooted. Apologies if this has already been covered, but I searched a couple of different ways and did not see anything.
Not sure what others are experiencing, but my Nexus 6 display will randomly wake into ambient mode even when I just have it sitting still on my desk or couch. There are no alerts that are driving it, so I am just wondering if others are seeing the same thing or if they have done anything with the settings to clear this issue.
I can't imagine that ambient display is a huge drain on the battery or anything, but it's not nothing. Plus it's distracting when it happens.

I've noticed mine coming on due to vibrations. I had it sitting on a minifridge next to my desk. I thought it was random too, but it turns out I was either knocking the side of my desk with my knee, or the fridge was kicking on/off.

Mine does it all the time. No movement to the phone or even around the phone. Hands no where near it. Just decides to wake up. I find the whole ambient display to be pretty annoying altogether honestly. Hoping devs can disable it and find a way to use the LED.

I saw a weird error message from LightFlow (which I installed and enabled to see what it would do). I wonder if this or other apps that are running in the background and potentially causing the screen wakes.
I will try uninstalling LighFlow to see if it improves the situation and report back with any news.

I think you might be right. I have the same problem but I didn't notice it when I first got the phone. I have installed lightflow and now that you mention it, this problem started soon after. So I just uninstalled lightflow and it already seems better.

When I installed that double tap to wake app it messed with ambient display and would turn it on, especially when the battery was low. I removed that app.
Since then I have also turned off ambient display because I found it fairly useless and feel it is using battery for very little benefit. If it flashed faster or kept flashing until I checked it I think I'd use it.

I turned it off because I had it sitting on a table with nobody touching the table and it kept coming on. I couldn't get light flow to get the light working unfortunately, hopefully there is a fix coming.

Moostafa29 said:
Mine does it all the time. No movement to the phone or even around the phone. Hands no where near it. Just decides to wake up. I find the whole ambient display to be pretty annoying altogether honestly. Hoping devs can disable it and find a way to use the LED.
Click to expand...
Click to collapse
root phone, install light flow, disable ambient display.
it's already been done.
i use light flow and it works perfectly, sans flashing LED but that seems hardware/kernel blocked.

It seems that LightFlow is what was causing the issue as I haven't noticed the screen waking since uninstalling it yesterday.
Sent from my Nexus 6 using XDA Premium HD app

I'm definitely looking forward to getting the LED indicator working.
Sent from my Nexus 6 using XDA Premium HD app

Ambient display is useless

I found that ambient display is useless.
I was thinking that whenever I got notification, the ambient display will lit the screen and then OFF ... then lit ... then OFF.
You know, kind of asking attention.
It is NOT.
It lit ONCE, then OFF forever, until I pick up the phone (of course).
The problem with this, if I leave the phone on my desk for quite long, I won't know if there was notification arrived, unless I pick up the phone.
So, what's the use of this ambient display?
Damn, LED notification would be much useful!

gogol said:
I found that ambient display is useless.
I was thinking that whenever I got notification, the ambient display will lit the screen and then OFF ... then lit ... then OFF.
You know, kind of asking attention.
It is NOT.
It lit ONCE, then OFF forever, until I pick up the phone (of course).
The problem with this, if I leave the phone on my desk for quite long, I won't know if there was notification arrived, unless I pick up the phone.
So, what's the use of this ambient display?
Damn, LED notification would be much useful!
Click to expand...
Click to collapse
So you can either see the notification come in first time when it lights up. Or you can quickly pick the phone up to see if there are any notifications without it fully waking up.
LED is easier though!

I prefer they don't lit it on and off constantly because it is distracting when you are in a meeting and it drains your battery. Though having an option would be nice

Yeah, I agree it is a useless battery wasting feature (though the impact to battery is minimal). Thankfully the LED can be enabled with Light Flow even though that is flawed as well since the app will randomly get killed and the light won't work.
Ambient Display would be perfect if it flashed continuously until you check it and if it worked in priority mode, which it doesn't if you have priority mode set up like the old silent mode. If you don't want your phone making noise or vibrating but still need to see notifications it is pretty worthless.

you are dead on sir.
gogol said:
I found that ambient display is useless.
I was thinking that whenever I got notification, the ambient display will lit the screen and then OFF ... then lit ... then OFF.
You know, kind of asking attention.
It is NOT.
It lit ONCE, then OFF forever, until I pick up the phone (of course).
The problem with this, if I leave the phone on my desk for quite long, I won't know if there was notification arrived, unless I pick up the phone.
So, what's the use of this ambient display?
Damn, LED notification would be much useful!
Click to expand...
Click to collapse
I was told Google is moving away from using led notification, but yet they designed a phone? with one built in but totally useless at this point. Hopefully the next update will address this.

Mine flashes continually until I check things... Every ten seconds or so. It is wonderful... Not sure what is up with your guys' one time notifications...

ambient display is alrite.... It doesn't work that well though. It does not consistently work when you pick up the phone. I would much rather have them activate the LED since it's already there.

you. me. and many more
tsy87 said:
ambient display is alrite.... It doesn't work that well though. It does not consistently work when you pick up the phone. I would much rather have them activate the LED since it's already there.
Click to expand...
Click to collapse
I'm setting this gripe in many circles outside of xda hopefully they will address it in the next update. Lots of corporate people want that portion which was always a part of android and even non android phones of the past.

EmperorX said:
Mine flashes continually until I check things... Every ten seconds or so. It is wonderful... Not sure what is up with your guys' one time notifications...
Click to expand...
Click to collapse
So does mine

vvveith said:
I was told Google is moving away from using led notification, but yet they designed a phone? with one built in but totally useless at this point. Hopefully the next update will address this.
Click to expand...
Click to collapse
in all fairness, Moto made the phone, whether for Android Silver or whatever other reason, it wasnt designed ground up with Google or originally planned as a Nexus.
I like ambient. Works great for me. and being an Amoled display, only the pixels being used light up, so battery is minimal

users report otherwise.
CraigP17 said:
in all fairness, Moto made the phone, whether for Android Silver or whatever other reason, it wasnt designed ground up with Google or originally planned as a Nexus.
I like ambient. Works great for me. and being an Amoled display, only the pixels being used light up, so battery is minimal
Click to expand...
Click to collapse
Acording to the battery threads I've read, ambient display sucks battery.

mzimand said:
So does mine
Click to expand...
Click to collapse
What are you guys using? Lightflow?

vvveith said:
Acording to the battery threads I've read, ambient display sucks battery.
Click to expand...
Click to collapse
Does the device wake up from deep sleep for it? If yes it sure does suck a lot of battery. Especially if it is supposed to flash up in intervals to remind you of the notification.
jawmail said:
What are you guys using? Lightflow?
Click to expand...
Click to collapse
I just tested it... it flashes up every 30 seconds or so. As soon as as you click on it the screen is on without any delay. So I guess it screws your battery hard by making it wake up each time? It would mean that as soon as you have a notification your device would wake up every 30 seconds.

I can't get Lightflow to work at all. Do you need a kernel that has LED support?

jawmail said:
What are you guys using? Lightflow?
Click to expand...
Click to collapse
I am just using the regular ambient feature built into the stock rom. I am encrypted, rooted with stock kernel on stock 5.0.1. I have not messed with any AOSP roms .

jawmail said:
I can't get Lightflow to work at all. Do you need a kernel that has LED support?
Click to expand...
Click to collapse
Rooted and use root access for the LED activated in Lightflow.
Lightflow screws up ambient tough. It constantly flashes as if it has an notification, even if it only shows the clock. This WILL kill your battery in my opinion...

Led notification will drain batttery fast?
Via my NeXus™ 7FHD on XDA Premium app

I actually like it more than Active Display. Active was much more sensitive to movements which for really annoying.
Sent from my Nexus 6 using Tapatalk

Alienfreak said:
Rooted and use root access for the LED activated in Lightflow.
Lightflow screws up ambient tough. It constantly flashes as if it has an notification, even if it only shows the clock. This WILL kill your battery in my opinion...
Click to expand...
Click to collapse
I don't know what settings you set to make it do that.
Light Flow doesn't do that here. Cooperates fine with Ambient.

I know there are people (Lightflow Dev) who are working on getting the built-in led working, and I think that's great. I wonder if there are any devs working on making Ambient Display more useful...? I'm going to shut off the Ambient Display today and mess around with an app I used to use on the Galaxy S called NoLed. It puts dots or icons on the screen and could notify me of anything... might be the ticket here.

Can someone explain MotoDisplay to me

So I'm coming from a 5X that had a nice RGB LED, I was able to set different colors for different apps and could tell from across the room what if any notifications I had - no need to look at it for more than a second or 2 or pick it up or anything. I could then respond accordingly: White - email, probably just spam ignore it; Green - text, get to it when not busy; Pink - tinder, drop the baby and run for the phone.
With the x4 I seem to have taken a step backwards - the screen lights up with the clock and an icon for whatever notification (but I have to be standing right by the phone to see the specific icon). But the bigger issue is it only lights up once when the notification comes in - I really don't need to know I have a notification when it comes in (I heard the chime or vibrate) but I would love to be able to walk away from my phone, glance at it and know if I missed anything without having to pick it up. I'm not sure a world where I have to move my phone every time I come back to it could be considered convenient.
From what I have seen online it described the phone has breathing (pulsing every now and then) when you have an active notification, but this was earlier Moto models - I get just one notification at the time it comes in and nothing else ever. Unless I move the phone - which brings me to the 2nd issue, the sensitivity of the motion sensor, I can have the phone on my desk or couch cushion next to me and just placing a remote down near it or typing the phone is constantly lighting up (even when I don't have a notification) I have the Approach for Moto Display turned off and it definitely has to be moved, but just the tiniest of amount - I get the feature is designed for people that want to grab the phone to see the time and not have to turn it on, but there is a huge difference between the slight vibration from typing on a keyboard next to it vs. actually picking the thing up.
If Motorola/Lenovo is going to want people to embrace Moto Display at least make it so it isn't constantly flashing away for no reason.
Anyway are my experiences the norm? While I would love to be able to turn the motion sensor off for Moto Display my big issue is lack of persistent notification notifying without any interaction from me.

https://forum.xda-developers.com/moto-x4/themes/app-frontflash-notification-v1-7-t3740066

Yea, it's working "as intended". It was a poor choice really to disable the notification LED from the phone. I think it's fine on Amoled displays that can have the breathing without affecting battery life too much, but it's not the case here.
Although I generally like the high sensitivity of the Moto Display. I leave the aporoach feature disabled, and everytime I go by my phone when it's in a table or something I just push it slightly to check the notifications, it's way more convenient than to use the power button and gives more information than a RGB LED.

Thank you both, yes I did some more digging and seems like they did away with the 'breathing' feature.
I'll try that front flash app,
This whole thing just seems a little poorly thought out - disable the breathing so as not to reduce battery life, but make the user pickup the phone periodically which decreases battery life.
I get if they want to do something different than a notification LED but not everyone wants to pick up there phone every X minutes to see if they missed something.
Least I now know when it periodically turns on the Moto Display its not to remind of a current notification its just the stupid motion sensor being way to sensitive.

It is normal. In my opinion the Moto display on the new Moto are not as sensitive as older models like the Moto x pure. You were able to literally wave your hand over the screen to see notifications and time and battery level. However I still love the active display. But I also miss the notification light. But because of the active display they felt like their was no need for led notification. The Moto x4 is still a great handset with features that many people actually use like active display. I have used Samsung and Sony and lg and always had issues. Since the Moto x first came out and bought it I have never had issues with hardware or software. Sure the updates may take a lifetime however Motorola in my opinion is the bear handset for me in terms of quality. It helps tho that even with Android one or Nexus out their that Moto has almost near clean stock of Android than any other manufacturer.

I can see the argument for not needing a LED when MotoDisplay would 'breath' and periodically show the notifications, but now they have done away with that it seems like an LED would really help. That being said I am trying to adjust and get into the habit of nudging the phone when I come back to it.