<![CDATA[PINE64 - All Forums]]> https://forum.pine64.org/ Thu, 04 Jun 2026 01:30:40 +0000 MyBB <![CDATA[Free HTML5 Games – Simple Browser Games on CPSGames]]> https://forum.pine64.org/showthread.php?tid=20283 Wed, 03 Jun 2026 07:33:06 +0000 Robin C Sikorski]]> https://forum.pine64.org/showthread.php?tid=20283
I wanted to share a browser gaming site I've been using for quick, casual gaming sessions. It's called CPSGames.org and it has a collection of free HTML5 games that don't require any downloads.

Some popular games they have include:

Penalty Shootout Multi League

Google Doodle Baseball

Bottle Flip

Fireboy and Watergirl 6

Google Snake

Smash Karts

Tag

Geometry Dash

The site is good for short breaks, quick gameplay, and casual fun without overcomplicating things. Everything works directly in your browser and it's free to play.

If you're into browser games or looking for something light to play between work or study, it might be worth checking out.

Link: https://cpsgames.org/

What browser games do you all recommend?]]>
I wanted to share a browser gaming site I've been using for quick, casual gaming sessions. It's called CPSGames.org and it has a collection of free HTML5 games that don't require any downloads.

Some popular games they have include:

Penalty Shootout Multi League

Google Doodle Baseball

Bottle Flip

Fireboy and Watergirl 6

Google Snake

Smash Karts

Tag

Geometry Dash

The site is good for short breaks, quick gameplay, and casual fun without overcomplicating things. Everything works directly in your browser and it's free to play.

If you're into browser games or looking for something light to play between work or study, it might be worth checking out.

Link: https://cpsgames.org/

What browser games do you all recommend?]]> <![CDATA[Octordle – Who is the game for?]]> https://forum.pine64.org/showthread.php?tid=20282 Tue, 02 Jun 2026 16:26:42 +0000 elonlilx54]]> https://forum.pine64.org/showthread.php?tid=20282 In an increasingly diverse world of games, stands out as a unique intellectual game for those who love challenges and language sophistication. But is this game for everyone? Let's find out who octordle is really for!
Word and language game lovers
Octordle is not simply guessing words – you need to solve 8 English words at a time with only 13 guesses. If you like Wordle, Crossword or Scrabble, Octordle is an advanced version that is fun and challenging.
Students learning English
This game is a very natural and effective way to learn vocabulary. Instead of learning by rote from books, you will be able to apply English in real-life situations, practice reasoning skills and recognize vocabulary patterns – helping you remember faster and longer.
Logic and strategic thinking enthusiasts
Octordle not only requires vocabulary, but also the ability to observe, deduce and strategize. Those with strong logical thinking will find this game as attractive as a math problem that needs to be solved step by step.
Office workers need to "relax their brains" gently
Instead of surfing social networks aimlessly, playing a game of Octordle every day helps you relieve stress and refresh your mind. It doesn't take too much time, but it's still enough to stimulate the brain and bring a sense of conquest.
Those who love challenges and patience
Octordle is not an "easy" game. It requires patience, perseverance and a spirit of not giving up. If you are someone who likes to set goals and conquer them step by step, Octordle is the ideal playground.
Octordle is for everyone, very suitable for those who like to play smart. If you love languages, love exploring, or simply want to exercise your brain every day in a fun way, then don't hesitate to try Octordle right away!
]]> In an increasingly diverse world of games, stands out as a unique intellectual game for those who love challenges and language sophistication. But is this game for everyone? Let's find out who octordle is really for!
Word and language game lovers
Octordle is not simply guessing words – you need to solve 8 English words at a time with only 13 guesses. If you like Wordle, Crossword or Scrabble, Octordle is an advanced version that is fun and challenging.
Students learning English
This game is a very natural and effective way to learn vocabulary. Instead of learning by rote from books, you will be able to apply English in real-life situations, practice reasoning skills and recognize vocabulary patterns – helping you remember faster and longer.
Logic and strategic thinking enthusiasts
Octordle not only requires vocabulary, but also the ability to observe, deduce and strategize. Those with strong logical thinking will find this game as attractive as a math problem that needs to be solved step by step.
Office workers need to "relax their brains" gently
Instead of surfing social networks aimlessly, playing a game of Octordle every day helps you relieve stress and refresh your mind. It doesn't take too much time, but it's still enough to stimulate the brain and bring a sense of conquest.
Those who love challenges and patience
Octordle is not an "easy" game. It requires patience, perseverance and a spirit of not giving up. If you are someone who likes to set goals and conquer them step by step, Octordle is the ideal playground.
Octordle is for everyone, very suitable for those who like to play smart. If you love languages, love exploring, or simply want to exercise your brain every day in a fun way, then don't hesitate to try Octordle right away!
]]> <![CDATA[Avaota A1 - Mainline]]> https://forum.pine64.org/showthread.php?tid=20281 Mon, 01 Jun 2026 13:16:01 +0000 sam_uk]]> https://forum.pine64.org/showthread.php?tid=20281 https://pine64.com/product/yuzuki-avaota...-4gb-32gb/

Trying to get mainline on it: https://github.com/Agroecology-Lab/build

Running into issues with it https://github.com/Agroecology-Lab/build/issues/1

If anyone wants to play along or help that would be great]]> https://pine64.com/product/yuzuki-avaota...-4gb-32gb/

Trying to get mainline on it: https://github.com/Agroecology-Lab/build

Running into issues with it https://github.com/Agroecology-Lab/build/issues/1

If anyone wants to play along or help that would be great]]> <![CDATA[Totally disabling auto-boot when charger is plugged in?]]> https://forum.pine64.org/showthread.php?tid=20279 Sat, 30 May 2026 16:28:09 +0000 A Mnesia]]> https://forum.pine64.org/showthread.php?tid=20279
Is there any way to totally and completely disable this auto-boot behavior?

Thank you very much in advance.]]>
Is there any way to totally and completely disable this auto-boot behavior?

Thank you very much in advance.]]> <![CDATA[Pine a64 lcd]]> https://forum.pine64.org/showthread.php?tid=20277 Thu, 28 May 2026 07:12:48 +0000 shinzuka]]> https://forum.pine64.org/showthread.php?tid=20277 <![CDATA[RockPro64 automatically run after power recovery - my solution]]> https://forum.pine64.org/showthread.php?tid=20274 Mon, 25 May 2026 10:57:03 +0000 g2t]]> https://forum.pine64.org/showthread.php?tid=20274 Motivation
Since some years my system (Rockpro64 V2.1 2018-07-02) is not starting properly after a power loss, with increasing occurrence. It seems after some hours of power loss (e.g. over night) it is working more reliable, but when waiting only a few minutes this is not working anymore at all. Only the power button can be used for startup my system reliable.

In the forum there can be find a similar thread with some general information about the schematic and some measurements with a new system. Many thanks to for his investigations on a  new board. This was the base for my investigations and I solved it finally. I will describe my work step by step now, so others can repeat it and hopefully fix there system. If someone can give me an advice how to add/upload pictures, I will add my photos, so you can see what I have done.

Repeat the same measurement
"PMIC" is measured on C205 (right side) and "VCC5V0_SYS" is measured on C2006 (left side). Both can be found on top of the circuit board. The measurement results nearly equal the results from "Nikolay_Po" (the colours yellow and blue are interchanged in my measurement). So, perhaps, not the discrete components has changed its behavior but something inside RK808 changes over time. Or, the original values of the discrete components are chosen very close to the borders of the PMIC-system. No matter what it is, we can only change the discrete components - C204 catches my attention first.

Measure around and modify C204
The capacitor C204 can be found on the bottom of the circuit board (SD card slot at bottom left), in the area between C164 and C168, left of the resistor R89 and over the resistor R88. Another description: between the both big capacitor (C164 and C168) there are 4 small components in a flipped L-shape. C204 is the one in the corner of the "L".

The measurement was done with 2 channels, connected left and right of the C204 component. This means one is "VCC5V0_SYS" and the other one is the connection between C204, R89, D5 (soldered on the top side) and R88.

Try to increase the capacitor C204
Because it was working with a brand new board, most likely some aging process has changed the timings a bit. A second capacitor will increase the peak and the time a bit and maybe this can fix the problem. I added two connectors with wires left and right besides C204 and was able to add a second capacitor in parallel with an alligator clip.

1. choose 1uF --> working 100%
2. choose 100nF --> working 100%

Fix by soldering a SMD capacitor on top of C204
I disassembled some small SMD capacitors from a old circuit board and found one with around 150nF. This part I soldered on top of the C204 capacitor and this really fixed the problem for now.]]> Motivation
Since some years my system (Rockpro64 V2.1 2018-07-02) is not starting properly after a power loss, with increasing occurrence. It seems after some hours of power loss (e.g. over night) it is working more reliable, but when waiting only a few minutes this is not working anymore at all. Only the power button can be used for startup my system reliable.

In the forum there can be find a similar thread with some general information about the schematic and some measurements with a new system. Many thanks to for his investigations on a  new board. This was the base for my investigations and I solved it finally. I will describe my work step by step now, so others can repeat it and hopefully fix there system. If someone can give me an advice how to add/upload pictures, I will add my photos, so you can see what I have done.

Repeat the same measurement
"PMIC" is measured on C205 (right side) and "VCC5V0_SYS" is measured on C2006 (left side). Both can be found on top of the circuit board. The measurement results nearly equal the results from "Nikolay_Po" (the colours yellow and blue are interchanged in my measurement). So, perhaps, not the discrete components has changed its behavior but something inside RK808 changes over time. Or, the original values of the discrete components are chosen very close to the borders of the PMIC-system. No matter what it is, we can only change the discrete components - C204 catches my attention first.

Measure around and modify C204
The capacitor C204 can be found on the bottom of the circuit board (SD card slot at bottom left), in the area between C164 and C168, left of the resistor R89 and over the resistor R88. Another description: between the both big capacitor (C164 and C168) there are 4 small components in a flipped L-shape. C204 is the one in the corner of the "L".

The measurement was done with 2 channels, connected left and right of the C204 component. This means one is "VCC5V0_SYS" and the other one is the connection between C204, R89, D5 (soldered on the top side) and R88.

Try to increase the capacitor C204
Because it was working with a brand new board, most likely some aging process has changed the timings a bit. A second capacitor will increase the peak and the time a bit and maybe this can fix the problem. I added two connectors with wires left and right besides C204 and was able to add a second capacitor in parallel with an alligator clip.

1. choose 1uF --> working 100%
2. choose 100nF --> working 100%

Fix by soldering a SMD capacitor on top of C204
I disassembled some small SMD capacitors from a old circuit board and found one with around 150nF. This part I soldered on top of the C204 capacitor and this really fixed the problem for now.]]> <![CDATA[Power button not being ignored by init]]> https://forum.pine64.org/showthread.php?tid=20272 Sun, 17 May 2026 23:08:01 +0000 forestcreature]]> https://forum.pine64.org/showthread.php?tid=20272
What I'm expecting to happen is that it will work as bound to Return in sxmo menus, that it will wake from suspend, or turn on the display when off, etc. (as it was doing previously).

I guess that I am missing some config to tell init to ignore the power button. Can someone please let me know e.g. which package would set that up on the pinephone? I reckon I might have accidentally deleted something in the fix of a messed up apk world.]]>
What I'm expecting to happen is that it will work as bound to Return in sxmo menus, that it will wake from suspend, or turn on the display when off, etc. (as it was doing previously).

I guess that I am missing some config to tell init to ignore the power button. Can someone please let me know e.g. which package would set that up on the pinephone? I reckon I might have accidentally deleted something in the fix of a messed up apk world.]]> <![CDATA[Raudio for Rock64 V2]]> https://forum.pine64.org/showthread.php?tid=20271 Sat, 16 May 2026 13:08:26 +0000 shinzuka]]> https://forum.pine64.org/showthread.php?tid=20271
Feel free to check out the GitHub page for this RuneAudio fork.


https://github.com/rern/rAudio

[Image: captur40.png]

[Image: captur10.jpg]



First Beta version of rAudio for Rock64 V2.

rock64-raudio-26052026.img.xz

What works:
- NAS mounting
- i2s ES9023 DAC
- i2s Hifiberry DAC+
- onboard analog input

What doesn't work yet: Many things, so I won't list them.


Beta 2

rock64-raudio - 30052026.img.xz
Beta 2 README]]>
Feel free to check out the GitHub page for this RuneAudio fork.


https://github.com/rern/rAudio

[Image: captur40.png]

[Image: captur10.jpg]



First Beta version of rAudio for Rock64 V2.

rock64-raudio-26052026.img.xz

What works:
- NAS mounting
- i2s ES9023 DAC
- i2s Hifiberry DAC+
- onboard analog input

What doesn't work yet: Many things, so I won't list them.


Beta 2

rock64-raudio - 30052026.img.xz
Beta 2 README]]> <![CDATA[pinephone keyboard]]> https://forum.pine64.org/showthread.php?tid=20270 Thu, 14 May 2026 19:25:51 +0000 oliveira11670]]> https://forum.pine64.org/showthread.php?tid=20270 <![CDATA[Screen size issues after update with diederik script]]> https://forum.pine64.org/showthread.php?tid=20269 Wed, 13 May 2026 16:18:38 +0000 pine-user]]> https://forum.pine64.org/showthread.php?tid=20269
The steps I took were the following:

I just got a new PineNote. It was working fine out of the box. I tried running apt upgrade:

Code:
sudo apt update

sudo apt upgrade

and I got the following error message:

Code:
******************************************************************************
*
* The base-files package cannot be installed because
* /lib64 is a symbolic link and not pointing at usr/lib64 exactly.
*
* This is an unexpected situation. Cannot proceed with the upgrade.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
******************************************************************************

I tried deleting the symbolic link as suggested here. The upgrade proceeded. During the upgrade, I was asked about updating the /etc/plymouth/plymouthd.conf config file. I chose to keep the current version. The upgrade finished without error. Over 800 packages were upgraded, and 17 packages were left unupgraded.

When I rebooted, the PineNote got stuck in a loop saying "booting". I was still able to ssh in. I followed the advice in the last post in the link above and ran the suggested script from diederik. (I downloaded the tar.gz labeled v0.0.4.) After running the script over ssh, the boot loop exited to the desktop screen on the PineNote. I rebooted again, and the PineNote booted normally and showed the desktop screen after booting.

However, at this point I noticed the screen size and icon size/label issues which I described above.

I have screenshots, but I'm not sure how to attach them.]]>
The steps I took were the following:

I just got a new PineNote. It was working fine out of the box. I tried running apt upgrade:

Code:
sudo apt update

sudo apt upgrade

and I got the following error message:

Code:
******************************************************************************
*
* The base-files package cannot be installed because
* /lib64 is a symbolic link and not pointing at usr/lib64 exactly.
*
* This is an unexpected situation. Cannot proceed with the upgrade.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
******************************************************************************

I tried deleting the symbolic link as suggested here. The upgrade proceeded. During the upgrade, I was asked about updating the /etc/plymouth/plymouthd.conf config file. I chose to keep the current version. The upgrade finished without error. Over 800 packages were upgraded, and 17 packages were left unupgraded.

When I rebooted, the PineNote got stuck in a loop saying "booting". I was still able to ssh in. I followed the advice in the last post in the link above and ran the suggested script from diederik. (I downloaded the tar.gz labeled v0.0.4.) After running the script over ssh, the boot loop exited to the desktop screen on the PineNote. I rebooted again, and the PineNote booted normally and showed the desktop screen after booting.

However, at this point I noticed the screen size and icon size/label issues which I described above.

I have screenshots, but I'm not sure how to attach them.]]> <![CDATA[Star64: All listed distros don't boot]]> https://forum.pine64.org/showthread.php?tid=20267 Fri, 08 May 2026 14:56:37 +0000 tantamount]]> https://forum.pine64.org/showthread.php?tid=20267 TL;DR: None listed in the wiki boot

Irradium 3.8, kernel 6.12: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

Irradium 3.8, kernel 7.0:   
 Doesn't boot. The power light stays green forever, no HDMI signal.

DietPi Trixie: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

Armbian: 
 They dropped the Star64 some time ago.

NixOS v2023.11.26: 
 This one doesn't decompress: "unexpected end of file"

NixOS 23.11.20230827: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

NuttX RTOS:  
 Doesn't boot. The power light stays green forever, no HDMI signal.

What does boot:
1. I still have an ancient copy of Armbian from when it did support the Star64, which does boot (non-graphical).
2. I see that Fishwaldo's old images from 2023 are still available here: https://pine64.my-ho.st:8443/

Thus I think the "Software releases" section should be updated to remove the entries for the distros that don't even boot.

Of Fishwaldo's 3 images (version 2.1), I get the following results:
  • The minimal distro does not boot. I get the green light that never blinks blue. This is a pity because text-only could be useful.
  • The Weston distro boots and provides a fast GUI, however it doesn't provide anything else, like a menu or a way to launch apps or settings.
  • The Plasma distro boots and provides a fast but more laggy GUI, but it does almost fully work.

Just now, with the Fishwaldo Plasma distro I was able to do the following which is pretty impressive:
  1. Boot up and log in as pine64 (password pine64).
  2. Set up Wifi, which works fine.
  3. Run Firefox, which is somewhat slow but it works.
  4. Download a FOSS program, compile it and run it.
  5. Su as root (password pine64) and run "apt update" but there are no new packages. (e.g. GCC is version 11 but the current version is 14).
  6. Install ffmpeg. This runs fine, however ffplay crashes with a segmentation fault.
  7. Mount a USB thumb drive from the command line (it wasn't seen by Dolphin file manager).
  8. Convert an MP3 to WAV and play it with `aplay`, which sounded like there was interference.

Regarding Weston, when I tried to force a text-only startup (systemctl set-default multi-user), this was ignored.
I think for some people, the text-only startup option could be necessary for projects.]]> TL;DR: None listed in the wiki boot

Irradium 3.8, kernel 6.12: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

Irradium 3.8, kernel 7.0:   
 Doesn't boot. The power light stays green forever, no HDMI signal.

DietPi Trixie: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

Armbian: 
 They dropped the Star64 some time ago.

NixOS v2023.11.26: 
 This one doesn't decompress: "unexpected end of file"

NixOS 23.11.20230827: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

NuttX RTOS:  
 Doesn't boot. The power light stays green forever, no HDMI signal.

What does boot:
1. I still have an ancient copy of Armbian from when it did support the Star64, which does boot (non-graphical).
2. I see that Fishwaldo's old images from 2023 are still available here: https://pine64.my-ho.st:8443/

Thus I think the "Software releases" section should be updated to remove the entries for the distros that don't even boot.

Of Fishwaldo's 3 images (version 2.1), I get the following results:
  • The minimal distro does not boot. I get the green light that never blinks blue. This is a pity because text-only could be useful.
  • The Weston distro boots and provides a fast GUI, however it doesn't provide anything else, like a menu or a way to launch apps or settings.
  • The Plasma distro boots and provides a fast but more laggy GUI, but it does almost fully work.

Just now, with the Fishwaldo Plasma distro I was able to do the following which is pretty impressive:
  1. Boot up and log in as pine64 (password pine64).
  2. Set up Wifi, which works fine.
  3. Run Firefox, which is somewhat slow but it works.
  4. Download a FOSS program, compile it and run it.
  5. Su as root (password pine64) and run "apt update" but there are no new packages. (e.g. GCC is version 11 but the current version is 14).
  6. Install ffmpeg. This runs fine, however ffplay crashes with a segmentation fault.
  7. Mount a USB thumb drive from the command line (it wasn't seen by Dolphin file manager).
  8. Convert an MP3 to WAV and play it with `aplay`, which sounded like there was interference.

Regarding Weston, when I tried to force a text-only startup (systemctl set-default multi-user), this was ignored.
I think for some people, the text-only startup option could be necessary for projects.]]> <![CDATA[Updated Pinebook Pro?]]> https://forum.pine64.org/showthread.php?tid=20266 Thu, 07 May 2026 14:51:18 +0000 tantamount]]> https://forum.pine64.org/showthread.php?tid=20266 I know there's a RAM crisis ongoing but is there ever going to be a new Pinebook Pro2 with more RAM?
Some chips are easier to get than others, for instance the 1.5GB chips are easier to get than 1/2/4 GB.
Therefore maybe a Pinebook with 6GB or 12GB RAM would be doable.
Cheers.]]> I know there's a RAM crisis ongoing but is there ever going to be a new Pinebook Pro2 with more RAM?
Some chips are easier to get than others, for instance the 1.5GB chips are easier to get than 1/2/4 GB.
Therefore maybe a Pinebook with 6GB or 12GB RAM would be doable.
Cheers.]]> <![CDATA[Unresponsive / inaccurate touchscreen]]> https://forum.pine64.org/showthread.php?tid=20265 Thu, 07 May 2026 09:37:08 +0000 PerfectJam]]> https://forum.pine64.org/showthread.php?tid=20265
I have a PineTime purchased in March 2023. When I first used it, the touchscreen was working perfectly.

I then left the watch unused for approximately 2 years. When I powered it back on, the touchscreen was no longer responding correctly, it feels like it is miscalibrated: inputs are not registered where I tap, or swipes are not recognized reliably.

I just updated the firmware to 1.16.0 (from 1.11.0), but the issue persists.

My assumption is that this may be a hardware degradation issue (deep discharge during storage) rather than a firmware problem, but I wanted to check here before concluding.

Has anyone experienced a similar issue after long-term storage? Is there any known fix or workaround short of hardware intervention?

Thanks and cheers !]]>
I have a PineTime purchased in March 2023. When I first used it, the touchscreen was working perfectly.

I then left the watch unused for approximately 2 years. When I powered it back on, the touchscreen was no longer responding correctly, it feels like it is miscalibrated: inputs are not registered where I tap, or swipes are not recognized reliably.

I just updated the firmware to 1.16.0 (from 1.11.0), but the issue persists.

My assumption is that this may be a hardware degradation issue (deep discharge during storage) rather than a firmware problem, but I wanted to check here before concluding.

Has anyone experienced a similar issue after long-term storage? Is there any known fix or workaround short of hardware intervention?

Thanks and cheers !]]> <![CDATA[Unresponsive / inaccurate touchscreen]]> https://forum.pine64.org/showthread.php?tid=20264 Thu, 07 May 2026 09:36:58 +0000 PerfectJam]]> https://forum.pine64.org/showthread.php?tid=20264
I have a PineTime purchased in March 2023. When I first used it, the touchscreen was working perfectly.

I then left the watch unused for approximately 2 years. When I powered it back on, the touchscreen was no longer responding correctly, it feels like it is miscalibrated: inputs are not registered where I tap, or swipes are not recognized reliably.

I just updated the firmware to 1.16.0 (from 1.11.0), but the issue persists.

My assumption is that this may be a hardware degradation issue (deep discharge during storage) rather than a firmware problem, but I wanted to check here before concluding.

Has anyone experienced a similar issue after long-term storage? Is there any known fix or workaround short of hardware intervention?

Thanks and cheers !]]>
I have a PineTime purchased in March 2023. When I first used it, the touchscreen was working perfectly.

I then left the watch unused for approximately 2 years. When I powered it back on, the touchscreen was no longer responding correctly, it feels like it is miscalibrated: inputs are not registered where I tap, or swipes are not recognized reliably.

I just updated the firmware to 1.16.0 (from 1.11.0), but the issue persists.

My assumption is that this may be a hardware degradation issue (deep discharge during storage) rather than a firmware problem, but I wanted to check here before concluding.

Has anyone experienced a similar issue after long-term storage? Is there any known fix or workaround short of hardware intervention?

Thanks and cheers !]]> <![CDATA[Volumio 3 Pine A64+ unofficial]]> https://forum.pine64.org/showthread.php?tid=20262 Sat, 02 May 2026 16:49:24 +0000 shinzuka]]> https://forum.pine64.org/showthread.php?tid=20262
Volumio is back on Pine A64

Image of Volumio tested on a working Pine A64+.

Volumio-3.999-2026-05-03-pine64plus.zip

Tested OK

- USB DAC
- Headphone jack

What remains to be tested:

- i2s DAC

**********Progress************

Volumio-3.999-2026-05-12-pine64plus.zip

- Jack output correction is now working.

- i2s ES9023 and Hifiberry DAC Plus (PCM5122) are available.


[Image: e38bb510.jpg]

in progress ...
[Image: captur38.png]

[Image: captur37.png]]]>
Volumio is back on Pine A64

Image of Volumio tested on a working Pine A64+.

Volumio-3.999-2026-05-03-pine64plus.zip

Tested OK

- USB DAC
- Headphone jack

What remains to be tested:

- i2s DAC

**********Progress************

Volumio-3.999-2026-05-12-pine64plus.zip

- Jack output correction is now working.

- i2s ES9023 and Hifiberry DAC Plus (PCM5122) are available.


[Image: e38bb510.jpg]

in progress ...
[Image: captur38.png]

[Image: captur37.png]]]>