Jump to content

Motorola Z Play (motorola-addison): Difference between revisions

From postmarketOS Wiki
Pat (talk | contribs)
No edit summary
Line 1: Line 1:
{{Infobox device
{{Infobox device
| manufacturer = Motorola
| manufacturer = Motorola
| name = Z Play
| name = Moto Z Play
| codename = motorola-addison
| codename = motorola-addison
| image = File:motorola-addison.jpg
| image = File:motorola-addison.jpg
| imagecaption = CHANGE_ME
| imagecaption = Motorola Moto Z Play
| releaseyear = 2016
| releaseyear = 2016
| originalsoftware = Android 6.0.1 - 8.0
| originalsoftware = Android 6.0.1, up to Android 8.0
| chipset = Qualcomm MSM8953 Snapdragon 625
| chipset = Qualcomm MSM8953 Snapdragon 625 (14 nm)
| cpu = Octa-core 2.0 GHz Cortex-A53
| cpu = Octa-core 2.0 GHz Cortex-A53
| gpu = Adreno 506
| gpu = Adreno 506
| storage = 32 GB
| storage = 32GB
| display = 1080x1920 Super AMOLED
| display = 1080 x 1920 Super AMOLED
| memory = 3 GB
| memory = 3GB
| architecture = aarch64
| architecture = aarch64
<!-- 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 = <!-- USB networking does work? then put Y here and delete this comment -->
| status_usbnet = Y
| status_flashing = <!-- Flashing with "pmbootstrap flasher" works? Put Y here. It works the same for everything coming below. -->
| status_flashing = Y
| status_touch = <!-- Touch screen is working? You can also answer these questions with P for partially. -->
| status_touch = <!-- Touch screen is working? You can also answer these questions with P for partially. -->
| status_screen = <!-- The display is working? -->
| status_screen = N
| status_wifi = <!-- Wireless network works? -->
| status_wifi = <!-- Wireless network works? -->
| status_xwayland = <!-- Showing X11 applications in a Wayland compositor (Weston, KWin, ...) works? -->
| status_xwayland = <!-- Showing X11 applications in a Wayland compositor (Weston, KWin, ...) works? -->
| status_fde = <!-- When installing with full disk encryption, can you type in the password with the on screen keyboard? -->
| status_fde = <!-- When installing with full disk encryption, can you type in the password with the on screen keyboard? -->
| status_mainline = <!-- Instead of a Linux kernel fork, it is possible to run mainline. -->
| status_mainline =  
| status_battery = <!-- Charging the battery with charging-sdl is possible -->
| status_battery = <!-- Charging the battery with charging-sdl is possible -->
| status_3d = <!-- Hardware accelerated 3D graphics (e.g. with freedreno) -->
| status_3d = <!-- Hardware accelerated 3D graphics (e.g. with freedreno) -->
Line 33: Line 33:
| status_sms = <!-- Sending and receiving short messages works as intended. -->
| status_sms = <!-- Sending and receiving short messages works as intended. -->
| status_calls = <!-- Talking to other people over the cellular network. -->
| status_calls = <!-- Talking to other people over the cellular network. -->
| status = <!-- Text displayed in the "not booting" table on the Devices page , e.g "kernel compiles, doesn't boot" -->
| status = boots
| booting = no <!-- The device is booting at all, can be yes/no *IMPORTANT* -->
| booting = yes


<!-- you can also use these lines if you need to:
<!-- you can also use these lines if you need to:
if the device haven't originally ran Android OS, e.g. Nokia N900
| n-android =  ✔
Version of the kernel that pmos is running
Version of the kernel that pmos is running
| pmoskernel = 3.x.x
| pmoskernel = 3.18.120
see Unixbench page on wiki
see Unixbench page on wiki
| whet_dhry = 0.0
| whet_dhry = 0.0
Line 47: Line 49:


== Contributors ==
== Contributors ==
* pat
* pat  
* ChrispyStrips


== Maintainer(s) ==
== Maintainer(s) ==
Line 61: Line 64:


== How to enter flash mode ==
== How to enter flash mode ==
* Power + Volume Down buttons


== Build ==
* hold Power + Volume Down button
boot.img must be less than 16MB to fit on boot partition. {{issue|126|pmbootstrap}} for possible strategies.


Kernel compiles for armv7(Android Roms were armv7).
== Installation ==
to unlock the bootloader, follow the instructions [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a here], then follow the [[Installation guide]]


Trying to build for aarch64 errors out:
== See also ==
<pre>
* {{MR|1577|pmaports}} Initial merge request
aarch64-alpine-linux-musl-ld: drivers/built-in.o: in function `f_midi_transmit':
/home/pmos/build/src/msm-3.18-60a8d8af3751b9dc22894fe68b3964ea94ae7888/out/../drivers/usb/gadget/function/f_midi.c:582: undefined reference to `free_ep_req'
/home/pmos/build/src/msm-3.18-60a8d8af3751b9dc22894fe68b3964ea94ae7888/out/../drivers/usb/gadget/function/f_midi.c:582:(.text+0x2fafc0): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `free_ep_req'
aarch64-alpine-linux-musl-ld: drivers/built-in.o: in function `f_midi_complete':
/home/pmos/build/src/msm-3.18-60a8d8af3751b9dc22894fe68b3964ea94ae7888/out/../drivers/usb/gadget/function/f_midi.c:283: undefined reference to `free_ep_req'
/home/pmos/build/src/msm-3.18-60a8d8af3751b9dc22894fe68b3964ea94ae7888/out/../drivers/usb/gadget/function/f_midi.c:283:(.text+0x312c90): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `free_ep_req'
aarch64-alpine-linux-musl-ld: drivers/built-in.o: in function `arm_smmu_add_device':
/home/pmos/build/src/msm-3.18-60a8d8af3751b9dc22894fe68b3964ea94ae7888/out/../drivers/iommu/arm-smmu.c:2827: undefined reference to `msm_pcie_configure_sid'
/home/pmos/build/src/msm-3.18-60a8d8af3751b9dc22894fe68b3964ea94ae7888/out/../drivers/iommu/arm-smmu.c:2827:(.text+0x5f7e50): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `msm_pcie_configure_sid'
</pre>
Used 32 bit config. Try again with https://github.com/Alberto97/android_kernel_motorola_msm8953/tree/pie/arch/arm64/configs


== Installation ==
<!-- add more sections below as necessary, e.g. WiFi, photos, ... -->
pmbootstrap flasher boot not working.
Flashing kernel returns Image not signed or corrupt
== See also ==
<!--
Link to related GitLab issues or merge requests like the following (replace CHANGEME with the ID, e.g. 1234):
* {{MR|CHANGEME|pmaports}} Initial merge request
* {{issue|CHANGEME|pmaports}} Some related issue
You can also add normal web links:
* [https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100 Replicant wiki page]
-->
<!--
<!--
If you manage to get your device packages merged, uncomment links below.
If you manage to get your device packages merged, uncomment links below and change DEVICE_CODENAME with the actual one.
* {{Device package|motorola-addison}}
* {{Device package|DEVICE_CODENAME}}
* {{Kernel package|motorola-addison}}
* {{Kernel package|DEVICE_CODENAME}}
-->
-->

Revision as of 18:56, 15 September 2020

Motorola Moto Z Play
Motorola Moto Z Play
Motorola Moto Z Play
Manufacturer Motorola
Name Moto Z Play
Codename motorola-addison
Released 2016
Hardware
Chipset Qualcomm MSM8953 Snapdragon 625 (14 nm)
CPU Octa-core 2.0 GHz Cortex-A53
GPU Adreno 506
Display 1080 x 1920 Super AMOLED
Storage 32GB
Memory 3GB
Architecture aarch64
Software
Original software Android 6.0.1, up to Android 8.0
postmarketOS
Category testing
Pre-built images no
Features
Flashing
Works
USB Networking
Works
Internal storage
No data
SD card
No data
Battery
No data
Screen
Broken
Touchscreen
No data
Multimedia
3D Acceleration
No data
Audio
No data
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
No data
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

  • pat
  • ChrispyStrips

Maintainer(s)

Users owning this device


How to enter flash mode

  • hold Power + Volume Down button

Installation

to unlock the bootloader, follow the instructions here, then follow the Installation guide

See also