But ChatGPT doesn’t have a way of “knowing” that there is no such Flatpak - it’s unlikely that its training data includes someone explicitly saying that. But it’s fair to “assume” that a Linux file manager is available as a Flatpak.
(…), so it’s definitely making up stuff.
Yes, it’s an LLM
The “security wormhole” is clipboard history managed by the OS. That’s all. Crappy clickbait headline.
Honestly, this is not really technobabble. If you imagine a user with a poor grasp of namespaces following a few different poorly written guides, then this question seems plausible and makes sense.
The situation would be something like this: the user wants to look at the container’s “root” filesystem (maybe they even want to change files in the container by mounting the image and navigating there with a file manager, not realizing that this won’t work). So they follow a guide to mount a container image into the current namespace, and successfully mount the image.
For the file explorer, they use pcmanfm, and for some reason decided to install it through Flatpak - maybe they use an immutable distro (containers on Steam Deck?). They gave it full filesystem access (with user privileges, of course), because that makes sense for a file explorer. But they started it before mounting the container image, so it won’t see new mounts created after it was started.
So now they have the container image mounted, have successfully navigated to the directory into which they mounted it, and pcmanfm shows an empty folder. Add a slight confusion about the purpose of xdg-open (it does sound like something that opens files, right?), and you get the question you made up.
Yes, you can’t install F-Droid
TL;DR: the minimum went from 16 to 32 GB
Nobody’s saying that Google won’t give them the code, though. Nothing is moving to closed source, Google just isn’t going to be showing the current work-in-progress code for the next release to the public.
How so? I doubt many ROMs are based on code that isn’t part of an Android release. Surely GrapheneOS devs can just use the Android 16 branch once it’s released to make an Android 16 version of GrapheneOS.
Not in the CPU/modem department, that’s a first
Nah, the kernel isn’t that important for apps - you can replace the kernel and update the massive Android framework to work with the new one relatively easily (you will need some Linux compatibility for native code that does syscalls on its own, but that’s pretty much it - even WSL1 could do that).
It’s all the APIs and system apps provided by Google that have no reasonable alternative in AOSP that are the problem for compatibility. Look how incomplete projects like MicroG (an open-source implementation of Google Play Services) are, and their only goal is to provide Android compatibility for unofficial ROMs without installing the proper Google services.
Google Maps is US-based whether you use it in the US or anywhere else
As far as I know, bootloader locks are done by the manufaturer not by the provider.
Verizon requires the phones they sell to NOT have the ability to unlock the bootloader. That’s why there are separate factory images for Verizon Pixels.
What do you mean “now”? Google Photos has had a photo editing feature for a very long time now
The package name is visible in App info, no need to install anything - just long press the app icon, pick App info and scroll down to version
That indeed is a Bluetooth feature that supposedly makes audio quality better by only lowering the volume using the actual speaker driver instead of doing it digitally and potentially throwing away some quiet sounds. In theory, doing it this way is always better and should be preferred. In practice, many devices handle it terribly.
If you want to turn the feature off, you can enable developer options on your phone (settings -> About phone -> tap Build number a bunch of times) and turn off absolute volume. That will give you back software volume control with fine-grained adjustments.
The CPU is still Google’s Tensor, and the modem on current Pixels is already a blackbox that custom ROMs interact with using binary blobs ripped from the official ROM. There isn’t much that could get worse with this change.
Google Drive app -> New (in the bottom right corner) -> Scan. It’s not supposed to be a part of the camera app, that’s just a useful shortcut.
Yeah, stock Google voice recognition also works offline if you download the language model beforehand.
Indeed, try switching your smartphone to airplane mode and see how far your voice commands get you.
Did that (or rather disabled mobile data and WiFi, because airplane mode would still keep the WiFi on), and then I dictated this sentence after the parentheses. So Google’s voice input works offline just fine.
Or do they mean something like a smart assistant? In that case fair, but it’s not like it will work with text input either.
It is true, however, that Google Translate doesn’t do offline voice translation even if the language you’re trying to translate from is downloaded for system-wide voice recognition.
That sounds like Xiaomi. The best price to performance ratio of any OEM, but at the cost of terrible software and this… experience… when you want to get rid of it.
Worth noting that not all OEMs are like this.
That’s weird, it works for me on Android 15 and I could swear it was always the case for me.
A simple way to disable the sound is to press a volume button, tap the small button at the top and pick silent or vibrate there. Does that really not work for you? Btw the screenshot sound is linked to ring volume, not notifications.