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.

I'm on US mobile and had data and mms working but a couple of upates and upgrades later no data connection. Still have phone and sms capabiltiy but no data. I have tried mulitple apns no luck. I flashed Biktorgj's firmware and recovery several times and different versions no luck. Phone shows 4G connection but no data. Wifi and bluetooth work fine. I'm running 2/20/22 weekly no help so went back to unstable still no help.

Wanting the board to power when power is connected (i.e. after power is restored after power loss)

Hmmm....  I have a one RP64 that starts this way.  I dug out my spare and it does not without hitting the power button.  

Maybe there is a jumper that needs to be set.  It was so long ago I set the first board up I can't remember and I don't see anything at the wiki that says to set a jumper for this.

Little help please.

Hello,

I have searched the internet as well as these forums and can not find plans for the watch and the charging base.

Any format would work: DWG, STL, Sketchup, ...

Can anyone assist?

Thanks

I run my WiFi on channel 13 (2472MHz 20MHz width) and channel 142 (5700MHz, 40MHz width) because of high congestion. It's legal where I live and I never have any problem because of that.
PPP EE works fine with both bands out of the box with stock firmware, however most third party distributions like the latest mobian refuse to work with these channels, SSIDs are just not visible on the phone.
Changing channels to something more common works this around, but noticeably reduces performance for other devices because of congestion.

iw reg get lists these frequences as usable:
phy#0
country 99: DFS-UNSET
 (2402 - 2482 @ 40), (6, 20), (N/A)
 (2474 - 2494 @ 20), (6, 20), (N/A)
 (5140 - 5360 @ 160), (6, 20), (N/A)
 (5460 - 5860 @ 160), (6, 20), (N/A)

There is no regulation data in system so regulation setting is bogus, but installing CRDA and setting a proper regulation domain doesn't result in anything.

I've tried to remove stock "brcmfmac43455-sdio.bin", "brcmfmac43455-sdio.clm_blob" and "brcmfmac43455-sdio.pine64,pinephone-pro.txt" from /lib/firmware/brcm and use firmwares from different images for PPP and PBP instead, the best I could get to is using "brcmfmac43455-sdio.bin", "brcmfmac43455-sdio.clm_blob" and "brcmfmac43455-sdio.txt" from /lib/firmware/updates/brcm (note the updates subdirectory) of the stock system.
This way I can use my 5GHz network, but 2.4GHz is still not accessible.

Have anyone else run into this issue? Any ideas on how to fix?

Hello everybody,


I'm currently working on a project based on Nordic Semi standard SoftDevice, with custom bootloader and application.
This project works well on developper version of PineTime, programing and debug were done via JTAG.
Now I wish to install it on a sealed version of PineTime but cannot found the right way to do that. I've tested deployment of my dfu package with nRF Connect on computer and smartphone, and also with a custom DFU application but nothing works.
The download seems to works, but InfiniTime indicates nothing (no progress bar or anything)...


What I wish to know is : 
- is it possible to flash the entire memory OTA or could I only flash the application ?
- is there a guide / tutorial that describes OTA update procedure ?
- is there specific parameters / keys to set in my dfu package to get it recognized as a valid package ?

Any help would be greatly appreciated !

Best regards.

Hi,

I've been running Mobian for a while and updated to Bookworm and have kept up-to-date since.
Calls have been working for me (non-IMS VoLTE) and so has SMS though I've had a few missing incoming calls / text notifications, too, from suspend.

Use case is phone on and suspended, modem firmware EG25GGBR07A08M2G_01.003.01.003

It seems that recently incoming calls and SMS no longer have any ringing / notification volume. I had several text messages give no notification from suspend with screen locked, I've tested an incoming call and the incoming call screen is there but no ringing. Same with SMS, I get the text notification popup on the lockscreen but no notification sound. Volume is on max.

Speaker tests from sound settings works, pulseaudio shows everything at 0dB.

I've logged a bug report
https://gitlab.com/mobian1/issues/-/issues/416

Wondering whether I'm the only one to have noticed this recently.

I just got my Pinecil in the mail, loving it so far, and was hoping to go update the firmware since the newest ones have usb pd improvements, which is what I use. The soldering iron its self works great, and boots up just like it is supposed to, but I can't get into DFU mode to update. I have tried different power sources, cables, and computers, but whenever I try to plug it in while holding the "-" button, it doesn't boot. I can leave it for 15 minutes and it never boots into DFU mode. Any ideas?