I received my pinephone a couple of days ago.
After having carefully unpacked the item, I wanted to check the factory tests, but the phone boot stubbornly on Android 7.0 and only on chinese language.
Further more, it is impossible so far to boot from a SD card with pine64-pinephone.img or ubuntu-touch-pinephoe.img ...
If somebody can tell me how to get rid of android 7.0, i would be extremely grateful.

I've set up a new Debian install with the Thompson installer and successfully got Cinnamon to run with it, but noticed that audio isn't working.

What might be missing in order to get audio to work?

Hi,
I am using Manjaro KDE on my pinebook with an external monitor HP ZR24w which has a resolution of 1920x1200 but unfortunately it only runs at 1920x1080.

Manjaro correctly prints the max resolution of monitor to 1920x1200 but if i select it the monitor turns black saying "Input Signal out of range". I am using this adapter: https://www.amazon.com/uni-Thunderbolt-C...601&sr=8-1 (USB-C to HDMI)

Maybe somebody has already tested the Pinebook Pro with an external display with 1920x1200 and has a good reccommendation for an adapter (preferably USB-C to Display Port)

Regards

Has anyone been using their PineBook Pro without PulseAudio or in some otherwise minimalist config and playing audio or videos with sound?

Have any interesting findings or discoveries to share?

I've got a minimalist-ish Debian install on mine with no PulseAudio (and no desktop-environment, just a window manager).  I've managed to get sound working through headphones, but I've run into problems getting the builtin speakers to work that I haven't fully investigated yet.

When I run alsamixer or alsamixergui, I get an overwhelming display with over 30 different controls, some of which have level sliders and some of which seem to be on/off only.  Most of them are somewhat cryptically labelled (at least for a
non-audio-geek like myself)  I've found two different controls that (usefully) affect the volume of the headphones, but the one that is labelled "Speaker" is just an on/off control.

I wonder if I should expect/assume that this will get better in future versions of the kernel or the device-tree.

Hi everyone,

First time posting on this forum and completely new to single-board computing.

I have a lot of time on my hands due to college and work being cancelled due to COVID-19, so I ordered myself a PINE A64+ 2GB and it should arrive soon. Very excited to start messing around with it.

My intentions for this board are

>Initially use it as a chip flasher to flash coreboot onto the BIOS chip of my Thinkpad. All of the tutorials I have seen call for a Raspberry Pi but I don't see why the PINE64 shouldn't be able to do the job. Maybe I will write a tutorial if it goes well!

>I live in a collective house. I would like to turn this device into an internet-connected Nextcloud server that I could give an account to each of my housemates if they want it.

>I will also like to set up an instance of Mastodon for the users in the house.

I do wonder if I'm asking too much of this board, for it to be a Nextcloud server and Mastodon server at the same time? What do you think?

I'll let everyone know how I get on.

Hello there!

I am new to single board computers,
I am wondering how to setup the Pine64

I have flashed Windows IoT to a 32gb class 10 microSD card, and I have attached the HDMI, Power Cable, and a mouse and keyboard
I have searched but nothing of the sort shows up 

Any help?

Hello,
  I would like to use UART on ROCKPro64 for bi-directional communication with Arduino Pro Mini.
According to documentation, UART4 TX, RX are connected to Pi-2 connector pins 19 and 21.
But there is no relevant device file - /dev/ttyS4. I can see only /dev/ttyS0 and /dev/ttyS2. I do not want to use these two, because they are already intended for Bluetooth and console.
How could I enable /dev/ttyS4 in my Linux system?
I am using rockpro64-debian-desktop-mrfixit-191226. ‘uname -a’ shows:
Linux Debian-Desktop 4.4.207 #1 SMP Fri Dec 27 11:35:59 EST 2019 aarch64 GNU/Linux  
Thanks in advance!

Not sure if I should post here or in general,  I bought the braveheart edition understanding full well the implications of what it meant,  I have been trying for almost 2 months to see if it was a software stack issue but alas I think I just got a phone which has a design flaw and am curious if anyone else has had the issue or knows a solution.  I can boot various distros installed on sd or emmc I've rebuilt software from scratch(with an arch linux on arm build I'm currently running)  I haven't messed with u-boot too much as I don't know it very well and don't want to brick the device(not sure if that's possible anyway).  But my screen's graphics no matter what system, even from day 1 with the testing system on it, just keep stuttering up and down, the touch screen works, but it really makes this device more or less a pineboard since I could never use that as a daily phone.  So is this a common issue that other users have come across and know how to fix?  I see they just added you can order parts(when they are in stock)so would anyone know which part needs replacing?  Is it something I can fix myself?  Or is the phone just bunked and I have to buy another when the next generation is released?  Also if it is a software issue with configuration I am up for trying anything cause I want it to work but I'm starting to accept this might be a lemon.  Any help or confirmation of my conclusion would be appreciated.

tricky getting past the install stage, screen goes dark ,and off ,several presses of the on/off will sometimes bring it back, risky setting a lock code ,screen changes before you get the code entered.
 but the general operation ,is very smooth ,and i would say improved a lot.
i did not put a sim in it.
if not for the screen blacking out and jumpy unlock screen , looks almost like a daily driver, (assuming the modem/phone works)
.
anyone else try it.?

< tried two downloads, the second seemed a little better, but still had something going on >

Games can be launched from command line but emulationstation crashes on load (x connection broken error) and the virtual keyboard map is pretty random. Anyway, here's a blurrycam video showing it in action.


  quake3a.jpg (Size: 183.37 KB / Downloads: 817)