

At least they don’t cheap out on the VRAM if there really is a 16GB variant
Verspielt verspult 🧑💻
At least they don’t cheap out on the VRAM if there really is a 16GB variant
Their FAQ says kind of:
Many other devices are supported by GrapheneOS at a source level, and it can be built for them without modifications to the existing GrapheneOS source tree. […] In most cases, substantial work beyond that will be needed to bring the support up to the same standards. For most devices, the hardware and firmware will prevent providing a reasonably secure device, regardless of the work put into device support.
The requirements that GrapheneOS has on the hardware, like relocking the bootloader and hardware level access, should be part of rights to repair / digital markets act imo. They are even considering producing their own hardware in the future.
Those do not have to cancel each other out necessarily. The open and modular design of Application APIs in AOSP lets the user decide which way they want to interact with the devices they own compared to the walled garden. Graphene does an excellent job by leveraging this design with further encapsulation while focusing on baseline compatibility and keeping up with google. Sadly the last one is a difficult task, so some features may take their time, while others we may never see.
That’s interesting. Apart from the pathfinding, Osmand behaves kind of sluggish for me and I had to get used to the UI/UX which can be overwhelming at first (even for tech savy people). But therefor its also a lot more sophisticated and feature complete which I also like.
To each their own, maybe even both ;)
Organic maps is the best alternative I could find. It’s on Accressent which you can get from the GrapheneOS App store. All the maps you want are downloaded to the device, no need for network access afterwards / continuously. Pathfinding is fast compared to e.g. Osmand. It’s pretty barebones though.
Thanks for the great writeup! Some of your Issues may be fixable, others stem from the fact that its sadly an alternative OS developed by a hand full of people compared to a multi billion dollar corp. But trying out new things and seeing true progression in development can be exciting too / make up for the inconveniences. In the long run this project can’t stay dependant on google, since they make their money from data and not hardware, and one of GrapheneOSs main purposes is to remove that source of income i guess. Also google is known to kill their products out of nowhere. Anyways:
The GrapheneOS forums say there is no intent on implementing this. It will probably be locked behind Google play services anyway.
Could be a great opportunity for MLC Chat, which uses OpenCL.
Or forbid network access in graphene os
Favourite Far Cry 2 and 3 are the best of the bunch imho
Would be nice if there could be an implementation by someone else than apple or google
Just checked and i guess you’re right! Time to do some distro hopping again lol.
Not the heroes we deserve, but the ones we need.
Would be great to see some major distros shipping with KDE by default. Fedora e.g. had this idea a little while ago.
There are some Raspi competitors offering SBCs with RISC-V chips, there is even a RISC-V Mainboard for the framework laptops, but the last time I checked they sadly didn’t reach the performance levels of comparable ARM chips.
Switched from a raspberry pi 3 to a second hand x86 thin client (lenovo thinkcentre m920q) because raspberry pi 4 were not available at the time. Made me learn proxmox and a bunch of other cool stuff my raspi couldn’t handle.
I’m rooting for ARM / RISC-V to become more popular in desktop computing / servers though.
Scary that they banned WhitePeopleTwitter, a sub with 3M+ subscribers.
I have a suspicion that this isn’t even about culture or revenue anymore. It’s about control.
I have the same setup, you have to add the line Environment="HSA_OVERRIDE_GFX_VERSION=10.3.0"
for that specific GPU to the ollama.service file
Therefor we got Finamp now, which is really good and about to get even better.