- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Hopefully we’ll see more progress soon
You must log in or # to comment.
Aaaa yay, ubuntu touch user here
I didn’t know about Ubuntu Touch. Thanks.
It’s so frustrating how hard it is to get hardware working. I’m sad it’s not further along, but actually super impressed by the people who keep working on it.
When I was like 10 I wondered why hardware didn’t just have some flash chip with its driver source code written in a standardized way. The idea sounds corny in retrospect, but honestly why isn’t it a thing?
Because the driver is the glue code between the device, and the operating system. What happens when the kernel changes, or needs to change? Then the driver on your devices don’t match up with the kernel anymore. A lot of Windows folks think Windows has some sort of stable interface and that’s why Windows is backwards compatible. But it’s untrue, Windows has inbox drivers, just like Linux has driver’s that build with the Kernel. Any driver that reaches inbox status get brought into the Windows source. As the Windows kernel changes, Microsoft engineers update all the inbox drivers to match the new kernel changes. When companies don’t get their driver inbox’d, they are responsible for keeping up with the kernel changes. Some devices eventually get left behind.
Because there is no such thing as a universal standard for software.
You’re imagining a way for software to talk to each other with something like Esperanto, right? Some universal library interface, a language that can be compiled for every CPU architecture, byte ordering, and operating system.
This would require all hardware vendors to agree on what that interface is, for each type of device. It would require that the API never changes, or else old devices wouldn’t work with new OSes; the alternative is that OSes have to support years of different versions of the language. It would prevent bug fixes, unless you add the ability to flash individual chips, which would make many more expensive. It would have to be a higher level interface which would limit both innovation and performance tuning. But the biggest issue is that this universal language would have to understand every operating system to know how to access itself using the OS’s paradigm.
Oh believe me, I know all those issues exist. The idea would simply never happen.
Unfortunately, If they did have onboard drivers it would only ever be for an old version of Windows. (Same as the disks and then later discs that used to come with hardware)
And in the case of phone hardware and features such as VoLTE it’s intentional so you’re locked into their OS.
Yeah, I know my idea is a pipe dream—it would never happen due to greed.
anyone running UT on a SDM845 or similar? I’ve got pmOS with Plasma Mobile on a OnePlus 6T with 8 GB RAM and it’s hella slugish; recent edge versions are way better than the ones from only six months ago, but it’s still nowhere close to the fluidity of Android.
so might consider trying this, but the install process puts me off as I must first restore the factory OxygenOS in order to install and I’d very much like to not do that.
I’ve found UBports to be a bit more fluid but I’m infatuated with the UX on sailfish which also has a community port for the oneplus 6t, as does droidian iirc
thanks. just bricked mine :( will see later if I can resurrect it. which sailfish port are you running?
Fuck! Thank goodness for MSM tool. I was using this one. https://forum.sailfishos.org/t/oneplus-6-t-the-port-to-get/19875/124 But unfortunately it seems the github page was completely blown away for it.
