Hello there,

I've just recieved my very first Pinephone 64 but it's barely working so I can't use it for anything. I haven't found how to fix these problems anywhere else so I'm asking you for help. I'm having these problems:

HDMI only works for a second, right after this the phone display starts jittering and I can't do anything with it from then on. I also sometime ssee a black box covering half of the srceen when I try to navigate the menu. The menu never open and the display jitters everytime I touch it.

Display sometimes flickers a lot, meaning the brightness goes form whatever I set it on to 0 every time I stop touching the display. It's very annoying possibly even health hazardous as contunous use of the phoen in this state is very disorienting at the very least. The only fix for this is restart.

Battery status is random to say the least. One second I have 50% th eother I have 8%, then I have 14%, then 80%, then 50% again. I have no idea how much battery I actually have and whether or not the phone needs charging.

Updates don't work anymore. I installed the first 2 updates (2-3 GB), but the new one (23 MB) can't be downloaded because something is missing (error message).

Can someone please help me with these issues? By the way I'm using the vanilla Pinephone 64 beta convergence edition with the OS it's shipped with.

Last week we booted Linux on the Pine64 Ox64 64-bit RISC-V SBC, powered by Bouffalo Lab BL808 SoC. And we wondered if a tiny 64-bit Real-Time Operating System (RTOS) like Apache NuttX RTOS might run more efficiently on Ox64. (With only 64 MB of RAM)

Let’s make it happen! In this article we...
(1) Begin with NuttX for Star64 JH7110 RISC-V SBC
(2) Boot it unmodified (!) on our Ox64 BL808 RISC-V SBC
(3) Add Debug Logs in RISC-V Assembly
(4) Tweak the NuttX UART Driver to print on Ox64
(5) Fix the Platform-Level Interrupt Controller
(6) Track down why RISC-V Exceptions aren’t dumped correctly
(7) And plan for the upcoming Initial RAM Disk

Check out the article:
RISC-V Ox64 BL808 SBC: Starting Apache NuttX Real-Time Operating System

Lup

   

So a combination of trying the commands
https://wiki.debian.org/Mobian/Tweaks#Au...pp_scaling (cause I wanted postmarketostweaks)
"apt update"
"apt upgrade"
has resulted in apt trying to install from "http://deb.debian.org/debian/pool/main/d/dbus/libdbus-1-dev_1.14.6-1_arm64.deb" However that 404s and looking up one directory in the url, I'm wondering where it got that version number, as versions 1.14.10-* are all older than my mobian install (I installed it this month!).
I have checked my sources files match the ones listed at https://blog.mobian.org/posts/2023/06/10/bookworm/

Given I now can't get apt install or remove cause of this I'd like to know how to fix this in either direction? Either remove what wants to install libdbus or get apt to fetch a version actually in the repo.
(yes I've already tried google I might not know the right search terms, so I'll happy take advice there too!).

I'd prefer to stick with Mobian, because I'm most used to Debian-based distros (and Mobian seems like the closest available to vanilla Debian on Pinephone/Pinephone Pro). But I'm looking to switch as much of my computing as possible to the tty. What recommendations do you all have?

My progress so far, aside from the utilities that ship with bash (at least on Debian):
* nvlc - stream internet radio and play downloaded audio
* curl wttr.in - weather service
* tilde - yes, it's heresy not to use vim or emacs or nano, but tilde is a simple CUA text editor and gets out of my way
* elinks - read HTML webpages online (but doesn't look like a way to access web-based services that require logging in); it is easy to use and impressively snappy except when my internet is slow
* alpine - takes tinkering in the config file and browsing forums, but seems to be working now
* pdftoppm, cacaview - initial tests suggest that they can act as a minimally adequate pdf viewer together, with much zooming in
* mapscii.me - would not work online with telnet, but the local client over node.js works; if you don't have unicode, it's not quite as rich of an experience
* will experiment with apertium for machine translation and csound for synthesizing music

Holes in my environment:
* browsh, carbonyl - respectively based on Firefox and Chromium, they purport to bring more extensive and modern access to more complicated web services, and they render webpages relatively impressively, but after a complicated installation process they both appear to require a mouse to do anything beyond scrolling whichever page you initially requested (and they may have other holes), but my tty does not have touch or mouse support; so a big hole is any web-based services that I can't find some alternative for (dropbox for file backups, ecommerce, proprietary financial services, and anything else that needs login and/or interactivity even as simple as a forum or shipping carrier website)
* clocks - any way to set alarms from the terminal and have them wake the phone to go off; gnome-clocks's command line options are exceedingly limited
* ditto for any kind of calling or text messaging; command line options are exceedingly limited for gnome-calls and chatty; gnome-calls refuses to work without a graphical display; chatty does have an intriguing daemon option but no documentation in the man page about how to use it; emailing a text to myself did not work either (phonenumber@txt.att.net)
* and a big miscellaneous category for various services that i took for granted on the gui, for example turning the volume or brightness up and down, checking the statuses of battery or mobile data or wifi, anything to do with bluetooth, even turning the torch on or off - hopefully some searching around online can come up with commands at least for the things that also apply to desktop Debian

* not to even mention a zoom videochat client, which is the only reason I still keep an old Android phone lying around because zoom's desktop client appears to be for x86 only, and their web client wasn't picking up my camera or microphone even in GUI Firefox

Just did another pacman -Syu, and it only refreshed the list of mirrors; on repeat it just said there was nothing to do. So my Manjaro Phosh is up to date, just like it was a few weeks ago.

However, since then the battery charge lasts less than a day. Before that it held for almost two days. Now if I charge it in the morning, and don't use it at all, by evening it's gone down to 2%, having shut down Manjaro. If I plug the red cable, it gives me the p-boot (now somehow stuck at the jumpdrive option, so if I accidentally press any buttons, that's what boots).

How can I find what's draining my battery?

Hi

I develop Slackware for the ARM platform, and Pine64 were kind enough to donate a PbPro to the project.
Unfortunately it's now developed a hardware fault, which I made a video about here: https://youtu.be/knOqICIOwdM

Who's the best person to contact about this?

Thanks
 Stuart.

I'm trying to get the second serial port working (/dev/ttyS2) on a PINE64-LTS board.

I created and edited the DTS file as @martinayotte  posted a while back (https://forum.pine64.org/showthread.php?...ight=ttyS2).
But it didn't seem to work. I am using a logic analyzer to monitor the signals and getting NO data. I am using a simple C program to open and write to the port. the write reports its writing data.

in /boot/dtb/allwinner I modified the "-lts.dtb" file
-rw-r--r-- 1 root root 41859 Feb 17  2023 sun50i-a64-pine64.dtb
-rw-rw-r-- 1 root root 41973 Nov  1 13:20 sun50i-a64-pine64-lts.dtb
-rw-r--r-- 1 root root 41909 Feb 17  2023 sun50i-a64-pine64-lts-dtb-backup
-rw-r--r-- 1 root root 41981 Feb 17  2023 sun50i-a64-pine64-plus.dtb


Is there a way to confirm 
a) which DTB file the system is actually using, or
b) that the "okay" on that serial port is enabling the mux mapping for those pins?

Thanks in advance.

I can't get sound to work through HDMI with Manjaro.  To see if it is a hardware or software issue, I put the latest Armbian (23.8 Bookworm Cinnamon) on SD.

The left-side USB-A port doesn't work.  It will provide power, but not recognize anything.  The right-side USB-A still works.  I took a USB stick that has both USB-A and USB-C jacks.  The drive shows up if I stick in the USB-C jack, but not the USB-A.  USB-A seems to work fine with Manjaro, so I doubt it is a hardware issue.

(HDMI also doesn't work.)

Any ideas?

Related threads:

https://forum.pine64.org/showthread.php?tid=8243
https://forum.armbian.com/topic/31416-pr...ebook-pro/

Hello everyone,

I have recently bought second-hand Pinebook Pro. I am using ARM platform for many years already (ASUS Chromebook C201PA with Devuan Linux as daily driver). Pinebook Pro brought my attention because of it's privacy features, great community support, RK3399 onboard (my chromebook has RK3288), case with alloy-magnesium, high resolution display and it looks modern and solid. I have installed Devuan Linux and it worked well with some workarounds (change sleep mode from deep to s2idle, my own custom background daemon for backlight management).

Pinebook Pro recently started having problems with charging. Through USB-C almoast always it is really charging (battery voltage rises by around 0.2-0.3V when plugged in as shown by command "sensors"). However sometimes the voltage does not change even though red LED is on. When I plug in barrell charger battery voltage never rises even though red LED is on. Earlier (one week before) battery used to charge normally through barrell or USB-C. Does anyone have any suggestions what is the problem in hardware? I have tried to perform some measurements for voltages on PCB but I didn't have enough time to investigate deeper and didn't find anything.

It's a shame that so promising device has dumb hardware issues (weak USB-A port unable to power HDD, high-pitch noise, exploding sound from speakers when audio codec goes to sleep mode regardless the volume, extremely slow charging, problems with charging, incorrect battery temperature reporting). I have come up with an idea that if I would not be able to solve charging issue, I will replace the motherboard with modified Orange Pi 3B accompanied by my custom PCB for I/O (USB ports, SD card slot and so on). What do you think about it?

The all important third row of symbols works with a press of Fn and Left Cmd when Mobian is set up for Left Super for alternate characters.