Intuitive and correct names for "Linux ports" and "Android ports"
-
@doniks
Interesting topic indeed.If I understand correctly even Halium is not correct as some ports called Legacy (I guess) are not based on it.
But if I'm still correct, both are based on Hybris so I would call them :
"Hybris based" ports or devices and "Mainlined" ports or devices.In the "Hybris based" I'd say there are "Halium based" ports and "Legacy" ports.
IIRC legacy because they are inheritance from Canonical, right ?! -
@applee said in Intuitive and correct names for "Linux ports" and "Android ports":
IIRC legacy because they are inheritance from Canonical, right ?!
Yes, and those are the BQ and Meizu devices.
-
@keneda Nexus 5 too IIRC
-
@applee Isn't N5 the first port from UBports?
2015-2023 : Meizu MX4 now in legacy drawer by lack of pristine battery 😫
2023-***** : Nexus 5 (16.04 OTA 25) for daily use, slowly dying 🤕
2024-***** : Fairphone 5 waiting UT for freedom 😉
🇲🇫🇬🇧 -
I don't think "legacy" is totally equivalent to 'inherited from Canonical'. Rather it denotes non-Halium ports.
-
@keneda I am pretty sure there was a port for the Nexus 5 since the Canonical days
-
@keneda No. Fairphone 2 or OnePlus 1 I think. N5 existed back then, but I don't think it was under the scope of UBports really. Someone else just did a port.
-
@doniks said in Intuitive and correct names for "Linux ports" and "Android ports":
My first idea would be "Linux based" and "Android based". I personally find it intuitive enough, but of course it is not correct. Android itself is Linux based.
Both are still Linux. The proper distinction here is "upstream" versus "Android" version of kernel. Though, technically speaking, the PinePhone, PineTab, and RPi do not use mainline kernel, as it's not built from upstream git, but instead use specific kernel versions and configs, which may also have patches not yet accepted upstream.
-
@dobey
Yes i searched the net and found something on XDA back in 2014 https://forum.xda-developers.com/t/port-ubuntu-touch-for-nexus-5.2594874/ -
@keneda Not sure if that's the same person, but the port I remember using was maintained by tassadar (the MultiROM author).
