Live data from Hacker News

Pocketblue – Fedora Atomic for mobile devices

github.com

11–20 of 52 posts

Re: Pocketblue – Fedora Atomic for mobile devices

#11
post #8

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!

Re: Pocketblue – Fedora Atomic for mobile devices

#12
post #6

how does something like this not support pinephone and librem5 from day 1?

Its just that none of the maintainers has a pinephone

Though it would probably be trivial to just copy what the non-atomic Fedora Mobility does for pinephones, I might as well do this in the future and just ask someone with a pinephone to test

Re: Pocketblue – Fedora Atomic for mobile devices

#13

It doesn't look like there's anything in the way of information posted that includes screenshots or what apps are included or available? Am I missing the link?

It's a new-ish project FYI. But to answer your questions:

- Apps: It's Linux (like desktop or server), but "image-based" so you install apps in containers like iOS or Android do (and therefore OS updates basically-never break). https://flathub.org is generally the main app store for Linux containerized phone apps.

- Screenshots: It'll look the same as other Linux-on-phones, so like https://en.wikipedia.org/wiki/PostmarketOS for instance. It's just built differently.

Re: Pocketblue – Fedora Atomic for mobile devices

#14
post #8

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!

No shade meant by the way, I fully understand how difficult it must be to support devices. Good luck!

Re: Pocketblue – Fedora Atomic for mobile devices

#15
post #6

how does something like this not support pinephone and librem5 from day 1?

Its just that none of the maintainers has a pinephone Though it would probably be trivial to just copy what the non-atomic Fedora Mobility does for pinephones, I might as well do this in the future and just ask someone with a pinephone to test

I have a PinePhone (original KDE Community Edition, convergence variant). I'd be more than happy to test for you! Email address in my profile :)

Re: Pocketblue – Fedora Atomic for mobile devices

#16
post #2

This is based on bootc (bootable containers), so note that the OS build is described in a normal Dockerfile: https://github.com/pocketblue/pocketblue/blob/main/Container... which is then run by the Github action (or locally). Very similar to how Universal Blue, Bazzite, Bluefin etc. build at https://github.com/ublue-os/bazzite (see their Containerfile), but for mobile. Has a similar mission to https://postmarketos.or…

Are we really bringing OCI to freaking OS builds? Nothing about OCI is pleasant. A list of Tarballs is the most backwards boot format I can think of. Terrible for reproducibility. Terrible for security.

Boot images should be Dm-verity protected EROFS images. We should not be building new things on OCI. It's really mind-blowing to me that this is a new direction people who are supposed to be top of class OS builders are moving to as a direction.

They took the CoreOS dream and threw everything in the trash

Re: Pocketblue – Fedora Atomic for mobile devices

#17
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.

Re: Pocketblue – Fedora Atomic for mobile devices

#18
post #17

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.

Re: Pocketblue – Fedora Atomic for mobile devices

#19
post #2

This is based on bootc (bootable containers), so note that the OS build is described in a normal Dockerfile: https://github.com/pocketblue/pocketblue/blob/main/Container... which is then run by the Github action (or locally). Very similar to how Universal Blue, Bazzite, Bluefin etc. build at https://github.com/ublue-os/bazzite (see their Containerfile), but for mobile. Has a similar mission to https://postmarketos.or…

  > Dockerfile
nitpick: Containerfile. I mention it because people still think container==docker. I am sure the Fedora people focus on podman, as part of the Red Hat ecosystem. For a better dev experience they offer podman-bootc¹, which you will miss when using Docker. Personally I am convinced that we should steer people to podman instead of Docker.

1. https://docs.fedoraproject.org/en-US/bootc/getting-started/

Re: Pocketblue – Fedora Atomic for mobile devices

#20
post #2

This is based on bootc (bootable containers), so note that the OS build is described in a normal Dockerfile: https://github.com/pocketblue/pocketblue/blob/main/Container... which is then run by the Github action (or locally). Very similar to how Universal Blue, Bazzite, Bluefin etc. build at https://github.com/ublue-os/bazzite (see their Containerfile), but for mobile. Has a similar mission to https://postmarketos.or…

Are we really bringing OCI to freaking OS builds? Nothing about OCI is pleasant. A list of Tarballs is the most backwards boot format I can think of. Terrible for reproducibility. Terrible for security. Boot images should be Dm-verity protected EROFS images. We should not be building new things on OCI. It's really mind-blowing to me that this is a new direction people who are supposed to be top of class OS builders a…

  > Dm-verity protected EROFS images
First time I hear about it. Playing the devils advocate: how does it improve over checksums + tarballs?
Post reply on HN