Difference between revisions of "Meizu Pro 5 (meizu-turbo)"

From postmarketOS
Jump to: navigation, search
(Kernels)
(Status: Removed framebuffer update information; outdated as msm-fb-refresher exists)
(Tags: Mobile edit, Mobile web edit)
 
(2 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
| releaseyear = 2015
 
| releaseyear = 2015
 
| originalsoftware = Android 5, Ubuntu Touch
 
| originalsoftware = Android 5, Ubuntu Touch
| chipset = Samsung Exynos 7420 Octa
+
| chipset = Exynos 7420 Octa
 
| cpu = Octa-core (4x2.1 GHz Cortex-A57 & 4x1.5 GHz Cortex-A53)
 
| cpu = Octa-core (4x2.1 GHz Cortex-A57 & 4x1.5 GHz Cortex-A53)
 
| gpu = Mali-T760MP8
 
| gpu = Mali-T760MP8
Line 16: Line 16:
 
| status_usbnet = Y
 
| status_usbnet = Y
 
| status_flashing = P
 
| status_flashing = P
| status_touch =  
+
| status_touch = Y
| status_screen = N
+
| status_screen = Y
 
| status_wifi =  
 
| status_wifi =  
 
| status_xwayland =  
 
| status_xwayland =  
Line 64: Line 64:
 
The device is accessible with telnet hook and via SSH (after additional procedure)
 
The device is accessible with telnet hook and via SSH (after additional procedure)
  
=== Procedure to get the device booting till the SSH ===
+
In order to workaround this problem you can compile a custom eudev package with this patch:
 +
https://github.com/elelel/eudev/commit/f27656ae371c0da23346cdccbd3dc28cf38d2794
 +
...and install it on the system
 +
 
 +
Current aport does not contain firmware blobs. Adding them might fix the eudev problem.
 +
 
 +
=== Getting device to boot in spite of uedev ===
  
 
Install PostmarketOS's telnet debug hook, log on with telnet, then  execute:
 
Install PostmarketOS's telnet debug hook, log on with telnet, then  execute:
Line 84: Line 90:
  
  
In chroot, comment out the offendig string, e.g. with sed replace.
+
If you want just to boot to SSH, in chroot, comment out the offendig string, e.g. with sed replace or vi in /etc/init.d/udev-trigger.rc
  
=== Getting the display to render frames ===
+
'''
Using MartinBraam's trick it is possible to make the display render frames like this:
+
udevadm trigger --type=devices --action=add
 
+
'''
while [ ! ]; do cat /sys/class/graphics/fb0/modes > /sys/class/graphics/fb0/mode; done
 
  
See https://github.com/postmarketOS/pmbootstrap/pull/66#issuecomment-306343779
+
If you want to make the device boot to UI as normal, you should install patched eudev package (see above) at this point and reboot.
  
 
== Development notes ==
 
== Development notes ==

Latest revision as of 17:23, 11 October 2019

Meizu Pro 5
[[|200px|alt=Meizu 5 Pro]]
Meizu 5 Pro
Manufacturer Meizu
Name Pro 5
Codename meizu-turbo
Released 2015
Original software Android 5, Ubuntu Touch
Hardware
Chipset Exynos 7420 Octa
CPU Octa-core (4x2.1 GHz Cortex-A57 & 4x1.5 GHz Cortex-A53)
GPU Mali-T760MP8
Display AMOLED, 16M colors
Storage 32GB/64GB
Memory 3GB/4GB
Architecture aarch64
Features
USB Networking
Works
Flashing
Partial
Touchscreen
Works
Display
Works
WiFi
Xwayland
FDE
Mainline
Battery
3D Acceleration
Accelerometer
Audio
Bluetooth
Camera
GPS
Mobile data
SMS
Calls
USB OTG



Contributors

elelel

Maintainer(s)

How to enter flash mode

The device has to be with unlocked bootloader. Android phone version has bootloader locked by default. Locked bootloader may be unlocked with a Beta FlymeOS image for the international phone version. International firmware can be flashed to Chinese phone if one changes phone's id (possible with a 5.1.x Chinese firmware, root and a hex editor).


Press volume down and power while turning on to get into fastboot mode.

Installation

Current pmbootstrap utility assumes that boot partition is always named 'boot' on fastboot devices. This device's boot partition has 'bootimg' label. Because of that boot partition must be either flashed directly with fastboot utility, or pmbootstrap config source code has to be fixed.

Status

Currently when turned on, the device enters reboot loop. The reboot is triggered by the line:

udevadm trigger --type=devices --action=add

The device is accessible with telnet hook and via SSH (after additional procedure)

In order to workaround this problem you can compile a custom eudev package with this patch: https://github.com/elelel/eudev/commit/f27656ae371c0da23346cdccbd3dc28cf38d2794 ...and install it on the system

Current aport does not contain firmware blobs. Adding them might fix the eudev problem.

Getting device to boot in spite of uedev

Install PostmarketOS's telnet debug hook, log on with telnet, then execute:

. init_functions.sh
mount_boot_partition
extract_initramfs_extra /boot/initramfs-*-extra
start_charging_mode
wait_root_partition
resize_root_partition
unlock_root_partition
resize_root_filesystem
mount_root_partition
mount -o remount,rw /dev/mapper/sda41p2 /sysroot
mount -t proc proc /sysroot/proc
mount -t sysfs sys /sysroot/sys
chroot /sysroot


If you want just to boot to SSH, in chroot, comment out the offendig string, e.g. with sed replace or vi in /etc/init.d/udev-trigger.rc

udevadm trigger --type=devices --action=add

If you want to make the device boot to UI as normal, you should install patched eudev package (see above) at this point and reboot.

Development notes

Kernels

There are several candidate kernels for the port:

  1. Official kernel sources
    1. Android branch. This branch seem to contain the very first kernel used for the earliest FlymeOS 4.x ROM. It is reported to be uncomplete, in particular, it misses Meizu proprietary sources for power management.
    2. Ubuntu branch. This branch seem to contain kernell for Android release updated to 3.10.100 in commit f866ad068f11fb5e68ff87901346483945972ae9. After that Ubuntu-specific patches as well as generic bugfixes come.
    3. Android 7 kernel, not released. Kernels from previous two links were only used in very early official ROMs. Later kernel sources were not realeased. There is a Github issue requesting the release. Meizu is known to respond positively to such issues.
  2. Unofficial sources
    1. UBPorts kernel. Based on Meizu Pro 5 branch. Contains Ubuntu Touch fixes and ports, mainly Android binder and anbox-specific patches.
    2. faust93's kernel. Kernel used in at least two unofficial Android roms. This kernel, probably based on CM14.1, seems to be most up to date candidate, but contains a lot of patches from assorted sources and may be not very stable


See also

Initial merge request