My phones motherboard just stopped working so I am now forced to use the PP as a daily driver. It's been alright so far but the microphone on the phone is super staticy and it won't work with my bluetooth headset. I can listen to music but can't talk over the phone. I can't get discord on the phone and Axolotl doesn't do phone calls so what other options are there?

I’m trying to compile Ayufan’s mainline Linux and I’m missing DT-overlay.  What is missing? I thought you just had to install the needing building tools, clone the git, cp the rockchip-Linux.config, make menuconfig, and then make -j6.  What did I miss?

Hi, a completely new user here!

I just bought my PineTIme, and it's the first product I've ever bought from Pine64. I was wondering if there is any reason for the PineTime to not support Unicode characters? The letters from my native language simply do not show up. Thanks to GadgetBridge I can at least replace those letters with other letters to better understand, but I find it weird that the device doesn't support Unicode.

So my question/point of discussion; Is there a technical limitation or something preventing Unicode-support? If so, what approach could the devs take to possibly support unicode or special characters? Is there any way a non-technical user can help out getting something like this through, or is it on some sort of roadmap already?

small instruction for building u-boot surrounded by aarch64:

Quote:U-Boot SPL board init
U-Boot SPL 2017.09-rk3566 (Jul 25 2021 - 00:51:44)
unknown raw ID phN
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
No misc partition
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256+ OK
## Checking uboot 0x00a00000 ... sha256+ OK
## Checking fdt 0x00b23d18 ... sha256+ OK
## Checking atf-2 0xfdcc9000 ... sha256+ OK
## Checking atf-3 0xfdcd0000 ... sha256+ OK
## Checking optee 0x08400000 ... sha256+ OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 257.451 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-135-gcda1658bc-dirty:xsf
NOTICE:  BL31: Built : 14:19:26, Jun  1 2021
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    pmu v1 is valid
INFO:    dfs DDR fsp_param[0].freq_mhz= 1056MHz
INFO:    dfs DDR fsp_param[1].freq_mhz= 324MHz
INFO:    dfs DDR fsp_param[2].freq_mhz= 528MHz
INFO:    dfs DDR fsp_param[3].freq_mhz= 780MHz
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    BL31: Initializing runtime services
INFO:    BL31: Initializing BL32
I/TC:
I/TC: Start rockchip platform init
I/TC: Rockchip release version: 1.0
I/TC: OP-TEE version: 3.6.0-307-g0b06ae94 #1 Fri May  7 01:52:27 UTC 2021 aarch64
I/TC: Initialized
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0xa00000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-rk3566 (Jul 25 2021 - 00:57:20 +0300)

Model: Pine64 RK3566 Quartz64 Board
PreSerial: 2, raw, 0xfe660000
DRAM:  7.7 GiB
Sysmem: init
Relocation Offset: ed354000, fdt: eb9f99f8
no mmc device at slot 1
dwmmc@fe2b0000: 1 (SD), dwmmc@fe2c0000: 2, sdhci@fe310000: 0
Bootdev(atags): mmc 1
MMC1: Legacy, 50Mhz
PartType: EFI
No misc partition
boot mode: None
FIT: No boot partition
No resource partition
Failed to load DTB
Failed to get kernel dtb, ret=-19
io-domain: OK

** Unable to use mmc 1:3 for loading the env **
Using default environment

Model: Pine64 RK3566 Quartz64 Board
rockchip_set_serialno: could not find efuse/otp device
CLK: (sync kernel. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
  apll 816000 KHz
  dpll 528000 KHz
  gpll 1188000 KHz
  cpll 1000000 KHz
  npll 24000 KHz
  vpll 24000 KHz
  hpll 24000 KHz
  ppll 100000 KHz
  armclk 816000 KHz
  aclk_bus 150000 KHz
  pclk_bus 50000 KHz
  aclk_top_high 300000 KHz
  aclk_top_low 200000 KHz
  hclk_top 150000 KHz
  pclk_top 50000 KHz
  aclk_perimid 300000 KHz
  hclk_perimid 150000 KHz
  pclk_pmu 50000 KHz
Net:  clk_get_by_name(master_bus) failed: -22eqos_probe_resources() failed: -22No ethernet found.
Hit key to stop autoboot('CTRL+C'):  0
## Booting FIT Image FIT: No boot partition
FIT: No FIT image
Could not find misc partition
ANDROID: reboot reason: "(none)"
optee api revision: 2.0
TEEC: Waring: Could not find security partition
Not AVB images, AVB skip
android_image_load_by_partname: Can't find part: boot
Android image load failed
Android boot failed, error -1.
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:2...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
212 bytes read in 17 ms (11.7 KiB/s)
1:      slarm64
Retrieving file: /Image
29239808 bytes read in 2476 ms (11.3 MiB/s)
append: root=/dev/mmcblk0p3 ro rootwait rootfstype=ext4 init=/sbin/init loglevel=4 earlycon=uart8250,mmio32,0xfe660000 console=tty1 console=ttyS2,1500000n8
Retrieving file: /dtb/rk3566-quartz64a.dtb
75961 bytes read in 85 ms (872.1 KiB/s)
Fdt Ramdisk skip relocation
## Flattened Device Tree blob at 0x0a100000
  Booting using the fdt blob at 0x0a100000
  'reserved-memory' ramoops@110000: addr=110000 size=f0000
  Using Device Tree in place at 000000000a100000, end 000000000a1158b8
Adding bank: 0x00200000 - 0x08400000 (size: 0x08200000)
Adding bank: 0x09400000 - 0xf0000000 (size: 0xe6c00000)
Adding bank: 0x100000000 - 0x200000000 (size: 0x100000000)
Total: 2980.864 ms

Starting kernel ...

I checked my repository listing from within the Software app. It shows two debian repos (main and non-free), flathub, and two firmware repos. I was looking for the Mobian repo. Has the need for a Mobian repo been eliminated by the updated debian repos? Or is there something not quite right with my system configuration?

The Pine Phone is working better than ever. I'm just concerned that my phone won't be getting the latest updates.

Hello Forum,

I had to change my screen and apparently lost the approximity sensor. Simultaneously I fired up Mobian on the internal storage.
When booting into it, the screen dims down after a couple seconds.

I would like to keep Mobian and found out that I have to disable the proximity sensor in the config files. Problem: I don't know how I can gain root access to the mounted phones storage (under Ubuntu).

Alternatively, I could also reinstall mobian having the proximity sensor disabled before. Unfortunately I also don't know how to do that.

If this is not mobian-specific enough, please let me know and I will delete the thread. Anyway, I would be very glad for any hint to solve this problem.
Thank you in advance

Hello,

I purchased my PinePhone Braveheart edition (v1.1) first time when they were launched (ordered in November 2019, received it in February 2020).
The microphone has never worked. At the beginning, I couldn't test it; when the first alpha distros became available and I was able to test the microphone, it was too late to send it back under warranty. Eventually I got a new Side Board, on which the microphone is soldered, and I replaced the original one, but the microphone still doesn't work.


Currently the installed OS is Manjaro with KDE Plasma Mobile. Just after the full OS is loaded, under Settings -> Audio, in "Recording Devices" section, the Internal Microphone is shown:


   


After tapping on the button and sellecting the "Headset Microphone" there is no option to go back to the "Internal Microphone" (see the image below):
   
In my opinion this looks like a software issue. If I use a headset, the microphone on the headset works fine and, if I make a phone-call, I can have a bi-directional conversation.


Any feedback? The next step would be to replace the main board. Or sell the phone on eBay and put a stop to my misery

Howdy Piners:

My pinebook pro didn't have bluetooth, wifi, audio, or display functioning properly, until I installed the blobs.  I'm running slarm64, so it was natural to download the blobs from the sndwvs repository:  https://gitlab.com/sndwvs/images_build_k...s/firmware. 

However, what if something happened to this repository and it went down?  I would feel safer having an additional source.

What other repositories contain pinebook pro blobs, and which repository is "most upstream" and likely to have the most up-to-date firmware?

Since source code is not shared with blobs, then these are certainly something we can't compile ourselves.  Does pine64 have an "official" repository from which it releases these nuisances (sorry I don't like blobs, and would prefer a totally open device with poor non-proprietary resolution on its display and camera).   Nevertheless, since forced to use the blobs if I want full functionality in my pinebook, it would be nice to know from where they can be retrieved?  

Also, will the pbp blobs eventually find themselves in linux kernel's mainline firmware:  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git?

Hi!

After updating to the latest version of Manjaro ([ARM Stable Update] 2021-07-23) my PBP's splash boot image does not appear anymore.
Only a black screen until the logging page appears.

I think this happens because the kernel boots plash was not added.
It should be like that? Is this a new feature?


Also there is one more annoying thing that happens after this update, my PBP freezes randomly and only a hard restart resolves this. Does this happen to anyone else?

Thanks

Here we compile and run the LVGL library demos on Arch Linux Barebone to show that we can create useful graphics through the Frame Buffer.

https://lvgl.io/

1) Install the basic dependencies for program development
------------------------------------------------------------
`sudo pacman -Syu base-devel`

2) Clone the relevant repositories
------------------------------------------------------------
`git clone --recursive https://github.com/lvgl/lv_port_linux_frame_buffer`

3) Adjust to Pinephone's screen resolution
------------------------------------------------------------
Edit the file "main.c" in "lv_port_linux_frame_buffer" and change Line 31 from 800 to 720 and Line 32 from 480 to 1440,

disp_drv.hor_res    = 720;
disp_drv.ver_res    = 1440;

4) Enable Touchscreen
------------------------------------------------------------
We use the "evdev" event driver, the raw data from the touchscreen for Arch Barebone are output at "/dev/input/event1", the rest of the events in the folder are the the physical buttons and the sense of USB, headphone and vibration.

We need to edit 2 files, "lv_drv_conf.h" and "main.c"

-------- lv_drv_conf.h ----------

Line 389 should be changed to

# define USE_EVDEV 1

Line 397 should be changed to

# define EVDEV_NAME "/dev/input/event1"

--------- main.c -----------

At the beginning of the file we should include the header

#include "lv_drivers/indev/evdev.h"

Right before Line 36 where we call the demo function we should initialise the touchscreen by adding the following code

/* enable event input*/
evdev_init();

/* enable touchscreen*/
lv_indev_drv_t indev_drv;
lv_indev_drv_init(&indev_drv);
indev_drv.type = LV_INDEV_TYPE_POINTER;
indev_drv.read_cb = evdev_read;
lv_indev_drv_register(&indev_drv);

5) Compile by running `make` in "lv_port_linux_frame_buffer"
------------------------------------------------------------
The command will generate an executable named "demo". If you want to change something and recompile then first remove all the object files of the edited files and the "demo" and `make` again.

`rm [edited-files].o`
`rm demo`
`make`

6) Run the program on Arch Linux Barebone
------------------------------------------------------------
`./demo`

7) Exit the program pressing CTRL+C
------------------------------------------------------------


Note :
------------

By default the code runs the `lv_demo_widgets` demo, you can test the rest of the 5 demos by changing line 36 in "main.c" to one of the following choices

lv_demo_widgets();
lv_demo_music();
lv_demo_keypad_encoder();
lv_demo_benchmark();
lv_demo_stress();

then remove "main.o" and "demo" and `make`

`rm main.o`
`rm demo`
`make`