I'm not sure if this is of any help, but I had the same issue with Wake on LAN enabled. This was a while ago with an Asus motherboard.
If you don't need WoL, disable it and it should fix it if your MB is affected.
But if you do need WoL, look at https://wiki.archlinux.org/title/Wake-on-LAN.
The section 5.2.2 Fix by kernel quirks was what fixed it for me.
FlorisBoard with the Material theme.
Tried many, but FlorisBoard's bugs bug me the least, not that there are many. The one feature I wanted was password manager autofill bar, FlorisBoard worked the best at the time and has been solid since. Material theme is nice too.
I've read a lot of outcry about this wrt self-hosted mail servers.
Some say this is fatal, some say it has no effect. Both sides seem to have valid technical arguments. It would be nice to understand the effects better.
Correct me if I'm wrong, but isn't DDG browser also based on Chromium?
Another vote for Aurora.
Universal Blue in general has been really solid, I remember one time in the last year or two when there's been any need for manual intervention. And that came with a notification after boot, with a link to instructions that were all copy-pastable as-is to the terminal.
My biased opinion is that most people run Nextcloud on an underpowered platform, and/or they install and enable every possible addon. Many also skip some important configurations.
If you run NC on a bit more powerful machine, like a used USFF PC, with a good link to it, the experience is better than e.g. OneDrive.
Another thing is, people say "Nextcloud does too much", but a default installation really doesn't do much more than files. If you add every imaginable app, sure it slows down and gets buggy. Disable everything you don't need, and the experience gets much better. You can disable even the built-in Photos app if you don't need it.
Not saying NC is a speed daemon, but it really is OK. The desktop and mobile clients don't get enough love, that's true.
I'm talking about the "bare metal" installation or the community Apache/FPM container images. AIO seems to be a hot mess, and does just about everything a container shouldn't be doing, but that's just my opinion.
Borgbackup in addition to git. Since there's probably not much data, any cheap VPS could act as storage.
Keep at it! The learning curve is not a straight line, just like with any skill. You'll see fast progress, just to be followed by a long plateau of no progress or even feel you're getting worse. And then you notice possibly big improvement again. And again.
Don't worry about following sheets/chords initially. If chords are not in your muscle memory, you're basically doing three complex tasks simultaneously, reading, figuring out chords and fingering chords. I'd try to memorize one or two simple pieces first, to get the chords under your belt. Start simple and stay patient, it'll take time.
Don't forget the rhythm. Play on top of recordings. You can be pretty liberal with the harmonics, but if you keep a steady beat it'll probably still sound good.
There's occasionally something buggy, but the last time I ran Windows there were a lot of bugs too. They're just abstracted away, which Linux DEs don't do at all.
For me, it's about choosing the bugs that bug me less. If Windows is working better for you, just run Windows. Internet points are not worth much.
Flashing the stock Pixel ROM back is just as simple as flashing GrapheneOS, the instructions in GOS website are very good for both.
The only two things I can think of that might be issues are banking apps and Google Pay, if you use that. I use Play services in the main profile and honestly there's not much difference to the stock ROM in terms of user experience. Even Android Auto works nowadays.
For the banking apps, you can have a look at https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/. Just note that if your bank is not on the list, it doesn't necessarily mean it wont work.
Portability is the key for me, because I tend to switch things around a lot. Containers generally isolate the persistent data from the runtime really well.
Docker is not the only, or even the best way IMO to run containers. If I was providing services for customers, I would definetly build most container images daily in some automated way. Well, I do it already for quite a few.
The mess is only a mess if you don't really understand what you're doing, same goes for traditional services.
I've used one called CIFS Documents Provider in the past, worked very well.
It adds SMB/CIFS as a storage provider like Google Drive or Nextcloud to the Android built in file manager.
Available only from Play Store, AFAIK. And I think I was still on Android 14 last I used it.