I would love to see an all-clear pine phone like those cool N64 and gameboys

Greetings from FydeOS!

We have now released the first FydeOS for You - Pinebook Pro v11.2. Inspired by the previous Chromium OS build produced by Ayufan-rock64, this has been 2 months of hard work from our dev team. Build artefacts can be found here, download links as below:

https://download.fydeos.io/FydeOS_Pinebo...1.2.img.xz
https://fydeos.cowtransfer.com/s/ee11aa4238f745

Please read the full release note and install instruction here.

For technical support, please use FydeOS Community and our Telegram Group.

Enjoy!

Hi,
I've almost finished a port of OpenMandriva to the Pinebook Pro -- the last remaining big issue: I can't get the SD card to boot by itself. It works fine if I use the UART cable to stop autoboot and run uboot commands to boot it manually.

I built u-boot from the megous repository, using the pinebook-pro-rk3399_defconfig configuration. Then I do
dd if=u-boot/idbloader.img of=/dev/sdb seek=64 conv=notrunc
dd if=u-boot/u-boot.itb of=/dev/sdb seek=16384 conv=notrunc

I have an ext4 partition starting at sector 32768 containing the files documented at http://opensource.rock-chips.com/wiki_Boot_option

But the bootloader simply doesn't seem to see the SD card as a bootable device, it boots Manjaro as usual when the SD card is inserted (unless I intervene manually over the UART).

What am I doing wrong?

U-Boot TPL 2020.01-7-g365495a329 (Mar 30 2020 - 15:28:38)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2020.01-7-g365495a329 (Mar 30 2020 - 15:28:38 +0000)
Trying to boot from MMC2


U-Boot 2020.01-7-g365495a329 (Mar 30 2020 - 15:28:38 +0000) Manjaro ARM

Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808  
MMC:   dwmmc@fe320000: 1, sdhci@fe330000: 0
In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: Pine64 Pinebook Pro
## Error: Can't overwrite "serial#"
## Error inserting "serial#" variable, errno=1
rockchip_dnl_key_pressed: adc_channel_single_shot fail!
Net:   No ethernet found.
Hit any key to stop autoboot:  0  

[ ---> I can manually intervene here and load my stuff from the SD card just <--- ]

starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3c0000: USB EHCI 1.00
Bus dwc3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus dwc3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 2 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf

I just received my Manjaro PinePhone, and my intended use is:

1. Make and receive calls
2. Send and receive SMS
3. Use Signal messenger
4. Use email (IMAP only)
5. Use Nextcloud for calendar and contacts

That's it. Anything else is optional.

I know this is an experimental phone, and I'm happy with that, but I'm curious about which of the currently available distros will get me the closest to a good experience with all the above - especially Signal messenger.

All thoughts welcome.

The screen switches off when the dock is connected to the USB-C port. This happens on 1.2a revision board, not the 1.2 or 1.1. At least, it should be 1.2a because this is the pmOS CE edition.

I have read something about fixing this by removing resistor R1318. But I don't know where this resistor is. There are pictures and videos on the web showing how to fix revisions 1.2 and 1.1 but nothing about 1.2a.

Does anyone know how to fix 1.2a?

Hey Guys, 

Fairly new to the Linux community so forgive me if this is a dumb question, I've been getting USB disconnects for awhile now. Also random crashes (which may or may not be related)

Decided to check my dmesg and it is very angry complaining of 

Finally I got my usb wifi dongle working.

From linux kernel 4.xx on this chip is supported but I found out - after using several linux distributions - that it just doesn't work from the start.
Two patches are needed for the driver to get it to play.

First get the right kernel sources and headers for the linux distribution (kernel) you use.
In my case it was a 5.8.17 linux kernel (armbian 20.08.1). With 'apt ..' you can get the kernel sources, but command 'armbian-config' makes it easy to install them in /usr/src/ .
Note that a specific version number within the headers (see http://billauer.co.il/blog/2013/10/versi...obe-force/ ) should be exactly the same for the compiled driver.
In my case this was 5.8.17-rockchip64, but the installed headers contained only 5.8.17.
Update this so it is the same. (If you don't do that insmod fails.)
Then follow the 2 steps below:

1. php.c
follow this: 
https://github.com/kuba-moo/mt7601u/issu...-352250127

2. mcu.c
follow this:
https://bbs.archlinux.org/viewtopic.php?id=224859

Command ifconfig should show a wifi device now.
'armbian-config' let you easily set the password and wifi access point for your wifi connection.

Regards,
Johannes

For development would be nice if we could have a screen share setup for the PinePhone.

I've got a mine with Manjaro and I'm struggling to find a way to share the PinePhone screen/imput to my linux desktop, I've tried to find vnc/xrdp through the package manager but no luck.

Does someone managed to have a good setup for screen/input sharing ?

Based on this page https://www.pine64.org/pinephone/ the pinephone does have a barometer sensor but I do not see any mention elsewhere about it.
If it doesn't have a barometer I think that page should be updated otherwise it can be viewed as false advertisement.

Does someone know something about it ?

Cheers !

====
SPECIFICATIONS

[*]Allwinner A64 Quad Core SoC with Mali 400 MP2 GPU

[*]2GB of LPDDR3 RAM

[*]5.95″ LCD 1440×720, 18:9 aspect ratio (hardened glass)

[*]Bootable Micro SD

[*]16GB eMMC

[*]HD Digital Video Out

[*]USB Type C (Power, Data and Video Out)

[*]Quectel EG-25G with worldwide bands

[*]WiFi: 802.11 b/g/n, single-band, hotspot capable

[*]Bluetooth: 4.0, A2DP

[*]GNSS: GPS, GPS-A, GLONASS

[*]Vibrator

[*]RGB status LED

[*]Selfie and Main camera (2/5Mpx respectively)

[*]Main Camera: Single OV6540, 5MP, 1/4″, LED Flash

[*]Selfie Camera: Single GC2035, 2MP, f/2.8, 1/5″

[*]Sensors: accelerator, gyro, proximity, compass, barometer, ambient light

[*]3 External Switches: up down and power

[*]HW switches: LTE/GNSS, WiFi, Microphone, Speaker, Cameras

[*]Samsung J7 form-factor 3000mAh battery

[*]Case is matte black finished plastic

[*]Headphone Jack

===

Hello,
I want to evaluate the watch capabilities and then I created an order for 2 dev kits + 2 pieces of the sealed box (total of 6 watches).
But the system say to me that I cannot order more than 1 piece of the sealed devices.
My question is: if we want to take this platform a a reference platform for one project, then how will be possibile to buy quantities?
Thanks in advance
D