Markaos
Pixels never had the SD card slot
Since the phones have water resistance, they are technically designed to work under water
Oh, so a device that offers no warranty in case of water damage (because you're not supposed to expose it to water) can use an IP certification as a loophole to completely avoid this law? That's not good
To be fair, giving a company that's been failing to get themed icons to work on Android for almost four years now less than a month to make a significant change to a core part of their software is... quite weird?
Like, the EU usually gives companies at least half a year to comply with smaller demands than this, because companies with such a huge bureaucracy load wouldn't even be able to change an app logo in such a short amount of time.
I don't think it supports displaying HDR at all? The GitHub issue regarding HDR is still open and it definitely doesn't switch to HDR mode when I open HDR photos with it.
The hardware supported it ever since adaptive charging was introduced, so that's not surprising.
The work profile seems like a better place for that, and it was available since Android 5
Just FYI, this seems to depend on where you get the Pixel from - if bought directly from Google, it should be offline-unlockable out of the box. The carrier-sold Pixels are a different story because the carriers demanded it.
Of course check this is true for the specific model you're buying before you actually buy it, but for me the unlock was never greyed out on my 7a.
Pixel - varies by manufacturer
That was the Nexus line, Pixel phones are all made by Google. Although Pixel 5 series and older use Snapdragon SoCs, while 6 onwards use Google's custom Tensor based on Samsung's Exynos. The major downside is IMHO the awful modem efficiency - if I want to keep mobile network on so that I can receive calls, my 7a is limited to 2 days of battery life if I'm lucky (and that's with barely using the phone, just a few pictures).
Edit: and I forgot to mention that all Pixels have great third party ROM support, except if you want GrapheneOS, in which case you need to go for the recent ones that are still supported by Google.
Nah, this development version is way worse than both Android 12+ design and Android 11 design - it just has random unlabeled tiles for system settings where you have to guess the meaning by the icon.
In Android 11, this was only used for the six quick settings you could access when you were looking at the notifications, and they would get labels when you expanded the settings side. In 12+, there are no unlabeled settings anywhere. But this redesign introduced unlabeled tiles for settings you don't use often, which just seems insane to me.
Wow, first time I feel strongly about a quick settings update. It looks awful, taking the worst parts of the Android 12+ redesign and combining them with the worst ideas from the older design, like unlabeled icons.
It looks like there are unlabeled icons in the expanded state? Wtf? If I'm expanding the quick settings, that means I'm fishing for the less used settings, so there's no way I'm going to remember that for example the weird circle with a small segment cut out means "Data saver". It will just be a mystery icon that does some mystery action - that has nothing to do in a modern OS.
It looks like this design is heavily sacrificing usability for people who don't spend hours every day mucking around with quick settings in order to please some hypothetical user who feels more slowed down by swiping over one or two screens than by having to find the one setting they currently need in a big matrix of poorly designed icons.
Edit: also it looks like the home screen is visible under the quick settings - I'm not a big fan of that, I really like the current design where the notifications are pretty much their own separate screen without distracting app content, but that's just my subjective taste. Unlabeled icons are objectively bad.
See, it's pro-consumer. Lol