Xiaomi Redmi 5 Plus (xiaomi-vince): Difference between revisions
m Slightly resize photo |
Some changes I forgot to add last week, and new FDE section |
||
Line 21: | Line 21: | ||
| status_wifi = Y | | status_wifi = Y | ||
| status_xwayland = Y | | status_xwayland = Y | ||
| status_fde = | | status_fde = P | ||
| status_mainline = N | | status_mainline = N | ||
| status_battery = Y | | status_battery = Y | ||
Line 39: | Line 39: | ||
| pmoskernel = 4.9.305 | | pmoskernel = 4.9.305 | ||
}} | }} | ||
{{Based on SoC|Qualcomm_Snapdragon_450/625/626/632_(MSM8953)|Snapdragon 625}} | |||
== Maintainer(s) == | == Maintainer(s) == | ||
Line 53: | Line 54: | ||
== Installation == | == Installation == | ||
Here's how to boot pmOS via fastboot: | Here's how to boot pmOS via fastboot: | ||
Line 77: | Line 77: | ||
You can do it in many ways: | You can do it in many ways: | ||
=== As a flag during PMOS installation: === | |||
<code> | |||
Follow the standard [[Installation guide]], and during <code>pmbootstrap install</code> step, use <code>--add triggerhappy</code> flag | |||
<code> --add triggerhappy</code> | |||
=== As a package on running device: === | |||
<code>$ sudo apk add triggerhappy</code> | |||
Type in device terminal: <code>$ sudo apk add triggerhappy</code> | |||
{{note|On both cases you always need to enable the triggerhappy daemon with: <code>$ sudo rc-update add triggerhappy default</code>}} | |||
<code> | == FDE == | ||
Encryption works fine, but [https://wiki.postmarketos.org/wiki/Osk-sdl osk-sdl] has some issues with <code>pixelformat</code> modes. | |||
I recommend to test [https://wiki.postmarketos.org/wiki/Unl0kr Unl0kr], because its made on LVGL, so it shouldn't have the same problems that osk-sdl encounters with directfb SDL2 backend. | |||
{{note|Actually, osk-sdl is working ok(ish) with <code>pixelformat</code> argument set in DFBARGS to <code>ABGR</code>, but I couldn't get this to work in initramfs and I don't think it is a proper way to do this.}} | |||
== Smart Speaker == | == Parts == | ||
=== Smart Speaker === | |||
To use the speaker, the device relies on: | To use the speaker, the device relies on: | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 100: | Line 105: | ||
|} | |} | ||
== Fingerprint == | === Fingerprint === | ||
Two drivers are available within downstream kernel | Two drivers are available within downstream kernel | ||
Line 114: | Line 119: | ||
|} | |} | ||
== Sensors == | === Sensors === | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 148: | Line 153: | ||
== See also == | == See also == | ||
* {{MR|1249|pmaports}} Initial merge request | * {{MR|1249|pmaports}} Initial merge request | ||
* [https://github.com/M0Rf30/msm8953-snd-card-mtp ALSA msm8953-snd-card-mtp UCM] | * [https://github.com/M0Rf30/msm8953-snd-card-mtp ALSA msm8953-snd-card-mtp UCM] | ||
* [https://github.com/GhostMaster69-dev/android_kernel_xiaomi_vince Downstream kernel source] | |||
* {{Device package|xiaomi-vince}} | * {{Device package|xiaomi-vince}} | ||
* {{Kernel package|xiaomi-vince}} | * {{Kernel package|xiaomi-vince}} | ||
* {{Firmware package|xiaomi-vince}} |
Revision as of 22:55, 25 March 2022
![]() Xiaomi Redmi Note 5 / 5 Plus | |
Manufacturer | Xiaomi |
---|---|
Name |
Redmi Note 5 / 5 Plus |
Codename | xiaomi-vince |
Released | 2017 |
Hardware | |
Chipset | Qualcomm MSM8953 Snapdragon 625 |
CPU | Octa-core Cortex-A53 2 GHz |
GPU | Adreno 506 |
Display | 2160x1080 (403 PPI) IPS |
Storage | 32/64 GB |
Memory | 3/4 GB |
Architecture | aarch64 |
Software | |
Original software | Android 8.1 |
postmarketOS | |
Category | testing |
Pre-built images | no |
Mainline | no |
postmarketOS kernel | 4.9.305 |
Flashing |
Works |
---|---|
USB Networking |
Works |
Internal storage |
No data |
SD card |
No data |
Battery |
Works |
Screen |
Works |
Touchscreen |
Works |
Multimedia | |
3D Acceleration |
Broken |
Audio |
Works |
Camera |
Broken |
Camera Flash |
No data |
IR TX |
Broken |
Connectivity | |
WiFi |
Works |
Bluetooth |
Broken |
GPS |
Broken |
Modem | |
Calls |
Broken |
SMS |
Broken |
Mobile data |
Broken |
Miscellaneous | |
FDE |
Partial |
USB OTG |
Works |
HDMI/DP |
No data |
Sensors | |
Accelerometer |
Broken |
Magnetometer |
No data |
Ambient Light |
No data |
Proximity |
No data |
Hall Effect |
No data |
Haptics |
No data |
Barometer |
No data |
This device is based on the Snapdragon 625. See the SoC page for common tips, guides and troubleshooting steps |
Maintainer(s)
- M0Rf30
Users owning this device
- 4PERTURE
- Bazsalanszky
- Bczeman
- Kasesag (Notes: Runs pmOS, main experimental Mobile Linux device.)
- KenOokamiHoro (Notes: 4+64GB variant, Dual boot with Pixel Experience 12)
- M0Rf30
- Tecncr
- Tfuxu (Notes: Old daily driver, now used only for experimenting)
- V1M4dr0n (Notes: LOS main & pmOS on SDCard)
How to enter flash mode
- Turn off the device
- Press + to enter fastboot
Installation
Here's how to boot pmOS via fastboot:
- Install to a SD card with
$ pmbootstrap install --sdcard=/dev/sdX
- Insert the SD card into the device
- Connect the device to your PC
- Enter the fastboot mode
- Finally, boot pmOS:
$ pmbootstrap flasher boot
or
- Enter the fastboot mode
- Flash system
$ pmbootstrap flasher flash_system
- Flash kernel
$ pmbootstrap flasher flash_kernel
- Finally, reboot into pmOS:
$ fastboot reboot
Audio
To enable audio you need to install triggerhappy. You can do it in many ways:
As a flag during PMOS installation:
Follow the standard Installation guide, and during pmbootstrap install
step, use --add triggerhappy
flag
As a package on running device:
Type in device terminal: $ sudo apk add triggerhappy
On both cases you always need to enable the triggerhappy daemon with: $ sudo rc-update add triggerhappy default |
FDE
Encryption works fine, but osk-sdl has some issues with pixelformat
modes.
I recommend to test Unl0kr, because its made on LVGL, so it shouldn't have the same problems that osk-sdl encounters with directfb SDL2 backend.
Actually, osk-sdl is working ok(ish) with pixelformat argument set in DFBARGS to ABGR , but I couldn't get this to work in initramfs and I don't think it is a proper way to do this. |
Parts
Smart Speaker
To use the speaker, the device relies on:
Vendor | Model |
---|---|
Texas Instruments | tas2557 (some useful commits 1)
Seems to be very similar to tas2559 |
Fingerprint
Two drivers are available within downstream kernel
Vendor | Model |
---|---|
Fingerprint Cards AB | FPC1020 (some useful commits 12) |
Goodix | GF3208 |
Sensors
Type | Vendor | Model |
---|---|---|
Accelerometer / Gyroscope | STMicroelectronics | LSM6DS3 |
Magnetometer / Compass | Asahi Kasei | AK09918 1 |
Ambient Light | Liteon Opto | LTR579 ALSPS |
Hall | ROHM Semiconductor | BU52061NVX |
Serial UART
TODO: This section needs further testing |
Getting UART output on this device should be pretty straightforward, because pins for serial transfer (TX and RX) are exposed directly on motherboard and are even labeled.
See also: Serial debugging