Then my coworker got the Pixel 8 Pro, and it has WAY worse battery life than my 7 Pro, he even went and got a new one at the store because it was so bad it had to be a fault, but no. It just is absolute garbage.
As an engineering lead I do a lot of my non-programming work directly on Pixel, including tons of remote desktop, meetings, GitHub/productivity, k8s management, etc. I don't get to write code nearly as much any more, probably around 10-20% of my work week. At least for those workloads, things are fine. But the workload you run can dramatically change things, especially if you've got particularly power hungry apps involved. The OS gives you tools to identify what those apps might be when you dig into the battery area of settings.
> even without google play services. (came from a 5a)
Since you can't remove GMS from a Pixel without flashing a ROM to it as far as I know, can I assume you are not using stock software? A lot of Pixel's battery performance is made up using the adaptive battery features. When they are off, things are more dicey. Do those work on custom non-GMS ROMs to begin with?
To sum it up, battery can definitely be better, but I'm just not seeing the kinds of problems people complain about and that surprises me given my experiences.
I wonder if there's a Termux equivalent for iPhone. It's the only thing keeping me on Android at this point.
If my financials got better, I'll definitely move to iPhone
Would you mind elaborating on this point?
I heavily doubt that Qualcomm is even capable of working in such a role. In fact, the C-suite probably believes that their core competency is lawsuits and not modems, anyway.
[0] https://twitter.com/calebccff/status/1472517091970494465
(Edit: I meant semi-custom SoC design/architecture not cores, like https://www.anandtech.com/show/7281/understanding-amd-semi-c... )
Yes, the early generations of Snapdragon SoCs were built using a custom ARMv7 core called Scorpion, which was later succeeded by another v7 core called Krait. The first ARMv8 SoC (the infamously disastrous Snapdragon 810) used stock ARM cores, but the next generation (820) switched to an in-house v8 design called Kryo. Around that time though, the company did massive layoffs, including in silicon engineering, leading to all the subsequent designs using tweaked ARM cores (despite also being called Kryo)
It's not 1 of capability. They're trying to force everyone to use the full SoC and not just the modem.
Google doesn't have nearly the same leverage and volume numbers to use against Qualcomm as Apple does, but even for Apple it's a devil's bargain. The licensing terms are incredibly onerous. If they updated them and you didn't agree, they used to just cut off your entire company's chip supply until that was ruled monopolistic and illegal. The royalties (one of the only royalties Apple actually pays) are substantial percentages of the final device price. Getting into bed with Qualcomm needs to be weighed against the risk to the rest of your business.
As a consumer, I buy Qualcomm modem phones, but as an engineer Qualcomm is only marginally below the plague on my avoidance list.
It's just a shame, even now I find myself eyeing the black Friday sales prices. I loved everything else about the phone, but I know that the battery life is going to drive me mad and with all the heat and increased number of charge cycles there's just no way the battery is going to last as long as the support does and that's a deal breaker for me.