41–50 of 52 posts
I'm surprised anyone would launch a mobile GNU/Linux distro without support for the Pinephone.
That said, as mentioned in another thread here, work is being done to add PinePhone support.
Earlier quoted context omitted.
Red Hat obviously wants to change people's vocabulary but "Dockerfile" is basically an industry-standard generic term by this point.
That is true, the same for "to google" if people mean "to search". It does bury the generality of the concept though. Like I said, a nitpick.
Oh, Linux on mobile. My cynic take: - only works with very few phone models - battery doesn’t last long - bad UI with tiny elements. - not managing a smooth refresh rate - no apps That‘s the pattern we‘ve seen over and over again. The only approach that has worked better is to base things on AOSP.
Very unhelpful comment. Some people don't want to run on anything AOSP. Being able to manage the device with standard linux tooling is a major plus for some people.
Oh, Linux on mobile. My cynic take: - only works with very few phone models - battery doesn’t last long - bad UI with tiny elements. - not managing a smooth refresh rate - no apps That‘s the pattern we‘ve seen over and over again. The only approach that has worked better is to base things on AOSP.
AOSP doesn't run on a single phone on earth, not even the android emulator. Android also has it's own problems.
This is good to see. The concept of immutable OS and fallback boots is going to be much more common. I think there are similar concepts being explored in postmarketOS such as https://gitlab.postmarketos.org/postmarketOS/duranium I've tried the silverblue desktop version of this and while I'm not convinced that a mix of OS/Brew/Flatpak/Containers is making things more approachable it's interesting to see these concept…
Earlier quoted context omitted.
AOSP doesn't run on a single phone on earth, not even the android emulator. Android also has it's own problems.
Sure, just like Linux doesn't run on a single phone on earth, unless you make some adjustments. I don't see a problem with that.
In AOSP, not even the call app is usable nowadays. AOSP doesn't have any functional UI anymore.
So depends what's your definition of a phone stack, if it includes a call app, an agenda or a keyboard, AOSP doesn't fit it.
Earlier quoted context omitted.
AOSP doesn't run on a single phone on earth, not even the android emulator. Android also has it's own problems.
But custom roms based on it do, like lineageos and grapheneos.
Supported devices: Xiaomi pad 5/6 Oneplus 6/6T ... That's it. Does anyone know if there's plans for more? Is this project in very early stages, or is it going to be another Graphene OS with an extremely limited device support?
There's also Poco F1, we just haven't released it yet, and I am yet to add it to the docs (we'll have a single common image for both op6(t) and beryllium soon) There's also a person working on a Fairphone 5 support and I think someone was going to work on a PinePhone port Contributions are always welome, we need more devices!
Are these devices so different that none of the testing and development work is transferable to the newer devices?
And, reversing the question, if one was to be the owner of a such a Xiaomi device, what can be done to help them being supported?
I'm surprised anyone would launch a mobile GNU/Linux distro without support for the Pinephone.
Written on a Pinephone.