Related
GROUND RULES:
Who should keep reading:
Current owners of Triumph or perspective buys who are trying to cut through all the trolls, flame wars, useless and/or misleading information from the (many) other threads, to find out what or if anything was wrong with their phone, how to identify these problems and most importantly, how to make intelligent decisions on whether to return or exchange before the 30 days run out.
Who should stop now and go read a book instead:
People who have (or think they have) perfect phones and feels it’s necessary to defend the Triumph’s honor at any mentioning of a problem. People who believes everybody else is clueless therefore it’s necessary to advertise basic settings changes as cure-alls (i.e. enable “use wireless networks,” it will fix your GPS problems). please give others more credit than that. And last but not least, people who hate the T and thinks it’s just the worst phone ever made… you have no reason to stay here.
Still with me? Good…
I have personally owned two T’s. the first one had several problems that I ended up returning, the second one was much better but not problem free. I also have access to two other T’s owned by friends. Everything I post here are based on facts that I have personally observed, not second-hand info or hear-say.
** GPS problem:
First of all, Google Map does NOT depend on GPS. Being able to see your location on the map means NOTHING when it comes to GPS location. In order to test if you have a GPS problem you have to either use an app like GPS Test or start Google Navigation. All tests should be done outdoors under open sky and while you have a valid data connection (for A-GPS data download). The GPS should lock-in within 2 minutes or less (Google Navigation should start showing your real time location as a blue arrow and start giving you turn by turn instructions).
A few minutes after a gps lock, you should have a location accurate to within 15ft or less. If google nav consistently shows a visible blue circle (of any size) around your current location, then it is unable to give you an accurate location lock, it is a problem.
If you have any problem at all with GPS lock or location accuracy, your phone has a broken GPS. Take it back for an exchange! Do not listen to people saying that you could fix it by running some magical software or do a special gps dance. You are wasting your time. If it wasn’t broken in the first place then you would have no need for those “fixes.” My first phone had an almost unusable GPS, the replacement and both of my friend’s phones have no problem whatsoever. Using GPS Test app, I was able to clearly see how the satellite signal levels were 30-50% lower on the previous T when compared to my OV, while the replacement had levels that are comparable to the OV.
** Data disconnect and/or drop to 1x when GPS is turned on.
I did not notice this behavior on any of the 4 Triumph I tested on. GPS and wireless signal can not interfere with each other, so if this happens consistently and is making data connection unstable or GPS lock problematic then there’s most likely a hardware problem. the phone should be exchanged.
** Screen flicker, white out, color cast:
If your screen ever turns white completely, or has a VERY heavy color cast, the answer is obvious, get it exchanged. meanwhile, all Triumph’s screen have overall “cooler” color when compared to my V. there were slight variations between each phone but as long as it was not extreme (i.e. making white look blue and red look purple) it should not be considered a problem. Just make sure you have removed the top layer screen protector before making a judgement.
slight screen flicker while turning on/off the phone repeatedly might not be worth an exchange for that reason alone. My first phone and one of my friend’s phone had the flickers, while my replacement and the other friend’s phone did not. The slight flicker did not both me or my friends at all.
**screen protectors:
Yes, there are two screen protectors. No, there’s absolutely no reason to keep the top layer. The second layer is very well applied and I doubt it’s meant to be taken off. You will never be able to apply another protector as well as that. If you have screen sensitivity issues, I’d suggest exchanging the phone rather than taking off that second layer of protector. None of the 4 phones I tried had any sensitivity issue with the protector attached. If you had to take it off then your phone has a problem.
** visible touch screen sensor elements:
If you can see “dots” on the screen under normal use, you are seeing the sensor elements embedded in between glass players. You should NOT be able to see them in any way during normal use. Exchange the phone if you do. it was a known LCD panels manufacturing problem on some earlier phones (mostly HTC). None of the Triumph I have seen had that problem.
** Signal level:
All four of the Triumphs had lower signal dbm numbers when compared to my OV. However, with my borderline coverage (-105dbm at home and -110dbm in the office), I had not experienced any drop calls on the T. Data connections were marginal but no worse than the OV. Do not make any decision based on dBm numbers alone. dbm is a relative value and do not mean what a lot of people seemed to think it means. In any case, exchanging the phone is not going to help in any way.
** WIFI disconnect:
I have not run into this with Triumph however, I had similar issue running AOSP rom on my OV while having no problem with other roms. This is likely something caused by the combination of router and phone software. My suggestion would be to try as many different routers as you can also try router settings such as G vs N, WEP vs WPA, hidden vs broadcast… if you have same problem everywhere then by all means try an exchange, I doubt it would help however.
** Touch button in sensitivity:
This happens randomly on all the T I have tested. It is likely a software problem that will not be fixed by exchanging the phone.
** Camera clicking while focusing:
All 4 phones had slight clicking noise while focusing but none had trouble actually gaining a focus. Exchange if you can’t get it to focus at all. the clicking seems to be normal however.
** Camera color cast:
None of the phones I have tried had problem with “green/blue color cast in the middle of the screen” as some have reported. If you have already removed the green screen protector on the camera itself then you probably have a real problem and should exchange the phone. just check your expectations – cell phone cameras have cheap plastic little fish eye lenses. Don’t expect results like your Canon or Nikon.
** phone stops charging while on:
I noticed two things: 1. some micro-usb chargers such as the one that came with OV would at times refuse to charge while the phone was turned on. Unplugging a couple of times may fix it. I haven’t had problem with stock T charger or the charger that came with my BlackBerry. 2. The charger will shut off once the phone temperature reaches 42c. this is most noticeable while in a hot car with phone on the dashboard. This is normal and is the result of an (over)sensitive overcharge protection.
** light leakage around bottom edges:
All the phones I have tired had various degrees of light leakage. It is consistent with problems reported on other versions of the same phone released earlier. the leakage was only visible in relative darkness so personally I did not think it was worth worrying about.
** Mismatched MEID:
To check your phone’s MEID, go to settings-> about phone -> status. The MEID should be an 18 digit number matching the stickers on the box, outside of the battery door and behind the battery on the back of the phone. Both of my phones had mismatched MEID. The phone itself was showing a 17 digit number while the stickers all have 18 digit numbers. an 0 in the middle is missing on the phones. One person (VM rep?) in an earlier thread had said VM was aware that 3,000 phones had this MEID mismatch so it seemed to be a known problem.
Some people have reported trouble using Google Voice on phones with mis-matched MEID. I have not been able to verify that myself.
** software version 38 vs 39:
Both of my Triumphs had version 38 software. the previous one had horrible GPS and some screen flickering while the replacement did not. There were also some obvious software differences between the two phones, despite the same software version. The replacement phone camera default to 5mp, while the previous one default to VGA resolution. The previous phone gallery had four random pictures referencing some Chinese websites (seemed to be leftover web cache). These pictures were in the ROM and did not go away after hard reset. The replacement phone had an empty gallery. One of my friend’s Triumph came with v.39 software which also had some screen flickers.
By itself, the software version did not indicate a good or bad phone. test everything!
The main thing to keep in mind is that there are many reported problems, not all of them were all that crucial. Given the obvious inconsistencies in build quality, it is a real possibility that the exchange would turns out to be much worse than the original phone. you really have to look long and hard at each problem and make an educated decision for yourself. Meanwhile, there’s absolutely no reason to put up with major things like a broken LCD or gps or insensitive touch screen. Take it back to the store!
This list was put together over several days, mostly as notes to myself. So please excuse me if it rambles a bit. Let me know if there’s something else you would like me to check.
Thanks and good luck.
I never even realized the 2 screen protectors but sure enough, they are there. As far as the light issues at the bottom of the screen, I definitely see it on mine as well.
microphone is awful.. sounds like there is tape on it. i checked, there isn't.
Heading to exchange it.
awesome write up. thank you sir
Another issue I just found out Im having is with my bluetooth. I have a Jawbone Icon and the sound seems overloaded. When I connect my older motorola BT headset to it, it works fine. Strange indeed!
My 30 day return period ends this weekend so I have to make a decision. GPS is really the only problem I have, and it is intermittent. I was hoping a software fix would come out so i wouldn't have to worry about exchanging.
As far as my bluetooth issues with the sound overpowering, I actually just bit the bullet and bought the a MOTO BT today to see how it would work. No issues. Fishy...
my biggest problem is that i cant seem to be able to stream music properly in google music. does everyone have this problem or should i exchange?
I even had full bars yesterday, and it was barely sputtering out any music.
crxmax said:
my biggest problem is that i cant seem to be able to stream music properly in google music. does everyone have this problem or should i exchange?
I even had full bars yesterday, and it was barely sputtering out any music.
Click to expand...
Click to collapse
I doubt that is a hardware issue. Probably a result of VM's network. Try running a speed test app and see what kind of speeds you are getting. I prefer "Open Signal."
the speeds i got on all the tests were all drastically different. I say an average of about 350kbs...is that normal?
It seems to me that Samsung has screwed up the screen calibration inadvertently in their cluster-F of an OS. The S4 shows black clipping in images, gamma test charts, and videos, but I found some remnants of a more capable screen here!
http://youtu.be/V7T4rEQt27o
Seriously Samsung, don't give a crap if it gives somewhat better battery life, FIX THE DAMN THING! What's the point of releasing an FHD phone and having that black clipping and blue tint? At least leave an option to switch it on and off.
Will be fixed with custom kernels as with S3/Note 2, hopefully.
Noticed this last night while multitasking.
Kind of annoying, I do think its software related because my SystemUI crashed at one point, among other things, and it stopped happening.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
burningembers said:
Noticed this last night while multitasking.
Kind of annoying, I do think its software related because my SystemUI crashed at one point, among other things, and it stopped happening.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Whats stopped happening after the UI crash? Did the clipping go away?
that would be a step in the right direction
sam2c said:
Whats stopped happening after the UI crash? Did the clipping go away?
that would be a step in the right direction
Click to expand...
Click to collapse
Correct. Whereas before going from one screen to the other would cause a momentary jump in brightness, then a quick lowering of brightness by a noticeable but nearly insignificant degree - post a ton of errors/crashes, it stopped happening.
At one point the phone jumped a few notches in brightness (without my touching anything). And from then on out, all my screen swaps from light/dark, dark/light, different apps stopped having that ever-so-slight adjustment.
So it *seems* like it is an adjustment made on-the-fly of sorts, and I would really love to just be able to disable it...
This was a major problem in the OG Note and was never fixed.
Samsung needs to fix their screen because it's terrible compared to other phones. I can barely see the screen in daylight when I'm outside.
As an experienced Android and iPhone user, this phone is the biggest disappointment of my life. The lag is horrible and there are so many annoyances like the screen brightness changing all of a sudden (with auto brightness off). We need CM10
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I can confirm that this happens in Netflix as well. If you pause on a scene with clipping, and hold down the menu button, the clipping goes away or atleast improves substantially, right before the Netflix app fades away.
There definitely seems to be something crippling the gamma across the OS
Is it me or am I the only one happy with the screen? It's not that bad in daylight as long as you bump up the brightness and you can adjust the color mode on the screen so it mimics the HTC One color saturation.
Also I don't notice any clipping, fault screen perhaps?
I leave auto brightness on all day I live in sunny Miami Florida and I see my phone perfectly outside. I never have any jump of brightness but in the settings menu I do get a little bit of this blue smearing and whites go a little darker but its minor not enough to make you annoyed. I don't know but I'm having no problems with my phone and I love it
Sent from my SGH-M919 using xda app-developers app
Thermalwolf said:
Is it me or am I the only one happy with the screen? It's not that bad in daylight as long as you bump up the brightness and you can adjust the color mode on the screen so it mimics the HTC One color saturation.
Also I don't notice any clipping, fault screen perhaps?
Click to expand...
Click to collapse
Go to the Play Store and watch the Trailer for Django Unchained.....no clipping? Clipping is present on every AMOLED, just to different degrees
As far as is my understanding, either the screen smears on grey on black, or you have reddish blacks. Some might not notice it or care really
pezlomd said:
I leave auto brightness on all day I live in sunny Miami Florida and I see my phone perfectly outside. I never have any jump of brightness but in the settings menu I do get a little bit of this blue smearing and whites go a little darker but its minor not enough to make you annoyed. I don't know but I'm having no problems with my phone and I love it
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
The smearing can be reduced by using the appear app Scream Adjuster and setting red green and blue to + 5 to +10 depending on how badly it smears.
Yea it sucks. But an update can easily address this issue
can someone give me a specific example of where they're having problems?
I just ran the black/white/APL clipping patterns from AVSHD-709. Movie, Photo, and Standard all show no problems. Dynamic however, crushes blacks. Those who are having issues, are you all running Dynamic screen mode?
edit: upon further inspection, it would appear that 17 and 18 get clipped in movie/photo/standard. It's not perfect, and that's all this guy seems to be demonstrating, but I can't imagine a situation where any of you could be legitimately noticing it. It's well below 10% luminance. Just leaning back in your computer chair can clip that many shades of black or more on an LCD monitor. Just as an example; this would not show up on a calibration report, even if gamma was done in 5% steps instead of the typical 10%.
If any of you are really seeing crushed blacks, I would bet that you're using dynamic mode.
Same issuse
Sent from my GT-I9500 using Tapatalk 2
King Shady said:
As an experienced Android and iPhone user, this phone is the biggest disappointment of my life. The lag is horrible and there are so many annoyances like the screen brightness changing all of a sudden (with auto brightness off). We need CM10
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
You must have a good life.....
King Shady said:
As an experienced Android and iPhone user, this phone is the biggest disappointment of my life. The lag is horrible and there are so many annoyances like the screen brightness changing all of a sudden (with auto brightness off). We need CM10
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Then you need to exchange your phone. I got the 32GB on the 10th and installed the Titanium backup setup from my GS3 and the S4 destroys it in every way. Absolutely no lag, much better battery life, more natural screen saturation, although still oversaturated on the greens. I havent changed the default setting for the screen, which was set on adapt. I am a full time video editor and I just watched the Django trailer off the play store and it was flawless, blacks were crisp, no pixellation or overcrushed blacks and the brightness did not pulsate with changes in luminance from scene to scene. With auto brightness on in a dark room or fully lit room.
I do remember when I got the S3 with ICS stock how terrible the autobrightness was and terribly laggy camera was but after wither the JB update or custom ROMs, all that went away. But none of that exists on this 32GB one I have, so if you applied the latest update and you have the same probs then def get an exchange.
the black clipping is a known issue, and if you're still complaining about lag, swap your phone as everyone who's done that hasn't had any since. as for random brightness changes, noone's mentioned them since the ota
Got rid of the lag by switching launcher to nova and froze a lot of **** from AT&T and Samsung. It hasn't freeze ever since.
The smearing is present but only in the settings menu when I scroll up/down. Not a big deal but I hope it gets fixed.
Besides that the screen is gorgeous and have no complaints. Excellent battery life.
Sent from my Samsung Galaxy S4
I'm returning my t-mobile V10, and just wanted to put some various ramblings and personal opinions here for anyone who's considering this phone. If you already have the phone and you like it, carry on. It's a pretty good phone, all around.
I was coming from a note 3, so I really wanted to keep the 5.7" screen. When it's in immersive mode, it's great, but one thing I didn't account for is that because it has no hardware home/menu/back buttons, the navigation bar takes up some of the screen size. The screen quality seemed fine, and the auto brightness was really quite good. Other than showing pictures to someone, I never found myself needing to take it off auto and increase the brightness.
The second screen seems like a really good idea. Unfortunately, due to a couple of issues, I found myself turning my phone on/unlocking anyway and wishing it had a notification LED instead. The second screen seems to shut itself off after it's been in your pocket/the dark a few minutes, and doesn't turn back on until you push the power button. At least on my unit, there's a lot of light bleeding (not confined to the second screen rectangle) that was disturbing. It's great being able to see graphics on the second screen, which is about twice the size of the notification bar, meaning you can see contact pictures when someone texts you instead of just their name, etc. The brightness on the second screen is far too low, and it doesn't appear to be adjustable (though when the device is on, the brightness is linked to the main screen's brightness, and looks good). Straight on, it's readable but from any kind of angle, the brightness wasn't enough to keep it readable and provide at-a-glance look at the date/time and waiting notifications. I understand part of the idea is lower battery consumption, but again, I found myself turning my phone on and unlocking it rather than trying to make out what was on the second screen.
It seems to be plenty fast, I didn't try any high-end games on it but it appeared to have no problem with me using it while it auto-updated 5-6 apps at a time, which was a very pleasant surprise. The UI is great, but it's not really laid out like i'd prefer, but I didn't get the feeling that the UI was slowing me down. Overall, the UI is a lot better than I thought it would be.
Battery life was mediocre. I probably would have bought the zerolemon extended battery, but it was out of stock at the time. The fast charging was great, but I had a small amount of anxiety about where my next charge would be coming from.
The camera seemed to take great pictures, but i'm not a photographer nor do I pretend to be.
I didn't notice any changes in cell signal between my note 3 and the V10, but I was told the V10 had something significant to pickup the signal better. I didn't notice it in 2G or 4G/LTE, but didn't really encounter 3G. Having said that, it wasn't terrible, just not an improvement.
The speaker was nice and loud for both music and calls.
I didn't even attempt to deal with the bloatware, rooted immedaitely and I tried cm12 but the second screen didn't work (without a notification LED, the second screen working is a big deal for me), and settled on the deodex/debloated rom. Now that i'm returning it, being able to flash it back to stock and relock the bootloader is awesome.
I hope this was helpful to anyone looking at this device.
Why return such an awesome device?
Sent from my LG-H901 using XDA-Developers mobile app
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
CurlyApple said:
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
Click to expand...
Click to collapse
I don't even think about it.
I share the same concerns.
The last OLED phone I had was a Galaxy Nexus and I told myself I'd never get an OLED screen again after that nightmare.
Dealing with the OLED issues has been better with improvements in the technology and overall quality control.
Android OS also has some changes that help prevent burn in. For example the navigation bar and status bar change colors based on the app.
With AOD I know Samsung for example slowly moves the elements around so it doesn't burn in. You can enable the Oneplus AOD with root but Always on Display isn't the same as the Ambient Display on stock Oneplus. Ambient display doesn't stay on screen long enough to really cause any burn in.
Best practices are to avoid high brightness, stay at half or less. If you have a game HUD or other static elements on screen for extended periods of time, rotate the phone when in landscape so it is less likely to burn in.
I'm not an expert on this so i'd like to hear others responses too. This is a more expensive flagship phone so I want to use it for games but avoid the burn in.
I've already read some reports of burn-in on Oneplus Chinese board. The culprits seem to be some Tencent games and its video streaming service. All have very high contrast UI elements, and users tend to turn the brightness very high.
This was the case with my plasma TV. Civ4 left some nasty burn-in in the first year but after so many years of heavy PC usage those remain the only true burn-ins on the TV. It depends on the app. Are there some ways to measure contrast of onscreen elements? In addition to phones I need to replace my plasma with OLED in the coming years.
I got burn in on my OnePlus 3 bc I keep it in my car and use it for a music player, there were times I left it on overnight on a static image multiple times, so if u plan keeping ur phone on all the time on a certain image then u don't have anything to worry about.
I used the Galaxy S3, Oneplus 3, Oneplus 5T all with OLEDs. No burn in. Never. Of course if you are and extrem case and you leave the screen static on for a lot of hours on several days there MIGHT be the risk. But with normal to "normal" heavy usage you shouldnt really be concerned.
CurlyApple said:
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
Click to expand...
Click to collapse
Better u only turn it on for a few seconds, be carefull after 10 sec it gets critical..
Just don't leave the screen on at max brightness for long periods of time and you'll avoid burn in.
Because the pixels are self-illuminating and will eventually wear out/start dimming in an OLED display over time, this will probably be a concern with any phone that has such a display.
I had burn-in with my OnePlus 3T starting after a little over a year of use. I had my 6T for about 7 months and hadn't noticed any problems with it by that point.
I think the biggest culprit in long-term use is the notifications area of the status bar, unfortunately. The notification icons usually directly contrast with whatever is on the screen at the time, which ends up causing the pixels to wear out at different rates. While the burn-in on my 3T wasn't defined or crisp, there was a noticeable brightness difference where the icons usually display, and it was apparent any time there was a solid color in that area of the screen.
https://www.cnet.com/news/oled-screen-burn-in-what-you-need-to-know/
To fight this, keep up to date with swiping away notifications, and use gesture controls in OOS instead of the navigation bar.
Use Auto brightness and enjoy the phone...
Honestly, I would be concerned. I have noticed screen burn on my 7 Pro already. My specific case is that I use Waze while driving, and on long (> 1 hour) drives I get the UI lightly burned in. After I noticed it, I alternate the phone orientation 180 degrees to minimize its effects. I also have the "Colors" screen saver activate whenever plugged in, which has noticeably reduced & corrected the issue. Just be aware and adjust the phone orientation regularly and you should not see anything burn in.
My Galaxy S4 and 1+ 3T both had burn in, but after several years of use. (Same app was the culprit.) I think the reason it happened on my 7 Pro faster is because of the higher brightness and 90Hz refresh rate. Once I kicked it down to 60Hz it does not happen near as often .
thedr9669 said:
Honestly, I would be concerned. I have noticed screen burn on my 7 Pro already. My specific case is that I use Waze while driving, and on long (> 1 hour) drives I get the UI lightly burned in. After I noticed it, I alternate the phone orientation 180 degrees to minimize its effects. I also have the "Colors" screen saver activate whenever plugged in, which has noticeably reduced & corrected the issue. Just be aware and adjust the phone orientation regularly and you should not see anything burn in.
My Galaxy S4 and 1+ 3T both had burn in, but after several years of use. (Same app was the culprit.) I think the reason it happened on my 7 Pro faster is because of the higher brightness and 90Hz refresh rate. Once I kicked it down to 60Hz it does not happen near as often .
Click to expand...
Click to collapse
Do you have your screen turned to full brightness when using waze? I keep mine at about 40-50% brightness. I use maps for 2-3 hours a day 4 or 5 days a week and I have had my 7 Pro since launch and I have zero burn in. I have never had burn in going back to my note 3 days either. I/m actually looking at my OP6 right now as well and no burn in there either (bought that on launch day as well). I also activated forced 90hz all apps on my 7Pro as well and nothing yet. I'm guessing it's your screen brightness that is doing it. Nothing else makes any sense.
Tmobile demo both phone in my store have burn in.... But also does the note 9 and a few others.
Those have the same image on the screen 90% of the time and the screens are set to max brightness to show off the display. All AMOLED displays will burn in if you test your phone the same. When I use maps, I turn off auto brightness and just set it bright enough to see the screen which usually is about 40% brightness. I also change my wallpaper like once a week as well
Had burn in on both 6p and s9 and all in status bar and navigation bar. Now I've installed system tuner and switched on full immersive mode. You need to be rooted though. Using battery widget to look at battery life.
CurlyApple said:
Hello, I've recently purchased a Oneplus 7 Pro and noticed it was using an OLED panel, the problem is that Burn-ins scare me a whole lot, as such, I have been wondering how others have been using their phones. I've tried using Google, but have found nothing truly satisfactory and as such, I have compilled a few questions i had about the display.
- Is screen burn-in still a real issue? and should I avoid using the phone over long periods of time?
- Do "True black" wallpapers help with this issue? what about dark gray? and a bright wallpaper?
- Do both the static navigation bar and status bar have issues? Same with the AOD, does the fingerprint icon cause issues?
- Should I take extra steps to prevent burn-in? (If so, please say which ones, eg. Any practices you have to prevent screen burn-ins)
(On a side note, does anyone approximatly know how long [in general] an OLED panel at medium brightness and daily moderate to heavy use has before it shows signs of burn-in?)
I'm sorry if this has already been addressed, but i have searched through the forums and have found nothing.
Thanks a lot!
Click to expand...
Click to collapse
Used my OP3 for 3 years straight until I switched to the 7 pro. Never had to think about burn in. Just chill and enjoy the device
When using google maps or waze on long trips, keep the screen off till the next turn. That's what i do. I NEVER keep the screen on long enough with a static image. I don't think there is any tech that will not give a burn in with a static image over long periods of time. I will still pick OLED over LCD any day.
equlizer said:
When using google maps or waze on long trips, keep the screen off till the next turn. That's what i do. I NEVER keep the screen on long enough with a static image. I don't think there is any tech that will not give a burn in with a static image over long periods of time. I will still pick OLED over LCD any day.
Click to expand...
Click to collapse
Everyone should just have a spare lcd phone for navigation. I use an iphone 6s for navigation in my card. Tether data from my phone and dont have tk worry about burn in
I use mine for navigation ,i drive a convertible so the screen is always on high brightness.
Never had any issues with my galaxy s8 which i had for over a year and used it the same way. Poor thing had the maps on more than anything else.i broke the display before the any burn ins.
The display should not have any burn ins even after prolonged use.
However you might want to keep it at 90%max brightness.
I make the most of my oneplus 7 pro so if i notice any burn ins i'll just return it to warranty. I don't care ,i use the phone however i want to.
Also the colors are going to be visibly washed out after a few years of use compared to when it was new,that's why i always insure my phones and just get a brand new one before my contract expires.
In order to avoid getting burn-in you have to:
1. Avoid displaying images with static contents for more than one hour at a time. Many people get their keyboard burnt in because they text obsessively.
2. Avoid using a higher brightness than you need.
3. Maybe use the gesture based navigation.
Tipically burn in is a non-issue but displaying static content for more than an hour uninterrupted can get it to appear, depends on the panel, brightness and color being displayed.. Just pause what you're doing every once in a while and you should be fine.
Hey guys, when I lower the brightness to the lowest, the screen looks so weird, everything is washed out, and the left side is less bright. And also more I lower the brightness, grey colors look more greenish. Changing 120hz to 60hz makes a big difference but my question is, is it how the note 20 ultra's display works? Does your display look fine, guys? Should I get it replaced?
Here is the picture of the difference between normal and low brightness: https://imgur.com/a/NubU2ER
i had this big on 3 different tab s6. it is some kind of software-bug, cause this issue does not appear while the device was booting. BUT since you cannot do **** about this (even reseting wont help. some kind of firmware issue) your only option is to get replacement. thats a known issue for amoled-displays (but its also known that if you dimm the display enought, green is the last colour that you will see on the display)