After updating a fresh PineNote there are now problems with the sizing of the display. The battery percentage is cut off on the right, and the on screen keyboard is partially cut off on the bottom. The application icons in the application view are small and harder to see now than they were before, and there is no text description under 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:

Here an overview of what Star64 distros work or don't.
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.
  

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.
   

Hi,
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.

Hello,

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 !

Hello,

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 !

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.




in progress ...

Hello,

I have a PinePhone 64. I’m desperately trying to figure out which Mobian image to use for the PinePhone.
I can’t find the image for the PinePhone on the Mobian website. And I don’t want to make a mistake.
Thank you for your help.

Hello,

My Pine time is dead. It won't charge from its cradle. Is there anything I can do to make it work?

Chris

Hello,
If I connect to a power supply, the display only shows calibrating, and not work. If I push the + switch under connecting the power,
it shows PD debug State 3 No Vbus. After push the - switch, only shows calibrating...
Under firmware update there are handshake errors. So I cannot step through the "calibrating" word.
The display orientation is changes, as I turn the pinecil handle to other direction....
How do I reset the unit to a working state?

Hello, everyone! I’m looking for engineer for customized PPP. I need to create an MVP based on PPP. I need to create a physical qwerty keyboard, replace display with touch screen with a smaller more. Replace the cameras. Anybody can help with it?