Hello,
I've watched a few reviews of the Pinephone and Pinephone Pro on Youtube.
There is a common theme about charging: That the phone has to be powered up while it is charging.
Has anything changed lately in that regard?
I have also noticed that the reviewers complain about battery life, because it seems the OS is unable to tell running apps that the phone is locked or the screen is off. I wonder why it doesn't just decrease the CPU cores' speeds in that case.
Thanks.

Just posting that there are still Pinephone Convergence sound issues occurring. Sometimes when making a call the call connects and I can hear the other person but they can not hear me. I have to hang up or they do and then I play with sound settings trying to figure it out. The calls system (Gnome) is erratic, unstable. At one point after this problem I noted that in sound settings there were no data in the fields. This indicates to me a complete crash of sound application. 

I would like to suggest that Calls and Chatty be their own operating system. A dedicated call/text system similar to that of Android type system. I now see that sharing the sound system with the operating system regardless of system is not a great idea. Is it possible to have a dual o.s. ? In my case Arch Linux but separate to Arch a dedicated side by side call / text system that Arch has nothing to do with?

https://www.facebook.com/gamesngearwales/

Hello,

I updated my freshly-received PinePhone Beta, which was working correctly. Then after restart I have only a black screen with KDE logo and a mouse pointer. I can connect via SSH.

SDDM's journal:

Quote:Jul 04 19:19:14 plasma-mobile systemd[1]: Started Simple Desktop Display Manager.
Jul 04 19:19:14 plasma-mobile sddm[3221]: Initializing...
Jul 04 19:19:14 plasma-mobile sddm[3221]: Starting...
Jul 04 19:19:14 plasma-mobile sddm[3221]: Logind interface found
Jul 04 19:19:14 plasma-mobile sddm[3221]: Adding new display on vt 1 ...
Jul 04 19:19:14 plasma-mobile sddm[3221]: Loading theme configuration from ""
Jul 04 19:19:14 plasma-mobile sddm[3221]: Display server starting...
Jul 04 19:19:14 plasma-mobile sddm[3221]: Adding cookie to "/var/run/sddm/{5894bace-d8ca-4a6f-b885-770aa308b4c9}"
Jul 04 19:19:14 plasma-mobile sddm[3221]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{5894bace-d8ca-4a6f-b885-770aa308b4c9} -noreset -displayfd 18
Jul 04 19:19:17 plasma-mobile sddm[3221]: Setting default cursor
Jul 04 19:19:17 plasma-mobile sddm[3221]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jul 04 19:19:17 plasma-mobile sddm[3221]: Display server started.
Jul 04 19:19:17 plasma-mobile sddm[3221]: Unable to find autologin session entry "plasma-mobile.desktop"
Jul 04 19:19:17 plasma-mobile sddm[3221]: Socket server starting...
Jul 04 19:19:17 plasma-mobile sddm[3221]: Socket server started.
Jul 04 19:19:17 plasma-mobile sddm[3221]: The configured theme "matcha-dynamic-sddm" doesn't exist, using the embedded theme instead
Jul 04 19:19:17 plasma-mobile sddm[3221]: Loading theme configuration from ""
Jul 04 19:19:17 plasma-mobile sddm[3221]: Greeter starting...
Jul 04 19:19:17 plasma-mobile sddm-helper[3312]: [PAM] Starting...
Jul 04 19:19:17 plasma-mobile sddm-helper[3312]: [PAM] Authenticating...
Jul 04 19:19:17 plasma-mobile sddm-helper[3312]: [PAM] returning.
Jul 04 19:19:17 plasma-mobile sddm-helper[3312]: pam_unix(sddm-greeteression): session opened for user sddm(uid=972) by (uid=0)
Jul 04 19:19:18 plasma-mobile sddm[3221]: Greeter session started successfully
Jul 04 19:19:18 plasma-mobile sddm[3221]: Message received from greeter: Connect
Jul 04 19:19:23 plasma-mobile sddm[3221]: Auth: sddm-helper exited with 11
Jul 04 19:19:23 plasma-mobile sddm[3221]: Greeter stopped.

Quote:Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, xcb.

Aborted (core dumped)

Hi!

I want to delete a single sms from chat history in phosh, not the whole chat history. How to do that?
IIRC phosh utilizes evolution for contacts and data.

IMHO, Broadcom is one of the worst companies when it comes to open-source (although perhaps slightly better than NVidia).

The regular Pinephone has a Realtek WiFi. Of course, this Realtek is worse than a freedom-respecting Atheros ath9k AR9462 found at Librem5,
but at least there's an ongoing research for the opensource replacement of Realtek blob which I've seen somewhere, giving some hope for a future liberation.

Meanwhile, there's no such research for Broadcom - because, the first thing any smart (capable-of-reverse-engineering) Linux-loving person does when he accidentally gets a laptop with a Broadcom WiFi preinstalled, is to throw it away and replace it with a card based on a better chip - either an old trusty blobless Atheros, or from another company the binary blob of which doesn't suck as much. But unfortunately you couldn't do this with Pinephone Pro since it's soldered...

The only reason why I'm not considering a Pinephone Pro - is because I would like to avoid Broadcom.
I hope this could be changed for the future generations of Pinephone. Wonder if MiniPCIe card could be fit

Hi, I've bought PinePhone (not PinePhone Pro) and needless to say, without the case (a silicone back case or some other)  the phone in a bag gets various scratches from things inside.
I have seen a similar post, but it's quote oldish. I hope there is something new. Is there anything specially designed for PinePhone? Perhaps you have several back cases and don't need one, I could buy it from you. 
Other phones' cases can sometimes fit, but they sometimes cover a camera, or a headphones' hole, or the volume buttons don't fit the design.
Hopefully, there are some options apart from sewing something 

I'm running Debian 11 (currently and temporarily Armium) and I need MRAA.  Unfortunately, I can't find Rock64 support in MRAA anywhere.

Someone else must be using MRAA on Rock64, can someone tell me how to get it?

If necessary, I can fork debian/mraa and add rock64 support, but to do that, I'd need all the relevant information. 

Worst case I hope would be copying a supported product.

Best case would be finding a deb repository.

I have a Rock64-2GB (V3.0).  Following these instructions (https://wiki.pine64.org/wiki/ROCK64_Soft...ses#Debian), I downloaded and burned a Debian 11 (Bullseye) installer to a microSd.

I don't have eMMC, so I installed a blank microSD into a USB3 adapter, and with the installer in the microSD slot and the target in the USB3 slot, I ran the installer, selecting sda as the target.

It took a while, but when it finished and started to reboot, I powered off, removed the installer, and put the newly installed microSD in the microSD slot.

It didn't boot.  I even tried using an HDMI head, but to no avail.

To temporarily continue with my work, I am running Armian (Bullseye), but that has it's own issues and I need to get the stock Debian working.

Can anyone offer help or suggestions?

Today my pinephone stopped booting: green led, black screen.



It allready happened to me once, it was after an upgrade that went bad (phone going to sleep before finishing building initrd, me not noticing, something like that), it was quick to resolve by mounting the phone on my laptop via USB, and chrooting in it.



But today it's harder, I tried multiple things with no luck:



- In a chroot ran: dpkg-reconfigure linux-image-5.15-sunxi64

- Configured an older kernel, and tried setting a rescue mode in /boot/extlinux/extlinux.conf directly, and noticing the comment, by modifying the files in /etc and running u-boot-update too.

- Dropped `splash` and added `console=tty1` in `/etc/u-boot-menu.d/pinephone.conf`, ran `u-boot-update`. (Still black screen at this point).

- Soldered a jack-to-USB using an old "FTDI Friend" round in a drawer so I can take a look at serial output (it works!)



At this point I noticed:



> Moving Image from 0x40080000 to 0x40200000, end=415b0000

>   Loading Ramdisk to 452ba000, end 49fff776 ... OK

> FDT and ATAGS support not compiled in

>

> resetting ...



and after doodling around decided to remember that u-boot was no longer supported in Mobian.



So I installed tow-boot (wow it's nice not having to change the SD card each time I want to switch to mass storage ♥).



But still no luck, here's what I see over serial: