I tried to installl caffeine today by running `sudo apt install caffeine`. I got this error message:

```
md5sum: /usr/lib/crust/scp.bin: No such file or directory
E: Sub-process if grep -qE '(u-boot-sunxi|arm-trusted-firmware)'; then touch /tmp/upgrade-uboot; else md5sum /usr/lib/crust/scp.bin > /tmp/crust.md5; fi returned an error code (1)
E: Failure running script if grep -qE '(u-boot-sunxi|arm-trusted-firmware)'; then touch /tmp/upgrade-uboot; else md5sum /usr/lib/crust/scp.bin > /tmp/crust.md5; fi

```

After this, I couldn't installl anything without getting the same message. So I ran the following:

```
sudo mkdir /usr/lib/crust/

sudo cp /usr/bin/scp /usr/lib/crust/scp.bin
```

Now everything works, but this is a hack and I'm not sure what went wrong here, or how to fix it properly. Thoughts?

Hello,

I have observed generation of spurios headphone detection interrupts on my second-batch PineBook Pro.  The interrupt count increases with no headphones being plugged in or out, which is obviously not the expected behavior.  I have also verified that music playback through internal speakers does not cause the tnterrupt count to increase.

You can check the above-described interrupt count by running something like this:

I want my phone to auto suspend, but not if music is playing. My player, gmusicbrowser, has an option to prevent a screensaver when the player is playing and fullscreen. However, it doesn't work on the Mobian Pinephone.

There's a program called caffeine that is supposed to let you tweak your sleep settings, but I can't install it on Mobian. I get these errors:

```
md5sum: /usr/lib/crust/scp.bin: No such file or directory
E: Sub-process if grep -qE '(u-boot-sunxi|arm-trusted-firmware)'; then touch /tmp/upgrade-uboot; else md5sum /usr/lib/crust/scp.bin > /tmp/crust.md5; fi returned an error code (1)
E: Failure running script if grep -qE '(u-boot-sunxi|arm-trusted-firmware)'; then touch /tmp/upgrade-uboot; else md5sum /usr/lib/crust/scp.bin > /tmp/crust.md5; fi

```

Any ideas?

Got my Manjaro CE phone in October. After playing with Phosh for a bit I switched over to KDE Plasma and found that the phone recognized my sim, but then after doing an update, would no longer see the sim card. I allowed it to go through several updates and continued to try to have it find my Sim with no success. Eventually I downloaded and flashed a very recent version of the KDE software in to the eMMC. Once again the phone saw the sim and hooked up with my cell provider. Just by circumstance I recieved a phone call from my brother in law and had a nice clear conversation on the phone. After that I did a large update (over 500 mg) and ever since then my phone will not see the sim and connect. I love the software and it seems to be getting better and better. But this thing of not seeing the sim is making me nuts. Does anyone have a remedy for this?

I have no use for the other keyboard, and I always switch right to 'terminal'. Is there a way to make this universal and persistent?

For Rock64 Ver2 (1GB ram), I installed OMV using Guide: Installing OMV5 on Raspberry PI's, Armbian SBC's, & i386 32-bit platforms: Link: https://forum.openmediavault.org/index.p...platforms/

I install the same thing again on another SD card but the same problem - can not shutdown - always reboots.

Sharing video files from OMV to Kodi & vlc on firestick 4k, NO buffers. works great.

I tried from OMV: https://github.com/ayufan-rock64/linux-build/releases/ - It works & shutdown too.

BUT, while sharing video files from OMV to Kodi & vlc on firestick 4k, buffers a lot & it's unwatchable.

How I can achieve the best of both worlds?

Hi everyone!
These last few weeks, I've been working on improving the MCUBoot bootloader. This bootloader is the one that is programmed at the factory along with InfiniTime 0.7.1.
I think I've reached a state that allows other developers and users of PineTime devkit (not sealed) to test, debug and raise issues.
But first, a bit of background info:

What is the purpose of a bootloader?
The bootloader is the first software to be ran after a reset. Its main goal is to initialize the MCU and load the application firmware. The bootloader can provides many additional functionalities like firmware upgrade, recovery, firmware authentification, HW diagnostic and selftest,...

As of now, there are 2 major bootloaders for the PineTime:

• The MCUBoot bootloader (used by InfiniTime)
  
• The NRF Bootloader (used by Wasp-os)
  

• The possibility to force revert to the previous version of the firmware
  
• The possibility to install a recovery firmware from the external flash memory. This firmware can be useful if you installed a firmware that does not support OTA, for example.
  
• Simple UI
  
• The bootloader displays its own version and exports it to the application.
  

• The update procedure from a device coming out of factory (factory bootloader + InfiniTime 0.7.1) : First update the bootloader, then flash the recovery firmware, then use your PineTime
  
• The OTA procedure (update InfiniTime)
  
• The revert procedure
  
• The recovery procedure
  
• The switching procedure to/from InfiniTime and wasp-os
  

• testfw-random-dfu.zip : this firmware contains only random data instead of executable code. This could happen if the user applied a DFU file that is not intended to be run on a Pinetime. In this case, the bootloader will apply the upgrade, notice that it's not runnable and will automatically revert to the previously running firmware.
  
• testfw-no-validate-no-watchdog.zip : this firmware displays a yellow InfiniTime logo. It does not validate the firmware and does not refresh the watchdog. It simulates a firmware that crashes and that is not able to refresh the firmware. The watchdog will reset the device and MCUBoot will revert to the previously running firmware.
  
• testfw-validate-wdt-no-ota.zip : This firmware does refresh the watchdog AND automatically validate the version. It means that to the point of view of MCUBoot, the firmware is working fine! BUT... this bad firmware does not provide the OTA and the reset functionality. This is one of the worst degraded case : the bootloader cannot do anything! The only workaround is to wait for the battery to drain completely and then charge the PineTime again. This is reset the CPU and offer the possibility to force a firmware revert during the next boot.
  
• The worst of the worst degraded cases is one where the new firmware erase or overwrite the bootloader and/or the recovery firmware with invalid data. In this case, the device is totally bricked and can only be recovered using SWD (meaning the device must be opened).
  

Why doesn't the Pinephone come with a fingerprint reader? This is a real dealbreaker.

I was playing with this SD card loaded with over a dozen OSs. Ubuntu Touch was running great, but all calls failed. Some other OSs were making great calls, but had some other rough edges. Is there a general agreement as to what OS is the most pleasing to use? The one the device shipped with had poor call quality. Thanks!

Items like Bluetooth, wifi etc cant be clicked? Only stuff like rotate and brightness. Whats up with that?