I purchased my Pinecil back in April, and it was useful one time in the field.

The other day I wanted to upgrade to IronOS from 2.15 (stock) to 2.18, and the device appeared to not boot but would DFU.

After some digging, I discovered the issue was with bad soldering on the OLED connector. Sure enough, after a reflow, I was able to upgrade.

Unfortunately, it appears the LCD is dead after a few minutes use.

I expect that the Pinecil is out of warranty. Does anyone happen to know the part# for the OLED LCD module? I'd like to try to replace it if possible.

I'm really disappointed with the build quality on the Pinecil, and this really leaves a negative impression of the Pine brand. I buy a *lot* of commodity electronics from CN/TW and even when the build quality is questionable, it usually will function reliably. Not so with the Pinecil.

I nominate that a mod please put a sticky at the top of the mobian forum that directs users to the Mobian wiki
https://wiki.mobian-project.org/doku.php?id=start
and the IRC channel #mobian on irc.oftc.net

Communication channels and contact info
Matrix
#mobian:matrix.org
Main Mobian channel
Matrix
#mobian-ports:matrix.org
Discussions about porting Mobian to new devices
IRC
#mobian on OFTC
This is bridged to the matrix channel
XMPP
Use https://irc.cheogram.com/ bridge to IRC

Telegram
https://t.me/mobian_project
also bridged to the matrix channel
Mastodon
https://fosstodon.org/@mobian

email
contact@mobian-project.org

I received my pine phone pro a couple of weeks ago
got it charged and working then left it until yesterday
now it will not charge 
it is completely unresponsive
what can i do

My PineTime is stuck on the InfiniTime triangles after trying to install the latest update 1.9.0. That got to 1% install and dropped the connection. The first restart got back to the normal watch screen so I tried again with the same result. Now holding the power button in gets the green Pine then just boots to InfiniTime screen. Have tried oldr updates which get to 2% before the connection is dropped, have left it for a couple of days tom drain with the same result. Holding the power button for longer just cycles through red green amd blue pines but ends at the same place. This is a sealed version and the hard reset has always worked before when stuck on InfiniTime screen. All update had been validated. Any hints on what to try next.

I have notice there have been no specific updates to UBPorts for PinePhone in a while. I have seen generic updates which would apply to all UBPorts supported device like language for the OS and keyboard.

Anyone know what is going on?

As time goes by Pine64 will be coming up with next generation designs, one feature which would be inexpensive and easy to implement is software definable buttons.
How would you like to have one, two, or more buttons which can trigger a scrip or other action, for example pop up a camera app or flashlight; maybe a coded key combo starts a script to quickly wipe and overwrite your entire flash memory and SD card.

Additionaly I would like to see larger hardware switches and an option for a battery cover that would allow me to use an external switch slider to toggle one or several of the dip switches without taking the back off. 

From a privacy standpoint I could see oppressed minorities, investigative journalists, even technology experts carrying trade secrets appreciating easier access to both hardware and software quick actions like these.  For most users there is probably a fast access app you would like a button for.

PineDio Stack BL604 ships with the Hynitron CST816S I2C Touch Panel. (Yep the same as PineTime!)

Here's how I created the Touch Panel Driver for Apache NuttX RTOS...

NuttX Touch Panel Driver for PineDio Stack BL604

feature request:
add some keys or functions to pp keyboard case, especially, pageup, pagedown, f11, f12 and maybe others.

i notice some function keys are missing, i think those should be added.
pageup: fn+l
pagdown: fn+k
f11: fn+o
f12: fn+p
maybe some others not listed.

Today I ran into issue #1 listed in the Mobian Wiki, where the boot process stops at a black screen.

https://wiki.mobian-project.org/doku.php?id=tow-boot

Holding in the power button resulted in the phone rebooting rather than powering off, where the cycle repeated. It took several tries to get Mobian booted up. Tried the reset button in the back and finally had to remove the battery even though that's not recommended. This was a real pain, so for now I'd like to go back to uboot which never seemed to have any problems.

Before installing tow-boot I took an image backup of the eMMC using jumpdrive. Obviously the entire image could be copied back to the eMMC, but would it be possible to just extract uboot from there and write it to the eMMC using dd? What is the offset and length of the uboot image?

Completed calls had been being briefly interrupted every few seconds and often terminated unexpectedly.  I turned off Chrony and this behavior stopped.  Turned it back on and the behavior resumed.  Evidently the phone can't deal with Chrony sending udp packets in the background during a call.  Sound is still so noisy and laggy as to be unusable, calling is unreliable, and I still have no data, but this is progress.

Also with Chrony active the ModemManager log cycles like this

<info>  [modem0] 3GPP registration state changed (home -> idle)
<info>  [modem0] 3GPP registration state changed (idle -> registering)
<info>  [modem0] 3GPP registration state changed (registering -> home)
<info>  [modem0] 3GPP registration state changed (home -> idle)
<info>  [modem0] 3GPP registration state changed (idle -> registering)
<info>  [modem0] 3GPP registration state changed (registering -> home)
<info>  [modem0] 3GPP registration state changed (home -> idle)


Stopping Chrony seems to have put a stop to that.


[Edit]
I can now complete calls (still not usable) with WiFi turned off. "ping 8.8.8.8" (or any other address) gets 5 to 10 returns and then stops. When I check the modem
state it has come unregistered. Trying to use data breaks something.