Motorola Moto G6 Play (motorola-aljeter): Difference between revisions
Appearance
add note: no device package is available (currently mentioned only in 'see also') |
ValPackett (talk | contribs) m nora note |
||
(7 intermediate revisions by 7 users not shown) | |||
Line 2: | Line 2: | ||
{{note| There is no available motorola-aljeter device package}} | {{note| There is no available motorola-aljeter device package}} | ||
{{note| There are G6 Play variants (-jeter, USA?) that use the MSM8920/427/Adreno308 quad-core chipset. All variants apparently have SKU XT1922-x. Check /proc/cpuinfo via adb, or <code>fastboot getvar all</code>. According to Wikipedia, Snapdragon 427 and 430 are pin and software compatible.}} | |||
{{note| Lots of community unofficial ROMs have been shown to work with MSM8953 kernels, both in Jeter and Aljeter. Can we try to use the 8953 mainline kernel fork that's available then?}} | |||
{{note| According to downstream dts sources, jeter is almost entirely identical to [[Motorola Moto E5 (motorola-nora)|nora]], join #msm8937-mainline:kde.org on Matrix if you have this device}} | |||
{{Infobox device | {{Infobox device | ||
| manufacturer = Motorola | | manufacturer = Motorola | ||
Line 9: | Line 16: | ||
| imagecaption = | | imagecaption = | ||
| releaseyear = 2018 | | releaseyear = 2018 | ||
| originalsoftware = Android 8.0 Oreo | | originalsoftware = Android | ||
| chipset = Qualcomm | | originalversion = 8.0 Oreo | ||
| extendedversion = 9.0 Pie | |||
| chipset = Qualcomm Snapdragon 430 (MSM8937) | |||
| cpu = 1.4 GHz Octa-core Cortex-A53 | | cpu = 1.4 GHz Octa-core Cortex-A53 | ||
| gpu = Adreno 505 | | gpu = Adreno 505 | ||
Line 17: | Line 26: | ||
| memory = 2/3 GB | | memory = 2/3 GB | ||
| architecture = aarch64 | | architecture = aarch64 | ||
| type = handset | |||
<!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) --> | <!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) --> | ||
| status_usbnet = Y <!-- USB networking does work? then put Y here and delete this comment --> | | status_usbnet = Y <!-- USB networking does work? then put Y here and delete this comment --> | ||
Line 88: | Line 98: | ||
The [https://github.com/Hacker1245/linux-cedric mainline fork] for [[Motorola Moto G5 (motorola-cedric)]] should help with this. Need to investigate what other drivers are required. | The [https://github.com/Hacker1245/linux-cedric mainline fork] for [[Motorola Moto G5 (motorola-cedric)]] should help with this. Need to investigate what other drivers are required. | ||
MSM8953 kernels also seem to work just fine with both the jeter variation and the aljeter one, so that gives us the chance to use the [https://github.com/msm8953-mainline mainline fork] for that SoC without much issues | |||
== See also == | == See also == |
Latest revision as of 23:31, 19 January 2025
This device is still running on armv7, although the processor supports aarch64. If you own it, change it and test it that way. |
There is no available motorola-aljeter device package |
There are G6 Play variants (-jeter, USA?) that use the MSM8920/427/Adreno308 quad-core chipset. All variants apparently have SKU XT1922-x. Check /proc/cpuinfo via adb, or fastboot getvar all . According to Wikipedia, Snapdragon 427 and 430 are pin and software compatible. |
Lots of community unofficial ROMs have been shown to work with MSM8953 kernels, both in Jeter and Aljeter. Can we try to use the 8953 mainline kernel fork that's available then? |
According to downstream dts sources, jeter is almost entirely identical to nora, join #msm8937-mainline:kde.org on Matrix if you have this device |
![]() | |
Manufacturer | Motorola |
---|---|
Name | Moto G6 Play |
Codename | motorola-aljeter |
Released | 2018 |
Type | handset |
Hardware | |
Chipset | Qualcomm Snapdragon 430 (MSM8937) |
CPU | 1.4 GHz Octa-core Cortex-A53 |
GPU | Adreno 505 |
Display | 720x1440 |
Storage | 16/32 GB |
Memory | 2/3 GB |
Architecture | aarch64 |
Software | |
Original software | Android |
Original version | 8.0 Oreo |
Extended version | 9.0 Pie |
postmarketOS | |
Category | testing |
Pre-built images | no |
Flashing |
No data |
---|---|
USB Networking |
Works |
Internal storage |
No data |
SD card |
No data |
Battery |
No data |
Screen |
Works |
Touchscreen |
Works |
Multimedia | |
3D Acceleration |
No data |
Audio |
Partial |
Camera |
No data |
Camera Flash |
No data |
Connectivity | |
WiFi |
No data |
Bluetooth |
No data |
GPS |
No data |
NFC |
No data |
Modem | |
Calls |
No data |
SMS |
No data |
Mobile data |
No data |
Miscellaneous | |
FDE |
Works |
USB OTG |
No data |
HDMI/DP |
No data |
Sensors | |
Accelerometer |
No data |
Magnetometer |
No data |
Ambient Light |
No data |
Proximity |
No data |
Hall Effect |
No data |
Haptics |
No data |
Barometer |
No data |
Contributors
Users owning this device
- NHellFire (Notes: 3GB RAM + 32GB flash)
How to enter flash mode
- + buttons
Installation
- Bootloader must be unlocked
- Installation with
pmbootstrap flasher
should work, but currently only installation from recovery (TWRP) has been tested.
Known Issues
- No 3D acceleration (A505 is supported with freedreno in 3.18, so that needs testing)
- WiFi can scan, but connecting fails, looks like memory allocation problems
[00000003B8323C6F] [wpa_s] wlan: [E :HDD] wlan_hdd_cfg80211_set_ie Set UNKNOWN IE 3B [00000003B838995C] [VosMC] wlan: [E :PE ] limProcessSwitchChannelRsp: 4153: channelChangeReasonCode 1 status 0 [00000003B8423B78] [VosMC] wlan: [E :VOS] vos_mem_malloc: called with invalid arg 0 !!! [00000003B8423D34] [VosMC] wlan: [E :PE ] limStripOffExtCapIE: 89: Unable to allocate memory to store addn IE [00000003B84DEB4C] [VosMC] wlan: [E :HDD] 82:16:c4:XX:XX:XX connected to 2c:4d:54:XX:XX:XX [00000003B84DF135] [VosMC] wlan: [E :HDD] wlan(5) 2c:4d:54:XX:XX:XX Standalone [00000003B85F421C] [wpa_s] wlan: [E :SME] csrRoamOffloadScan: 17683: RSO command 2 lastSentCmd 2, RSO is out of sync in HOST-FWR wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:4d:54:XX:XX:XX reason=0 locally_generated=1 [00000003B8617525] [VosMC] wlan: [E :HDD] hdd_smeRoamCallback : Rssi on Disconnect : -53 [00000003B86526C8] [VosMC] wlan: [E :HDD] wlan: disconnected
- Audio only works through headphones
Mainline
The mainline fork for Motorola Moto G5 (motorola-cedric) should help with this. Need to investigate what other drivers are required. MSM8953 kernels also seem to work just fine with both the jeter variation and the aljeter one, so that gives us the chance to use the mainline fork for that SoC without much issues
See also