<![CDATA[PINE64 - All Forums]]> https://forum.pine64.org/ Fri, 10 Apr 2026 09:15:31 +0000 MyBB <![CDATA[Looking for engineer for customized project MVP based on PPP]]> https://forum.pine64.org/showthread.php?tid=20251 Mon, 06 Apr 2026 14:44:41 +0000 Andrey_voce]]> https://forum.pine64.org/showthread.php?tid=20251 <![CDATA[Finally got Kali working on my Pinebook Pro!]]> https://forum.pine64.org/showthread.php?tid=20244 Sat, 04 Apr 2026 14:00:51 +0000 qingss0]]> https://forum.pine64.org/showthread.php?tid=20244         I bought a crashed second-hand Pinebook Pro for a rock-bottom price.After some thinking and several attempts, I finally managed to get Kali Linux up and running properly on my Pinebook Pro.

What worked for me:
  • Switched to USTC (University of Science and Technology of China) mirrors
  • Used a command to bypass the command-not-found hook error.
        Feels great to see  apt-update  complete without segmentation faults or decompression errors. The Pinebook Pro is finally usable with Kali!]]>         I bought a crashed second-hand Pinebook Pro for a rock-bottom price.After some thinking and several attempts, I finally managed to get Kali Linux up and running properly on my Pinebook Pro.

What worked for me:
  • Switched to USTC (University of Science and Technology of China) mirrors
  • Used a command to bypass the command-not-found hook error.
        Feels great to see  apt-update  complete without segmentation faults or decompression errors. The Pinebook Pro is finally usable with Kali!]]> <![CDATA[Charging problem]]> https://forum.pine64.org/showthread.php?tid=20243 Sat, 04 Apr 2026 13:30:31 +0000 RicTor]]> https://forum.pine64.org/showthread.php?tid=20243
I have been investigating and think I have found what  is happening - hence how to trigger charging. But I don't know why! 

Anyone else have the problem?

Are there any experts here who know the power / charging system? I can use help understanding the  schematic...]]>
I have been investigating and think I have found what  is happening - hence how to trigger charging. But I don't know why! 

Anyone else have the problem?

Are there any experts here who know the power / charging system? I can use help understanding the  schematic...]]> <![CDATA[Updates have gotten me excited again]]> https://forum.pine64.org/showthread.php?tid=20237 Thu, 02 Apr 2026 23:16:51 +0000 bills2002]]> https://forum.pine64.org/showthread.php?tid=20237
Anyway with the latest update...Im finding it very useable.
- Liferea for RSS feeds.  Read the news, 3 pane window landscape...very functional.  Cant remember how I imported them but have 100s of feeds.  Update all takes about 5 minutes and then there is more articles than I can consume.
- KOreader with OPDS / Project Gutenberg gets me tons of reading material.
- Xournal++ for notes and drawings

Set the screen mode to BW:1 (or dither) and turn off automatic screen updates.  No flashing, smooth scrolling, clear as day.

Still wish:
- X11 was available for more panel options.
- faster writing response in Xournal++
- Some form of Libby / overdrive for checking out books from libraries.

Just wanted to say that it is beoming a daily need now.

Fingers crossed for a PineNote 2 with more cores, more mem, expandable storage.

Bill]]>
Anyway with the latest update...Im finding it very useable.
- Liferea for RSS feeds.  Read the news, 3 pane window landscape...very functional.  Cant remember how I imported them but have 100s of feeds.  Update all takes about 5 minutes and then there is more articles than I can consume.
- KOreader with OPDS / Project Gutenberg gets me tons of reading material.
- Xournal++ for notes and drawings

Set the screen mode to BW:1 (or dither) and turn off automatic screen updates.  No flashing, smooth scrolling, clear as day.

Still wish:
- X11 was available for more panel options.
- faster writing response in Xournal++
- Some form of Libby / overdrive for checking out books from libraries.

Just wanted to say that it is beoming a daily need now.

Fingers crossed for a PineNote 2 with more cores, more mem, expandable storage.

Bill]]> <![CDATA[Voidlinux working on eMMC]]> https://forum.pine64.org/showthread.php?tid=20234 Mon, 30 Mar 2026 23:07:35 +0000 cheepeero]]> https://forum.pine64.org/showthread.php?tid=20234
I have decided to try out Voidlinux on my Pinetab2, replacing the factory Archlinux I had installed until now. When I finished, I found that the same Plasma 6 desktop is much more responsive, with a significantly lower memory footprint. Maybe this is due to musl vs glibc, but it also might be that I have missed some memory-intensive services. Also note that I am using my old Archlinux home folder on the new Voidlinux system, and everything works.


So, here is my experience with this migration. I hope it will help others that want to migrate or try Voidlinux, so you can avoid bricking the Pinetab2 in the process, like I did.


First, I followed the installation instructions on the Pinetab2 releases page, which wrongly state that the Voidlinux image there is suitable both for the SD card and for the eMMC. The SD card worked, but flashing the eMMC bricked the device, so I had to revive it using the UART debugger. Do not do that!

The resources I needed are as follows:

If you follow my steps, and skip step 2, you won't need this, but it was handy for me:

Below are the steps I took. If you follow this, SKIP STEP 2!

0. On the Pinetab2 I had the danctnix preinstalled factory image, which I used productively since I first received the device. At this step, I backed up my files using dd, and migrated my LVM home onto a separate HDD via USB.
1. I flashed Voidlinux as instructed in the Pinetab Software Releases page onto an SD card, and it booted just fine. I did not require the UART device.
2. DO NOT DO THIS STEP! It is here for informative purposes only: I flashed the same Voidlinux SD card image onto eMMC, as instructed by the Wiki page, which bricked the pinetab. So, again, DO NOT DO THIS.
    - I recovered with the UART (https://pine64.org/documentation/PineTab...s_and_FAQ/ - Recovery from non-booting device) and installed a fresh danctnix Archlinux factory image.
    - Note to maintainers: please remove the faulty instruction from the Wiki page, or, alternatively, clarify how to flash Voidlinux to the eMMC.
3. After the blunder above, I rebooted into the Voidlinux SD card install, and I left the eMMC mmcblk0p1 unchanged (the boot partition, with danctnix u-boot and the kernel), but recreated and formatted the root partition, mmcblk0p2, with an empty ext4 filesystem.
4. From the SD card I followed the instructions on chroot install from Voidlinux handbook (https://docs.voidlinux.org/installation/...hroot.html), with the following notes:
    - mounted /dev/mmcblk0p2 as /mnt, next /dev/mmcblk0p1 as /mnt/boot. There is no need for an EFI partition.
    - I used `ARCH=aarch64-musl` and the repo URL `REPO=https://repo-default.voidlinux.org/current/aarch64/`
    - after copying the xbps keys and running the chroot install, remember to skip the rootfs tarball method, but continue with generating fstab and setting a root password
    - also skip stuff related to GRUB and EFI
    - as a side note, the section about Pinebook Pro does not apply at all to Pinetab2
5. I jumped to the Voidlinux-pinetab2 readme on github, and installed all the packages mentioned there. I did not have the files downloaded on SD card, so had to configure the network at this step, but one can prepare the files beforehand, after flashing the Voidlinux SD card.
    - the imageramfs step did not work - out of disk space on boot partition, but the system boots and works fine without it
    - the u-boot boot.scr needed to be regenerated. The xbps-install output provides necessary instructions on-screen
6. Unmounted /mnt/boot and /mnt, sync and next poweroff, remove SD card, power on from button, and Voidlinux booted from eMMC successfully into the text console.
7. As root, started following the Voidlinux handbook guide on how to configure the system (lvm, sddm, wayland, xdg portals, cron etc). Finally, I configured my non-root user, after installing and testing SDDM and KDE, I moved back the LVM home volume from the external HDD, and all worked out well. (Note that I still had the dd backup of the LVM volume, just in case)

At this stage I still have Voidlinux-related stuff to fix, but the base system and KDE/Plasma works.]]>
I have decided to try out Voidlinux on my Pinetab2, replacing the factory Archlinux I had installed until now. When I finished, I found that the same Plasma 6 desktop is much more responsive, with a significantly lower memory footprint. Maybe this is due to musl vs glibc, but it also might be that I have missed some memory-intensive services. Also note that I am using my old Archlinux home folder on the new Voidlinux system, and everything works.


So, here is my experience with this migration. I hope it will help others that want to migrate or try Voidlinux, so you can avoid bricking the Pinetab2 in the process, like I did.


First, I followed the installation instructions on the Pinetab2 releases page, which wrongly state that the Voidlinux image there is suitable both for the SD card and for the eMMC. The SD card worked, but flashing the eMMC bricked the device, so I had to revive it using the UART debugger. Do not do that!

The resources I needed are as follows:

If you follow my steps, and skip step 2, you won't need this, but it was handy for me:

Below are the steps I took. If you follow this, SKIP STEP 2!

0. On the Pinetab2 I had the danctnix preinstalled factory image, which I used productively since I first received the device. At this step, I backed up my files using dd, and migrated my LVM home onto a separate HDD via USB.
1. I flashed Voidlinux as instructed in the Pinetab Software Releases page onto an SD card, and it booted just fine. I did not require the UART device.
2. DO NOT DO THIS STEP! It is here for informative purposes only: I flashed the same Voidlinux SD card image onto eMMC, as instructed by the Wiki page, which bricked the pinetab. So, again, DO NOT DO THIS.
    - I recovered with the UART (https://pine64.org/documentation/PineTab...s_and_FAQ/ - Recovery from non-booting device) and installed a fresh danctnix Archlinux factory image.
    - Note to maintainers: please remove the faulty instruction from the Wiki page, or, alternatively, clarify how to flash Voidlinux to the eMMC.
3. After the blunder above, I rebooted into the Voidlinux SD card install, and I left the eMMC mmcblk0p1 unchanged (the boot partition, with danctnix u-boot and the kernel), but recreated and formatted the root partition, mmcblk0p2, with an empty ext4 filesystem.
4. From the SD card I followed the instructions on chroot install from Voidlinux handbook (https://docs.voidlinux.org/installation/...hroot.html), with the following notes:
    - mounted /dev/mmcblk0p2 as /mnt, next /dev/mmcblk0p1 as /mnt/boot. There is no need for an EFI partition.
    - I used `ARCH=aarch64-musl` and the repo URL `REPO=https://repo-default.voidlinux.org/current/aarch64/`
    - after copying the xbps keys and running the chroot install, remember to skip the rootfs tarball method, but continue with generating fstab and setting a root password
    - also skip stuff related to GRUB and EFI
    - as a side note, the section about Pinebook Pro does not apply at all to Pinetab2
5. I jumped to the Voidlinux-pinetab2 readme on github, and installed all the packages mentioned there. I did not have the files downloaded on SD card, so had to configure the network at this step, but one can prepare the files beforehand, after flashing the Voidlinux SD card.
    - the imageramfs step did not work - out of disk space on boot partition, but the system boots and works fine without it
    - the u-boot boot.scr needed to be regenerated. The xbps-install output provides necessary instructions on-screen
6. Unmounted /mnt/boot and /mnt, sync and next poweroff, remove SD card, power on from button, and Voidlinux booted from eMMC successfully into the text console.
7. As root, started following the Voidlinux handbook guide on how to configure the system (lvm, sddm, wayland, xdg portals, cron etc). Finally, I configured my non-root user, after installing and testing SDDM and KDE, I moved back the LVM home volume from the external HDD, and all worked out well. (Note that I still had the dd backup of the LVM volume, just in case)

At this stage I still have Voidlinux-related stuff to fix, but the base system and KDE/Plasma works.]]> <![CDATA[A/V output enable]]> https://forum.pine64.org/showthread.php?tid=20227 Tue, 24 Mar 2026 22:45:39 +0000 8lall0]]> https://forum.pine64.org/showthread.php?tid=20227 Hello everyone!

I have a Rock64, but i cannot get the A/V jack to output video.

Do you have any hints?

Thanks!]]> Hello everyone!

I have a Rock64, but i cannot get the A/V jack to output video.

Do you have any hints?

Thanks!]]> <![CDATA[If your USB-C port is flakey...]]> https://forum.pine64.org/showthread.php?tid=20226 Tue, 24 Mar 2026 20:25:41 +0000 Zebulon Walton]]> https://forum.pine64.org/showthread.php?tid=20226
I do have a spare USB board but before doing surgery on the phone I sprayed some DeoxIT contact cleaner into the port and plugged/unplugged a USB cable several times. After doing this the port is working fine! Even directly wiggling the connector doesn't break the connection.

The Pinephone's USB port is open to dirt and debris and over the years apparently enough got in there to affect the connection. So if you're having problems with your USB connection this is something to try before swapping out the board.

*** EDIT *** Oops, I meant to post this in the regular Pinephone board, not the Pro board! Though I expect this info applies to both models.]]>
I do have a spare USB board but before doing surgery on the phone I sprayed some DeoxIT contact cleaner into the port and plugged/unplugged a USB cable several times. After doing this the port is working fine! Even directly wiggling the connector doesn't break the connection.

The Pinephone's USB port is open to dirt and debris and over the years apparently enough got in there to affect the connection. So if you're having problems with your USB connection this is something to try before swapping out the board.

*** EDIT *** Oops, I meant to post this in the regular Pinephone board, not the Pro board! Though I expect this info applies to both models.]]> <![CDATA[Pine a64+ power supply]]> https://forum.pine64.org/showthread.php?tid=20223 Wed, 18 Mar 2026 07:02:55 +0000 davidspencer]]> https://forum.pine64.org/showthread.php?tid=20223 I’m new here. A friend gave me his old Pine A64+ that I want to use to run a program for my 3D printer. I’ve run into some problems and narrowed them down to a few possibilities, one of which is the power supply. What do you all use for your Pine A64+ boards?

Right now I’m using a USB cable from an old 5 V phone charger plugged into a cheap surge‑protected power strip. Is that okay, or do I need a more stable or controlled power source?]]> I’m new here. A friend gave me his old Pine A64+ that I want to use to run a program for my 3D printer. I’ve run into some problems and narrowed them down to a few possibilities, one of which is the power supply. What do you all use for your Pine A64+ boards?

Right now I’m using a USB cable from an old 5 V phone charger plugged into a cheap surge‑protected power strip. Is that okay, or do I need a more stable or controlled power source?]]> <![CDATA[Prohibit Pinecil from going nuclear]]> https://forum.pine64.org/showthread.php?tid=20216 Thu, 12 Mar 2026 13:30:25 +0000 snorkel]]> https://forum.pine64.org/showthread.php?tid=20216 It works just fine! Most of the time...

Then and again it goes into nuclear mode, I see it tries to run 450C or something like it.
After that the tip is toast.

Now, tips are'nt directly cheap and I consider this to be a manufacturing problem.
But you all know the drill..

What I want to know, does anybody else have this problem?
I saw some weird setting regarding high temperature, nothing I could turn off as far as I understodd.

Please help, before I run out of tips..

  /Snorkel]]> It works just fine! Most of the time...

Then and again it goes into nuclear mode, I see it tries to run 450C or something like it.
After that the tip is toast.

Now, tips are'nt directly cheap and I consider this to be a manufacturing problem.
But you all know the drill..

What I want to know, does anybody else have this problem?
I saw some weird setting regarding high temperature, nothing I could turn off as far as I understodd.

Please help, before I run out of tips..

  /Snorkel]]> <![CDATA[Looking for PineTime users to test an Android app with BLE heart rate support]]> https://forum.pine64.org/showthread.php?tid=20215 Wed, 11 Mar 2026 17:42:20 +0000 Mitrax]]> https://forum.pine64.org/showthread.php?tid=20215
I'm currently developing a small Android app called Dormivox.

The Bluetooth feature was mainly designed with the Pine watch in mind – mostly because I like the project.

Current features:
• Live noise level detection
• Alarm to interrupt snoring
• Night statistics and history
• Playback of recorded audio segments
• Optional Bluetooth heart rate input (BLE)

I'm particularly interested in testing Bluetooth heart rate devices with open BLE support (for example PineTime or other BLE HR monitors).

If anyone here would like to try it and give some feedback, that would be very helpful.

You can find the app on the Play Store by searching for: Dormivox

Thanks!
Mitrax


.jpg   dormivox_audio_graph_600.jpg (Size: 66.49 KB / Downloads: 80) ]]>
I'm currently developing a small Android app called Dormivox.

The Bluetooth feature was mainly designed with the Pine watch in mind – mostly because I like the project.

Current features:
• Live noise level detection
• Alarm to interrupt snoring
• Night statistics and history
• Playback of recorded audio segments
• Optional Bluetooth heart rate input (BLE)

I'm particularly interested in testing Bluetooth heart rate devices with open BLE support (for example PineTime or other BLE HR monitors).

If anyone here would like to try it and give some feedback, that would be very helpful.

You can find the app on the Play Store by searching for: Dormivox

Thanks!
Mitrax


.jpg   dormivox_audio_graph_600.jpg (Size: 66.49 KB / Downloads: 80) ]]> <![CDATA[US Tariffs & Recent Supreme Court Decision]]> https://forum.pine64.org/showthread.php?tid=20209 Mon, 09 Mar 2026 15:46:33 +0000 recursivenomad]]> https://forum.pine64.org/showthread.php?tid=20209
I see that making a purchase to the US is still charging the full $25 shipping, noting coverage for tariffs, and the amount has not changed since the US Supreme Court decision to suspend specific tariffs in February.  I just wanted to ask if there are any plans to update this cost to reflect the new tariff situation, or if this cost is expected to remain the same?

Thank you for developing and selling awesome open-source hardware Smile]]>
I see that making a purchase to the US is still charging the full $25 shipping, noting coverage for tariffs, and the amount has not changed since the US Supreme Court decision to suspend specific tariffs in February.  I just wanted to ask if there are any plans to update this cost to reflect the new tariff situation, or if this cost is expected to remain the same?

Thank you for developing and selling awesome open-source hardware Smile]]> <![CDATA[Question About New Product Releases]]> https://forum.pine64.org/showthread.php?tid=20208 Sat, 07 Mar 2026 07:17:44 +0000 kulala]]> https://forum.pine64.org/showthread.php?tid=20208 ]]> ]]> <![CDATA[Pinecil v2: Use car battery for power?]]> https://forum.pine64.org/showthread.php?tid=20204 Mon, 02 Mar 2026 15:56:01 +0000 FZB]]> https://forum.pine64.org/showthread.php?tid=20204 <![CDATA[RISC OS Linux port]]> https://forum.pine64.org/showthread.php?tid=20203 Thu, 26 Feb 2026 11:40:56 +0000 Raik]]> https://forum.pine64.org/showthread.php?tid=20203
[Image: ROS_PineTab2.jpg]

You can download from PyraDirect . The collection I have made for the Pyra handheld based on ROD's PiDirect but works fine on PineTab.

It need base-devel as dependencies (e.g. sudo pacman -Sy base-devel)

Unpack the download in Terminal with

tar —xattrs -xvf Downloads/pyra_direct.tar.gz

to your home directory. It takes a while.

Then in Terminal…

Dir RISC_OS

./run_RISC_OS

The first start takes a bit longer.]]>
[Image: ROS_PineTab2.jpg]

You can download from PyraDirect . The collection I have made for the Pyra handheld based on ROD's PiDirect but works fine on PineTab.

It need base-devel as dependencies (e.g. sudo pacman -Sy base-devel)

Unpack the download in Terminal with

tar —xattrs -xvf Downloads/pyra_direct.tar.gz

to your home directory. It takes a while.

Then in Terminal…

Dir RISC_OS

./run_RISC_OS

The first start takes a bit longer.]]> <![CDATA[Systemupgrade fails]]> https://forum.pine64.org/showthread.php?tid=20202 Thu, 26 Feb 2026 05:15:53 +0000 Raik]]> https://forum.pine64.org/showthread.php?tid=20202 With CTRL+ALT+F2 I can enter the Terminal. My account is working but no network and "startx" fails.

I have try to install the available actualization in discovery and later, after a "factory reset", in terminal "sudo pacman -Syu". All the same.
After the actualization e.g. freecad, musescore are working (before only installing possible) but after a restart... next "factory reset".

Any ideas?]]> With CTRL+ALT+F2 I can enter the Terminal. My account is working but no network and "startx" fails.

I have try to install the available actualization in discovery and later, after a "factory reset", in terminal "sudo pacman -Syu". All the same.
After the actualization e.g. freecad, musescore are working (before only installing possible) but after a restart... next "factory reset".

Any ideas?]]>