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

From postmarketOS
Jump to navigation Jump to search
(Add info about OpenRC not logging)
Line 64: Line 64:
 
Turning on OpenRC logging does not produce any log files in /var/log on sysroot partition, which suggests that either switch_root and call to /sbin/init fails,
 
Turning on OpenRC logging does not produce any log files in /var/log on sysroot partition, which suggests that either switch_root and call to /sbin/init fails,
 
or OpenRC fails on very early stage.
 
or OpenRC fails on very early stage.
 +
 +
== Development notes ==
 +
=== Kernels ===
 +
There are several candidate kernels for the port:
 +
 +
# Official kernel sources
 +
## [https://github.com/meizuosc/m576/tree/master 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.
 +
## [https://github.com/meizuosc/m576/tree/ubuntu Ubuntu branch]. This branch seem to contain kernel actually used in more recent official Android releases (3.10.100) at least till commit f866ad068f11fb5e68ff87901346483945972ae9. After that Ubuntu-specific patches as well as generic bugfixes come.
 +
## 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 [https://github.com/meizuosc/m576/issues/5 issue] requesting the release. Meizu is known to respond positively to such issues.
 +
# Unofficial sources
 +
## [https://github.com/ubports/kernel_turbo UBPorts kernel]. Based on Meizu Pro 5 branch. Contains Ubuntu Touch fixes and ports, mainly Android binder and anbox-specific patches.
 +
## [https://github.com/faust93/kernel_meizu_m576 faust93's kernel]. Kernel used in at least two unofficial Android roms. This kernel seems to be most up to date candidate, but contains a lot of patches from assorted sources and may be not very stable
  
 
<!-- add more sections below as necessary, e.g. Wifi, photos, ... -->
 
<!-- add more sections below as necessary, e.g. Wifi, photos, ... -->

Revision as of 14:51, 18 December 2018

Meizu Pro 5
[[|200px|alt=Meizu 5 Pro]]
Meizu 5 Pro
Manufacturer Meizu
Name Pro 5
Codename meizu-turbo
Released 2015
Category testing
Original software Android 5, Ubuntu Touch
Hardware
Chipset Samsung 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
Display
Broken
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. USB networking workds, telnet debugging hook lets log in at early stage before the reboot. All steps from init.sh until switch_root when entered manually in telnet debug shell seem to work without problem. The display is not working - blank black screen. If provoked to display an early splash (e.g. no rootfs), a black image is displayed with white lines on the left and top borders, as if it is a part of zoomed in image. Turning on OpenRC logging does not produce any log files in /var/log on sysroot partition, which suggests that either switch_root and call to /sbin/init fails, or OpenRC fails on very early stage.

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 kernel actually used in more recent official Android releases (3.10.100) at least till 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 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