Shobai wrote:Now XDA et al. are finding that some Pixel 2 phones are failing to flash OTA updates and factory images... particularly the non-XL.
Oh joy!
So what's Google's excuse now, with the price argument being dead in the water already?
Personal computing discussed
Moderators: renee, David, mac_h8r1, Nelliesboo
Shobai wrote:Now XDA et al. are finding that some Pixel 2 phones are failing to flash OTA updates and factory images... particularly the non-XL.
Oh joy!
End User wrote:As I said before, the only reason we have the iPhone 8 is because of iPhone X production limitations. The iPhone 8 is a legacy product. It is obsolete.
derFunkenstein wrote:Straight from the horse's mouth: burn-in issues on the Pixel 2 XL are comparable to OLED panels used in other premium smartphones. Uh...the LG V30, maybe, but definitely not happening on my Pixel 2 and it's not happening on the Galaxy phones (it'd be widely reported if it was).
Redocbew wrote:I guess that's corporate-speak for "someone else released a phone with a crappy panel and got away with it, so there's no reason we can't do the same".
DancinJack wrote:(pulled from smart phone evolution thread)
Vhalidictes wrote:EDIT: Why and how is a 2012 Snapdragon S4 Pro CPU faster than some of my 2017 8-9" tablets?
derFunkenstein wrote:Vhalidictes wrote:EDIT: Why and how is a 2012 Snapdragon S4 Pro CPU faster than some of my 2017 8-9" tablets?
Because the Cortex A53 at the heart of so many "midrange" SoCs is hot garbage that should be purged from the surface of the earth.
DancinJack wrote:derFunkenstein wrote:Vhalidictes wrote:EDIT: Why and how is a 2012 Snapdragon S4 Pro CPU faster than some of my 2017 8-9" tablets?
Because the Cortex A53 at the heart of so many "midrange" SoCs is hot garbage that should be purged from the surface of the earth.
I think a more accurate answer would be that you're either buying cheap tablets with crap CPUs in them, or the software on them is crap. I'm not sure i'd call the A53 hot garbage, but it wasn't really meant to be the main event like so many OEMS use it.
Vhalidictes wrote:I have a Samsung Galaxy Tab E, apparently it's a Quad-core 1.3 GHz Cortex-A53 (AKA Snapdragon 410), and it can't handle more than, say, 10 tabs in Chrome without choking, something none of my phones have any trouble with.
ludi wrote:Vhalidictes wrote:I have a Samsung Galaxy Tab E, apparently it's a Quad-core 1.3 GHz Cortex-A53 (AKA Snapdragon 410), and it can't handle more than, say, 10 tabs in Chrome without choking, something none of my phones have any trouble with.
That might be the 1.5GB of RAM filling up, particularly if you have the tablet set to request desktop sites while the phone is loading the mobile-optimized version.
Vhalidictes wrote:DancinJack wrote:derFunkenstein wrote:Because the Cortex A53 at the heart of so many "midrange" SoCs is hot garbage that should be purged from the surface of the earth.
I think a more accurate answer would be that you're either buying cheap tablets with crap CPUs in them, or the software on them is crap. I'm not sure i'd call the A53 hot garbage, but it wasn't really meant to be the main event like so many OEMS use it.
I have a Samsung Galaxy Tab E, apparently it's a Quad-core 1.3 GHz Cortex-A53 (AKA Snapdragon 410), and it can't handle more than, say, 10 tabs in Chrome without choking, something none of my phones have any trouble with.
DancinJack wrote:FWIW, that tablet was released July 1, 2015. So, it's not necessarily representative of an Android mid-range tablet of today. I'm not certain how much it cost when you got it though so I can't be totally sure. It looks like a lot of mid-range (albeit, brand name) stuff is A72+A53 these days. There are some decent looking ones that I'm seeing now like the Huawei MediaPad M3 8.0 or the Asus Zenpad 3S 10.
I'm definitely not going to tell you how to browse the internet, but with only 1.5GB of RAM on-board you might try scaling back by a few tabs and see how it goes.
DancinJack wrote:http://www.androidpolice.com/2017/11/02/pixel-2-xl-units-shipping-without-operating-system/
I mean, I can't suggest ANYONE touch the 2 XL right now. They have completely wrecked this launch so badly.
gcrosier wrote:I just received my Pixel 2 XL last night and so far no issues. the screen color doesn't bother me, works wonderfully so far. Just adding in that they aren't all horrible.
derFunkenstein wrote:I really hope you're able to avoid the burn/retention issues. The Oreo 8.1 beta on my phone draws the navigation bar in white/gray sometimes (like in the Settings app) and black/white the rest. That might help reduce the issue, or it might exacerbate it when the whole section is dimmer.
tipoo wrote:It's really no wonder Apple had to single source their OLED from Samsung. LGs Plastic OLED is nowhere close to the Sammy AMOLED. These issues would be more of a firestorm on the X, though they're still unforgivable at the also nearing 1K Pixel 2 XL.
derFunkenstein wrote:DancinJack wrote:http://www.androidpolice.com/2017/11/02/pixel-2-xl-units-shipping-without-operating-system/
I mean, I can't suggest ANYONE touch the 2 XL right now. They have completely wrecked this launch so badly.
< O_o> what the hellgcrosier wrote:I just received my Pixel 2 XL last night and so far no issues. the screen color doesn't bother me, works wonderfully so far. Just adding in that they aren't all horrible.
I really hope you're able to avoid the burn/retention issues. The Oreo 8.1 beta on my phone draws the navigation bar in white/gray sometimes (like in the Settings app) and black/white the rest. That might help reduce the issue, or it might exacerbate it when the whole section is dimmer.
gcrosier wrote:Well so far, when my nav bar shows up it's black and not white/gray. on the homescreen, all I see are the three symbols on the bottom. in any app, all I see is a black bar at the bottom with those three symbols.