lol

Appreciate the info & context, and I agree with your overall sentiment WRT device protection against authorities.

I’ll be moving to grapheneOS for my next phone (which unfortunately may be another from the pixel series). I suppose I can try my hand at magisk and other things (I’d still prefer to use MicroG on GOS). If it writes a custom boot image then there’s a chance it’ll prevent boot entirely. I’m not sure if there are other methods for installation or temporary use of root?

I’ve been using calyxOS for several years on pixel hardware, and I’d honestly recommend you go with grapheneOS; it is technologically the more sophisticated project, and I’ve just sort of made my peace with the concessions I have to make using Calyx (it’s kind of ideologically driven, given that I like the idea of microG in principal).

Genuinely I would avoid root on Android if security and device integrity is a key focus for you, but I also empathise with the perspective of wanting to feel like you own the device you paid for. It depends on what you do on your phone; If banking apps or the handling of any sensitive data fall into the equation, I would completely avoid root.

Similarly to you, I also used to block adverts systemwide via hosts / adaway. Today I use Firefox for Android with the ublock origin plugin. Any apps that would have presented ads to me otherwise have kind of been phased out over time by FOSS replacements (if there are any alternatives you need, please reach out).

For a comprehensive backup system, you might want to check out Seedvault? I’m not certain but I hope this will cover your requirements?

I’m not sure what ‘mess with apps’ internal states implies, can you please elaborate on this?

it’s a hard life!

do you have the specific vendor model handy? Maybe it could help soemone else with the exact same model board (vendor supplied clock and voltage properties via VBIOS).

Huh, so the onboard power play was unstable? Which model GPU was this with?

they’re just little bulbasaurs charging up their solar beam

Dash to panel, no overview at login, kstatus / appindicator tray icon support and gsconnect

The no overview at login story highlighted the sheer hubris of the gnome design team. Wild ride.

I wouldn’t be surprised if something like that was the case. Could have been that the successive work was negotiated with khronos & lunarg before the final name was chosen.

Yup, derived from a point in time where Vulkan was seen as a direct successor to OpenGL.

I suppose credit where due, AMD did kind of put an end to mantle, and give that over to the Khronos group to later become Vulkan. XGL as the UMD reference may predate the name Vulkan altogether.

As far as I’m aware, the RadeonSI driver was built internally, whilst RADV was an external effort.

The focus was on AMDVLK as it’s similar in design to the XGL windows vulkan driver

fair enough, it’s still in stark contrast to all of eternal’s exposition, which was pretty hard to watch (the Colosseum scenes especially).

That’s not to say the story isn’t good or interesting,

2016 had the perfect balance between story and gameplay to me, in that the player character expressed flagrant disregard for any narrative elements. This was doom 1 af.

Just keep moving and turn the bad guys into chunks. Need nothing more.

I fucking hated the loop in eternal. I get that the developers wanted you to play in a specific way, they partially achieved this through arbitrary mechanics like ammo scarcity. I can appreciate that it’s a good game, but I didn’t get on with it.

The art style went full Hollywood horror, and the exposition was kinda dialed up to eleven by contrast to its direct predecessor. Very much disliked that you couldn’t crouch (definitely more of a me issue, though I think sliding is a missed opportunity in Eternal’s movement repertoire).

2016’s PvP was imperfect but still fun and much appreciated. Snapmap was super underrated and has many sick community made levels.

The later games are a phenomenal technical showcase; the absolute posterchild for the Vulkan gfx API, but it’s not very ‘doom’ in spirit to me any more

I don’t have a lot of experience with cats specifically, but pets need time to get used to a new home. This can take up to three months.

If this is day one, give them some space, blink slowly at them; let them know you’re gentle and there if needed.

I see. Given the general reception of the 343 games, it’s a little surprising to see people ask for 5 in its entirety, though I will admit there were moments of fun to be had with H5f.

I’m not sure what fire team raven is, will need to look that one up.

what other games besides halo 5? Also why halo 5

Hey, I’m glad you’ve identified the issue. Memory errors are spooky 😟

We must remember our ABCs - always be testing the shit out of new system memory.

Helldivers 2 is autodesk stingray engine / bitsquid.

Did you reinstall the OS when you got this PC?

Have you ever had a passing point? (I.e. has this system ever not crashed in the games you’ve specified?)

Can you please try to verify your memory config and run some integrity tests against that specifically? (Windows memory diagnostic, Memtest86/86+, Karhu)

In Windows’ Event Viewer, can you go to Applications and Services Logs > Microsoft > Windows > Kernel-WHEA > Errors and tell us if there are any entries there?

Can you let us know if you have any minidmp files over at C:\Windows\Minidumps\ or C:\Windows\LiveKernelReports\WATCHDOG\?

Better yet, do you perhaps have a kernel memory DMP over at C:\Windows\MEMORY.DMP corresponding to one of the full system failures where it hangs on the last frame and eventually reboots?

Has any of this ever prompted the AMD Bug Report Tool? Like has it ever popped up to say there has been a timeout or anything like that?

Absolutely no player moderation infrastructure whatsoever. It’s as if they never made a halo game before.

I recall some streamer lady getting relentlessly harrassed via lobby voice chat at the beginning of infinite’s life cycle. Zero recourse; there’s no in-game reporting function (the game directs you to the halo waypoint website, it’s a fully manual process, you supply the offending player’s name, you’re even expected to manually capture infractions via the (still) broken in-game theatre mode).

As for betrayal booting, I have a kind of roundabout theory. 343 in their infinite wisdom decided to disable player collision and friendly fire in the sandbox by default.

On one hand, this is behaviour in-line with contemporary shooters to prevent griefing. On the other hand, it’s entirely detrimental to sandbox immersion and can lead to bad habits when it comes to player positioning.

I suspect this change lead to the oversight of any player booting mechanism, though it’s still possible to team-kill via vehicle collisions.

There’s so much wasted potential in infinite, yet the core mechanics are pretty nailed down.

I’m astounded they released this multiplayer focused game with no betrayal booting or any form of in-game player reporting.