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.

Hey everyone,
After my keyboard case happily working for the last few weeks/month or so, I ran a pacman -Syyu a few days ago (Friday I think) and on reboot the keyboard stopped responding. Did I miss something in the install messages? Am I just waiting for some kernel fix to make its way down to me?

The one odd-ball thing about my setup is I disabled sddm and have been using Emptty to boot into Awesome (pinephone = tiny linux desktop).

Only other clue is the power button on the keyboard case seems to still kick the phone on, so it's not like there's no contact between the phone and the keyboard. (I did try popping the phone out and back in just in case, but that pin-connecting issue isn't one I've had.)

Happy to wait for an update to come down, but I don't want to sit here with no working keyboard if I just forgot to edit some settings or something.

Thanks!

I recently did a kernel update and ever since I can't find a way to use the keys next to f1-f10, like +,=,-,_, etc.

I need to get something off my chest and I hope, I will find help here.
 
I am not a Linux Pro, but I am using Linux on my Laptops and PCs for many years now.
When Ubuntu Touch came up, I immediatly ordered a BQ E5 Ubuntu Edition. 
I've been using Ubuntu Touch for years now and I was happy, when the Pinephone came up. Finally open Hardware!

I own more than one Pinephone and I know people who own one. And I am absolutely happy using them and tinkering around.
But let's take 5 Pinephones. At least 3 of them have hardware issues (not just some dead pixels, which would be happily accept). Summed up, these phones have been in use for not more than a months's time and have never left the building. They're absolutely in mint condition. So too heavy "use" can't be a reason.

• We have one with a display defect (parts are darker/brighter than others)
  
• We have one, gotten hot and startet to damage the display
  
• We have one, which gets hot as soon as the speaker is active
  

Hello

I have copied the image (booting form SD, using dd) to the eMMC. The image file is exactly the same as was used to flash the SD card.
After this has been done, the PBP does not boot anymore (neither eMMC, nor SD). The power LED stays amber, nothing happening.
Any hints?