It isn’t really convenient to do that at the moment, but here is a guide that involves some manual looking around in pmaports: https://wiki.postmarketos.org/wiki/Configure_postmarketOS_for_multiple_UIs_or_users

Yes, here: https://gitlab.com/groups/postmarketOS/-/milestones/25

Haven’t seen that error yet, but I’d suggest trying other Alpine mirrors (set them in your /etc/apk/repositories): https://mirrors.alpinelinux.org/

(there’s also “apk fix” which helps when installing a package failed earlier for whatever reason, but that doesn’t seem to be the cause here)

The bug gets tracked in https://gitlab.com/postmarketOS/pmaports/-/issues/2299, and a fix is being developed. Workarounds are mentioned in that issue. The download page has been updated to mention this and link to the issue in the meantime.

Is Alpine also becoming immutable, or is this development towards immutable independent/separate from Alpine?

It’s a separate effort. 🙂

From the features table, looks like it barely boots up with the downstream kernel and can use the display. Check it out if you are curious and want to extend the port, or if you can come up with your own use case.

If you want the encrypted install on the eMMC, copy over the installation from the SD card (or image file if you don’t use --sdcard) to the eMMC. Good luck!

Yes, through ondev2: https://fosdem.org/2023/schedule/event/ondev2_installer/ Still WIP at this point, but until then you should be able to make your own encrypted image with pmbootstrap install --fde --sdcard=… - see https://wiki.postmarketos.org/wiki/Pmbootstrap#SD_card

Sounds like not postmarketOS specific packages, but rather ones that would go into Alpine. You could make a packaging request here, and maybe someone wants to package it and maintain it for you if you are lucky: https://gitlab.alpinelinux.org/alpine/aports/-/issues/

Or you could try to build it yourself (and if you are willing to maintain it, then get that package into Alpine). Building Alpine packages is relatively easy: https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package

While I have not personally used any of them, I guess as long as they support standard wireguard or openvpn, they should work fine.

This looks really interesting, thanks for sharing!

good question, thanks puts in queue for podcast questions

Hi all,

postmarketOS does use deep sleep for the PinePhone for quite some time.

However on edge, this is currently broken: https://postmarketos.org/edge/2022/04/06/pinephone-suspend/

I suggest to use postmarketOS stable instead, or wait a bit until we’ve figured this out on edge. See the issue linked in that edge post for more information.

Thanks for the nice comment, I’m happy that you enjoy the podcast! We’ll probably answer that on the podcast then, and thanks for the guest suggestion!

See the list of devices and their status here: https://wiki.postmarketos.org/wiki/Devices

The Jolla Phone has a port: https://wiki.postmarketos.org/wiki/Jolla_Phone_(jolla-sbj)

The Aqua Fish doesn’t have a port yet, so you’d need to create one (more work of course, but you can learn a lot about how things work if you are curious): https://wiki.postmarketos.org/wiki/Porting_to_a_new_device

You can use either as playground for postmarketOS. But you won’t be able to use it as daily driver or in general have many features working compared to the devices in the “main” or “community” categories.

Note that it’s only recommended to get the pinephone pro at this point if you want to develop for it, it doesn’t yet have as much working as the original pinephone.

In general, if you’re a Linux enthusiast who likes to tinker around with this, go ahead! If you are looking for something that you can replace your Android/iPhone with without any effort, then this is not for you yet.

Thanks!

Yep, /etc/deviceinfo exists for all devices in postmarketOS. So if you want to do a quick hack, you can simply source the file in a shell script and add logic based on the codename defined there.

If you want a distro-agnostic solution, use the device-tree string, e.g.:

$ cat /proc/device-tree/compatible
pine64,pinephone-1.2pine64,pinephoneallwinner,sun50i-a64

This is what we use in megapixels for example.

Sorry to hear that.

Maybe that’s the problem? From pinephone faq:

In order to use the modem and Wi-Fi/Bluetooth, you need to ensure the battery is inside the device and has a sufficient charge. Even when supplying the phone with enough power, the modem and Wi-Fi chip will not work without a connected battery. Further, double check that you have not put the SD card into the sim card slot, or vice versa.

If that’s not the problem, please create an issue here and fill out all information of the template: https://gitlab.com/postmarketOS/pmaports/-/issues

FWIW, I run pmOS edge on the pinephone with latest updates and calls work for me.

You might be able to use the online versions of these services (in a browser). I don’t use google apps so I’m just guessing.

(Now that answers which phone you are running ;) )

Issues should not be reported here in lemmy, but instead on gitlab / or in case of megapixels in the megapixels project.

• https://wiki.postmarketos.org/wiki/How_to_report_issues
• https://todo.sr.ht/~martijnbraam/Megapixels

With that being said, you don’t need to open an issue for this one. megapixels doesn’t run on anything but the pinephone and pinetab right now (but that is changing, e.g. the Purism folks have forked it to run on the Librem 5 and will probably upstream their patches at some point). There were also efforts to get them running on Samsung devices. If you really want to dig into it and are not afraid of hacking on the code, I suggest taking a look at the code. Otherwise you’ll need to wait until somebody makes it work with your device.