One of the things Solaris & AIX have for safe patching & upgrades, are alternate boot environments. AIX solves this by having an OS boot mirror device that can be detached and made bootable as a backout plan. Solaris 11 does this through a mostly automated procedure with ZFS snapshots & file system clones, using the "beadm" command. The intent is to allow easier restoration of service without having to perform a full restore. (Either from backups, if you have them. Or re-install.) Simply reboot to the previous OS image.

At home, with Linux, I've done 3 different methods for backing out changes & updates. First method applies here, using a second OS partition for the backout plan. This is what I will describe for the Pinebook Pro, with Manjaro on eMMC. This can work for other Linux distros, but I will not be describing them at present.

It's a bit more clumsy on the Pinebook Pro right now, as we can't use Grub menus to select the prior OS in case of complete failure. If the default OS is completely un-bootable, then you have to boot and use a SD card to perform the change back.

To start, you need to re-partition your eMMC to something like below. If this is beyond your skill set, then it's likely the rest would be too.

part 1 - /boot
part 2 - / (root 1, about 15GB)
part 3 - / (root 2, same size as root 1)
part 4 - /comm (common for rest of the space)

What you call the "/comm" is up to you. I normally use the host name. Basically you should put your home directory, and other things that should be common for both OS images in a separate partition.

I will assume you have the root file system on partition 2 booting fine under Manjaro.

Manjaro uses the file system label in the U-Boot configuration file. So, we use a different file system label for the second root OS. Here we make a second file system, with different label, mount it and copy it.

I had recently seen the video by megi tweeted by pine64 of the pinephone displaying on a monitor, but there was no mention of the phone having a hardware mod.
https://twitter.com/thepine64/status/127...7726109696

Later I discovered on the wiki page that there was a hardware quirk that was discovered after the production of the CE version.
https://wiki.pine64.org/index.php?title=PinePhone_v1.2

A workaround is to desolder to switches.
https://wiki.pine64.org/index.php?title=...ONN_is_off
https://xnux.eu/devices/pine64-pinephone.html

But apparently this causes another issue when using a USB-C hub: "SD card reader not enumerating on PP with removed VCONN switches"
https://wiki.pine64.org/index.php/PinePh...patibility

So I have a couple of questions. I ordered my pinephone on may 21 with DHL shipping. I have not yet received DHL notification e-mail.
Do the shipped pinephones all have this hardware quirk?
Should I cancel my order and wait for a new pinephone revision?
Will there even be another revision?

I would really like to know, because I was really looking forward to this feature and cannot afford to buy more than one pinephone.

I've discovered quite a few ways that don't work...

Starting with the 0.10.12 ayufan arm64 builds, things work sanely, with the exception of deep sleep and sound.

Using the pbp-tools repo (thanks, those scripts are awesome!), I was able to build an updated 5.7 mainline kernel from the Manjaro git repos, which gives support for just about everything.  The postinstall script fixes sound, not that I really care too much about sound these days.

What I can't quite figure out the details for is the deep sleep mode.  It's not critical - I can live without it, but I'd like to have it working if possible, because that's the last step before it's "totally working."  The s2idle sleep mode works fine, but the deep mode doesn't.

I understand this is related to a lack of the binary bsp blobs in the bootloader regions, which on these images seems to be a 4MB partition starting at the standard 32kb offset.  I just don't quite understand where to find the BSP blobs, or how to arrange them in this 4MB region.

Is this documented anywhere?  I've found plenty of references to what to do, but not any specific steps of "You grab these blobs, arrange them this way, and it solves the problem."

Hello every one.

I would like to take a screenshot of my Pinephone UB port Edition (UBports 20200608-18105) from my cumputer (Kubuntu 18.04).

Is someone know how to do it?

With my android devices, I can do this with "Monitor" wich is included in Android Studio.

Anyway, thank you for reading, and have a nice day.

Let me know if anyone is willing to sell their pinephone the UBports edition is preferred. I will only send money through PayPal.

Found one

Hi everyone, I was really excited to get my pinephone and am now playing around with it.  I popped my sim in but can't get it to make calls on Verizon.  Has anyone been able to figure this out?  I contacted Verizon and was told that the phone is not support because it is not on their list of non-verizon phones.

I'm looking for a booklet type case for my new PinePhone. I'm currently using the hard case and a glass screen protector, but especially the latter I quite dislike. I prefer to click my phone into a leather case and have a flap protect the screen when it's in my pocket.



Does anyone have experience with an existing case for an existing phone in which the PinePhone can be made to fit?

Things got a bit messed up when I switched to dev 46, so I'd like to start again.

Has anyone flashed an Ubuntu Touch image to the internal eMMC?  Would you mind detailing how you did that please?  I'll just stick to stable on there for now, and save the experimenting for SD cards!

Thanks.

Hi,

I noticed that since #45 or #46, the phone would stop charging when full and then slowly go down. If I remember correctly, it started to charge again from about 90%.

Since #47, it does not start to charge again. The result is that the battery would go down to 0%, even when the phone is connected to the charger.

Is this behaviour related to crust?

I get this message on the shopping cart page: 

"Sorry, we do not have enough "PINETAB - 10.1" Linux tablet with detached backlit keyboard" in stock to fulfill your order right now. Please try again in 4320 minutes or edit your cart and try again. We apologise for any inconvenience caused."

The standalone tab is listed as out of stock on the store page.

Asking if this is a glitch because I think I remember something similar happening during the BH pinephone preorders