Just some observations concerning HDMI.
I have Arch Linux on my PPP and have noticed issues concerning power and HDMI - USB thumbdrive.
What I did was unplug the power from my ICZI dock and then used a background image for lock screen and app list
and then rebooted with HDMI plugged in but no power cord attached to dock.
The result was HDMI works (background image applied) and mouse keyboard work as well.
Drawback - no power cord can be attached. 
As soon as I plug in power to dock I lose mouse, keyboard and monitor and USB.
Hope this helps some folks.
-----------------------------------------------
Edit May 19,2022
The PPP works perfectly with Pine dock but not the ICZI.
Edit 2:
Replaced wall unit for USB (for BlackBerry and Moto E4) with a quality unit with multiple plug.
I suspect that the ICZI dock might now work.

The back cover of my Pinephone has two cracks and I'm afraid it won't make it much longer.

A replacement only costs $5 -- but shipping to Europe would be an additional 30 (!) Dollars.

Is there any way to circumvent these exorbitant shipping costs, i.e. are there any resellers or collective orders etc?

(To be fair, I this were an iPhone, I'd probably be pleasantly surprised if Apple only charged me $35 (and not 120) for a comparable spare part; but it seems absurd to me that these simple, cheap parts are all shipped individually for $30 each...)

Hi all:  I did a search on xrdb for this group and came up empty before I posted.  Did a cursory search of other groups in PINE64.   I did find some information. I have installed xrdb and tigervnc.  I tried xrdb with windows10 remtoe desktop connection was not successful. I have a RockPro64 with Debian installation.  I installed everything about 3 days ago, so my guess is that I have the latest Rockpro64 version of Debian installed.

If there is previous post on how to configure Debian + RockPro64 and use windows 10 to remote log into rockpro64 please direct me to the post.  My guess is many of you are doing this, and I am just not configuring things correctly. 

The error messages I get are :
sending login info to session manager, please wait...
login successful for display 11
VNC started connecting
VNC connecting to 127.0.0.1 5911
VNC error - problem connection
some problem

Thanks in advance, and please excuse me if I missed an answer to this post already.   

Hi everyone, I'm putting my ANSI PineBook Pro up for sale.

• Perfect working condition
  
• Excellent cosmetic condition
  
• Only lightly used
  
• Fresh install of Manjaro Mate
  
• Clean
  
• The only thing missing is the power adapter. (The adapter was DoA but USB-C charging works fine.)
  
• Asking $200 which includes UPS shipping
  
• PayPal
  
• Prefer to ship US only
  

I've got an PinePhone (Evergreen) running Mobian Bookworm.  I got MMS messaging working in February after installing chatty v0.6.0-1 and it was fine until on or shortly before March 12 2022.  The messages seem to be retrieved and queued in ~/.mms/modemmanager/ but they don't get processed further and make their way into chatty anymore.

I've also got a Ting SIM with service via T-Mobile/Dish and MMS works fine with that.  I've switched SIMS back-and forth several times and the symptoms are persistent - Verizon always fails now and Ting works.

Here is the log for a 2nd attempt at processing a message:

Hello,

hopefully this does not sound too weird.
I purchased a 3 pack of sealed Pinetimes shortly after it became available.

Last summer, I noticed horizontal stripes under the display and asked here what that might be and where it came from. We didn't find an explanation but others having this phenomenon themselves.




Since I got a 3 pack, I used the second watch after some time because I found those stripes annoying. Summer was over by then.

Everything was perfectly fine for months until summer started a short time ago. After having been outside for one or two sunny days, my second Pinetime suddenly also had exactly those stripes.

Now I came along thinking of some UV radiation issue.

Is that nonsense or might there be a connection?

Best regards

Where's the blog post?

Hey all,

Are multiple eSIMs support on the Pine Phone?

Thanks.

PinePhone 1.2 - Linux mobian 5.15-sunxi64

I just recently reflashed my PinePhone with Tow-Boot and the mobian-installer-pinephone-phosh-20220508 and since then the keyboard battery is not being charged.

The fully charged battery was completly drained and remains at 0%, in Gnome Settings --> Power under Devices kb151 is listed with 0% charge and the Powersupply app has the Keyboard Case listed as well with Capacity 0%, Voltage 2.601V, Status flickering between Discharging and Charging (0.02W) and Health Good.

demsg returns --> kb151 2-0015: Charger read failed - MCU returned 0xff

Before the switch to Tow-Boot / Mobian I had U-Boot / Mobian and the battery in the keyboard case was working just fine.
It was keeping my phone charged and was a nice companion as it extended the usable life of the phone to a fine 24hrs.
Since the switch to Tow-Boot / Mobian, the once full battery in the keyboard case was completly drained by the phone, but never recharged.
As soon as I plug in the power supply it starts charging the phone (charge current alternates between 1.2A and 1.7A) once the phone battery is charged it stops charging (charge current drops to 0.3A) and the keyboard case battery remains at 0% charge, i.e. it does not charge the beyboard case battery.
Power is connected directly to the keyboard case and the top-right corner of the keyboard case gets warm indicating that the electronics inside seems to be working.

Any ideas on how to get the keyboard case battery back to working order?
I do updates on a daily basis via apt, so should have the latest version of mobian and software, and I am using the PinePower 120W Desktop Power Supply to charge the phone.

Pinephone won't boot from the SD card.
I put in Tow Boot formatted SD card and turned it on.
The flashlight turns on and the phone doesn't turn on.

I flashed the Tow Boot image with Etcher and also with dd.

I just got this phone yesterday so I'm not sure if this is a hardware problem and I should contact Pine64 support.

I am downloading a PostmarketOS bootable image to try that out.

Any suggestions? Anyone experienced this?