My old Nexus 5 was my first smartphone and probably still holds the top spot for price, performance and usability (at the time) of any phone I’ve owned. My current Pixel 6 is somewhat close- but there was just something SO solid and magical about the old Nexus 5.

If you’re gaming you might as well just jump on Bazzite if you’re already interested in Kinoite. Very similar base, but Bazzite has some extras Kinoite doesn’t and it makes a transition into an immutable distro easier.

AMD with ray tracing isn’t great. Not as bad as it used to be, but pretty lackluster overall compared to Nvidia (and to a lesser extent Intel’s GPU offerings). Linux ray tracing via Proton is also not as optimized at present, so that can take something “passable” in windows and make it unplayable on an AMD card in Linux. If you get something overkill for the resolution you’re playing at that can somewhat make up the difference.

If you’re doing 1080p the 6600 is pretty solid. Or 7600, really. It CAN do higher resolutions, but then you’d need to start doing FSR scaling or drop settings to keep things smooth/consistent.

I’m just here to say Bazzite all the way. No clue what that poster meant by breaking issues or problems with rollback… Bazzite is literally designed to be the antithesis of both. The ONLY time I’ve had a problem with it was rebasing my laptop between Silverblue and Bazzite. Technically allowed, but I wouldn’t advise it as that did cause me stability problems. I’d blame Silverblue more than Bazzite in that case, however. A clean Bazzite install has been solid ever since.

Possibly dumb question: why not use an Authentik outpost with a reverse proxy to enforce SSO? It wouldn’t be “baked in” so to speak, but it would be fully OIDC and as long as you’re just running it through a web browser. Biggest downside is you’d need 2 logins (one for the outpost and one for the app). I’d assume the sso is specifically for the extra security though, so that shouldn’t be a problem outside of it being a little hassle.

I believe it’s more a “the PS3 CPU architecture was an absolute nightmare and emulating it is difficult/slow” more than it had anything to do with the graphics rendering portion- which is typically where phones would have made the most substantial advancements. There are specific instruction sets that need to be supported by any CPU emulating PS3 to run anywhere near native speed… And I don’t believe much work has been done for ARM cpu’s to support the needed instructions in mobile devices.

Isn’t AMD’s HEVC/265 still decent, specifically? I feel like I read that somewhere years back. 264 has always been a weak spot for them, however.

Isn’t this almost the inverse argument to the android vs iPhone thing? Like the iPhone being (traditionally) more expensive for the “same technology from 5 years ago”? I don’t really have a horse in this race, I’m a firm believer in use what you like and is easiest/best for you. But I do feel compelled to call this one out a bit.

Software-wise, it seems that the relatively fast adoption of flatpaks and other containerized formats somewhat solves the typical dependency hell that was so common in Linux just a few years back (and to some extent still is an issue today depending on your distro and use case). The hardware support side is a little harder. That’s going to be up to vendors to play nice with the Kernel team and/or introduce reasonable userland software that doesn’t break the golden rule. Until Linux gets more market share the latter isn’t likely to happen. A nice side benefit of the emergence of immutable and/or atomic distros is that users can play around and try things with much lower risk of bricking their systems, so I’d also consider that a step closer in the “it just works” department.

Very true. But brute force checking through tons of different settings for each camera you need to configure is not fun. I couldn’t seem to find any kind of “known working configs” database or anything either. Every camera seems to be different in what it expects, outputs, authenticates, etc. Once it’s set up, I agree, maintaining the config is easier. Having all your cameras match in model and firmware version probably makes the whole endeavor MUCH easier.

AmCrest and Frigate together are SO good. Integrating Frigate with Home Assistant was also insanely easy for quick viewing and notifications. That initial Frigate config is a bit of a bear- but once you’re past that I cannot speak more highly of it.

hunter2

Even with nvme drives which supposedly “don’t need” to use BFQ, I STILL always swap it since it maintains responsiveness across the system during heavy IO loads. I used to have similar full system freezes when downloading steam games which notoriously overload your IO in Linux. BFQ was the solution every single time.

Edit Try following the instructions detailed in this post to add a systemd rule to set the scheduler: https://stackoverflow.com/questions/1009577/selecting-a-linux-i-o-scheduler

The second answer that shows an actual rules.d file example has always worked for me. If using nvme or old school spinning rust you’ll need to change it up a bit. Instead of “noop” set it to “BFQ”.

Try swapping to BFQ io scheduler and see if that makes a difference.

Are you on Gnome, KDE, or some other desktop environment? I know KDE Wayland and Nvidia do NOT play nice (presently).

Are you running it through Lutris? Steam with Proton? That error seems decidedly like a Wine specific problem, which Proton should have ironed out at this stage for this particular game.

*Unless you’re trying to play on hardware with incomplete Vulkan support. Then it’s a hardware support problem that is unlikely to be fixed in a reasonable timeframe.

Ooooh okay. Yeah, I avoided the playstore version. I’m pretty sure I had read somewhere early on that the Playstore version would lack features or otherwise be behind in some ways due to complying with certain Google specific requirements to be allowed on the storefront. Kind of like KDEConnect.

I’ve got it opening YouTube links by default… At least from within other apps. In Firefox I can also hit “open in app” and it pops right up. Casting works too.

I’m going to assume it’s not Universal Blue… But parts of your description reminded me of it.