In case anyone is still using their original Pinebook - I pulled mine out of storage couple days ago and installed Debian Sid on it. Everything is working fine so far, except Bluetooth, sound, and deep sleep. The only special thing I had to do is build kernel module separately for WiFi.

I used https://d-i.debian.org/daily-images/arm6...rd-images/ to create a Debian installer SD card. Generally installer worked, but letting it do it's own thing hands-off resulted in a system that's not bootable without an SD card. To make it bootable 16MiB free space is required in the beginning of the eMMC (I didn't try using SPI flash). So I partitioned eMMC manually, creating a single ext4 partition that starts at 16MiB mark and takes all of eMMC - I didn't want the hassle with any special partitioning. After that I went through the installation, and in the end installed u-boot-sunxi and ran `u-boot-install-sunxi64 /dev/mmcblk0` (make sure you got the right device number) to install u-boot. One thing to note though is I used u-boot-sunxi from experimental - it seems the version in Unstable is not yet able to boot from ext4 partitions. After that the system boots fine on its own, but doesn't have any WiFi. To get WiFi working I cloned https://github.com/Icenowy/rtl8723cs, installed basic build dependencies (build-essential, linux-headers-arm64), cd to the folder, `make && sudo make install && sudo modprobe 8723cs`. After that I installed the rest of the packages and got a full working system. For KDE Plasma QML not to glitch all the time I had to set QT_XCB_FORCE_SOFTWARE_OPENGL to 1 (I added `QT_XCB_FORCE_SOFTWARE_OPENGL=1` line to /etc/environment).

I am a new user in Linux and a new owner of a pinebook pro from Russia . How to fix booting after incorrect installation of Manjaro?

I received my Dock today, but it seems that it doesn't function properly, none of the ports are working including the VGA and HDMI. When I plug the dock into the laptop's type c port, I get a loud coil whine. This also happens if I plug power into the dock's power port. Has anybody else experienced similar issues? your help would be greatly appreciated. 
Thanks

Hello,

I have read in various forums / Twitter that Jolla and Pine64 have entered into a cooperation or that devices have been shipped.
Is there any news if the Pinephone will be a supported device at Jolla? Or will it remain a community device.

Surprisingly, the Pinephone runs very smoothly with Sailfish OS 4.
Apart from the well-known modem problem that affects all OSes, the rest runs stably.

Thanks to the community for their hard work.


A statement from Pine64 would be great here.

with friendly greetings
Steffen

I have a beta edition pinephone, using Manjaro Plasma. I am experimenting with a Nexdock, and getting poor results.

When I turned on the phone and plugged it in, they did connect, and the display was sort of shown on the Nexdock.  I got strange effects, though: sometimes the two displays seem to overlap, sometimes the phone display was shown at phone size in the upper left corner of the Nexdock, occasionally other strange stuff. 

I went into the settings and messed with them a bit. It showed the Nexdock display, and showed the phone (called it laptop, but the sizes made it obvious which was which).  After a bit the phone display went black, and the Nexdock display began to blink furiously if I moved the mouse pointer.  The earlier strangeness was intermittent, and now this is continuous.  The only way I can get out of the jam is to unplug and reboot the phone.  If I plug it back in and turn on the Nexdock, I'm back to black screen on the phone and blinky on the Nexdock.

If anyone has made this combo work, I'd appreciate some pointers.

When I receive and answer a call, the audio switches to the earpiece. When I hangup the call, the audio won't switch back to speaker. I can't even switch it back using the settings. The only solution is to restart the phone.

Is this a known issue? If not, where would I even report it?

Hi

sorry, just copied and modified the thread title.

How can I tell what the hardware version/revision of a rock64 is?

Running Linux. The Wiki has nothing, /proc has nothing, and even dmesg has nothing whatsoever.

Maybe if any hardware differences were known, the dmesg output could point to what hardware version/revision it is.

v1 vs v2 vs v3, or rev2, or rev3?

thanks

I booted up my beta edition pinephone this morning, and everything on screen is half the size it was yesterday. Icons are tiny, text is tiny, everything is hard to see.  

I restarted it, this time without having the docking bar plugged in, and everything was back to normal size.  It looks like booting with the docking bar plugged in is what caused that?  

Does anyone know what happened, and how to do/undo that without rebooting? I looked in the settings, but can't yet find anything that applies.

Hello,

So i've dusted of my old pinetime dev kit. Beforte the infinitime 0.7 firmware. Just the closed source firmware.

Here is my plan. Will it work or will it brick?

-> Flash new bootloader with BLE with the DaFlasher App
Like described on the WaspOS tutorial*:
1) flash 'hacked'
2) flash 'dafit..'
3) and then?

The documantation says flash 'bootloader-daflasher.zip'. But i can't find that file anywhere.
I think that, finishing stages 1 and 2 will give me a 'unlocked' pinetime. And i can flash the waspos 4.1 firmware. 
? Is this correct?

Or can i then follow the infinitime instructions**
1) flash inifitime 1.x
2) flash bootloader
3) flash recovery

I expect that i have to flash a wasp/infinitime bootloader first. That 'bootloader-daflasher' that seems missing..

Help appreciated!

*Installation Guide — WASP-OS documentation
**InfiniTime/gettingStarted-1.0.md at 1.2.0 · JF002/InfiniTime · GitHub

Just installed the edge build here - edge/pine64-pinephone/phosh/20210630-0055 - postmarketOS // Official Images - and I can't find out what the default pin is!

Why release this and give nobody the default pin!? And don't tell me it's in there because I've already tried it!