Xiaomi Redmi 6A (xiaomi-cactus)

From postmarketOS
Xiaomi Redmi 6A
Plasma Desktop
Plasma Desktop
Manufacturer Xiaomi
Name Redmi 6A
Codename xiaomi-cactus
Released 2018
Category testing
Pre-built images no
Original software Android (MIUI)
Original version 9
Hardware
Chipset MediaTek Helio A22 (MT6761)
CPU Quad-core 2.0 GHz Cortex-A53
GPU PowerVR GE8320
Display 720 x 1440 IPS
Storage 16 GB
Memory 2 GB
Architecture AArch64
Features
USB Networking
Works
Flashing
Works
Touchscreen
Works
Display
Works
WiFi
FDE
Mainline
Battery
3D Acceleration
Audio
Bluetooth
Camera
GPS
Mobile data
Internal storage
SMS
Calls
USB OTG
Sensors
Accelerometer
Magnetometer
Ambient Light
Proximity
Hall Effect
Barometer
Power Sensor
Misc
Built-in DVB
Camera Flash
Keyboard
Touchpad
USB-A
HDMI/DP
Ir TX
Ir RX
Stylus
Memory Card
Haptics
Ethernet
FOSS bootloader


Contributors

  • jdr

Maintainer(s)

  • jdr

Users owning this device


How to enter flash mode

  • Shutdown the phone completely
  • Press Volume down(-) and Power button simultaneously to enter the fastboot mode.


Bootloader original status

Installation

The following steps boots postmarketOS.

  • pmbootstrap flasher flash_rootfs
  • pmbootstrap flasher flash_kernel
  • pmbootstrap flasher boot

Plasma Mobile

Need to modify the file /usr/bin/startplasmamobile

Add --framebuffer --fb-device /dev/fb0 to arguments of startplasma-wayland

Like this:

startplasma-wayland --framebuffer --fb-device /dev/fb0 --xwayland --lockscreen --inputmethod maliit-keyboard --exit-with-session=/usr/lib/libexec/startplasma-waylandsession

This ensures that the Plasma Mobile is rendered using a frame buffer.

Current boot status

Currently (Linux 4.9.117, edge, 01 Nov 2023) on Plasma Mobile (both using framebuffer and not), Gnome Mobile and Phosh phone boots up, successfully shows loading animation, resizes system partition on first boot, starts SSHd (so you can SSH into) but after that loading animation stops and desktop environment doesn't show up.

Xfce4 works out-of-the-box.

Here is an output of startplasma-wayland:

qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
kdeinit5: Communication error with launcher. Exiting!
Error: could not determine $DISPLAY.
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" () exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.

See also