Some people might be affected by some driver bug where the camera:

• does works right after boot of the PinePhone Pro.
  
• But after suspend, the camera stops working.
  

I succesfully opened the pinetab2 very carfully and replaced a front screen. Put it all back together and...... Everything works, except the keyboard. I was really carful with the ribbon cables. The keyboard cable doesnt appear missalined or broken anywhere.

i'm assuming the cable must be broken internally.
i thought maybe i put the docking connector back in, reversed, so maybe the pins are in reversed order? It looks like theres only one way to screw down the ribbon cable end with the connector pins into the casing.

so im assumin i need a new ribbon cable. Can i buy one specifically sized for that keyboard? Is that kind of ribbon cable a standardized thing?

short of that, does anyone have a suggestion on why the keyboard may not be responding?

is there a way via command line or by kde info center where i could see if the keyboard hardware is present or not?

thanks in advance,

I've been trying with some small success to make use of an SOQuartz with both the Pine64 Model A baseboard and a Waveshare CM4-to-Pi3 baseboard, although things are extremely messy and I have no idea where to look to be able to figure out how to fix things.

It seems a lot of the distros available on the software releases page supposedly use the CM4 baseboard, and while it works and I can get video on HDMI, even a graphical console using the latest Manjaro image from June 2023, the USB ports do not work. I have no idea how to get them to work and searches have not turned up any useful information.

I also attempted to use DietPi, Manjaro, and Plebian on the Model A baseboard, and have noticed a lot of oddities. The Pine64 wiki page on software releases for the SOQuartz instructs one to change extlinux.conf to use the model-a.dtb but doing this results in failure to boot. I don't yet have the time to hook up one of my FT232s to this thing to dig deeper. I forgot to change the DTB file once however that resulted in the Model A booting properly. However, I don't think I like Manjaro very much and would much prefer a Debian-based one, and in any case, getting system upgrades fails badly. Plebian boots, however it has no support whatsoever for the built-in WiFi or any of the WiFi dongles I have, making it a non-starter since I then have to plug the thing into a network port somewhere and do a headless install and that's too tedious to do with the way I have things set up now, and then I have no idea how to get any of the wireless modules working. DietPi works and I'd been able to get it to run, however I noticed that it runs very hot, temperature peaking at 71°C, which is very bad. I have some CM4 heatsinks on the way but I also noticed that the linked DietPi image uses the cm4 DTB, and I suspect this might partially be to blame for the thermal issues.

So I have several questions:

1. What do I need to do to get the USB ports on the Waveshare CM4-Pi3 board to work? Has anyone else experienced this issue? It is possible that I have a bad board given that I got mine suspiciously cheap (~US$5), but before I try to buy another one I want to know if this might be a known issue.

2. What do I need to do in order to get the built-in wireless networking on the SOQuartz to work? I take it we need some kind of firmware files which none of the linked distros include for whatever reason.

3. What's with these DTB files? Is it really safe to use the CM4 DTB even if you're using a Model A baseboard?

Thanks in advance for any help that anyone can give.

For reference the Waveshare board I have is this one

https://www.waveshare.com/wiki/CM4-to-Pi3-Adapter

I would like to run several sudo commands in a terminal, which requires me to enter my password. But I was never prompted to enter a password, is there a default password? My pine phone came preinstalled (Manjaro-ARM, Release 21.03).

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.