Wiki

• FrontPage
• RecentChanges
• FindPage
• HelpContents
• PocophoneF1

What's not working as of Trixie

• USB OTG
• Front Camera
• Should work with tweaks:
  • Sensors (accelerometer, light sensor, proximity sensor)
  • Bluetooth
  • Suspend + wake on calls

• Works with tweaks (see Notes:)

  • Speakers (volume is too low)
  • Audio calls
• suspension is known to be broken in several aspects, e.g. increasing energy consumption, not resuming for a network event (call), breaking audio settings. See suspend section for workarounds

Support

If something isn't working for you, you can get in contact with Mobian developers and the Mobian community in various ways. All of them are listed here.

Installation

Obtain the Image

Pre-built images for your device are available from https://images.mobian.org/qcom/weekly/, packed in a file named

• mobian-<family>-<graphical_shell>-YYYYMMDD.tar.xz

(where the <family> you are looking for is sdm845).

Verifying the images

See FAQ#How to check Mobian images' signature.

Preparing and flashing the device

WARNING: Flashing Mobian to your device will wipe your Android installation and all the data contained in it. If your device contains data you'd like to retain, please make a backup in advance. Installing a recovery software such as TWRP and making sure you understand how to recover your system before proceeding is also recommended, unless your device contains no valuable data and you know how to recover it.

It's recommended that you upgrade Android to the latest available version and install all system updates before installing Mobian, because Mobian uses FW files from Android partitions for enabling various peripherals.

Device's bootloader needs to be unlocked: the procedure varies depending on the device you own, then either refer to Xiaomi guide for unlocking bootloader or search the Internet for an unlock guide aimed at your specific device.

Mobian images are made of:

• an Android bootimg containing the kernel, device-tree and initramfs named mobian-<processor>-phosh-YYYYMMDD.boot-<model>.img

• an Ext4-formatted rootfs (using Android's sparse image format) named mobian-<processor>-phosh-YYYYMMDD.rootfs.img

Note: Up until 2023-10-22 the archives used to contain an additional image file named mobian-<processor>-phosh-YYYYMMDD.boot.img meant to be flashed to the system partition. This is no longer the case starting with the 2023-10-29 set of images.

As these devices have several variants, which differ only by the device-tree they need, and the DT being part of the bootimg, we provide one bootimg for each variant. You have to flash the one matching your device:

• Xiaomi Pocophone F1 with ebbg touchscreen: beryllium-ebbg

• Xiaomi Pocophone F1 with tianma touchscreen: beryllium-tianma

If unsure, complete the procedure here below using the tianma bootimg and then check if touchscreen is working: if not, repeat the flashing procedure with the ebbg bootimg.

Once you have uncompressed the tarball, boot your device into fastboot mode, connect it to your computer using a USB cable and run the following commands to install Mobian:

fastboot flash boot mobian-<processor>-phosh-YYYYMMDD.boot-<model>.img
fastboot erase userdata
fastboot -S 100M flash userdata mobian-<processor>-phosh-YYYYMMDD.rootfs.img
fastboot erase dtbo
fastboot reboot

It is recommended to reboot the device after flashing via the "fastboot reboot" command, as the reboot is triggered after the writings to device's internal memory from previous steps are completed.

Fastboot mode

When the device is shut off, the xiaomi-beryllium can be put in fastboot mode by pressing and keeping pressed the power and volume down buttons, until a screen with a bunny and an android with a blue 'FASTBOOT' writing appears.

Default pin and password

The default user is mobian with password 1234 . See Mobian/FAQ#Default_pin_and_password .

Automatic resizing of your filesystem on first boot

After flashing the image and booting for the first time, Mobian will resize the root filesystem to take all possible space on the disk. This can take a while and will only happen on first boot. So grab a ${DRINK_OF_CHOICE} and be patient.

Notes:

General:

• If the device becomes unresponsive after a fastboot command succeeded, power it off and boot into fastboot mode again, then execute the remaining commands.

Audio

• for general audio to work one needs to drop alsa's state file:

 sudo systemctl mask alsa-restore 
 sudo rm -f /var/lib/alsa/asound.state

Data connection

In case mobile data connection is not working, it has been experienced that installing Android 11 on the device before installing mainline Linux distributions gets the required modem FW in place. Please note, even after that process mobile data can still be unstable.

After downgrading the firmware, update the bootloader following https://wiki.postmarketos.org/wiki/Xiaomi_POCO_F1_(xiaomi-beryllium)#Updating_the_bootloader

Bluetooth

In order to get Bluetooth working, execute the following

  sudo cp /lib/firmware/updates/qca/beryllium/crnv21.bin /lib/firmware/qca/

then reboot. Reference salsa.debian.org/qcom-linux#10

Suspend

• Suspension can be inhibited by enabling Caffeine quick setting in Phosh/Plasma. This needs to be done on every boot.

Camera

Starting with the 6.12 kernel shipped with Trixie, this device's camera is (at least basically) supported. Only the main (back) camera is supported for the moment.

To control the camera, you'll like to install gnome-snapshot and/or plasma-camera. It was reported the former can have some issues with cameras not recognized or black frames from time to time, while the latter feels stable and takes higher resolution pictures.

If you're experiencing any camera-related issue, in order to check whether the camera support is broken at the kernel level or below in the libcamera-gstreamer-pipewire stack, please use following commands:

• gst-device-monitor-1.0 Video/Source should show supported cameras and related resolution/color modes

• gst-launch-1.0 libcamerasrc ! queue ! glimagesink rotate-method=1 should bring full-screen the gstreamer pipeline with the video stream coming from the main camera

Installing to an SD Card

The installation above is to the internal memory (UFS). There can be many reasons why you want to install to an SD card:

• You want to swap an installation between different phones.
• The **installation to internal memory might be broken**.
• For old versions: The UFS implementation might be broken for your combination of kernel and device and lead to IO errors.

Before proceeding you must have installed the same version to the internal memory, as described above, but flashing the rootfs.img should be left out (can lead to confusion with the root image that will be installed to the SD card). The steps for installing to an SD card (recommended at least 16 GB):

• On a PC, add a partition number 1 with filesystem ext4 to your SD card.

• Convert the root image from sparse to non-sparse format: simg2img mobian-<processor>-phosh-YYYYMMDD.rootfs.img mobian-<processor>-phosh-YYYYMMDD.rootfs.raw

• Write the .raw file to partition 1, determine which letter you should use as N in sdN1 to access the mentioned SD card: sudo dd if=mobian-<processor>-phosh-YYYYMMDD.rootfs.raw of=/dev/sdN1 bs=1M status=progress

• Move the SD card from the PC to the phone.
• Start the phone.