In your January update you wrote that there will be another batch of the pencil in early February. Have I missed that already?

Hello fellow Pine-pals,

I have a PBP which I've installed Arch on and over all it works great. One annoyance has been that if I shut the lid it'll go to sleep but when I open the lid it doesn't wake up. I've tried pressing keys, tapping the power button, disconnecting and reconnecting the power...  nothing. I haven't tried accessing the serial console but that might be my next step.

Since it sleeps OK I'm thinking this isn't the magnet issue but something else.

Has anyone seen this issue before? I can't recall if it happened with Manjaro or not.

Thanks,

Duck of Death

Hi all!

I have encountered what I suspect might be a severe bug regarding the encrypted installer from (?) 15 Dec:

I installed this from an sdcard no worries, to try it out. worked fine.
Then using jumpdrive I installed it to 2 pinephones, first and second ce versions, 2Gig and 3Gig. Also worked fine on both.

Now the problems start:

To have an experimental system to tryout updates before committing myself to changing my installed system, I made a fresh install of the encrypted installer onto an sdcard, and booted from it, and let it go through it's standard setup process, choosing to enable encryption in the process. I thought this would leave the installed system on the phone alone.

The setup process did not quite complete, it displayed the progress bar for a few minutes, getting to about 93%, then I suppose it tryed to reboot or something, but ended up with a blank, faintly lit screen, which did not progress any further.

When I removed the sdcard, and tryed to boot the phone from the internal storage, it did not succeed, and displayed the message: "cryptsetup waiting for encrypted source device UUID: then a bunch of characters followed this"

I created another encrypted installer image on an sdcard, and tryed it on my other pinephone, and the same thing happened, it did not succeed in the installation on the sdcard, and after that the existing encrypted installation on the internal storage would not boot.

I then tryed reflashing the encrypted installer onto one of the phones using jumpdrive, and going throught the setup process again from the internal storage, choosing to enable encryption, and this worked well.

-I wonder it the encrypted intaller is becoming confused at some point, in cases where it is installing to an sdcard, but where there is already a copy of the encrypted system on the internal storage of the phone? -Could it be looking for a particular storage type/name/uuid and finding the one on internal storage first, and overwriting it or something?

Great system regardless, and I am very grateful that it exists!

All the best, hope this is helpful feedback?

I've spent a couple of days building a library for the pinephone.

Its early in development, some things are still a bit wonky but all in all it works and I've written two services that run on my pinephone.
There's a nuget package available, however its not up to date, I recommend cloning the repo and adding a Project Reference if you want to use it.

The only things missing is the Vibrator and the Modem. All other Sensors are wrapped. 

If you don't use the WiFi classes, there's zero dependencies, all of it works using the kernel filesystem and input events - if you do use the WiFi classes, there's multiple implementations for most methods, NMCLI, IFCONIG, IWCONFIG,... more about that in the Readme on the repo. 

Getting .net5 setup on the pp is easy, the repo  contains a wiki with a install instructions

https://github.com/Alumniminium/PinePhoneCore

I'm trying to attract other .net/C# developers to contribute / work together, feel free to reply here, message me privately or talk to me on Matrix

The feet on my PBP are barely holding on. It looks like this is a common problem, so I'm asking for advice of others who are . . . footloose .

What glue works well for reattaching loose feet?

Hello
Anbox currently doesnt work with wayland backend right now due to a pbuffers issue: https://github.com/anbox/anbox/issues/1270
This is why it looks so fuzzy on pinephone, because its using xwayland witch its not ideal and makes it slower.

There is a bounty source for making Anbox work on Wayland. Currently its at 180$ if someone is interesting on contributing to the bounty or making the work and reclaiming the price its here:

[color=var(--tertiary)]https://www.bountysource.com/issues/95432153-implement-native-wayland-support-for-anbox[/color]

This one.

This was merged upstream I guess (not up on the terminology here, so bear with me). I decided to set up the sxmo build environment so I can tweak some things, so I ran the build script which installs all the latest versions of the little scripts and all that.

Today I get a call, and it starts executing my ring hook, except it's doing it over and over and over, overlapping. I go to pick up the call and it's still ringing (x100 overlapping) and also somehow hangs up when I pick it up, while still ringing. All hell is breaking loose.

So I'm testing out what broke tonight, and I disabled my ring and pickup hooks just to be sure. Sure enough, I get a call in, go to pick up, and it just hangs up immediately. There was no option to discard, so I'm guessing that the pickup and discard functions are happening simultaneously when selecting to pick up. 

For now I've commented out these lines in sxmo_modemmonitor.sh in the checkforincomingcalls section:

The Pine64 website gives conflicting claims about the availability of its products.

On the home page, it gives the option to pre-order Pinebook Pro. But pressing this leads to a product page which gives no option to preorder, which says that the product is out of stock, and gives no indication of when or if it will be back in stock.

So I guess, shortly phrased, my question is "When will Pinebook Pro be available to purchase?"

Hi folks!
You might think your pinephone is a slow POC device.
Welp! that's true BUT pmOS sxmo is an incredibly smooth OS!
You can check my review here: https://youtu.be/Q6L9K0EW3qg

*How to install?*

# 1. Easy way --

## 1.1 From the computer
Download https://lucasanss.xyz/pine64-pinephone.img
then burn the image to you sdcard*. 
On a linux desktop the fastest way to do so is to download
the image while uncompressing it while writting the decompressed
output on your device.
if your sdcard is `/dev/mmcblk0` run: 
`curl https://lucasanss.xyz/pine64-pinephone.img.zst | zstdcat > /dev/mmcblk0`
if you want to check the writting progress:
`curl https://lucasanss.xyz/pine64-pinephone.img.zst | zstdcat | dd of=/dev/mmcblk0 status=progress`
Then boot 

## 1.2 From your phone

- Boot from your internal storage, /!\ -- important!
- Open up a terminal, run**:
  `sudo su`
  `curl https://lucasanss.xyz/pine64-pinephone.img > /dev/mmcblk0`
  /dev/mmcblk0 is the default partition for your external sdcard.

## 1.1 credentials
Default login : pine
Default password: enip

# 2. The hard way
Read the wiki https://wiki.postmarketos.org/wiki/PINE6...pinephone)
Follow the `pmbootstrap` instructions.

# 3. Important notes
READ the user instructions: https://git.sr.ht/~mil/sxmo-docs/tree/ma...ERGUIDE.md
Sxmo is easy to use but there is a certain learning curve.
For example by default the modem is disabled. While you'll
be able to make phone calls and receive sms, you'll can't 
receive any. So you'll need to enable it via the menu.

---
* If you use windows, I'd suggest using `rufus` in dd mode, or etcher.
Nonetheless, I haven't tested burning the image on windows

** Make sure curl is installed and that you have a reliable internet.
If download fails restart. Otherwise download the image and flash it
with `wget` and `dd`:
`wget https://lucasanss.xyz/pine64-pinephone.img`
if download succedeed:
`sudo dd < pine64-pinephone.img > /dev/mmcblk0`
yes you can use “<” and “>” instead of “if=” and “of=”

Hi all,

  I made a test on nvme ssd performance.
 
- 2 rockpro 64
    - one with Armbian (tried 5.9.14 and 5.10 rc7)
    - one with Ayufan’s kernel (5.9.)
- 2 pcie to nvme cards
    - a black one from Pine64 (gen2)
    - a red one  (perhaps gen3)
- 2 ssd samsung evo plus

The result :