lemann

In the video, the solution looked to be a wireless remote that cycled the MIG cart to the next game, quite cumbersome IMO

From what I've gathered from various sources:

• Orange Pi: Good documentation, but prices of newer models are not as affordable as previously
• Radxa/Rock: Poor hardware support apparently
• Pine64: Amazing hardware variety (phone, smartwatch, IP camera, soldering iron), but documentation can be hit or miss. Check the Pine64 wiki and search around for other documentation by community members
• Khadas: Good documentation, and support directly from the hardware developers, but this comes at a cost
• MilkV: Poor documentation - Ideal if you want to tinker
• Libre Le Potato: Generally hear positive things about their hardware. Hundreds of these were used on a recent YT project in lieu of a Pi with great success, so may be worth a look.

Another thing to check would be Armbian's site - if something is supported by that distro, it might be worth taking a closer look at

A lot of the companies producing these "Pi killers" made them to survive the shortage, because their Pi accessories weren't selling. This means that generally they'll work great with the accessory, but support may be hit or miss outside of that.

I would lean towards Orange Pi personally, mainly due to cost and how long they've been around. Avoid the very early models as there were some overheating issues on a minority of the Allwinner chips - iirc their recent boards are using Rockchip instead.

Edit: add Libre Le Potato

That's sad to hear, ugh...

Thanks for sharing the article though, I never knew they went after that game

While it's good that they have been ramping up production, their attitude towards consumers during the shortage is something that some users won't forget, as well as them seemingly ignoring that they are an education charity.

At least the Pi CEO acknowledges this in the CES interview with Jeff Geerling, where he mentions that the company has been "burnt" from a customer perspective. While they do contribute a lot to mobile linux development (indirectly), I think most people here would probably prefer the company just focus on their original mission of getting an affordable, credit card sized computer into users' hands... not scalpers and hardware developers' warehouses.

Also, I personally don't really want to support Broadcom seeing the horrible decisions they've been making recently - why would they buy VMWare, then proceed to drop ALL of their partners, and put a ton of their staff out of work??

I hope Take Two loses this, what an absolutely disgusting publisher to file something as baseless as this.

There is no star or blue/yellow background on Remedy's logo, even the R is a different color

I saw this on someone's phone and was wondering what it was, seems neat tbh but I already own a ship 🏴‍☠️

I also use a Fairphone and haven't encountered issues with gestures while using a third party launcher (previously Niagara, now Kvaesitso)

Admittedly I switched the gestures back off anyway because I'm just used to using the on screen buttons for the moment

Showing a notification doesn't "evade" battery optimization - as battery optimization is completely independent of Android's memory management.

Showing a notification allows Android's memory management to better assess what apps to kill using a weights system, based on whether they are in the foreground or background, if any of the app's overlays/notifications are visible to the user, and exactly how visible they are.

Battery optimization will kill any non-system app based on how frequently it is used, dependent on its overall background CPU usage, regardless of whether the app is showing a notification or not.

Set the battery usage of your essential apps to Unrestricted and your persistence problem is solved

The background app battery usage feature (otherwise known as "allow background activity", "battery care", or "Adaptive battery") is a different feature to what I'm talking about here sadly AFAICT, and doesn't affect the relative importance weight of apps when Android's memory management is looking for things to kill.

The only thing that the background app battery usage restriction does is stop "inactive" apps from running in the background if they are using up a lot of CPU time, and if the app is not being interacted with frequently: either directly by the user, indirectly via Google Cloud Messaging, or by another app on the device. From what I can tell, it's completely separate to Android's memory management and solely exists to extend battery life.

Android has vastly improved its security by cutting off the workarounds shady (and legit) apps have used to persist.

Shady apps already persist using Google (Firebase) Cloud Messaging, and this change does not impact them. Even if they are killed by the separate background battery app usage feature, a simple push message typically brings these back.

The hacky workarounds you speak of to maintain persistence on A14 should be killed off to improve everyone's privacy.

I wouldn't exactly categorize this as a hacky workaround, since it follows the documented relative app importance weights used by Android's memory management. Users can even bypass this themselves by swiping on the persistent notification, and hiding those types of app notifications.

If anything IMO it forces apps to be less transparent about their activity, since they cannot communicate to the user that they are running

If I'm wrong about the background battery app feature's seemingly lack of impact on Android's memory management please do let me know - I've yet to come across anything suggesting it does ☹️

Their news has been all over lemmy for the past few days, a korean compamy decided it wanted to try and take the devs to court, so the main project packed up shop and some branches emerged in its place.

Would suggest migrating to one of the branches asap, as AFAIK you can still import your data from Tachiyomi, but in future this import capability may not be guaranteed as the codebases diverge

Since Android 10 the OS has really gone downhill IMO.

IIRC they have also been ripping out workarounds that people use to keep their apps open, so expect things like Syncthing/OpenVPN/Element/Termux etc to no longer be able to survive in the background - I believe the non dismissable notifications are a part of that too. To me this also means apps using their own push services are now being forced into a position where they'll need to consider Google Cloud Messaging.

The OpenVPN one is pretty poor because unless you have it set to be always-on, Android can kill it freely now, then completely bypass your VPN preference because "it's not working"

These new changes in A14 kind of show everything wrong with having an ad company in charge of a mobile OS

These analysts can take their ambitious thinking elsewhere. I for one have no plans to upgrade, especially while GPUs cost as much as a console (originally mentioned by @PP_BOY_@lemmy.world )

My R7 2700 + GTX 1060 will carry me until prices come back down