I *much* prefer LCD purely due to the burn-in on AMOLED. Sony manage to get deep blacks with their LCD screens so I don't think the black thing is such a big deal.
Last edited by a moderator:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Galaxy S7
- Thread starter nviz22
- Start date
- Sort by reaction score
I used a Note 3 for three years with no burn in. Heavy usage from day 1 of release till August this year.
Although the screen brightness did degrade very slightly. The top bar of the screen is usually black, so that part of the screen is hardly "on". So when you watch a movie, you can notice that top part of the screen seems newer/brighter.
No it isn't. It is not burn in or image retention. It has to do with the life time/life span of OLED displays.
That is burn in. The image is retained because the pixels have dimmed at an uneven pace, so the area where your status bar is at the top which has dimmed slower then the rest of the display is now brighter then the rest of the screen. Same thing happens with those with on screen buttons, where the home, back, and multitasking buttons start wearing those pixels out faster.
Burn in would leave a image on the screen. Having part of the screen slightly brighter is not burn in.
Attachments
Burn in would leave a image on the screen. Having part of the screen slightly brighter is not burn in.
But that is exactly what happens when the image is retained. Pixels wear out unevenly and then the image is still visible because parts are dimmer or brighter then the rest.
Jesus Christ, we had to have the Note 7 thread closed because it turned into an iPhone vs Samsung tit for tat nonsense.
Likewise there are a handful of threads that you are all posting the same rubbish over and over again and turning everything into a glorified pissing contest.
This thread is for the Galaxy S7. Either discuss the galaxy S7 or create a dedicated thread to the tit for tat bickering.
Back OT or move on folks.
Likewise there are a handful of threads that you are all posting the same rubbish over and over again and turning everything into a glorified pissing contest.
This thread is for the Galaxy S7. Either discuss the galaxy S7 or create a dedicated thread to the tit for tat bickering.
Back OT or move on folks.
My S7 edge hasn't got the Samsung Cloud update yet. For back ups, does it also back up app data?
https://www.smugmug.com/gallery/n-Mzb5Hj/i-jWwSZNj Here are two things I took a picture of. The S7 definitely has more pop. But in real life, the iPhone 7 plus actually matches the colors that are really on what I took. Like the wall is white, but the light that was shining has a yellow color to it, so it is really making the wall look yellow. The iPhone picked up on that correctly. The car is also not bright RED in that pic, it has an orange tint to it which the iPhone got. So the iP7 is definitely more color accurate.
That’s unfortunate.
One of the things I really miss about ios is not having to worry about back ups. Most people bash it, but iTunes and icloud did a great job of backing up everything at once. None of this “one app for this, one for those” nonsense. I know of titanium, but this phone is staying without root for now.
Android is terrible with backups, absolutely agreed. That's pretty much the only thing I miss about having an iPhone. How come it didn't occur to Google that some weirdos might want to, dunno, keep backups?
In fairness it's got a little better with marshmallow and nexus devices (now pixel) but still a good way behind, but that's because of variety of OEM's, different versions of Android etc ...
Yeah that's true ....
Maybe Google should just buy TB and roll the tech directly into Androids core.
Just saw this, its a speed test between the Pixel and iPhone 7. I know this is the S7 thread, the point is that the way the pixel began reloading apps in the second is very reminiscent of how Samsung phones have done in this same test, resulting in a lot of flack for touchwiz, but here is Googles version and it does the same thing. It's weird because I've seen tests with HTC phones and past Nexuses that haven't done this. Could this be a result of using the faster on board storage that Samsung has been using for a while?
I wonder if thats the 128GB model?The other speed tests showed Pixel running circles around the 32GB version while some showed them being almost neck to neck.In this test though (I really am suspicious if he rigs his tests) ,it seems as if iPhone is demolishing the Pixel phones.1 Minute and 55 seconds vs a whole 3 minutes?At this rate even the Pixel 2 coming out next year wont be able to beat iPhone 7
I doubt he rigs it, he mostly uses android phones as his daily drivers, he seems to favor android over iOS.
Most of that was lead was from reloading apps, apple has just done an extraordinarily great job at optimizing ram. Hope google gets on that now that they got the frame rate stabilized.
It was last years Samsung devices with their aggressive ram management that exhibited same, the S7/S7e didn't suffer as much from the issue (especially the exynos variants which outperformed the Snapdragon).
But yeah, I'd like to see the same test against the Nexus 6P so we can see if it's a software issue on the Pixel.
The 6P previous Phonebuff tests didn't do this.
So why ?
Two possible scenarios.
1) Android 7.1 on the pixel still has bugs / chinks that need to fixed
2) The underclocked Snapdragon 821 could point to the fact they are also aggressively killing ram as a way to extend battery life.
We have seen the OP3 do a similar thing where it's 6gb ram on arrival only performed like a 2gb device, and even with the update to fix the issue, the build.prop limited adjustment OP changed to means it still only uses around 3 tops of the 6gb available. (Meaning unless you circumvent the issue and adjust build.prop yourself you will never benefit from 6gb).
Anyway so there are your two scenarios.
1. Buggy software
2. An artificial ram limiter which expunges stored data early in order to preserve battery.
If it's the latter, that would truly suck. A €750 pixel shouldn't perform like a €250 Nexus 5X memory wise.
However I hope it's the former and it's simply buggy software.
Time will tell, what we need is a Pixel Vs Nexus 6P running 7.0 to see a comparison in behaviours.
Last edited:
I don't know, I'm thinking you're right and it's #2, it's probably aggressive ram management to prolong battery life and relying on the faster storage to makeup for it. That seems to be what Samsung did and then dialed it back with the S7 line, though even then it still wasn't where the iPhone is now.
821 is underclocked, and the Pixel struggled particularly with rendering video. Otherwise, for most "average" apps it did just fine.
But have to say the iPhone is pretty damn good. That chip is fire.
[doublepost=1477474167][/doublepost]
Previously would have agreed with you but when I went from Samsung S6 to S7 a couple of weeks back, I was shocked by just how much the whole process had improved.
I'd say it backed up about 95% of everything - between Google and Samsung, anyway - and that remaining 5% was just faffy passwords for certain apps that I had to log back into. If I finally used something like 1Password (I've been saying I would for 2 years now!) then that process would have been a lot quicker.
It even transferred the lock/homescreen wallpaper pics across. Music. Photos. Apps in the right position (and in the app drawer). Messages. Documents. Videos.
It was a massive step up from the painful processes of yesteryear.
However, I do recognise this was Samsung to Samsung. Even so, definitely much improved and Google chips in at the beginning for 5 minutes too with their own back up.
Also, agree that the general 100% backup of syncing to iTunes is something I do miss. It boggles my mind how many people I know with iPhones that literally never backup their phone properly!
But have to say the iPhone is pretty damn good. That chip is fire.
[doublepost=1477474167][/doublepost]
Previously would have agreed with you but when I went from Samsung S6 to S7 a couple of weeks back, I was shocked by just how much the whole process had improved.
I'd say it backed up about 95% of everything - between Google and Samsung, anyway - and that remaining 5% was just faffy passwords for certain apps that I had to log back into. If I finally used something like 1Password (I've been saying I would for 2 years now!) then that process would have been a lot quicker.
It even transferred the lock/homescreen wallpaper pics across. Music. Photos. Apps in the right position (and in the app drawer). Messages. Documents. Videos.
It was a massive step up from the painful processes of yesteryear.
However, I do recognise this was Samsung to Samsung. Even so, definitely much improved and Google chips in at the beginning for 5 minutes too with their own back up.
Also, agree that the general 100% backup of syncing to iTunes is something I do miss. It boggles my mind how many people I know with iPhones that literally never backup their phone properly!