Idk, ~five years doesn’t seem like a long time with regards to CPUs. I had my Ryzen 2200G from summer 2018 to this January, and I would consider my purchase of a cheap Ryzen 3600 to be a bit premature (and it was definitely an impulse purchase). And it also means that the CPU sticker became outdated pretty soon.

It was removed in Android 12

The author acknowledges that, the blog post seems to be aimed at demystifying the concept of namespaces by showing that a “container runtime” that only does limited filesystem namespaces (using chroot) is enough to get some widely used containers running (of course without all the nice features and possibilities of the other types of namespaces)

saying that my legitimate copy of Windows 11 was at end of service

The screenshot says the version you use reached EoS and you need to update. There’s absolutely nothing about invalid licenses in the screenshot.

Good job for getting upvotes on a “haha winblows bad” troll post, I guess.

However, for most people, the 5-a-day limit might actually provide a better framework for taking high-quality images. This limit makes you think more about your shots, so it could be useful to improve. your composition, timing, and framing.

See, it’s pro-consumer. Lol

OK, so the current dev implementation seems to make accessing notifications one-handed nearly impossible? You need to reach somewhere to the left half of the upper edge to pull them down - the top right corner is already far enough from my thumb most of the time to be a bit inconvenient to pull down on.

And I hope they bring back some quick toggles to the notification screen, it would be awful to have to go to the full quick settings menu just to turn on the flashlight, lol.

If you keep your Pixel plugged in for a few days, it will give you an option to limit charging to 80% (or maybe just turns it on on its own, not sure about that). There’s no other way to activate it currently, but that should change soon (the Adaptive Charging option will have three options instead of just on/off).

deleted by creator

As far as I was aware AMDGPU is used by default on most if not all distros

I really don’t think that’s the case, assuming you’re talking about AMDVLK (amdgpu is the kernel module used by all three Vulkan drivers - RADV, AMDVLK and the Vulkan driver from AMDGPU-PRO). Ubuntu and Fedora definitely default to RADV, and Arch Wiki recommends RADV unless you need something from the other drivers.

I noticed a performance increase after forcing RADV on NixOS so not really sure.

NixOS seems to default to RADV according to their Wiki. If this was a few years ago then maybe you might be confusing it with the ACO shader compiler for RADV? That brought a significant performance increase and eventually became the default in RADV. I remember using custom Mesa (the project that develops open source graphics drivers, like RADV and radeonsi) builds to massively reduce stuttering in DirectX games.

I personally chose RADV after looking into this myself and the only drawback from my understanding is that they are proprietary drivers.

RADV is the open-source community developed Vulkan driver. It has the widest hardware support of the three Vulkan drivers and is generally the best for gaming.

AMD provides two more Vulkan drivers - AMDVLK is the open-source one available in AMDGPU, then there’s the unnamed proprietary Vulkan driver in AMDGPU-PRO. The biggest advantage of the proprietary one is that it is certified - doesn’t matter most of the time, but when it does, a missing certification is a deal breaker.

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

As @Treeniks@lemmy.ml pointed out, the author considers something as small as spawning a separate process for each window to mean a “non-native experience” (wait till they see how web browsers work)

It’s likely the same sensor that is included in the rest of the Pixel 9 Pro Fold.

I see proofreading the first paragraph is too hard these days.

Don’t know about the rest, but…

Does reflashing a ROM fix it?

The phones appear to be simply dead with no response to anything. No way to connect ADB, no way to connect fastboot, nothing.

Also the bootloader allows flashing over the cable only when it’s unlocked (at least on Pixels; I couldn’t find anything relevant in the Android documentation). The vast majority of Pixels should have their bootloaders locked, and it is only possible to unlock it through the system settings, so it’s pretty safe to say that most Pixels cannot be recovered if Android fails to boot because you cannot unlock the bootloader if you can’t get into settings.

That depends a lot on how the license gets interpreted and how license violations are handled by the local law. The argument for why the end user cannot do anything about GPL violation is that the violated contract is between upstream and the “bad” developer - the upstream project gave the bad developer access to their source code under the condition that the license stays the same. You as the end user only get exposed to the bad developer’s license, so you can’t do anything. It’s the upstream who must force them to extend a proper license to you.

However there was also a case recently where the FSF argued that this interpretation / handling of the situation is against the spirit of GPL and I think they won, so… Yeah, it’s just unclear. Which is normal for legal texts (IMHO intentionally, but I’m not here to rag on lawyers, so I’ll leave it at that).

While I agree with your view (at least when it comes to firmware, especially given that hardware that doesn’t require a firmware upload on boot generally just has the very same proprietary firmware on a built-in memory, so the only difference is that you don’t get to even touch the software running on it), the point of this project is to remove non-libre components from coreboot/libreboot.

It doesn’t differentiate itself from upstream in any other way, so if it fails to do the one thing it was made to do, then that’s in fact a newsworthy fact.

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