grow a plant, hug your dog, lift heavy, eat healthy, be a nerd, play a game and help each other out
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?
good to know it can work!
Ah, I’m not sure how well that’d work via yuzu and ryujinx forks. Perhaps if the executable is added through the steam client so you could delegate the functionality via steam input? Sounds messy as heck though.
If you don’t use them to relax your grip in specific types of games (delegating common functions to them and away from thumbs) you might like to use them for DVR capability like instant replay?
If your controller has a gyroscope, you may use them to toggle engagement? Gyro aim can be surprisingly effective once you’re accustomed to it.
Could be a prod ready engineering sample. They get around more than you may think.
suse is neat 🥰
habibi I’m afraid I’ve not had good experiences with manjaro, I may need to defer to someone else in this thread. tumbleweed is cool as heck though.
I’d personally stick to fedora?
This may be at odds with stability somewhat being rolling release, but you may want to check out SUSE tumbleweed or EndeavourOS. You already have a solid pick based on your established requirements.
Couldn’t hurt to poke around other offerings in a VM, though
well, at least they provided some rationale for switching browsers. still, it’s good thing we have bazzite.
I feel that, I just wanted to set your expectations. I prefer and will continue to use CalyxOS but I have no expectation that they will deliver the same level of protections/mitigations at the OS side as Graphene given their project scope is different.
CalyxOS aims for a private, yet simple (attainable) Android experience, and I align more closely with their ideology on having a FOSS replacement for Google Play Services in MicroG.
I suppose one thing you could levarage is work profiles on Calyx to “jail” apps you do not trust, though I’m not sure that meaningfully builds upon Android 15s own application sandboxing.
Perhaps as a long term goal you could look into making a custom fork of CalyxOS for your device and incorporating parts of Graphene’s hardening but this will be a lot of work.
As a calyxOS user, if your key concerns are security and device hardening, I’d recommend you just make a seedvault backup and switch to graphene.
The two projects have somewhat different scopes and I don’t think you’ll achieve the same degree of sw security on calyx.
so sayeth artist_mariana lmao
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?
I don’t believe FPO was expanded to >2 displays, though having identical panels would eliminate VBI complexities. Will be interested in understanding how this behaves with rdna 4.
Huh interesting. Are these displays all the exact same model?
There’s a relatively new feature in the amd gfx display abstraction layer called freesync power optimisation. This feature leverages panel VRR to help mclk idle low at the desktop. This was introduced for single display use with RDNA 2, and expanded to dual display along with RDNA3s MALL advancements. I’m not sure if this is expanded further with RDNA 4 but I can try to find out.
This isn’t true for Vega 10 and 20 due to their use of HBM2. In general what you’re describing is a comparative weakness of GDDR as a technology. I don’t think there’s anything to suggest there’s an inherent issue with idle power on older gen asics at >60 Hz save from the typical limitations with VBI compatibility in an array of panels or display bandwidth thresholds. In the case of VBI compact issues, modifying EDIDs can indeed help.
That’s kind of curious. I don’t think 3D_FULLSCREEN should inherently determine idle mclk behaviour in and of itself. Is this just a single 1440p display at 120Hz? Is VRR enabled?
about fucking time