Apparently, the protective cases for the regular PinePhone (hard, soft) and the screen protector are not suitable for the Pro, are they?

Are there their Pro siblings around, or coming along anytime soon?

I was wondering if there is anything that can be added to the keyboard case to make it less slick? I feel like every time I grab it I am going to drop it. Any ideas?

Currently packet injection is not working on the unofficial kali linux pinephone image based from mobian.
I asked the dev when it will be added but he doesn't know because he doesn't have time to try new things. he can only build the kernel at the moment.
 My conversation is located here https://github.com/Shubhamvis98/kali-pinephone/issues/1

 So what I'm asking you people is if someone can help him add packet injection to his image please?

Hi all,

Has anyone got confirmation of pinephone's being shipped out from the EU warehouse yet?

I find it a bit weird that it's been nearly a month since I ordered and nothing but silence about the phone, but the keyboard case is already shipped.

Anyone in a similar situation?

Hi, 
I have some problems of memory corruption with sopine compute module. 

Memory corruption change content of file. 

We removed all hard shutdown to avoid corruption, and we shut down system with command shutdown -h now .


Have you already seen this issue ? What can be used to avoid memory corruption ? 

Thx.

Just got by new cases and wanted to share my first impressions (just look and feel and not commenting of software support).

My first thought was how the case reminded me on a Nintendo DS. And the second was wishing there were shoulder buttons. I'm only half-kidding. If you are holding the case in your hand, you have about 8 fingers doing nothing. It would be nice if at least 2 could conveniently press a button. I believe in remapping keys in software so wouldn't have a strong preference on what the default is but some options that come to mind

• Volume keys - The only keys on the phone itself aren't easily accessible when holding the keyboard
  
• Scrolling UP/Down
  
• CapsLock - I think it the default functionality is useless so I had remapped it and now it is a pretty convenient key that I've lost. (Also think Super_L is important so would prefer to not just override that)
  

I recently installed Megi's userland keyboard driver on the PinePhone running Mobian. What I really wanted to do was get my pinephone and keyboard case running as a mini-computer with a CLI (no GUI). I discovered DanctNIX barebones Arch Linux image and finally got the userland driver running on that also. So this is a complete list of steps required to do so. You can find all of this information in various places, but I'm hoping it's handy to have it all in one location for someone...

1. Fix the keyboard case's pogo pads

First, the hardware of the keyboard needs to be hacked a bit. It won't work out-of-box. Locate the Pogo pin pads in the back cover of the new keyboard case where the phone's pogo pins are supposed to make contact. The pogo pads on the keyboard case will not make contact with the pogo pins on the back of the phone unless you do something to raise the pads. 

I carefully pried the plastic holding the pogo pads from the back of the case and slipped a small folded strip of paper beneath them. The plastic holding the pads is glued to the case (which will be the new back of the phone case) and can be pried away carefully. There were no screws in my keyboard case holding the pogo pads.

reference https://xnux.eu/pinephone-keyboard/faq.html#ts in the troubleshooting section at the bottom.

2. Install Arch Linux

Arch Linux ARM builds for pinephone (and PPPro and other devices) are located here: https://github.com/dreemurrs-embedded/Pi...h/releases The latest versions include kb151, the i2c keyboard driver needed by the pinephone's keyboard case. I installed the barebones version which merely boots to a tty and the rest of these instructions are specifically for CLI.

I used the Jumpdrive method which is documented here: https://wiki.pine64.org/wiki/PinePhone_I..._JumpDrive

Connect to your local WIFI...
$nmtui

Select Activate Connection, then select your WIFI and enter password. You can use the arrow keys to move around the TUI (FN+> is UP, FN+{ is DOWN, FN+" is LEFT, and FN+} is RIGHT).

Determine your pinephone's IP address...
$ip a

Look for the ip address for the WLAN0 network connection.

For simplicity, SSH into your pinephone from a linux PC (x.x.x.x is the ip address of your pinephone)...

$ssh alarm@x.x.x.x

Update and upgrade with the following:
$ sudo pacman -Syu

Install some stuff you'll need...
$ sudo pacman -S nano terminus-font git gcc php make

3. Rotate the screen and increase font size

Still SSH'ing into your pinephone...
$ cd /boot
$ sudo nano boot.txt

Locate the line starting with setenv bootargs... This is a list of kernel parameters. Append the following to the end of the list (include a single space to separate it from the prior parameter). The fbcon parameter will rotate your screen 90 degrees clockwise putting it in landscape mode and the kb151 parameter will effectively disable kb151 so we can use the userland driver, which we'll install later. (if you're entering all this from the pinephone keyboard case, don't do the kb151 parameter yet, or make sure you finish everything before rebooting).

fbcon=rotate:1 kb151.disable_input

(Megi added a second fbcon parameter to set the font, but I wasn't able to get this to work, so I added it to the system-wide bash script, which we'll get to in a second....)

To save changes and close Nano, type CTRL-X, Y, and Enter.

back on the command line, run the following to update the boot.scr file from boot.txt...

$ sudo ./mkscr

Reference https://xnux.eu/log/#058 regarding disabling kb151; I tried a couple other methods, but only this one worked.

Add a setfont step to the system wide bash login script /etc/bash.bashrc...

$ sudo nano /etc/bash.bashrc

Add the following line at the end of the file to change the tty font to Terminus c32n (or whatever you like)...

setfont ter-c32n

To save changes and close Nano, type CTRL-X, Y, and Enter.

4. Download, build, and install the userland driver

$ git clone https://mff.cz/git/pinephone-keyboard/
$ cd pinephone-keyboard
$ make

Now we write the systemd unit file...

$ sudo nano /etc/systemd/system/ppkb-i2c-inputd.service

Enter the following into this new .service file...

  [Unit]
  Description=Pinephone Keyboard Service Daemon

  [Service]
  Type=simple
  ExecStart=/home/mobian/pinephone-keyboard/build/ppkb-i2c-inputd

  [Install]
  WantedBy=multi-user.target

To save changes and close Nano, type CTRL-X, Y, and Enter.

Now we enable this service the next time we boot with ...

$ sudo systemctl enable ppkb-i2c-inputd.service

Reference https://wiki.mobian-project.org/doku.php...-case-ppkc regarding runningn this userland driver as a systemd service.

5. Reboot and test

You're done.

$ sudo reboot

When the system reboots, it will still load kb151, but that driver will be disabled. The systemd service ppkb-i2c-inputd will be loaded by systemd and be the driver for the new keyboard case.

Use the Pine key (pinecone symbol) with number keys to enter FN keys. Try it out by typing CTRL-ALT-PINE-2 to switch to tty2 and then CTRL-ALT-PINE-1 to switch back to tty1 which is the default tty.

Hi everyone, I've been working through this multiboot method.  I compiled u-boot with the volume key patch, flashed it to an SD card, hooked up a serial console cable, and verified that the key presses were detected.  That part is all well and good.  Now I'm running into a few problems making it actually boot things and I'm sure I'm missing something minor.  This is being tested on a ubports edition Pinephone, not that it matters but Mobian Bookworm is on my eMMC.

My goal is to boot eMMC with no key press, jumpdrive with a volume up key press, and Mobian from SD card with a key down press.


Problem 1

I set my SD card partitions up like this with sdb1 for boot, sdb2 for Mobian, sdb3 for eMMC Mobian /home:

Running a community edition pinephone using mobian bookworm on my new keyboard. Everything appears to be working with the exception of having an underscore character. Cannot type name_pine in any app. Really need access to this character for terminal. Any ideas or comments are appreciated. Thanks

You can piece this together from a variety of sources, which I've linked to in this post, and I DID eventually put it all together but I'm posting this hoping to help make it a bit easier one someone.

I've got the regular PinePhone (not Pro) running Mobian, (because I'm most familiar with Debian). This should be everything you need to know to get the new keyboard case working.

1. Fix the keyboard case's pogo pads

First, the hardware of the keyboard needs to be hacked a bit. It won't work out-of-box. Locate the Pogo pin pads in the back cover of the new keyboard case where the phone's pogo pins are supposed to make contact. The pogo pads on the keyboard case will not make contact with the pogo pins on the back of the phone unless you do something to raise the pads. 

I carefully pried the plastic holding the pogo pads from the back of the case and slipped a small folded strip of paper beneath them. The plastic holding the pads is glued to the case (which will be the new back of the phone case) and can be pried away carefully. There were no screws in my keyboard case holding the pogo pads.

reference https://xnux.eu/pinephone-keyboard/faq.html#ts in the troubleshooting section at the bottom.

2. Update to a version of Mobian that has the kb151 driver in the kernel

I reinstalled Mobian using the most recent weekly build found here: https://images.mobian-project.org/pinephone/weekly/. The Stable release, at the time, didn't yet include the KB151 module that supports the I2C keyboard. I used the Feb 20th release; note the list is in ascending order and the most recent release is at the bottom.

I used the Jumpdrive method to install directly onto the eMMC. https://wiki.pine64.org/wiki/PinePhone_I..._JumpDrive

3. Install the pinephone in the pinephone keyboard case

Once a current version of Mobian is installed and the pinephone is installed in the keyboard case, the keys are mostly functional. I think the only problem is that the FN keys don't work. The kernel used by Mobian includes a module called kb151, which is an i2c keyboard driver specifically for this keyboard case.

4. Build and enable the userland driver

A 'userland' driver is available which also supports the FN keys. To install this userland version of the driver (and disable kb151), do the following from King's Cross, or any other terminal emulator on the phone...

$ git clone https://xff.cz/git/pinephone-keyboard/

$ cd pinephone-keyboard

$ make

If make indicates a command is not found available, install it. I had to install PHP using the following:

$ sudo apt install php

Next, we'll write a systemd service file for the userland keyboard driver we just compiled...

$ sudo nano /etc/systemd/system/ppkb-i2c-inputd.service

Enter the following into Nano... (note that the ExecStart line must reference the ppkb-i2c-inputd which we compiled. If you put it somewhere else, you'll need to modify that line.)

  [Unit]
  Description=Pinephone Keyboard Service Daemon

  [Service]
  Type=simple
  ExecStart=/home/mobian/pinephone-keyboard/build/ppkb-i2c-inputd

  [Install]
  WantedBy=multi-user.target

(to save changes and close Nano, type CTRL-X, Y, and Enter)

Now we will blacklist kb151 so it won't be loaded by the kernel next time we boot...

$ sudo nano /etc/modprobe.d/blacklist.conf

Add this single line to the file...

  blacklist kb151

(to save changes and close Nano, type CTRL-X, Y, and Enter)

The new blacklist.conf file won't make any difference until you update the ram filesystem with this command, which will take a couple minutes to complete:

$ sudo update-initramfs -u

Now we'll enable the new systemd service...

$ sudo systemctl enable ppkb-i2c-inputd.service

you'll be prompted for your pw a couple times. Once this process completes, reboot. 

You're done. 

Use the Pine key (pinecone symbol) with number keys to enter FN keys. Try it out by typing CTRL-ALT-PINE-2 to switch to tty2 and then CTRL-ALT-PINE-7 to switch back to tty7 where the GUI is (maybe mobian uses tty1 for login??).

Now I just need to rotate the tty2-tty6 screens and increase the font size... Let me know if you already know how to do that.