I have downloaded the TwisterOS image located here: Pinebook Pro Software Release - PINE64 and flashed it to a microSD on using DD under the included Manjaro Plasma installation. I followed the instructions and changed the armbianEnv.txt file to point at the rk3399-pinebook-pro.dtb file. I shutdown the computer and restarted with the card inserted (in the external microSD slot) and the machine will not post. The green power indicator slowly turns off and on in a continuous loop suggesting the machine is restarting after failing to boot.

Is this image not compatible with the latest release of the pinebook pro? Is there another version of the image I can/should use in its place? If this is all a moot point is there a similar flavor of linux to TwisterOS which includes wine and other arm specific versions of x86 emulation software?

Hello,

maybe it is time to create a forum section for the new rk3588 board, or do we share the quartz64 space ?

Hi,

I have a recent Pinebook Pro from September 2022 (motherboard bears a 2022/07 QC sticker)

It has an NVME (low power WD) SSD for /home and data only, and Manjaro Linux KDE runs from the eMMC, with latest updates applied.

When running from mains power, the system is perfectly stable. But the power cable is so short !

OTOH when running on battery, even fully charged, it happens very often (twice attempting to write this post) that the system completely freezes with the power LED blinking red/green.

At this point I can only perform a hardware poweroff.

Any clue ?

Kind regards.

In the last two weeks, since I played with Mobian for a while and a few others and eventually settled on Manjaro Phosh, things began working more or less fine, except two weird things (and more came as I was writing).
- if I don't close all apps, the phone may need to be rebooted. Doesn't happen every time, but does often.
- when I boot it, it sometimes takes two or three reboots until it shows the desktop
- today when I tried to call someone, it reported that she was calling me (three tries, did so each time); worked around it by sending a SMS and then she called me, which went fine. On next boot, called someone else, that went fine
- just now someone called me, and during the call the screen went black (as I assume should be normal), but then when I turned it on and tried to enter the passcode, after three digits the digit buttons just flowed away to the right, as did the indicators on top, leaving me with just the background picture with nothing on it. On next suspend/resume it shows the top row controls, and they work, but the passcode digits and the bottom arrow to show them didn't appear.
- one reboot later it's back to normal.

Hi folks,
Has anyone set up a printer in Postmarket os Plasma? I installed printers config and cups and I can't seem to get Pinephone to see the printer.

Hey all

I'm new to the pine world, have used other sbc's multiple times. I've got the quartz64 model A, installed a 32Gb emmc module and using a power adaptor from the pine store (https://pine64.com/product/12v-5a-us-power-supply/). When I plug in the power supply I get the green DC light, I've followed the instructions from this link: https://wiki.pine64.org/wiki/Installing_...e_Quartz64

I have a 16Gb SD card in my laptop, run this command (SD card is mounted as sda): 

I'm trying to find simple instructions for how to compile and implement fbkeyboard so it's running at TTY when it asks for login/password on PostmarketOS.

Repo: https://github.com/julianwi/fbkeyboard
Example of it running at tty login on a Pinephone: https://youtu.be/npKwMWr1F_0?t=1099

I've searched around a while but can't seem to find much. The repo's readme is somewhat helpful but i'm not used to Alpine's musl compiler or how to auto-start a program so it's runs at the TTY prompt.

Much thanks for any suggestions and if I find the answer i'll post it here.

Like the title says, I did an apt dist-upgrade and now I can install gnome-contacts and loose chatty(SMS and some IM) or install chatty and loose installed gnome-contacts.  No matter what gnome-contacts is broken or gone so I choose installing a working chatty and use the phone app for contacts short term.
More of an FYI as I expect it to be fixed in a few days unless anyone has a slick fix.

I have successfully installed Arch Linux on my Pinebook Pro using the following wiki article:

https://wiki.pine64.org/wiki/Installing_...nebook_Pro

However, I had to use the Pinephone dock to enable networking because the wifi adapter does not work out of the box.

dmesh output shows:

brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.pine64,pinebook-pro.bin failed with error -2
brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.bin failed with error -2


I tried some suggestions from the friendly people on the Pine64 Telegram channel but until now I cannot get it to work.

Here is what I tried:

https://forums.raspberrypi.com/viewtopic...7&t=291688

This is a thread on the Raspberry Pi 4 which seemingly uses the same hardware? I tried copying the suggested file but that did not solve the problem. Note that the file was not there in the first place so renaming failed.

Copied the files found here:

https://gitlab.manjaro.org/manjaro-arm/p...6-firmware

Also this did not solve the problem.

Another suggestion is to see whether the alarm repos have a firmware package for this but I'm a bit at a loss as to how to do this.

A usb wifi dongle works without any problem so I have a workaround but I would be happy if the on board wifi would work.

Any help/pointers are appreciated.

I know that some people have it working so it is just me not having found the solution yet.

Back in the N900 days we had an app which used rendezvous auto discovery IM protocol to bridge the phone's SMS to LAN instant messenger.
While HeySMS could probably be ported or cloned with recent libs https://talk.maemo.org/showthread.php?t=84705 I think that there is probably a quick ready to get a basic SMS send.

Is there an easy way to send a command line trigger or AT command followed by the text to at least write a SMS and then send it over SSH.