Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,759
» Latest member: Ounfee
» Forum threads: 16,283
» Forum posts: 117,289

Full Statistics

Latest Threads
PinePhone USB-C port and ...
Forum: PinePhone Hardware
Last Post: RobinHayes
1 hour ago
» Replies: 7
» Views: 6,208
Wifi 5Ghz Issue
Forum: PineNote Software
Last Post: Ounfee
10 hours ago
» Replies: 1
» Views: 7,820
No phone call audio, logs...
Forum: PinePhone Pro Hardware
Last Post: DieSkaarj
Yesterday, 04:18 PM
» Replies: 11
» Views: 755
Diagnosing and fixing fai...
Forum: PinePhone Pro Software
Last Post: Kevin Kofler
Yesterday, 02:33 PM
» Replies: 4
» Views: 533
Quartz64b pcie help neede...
Forum: Quartz64 Hardware and Accessories
Last Post: S265
12-19-2025, 04:08 PM
» Replies: 1
» Views: 124
Tariffs on delivery to US
Forum: General
Last Post: Sergiu
12-19-2025, 05:31 AM
» Replies: 0
» Views: 92
Legaxy LCD images
Forum: Android on PINE A64-LTS / SOPINE
Last Post: TaleyaJ
12-18-2025, 06:47 AM
» Replies: 0
» Views: 67
Pinephone (Pro) Keyboard ...
Forum: PinePhone Accessories
Last Post: biketool
12-18-2025, 05:10 AM
» Replies: 5
» Views: 13,689
What to can't boot from T...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
12-18-2025, 01:05 AM
» Replies: 1
» Views: 168
SSH over USB
Forum: PineNote Software
Last Post: Szybet
12-17-2025, 02:54 PM
» Replies: 4
» Views: 1,496

 
Exclamation The internal speaker stops working
Posted by: anonymous - 01-15-2024, 02:56 AM - Forum: Mobian on PinePhone - Replies (6)

Hello

The internal speaker no longer works on my Pinephone, even after rebooting. I haven't updated it for several days. I assume that I broke something after trying to use an external speaker through bluetooth. The internal earpiece and the headset still work.

How can I solve my problem, preferably without reinstalling the whole system as I use my phone daily?


  Pinebook Pro Recovery with Void Linux (xbps)
Posted by: bds - 01-14-2024, 10:21 PM - Forum: Pinebook Pro Tutorials - Replies (4)

Pinebook Pro Recover with Void Linux (xbps)

Hello all!

I recently received my Pinebook Pro and, as I have gathered has happened to quite a few people, broke the system with an initial Manjaro update. I thought I'd do my part to help anyone else having the same problem by documenting what I've figured out over the last few days. This will basically be a compilation of a bunch of different articles and tutorials from across the internet, with application specific advice. I'll try to link all major sources. I chose to use Void Linux just 'cause it's what I'm used to, and xbps makes building a system onto the SD card super easy.

While I've learned a lot through this process, I'm by no means an expert. I would appreciate any input, correction, or elaboration the topics discussed.

Just to account for any hardware differences, this was on a PBP received on Jan 11 2024. I haven't checked into this, but if there's any where I can find a hardware revision number or anything like that, let me know.

Some preamble:
The PBP can boot directly from, in order:
- the onboard SPI module,
- the onboard eMMC module, or
- a microSD card.

By default, nothing is written to the SPI. The factory Manjaro ARM system is installed on the eMMC. From what I understand, the system breaks after a Manjaro update because the system updates the bootloader package without properly configuring it. The result is that the PBP boots from the eMMC, but the user gets nothing but a black screen.

Fortunately, the PBP mainboard has a hardware switch to block access to the eMMC, so we can turn that on and boot instead from a microSD card.

Regarding the bootloader, I to use Tow-Boot. I don't have experience any with alternatives, but it was simple to flash and is flexible at boot-time, which is what I was looking for.

So this was my strategy:
1. Disable the eMMC
2. Boot from SD card
3. Flash Tow-Boot to the SPI
4. Re-enable the eMMC
5. Boot again from the SD card
6. ???
7. System repaired.

If I wanted to, I think I could have skipped a couple steps by re-enabling the eMMC while the system was running and flashing Tow-Boot to the eMMC's boot partition. However, I like having the bootloader on the SPI and didn't want to keep Manjaro anyways. Furthermore, this method lets me use GPT and EFI; this probably doesn't matter but it just feels right.

# Setup
To start off with, we're gonna want an existing Void Linux system, though you should be able to follow the same process on any Linux system using a statically-linked XBPSThis can be from a live image, though depending on your setup that might present some issues with memory and device throughput when writing to the SD card.

First off, we're gonna want to make sure all our repositories and packages are up to date:

Code:
# xbps-install -Su xbps
# xpbs-install -Su

Next, we'll make sure we have the packages we need for building the system on the SD card. `binfmt` and `qemu-static-user` are required for cross-building, so they're not required on an aarch64 host system.
Code:
# xbps-install -Su xz wget xtools binfmt-support qemu-user-static

Enable the `binfmt-support` service:
Code:
# ln -s /etc/sv/binfmt-support /var/service

# Building the SD card
First, identify your SD card's device handle. If your host system has built-in SD card support, it will likely be `/dev/mmcblkX`. I was using a USB adapter, so mine was at `/dev/sdX`.

## Flash Tow-Boot to the SD card
It should go without saying, but make sure to back up anything you don't want to lose.

Download and extract Tow-Boot for the PBP:
Code:
# wget https://github.com/Tow-Boot/Tow-Boot/releases/download/release-2022.07-006/pine64-pinebookPro-2022.07-006.tar.xz
# tar xvf pine64-pinebookPro-2022.07-006.tar.xz

Flash Tow-Boot to the SD card. For reference, we're using the "shared storage strategy.":
Code:
# dd if=pine64-pinebookPro-2022.07-006.tar.xz/shared.disk-image.img of=/dev/XXX bs=1M oflag=direct,sync status=progress

## Install Void via chroot
This next portion follows this guide from the Void Handbook. In particular, we're using the XBPS method.

### Partition and format the SD card
Flashing Tow-Boot should have created initialized a GPT partition table and created a partition at the beginning of the SD card. I used cfdisk to partition the rest of the SD card, so it looks like this:
/dev/sdg1 = Tow-Boot
/dev/sdg2 = +256M, EFI System
/dev/sdg3 = to the end of the disk, Linux Filesystem.

After that, create the filesystems:
Code:
# mkfs.vfat /dev/sdg2
# mkfs.ext4 /dev/sdg3

### Mount the new filesystems
Code:
# mount /dev/sdg3 /mnt
# mkdir -p /mnt/boot/efi
# mount /dev/sdg2 /mnt/boot/efi

### Creating the base installation
A caveat: I don't actually know what the ideal kernel and firmware situation looks like. Void's Pinebook Pro packages seem fairly old, and I specifically want to avoid the `pinebookpro-uboot` package (and the `pinebookpro-base` package which depends on it). I opted to use the basic linux kernel and install the `pinebookpro-firmware` package, because I figured it couldn't hurt. Regardless...

We want to set environment variables that we'll use to tell XBPS which repo to pull from and what architecture to use. Set `ARCH` to either `aarch64` or `aarch64-musl` to use glibc or musl, respectively.
Code:
# REPO=https://repo-default.voidlinux.org/current/aarch64
# ARCH=aarch64-musl

Copy the RSA keys from the host to the SD card:
Code:
# mkdir -p /mnt/var/db/xbps/keys
# cp /var/db/xbps/keys/* /mnt/var/db/xbps/keys/

And finally we'll use XBPS to bootstrap the installation.
Code:
# XBPS_ARCH=$ARCH xbps-install -S -r /mnt -R "$REPO" base-system pinebookpro-firmware linux

### Configuration
Chroot into the new installation using `xchroot`:
Code:
# xchroot /mnt /bin/bash

Set the root password:
Code:
[xchroot /mnt] # passwd

Follow the instructions in the Void Handbook for configuring fstab and for installing GRUB. We want to use the instructions for UEFI, with the `grub-arm64-efi` package, and use the `--removable` flag on `grub-install`

Before leaving the chroot, install `mtd-utils`, which has the `flashcp` utility we'll use for flashing to the SPI, and run `xbps-reconfigure` to make sure everything's set up correctly.
Code:
[xchroot /mnt] # xbps-install mtd-utils
[xchroot /mnt] # xbps-reconfigure -fa
[xchroot /mnt] # exit

### The final touch
Before unmounting the SD card and slapping it into the PBP, copy over the Tow-Boot image we're gonna flash to the SPI.
Code:
# cp pine64-pinebookPro-2022.07-006/binaries/Tow-Boot.spi.bin /mnt/root
# umount -R /mnt

## Booting the SD card and flashing the SPI
As long as the eMMC is disabled, you should now be able to insert the SD card and boot into it through Tow-Boot, followed by GRUB. Log in using the root password you set earlier, and flash the Tow-Boot image we copied over onto the SPI:
Code:
flashcp Tow-Boot.spi.bin /dev/mtd0

At this point, you should be able to remove the SD card, enable the eMMC, reboot the machine, and be met with the Tow-Boot graphical interface, though the system installed on the eMMC will likely still be unusable. I leave repairing/replacing the system installed on the eMMC as an exercise for the reader. I followed a similar process to what's described above to install Void Linux with EFI boot. It should be noted that GPT doesn't play well with the layout of the eMMC's boot memory, so you should zero out the first 32768 bytes and skip them in your partition scheme, or perhaps just flash Tow-Boot's `noenv` image onto it. This document was helpful for some details.

That's all, thank you.


  Android OS that supports LCD touch panel (pine a64)
Posted by: Spekboy - 01-14-2024, 01:41 PM - Forum: General - No Replies

Hi,
I just bought the LCD panel for my pine a64 and I was wondering where I can find the android os that supports the screen? or else can anyone tell me how to find and edit the uEnv.txt file to make it display on the LCD?


  qcell modem id
Posted by: aular - 01-14-2024, 12:08 PM - Forum: General Discussion on PinePhone - Replies (6)

So i have run into an issue with the fwupdmgr when trying to find the modem id. I go to get devices and it doesnt bring back a actual manafucture of the modem to upgrade it, all it gives me is a whole bunch of nunbers. Is there any thing i can do to get the device id of the qcell modem so i can upgrade it. All i see is letters and numbers. thanks


  pine vacuum cleaner and door phone
Posted by: norayr - 01-13-2024, 07:58 AM - Forum: General - Replies (3)

these are two products i need.

well i need a robot vacuum cleaner, which walks around and cleans.
but i do not want to invest in those things that are connected to clouds and send data, or controllable from clouds.

same with the door phone.

our building's small community had to choose one. and we were not able to find one not connected to the cloud.

i am quite sure i would convince our community to use pine door phone (intercom) if it was selfhosted, and would just require a real ip.

there's no sense of our data to go abroad and come back for opening the door. and the current solution probably gathers photos of everyone who comes and goes, and nobody knows what would it do with the photos.


  PinecilV2 OLED stopped working
Posted by: slura - 01-13-2024, 06:21 AM - Forum: General Discussion on Pinecil - No Replies

Hi! Was using Pinecil V2 for half a year mostly with a Lenovo 65W PD3.0 without any problems. And sometimes with Xiaomi powerbank which supports 15V/3A/45W PD 3.0. One day display stopped working. Dissembled the unit. 4.6V is there after a buck converter. 3V3 is also after the LDO. Firmware flashes successfully. Tried IronOs V2.22 and V2.20. Tried to press '+' button after powering on, tip doesn't get hot. 

Should i try replacing the OLED? 

Any suggestions? Thanks!


  PinePhone Pro Explorer's edition Qualcomm modem recovery
Posted by: shifras - 01-12-2024, 01:49 PM - Forum: PinePhone Pro Hardware - Replies (11)

Hi guys,

i really need help on my PPPro. I was recently trying to update my modem's firmware using gnome-firmware app using this instruction in the video "4 of 5": https://forum.pine64.org/showthread.php?tid=18209
Update failed to install, and now i ended up with non-bootable modem. I searched the PineWiki and found this emergency procedure designed to boot modem in to EDL mode by shorting the test points on the PinePhone, but when i removed the back cover i only found there is no simmilar pins, or at least i don't know which ones to use on my the explorerss edition phone. Also i used this Hardware test build from here: https://wiki.pine64.org/wiki/PinePhone_P...e_Checking 
and test fails for sim card. Also in Arch build it is not listed as /dev/ttyUSB2 or any ttyUSB. Seems it is bricked, and i need to enter EDL mode somehow. Is there any hope to revive the modem?
[Image: PPP-mainboard-nanosim-1.jpg]


  Im thinking of building a Pine64 cluster
Posted by: Theirat1991 - 01-11-2024, 10:10 PM - Forum: General - Replies (1)

So Im thinking of building a Pine64 cluster for a homelab over a Pi for a couple reasons, also being able to order more than one of the same type.
Their website sells USB to barrel power adapters awesome! But I need a power strip that can output 5V 3A for at least four USB ports.
I am not honestly that familiar with power usage and finding pieces but I see a lot of 2.4Amps with a max total of 12Amps. Out of a USB power strip. Is 3A really just 2.4?192.168.0.1 routerlogin 192.168.l.l


Information Heads up: Ordered SI7210-B-00-IVR hall effect sensors
Posted by: TheGrue - 01-11-2024, 04:25 AM - Forum: Pinecil Hardware and Accessories - Replies (2)

Hello everyone!

Just a heads up for German and European users: I ordered some hall effect sensors and should have three (if I don't kill one when soldering) left to give to users so they don't have to order in Asia. Since customs and so on is ugly, I'll only ship within the European union.

I don't have them yet, ETA is 15 days. If you can wait, you won't have to order in Asia, I'll just send it to you in a letter. First come, first serve.

Price is US$ 1.6842 +  0.85€ shipping (a standard letter). I.e. I'll pay the shipping from Asia myself.
One piece per person.
NO GUARANTEES AT ALL.

Tell me in this thread if you need one.

Hope it helps someone.

cu
/me


  dependancy hell
Posted by: SchizoPinePhone225 - 01-10-2024, 07:28 PM - Forum: Arch Linux on PinePhone - Replies (4)

I cannot fix my dependancy issues.

For context I updated my phone, when it asked to replace dependancies I hit yes and all was well until maybe 3 updates later when it began asking for dependancy switches again and now it won't work and claims there is a dependancy conflict.

What must I do? reflash the OS? there has to be another way right?


I tried keyring reset and "pacman -Syyu"
it sucks because these dependancies look very important for KDE