<![CDATA[PINE64 - Portal]]>

<![CDATA[PINE64 - Portal]]> https://forum.pine64.org/ Wed, 02 Sep 2026 10:03:00 +0000 MyBB <![CDATA[Hardware Feature Suggestion for Quartz64: SPI Flash Hardware Write-Protect]]> https://forum.pine64.org/showthread.php?tid=20366 Mon, 31 Aug 2026 01:19:48 +0000 Independent Researcher]]> https://forum.pine64.org/showthread.php?tid=20366
First of all, thank you for providing amazing open-source hardware to the community. I am a developer, privacy enthusiast, and independent researcher, and I would like to propose a simple yet high-value hardware revision for future batches of the Quartz64 or upcoming single-board computers. Currently, the board relies on DIP switches for boot priority, which is firmware-based and does not physically cut the power line for the SPI Flash write operations.

For users focused on sovereign security, physical containment, and preventing persistent firmware implants (rootkits), having a Hardware Write-Protect (WP# linked to GND via a physical Jumper or a Screw mechanism)—similar to the Chromebook write-protect screw—is crucial. Adding small exposed copper jumper pads (open pads) between Pin 3 (WP#) and Pin 4 (GND) on the PCB layout would allow advanced privacy users to bridge them and achieve true physical, air-gapped read-only isolation for the Tow-Boot/SPI flash.

Furthermore, for PINE64 boards that come with a pre-soldered SPI Flash from the factory, we strongly suggest shipping them with a clean, verified, and officially signed open-source bootloader (like Tow-Boot) pre-flashed out of the box. Many security-conscious buyers operate in highly compromised, untrusted, or heavily monitored network environments where flashing a clean image locally from scratch is incredibly risky or nearly impossible without immediate interception. Shipping the hardware with a factory-guaranteed clean bootloader would provide a secure and immutable root of trust immediately upon unboxing.

I highly recommend offering these as design standards in your upcoming revisions, or even as an optional manufacturing configuration toggle for a small extra fee. It would make PINE64 the ultimate choice for the global privacy and secure-boot developer community.

Looking forward to hearing your thoughts on this hardware implementation.]]>
First of all, thank you for providing amazing open-source hardware to the community. I am a developer, privacy enthusiast, and independent researcher, and I would like to propose a simple yet high-value hardware revision for future batches of the Quartz64 or upcoming single-board computers. Currently, the board relies on DIP switches for boot priority, which is firmware-based and does not physically cut the power line for the SPI Flash write operations.

For users focused on sovereign security, physical containment, and preventing persistent firmware implants (rootkits), having a Hardware Write-Protect (WP# linked to GND via a physical Jumper or a Screw mechanism)—similar to the Chromebook write-protect screw—is crucial. Adding small exposed copper jumper pads (open pads) between Pin 3 (WP#) and Pin 4 (GND) on the PCB layout would allow advanced privacy users to bridge them and achieve true physical, air-gapped read-only isolation for the Tow-Boot/SPI flash.

Furthermore, for PINE64 boards that come with a pre-soldered SPI Flash from the factory, we strongly suggest shipping them with a clean, verified, and officially signed open-source bootloader (like Tow-Boot) pre-flashed out of the box. Many security-conscious buyers operate in highly compromised, untrusted, or heavily monitored network environments where flashing a clean image locally from scratch is incredibly risky or nearly impossible without immediate interception. Shipping the hardware with a factory-guaranteed clean bootloader would provide a secure and immutable root of trust immediately upon unboxing.

I highly recommend offering these as design standards in your upcoming revisions, or even as an optional manufacturing configuration toggle for a small extra fee. It would make PINE64 the ultimate choice for the global privacy and secure-boot developer community.

Looking forward to hearing your thoughts on this hardware implementation.]]> <![CDATA[Single-board computers and the art of companionable coexistence: Has anyone ever pair]]> https://forum.pine64.org/showthread.php?tid=20365 Sun, 30 Aug 2026 02:12:53 +0000 Spaker]]> https://forum.pine64.org/showthread.php?tid=20365

MeetAgree.com
Your city's hottest girls are here ]]>

MeetAgree.com
Your city's hottest girls are here ]]> <![CDATA[Pinecil as a Pocket-Sized Wingman?]]> https://forum.pine64.org/showthread.php?tid=20363 Thu, 27 Aug 2026 15:15:21 +0000 Arsen]]> https://forum.pine64.org/showthread.php?tid=20363

MeetPrettyGirls.com
Find a girl to share the night with ]]>

MeetPrettyGirls.com
Find a girl to share the night with ]]> <![CDATA[SlateOS feedback needed!]]> https://forum.pine64.org/showthread.php?tid=20362 Mon, 24 Aug 2026 14:00:37 +0000 highjumpman]]> https://forum.pine64.org/showthread.php?tid=20362
- Vibration toggle
- Optimisation of app to watch comms
- A fix for the launcher not being available after reconnecting
- The companion app now finds the app after it was away from the phone

I would really like your feedback! I'm also curious for more sub-app ideas, and if anyone has tried writing their own.]]>
- Vibration toggle
- Optimisation of app to watch comms
- A fix for the launcher not being available after reconnecting
- The companion app now finds the app after it was away from the phone

I would really like your feedback! I'm also curious for more sub-app ideas, and if anyone has tried writing their own.]]> <![CDATA[Hello, I am a new member of the forum.]]> https://forum.pine64.org/showthread.php?tid=20357 Thu, 20 Aug 2026 18:17:43 +0000 WhiteRabbit0]]> https://forum.pine64.org/showthread.php?tid=20357 <![CDATA[RAM-free SBCs with SODIMM slots]]> https://forum.pine64.org/showthread.php?tid=20356 Thu, 20 Aug 2026 14:21:58 +0000 anchor]]> https://forum.pine64.org/showthread.php?tid=20356
This could have several advantages:

- Much lower base price

- No need for separate 4/8/16/32 GB SKUs

- Users can choose the amount of RAM they need

- RAM could be upgraded later

- Less dependency on onboard RAM availability

Any thoughts?]]>
This could have several advantages:

- Much lower base price

- No need for separate 4/8/16/32 GB SKUs

- Users can choose the amount of RAM they need

- RAM could be upgraded later

- Less dependency on onboard RAM availability

Any thoughts?]]> <![CDATA[Default password]]> https://forum.pine64.org/showthread.php?tid=20355 Thu, 20 Aug 2026 11:02:27 +0000 dissimilar_goose]]> https://forum.pine64.org/showthread.php?tid=20355
The username alarm is the one it wants me to log in to but none of the passwords I've tried have worked]]>
The username alarm is the one it wants me to log in to but none of the passwords I've tried have worked]]> <![CDATA[New SlateOS features]]> https://forum.pine64.org/showthread.php?tid=20351 Tue, 18 Aug 2026 01:47:44 +0000 highjumpman]]> https://forum.pine64.org/showthread.php?tid=20351 Github:

Fix for accelerometer.
Fix for overlapping buttons on the watch.
Fix for recurring notification vibrations.
Companion app UI reworked.
Shake-to-wake in addition to raise to wake.
Sensitivity settings for both accel-based wake methods.
Deactivation of face diagnostics.
Notification on the watch.
Watch screen navigation indicators.
Watch face, button and text colours!
Media control sub-app (tested with Spotify).
Weather sub-app with tides (I live near the sea) (uses phone GPS).
Turn-by-turn Navigation sub-app for OsmAnd Free and Pro (no affiliation there!). Start navigation in OsmAnd and open the Vavigtation sub-app on the watch.
RSS news reader sub app (configure via its settings in the companion app sub-app repository).
Companion app sub-app connectors for http, calendar, alarms, HealthConnect, Home Assistant.

]]> Github:

Fix for accelerometer.
Fix for overlapping buttons on the watch.
Fix for recurring notification vibrations.
Companion app UI reworked.
Shake-to-wake in addition to raise to wake.
Sensitivity settings for both accel-based wake methods.
Deactivation of face diagnostics.
Notification on the watch.
Watch screen navigation indicators.
Watch face, button and text colours!
Media control sub-app (tested with Spotify).
Weather sub-app with tides (I live near the sea) (uses phone GPS).
Turn-by-turn Navigation sub-app for OsmAnd Free and Pro (no affiliation there!). Start navigation in OsmAnd and open the Vavigtation sub-app on the watch.
RSS news reader sub app (configure via its settings in the companion app sub-app repository).
Companion app sub-app connectors for http, calendar, alarms, HealthConnect, Home Assistant.

]]> <![CDATA[Newbie questions]]> https://forum.pine64.org/showthread.php?tid=20350 Fri, 14 Aug 2026 02:09:07 +0000 TouchuvGrey]]> https://forum.pine64.org/showthread.php?tid=20350
i'm Mike from Australia and am considering buying a PineTime watch.

i would prefer to sync/connect it directly to my linux compter. if necessary, through a
Samsung s21

i get the watch in the post. i open the box. i charge it.

What do i need to do after that ? Their website is anything but clear.

Are there any fitness apps that work with PineTime ?

Does PineTime count calories burned ?

Mike]]>
i'm Mike from Australia and am considering buying a PineTime watch.

i would prefer to sync/connect it directly to my linux compter. if necessary, through a
Samsung s21

i get the watch in the post. i open the box. i charge it.

What do i need to do after that ? Their website is anything but clear.

Are there any fitness apps that work with PineTime ?

Does PineTime count calories burned ?

Mike]]> <![CDATA[Beta test Signal Desktop for Linux ARM64]]> https://forum.pine64.org/showthread.php?tid=20349 Tue, 11 Aug 2026 14:57:04 +0000 as365n4]]> https://forum.pine64.org/showthread.php?tid=20349 Quote:Hi everyone,

We’ve been working on Linux ARM64 support and it’s now available for beta testing. There are Debian and AppImage packages available. We’d appreciate your help testing it on your favorite ARM processor! Please let us know how it goes and share your feedback here. https://community.signalusers.org/t/sign...64/9001/90

Debian and AppImage packages are available direct from Signal, please follow the steps in the link below.
https://community.signalusers.org/t/beta...rm64/76184

Arch Linux ARM packages are available through pacman

Code:
sudo pacman -S signal-desktop

and via AUR

Code:
yay -S signal-desktop-beta

Anyone interessted in testing on PinePhone and PinePhonePRO please use the "Desktop" image and give feedback to Signal via the links above to their cummunity forum.]]> Quote:Hi everyone,

We’ve been working on Linux ARM64 support and it’s now available for beta testing. There are Debian and AppImage packages available. We’d appreciate your help testing it on your favorite ARM processor! Please let us know how it goes and share your feedback here. https://community.signalusers.org/t/sign...64/9001/90

Debian and AppImage packages are available direct from Signal, please follow the steps in the link below.
https://community.signalusers.org/t/beta...rm64/76184

Arch Linux ARM packages are available through pacman

Code:
sudo pacman -S signal-desktop

and via AUR

Code:
yay -S signal-desktop-beta

Anyone interessted in testing on PinePhone and PinePhonePRO please use the "Desktop" image and give feedback to Signal via the links above to their cummunity forum.]]>