I finally got the touch screen working! still some spurious events I need to track down still, including an interrupt flood. But the first thing I added was finger paint mode, to check touch locations, and a button to clear the screen
All good fun, but my 'clear screen' functionality is super slow. I'm guessing at .25s, slow enough to see the progress. This is using a framebuffer approach i.e. no GPU, and a memset to do the clear. But I also tried a direct arm assembly loop, and looks the same.
I dont have enough experience with the PinePhone to know if this is to be expected? or an anomaly in my approach. I was expecting to be able to easily do 60fps with plenty of spare cycles to run my apps.
firstly the earpiece hardware works fine, I can play audio through it.
I replaced the mainboard on my PPpro and at some point early on I lost the ability to hear or send audio on a telephone call.
I flashed themodemdistro firmware 8.0 via ./flashall and then ADSP V 01.003.01.003 and then DSP V 01.002.01.002 https://github.com/the-modem-distro/pine...LASHING.md
did both several times over the last days.
incoming and outgoing calls no luck; 2g, 3g, 4g
interesting ringtone doesn't work either
I have been flashing various images testing, I have flashed an image of the final from my old main board where phone audio mostly worked. I have been writing my old /home onto the new installs once I have them installed but I do a phone test first.
Rebooting as well as shutdown, rest, boot doesn't work either.
Data works, SMS works, DIalling works receiving works, just no audio except that 4g fails to make/take a call as usual which will be a problem once 2g and 3g shut down.
the audio line alsa/pipewire stuff gets complicated I am nut sure what to look for in the modem's dmsg
I am probably missing an obvious mistake, embarrass me please by showing me my error!
(edit)moved to ADSB 30.004 and 4g seems to be work, but that is always temporary, not the real problem of this post anyways
(edit2) I even rewrote the EFS https://themodemdistro.com/efs_recovery makes calls no audio in/out
As was just verified, the arm64 UEFI variant of the Window Maker Live Linux distribution based on Debian/Trixie boots just fine on towboot enabled Pinebook Pro. This also includes the graphical debian installer routine, avoiding the need to bother with the awkward serial console for installations. I didn't complete a full installation yet on my own bare metal PBP because the machine needed for development is not suitable also for testing, and all installation testing has been done only in qemu so far.
Before you start downloading the ISO image for trying it out yourself, be aware that with the exception of the freely usable i386 version, the ISO images for both arm64 and amd64 are distributed as encrypted 7z archives which require a password to unpack them. Due to personal circumstances i am currently not in the position to just give away the fruits of my time and efforts investment without asking for a return. Until it will finally be publically disclosed at the end of this year, this password is therefore provided only to people who are donating some cash to the project.
On the other hand, the sources to enable people to build any variant of the ISO themselves are, of course, readily available. So if you can't afford even any minimal donation and don't want to wait for the public password disclosure at the end of the year, you can simply create your own custom ISO image.
For interested people who are contributing any publically accessible open source work themselves, the password will be freely provided without any donation requirement. Please contact me privately if this is of interest for you.
TL;DR: See the attached picture. Has anybody got a this Micro SDXC class 10 with 1 TB working in a PinePhone or PineBook? Could this be a PAGHY card?
I bought this card around May 2021 after I got the PinePhone in April 2021. My intention is to have a multi-distribution card as described on https://wiki.pine64.org/wiki/PinePhone_P...sing_rk2aw for the PinePhone Pro. In the time before last week I was busy with other things so the card wasn't really used much.
During the preparations several problems occured.
The first hint is "Alternate GPT is invalid, using primary GPT".
[Fr Nov 28 11:11:37 2025] mmc0: new high speed SDXC card at address 215d [Fr Nov 28 11:11:37 2025] mmcblk0: mmc0:215d APPSD 999 GiB [Fr Nov 28 11:11:37 2025] Alternate GPT is invalid, using primary GPT. [Fr Nov 28 11:11:37 2025] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 [Fr Nov 28 11:11:37 2025] mmc2: new DDR MMC card at address 0001 [Fr Nov 28 11:11:37 2025] mmcblk2: mmc2:0001 DA4032 29.1 GiB [Fr Nov 28 11:11:37 2025] mmcblk2boot0: mmc2:0001 DA4032 partition 1 4.00 MiB [Fr Nov 28 11:11:37 2025] mmcblk2boot1: mmc2:0001 DA4032 partition 2 4.00 MiB [Fr Nov 28 11:11:37 2025] mmcblk2: p1 p2
mobian@mobian:~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 999G 0 disk ├─mmcblk0p1 179:1 0 1G 0 part ├─mmcblk0p2 179:2 0 16G 0 part ├─mmcblk0p3 179:3 0 64G 0 part ├─mmcblk0p4 179:4 0 64G 0 part ├─mmcblk0p5 179:5 0 64G 0 part ├─mmcblk0p6 179:6 0 64G 0 part ├─mmcblk0p7 179:7 0 64G 0 part └─mmcblk0p8 179:8 0 128G 0 part mmcblk2 179:32 0 29,1G 0 disk ├─mmcblk2p1 179:33 0 504M 0 part /boot └─mmcblk2p2 179:34 0 28,6G 0 part / mmcblk2boot0 179:64 0 4M 1 disk mmcblk2boot1 179:96 0 4M 1 disk zram0 254:0 0 1,5G 0 disk [SWAP] mobian@mobian:~ $
The second problem occured when I tried to make a F2FS on /dev/mmcblk0p8
Info: Disable heap-based policy Info: Debug level = 0 Info: Trim is enabled Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 268435456 (131072 MB) Info: zone aligned segment0 blkaddr: 512 Info: format version with "Linux version 5.10-sunxi64 (builder@mobian) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT Fri Jul 23 10:30:36 UTC 2021" Info: [/dev/mmcblk0p8] Discarding device Info: This device doesn't support BLKSECDISCARD Info: This device doesn't support BLKDISCARD Error: Failed to create the root directory!!! Error: Could not format the device!!!
The card war removed after the errors.
mobian@mobian:~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk2 179:32 0 29,1G 0 disk ├─mmcblk2p1 179:33 0 504M 0 part /boot └─mmcblk2p2 179:34 0 28,6G 0 part / mmcblk2boot0 179:64 0 4M 1 disk mmcblk2boot1 179:96 0 4M 1 disk zram0 254:0 0 1,5G 0 disk [SWAP] mobian@mobian:~ $
[Fr Nov 28 11:15:28 2025] ov5640 4-004c: firmware upload success [Fr Nov 28 11:15:28 2025] ov5640 4-004c: uploaded firmware didn't start, got to 0x7f, retrying... [Fr Nov 28 11:15:28 2025] ov5640 4-004c: uploaded firmware didn't start, got to 0x7f [Fr Nov 28 11:15:28 2025] ov5640 4-004c: ov5640_set_ctrl_focus: no autofocus firmware loaded [Fr Nov 28 11:26:15 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:26:15 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:26:15 2025] mmc_erase: group start error -110, status 0x0 ... [Fr Nov 28 11:26:32 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:26:32 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] sunxi-mmc 1c0f000.mmc: data error, sending stop command [Fr Nov 28 11:27:14 2025] sunxi-mmc 1c0f000.mmc: send stop command failed [Fr Nov 28 11:27:14 2025] mmc0: tried to HW reset card, got error -110 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 774187008 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 774359040 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 774531072 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 774703104 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 774875136 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 775047168 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 775219200 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 775391232 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 775563264 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] blk_update_request: I/O error, dev mmcblk0, sector 775735296 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:14 2025] mmc_erase: group start error -110, status 0x0 ... [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] print_req_error: 767 callbacks suppressed [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 907226112 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 907398144 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 907570176 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 907742208 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 907914240 op 0x3 (DISCARD) flags 0x0 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 908044288 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 908216320 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 908388352 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 908560384 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] blk_update_request: I/O error, dev mmcblk0, sector 908732416 op 0x3 (DISCARD) flags 0x4000 phys_seg 1 prio class 0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:19 2025] mmc_erase: group start error -110, status 0x0 ... [Fr Nov 28 11:27:21 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:21 2025] mmc_erase: group start error -110, status 0x0 [Fr Nov 28 11:27:22 2025] sunxi-mmc 1c0f000.mmc: data error, sending stop command [Fr Nov 28 11:27:22 2025] sunxi-mmc 1c0f000.mmc: send stop command failed [Fr Nov 28 11:27:22 2025] sunxi-mmc 1c0f000.mmc: Card stuck in wrong state! card_busy_detect status: 0x700 [Fr Nov 28 11:27:22 2025] mmc0: tried to HW reset card, got error -110 [Fr Nov 28 11:27:22 2025] mmcblk0: recovery failed! [Fr Nov 28 11:27:22 2025] mmc0: card 215d removed
After a reboot I tried an ext4 fs. Is ext4 on a sd-card a bad idea anyway?
Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done
Fine so far.
mobian@mobian:~ $ sudo mount /dev/mmcblk0p8 /media/Images/ mount: /media/Images: wrong fs type, bad option, bad superblock on /dev/mmcblk0p8, missing codepage or helper program, or other error.
I just received my replacement Pinephonepro system board.
I had a tow-boot bootable SD ready to begin the process but the phone now loads a Rockchip splash and then boots into Chinese Android.
It also doesn't auto-boot when plugged into power, it just charges as it is an android.
How can I force this to bootfrom SD?
I wonder if this requires ADB commands?
I also wonder if the board requires ADB unlocking now as it is loaded with android...
I do not dread/write/speak Chinese so I have no idea how to get into dev mode.
A side problem is the main camera socket keeps popping off from the new board, I tried adding a paper shim to push it down via pressure form the plastic enclosure when screwed down. I wonder if it is broke and I need to spend $30 replacing the camera.
it also seems that the proximity detector is not fully pushed into its place as I can see the notification LED, this probably just needs to be opened and pushed down or remove the shim from the main camera.
(edit) https://wiki.radxa.com/Rock/SD_booting this is for rockchip not sure if it will do anything useful for me, I want to be careful that I dont do more damage.
This just seems to be a windoze SD card writer app which can flip the bootable bit
per the dev boards(r-pi like boards) stuff here https://wiki.radxa.com/Rock/dual_boot
You can flash over those board's /recovery partition, if I could get that much access from my phone
For now this might as well be bricked unless I reinsert the broken board that cant use hibernate mode and cant boot without a good smack(detached RF shield), I wonder if I can interfere with anything to force a SD boot using the serial cable?
Bus 003 Device 004: ID 1163:0200 DeLorme Publishing, Inc. Earthmate GPS (LT-20, LT-40)
Danctnixfor the Pinephone and PPpro I assume have working GPS and mapping that attach to the USB device generated by the modem package.
If that is the case what packages sould I Syu or flatpak onto a Pinetab2 to get this setup so I can have bigger screen navigation with the GPS receiver suction cupped to the window vs inside the device?
(edit)
It seems like there is a problem with the cypress_m8 driver since around it's introduction in 2005 so it requires a kernel patch to receive the NEMA feed see 1 & 3.
1 - https://linux-usb-devel.narkive.com/sz0J...s-m8-patch#
2 - https://github.com/torvalds/linux/blob/m...press_m8.c
3 - https://bugs.launchpad.net/bugs/111694
3 uses a fix referred to in 1 though this seems to be sub-optimal commenting out this line and recompiling
Code:
cypress_set_dead(port);
I had found these Delorne Earthmate dongles on the auction site for $5 each.
(it makes me wonder if a hardware hack with a new soldered in usb-serial adapter to the NEMA output might be easier)
So I got the proximity / light sensor working in my Zig OS Although the sensor seems to be always powered on, which kinda makes sense, but I somehow expected a GPIO pin for switching it off.
Now I am looking at the gyroscope, wow it looks complicated and I am kinda glad to see the secondary I2C fusion? lines are not connected.
But here again it seems to be always powered on? (based on schematic), and I recall from my early iOS days, that gyroscopes can waste some power when always on. Did I miss something?
Howdy.
I've come across several daily driver users who eventually state things like
Oh, I don't care about buggy wifi, slow X, crashing Y or unstable Z because I use it only for: calls, sms, contacts.
Oh, who cares about battery life, i keep it powered off most of the day etc..
my question is, what is the point of having a linux phone when use case is dumb phone features only? Why not just use some dumb nokia that runs for 7 days on a battery and call it a day? also same privacy level on those devices...
I think the cold truth is, because its too slow and unstable to do anything else then calls and sms with it, but then the loop goes back to the beginning, what is the point..
We are looking for people to guide them to install it and write the installation steps along the way, so if you are interested, contact us in our discord server or in the official #pinenote
Also of course some more disclaimers:
1. Quill on pinenote is in its early days, there are many issues and minor problems like no rotation, no sleep (sleep drains the battery a lot anyway, so i did not care to add it)
2. The installation, while we used it, could have problems along the way, cant promise it would be painless, so maybe a few days without a working pinenote is possible
):