At this point, it's been quite a while since the screen (specifically nav bar) burn-in issues were brought to light. In November, Google released an update that faded the nav bar buttons after a few seconds, in order to prevent premature burn-in. Personally, I didn't want to risk it so I immediately disabled my nav bar with the build.prop and have been relying solely on pie controls since day 1. As such, I have no noticeable burn-in in the nav bar area, or anywhere on the screen. But, I'm considering going back to the normal stock nav bar as I find that to be a more simple way to navigate on a daily basis. But I don't want to risk premature screen burn-in by doing so.
Since November, the talk of screen burn-in issues has pretty much disappeared. And now it has me wondering if that November update to fade the nav bar buttons truly resolved the problem. So I'm looking to get feedback from those who have had their Pixel 2 XL for more than 2 months and have had their nav bar fully enabled the entire time, in order to get a base line of whether or not the premature screen burn-in issue is really a thing of the past.
So please report in if you have:
1) Had your 2 XL for at least 2 months
2) Had your nav bar fully enabled the entire time
If you are one of those people, please participate in the attached poll. Also, feel free to comment with your thoughts if you wish.
Thanks!
I am using my Pixel 2 XL for 5+ SOT daily since early december with about 50% screen brightness. My permanently visible navbar shows zero burn-in.
Try Swipe Navigation to navigate without the Navigation Bar, I will never go back to those buttons.
I've been using mine completely stock since I got it Nov 23, and I've got zero burn in. I was even using mine before the supposed fix was rolled out.
---------- Post added at 12:45 AM ---------- Previous post was at 12:44 AM ----------
mnrivera210 said:
Try Swipe Navigation to navigate without the Navigation Bar, I will never go back to those buttons.
Click to expand...
Click to collapse
How do you get swipe navigation. Do you need to have root?
benhaube1 said:
How do you get swipe navigation. Do you need to have root?
Click to expand...
Click to collapse
You need root in order to edit the build prop to disable the nav bar.
I'm testing swipe navigation out now. I think I do prefer it over Pie Controls, in my short 2 hours of playing with it.
I'm glad to hear that the burn-in issue seems to be a thing of the past, even with the stock nav bar. I'm hoping people continue to chime in with their long term use of the stock nav bar and burn-in. I am still thinking I'd prefer to go back to the stock nav bar if I don't have to worry about burn-in with it.
sn0warmy said:
You need root in order to edit the build prop to disable the nav bar.
I'm testing swipe navigation out now. I think I do prefer it over Pie Controls, in my short 2 hours of playing with it.
I'm glad to hear that the burn-in issue seems to be a thing of the past, even with the stock nav bar. I'm hoping people continue to chime in with their long term use of the stock nav bar and burn-in. I am still thinking I'd prefer to go back to the stock nav bar if I don't have to worry about burn-in with it.
Click to expand...
Click to collapse
It's funny, I used swipe navigation since I got this phone but it was a pain to reach all the way over to the left when using it one handed to go back. I kept seeing your posts about using pie controls so I figured I would give it a go. What I like about pie control over swipe is you don't have to reach to far. I set the bottom 2 corners as the trigger. I do like swipe navigation better though.
I've had mine since October 26th and have zero burn in. 4-5 hours SOT a day. I'm still awaiting reports of 100% verified burn in at launch as opposed to image retention. Most people were probably full of ****.
hatdrc said:
It's funny, I used swipe navigation since I got this phone but it was a pain to reach all the way over to the left when using it one handed to go back. I kept seeing your posts about using pie controls so I figured I would give it a go. What I like about pie control over swipe is you don't have to reach to far. I set the bottom 2 corners as the trigger. I do like swipe navigation better though.
Click to expand...
Click to collapse
Sorry, I misspoke. I'm using "Gesture Control", not Swipe Navigation. With Gesture Control, the trigger points are all in the bottom center area of the screen. So you don't have to reach all the way to the edges of the screen to go back or open recents.
Link to Gesture Control:
https://play.google.com/store/apps/details?id=com.conena.navigation.gesture.control&hl=en
AndrasLOHF said:
I've had mine since October 26th and have zero burn in. 4-5 hours SOT a day. I'm still awaiting reports of 100% verified burn in at launch as opposed to image retention. Most people were probably full of ****.
Click to expand...
Click to collapse
I'm really starting to think you're right. I did see very clear pictures that showed the issue. But everyone that shared the pictures immediately returned their phone, rather than doing something like trying to play a full screen movie to see if it resolved it. I suppose if premature burn-in was really an issue, we would see it with the status bar, specifically the battery indicator. However, after over 4 months of usage as my daily phone, I have absolutely no burn in anywhere on my screen, including the status bar. And I haven't seen a single other person report burn-in with their status bar.
AndrasLOHF said:
I've had mine since October 26th and have zero burn in. 4-5 hours SOT a day. I'm still awaiting reports of 100% verified burn in at launch as opposed to image retention. Most people were probably full of ****.
Click to expand...
Click to collapse
Mine was burnt in since launch and it's worse now. I have used a white and coloured nav bars to minimise it but it's there.
There is status bar burn in and a burn in just above the navigation keys.
I am always considering trying to get it exchanged but I am in the UK and have to go to EE and i'm sure they'll mess me around. Don't want to waste money on Insurance as i'm sure I will get burn in again on the next one.
As for the update to fade the nav bar, having a black nav bar is what causes the worst issue as the nav bar area is brighter on an all white screen. The buttons themselves are only very slightly visible so fading the navbar isn't a solution.
Samsung changed their nav bar to light colours in an update on the S8 shortly after launch as they knew the nav bar being black would make the rest of the screen burn in quicker.
Jonathan-H said:
... Don't want to waste money on Insurance as i'm sure I will get burn in again on the next one.
Click to expand...
Click to collapse
I wouldn't be so sure your next one will get burn-in. At this point I have to believe you just received a defective screen. I have been using my 2 XL daily with 4+ hours of screen on time since late October and even though I've had my nav bar disabled since day 1, my status bar has been untouched. I just checked again with a burn in check app and my status bar has absolutely no burn-in, no matter what color background I test on with 100% screen brightness. Even in the one area I'd expect to see it, which is where the battery indicator is.
Even though there were some initial reports of nav bar burn-in, there were maybe 2 reports of status bar burn-in, that I remember seeing. And in the last 4 months since launch I haven't seen a single report of status bar burn-in. Honestly, if you have those issues you should definitely swap out for another device as what you are describing absolutely is not common on this phone.
....
Personally, after testing gesture navigation for 2 days, I think I'm going to stick with that, rather than re-enabling my nav bar. It took a little getting used to but now I'm really loving it. It makes the stock nav bar (and even pie controls) feel/look dated.
This was my phone as of the 16th of December.
https://i.imgur.com/tCJDM5V.jpg
That's barely 2 months of usage. My status bar is also burnt in. It definitely exists and is definitely an issue. I'd also like to add that my display has very noticeable grain at virtually all birghtness levels.
Lambo_car16 said:
This was my phone as of the 16th of December.
https://i.imgur.com/tCJDM5V.jpg
That's barely 2 months of usage. My status bar is also burnt in. It definitely exists and is definitely an issue. I'd also like to add that my display has very noticeable grain at virtually all birghtness levels.
Click to expand...
Click to collapse
whats your manufacturing date?
xflowy said:
whats your manufacturing date?
Click to expand...
Click to collapse
I believe mid October
AndrasLOHF said:
I've had mine since October 26th and have zero burn in. 4-5 hours SOT a day. I'm still awaiting reports of 100% verified burn in at launch as opposed to image retention. Most people were probably full of ****.
Click to expand...
Click to collapse
My experience has been the same. I bought my phone on launch day and got it October 24th. I have no burn in.
As for the comments about using navigation bar replacements like Pie Controls, Swipe Navigation, etc I just don't understand how people enjoy using those. They are so awkward, unintuitive and just a pain in the ass. Nice that the option exists but I'll never touch them. Plus, from everything I've read they require root which I will never do. I love the navigation bar just the way it is.
Now if Google could just fix the battery issues that started with the February update and became worse with the March update.
I've had my phone since mid October and if I put a solid grey background on, I can see an ever so subtle hint of maybe burn in but I think it's actually just some image retention. I say that because it's not noticeable at all with pictures or videos.
Related
Seeing as how some were concerned with burn-in/didn't want the status bar I'm releasing a first step towards it.
The status bar has been removed, however apps don't seem to reclaim it. I'll be working on this tonight/tomorrow and post any updates on it.
This is for Bigxie's v1 version of JB.
Update:
Adding a fullscreen version that permanently remains fullscreen after 2-3 force closes (There's only a few but they stop after a minute or two and I've yet to have any issues with anything else though I haven't extensively tested it).
XDA is having issues with photos for me, screenshot is here: http://postimage.org/image/yx6en8kif/
FullScreen Mode: http://multiupload.biz/0y10uw1bgdgh/FullScreen Mode_MultiUpload.biz.zip.html
And for those with issues:
Standard JellyBean:
http://multiupload.biz/5puvw2cp7yp1/JB-Original-Navbar_MultiUpload.biz.zip.html
one questions: are only the icons removed or the hole status bar includig the black background?
the status bar doesn't burn in. the rest of the screen just loses brightness, whereas the status bar is black and doen't emit light. the oleds in this section and in the softbutton-section don't lose brightness because they aren't used that much. that's crappy, cause it is pretty good visible after just a couple of months of usage.
madphone said:
one questions: are only the icons removed or the hole status bar includig the black background?
the status bar doesn't burn in. the rest of the screen just loses brightness, whereas the status bar is black and doen't emit light. the oleds in this section and in the softbutton-section don't lose brightness because they aren't used that much. that's crappy, cause it is pretty good visible after just a couple of months of usage.
Click to expand...
Click to collapse
The whole status bar is gone, you can't even slide it down or anything. Also could you elaborate on the losing brightness part please?
Also if anyone else has ideas I'm willing to try them. Causing the SystemUI to crash it enters the correct full screen for a min or two, but that isn't permanent nor ideal.
especially the blue subpixels lose brightness the older they get. entering fullscreen mode, let's say watching a movie, shows, that the status bar and onscreen buttons area are more blue than the rest of the screen. this is because these areas weren't used that much.
samoled is very crappy when it comes to longevity. especially for power users it's really bullsh... i had it on every samsung samoled so far. only omnia 7 with windows phone doesn't show these "burned icons" because it's mostly running in full screen, except you touch the status bar, then the icons pop in.
Lol sorry to say but after reading this thread ... I'm just as confused as the box boy in your phones background... =\ not going to try this one...
=]
-Google
madphone said:
especially the blue subpixels lose brightness the older they get. entering fullscreen mode, let's say watching a movie, shows, that the status bar and onscreen buttons area are more blue than the rest of the screen. this is because these areas weren't used that much.
samoled is very crappy when it comes to longevity. especially for power users it's really bullsh... i had it on every samsung samoled so far. only omnia 7 with windows phone doesn't show these "burned icons" because it's mostly running in full screen, except you touch the status bar, then the icons pop in.
Click to expand...
Click to collapse
Wow i`m waiting for a replacment now for this burn in crap,i like the phone but this is unbearable wish i would of known.
How the hell do you check your notifications?? This seems kind of stupid.
akira02rex said:
How the hell do you check your notifications?? This seems kind of stupid.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28124445&postcount=1
I've seen a couple of requests like that one. Notifierpro apparently lets you (I've never tried it) and my curiosity as to how to actually remove the status bar lead me to this. (I'm not so worried about the burn in, and will leave my status bar there, I just know a couple of people seemed to want it gone to remove burn in)
Why not hide it with Nova/Apex launcher?
Sent from my Galaxy Nexus using xda premium
DavidXSU said:
Why not hide it with Nova/Apex launcher?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Because it will come back whenever you go into any other app. I don't care for this mod, but can see its use for some.
MattJ951 said:
http://forum.xda-developers.com/showpost.php?p=28124445&postcount=1
I've seen a couple of requests like that one. Notifierpro apparently lets you (I've never tried it) and my curiosity as to how to actually remove the status bar lead me to this. (I'm not so worried about the burn in, and will leave my status bar there, I just know a couple of people seemed to want it gone to remove burn in)
Click to expand...
Click to collapse
Thank you for your work!
Just a question, if I was using apex, and I set swipe down action will show notification, will it show?
right7left said:
Thank you for your work!
Just a question, if I was using apex, and I set swipe down action will show notification, will it show?
Click to expand...
Click to collapse
No Idea, sorry, also adding an update to the main post.
http://postimage.org/image/yx6en8kif/
tried this on holo launcher, notifications didn't show up
Sent from my Galaxy Nexus using xda app-developers app
Hi matt
I have error 404 when trying to download the full screen zip
Is it possible to have the reversal zip ? or a toggle function ?
I need a mediafire or dropbox link for Fullscreen please
Updated with original/ working upload for fullscreen
Thank you
Is it possible to have a toggle Fullscreen ?
brunoisa10 said:
Thank you
Is it possible to have a toggle Fullscreen ?
Click to expand...
Click to collapse
I might be able to make an app do it, to swap out the SystemUI.apk when toggled. idk if you can do that with the phone running though.
hi matt
just installed your Full Screen mod
and my Gnex is never starting (stays on bootloop)
I have the Jelly Belly V2 ROM
any idea ?
brunoisa10 said:
hi matt
just installed your Full Screen mod
and my Gnex is never starting (stays on bootloop)
I have the Jelly Belly V2 ROM
any idea ?
Click to expand...
Click to collapse
Probably isn't compatible with Jelly Belly V2.
I've only tested it on bigxie's v1
strange as it it is system.apk or system UI if I'm right , so must be the same on JB ROMs
I can't believe Google was so stupid as to design ON-SCREEN buttons and not foresee screen burn-in issues.
Does anyone have any ideas on how we can fix Google's mistake?
If only there was a way to keep the Navigation Menu always hidden and then only make it appear when we need to use it...sort of like how you can hide the Windows Start bar and when you move your mouse, it animates into view on top of everything else.
Maybe, we can use the proximity sensor to show or hide the Navigation Menu? Like, when you swipe your hand over the sensor, it shows or hides it. Or, maybe make it shake activated? Like just shake your phone and the Navigation Menu appears/disappears. If it's shake activated, then we should make it so we can adjust the shake sensitivity because not everyone shakes the same.
Does anyone have any other ideas on how to solve this? Please post them!
I hope Google tracks this thread and patents and uses our ideas. Or else, give us tactile or capacitive buttons in the next Nexus!
Neo3D said:
If only there was a way to keep the Navigation Menu always hidden and then only make it appear when we need to use it...sort of like how you can hide the Windows Start bar and when you move your mouse, it animates into view on top of everything else.
Click to expand...
Click to collapse
I'm sure there is a ROM or two that does this. I know one for the N7 has that feature... I think it was Glazed. Maybe their GNex ROM has it also.
I haven't had any screen burn-in issues in 8 months of owning the phone so unfortunately I can't help there. good luck.
Neo3D said:
I can't believe Google was so stupid as to design ON-SCREEN buttons and not foresee screen burn-in issues.
Does anyone have any ideas on how we can fix Google's mistake?
If only there was a way to keep the Navigation Menu always hidden and then only make it appear when we need to use it...sort of like how you can hide the Windows Start bar and when you move your mouse, it animates into view on top of everything else.
Maybe, we can use the proximity sensor to show or hide the Navigation Menu? Like, when you swipe your hand over the sensor, it shows or hides it. Or, maybe make it shake activated? Like just shake your phone and the Navigation Menu appears/disappears. If it's shake activated, then we should make it so we can adjust the shake sensitivity because not everyone shakes the same.
Does anyone have any other ideas on how to solve this? Please post them!
I hope Google tracks this thread and patents and uses our ideas. Or else, give us tactile or capacitive buttons in the next Nexus!
Click to expand...
Click to collapse
Like 98% of the issues around here I've never had this problem. Sometimes I think I'm the only person with a problem free Nexus. Nevertheless, jaseglenn4 has a thread discussing this. You'll find some info there, good luck:
http://forum.xda-developers.com/showthread.php?t=1606237
I have screen retention with my keyboard and that's about it.
Sometimes it's fairly noticeable, sometimes it's not, not bothering me enough to get it replaced.
I just changed my habits so that I rotate the screen 90° to the right whenever I use landscape (web browsing and lots of other things) so as to switch the menu to the opposite side. I figure with that usage pattern it'll take twice as long to notice any burn in.
With low brightness settings in most cases I figure this'll be longer than I expect to keep the phone anyway.
Sent from my Galaxy Nexus using xda app-developers app
I heard a myth that if you had screen burn in issue you can reduce it by setting a fullscreen white image, crank it up to max brightness and leave it there for 1-2 hours.. it's not gone but it'll be reduced..
Can someone confirm this?
Sent from my Galaxy Nexus using Tapatalk 2
Yes some roms have the expandable desktop option to make it full screen. I see some people use that and LMT so they don't have to use nav bar instead just gestures to move around phone
Don't ever buy a phone with an amoled display again. *solved*
good day.
It's not going to burn in. Your screen would have to be on for days and days consecutively, nonstop, with the keys never hiding or changing position. And even then with the stock color of the keys it's even less likely.
Sent from my AOSP Android 4.1.1 Galaxy Nexus
Has anyone got burned in images of the buttons on their phone right now? Or is this a "this might happen" question? Have been using mine for a good few months now and there is no sign of this issue!
I Am Marino said:
I have screen retention with my keyboard and that's about it.
Sometimes it's fairly noticeable, sometimes it's not, not bothering me enough to get it replaced.
Click to expand...
Click to collapse
x2, and even then it's only when I have a gray background
Xadin said:
Has anyone got burned in images of the buttons on their phone right now? Or is this a "this might happen" question? Have been using mine for a good few months now and there is no sign of this issue!
Click to expand...
Click to collapse
I think the reason Google made the virtual keys grey is for this reason solely. It's not full white so there shouldn't be able burn-in issues.
I commonly see image-retention (keyboard shadows etc.) but not burn-in. I highly doubt anyone has the latter.
Enhanced said:
I think the reason Google made the virtual keys grey is for this reason solely. It's not full white so there shouldn't be able burn-in issues.
I commonly see image-retention (keyboard shadows etc.) but not burn-in. I highly doubt anyone has the latter.
Click to expand...
Click to collapse
Soooo, this is a non-issue. Good to know!
You have any idea how long it takes for burn in to occurred? Last time I try, it took a week or two, with the screen on 24/7 to get a little burn in on my laptop LCD display. It went away after I turn off the screen for a night.
For the nexus to have a burn-in onscreen button happened? Good luck with that.
Neither mine or my gf's have this issue. Now my nexus 7....it has it bad....
Sent from my Galaxy Nexus using xda premium
Enhanced said:
I think the reason Google made the virtual keys grey is for this reason solely. It's not full white so there shouldn't be able burn-in issues.
I commonly see image-retention (keyboard shadows etc.) but not burn-in. I highly doubt anyone has the latter.
Click to expand...
Click to collapse
What's the difference between image-retention and burn-in?
The issue I'm seeing is that when the screen is white or a light color, I can see where the Navigation Menu used to be (when I hide it).
I hide top and bottom bar so I avoid any burn in.
Hinouchi said:
You have any idea how long it takes for burn in to occurred? Last time I try, it took a week or two, with the screen on 24/7 to get a little burn in on my laptop LCD display. It went away after I turn off the screen for a night.
For the nexus to have a burn-in onscreen button happened? Good luck with that.
Click to expand...
Click to collapse
burn in is a lot easier on amoled displays....
your comparison makes no sense
I have seen a little retention but nothing i would worry about. Usually goes away after a few seconds.
Personally i love the on screen nav buttons.
Sent from my MB886 using xda app-developers app
RogerPodacter said:
I hide top and bottom bar so I avoid any burn in.
Click to expand...
Click to collapse
How do you hide the nav bar?
I would love to know one how come now ROMs do lower than 24dpi Nav bar. Would love 16 or low enough where can even see like I've seen a long time ago. So can use Nav bar ring without Nav bar actually there. This way isn't as much need for lmt launcher if maybe not needing it all. When this happen we would be able to use Nav ring at bottom as many are requesting that lmt get activate from bottom function.
This would created a neater look. One less app that's need. Would be cool as hell.
I tried to figure out how to make smaller than 24 DPI and failed. If someone with more knowledge could produce a smaller almost non existent almost like just one line of pixels at bottom black line (Nav bar) just enough to be able to swipe up and activate nav bar. Would be awesome.
gkitab said:
I would love to know one how come now ROMs do lower than 24dpi Nav bar. Would love 16 or low enough where can even see like I've seen a long time ago. So can use Nav bar ring without Nav bar actually there. This way isn't as much need for lmt launcher if maybe not needing it all. When this happen we would be able to use Nav ring at bottom as many are requesting that lmt get activate from bottom function.
This would created a neater look. One less app that's need. Would be cool as hell.
I tried to figure out how to make smaller than 24 DPI and failed. If someone with more knowledge could produce a smaller almost non existent almost like just one line of pixels at bottom black line (Nav bar) just enough to be able to swipe up and activate nav bar. Would be awesome.
Click to expand...
Click to collapse
Wrong thread this is for developers to release ROMs only.
Sent from my Galaxy Nexus using Tapatalk 2
Sorry i don't post often. R u sure its only ROM only?
What if someone ended up developing a mod for this suggestion?
gkitab said:
Sorry i don't post often. R u sure its only ROM only?
What if someone ended up developing a mod for this suggestion?
Click to expand...
Click to collapse
yeah... read the rules
I enabled full immersive mode to help prevent screen burn-in and now I'm finding that a couple of apps, namely Spotify, won't utilize the full screen area and keeps a huge black bar on the top and bottom of the app. On my LG V30, there was an option to force apps to utilize the full screen and this worked perfectly with Spotify. However, I'm not seeing this option on my 2 XL.
Does anyone know how to force certain apps into full screen on the 2 XL?
Same problem here, would love a fix for this so I can use the whole screen
Accessibility has a magnification option when triple tapping the screen. It zooms in a bit too far but it does go full screen. I wonder if there is a way to lower the zoom amount somewhere.
Sent from my Pixel 2 XL using Tapatalk
The LG V30 handles this really well. Little button on nav bar to switch between full screen and regular and the setting sticks per app.
This seems like and option but I haven't tried it out yet myself.
https://play.google.com/store/apps/details?id=com.gmd.immersive
SWBgHz said:
The LG V30 handles this really well. Little button on nav bar to switch between full screen and regular and the setting sticks per app.
This seems like and option but I haven't tried it out yet myself.
https://play.google.com/store/apps/details?id=com.gmd.immersive
Click to expand...
Click to collapse
Yeah, I pulled my V30 back off the shelf for a bit yesterday and it made me envious of how well it handles immersive mode, compared to the 2 XL. Sadly, yesterday, I started to experience the issue that others have mentioned with immersive mode enabled on the 2 XL, which is that occasionally the screen won't wake and the only way to fix it is with a hard reboot (hold power for 10 seconds). It happened to me 3 times yesterday. So now I'm realizing that in order to keep my phone fully functional and reliable, I have to disable immersive mode.
On the plus side, my squeeze for assistant feature will work again but now I'll be putting myself at risk for screen burn-in. So anything I can do to hide the nav bar whenever possible will be very welcomed. I'll give that GMD Full Screen app a try. No matter what I'm going to use Nav Bar Apps to change the color of the nav bar based on the app being used. This will allow me to prevent the black nav bar from showing up, minimizing the risk of screen burn-in.
Maybe set nav to 1 ?cuz apk need to see if there is a keyboard
Icyou said:
Maybe set nav to 1 ?cuz apk need to see if there is a keyboard
Click to expand...
Click to collapse
How do I do that? I'm familiar with ABD/fastboot commands but not sure what the command is to change nav to 1.
Removing the navbar doesn't force apps into fullscreen
I like that my Note 8 gives you the option to force it in apps that don't support it and it remembers that decision
imtjnotu said:
I like that my Note 8 gives you the option to force it in apps that don't support it and it remembers that decision
Click to expand...
Click to collapse
That is what V30 does, nice thing with V30 is you have a 4th button on nav bar that is a toggle between immersive on and off and however you set it 'sticks' for that app for next time. So it makes it very easy to setup/use. Frankly, this should be default behavior in Android and the fact that it isn't just wreaks of Google stubbornness we see where they just won't make and obvious and necessary changes because their original thinking is different than what people want.
Guys you will have to wait for custom roms to come out. They (at least some) will more then likely have features like this. The pixel is stock android pretty bare bones when it comes to things like that. Google isnt going to put a feature like that in (for some reason) that wouldnt be utilized by other phones. Now i know what your thinking. "But the pixel does have some "pixel specific software features" And this is true. But hey its Google it only took them 13 OS iterations to give us a proper ****ing battery % indicator.
sn0warmy said:
Yeah, I pulled my V30 back off the shelf for a bit yesterday and it made me envious of how well it handles immersive mode, compared to the 2 XL. Sadly, yesterday, I started to experience the issue that others have mentioned with immersive mode enabled on the 2 XL, which is that occasionally the screen won't wake and the only way to fix it is with a hard reboot (hold power for 10 seconds). It happened to me 3 times yesterday. So now I'm realizing that in order to keep my phone fully functional and reliable, I have to disable immersive mode.
On the plus side, my squeeze for assistant feature will work again but now I'll be putting myself at risk for screen burn-in. So anything I can do to hide the nav bar whenever possible will be very welcomed. I'll give that GMD Full Screen app a try. No matter what I'm going to use Nav Bar Apps to change the color of the nav bar based on the app being used. This will allow me to prevent the black nav bar from showing up, minimizing the risk of screen burn-in.
Click to expand...
Click to collapse
I haven't experienced this issue. I am using this command to enable immersive mode however in order avoid issues previously reported - battery drain, performance problems and delay waking up the screen: settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
sn0warmy said:
Yeah, I pulled my V30 back off the shelf for a bit yesterday and it made me envious of how well it handles immersive mode, compared to the 2 XL. Sadly, yesterday, I started to experience the issue that others have mentioned with immersive mode enabled on the 2 XL, which is that occasionally the screen won't wake and the only way to fix it is with a hard reboot (hold power for 10 seconds). It happened to me 3 times yesterday. So now I'm realizing that in order to keep my phone fully functional and reliable, I have to disable immersive mode.
On the plus side, my squeeze for assistant feature will work again but now I'll be putting myself at risk for screen burn-in. So anything I can do to hide the nav bar whenever possible will be very welcomed. I'll give that GMD Full Screen app a try. No matter what I'm going to use Nav Bar Apps to change the color of the nav bar based on the app being used. This will allow me to prevent the black nav bar from showing up, minimizing the risk of screen burn-in.
Click to expand...
Click to collapse
Try out the app "Navbar Apps" in the play store. What it does is creates a matching color for the navbar of whatever app you're in simply lar to how the status bar works by default in apps. Some aren't accurate but you can manually set colors for apps too. Most are pretty spot on.
This works perfect to help with burn-in. The reason being is that people have it backwards, the navbar is the only thing not burning in due to black on Oled meaning the pixels are off. So by having a black navbar on all the time you're actually seeing burn-in from the entire rest of the screen with the navbar being darker since it's not active. Using the app I recommended above will basically even out the screen so it's all being used the same amount, thus reducing any noticable burn-in. It also looks really cool and has a bunch of great features.
Icyou said:
Maybe set nav to 1 ?cuz apk need to see if there is a keyboard
Click to expand...
Click to collapse
I too would like to know how to do this. Had it on my S8+ and loved it. Someone over there made an rro theme that removed it
Nephilim said:
Try out the app "Navbar Apps" in the play store. What it does is creates a matching color for the navbar of whatever app you're in simply lar to how the status bar works by default in apps. Some aren't accurate but you can manually set colors for apps too. Most are pretty spot on.
This works perfect to help with burn-in. The reason being is that people have it backwards, the navbar is the only thing not burning in due to black on Oled meaning the pixels are off. So by having a black navbar on all the time you're actually seeing burn-in from the entire rest of the screen with the navbar being darker since it's not active. Using the app I recommended above will basically even out the screen so it's all being used the same amount, thus reducing any noticable burn-in. It also looks really cool and has a bunch of great features.
Click to expand...
Click to collapse
Yeah, this option makes complete sense, actually. I couldn't understand why it would be the pixels that are turned off the most (with the black nav bar) that would cause the burn-in. So your explanation helps clear that up for me. Right before leaving for a 5 day trip in Costa Rica, I disabled full immersive mode and installed Nav Bar Apps. I spent my downtime on the plane to get all my app nav bar custom colors setup to my liking. Now all my apps have color variations ranging anywhere from red, to blue, to green, orange, yellow, white and everything in between. Everything EXCEPT black. I used the phone the entire trip for travel guidance, music, watching Netflix/Hulu, taking pictures etc.. All with absolutely no black nav bar. I just got home last night, checked the phone this morning for burn-in and there's nothing.
It's sad that this screen burns in so quickly with the black nav bar, but to me its become such a non-issue since it's so easy to avoid. The ideal setup would be to fully disable the nav bar and use pie controls instead but a ROM isn't yet available to do this. I've read that Custom Navigation bar is another solid option as it allows you to hide the nav bar by app. However, I'm not sure it allows you to change the nav bar colors and I'm fairly certain it still disables the squeeze for assistant feature because it's still technically using immersive mode in some form.
Pecata said:
I haven't experienced this issue. I am using this command to enable immersive mode however in order avoid issues previously reported - battery drain, performance problems and delay waking up the screen: settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
Click to expand...
Click to collapse
Can you elaborate on this a bit?
I tried that command but it didn't do anything. So I tried the same command with a different app, example...
settings put global policy_control immersive.navigation=apps,-com.google.android.youtube
And what I noticed is that it put the full nav bar immersive mode system wide on everything EXCEPT Youtube. This was the opposite of what I anticipated would happen. Now I'm thinking the "-" means I'm telling the system to make everything immersive except the app I specified in the above command. Is this correct? If so, the only benefit I see to using this method is to pick and choose certain apps to prevent the immersive nav bar.
Perhaps I'm misunderstanding?
sn0warmy said:
Yeah, this option makes complete sense, actually. I couldn't understand why it would be the pixels that are turned off the most (with the black nav bar) that would cause the burn-in. So your explanation helps clear that up for me. Right before leaving for a 5 day trip in Costa Rica, I disabled full immersive mode and installed Nav Bar Apps. I spent my downtime on the plane to get all my app nav bar custom colors setup to my liking. Now all my apps have color variations ranging anywhere from red, to blue, to green, orange, yellow, white and everything in between. Everything EXCEPT black. I used the phone the entire trip for travel guidance, music, watching Netflix/Hulu, taking pictures etc.. All with absolutely no black nav bar. I just got home last night, checked the phone this morning for burn-in and there's nothing.
It's sad that this screen burns in so quickly with the black nav bar, but to me its become such a non-issue since it's so easy to avoid. The ideal setup would be to fully disable the nav bar and use pie controls instead but a ROM isn't yet available to do this. I've read that Custom Navigation bar is another solid option as it allows you to hide the nav bar by app. However, I'm not sure it allows you to change the nav bar colors and I'm fairly certain it still disables the squeeze for assistant feature because it's still technically using immersive mode in some form.
Click to expand...
Click to collapse
Glad you like it. I'm enjoying it a lot. It makes you feel like you're actually using the whole screen instead of having the ugly cut off black bottom with nav buttons.
Nephilim said:
Glad you like it. I'm enjoying it a lot. It makes you feel like you're actually using the whole screen instead of having the ugly cut off black bottom with nav buttons.
Click to expand...
Click to collapse
Thanks for the heads up on this. Back in the day an Xposed module was needed for this and there was a spreadsheet going on matching apps colors that were detected wrong. The last good PA ROM had it baked in as well. Though I wonder how much longer this will be on the Play Store with Google set on removing anything that touches Accessibility Services that aren't related to a disability.
sn0warmy said:
Can you elaborate on this a bit?
I tried that command but it didn't do anything. So I tried the same command with a different app, example...
settings put global policy_control immersive.navigation=apps,-com.google.android.youtube
And what I noticed is that it put the full nav bar immersive mode system wide on everything EXCEPT Youtube. This was the opposite of what I anticipated would happen. Now I'm thinking the "-" means I'm telling the system to make everything immersive except the app I specified in the above command. Is this correct? If so, the only benefit I see to using this method is to pick and choose certain apps to prevent the immersive nav bar.
Perhaps I'm misunderstanding?
Click to expand...
Click to collapse
So I spent some more time fiddling with this and tried testing the same command but without the "-". So the new command is:
settings put global policy_control immersive.navigation=apps,com.google.android.youtube
What I noticed is that the nav bar immersive setting still seems to be system wide. However, squeeze for assistant is still working with the screen off. This has not been the case with any other immersive commands I've tried. So this definitely handles it a little differently. I'll test this for a while to see if I have any issues with screen not waking from sleep.
AndrasLOHF said:
Thanks for the heads up on this. Back in the day an Xposed module was needed for this and there was a spreadsheet going on matching apps colors that were detected wrong. The last good PA ROM had it baked in as well. Though I wonder how much longer this will be on the Play Store with Google set on removing anything that touches Accessibility Services that aren't related to a disability.
Click to expand...
Click to collapse
I couldn't care less if things get removed from play store, we can still sideload and I'm sure someone as useful as Navbar Apps would just move to XDA Labs if it got removed.
I was watching a YouTube video earlier and noticed burn-in. The home button and the line that separates the navbar from the rest of the screen. If Google would get rid of the navbar it would almost eliminate burn-in. I got an RMA so hopefully my next one won't do it. Here's the pics I sent Google.
+1, I've had mine for just over two weeks and I'm already seeing navbar burn in. Question, did yours seem to have status bar burn in when you first turned it on? I swear I saw the burn in line going across, it lines up with the bottom of the notch
There is already a thread about this. Search next time please
@qtpa2tnh
Me too. I could see at first time switching on a "line" between normal display and notch area.
I don't know if it's the display or just the program code.
If there's already a thread, can someone post the link?
I couldn't find it.
lambda89 said:
@qtpa2tnh
Me too. I could see at first time switching on a "line" between normal display and notch area.
I don't know if it's the display or just the program code.
If there's already a thread, can someone post the link?
I couldn't find it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3-xl/how-to/status-bar-burn-t3862236
c_86 said:
There is already a thread about this. Search next time please
Click to expand...
Click to collapse
Thanks for pointing this out. The mods don't seem to care about keeping uncluttered boards around here anymore. I reported that there were multiple threads regarding the speakers and this is the reply I received, "that`s fine , we let them be, thanks for reporting".
I strongly recommend NavBarApps
https://play.google.com/store/apps/details?id=pl.damianpiwowarski.navbarapps
You need some color to fill the empty navigation bar. Your entire screen is wearing pixels but the nav bar is not. That's how you're getting screen burn. Notice how every other manufacturer is doing that but Google.
I've used this app on my P2XL with success.
Sent from my Pixel 3 XL using Tapatalk
obsanity said:
I strongly recommend NavBarApps
https://play.google.com/store/apps/details?id=pl.damianpiwowarski.navbarapps
You need some color to fill the empty navigation bar. Your entire screen is wearing pixels but the nav bar is not. That's how you're getting screen burn. Notice how every other manufacturer is doing that but Google.
I've used this app on my P2XL with success.
Click to expand...
Click to collapse
I was using Navbar Apps. Still burnt in the home button.
It also matters what color you use. Red doesn't wear at all. Green is middle of the road and blue is the most wearing. I usually stick to light gray navigation and status bar colors to include all pixels as much as possible and still see buttons and icons.
westside80 said:
I was using Navbar Apps. Still burnt in the home button.
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk