Hello there,
I am offering my Pine64 Pinephone Pro in the Explorer Edition (hardly used and in great condition) for sale,
Unfortunately, I didn't find the time to deal with it more intensively.

The Pinephone Pro is in very good condition and will be shipped with the original packaging.
Included are the original data cable and an unused screen protector.

Purchased from the pine64.com store in November 2022
The new Ubuntu Touch Focal/20.04 is currently installed.

I ship the Pinephone Pro from Germany only to the EU area.

At that time I paid the $399 as well as the shipping of $35 and the import costs of about 92€.
In total about 500€.
The PinePhone Pro currently costs 592.50€ in the PinePhone64eu shop and is currently out of stock!

I'm now offering the Pinephone Pro for 390€ in great condition and without any further import costs.
Only the shipping costs come on top.
A great opportunity to get in cheaply and without waiting!

If you are interested:

https://www.ebay.de/itm/195944099956?mke...name=12000

Hi there,

I've made a BLE-MIDI-controller app for PineTime, which can send MIDI-data over BLE to music synthesizers:
https://codeberg.org/Luno/InfiniTime_ble-midi

Hello,

The default sxmo setup on postmarketOS doesn't make any use of the notification LED. I'd like the LED to stay on when there are unread SMS and/or missed calls, how can I enable this? The sxmo port to Arch Linux does provide such notifications, so it shouldn't be much of a big deal, I guess.

Now that I've rebuild all the broken nut insert mounts in my case with JB Weld epoxy, thus securing the display hinges and bottom cover again, I have several keys that appear to be almost dead. In the beginning of the problem, these half-dozen or so faulty keys were intermittently functional so somewhat usable with "re-tries" but they are no longer usable. (Very occasionally one of them might function for a single stroke.)

I've tried re-seating the ribbon cable into the mainboard connector to no avail. I very much doubt this failure is related to my repair job. Does anyone have experience with keys going dead?

What is the likelihood that replacing the keyboard with a new one from Pine64 will fix the problem? I fear the fault lies in the mainboard, in which case a repair would not be economical.

This must be my year for laptop keyboard failures. My 6 or 7 year-old HP laptop has the same problem but retries still work on it. In owning and using many laptop computers since they were invented, this is the first time I've had this failure!

Cheers,

Cal

Greetings! I'm looking for a bit of advice.

After numerous attempts, I am unable to get my Star64 board to boot.  I'm attempting to run Armbian, including the build by balbes150 (https://forum.pine64.org/showthread.php?tid=18344) and the build on the Armbian website.

I've read about setting the Component S1804 switches to boot from SD card, which I've tried. I also wrote an image to an eMMC module and tried booting from that (changing the S1804 switches accordingly). 

I have a 3amp power supply purchased from Pine.

I'm using the serial console on pins 6, 8 and 10.  The only message I ever see is this:

The pinetab2 is a bit of a unique device. It is a tablet sized device, however it also comes with a keyboard and trackpad and a full linux install. This places it as something that isn't quite a regular desktop and isn't quite a mobile experience.

Because of its novelty I want to start a discussion on which desktop environment do users prefer so far, between plasma/KDE, plasma mobile, PHOSH*, LXDE, or any others. I would appreciate hearing what DE you used and any comments you may have.


For me the default is always KDE as I have used it since 3.0, although for the pinetab2, it felt somewhat sluggish and not very well adapted to using both tablet and keyboard features. While in theory touchscreen gestures from the screen edges and the automatic keyboard popup is fantastic, depending on what is open the touchscreen gestures don't always work or have a decent delay to them.

Currently trying PHOSH and find it much more responsive, touchscreen gestures are quick and work consistently. However the downsides are the display of all applications is already too big. A desktop install will simply have many more applications than most mobile devices, in practice starting applications using alt-f2 is just more practical.

I have not used an external monitor for the pinetab2, I imagine that would again change the consideration of DE.

* a working trial of phosh may be installed from the default danctnix repositories as simply as

Have dragged the PinePhone out of the cupboard to give it another try.
Have tried to install the Latest version of PostMarket OS to both EMMC and the SSD card.

The install was very easy but upon boot I get
can't create directory '/home/user/local/' :read only file system

then a string similar errors around cannot create files due to read only file system.

Would seem Postmarket Os has installed with a Read only filesystem.

Any ideas how to fix this?

thanks

Just signed up for T-Mobile home internet in US. It is basically a permanent hotspot on their network. Setup other devices (MacBook, iPhone, Motorola) without issues just connecting to new Wifi network with credentials. Tried to do it on my Pinebook Pro running default, udpated, Manjaro OS but it can't get a connection. Switched back to old network and connected right away. Just curious if anyone has had a similar issue, haven't had a chance to go through all the troubleshooting steps yet.

Pinephone screen stopped working. The system starts but the screen is black. When starting the jumpdrive, the screen is bright gray, but after an hour of charging, nothing has changed. The battery voltage is 3.76 volts. I have tried different operating systems and chargers. The last time it worked, I turned it off by holding the power button and put it on the table.

Hello all! 

I have installed the stable version of Mobian on my new PinePhone Pro. (mobian-pinephonepro-phosh-12.0.img.gz)

Now I noticed that the Camera app is very slow. In the Softwares About I found "0.1.0-net.flyingpimonster.Camera". Is it possible that the camera app is not up to date? The project Camera stoped in 219 and called now Snapshot, right?

Have you an Idea to solve the problem? Do you use maybe another app for shooting images?

Cheers - Martin