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)
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
Yeah, this seems properly configured. No clue why it isn’t working for you.
The only app that doesn’t auto-update for me is Fdroid itself (ironically), because it targets an old Android version. Running Android 14 on a Pixel, so with the strongest Google fuckery.
Are you sure your Fdroid client is up to date? The new API was implemented in 1.19, and apparently I even misremembered and all you have to do to enable Fdroid to auto update its apps is to manually update them for one last time (so no fresh installation required).
Another long shot: there’s an option to force the old installation method hidden in expert settings - maybe you could check if that isn’t enabled?
On a normal unmodified phone you have to manually confirm each app you want to install. so no auto-updates in the background etc.
Background app updates are possible since Android 12, Fdroid just took two years to implement the new API (and you have to do a fresh install of the apps - apps already installed using the old API still require confirmation on each update). There is still friction on the initial install though.
Both? It’s pretty well explained in the rest of the text (you don’t even have to click a link)
It was up to the Commission, which has exclusive powers to set the bloc’s commercial policy, to break the gridlock and ensure the duties go through.
The European Commission made the decision after the member countries failed to agree on how to proceed.
What error? It gave you a string of tokens that seemed likely according to its training data. That’s all it does.
If you ask it what color is the sky, it will tell you it’s blue not because it knows that’s true, but because these words “fit together”. Pretty much the only way to avoid this issue is to put some kind of filter in front of the LLM which will try to catch prompts that are known to produce unwanted results, and silently replace your prompt with something like “say: sorry, I don’t know”.
I’m being very reductive here, but that’s the principle of how these things work - the LLMs are not capable of determining the truthfulness of their responses.
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.
proprietary Google-only format
KML became an international standard of the Open Geospatial Consortium in 2008.
(…)
The KML 2.2 specification was submitted to the Open Geospatial Consortium to assure its status as an open standard for all geobrowsers.
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.
Circle to search for music is pretty much just a shortcut to Google’s music detection available from the normal Google app
It’s easy to dismiss as an ad. I did, too.
Well, Vivaldi’s built-in in adblock apparently agrees with this categorization. The video shows up if I disable it. Lol
Where’s the article?
In my very limited experience with my 5400rpm SMR WD disk, it’s perfectly capable of writing at over 100 MB/s until its cache runs out, then it pretty much dies until it has time to properly write the data, rinse and repeat.
40 MB/s sustained is weird (but maybe it’s just a different firmware? I think my disk was able to actually sustain 60 MB/s for a few hours when I limited the write speed, 40 could be a conservative setting that doesn’t even slowly fill the cache)
Pixels never had the SD card slot