<![CDATA[PINE64 - PinePhone Accessories]]> https://forum.pine64.org/ Mon, 11 May 2026 14:04:41 +0000 MyBB <![CDATA[NEW pinephone keyboard case and LoRa backplate for sale]]> https://forum.pine64.org/showthread.php?tid=20163 Tue, 13 Jan 2026 00:09:40 +0000 ragele]]> https://forum.pine64.org/showthread.php?tid=20163 search, they are only available through this auction btw... just spreading the word. thanks]]> search, they are only available through this auction btw... just spreading the word. thanks]]> <![CDATA[sd card problems]]> https://forum.pine64.org/showthread.php?tid=20097 Sun, 30 Nov 2025 14:04:14 +0000 ottahe]]> https://forum.pine64.org/showthread.php?tid=20097
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

mobian@mobian:~ $ sudo mkfs.f2fs -f /dev/mmcblk0p8

F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

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?

mobian@mobian:~ $ sudo mkfs.ext4 /dev/mmcblk0p8
[sudo] Passwort für mobian:
mke2fs 1.46.2 (28-Feb-2021)
Discarding device blocks: done                           
Creating filesystem with 33554432 4k blocks and 8388608 inodes
Filesystem UUID: a8faee30-82dd-4121-96a9-ce4955c3f06f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

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.

No hints in the dmesg output.

.jpg   20251128_114742.jpg (Size: 214.41 KB / Downloads: 110) ]]>
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

mobian@mobian:~ $ sudo mkfs.f2fs -f /dev/mmcblk0p8

F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

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?

mobian@mobian:~ $ sudo mkfs.ext4 /dev/mmcblk0p8
[sudo] Passwort für mobian:
mke2fs 1.46.2 (28-Feb-2021)
Discarding device blocks: done                           
Creating filesystem with 33554432 4k blocks and 8388608 inodes
Filesystem UUID: a8faee30-82dd-4121-96a9-ce4955c3f06f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

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.

No hints in the dmesg output.

.jpg   20251128_114742.jpg (Size: 214.41 KB / Downloads: 110) ]]> <![CDATA[Replacement battery for PinePhone?]]> https://forum.pine64.org/showthread.php?tid=19843 Mon, 26 May 2025 23:26:18 +0000 j_s]]> https://forum.pine64.org/showthread.php?tid=19843
I don't have an external battery charger and if I connect a wall charger to the phone, the battery charges for a few seconds then tries to boot and dies after a few seconds tries to boot again, diess, over and over.

I did an amazon search on the replacement models in the wiki and the one I bought turned out to be about 6mm short in bothe diemension. Is there a specific battery that I can buy on amazon that will work in a PinePhone?

Is there a way to keep the PinePhone from trying to boot before the battery is charged enough to boot and run with a charger connected by USB?]]>
I don't have an external battery charger and if I connect a wall charger to the phone, the battery charges for a few seconds then tries to boot and dies after a few seconds tries to boot again, diess, over and over.

I did an amazon search on the replacement models in the wiki and the one I bought turned out to be about 6mm short in bothe diemension. Is there a specific battery that I can buy on amazon that will work in a PinePhone?

Is there a way to keep the PinePhone from trying to boot before the battery is charged enough to boot and run with a charger connected by USB?]]> <![CDATA[Searching for a PinePhone Keyboard Case]]> https://forum.pine64.org/showthread.php?tid=19442 Wed, 02 Oct 2024 18:35:47 +0000 RubiksCube]]> https://forum.pine64.org/showthread.php?tid=19442
I am looking for an original PinePhone Keyboard Case as it is not possible to buy it from the official store (and sadly will maybe never be). If you have one for sale, just write me a pm with your price and location (and maybe a picture) and we will get this going. I am also willing to pay for international shipping.


Thanks!
P.]]>
I am looking for an original PinePhone Keyboard Case as it is not possible to buy it from the official store (and sadly will maybe never be). If you have one for sale, just write me a pm with your price and location (and maybe a picture) and we will get this going. I am also willing to pay for international shipping.


Thanks!
P.]]> <![CDATA[Rii mini 4 keyboard and touchpad work over Bluetooth]]> https://forum.pine64.org/showthread.php?tid=19352 Fri, 19 Jul 2024 14:02:45 +0000 Peter Gamma]]> https://forum.pine64.org/showthread.php?tid=19352
I thought that the Rii mini 4 with 2.4 Ghz dongle would be the ultimate solution to solve the Pinephone keyboard problem. After a sleepless night in which I tested 6 cheap Aliexpress docks in all configuration with usb keyboard and mouse, none of the worked. Some time ago, one of them worked with usb keyboard and mouse, but I could not reproduce it.  I thought a Rii mini 4 with 2.4 Ghz dongle would eventually the solution for the Pinephone keyboard problem together with the docking sation:

https://forum.pine64.org/showthread.php?tid=19350

But in the morning I decided not to buy any further Pinephone accessoires for a Pinephone I never use and put on the screed and take it down again for some tests. 

In the afternoon, I thought,  why not to try the Rii 4 over Bluetooth? Reports of Zebulon Walton about a Bluetooth mini keyboard where horrible:

https://forum.pine64.org/showthread.php?...316&page=2

Now i paired the Rii 4 mini over Bluetooth to my Pinephone with postmarketOS. There where no disconnection issues during 3 min tests as where reported with other Bluetooth keyboards:


https://forum.pine64.org/showthread.php?tid=13835

Keys, touchpad and scrollweel worked. One user reported to have issues with connecting a Bluetooth keyboard and mouse at the same time. Only one device worked, either keyboard and mouse.  Other reported that Bluetooth keyboard and mouse work with Logitech devices:

https://forum.pine64.org/showthread.php?...316&page=3

But Logitech has not mini keyboards. The Rii mini 4 is a mini keyboard with dual mode BLE and 2.4 Ghz dongle. I did not get to work the 2.4 Ghz dongle, but the keyboard with touchpad.

The Rii 4 over Bluetooth is the best experience for a Pinephone keyboard for me personally to this date. It is available and worked for 3 min. reliably. And it has also a layout with many keys, similar to the Pinephone keyboard which makes it  a great device. The keyboard is not much bigger than the Pinephone, and fit’s in a pocket.



.jpeg   proxy-iasdfasfasdfasdfmage.jpeg (Size: 27.02 KB / Downloads: 412)
]]>
I thought that the Rii mini 4 with 2.4 Ghz dongle would be the ultimate solution to solve the Pinephone keyboard problem. After a sleepless night in which I tested 6 cheap Aliexpress docks in all configuration with usb keyboard and mouse, none of the worked. Some time ago, one of them worked with usb keyboard and mouse, but I could not reproduce it.  I thought a Rii mini 4 with 2.4 Ghz dongle would eventually the solution for the Pinephone keyboard problem together with the docking sation:

https://forum.pine64.org/showthread.php?tid=19350

But in the morning I decided not to buy any further Pinephone accessoires for a Pinephone I never use and put on the screed and take it down again for some tests. 

In the afternoon, I thought,  why not to try the Rii 4 over Bluetooth? Reports of Zebulon Walton about a Bluetooth mini keyboard where horrible:

https://forum.pine64.org/showthread.php?...316&page=2

Now i paired the Rii 4 mini over Bluetooth to my Pinephone with postmarketOS. There where no disconnection issues during 3 min tests as where reported with other Bluetooth keyboards:


https://forum.pine64.org/showthread.php?tid=13835

Keys, touchpad and scrollweel worked. One user reported to have issues with connecting a Bluetooth keyboard and mouse at the same time. Only one device worked, either keyboard and mouse.  Other reported that Bluetooth keyboard and mouse work with Logitech devices:

https://forum.pine64.org/showthread.php?...316&page=3

But Logitech has not mini keyboards. The Rii mini 4 is a mini keyboard with dual mode BLE and 2.4 Ghz dongle. I did not get to work the 2.4 Ghz dongle, but the keyboard with touchpad.

The Rii 4 over Bluetooth is the best experience for a Pinephone keyboard for me personally to this date. It is available and worked for 3 min. reliably. And it has also a layout with many keys, similar to the Pinephone keyboard which makes it  a great device. The keyboard is not much bigger than the Pinephone, and fit’s in a pocket.



.jpeg   proxy-iasdfasfasdfasdfmage.jpeg (Size: 27.02 KB / Downloads: 412)
]]> <![CDATA[How to get the Rii 4 with 2.4 Ghz get to work with the PP]]> https://forum.pine64.org/showthread.php?tid=19350 Thu, 18 Jul 2024 14:22:34 +0000 Peter Gamma]]> https://forum.pine64.org/showthread.php?tid=19350
This keyboard is one of the most interesting keyboards for the Pinephone for me personally if it works.

I suppose it is with lesser issues than Bluetooth

But it was not possible to pair the keyboard to the dongle as described above.

Then I tried to use a usb keyboard and mouse.

Here are examples which show that this works with the PP:

https://petergamma.org/how-to-get-a-usb-...pinephone/

All of these examples use a usb-c dock

And here is a list of 3.th party docks which work with the Pinephone and keyboard and mouse:

https://petergamma.org/issues-with-four-...epone-pro/

I tested previously 3 cheap usb docks I bought on Aliexpress.

HDMI out worked with none of them.

keyboard and mouse worked with one of those, but I could not reproduce it today

usb-c adapters are tricky  Sometimes I need to turn those around to get it to work.

I recently saw that is possible to read and write to an usb flash drive with an Android phone:

https://petergamma.org/the-problem-googl...oid-phone/

But it needs to be an OTG drive, and the right configuration in Android.

Do you have experience with these kind of adapters?

Does it need to be an OTG adapter for keyboard and mouse?

And does it need to be powered?]]>
This keyboard is one of the most interesting keyboards for the Pinephone for me personally if it works.

I suppose it is with lesser issues than Bluetooth

But it was not possible to pair the keyboard to the dongle as described above.

Then I tried to use a usb keyboard and mouse.

Here are examples which show that this works with the PP:

https://petergamma.org/how-to-get-a-usb-...pinephone/

All of these examples use a usb-c dock

And here is a list of 3.th party docks which work with the Pinephone and keyboard and mouse:

https://petergamma.org/issues-with-four-...epone-pro/

I tested previously 3 cheap usb docks I bought on Aliexpress.

HDMI out worked with none of them.

keyboard and mouse worked with one of those, but I could not reproduce it today

usb-c adapters are tricky  Sometimes I need to turn those around to get it to work.

I recently saw that is possible to read and write to an usb flash drive with an Android phone:

https://petergamma.org/the-problem-googl...oid-phone/

But it needs to be an OTG drive, and the right configuration in Android.

Do you have experience with these kind of adapters?

Does it need to be an OTG adapter for keyboard and mouse?

And does it need to be powered?]]> <![CDATA[The Pinephone keyboard offers alternative layouts]]> https://forum.pine64.org/showthread.php?tid=19330 Thu, 04 Jul 2024 11:40:12 +0000 Peter Gamma]]> https://forum.pine64.org/showthread.php?tid=19330 - It has alternative layouts such as AZERTY or QWERTZ (Default).
- and a programmable open firmware by Megi

https://xnux.eu/log/044.html

https://pine64eu.com/product/pinephone-p...oard-case/

– so bring it back!]]> - It has alternative layouts such as AZERTY or QWERTZ (Default).
- and a programmable open firmware by Megi

https://xnux.eu/log/044.html

https://pine64eu.com/product/pinephone-p...oard-case/

– so bring it back!]]> <![CDATA[Bring the Pinephone keyboard back, it is worth it!]]> https://forum.pine64.org/showthread.php?tid=19329 Thu, 04 Jul 2024 05:37:58 +0000 Peter Gamma]]> https://forum.pine64.org/showthread.php?tid=19329
And know I found that the Pinephone is almost daily driver ready for writers after many years. Look at the wonderful possibilities the Pinephone has for writers:

https://petergamma.org/selected-office-a...-zero-2-w/

There are other devices availble for office mobile, but what is special about the Pinephone is it’s hard wired keyboard. This makes it to a robust device.

The Pinephone keyboard has issues, but one can work with. And the issues are known. And eventually someone makes an updated version.

There are 121 pages in the Pine64 forum about the Pinephone since 10-17-2019, 05:48 PM. This makes the Pinephone from a bad device to a good device.

There are other devices out there which are better for the one or the other application. But we need to build these device first. And who wants to do that now that the Pinephone has become a good device for writers, and there is no need to build a new device?

If you care for a special Pinephone distro and you  are a skilled coder, please put Word 97 in your app store if this is possible. Jackfish has put the instruction here:

https://forum.pine64.org/showthread.php?tid=18489

I will not use Word 97 on my Pinephone. It easier for me personally to use it only with Abiword and change to another device which offers LibreOffice without issues. But Word 97 in an app store of the Pinephone would be a reason to come back to the Pinephone.

With the Pinephone keyboard and Word 97 the Pinephone is a good daily driver for writers, and also worth stealing for the thieves in Zurich. Since even if you have a lot of money it is difficult to find a better device for writers which makes the Pinephone worth stealing.]]>
And know I found that the Pinephone is almost daily driver ready for writers after many years. Look at the wonderful possibilities the Pinephone has for writers:

https://petergamma.org/selected-office-a...-zero-2-w/

There are other devices availble for office mobile, but what is special about the Pinephone is it’s hard wired keyboard. This makes it to a robust device.

The Pinephone keyboard has issues, but one can work with. And the issues are known. And eventually someone makes an updated version.

There are 121 pages in the Pine64 forum about the Pinephone since 10-17-2019, 05:48 PM. This makes the Pinephone from a bad device to a good device.

There are other devices out there which are better for the one or the other application. But we need to build these device first. And who wants to do that now that the Pinephone has become a good device for writers, and there is no need to build a new device?

If you care for a special Pinephone distro and you  are a skilled coder, please put Word 97 in your app store if this is possible. Jackfish has put the instruction here:

https://forum.pine64.org/showthread.php?tid=18489

I will not use Word 97 on my Pinephone. It easier for me personally to use it only with Abiword and change to another device which offers LibreOffice without issues. But Word 97 in an app store of the Pinephone would be a reason to come back to the Pinephone.

With the Pinephone keyboard and Word 97 the Pinephone is a good daily driver for writers, and also worth stealing for the thieves in Zurich. Since even if you have a lot of money it is difficult to find a better device for writers which makes the Pinephone worth stealing.]]> <![CDATA[Keyboard & 2.4G usb dongle for the Pinephone?]]> https://forum.pine64.org/showthread.php?tid=19317 Sat, 29 Jun 2024 13:10:03 +0000 Peter Gamma]]> https://forum.pine64.org/showthread.php?tid=19317
https://youtu.be/5cIqwIye2Q0

But small usb keyboards for mobile use are hard to find. I only found one from Poland from which I do not know if it is still avaiable.

A device which is also known to have issues with Bluetooth peripherials is the Orange Pi 5.

https://youtu.be/cBqV4QWj0lE

Crosstalk solution shows a kit especially for the Orange Pi 5. on YouTube:

https://kit.co/crosstalk/orange-pi-5

It shows a wireless dual mode Bluetooth Rii (Upgrade) i4 Mini Bluetooth Keyboard with Touchpad, Blacklit Portable Wireless Keyboard with 2.4G USB Dongle for Smartphones, PC, Table:

https://www.amazon.com/Rii-Bluetooth-Key...B07T13GLY3

Should a keyboard with a 2.4G USB dongle which is included with the mini keyboard not work as a USB keyboard?]]>
https://youtu.be/5cIqwIye2Q0

But small usb keyboards for mobile use are hard to find. I only found one from Poland from which I do not know if it is still avaiable.

A device which is also known to have issues with Bluetooth peripherials is the Orange Pi 5.

https://youtu.be/cBqV4QWj0lE

Crosstalk solution shows a kit especially for the Orange Pi 5. on YouTube:

https://kit.co/crosstalk/orange-pi-5

It shows a wireless dual mode Bluetooth Rii (Upgrade) i4 Mini Bluetooth Keyboard with Touchpad, Blacklit Portable Wireless Keyboard with 2.4G USB Dongle for Smartphones, PC, Table:

https://www.amazon.com/Rii-Bluetooth-Key...B07T13GLY3

Should a keyboard with a 2.4G USB dongle which is included with the mini keyboard not work as a USB keyboard?]]> <![CDATA[So which keyboard you suggest for the Pinephone?]]> https://forum.pine64.org/showthread.php?tid=19316 Sat, 29 Jun 2024 11:04:37 +0000 Peter Gamma]]> https://forum.pine64.org/showthread.php?tid=19316
https://petergamma.org/selected-office-a...-zero-2-w/

But now that I found that it is device which is suitable for this purpose, the Pinephone keyboard has been pulled from the Pine 64 store. The only keyboard I know which has been confirmed to work by wibble is the 10 year oldGo Stowaway Ultra-Slim Bluetooth Keyboard for BlackBerry and Other PDA/Handhelds:

https://www.amazon.ca/Igo-Stowaway-Ultra...B0002OKCXE

But who wants to fold up the keyboard every time he writes a text? It sould in principle be possible to solder a keyboard to the POGO pins of the Pinephone. But small wired keyboards are very difficult to find. And the developers of the Pinephone Keyboard have already solved this problem.
And now it is not avaible again. What a pity.

All my hard work for the Pinephone in vain, such as install LibreOffice and reviewing it on my site for mobile office:

https://petergamma.org/category/mobile-office/

Since editing text on the Pinephone without a handy keyboard does not make any sense for me personally. So which keyboard you suggest to use?]]>
https://petergamma.org/selected-office-a...-zero-2-w/

But now that I found that it is device which is suitable for this purpose, the Pinephone keyboard has been pulled from the Pine 64 store. The only keyboard I know which has been confirmed to work by wibble is the 10 year oldGo Stowaway Ultra-Slim Bluetooth Keyboard for BlackBerry and Other PDA/Handhelds:

https://www.amazon.ca/Igo-Stowaway-Ultra...B0002OKCXE

But who wants to fold up the keyboard every time he writes a text? It sould in principle be possible to solder a keyboard to the POGO pins of the Pinephone. But small wired keyboards are very difficult to find. And the developers of the Pinephone Keyboard have already solved this problem.
And now it is not avaible again. What a pity.

All my hard work for the Pinephone in vain, such as install LibreOffice and reviewing it on my site for mobile office:

https://petergamma.org/category/mobile-office/

Since editing text on the Pinephone without a handy keyboard does not make any sense for me personally. So which keyboard you suggest to use?]]> <![CDATA[Swiss German layout on PP keyb. with «ä» & «ü»?]]> https://forum.pine64.org/showthread.php?tid=19305 Wed, 19 Jun 2024 02:32:40 +0000 Peter Gamma]]> https://forum.pine64.org/showthread.php?tid=19305
- I have installed postmarketOS on my Pinephone.

- postmarketOS only supports English and Czech

https://en.wikipedia.org/wiki/PostmarketOS

- Here is the discussion how to update the PinePhone keyboard driver to support missing characters:

https://forum.pine64.org/showthread.php?tid=16750

- Is it still possible to add charakters such as «ä» or «ü» to the Pinephone keys so that if i use for instance Abiword that I can use it for writing in Swiss German which requires «ä» and «ü»?]]>
- I have installed postmarketOS on my Pinephone.

- postmarketOS only supports English and Czech

https://en.wikipedia.org/wiki/PostmarketOS

- Here is the discussion how to update the PinePhone keyboard driver to support missing characters:

https://forum.pine64.org/showthread.php?tid=16750

- Is it still possible to add charakters such as «ä» or «ü» to the Pinephone keys so that if i use for instance Abiword that I can use it for writing in Swiss German which requires «ä» and «ü»?]]> <![CDATA[Was someone able to use the Pinephone keyboard & an usb mouse at the same?]]> https://forum.pine64.org/showthread.php?tid=19304 Tue, 18 Jun 2024 20:48:55 +0000 Peter Gamma]]> https://forum.pine64.org/showthread.php?tid=19304
- So the only way to go for me personally is a usb mouse

- But was someone able to get a usb mouse to get to work simultaneously with the Pinephone keyboard?

- What is shown in the following discussion shows only:

https://petergamma.org/how-to-get-a-usb-...pinephone/

- 1. A Pinephone with a Pinephone dock and a keyboard which as a trackpad which works.

- 2. A Pinephone with a Pinephone keyboard and a docking bar which shows that both external keyboard and mouse work, but not the the Pinephone keyboard.

- What would be interesting to know if someone confirms that the Pinephone works with an external usb mouse simultaneously.

- Can someone confirm this?]]>
- So the only way to go for me personally is a usb mouse

- But was someone able to get a usb mouse to get to work simultaneously with the Pinephone keyboard?

- What is shown in the following discussion shows only:

https://petergamma.org/how-to-get-a-usb-...pinephone/

- 1. A Pinephone with a Pinephone dock and a keyboard which as a trackpad which works.

- 2. A Pinephone with a Pinephone keyboard and a docking bar which shows that both external keyboard and mouse work, but not the the Pinephone keyboard.

- What would be interesting to know if someone confirms that the Pinephone works with an external usb mouse simultaneously.

- Can someone confirm this?]]> <![CDATA[Troubleshooting Pinedio LoRa Add-on Case]]> https://forum.pine64.org/showthread.php?tid=19296 Sun, 16 Jun 2024 07:03:19 +0000 nickp]]> https://forum.pine64.org/showthread.php?tid=19296
I am trying to run meshtasticd on my Pinephone.
Suddenly tough, the received bytes of the SX1262 are all zero, and I never managed to get the standard 0xA2 answer back.
I2C communication works still, which is why I am suspecting that the radio chip is at fault.
Does anybody know what I was doing wrong or how to debug this?

Onto the details, I simply implemented an SPI device driver which translates to I2C such that mestasticd can communicate with it as if the ATTiny bridge isn't there.
The code for the kernel driver and a dmesg trace with debug output can be found here: https://gist.github.com/pectec/ffddf32ae...041bc92bbe

Any help on this is appreciated Smile

Thank you,
Nick

Edit: I managed to damage it, Pine64 says that there isn't going to be a production batch anytime soon.
My only option is DIY at this point (using a [url=https://www.amazon.de/dp/B0CSFG65MS?psc=1&ref=ppx_yo2ov_dt_b_product_details][/url]Waveshare RP2040), which I'll do when I come around to it, so I'll mark this issue as solved.]]>
I am trying to run meshtasticd on my Pinephone.
Suddenly tough, the received bytes of the SX1262 are all zero, and I never managed to get the standard 0xA2 answer back.
I2C communication works still, which is why I am suspecting that the radio chip is at fault.
Does anybody know what I was doing wrong or how to debug this?

Onto the details, I simply implemented an SPI device driver which translates to I2C such that mestasticd can communicate with it as if the ATTiny bridge isn't there.
The code for the kernel driver and a dmesg trace with debug output can be found here: https://gist.github.com/pectec/ffddf32ae...041bc92bbe

Any help on this is appreciated Smile

Thank you,
Nick

Edit: I managed to damage it, Pine64 says that there isn't going to be a production batch anytime soon.
My only option is DIY at this point (using a [url=https://www.amazon.de/dp/B0CSFG65MS?psc=1&ref=ppx_yo2ov_dt_b_product_details][/url]Waveshare RP2040), which I'll do when I come around to it, so I'll mark this issue as solved.]]> <![CDATA[Slip/Zippered Case for PP/KB?]]> https://forum.pine64.org/showthread.php?tid=19116 Sun, 03 Mar 2024 22:55:34 +0000 jakfish]]> https://forum.pine64.org/showthread.php?tid=19116 <![CDATA[Keyboard doesn't charge my phone no matter what, so can I charge my phone directly]]> https://forum.pine64.org/showthread.php?tid=19003 Tue, 09 Jan 2024 15:05:36 +0000 ragreenburg]]> https://forum.pine64.org/showthread.php?tid=19003
I can check the keyboard battery with UPower and it shows 100% but no matter how good/bad of a charger I connect to it, the power never gets to my phone. The good news is, I can type on it though. 

So my question is, since there is no working connection to the charging chip, would it be safe to charge the phone directly while it is connected to the keyboard?]]>
I can check the keyboard battery with UPower and it shows 100% but no matter how good/bad of a charger I connect to it, the power never gets to my phone. The good news is, I can type on it though. 

So my question is, since there is no working connection to the charging chip, would it be safe to charge the phone directly while it is connected to the keyboard?]]>