Weird coincidence that the exact reason for this thread is addressed in https://github.com/nextcloud/android/releases/tag/rc-3.35.0-01. RC2 was just released yesterday.

This. I had symptoms extremely similar to OPs and saw this in the kernel logs immediately before the system would reset:

[    0.705185] mce: [Hardware Error]: Machine check events logged
[    0.705187] mce: [Hardware Error]: CPU 17: Machine Check: 0 Bank 5: baa0000000090150
[    0.705190] fbcon: Taking over console
[    0.705191] mce: [Hardware Error]: TSC 0 MISC d012000200000000 SYND 4d000020 IPID 500b000000000
[    0.705195] mce: [Hardware Error]: PROCESSOR 2:a20f12 TIME 1678252812 SOCKET 0 APIC 3 microcode a20120a

It turned out to be a hardware issue with my CPU (AMD Ryzen 9 5950X). I got it replaced under warranty (twice actually, the first replacement had other issues) and everything is fine now. Definitely check what the kernel logs say.

You can look at the previous kernel log from before a reboot with journalctl -k -b -1 (as root)

You can do it just in the sketcher and get 90% of the way there with just sketcher constraints. You can also create a body with a subshape binder for each sketch line and use assembly and create an animation. You don’t even need 3d solids. I created a gif, we’ll see if it attaches properly to this reply…

I dunno why but this immediately made me think of Uplink https://en.wikipedia.org/wiki/Uplink_(video_game)

Someone posted this https://webvm.io/alpine.html in another community and it made me think of this post. I’ve never used webvm and I suspect there are many downsides but seemed relevant and the demo seems to be able to run a full desktop environment. You have to find a CAD software that supports Linux though which is a controversial topic at best.

There is also Cascade Studio (Demo). Sadly development has stalled, it was a really cool project.

Probably not at all what OP is looking for though since TinkerCAD is just sketch/primitive type workflow, not like openscad.

The really hilarious thing to me is that the NextPush app (unified push provider that can be run on your nextcloud server) is unsupported by nextcloud talk. But it is supported by a bunch of other competing applications.

Gatgetbridge (your link) has a breakdown of devices they support https://gadgetbridge.org/gadgets/ . You can click through the vendors to find devices which are both “highly supported” and “no vendor-pair”. Meaning most/all the features work without any reliance on the vendor app.

As for the similarity you are asking about with pixel->GrapheneOS, there are very few watches that can run an alternative open source firmware or operating systems apart from the ones that are already open source, like bangle.js, pinetime, etc. Wearables are even more specialized than phones, they require specialized code designed specifically for them and would likely require pretty extreme effort to reverse-engineer.

I use a pebble 2 HR with gadgetbridge but the watch it self runs the old pebble firmware which gadgetbridge talks to. This is fine for me, but if you are looking for a more modern watch you may have to make some compromises.

Ok, I’m prepared to be downvoted today so here goes.

Nextcloud is an enterprise cloud suite. The one you run in docker on your rpi (or whatever) is the same one that is run at a company, albeit with more high availability and redundancy, but the same application, proxies, caching, db, etc. Nothing is stopping you from running the stable channel and testing your upgrades, or even rolling out specific stable client versions to your devices.

Said companies often have teams (more than one person) to run it, stage upgrades, automated testing, automated backups, monitoring, etc. They go to work and do just that, maybe not every day but at least a couple times a week their focus is Nextcloud and only Nextcloud.

What many people in the self hosting community do is spin up docker, without ever having touched docker before, and try to run Nextcloud, forget that it exists, and then upgrade it a year later across multiple versions without maintaining the database. Then they obsess about how fast an app loads by refreshing it a whole bunch, and then complain on internet forums that it sucks. This, like many posts, doesn’t have a specific problem for us to help with, no logs or stack traces have been posted, and the subject of the complaint shows just how terrible your understanding of application security is.

So, while there is legitimate criticism of some of Nextcloud’s design choices, this isn’t it. And at the risk of sounding a little gatekeepy, if you post “nextcloud updates break everything” with no context you probably should spend some time gaining a better understanding of how internet facing services work and make an attempt to fix the problem (probably misconfiguration, and in this desktop client case probably a heap of un-updated local software installed alongside the client), which I’m sure people would find if they did the bare minimum of reading a few log files or any of the other things that come with being an application admin.

This is… exactly my setup too. Works great. The brio is a tiny bit weird in that it appears as two independent video devices in Linux, but choosing the right one is all that’s necessary and it works fine.