Yeah iOS is weird about background processes and some versions are bad about killing parts of apps but not informing the app it was killed when restoring the state of the main process. One reason I personally don’t develop my stuff for iOS. It requires a lot of extra code to deal with the disparate ways in various versions that coming back from being in the background requires. Since just restarting everything can be frustrating to users.
It’s a full release, not a point/patch release, the title just doesn’t show the second .0. They use semantic versioning so it’s major.minor.patch.
It’s also a very minor change and only affects a single configuration property and only people who used relative paths in that property.
I had a lot of trouble with keeping the connections stable and having to reatart services with both KDEConnect and Warpinator, but LocalSend has been perfect every time. I’m using a Fedora laptop with a Pixel 7 Pro running GrapheneOS.
But most of those should support booting from USB devices.
I don’t know that very many people would understand the limitations of it just like they didn’t with ChromeOS. Just need a major hardware manufacturer to start putting a Linux distro on their machines and make a more stable application installation system than KDE Discover or shore up Discover a bit and it would be great to consolidate rpm, deb, etc., rather than adding new systems like Snap and Flatpak.
Arch is not recommended for idiots either. If you want cutting edge, you accept the risks. Works that way with all tech.
…worse for users. Better for them…in the shirt term. That’s the real issue. Short term Profit overrules everything in modern corporations.
Well, they have to be accused of something to be detained. Immigration violations of some types don’t get a court hearing to be “convicted” of those violations by a judge by default.
As others mentioned Esc during boot. You can also configure this in your grub config so you don’t have to hit escape, assuming your distro uses grub. Other boot config options will exist in other systems.
For grub it also depends on the distro as to where it is, but look for /etc/default/grub edit that and on the lone that has GRUB_CMDLINE_LINUX_DEFAULT remove the quiet and splash options. So if it looks like this:
GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash”
change it to
GRUB_CMDLINE_LINUX_DEFAULT=“”
Then run “sudo update-grub2” to make it effective.
Icons for pictures, detail view for everything else. Easier to sort in the detail view.
That was a lot of really good info. I’ve been having to deal with some more complex systemd configurations at work which has gotten me interested in the subject. This was a really good intro and will help a lot in my own self-hosted activities as well as work.
Yeah that can make a difference in some cases. Are they media files? Android tends to do more scanning of those as each is created. You can also set a .nomedia file in the directory that you’re unzipping to on order to reduce sone of that, though not sure if the new AI stuff obeys those like Android itself does.
Pixel 9a has some issues with performance, currently. They used older storage tech for the 9 and 9a than other devices and not enough memory for all the “AI” features that are tracking everything you do to make things more convenient. There are a few articles out there related to some ways to improve performance a bit by disabling some background apps that you may not be using. It’s also possible future updates from google may fix some of whatever is causing the issues for many users.
But it’s not an endemic Android issue, at least not modern versions in my experience. I use GrapheneOS on a Pixel 7 Pro currently and just grabbed a couple of 10+ GB zip files I had on an old dropbox account and unzipped them with the fossify file manager. It was basically instant. Took longer to download them than unzip.
As I mentioned, your best bet is to use ADB or similar and monitor what applications are eating up resources and try to free some up. Especially any apps thrashing the storage or filling memory. That’s assuming you have already uninstalled any bloatware and rebooted recently to make sure no bad apps are stuck.
TL;DR: You should have both due to the explicit breaking of the robots.txt contract by AI companies.
AI generally doesn’t obey robots.txt. That file is just notifying scrapers what they shouldn’t scrape, but relies on good faith of the scrapers. Many AI companies have explicitly chosen not no to comply with robots.txt, thus breaking the contract, so this is a system that causes those scrapers that are not willing to comply to get stuck in a black hole of junk and waste their time. This is a countermeasure, but not a solution. It’s just way less complex than other options that just block these connections, but then make you get pounded with retries. This way the scraper bot gets stuck for a while and doesn’t waste as many of your resources blocking them over and over again.
Bottleneck is usually storage speed rather than processing power. If you have a device that can use external sd cards and your device supports high-speed cards, that might help, though if the controller for sd cards is slow, that might just end up a worse bottleneck. But that’s just a guess and it definitely could be that your memory is not sufficient or background apps are eating up processing, such as crypto-mining malware just as an example. You can check resources over adb while unzipping or try some benchmarks to determine your issue.
Anecdotally, I have no issues on my Pixel 7 Pro and never had issues on past Pixel or Nexus phones I’ve owned (generally higher end models with plenty of memory and storage space). Pixel devices don’t include sd card slots so this is all on internal storage in those cases.
Sure anything is likely to take longer on a phone than on a laptop or desktop, but shouldnt be that significant of a difference unless there’s a hardware bottleneck or other apps are using all the resources.
It’s not that kind of breaking change. It’s a change that won’t affect most people. Only those who chose to use a custom location for their media location and chose to set that to a relative path instead of an absolute one which caused the application to have trouble resolving the paths. The change eliminates a bug by preventing people from doing something that was not intended to be supported. So it’s not a “breaking” change necessarily in the sense that they are changing documented functionality. They are eliminating a way that people can misconfigure the application which may in some cases cause the application to break if someone successfully configured the application in this unintended way.