Just got my Pinephone in the mail. Installed the updates listed and now when I start the phone it shows me the K-gear background and a mouse pointer. I can move the mouse, but that's about it. I can pull up the terminal with a keyboard connected, but unsure how to get back to the GUI.

Any suggestions would be appreciated.

Thanks

Which video players do you use?

I tried some, but the only one working which has a usable UI for me so far is Clapper. But it has annoying artifacts appearing while playing and some minor image errors.

So maybe someone knows about an alternative?

My PPP is borked over sim/sd card issues due to multidinous reinsertions of cards into holder.  Doesn't find sim or make calls as it once did.  The sim card is good as it works in PP.

Per the instructions of pinephone, it was stated that they will send you a new sim/sd card holder if you send your order number and a picture of the card to "pinephone support".  Have done that and no response that they will send a new card or that they even acknowledge receipt of my request.  Sent more than a month ago.

I admit that I took the picture myself and did not take phone to repair shop.  I'm not paying $100 to get a repair shop to send a picture.  I might pay them to install the part later but so far no progress on getting the part.  I might even install a new PPP board if those are ever available on PPP parts site.

So, anyone yet received a replacement sim/sd card holder as promised by pinephone?

thanks,       tom kosvic

Has anyone gotten MMS working and also on Verizon? I've distro-hopped, tried jmms on Mobian, played with APN/MMSC settings (btw, mms.vtext.com doesn't resolve in DNS), and even tried messing with the modemmanager mms config file (stopping and starting mmsd-tng). Nothing seems to do the trick. This is about the last thing I need to get working to really daily drive my PPP.

On June the 6th I apt upgraded my PinePhone CE running Mobian Bookworm after 2 wks. It prompted me to reboot, and when I did the keyboard was no longer recognised, neither as a battery or as an input source, yet the keyboard battery continued to charge the phone itself.

I suspected this was an issue with the update and started investigating; from what I have gathered the keyboard battery is supported via module ip5xxx_power, and the keyboard itself via module kb151. None of these modules are present in my /lib/modules/5.15-sunxi64/kernel subtree, and I the modification date of kernel/drivers/power matches the 06/06 date. 

I understand you can build these modules from source, but I would like to understand why they have disappeared in case this is an issue with Mobian and the maintainers need to be notified. I would appreciate if anyone with a working keyboard could locate these modules and confirm their location.

OK this is going to be a dumb question, but at the store listing page for the POCK64 at https://www.pine64.org/devices/single-bo...rs/rock64/ it says that there's a POE HAT for the ROCK64 but it doesn't say where or what HAT, and the accessories tab of the store doesn't have any POE HATs (at least as far as I can see).

What HAT is compatible / recommended and where can I get it?

June 6, 2022

I originally didn't have Blender on PBP, then I did, then it didn't work with new OS updates, then I fixed that, now it doesn't work with new OpenGL3.3.

PineBook Pro 1st edition
Manjaro/Arch
Linux D0 5.7.19-1-MANJARO-ARM #1 SMP Wed Sep 2 20:43:09 +03 2020 aarch64 GNU/Linux
OpenGL 3.3 support (/etc/environment updated with PAN_MESA_DEBUG="gl3")
community/blender-2.7-es2 2.79b.r71421.e045fe53f1b-9


----------------------------------------------------------------------------

Warning: Could not find a matching GPU name. Things may not behave as expected.
Detected OpenGL configuration:
Vendor: Panfrost
Renderer: Mali-T860 (Panfrost)
ERROR (gpu.shader): OVERLAY_shader_armature_shape_425 GeomShader:  
     |  
  20 | {
     |  
     | Error: maximum output vertices (2) exceeds GL_MAX_GEOMETRY_OUTPUT_VERTICES

Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)

---------------------------------------------

Sure, the geometry shader doesn't work properly as described here:

"Note that GL 3.3 support is incomplete and some rendering features do not work yet, notably geometry shaders."

But darn it, it USED TO, up until the latest rolling Arch distro that I upgraded to today

I just received my PineTime yesterday, and tried to turn it off for the night by holding the power button. However, I believe it rebooted, then stayed in the bootloader (I held it for some time after it rebooted, too). I've tried letting the battery run out, but it still stays in the bootloader. I've attempted to flash a more recent version of Infintime, but I'm not sure it went through. If it did go through, it still isn't turning on after draining the battery. What do I do to fix this?
Ideas:
Re-flash the bootloader
Flash a new bootloader (I'm wanting to switch to Wasp OS, so that might work)

Does anyone have any ideas or suggestions on how to fix this?

Note: If I hold the power button, it shows the green, blue, and red cycles. I looked at the wiki, and don't understand exactly how to use these.
I also can connect to the watch via Bluetooth.
It's a sealed watch.

I have a Beta edition PinePhone which had the default Manjaro OS installed, but things started breaking after I pacman -Sy && pacman -Su-ed it. The first warning sign was the on-screen keyboard not showing up on the SDDM lock screen, and after a reboot, SDDM outright failed to start. sshd was still working, so I installed and started LXDM (after stopping and disabling SDDM), and although it started succesfully, the on-screen keyboard still failed to show up. 

Next, I tried replacing the contents of /etc, /usr, /var, and /opt on the eMMC with a fresh copy from Manjaro's PinePhone image by copying them over without flashing the entire drive (which was a horrible idea in retrospect and wouldn't have saved any time vs. reflashing from microSD), but something went horribly wrong because sshd went down almost immediately, and I can't tell if the phone is on any more.

Just now, I dd-ed JumpDrive onto a microSD card and booted my phone, but the only difference seems to be that a green LED in the upper left corner of the front of the phone turns on; the screen itself is off, and I don't see any new block devices from my PC. I think my immediate questions boil down to these:

1. Is my host PC missing a driver? dmesg doesn't seem to have picked up any plugging/unplugging events while the phone is on and ostensibly booted into JumpDrive. lsusb likewise doesn't change with the phone connected or disconnected. If the kernel driver needed to detect a PinePhone running JumpDrive isn't installed/loaded by default on a typical Arch system, this could be a quick and easy fix.
   
2. Is it normal for JumpDrive to start with a blank screen? If not, how should I troubleshoot it? I've already downloaded the image twice with cache cleared, and the checksums match.
   
3. If all else fails, is there a way to have the eMMC reflashed more "manually?" I don't have much in the way of appropriate tools/equipment, though...
   

Hello,

I was wondering if XMPP will ever be a direct option for joining the joined chatrooms.

I'm currently joined via an IRC transport, but that might require a bit too much setup for newcomers. Joining via a bifrost bridge (matrix.org or aria-net.org) are options, but they tend to be unreliable

Matterbridge (I assume that's what you're using) supports XMPP, but I understand it's not that simple. The Pine64 team seems to prefer self-hosting where possible, so they'd need a team member willing to set up the XMPP conference server, maintain it, and moderate the MUCs

I understand if it doesn't happen, but I figured it wouldn't hurt to ask. Thank you for your time and the awesome open-source hardware!