3 ms·
> That's a chip-related problem. The chips are fine, or at least they are as fine as they were when they were bought, so it is not a chip problem. It is a Goo
by AshamedCaptain 4y ago
> That's a chip-related problem.
The chips are fine, or at least they are as fine as they were when they were bought, so it is not a chip problem. It is a Google problem.
- hammyhavoc 4y agoNote the word "related". It's doing a lot of heavy-lifting in this sentence. The drivers for the SoC are closed source. Qualcomm refuses to update the drivers, meaning more sales. The modern Pixel uses Google's Tensor, not Qualcomm's Snapdragon.
- AshamedCaptain 4y agoIf only there was one entity that literally controls who has access or not to the Google Store, and could enforce practices like actually respecting copyrights (like the GPL) or even using an upstream kernel for any device that ever wants to access the Google Store... This is all Google's fault. They are the ones who develop most of the software. They are the ones who decide what to deprecated and what not. They also set the rules about what is acceptable and what is not ('open' handset alliance my ass).
- dmbche 4y agoYeah I'm on a Pixel 2 still and it's snappy as ever, I would see no improvement at all by buying this year's flagship. I'm sorry to hear other androids aren't the same.
- hammyhavoc 4y agoBut the Pixel 2 got its final update in 2020 and doesn't get security updates anymore, right? I'll take security over performance if it's my daily-driver and I'm doing things that might actually make sense to protect (banking et al), but threat models vary of course.
- dmbche 4y agoYou're right - I forgot about that - I assume my device is already unsecure to the bone, but I doubt that's fine for most people