I have recently rediscovered my older PBP I think its number 328, hence I am curious what if any preemptive fixes would be advised for such a system and can be done regarding the broken plastic around the ports?

How to donate to the maintainers of DanctNix Arch Linux?

Thanks

I'm having an issue where my PinePhone can use the 4G network for data and SMS/MMS (in/out), but I'm unable to hold a call on the 4G network. Currently the call immediately degrades to the 3G network, and if I force exclusive usage of the 4G network, my calls fail to connect entirely.

Here's my current setup:
PinePhone v1.2b Beta Edition
postmarketOS (systemd; edge release) -- Phosh UI
calls 48.2 (GNOME)
default firmware for the Quectel EG25-G modem (I've not yet tried https://github.com/the-modem-distro/pinephone_modem_sdk).

network: Public Mobile (Canadian subsidiary of TELUS)

I've been following https://pine64.org/documentation/PinePhone/Modem/ to attempt to set up VoLTE.

Using the default profile ROW_Generic_3GPP and subsequently trying the profile Telus-Commercial_DO, I've sent AT commands in this way:

Hi

When is it expected that I can  buy a PineNote Community Edition (Europe)?

Hi all, I’m building a logger platform with the Pine A64 board that collects environmental data from multiple ESP32 modules, and I’m deciding whether to use MQTT over local Wi‑Fi or direct USB/UART communication. I recently found this guide on ESP32 MQTT setup and found it an excellent primer for structuring reliable publishing from sensors:
https://www.theengineeringprojects.com/2...-mqtt.html
I’ve also been exploring how to implement MQTT on ARM boards using Mosquitto on Armbian, and came across a hands-on ESP32 + MQTT + Node-RED sensor dashboard project. My main concern is latency, long-run stability, and ease of integration via UART. Has anyone built a similar real-time logging system on Pine A64 with multiple ESP32s? Which communication method worked best for you in terms of reliability and scalability?

I am at my second PinePhone, the first one having had a hardware failure that made the modem, among other things, inoperable (and the outer parts: screen, case, buttons having been damaged enough to make a mainboard replacement not worthwhile).

So I bought this PinePhone in March 2023 from the EU Store. Sadly, this means that the compulsory EU warranty (2 years) has expired 3-4 months ago. So far, I was happy with it (and the outside is in good condition), but…

I have noticed 2 failures this week – I cannot prove that they happened simultaneously, but the coincidence seems odd:

1. The USB-C port works for charging only. The data lines appear to be completely dead. I first noticed this (a few hours ago) trying to boot into JumpDrive, to connect the PinePhone to my computer (because I wanted to back up and then replace the installed OS through USB, trying to switch from Manjaro ARM stable, last updated over a year ago, to postmarketOS 25.06). There was no way I could get the computer to detect the PinePhone. I tried 2 different cables, 3 different USB-A ports on the computer, rebooting the PinePhone several times and the computer twice, nothing helped. Then I took out the JumpDrive microSD card, booted back into the installed OS, and tried using the "convergence package" dock stick to plug in my (USB-A) notebook mouse. Nothing, no way I could get the PinePhone to see the mouse at all, either. Charging works even through the dock (using its USB-C power input), but nothing else works. One would think that this is clearly a failure of the USB-C daughter board, but…
   
2. The audio jack on the other end of the phone also stopped working. I first noticed that this Thursday. When I try to connect the PinePhone to a hardware audio mixer, or to my small home stereo, it fails to detect that there is anything plugged in and does not produce any audio output. Tried 2 different cables, 2 different ports on the audio mixer, and even another output device (my stereo), nothing worked. This time, at least, there is some output in the journal, but it sounds like a typical "bad contact" on-and-off scenario: Within 1 second, I get around 20 times:
   
   Code:

   Jul 07 00:11:26 plasma-mobile kernel: jack: irq plug-in
Jul 07 00:11:26 plasma-mobile kernel: jack: irq plug-out
   So, while the PinePhone did detect that something was plugged in, it comes and goes (and comes back and goes again), around 20 times per second.
   

• The WiFi has become much worse at keeping connections alive. Running ping commands (doing a ping every second) either from the PinePhone to somewhere else or from the computer to the PinePhone makes it better, but the WiFi used to work much better even without that workaround.
  
• Bluetooth stopped pairing successfully with one particular audio device (the same hardware audio mixer that I first tried using the audio jack with), but the PinePhone pairs successfully with other Bluetooth devices (at least a small Bluetooth receiver and my computer), and other smartphones pair successfully with the audio device that the PinePhone has trouble with. In the particular pairing that stopped working, I always get the same "br-connection-unknown" error. It used to work fine for months, then suddenly started failing around 2 weeks ago.
  

I finally bought a PinePhone Pro.

https://xnux.eu/rk2aw/
"To enter the menu, you just need to keep holding the power button when powering up the device, until the LED indicator stops flashing."

But nothing, black display for me...

Hello, first time user, 

The UI in settings does not seem to work, because the packages to be updated are always the same.

Particularly firmware is brcm80211    20240709 and it seems it expects to be updated to 20250410 even if it does not work

So I tried to update using the terminal
 sudo apt update

, but I get an error regarding invalid signature: EXPKEYSIG 447D9EBF6B6F552D Maximilian Weigang

May you help?

Best

background:  2 years ago, I was following along with @lupyuen  great series of articles to get LVGL running on PinePhone.  I was emulating the same journey but using Zig for all the hardware interfacing (and I got quite far).  But at the time I was stuck on an old version of Zig and lost motivation.  Now I finally have some hardware to run latest Zig, and I decided to port my project over to Zig 0.14 including it's new build system.

I've struggled for a few days to recreate the environment I had running (I also switched from macos to to Linux and still learning!).  So I decided to go back to basics, and try to understand how NuttX interects with the JumpDrive image.

This is what I tried:

1. compiling some very simple Zig code, that should toggle the phone LEDs.
2. build the above as an elf file for arm freestanding with a target of cortex_a53
3. created a simple .ld linker file that ensure my entry point is at 0x40080000
4. using objCopy extract hex via the -O binary
5. gzip the resulting binary file into Image.gz

I was expecting that whatever the JumpDrive util does, it somehow jumps to executing the code directly from Image.gz.  However now I suspect that this .gz might be a bit more complicated than straight arm machine code.  But I have no idea what? and I struggle to follow the NuttX build (maybe something to do with a util called binfmt? but also I saw mention of nxflat).

Ultimately it would be nice to find a way to deploy to PinePhone as 'baremetal'.  But for now the JumpDrive 'hack' would be enough, allowing me to hop between SDCards to compare/debug different images.

Does anyone have any idea how to wrap my baremetal code into something JumpDrive can recognize from the Image.gz file please.

I've been running Mobian on my Pinephone for about 4 years now... maybe 5.
I prefer X11 to Wayland for my own reasons, so I'm looking to find out if I can port XLibre to Aarch64 Mobian.
XLibre looks like it will be supported and extended in future, whereas it looks like XOrg is either stalled or ending.

Has anyone tried it yet?