From the terminal

"The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mobian-project.org bookworm InRelease: The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
W: Failed to fetch http://repo.mobian-project.org/dists/bookworm/InRelease  The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
W: Some index files failed to download. They have been ignored, or old ones used instead."


I remember having similar problems with other repos but cannot find the fix. Where can I find the new key?

since quite a while, I realize my pinephone does not accept the letter Y on the onscreen keyboard. This happens in Manjaro Plasma mobile, and also in Postmarket OS SXMO. The screen is delaminating. Could this be a hardware related problem, or is it a software thing?

Next to

1. the PinePhone keyboard

which is great, which keyboards can be used? There is still an issue that the PinePhone keyboard does not work with all distros. Wibble tested the:

2. iGo Stowaway bluetooth keyboard with the PinePhone:

https://forum.pine64.org/showthread.php?tid=16449

For us, the Go Stowaway bluetooth keyboard is a bit large for mobile use. It exists since  December 28, 2004:

https://the-gadgeteer.com/2004/12/28/thi...rd_review/:

With newer devices:

kugiigi 19 Mar 2022, 05:20 in the Ubuntu Touch forum:

«Bluetooth is a miss and hit in UT unfortunately. In my experience, any BLE or higher than BT 3.0 have issues»

what about:

3. Logitech Dinovo MINI Bluetooth, PC / Mac, Keyboard ?

https://www.amazon.de/Logitech-Fernbedie...B0012AYEHM

https://wiki.ubuntu.com/logitech%20dinovo%20mini

There are some thirt party Logitec GITHUB projects available, which could be tested with the Logitech keyboard:

https://github.com/PixlOne/logiops

https://github.com/libratbag/piper/

Why did Martin Braahms built an own keyboard? Did he not find a BLE keyboard on the market, which works satisfyingly with the PinePhone?

Has anyone opened up their PPKB to add a hardware kill-switch for its battery? This way, the USB port of the phone could be used safely (when the switch is off).

Would this make sense?

Alternatively, a slider-switch could be added to the back of the phone, made accessible from the outside (by drilling), which would slide under the Pogo pins that feed power from the battery, disconnecting them when desired.

No matter how it's done, it really looks like the battery inside the PPKB needs some sort of hardware switch. This way, it will truly behave as what it really is: a powerbank, not just an extra battery. A powerbank which you manually connect and disconnect, and charge separately on its own port.

As of the time of writing this post, the official pinephone lithium battery is out of stock.

The wikipage to which the above page redirects to (namely this one) says:

Quote:The supplied battery is meant to be compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone. The extended life aftermarket BBU does fit, although it is a tight fit.

I received my keyboard a few days ago, long awaited, probably because of COVID supply chain issues.

I've gotten it to work, but with some serious issues. First and most importantly, keys constantly get "stuck" and repeat a character continually, until I hit another key or two to break it out of the loop. I've had the keyboard's repeating character issues cause me to execute commands in the terminal from my shell history that I did not want to execute, which obviously can be extremely dangerous if you're doing the wrong task.
I've tried both the userland and kernel-mode drivers. Both have this issue, so probably not a software issue.

I haven't found a workaround for this. I've tried to ensure the pogo pins make good contact, doesn't seem to help.

Secondly, while I can live with the idea that I can't use the phone's USB-C port while it's in the keyboard, I have also heard gurglings of keyboards destroying PinePhones for no apparent reason, even when instructions are followed. If this is true, I may not want to use the keyboard at all, because despite its bugginess, I do use my PinePhone with Fedora as my daily driver.

Lastly, the keys just suck. You have to hit them dead-on or they don't depress, and even then you have to hit them *hard*, and I'm not just talking about the top row.

Returning isn't an option, for one it's not enough money to be worth the shipping hassle, and for another I doubt Pine64 would respond to help in any reasonable amount of time anyways.

What the hell should I do? Just eat the cost and forget about it?

Hello

On my mobian phone there is a process named jitterentropy-rngd. Compared with all the other processes running, this one is cumsuming a good amount of CPU.
On the other hand the current kernel 5.15 has the modules sun8i_ce (where CONFIG_CRYPTO_DEV_SUN8I_CE_TRNG is included) and arm_smccc_trng (CONFIG_HW_RANDOM_ARM_SMCCC_TRNG). I don't know if the older kernels have them as well. Based on the description, I would expect them to provide "good" random numbers.
If at least one of these modules is active, is there still a need for jitterentropy-rngd then?
Is there a way to test it?

I have touch display and it works fine with android image.

I'd like it to work with the latest armbain (jammy, or bullseys).

Anyone have it running on that linux distro?

Does the 5.15 kernel support it directly?   If so how to get the boot env correctly, if not help on building a dtb module or complete kernel.

Thx

Any clues as to what carrier is compatible with the Pro? I'm trying to get my ducks in a row.

Hello, I'm trying to flash Manjaro ARM Phosh to /dev/mmcblk as described on the Flashing to the eMMC section of the wiki.

However, when I run the dd command an error is returned: error writing to '/dev/mmcblk2': No space left on device
1803+0 records in
1802+0 records out
1890381824 bytes (1.9 GB, 1.8 GiB) copied

Using the manjaro-arm-phosh image file.


I've run