Motorola Moto G5 Plus (motorola-potter)
USB Networking |
Works |
---|---|
Flashing |
Works |
Touchscreen |
Works |
Display |
Works |
WiFi |
Works |
Xwayland |
Works |
FDE | |
Mainline |
Works |
Battery |
Partial |
3D Acceleration |
Works |
Accelerometer |
Broken |
Audio |
Works |
Bluetooth |
Works |
Camera |
Broken |
GPS |
Broken |
Mobile data |
Broken |
SMS |
Broken |
Calls |
Broken |
USB OTG | |
Contents
Contributors
- chin123
- uknown
Maintainer(s)
- uknown
How to enter flash mode
- Power + Volume Down buttons
Installation
$ pmbootstrap flasher flash_rootfs
$ pmbootstrap flasher boot
Photos
Device status with the mainline-ish kernel
board_id = <0x46, 0x83a0>
. It should work on other devices, but may not.la.um.6.6.r1-V2
.Display
There are two panel supliers: Boe and Tianma. The panel will be selected at boot via lk2nd, based on the cmdline from the bootloader.
Boe
The Boe panel works as expected, with colours and backlight controls
Tianma
The Tianma panel also works as expected
Storage
Internal Storage
Works as expected.
SD Card
Works, but card detection is broken.
GPU
Works, but preemption is broken. See msm8953 status.
Touchscreen
Synaptics 3203B. Works as expected.
USB
ssh and telnet work, however OTG is currently broken (needs the charger to be enabled). Low power mode does not work (broken on downstream too). Until low power mode was disabled, ssh and telnet were unusable, failing to send data properly.
Battery
Reporting is done via the qcom-fg driver. However the charger has not been ported yet, so charging does not work.
NFC
NXP PN548. It is very similar to the already mainlined PN544, it just needs 2 extra clocks. However, enabling those clocks causes a hang.
LEDs
the front charging LED works with the atc-led driver (4 states, controlled via brightness: off, blink slow, blink fast, on)
WiFi
Works as expected, can connect to 2.4GHz and 5GHz 802.11n networks.
Bluetooth
Works, uses the same WiFi controller. Userspace may need additional tools installed to see the device. Also, the device doesn't power on by default, it must be manually powered on via bluetoothctl
Modem
The modem needs special firmware from /persist that is unique to each device, along with a patched tqftpserv. Follow the instructions User:TravMurav/Dual-Sim_QMI_draft to get the modem fully "ready". Experimental patches for IPA v2 on mainline exist, using those allows the modem to make/receive calls and send/receive SMS. Without IPA, the modem will crash and complain about missing IPA. Also, neither stock ofono nor ModemManager support QRTR based modems. An MR has been made for ModemManager, for ofono look at the MSM8953 status page on this wiki.
Modem boot process
The modem needs some data to be written to SMEM, lk2nd currently handles this. Following that, the modem is booted up by the kernel. Then the modem connects via QRTR to rmtfs and tqftpserv. It downloads the modem firmware from rmtfs. It makes TFTP requests for other files, which are handled via tqftpserv. The tqftserv files are where it derives the IMEI and other important data from. Following this, the modem application ID must be set (as it is a dual sim phone). Once that is done, the modem attempts to communicate with the IPA driver via QMI. After communicating with the IPA service, the modem is then "ready". It can be used with ofono or ModemManager.
Audio
Uses ADSP + speaker. Works as expected with ucm from the msm8916 alsa-ucm fork. There is however a mild hiss on headphones when no audio is playing.
Anything that isn't listed above can be assumed to not work.
See also: MSM8953 mainlining status
Links
- GSM Arena specifications page: https://www.gsmarena.com/motorola_moto_g5_plus-8453.php
- TWRP Recovery: https://twrp.me/motorola/motorolamotog5plus.html