nyuuzyou/wikis huggingface dataset:
Acer Liquid Z330 (acer-t01)

== Variants ==
There are also 3G / Windows Phone variants:
* Acer Liquid Z330 (Android LTE)
* Acer Liquid Z320 (Android 3G)
* Acer Liquid M330 (Windows Phone LTE)
* Acer Liquid M320 (Windows Phone 3G)
== Users owning this device ==
== Installation ==
== Panel Display ==
Using simple-framebuffer instead of DRM panel driver due to missing MDP3 support in mainline Linux for now.
Backlight is not controlled by the panel.
Sometimes the panel doesn't show anything.
== Touchscreen ==
(phoc:3653): phoc-wlroots-CRITICAL **: 09:03:35.192: [libinput] event3 - MStar TouchScreen: client bug: event processing lagging behind by 63ms, your system is too slow
Touchscreen doesn't work in Phosh.
== Audio ==
== GPS ==
== Proximity Sensor ==
== See also ==
* Initial merge request
* 
* 
== References ==
Acer Liquid Zest 4G (acer-t07)

== Contributors ==
* Erik D. (erikd256)
== Users owning this device ==
== How to enter flash mode ==
Boot up while pressing volume up key, then navigate to the fastboot entry (keep pressing volume up key and see the arrow moving across the menu) and press volume down.
== How to unlock bootloader ==
Go into fastboot mode, and type in your host device fastboot oem unlock.
== Installation ==
* Normal install with pmbootstrap, until the flashing step!
* Go into fastboot mode
* Flash only the boot.img using pmbootstrap flasher flash_kernel (If this fails try with: fastboot flash:raw boot /tmp/postmarketOS-export/boot.img). 
* Flashing system.img is impossible due to many errors. (It could also be the loose USB-Connector of my phone, I can't say this with 100% certainity)
* Afterwards, run pmbootstrap install --sdcard=/dev/sdX (replace /dev/sdx with your number of the sdcard). 
* Put the SD-Card in your device and boot up.
== See also ==
Acer support page
Acer travelmate I B

== Contributors ==
* Nugget095
== Users owning this device ==
== downloading ==
*go to downloads -> 
*scroll down to generic images.
*get the x86_64 generic image by clicking the edge button
*get whatever client you want (gnome is reccomended)
=== flashing to usb or others ===
*windows: balena, unetbootin.
*linux: disks, balena
*choose the image you downloaded.
*choose the target (usb or others)
*flash
(disks tutorial is going to be added)
 
== BIOS ==
=== entering BIOS ===
* click the power button, and than quickly hold or spam F2 button.
* enter your password, or not depending if you have one.
=== BIOS options ===
* go to the Boot section
* disable secure boot
* enable boot menu if it isnt there.
* change the boot preference and set the usb in the first place.
* navigate to exit and choose "exit and save changes"
== Installation ==
*press F12 to get to boot menu
*choose the USB
*and your booted in the postmarketOS live
(installing to HDD/SSD will be added soon.)
== Known issues ==
camera is sometimes working sometimes not, perhaps this is due to faulty driver or conflicting drivers.
== See also ==
Add a new architecture to postmarketOS

If you would like to port to a device architecture, that is supported by Alpine, but not by postmarketOS, you can bootstrap the architecture in pmOS with the following steps. As usually, please correct this manual if you find errors or outdated information in it.
1. To avoid querying the pmOS repos for the new architecture and therefore failing, run: pmbootstrap config mirrors.pmaports none and pmbootstrap config mirrors.systemd none
2. Add the architecture to build_device_architectures in pmb/core/arch.py and add it to the test cases in pmb/core/test_arch.py.
3. Create aports for cross compilation (replace armhf with your new architecture):
$ pmbootstrap aportgen gcc-armhf musl-armhf
4. Try to build one package for the new architecture. pmbootstrap will build necessary packages first, such as the cross compiler. If you get any Python errors, you might need to adjust architecture mappings in pmb/core/arch.py.
$ pmbootstrap build hello-world --arch=armhf
5. Build your device's linux-... package.
$ pmbootstrap build linux-samsung-i9100
6. Do a full installation:
$ pmbootstrap install
If everything worked out, please make one separate merge request to add the new architecture and mention there which device you have ported. After that merge request is through, make another one for the device.
Category:Guide
Alcatel Idol 3 4.7" (alcatel-idol347)

== Contributors ==
* Vknecht
== Maintainer(s) ==
* Vknecht
== Users owning this device ==
== How to enter flash mode ==
* Recovery: Power on the device with both and buttons.
* Fastboot: Power on the device with both and buttons.
Stock fastboot was removed on update from Android 5/Lollipop to 6/MarshMallow.
Installing lk2nd is required to run mainline kernel anyway.
== Installation ==
# Install lk2nd (alternative bootloader that provides a standard fastboot interface) to boot partition using either:
#* Alcatel Flasher tool
#* emmcdl or edl with Idol34_7_NPRG7627.bin lk2nd-msm8916.img
#* dd command from TWRP
# Follow Qualcomm_Snapdragon_410/412_(MSM8916)#Installation.
== Pictures ==
File:Alcatelidol347_phosh.jpg|thumb|left|Alcatel Idol 3 4.7" running Phosh
== See also ==
* Initial merge request
* 
* XDA thread Fastboot instructions
Alcatel Idol 3 5.5" (alcatel-idol3)

== Contributors ==
* Vknecht
== Maintainer(s) ==
* Vknecht
== Users owning this device ==
== How to enter flash mode ==
* Recovery: Power on the device with both and buttons.
* Fastboot: Power on the device with both and buttons.
Stock fastboot was removed on update from Android 5/Lollipop to 6/MarshMallow.
Installing lk2nd is required to run mainline kernel anyway.
== Installation ==
# Install lk2nd (alternative bootloader that provides a standard fastboot interface) to boot partition using either:
#* Alcatel Flasher tool
#* emmcdl with Idol35_5_NPRG7627.bin or edl.py
#* dd command from TWRP
# Follow Qualcomm_Snapdragon_410/412_(MSM8916)#Installation.
== Touchscreen ==
There are two touchscreen variants:
* edt-ft5x06
* synaptics / rmi4
Currently, only the edt-ft5x06 one is enabled.
If you have the Synaptics one, you'll have to edit the DTS file to disable edt-ft5x06 and enable synaptics, then rebuild the kernel package.
This shall be solved in lk2nd in the future.
== See also ==
* Initial merge request
*
Alcatel MyFlip (alcatel-gflip2)

== Overview ==
The Alcatel MyFlip, otherwise known as the Alcatel Go Flip 2, is an entry-level Feature phone featuring the clamshell design. This phone was the first KaiOS phone to support the Kai Store in North America.
== Contributors ==
Justsoup
== Users owning this device ==
== How to enter flash mode ==
Fastboot is most likely locked on this device and rooting has not been found yet either. This will most likely either require edl or some workaround to gain root access using adb.
== Installation ==
This device has not been ported yet
== EDL ==
Research is being done on how to flash lk2nd to the recovery partition to get a standard fastboot interface. The most promising outcome seems to be using the Qualcomm Emergency Download Mode of the SOC to directly write a lk2nd image.
To gain access to EDL mode, there is most likely a way using hardware buttons, but these have not been found yet. The most direct mode is shorting the EDL point on the motherboard, as circled above, to ground.
== See also ==
EDL Information
Alcatel OneTouch Pixi 4 (5) 5010D (alcatel-5010d)

== Contributors ==
* Er2
== Maintainer(s) ==
* Er2
== Users owning this device ==
== How to enter flash mode ==
To enter recovery, hold (until logo appears) and buttons.
If you want to enter fastboot (can't flash system), go .
== Installation ==
# Install pmbootstrap.
# pmbootstrap init
#* Vendor must be alcatel
#* Device codename must be 5010d
# pmbootstrap install --android-recovery-zip
# pmbootstrap flasher --method adb fastboot
# Go to 
# Connect device to your PC
== See also ==
* Initial merge request
Alcatel OneTouch Pop 7S (alcatel-pop7lte)

== Contributors ==
* thejsa
== Maintainer(s) ==
* thejsa
== Users owning this device ==
== How to enter flash mode ==
I have as yet been unable to find a way to directly enter fastboot on this device, nor have I been able to find any hint of custom Android ROM / custom recovery development for this or info on sites like XDA-Developers.
However, one is able to reboot into the bootloader from a running Android system through ADB by running `adb reboot-bootloader` on one's host system.
== Installation ==
In theory you should be able to directly install onto the device, but due to the aforementioned difficulties getting into fastboot I have not tried this. All of my testing has been undertaken by installing onto an SD card (pmbootstrap install --sdcard [device]) and directly booting the kernel using pmbootstrap flasher boot.
== Bootloader unlocking ==
I was able to unlock the bootloader on my device with a simple fastboot oem unlock, although I did not test if this works if the device is still carrier locked (in the UK, these devices were mainly sold cheaply -- and carrier locked -- by EE and O2; I was able to obtain a carrier unlock code for my device for under £1 from an eBay seller as EE is slow and charges £9 at time of writing).
== Touchscreen ==
The touchscreen in this device uses a FocalTech FT5436 controller - firmware is compiled into the kernel, is required for the driver to build, and is stored as .i files in the kernel tree in drivers/input/touchscreen. (I agree, this is yucky.)
tslib and libinput recognise the screen and tslib calibration seems to recognise touch inputs, but Weston does not (suspected driver issues?)
Touch input seems to work in xfce4, however (at least for moving the cursor), although incorrectly rotated (needs calibration).
== WiFi ==
WiFi firmware is packaged but the prima/pronto driver appears to be missing in Alcatel's kernel tree :-(
== See also ==
* Initial merge request
Alcatel One Touch Pop C1 (alcatel-yaris35-gsm)

== Contributors ==
== Users owning this device ==
== How to enter flash mode ==
=== Using mtkclient ===
Turn off the phone, start mtkclient, attach usb cable. Works without battery too.
=== Using spflashtool ===
==== spflashtool for linux ====
Use version 5.2032.00, later versions no longer work with MT6572.
=== Using recovery ===
Seems that there is no button combination to enter recovery during boot. It's possible to enter recovery by issuing adb reboot recovery command. However, recovery is locked and only accepts signed archives.
To install unlocked recovery:
* Root the phone with framaroot, use Barahir exploit.
* Use rashr to install new recovery, such as TWRP (use recovery image specially built for this phone).
== Installation ==
Use pmbootstrap to build your own installation image.
$ pmbootstrap init
$ pmbootstrap install --fde
== See also ==
* Modified kernel source (first commit aa7c7c44 contains original source)
* Another original kernel source archive
* Tag on xdaforums
* CyanogenMod 12.1 for Alcatel One Touch Pop C1
All devices

__NOTOC__ __NOCACHE__
All the devices in this table can at least boot postmarketOS. To monitor boot progress, you must be able to receive output from the screen, a network adapter, or a serial port. If you verify that a device not on this list boots postmarketOS, please create a page for the device and make a merge request.
Status columns are described further below. In particular, Mainline* refers to (close to) mainline and is written this way to save screen space in this big table.
=== Status Legend ===
Code	Meaning
Y 	Yes, fully implemented
P 	Partially implemented
N 	Not working yet
 	Untested
- 	Not applicable -- device does not have feature
=== Status Columns ===
Column 	Meaning
USB Net 	After connecting the device with USB to your PC, you can connect to it via telnet (initramfs) or SSH (booted system).
Flashing 	It is possible to flash the device with pmbootstrap flasher.
Touch 	Touching the screen is recognized properly.
Screen 	The device's display is working.
Wifi 	Connecting to wireless network is possible.
XWayland 	Showing X11 applications in a Wayland compositor (Weston, KWin, ...) works.
FDE 	Full disk encryption and unlocking with osk-sdl.
Mainline* 	Runs a (Close to) Mainline kernel, not an Android downstream kernel.
Battery 	Charging the battery with charging-sdl is possible (this seems to be largely untested, please update your device's column if charging is possible).
3D 	Hardware accelerated 3D graphics
IMU 	The sensor that measures proper acceleration works.
Audio 	Using the device's speakers/headphone jack works.
Bluetooth 	It's possible to pair and use other devices via the bluetooth protocol.
Camera 	Taking photos and videos works.
GPS 	The Global Positioning System sensor works.
Mobile Data	Connecting to the Internet via cellular network.
SMS 	Sending and receiving short messages works as intended.
Calls 	Talking to other people over the cellular network.
== Non-booting devices ==
The devices list below cannot boot postmarketOS (yet). As such, they have not been integrated into the postmarketOS source tree. Once the device becomes bootable, it might appear in this least until a pull-request to integrate the code has been accepted. If you have verified that a device in this list boots postmarketOS, please make a merge-request.
==See also==
* All devices
* Renamed Devices
* Device Wishlist
* The-big-list-of-who-has-what-device
* :Category:Manufacturers All devices but sorted by Manufacturers
* :Category:Architecture All devices but sorted by Architecture
Category:Hardware
Allwinner A33

== Devices ==
Allwinner A33 (sun8i) SoC features a Quad-Core Cortex-A7 ARM CPU, and a Mali400 MP2 GPU from ARM. It is a Quad-Core pin-to-pin-compatible version of the Allwinner A23 (which in turn is a lower power, cut-down, not-pin-compatible version of the Allwinner A20).
It's now also called the Allwinner R16, targeted on miscellaneous IoT devices, such as the Nintendo NES Classic Edition gaming console.
==CPU==
*ARM Cortex-A7 Quad-Core
*512 KB L2-Cache (shared between four cores)
*256 KB (Instruction) / 32 KiB (Data) L1-Cache per core
*SIMD NEON, VFP4
*Virtualization
*Large Physical Address Extensions (LPAE) 1 TB
==GPU==
*ARM Mali400 MP2
*Featuring 1 vertex shader (GP) and 2 fragment shaders (PP).
*Complies with OpenGL ES 2.0
==Memory==
*DDR3/DDR3L controller
*NAND Flash controller and 64-bit ECC
==Video==
*Full HD 1080p video decoding of MPEG-2, MPEG-4 SP/ASP GMC, H.263, H.264, WMV9/VC-1, and VP8
*BD Directory, BD ISO and BD m2ts video decoding
*H.264 High Profile 1080p @ 30 fps encoding
*2160×1080 @ 30 fps 3D decoding
*Complies with RTSP, HTTP,HLS,RTMP,MMS streaming media protocol
==Display==
*CPU/RGB/LVDS LCD interface 1280x800 resolution
*MIPI DSI interface up to 1280x800 resolution
==Camera==
*Integrated parallel 8-bit I/F YUV sensor
*Integrated 24-bit parallel YUV 444 I/F
*5M/8M CMOS sensor support
*Dual-sensor support
==Audio==
*Integrated HI-FI 100 dB Audio Codec
*Dual MIC noise cancellation
==PMIC==
*X-Powers AXP223, designed for the A23, connected via Allwinner's Reduced Serial Bus (RSB)
= Documentation =
* A33 User Manual v1.0 (PDF, 580 pages, 2014-05-25)
* A33 Datasheet v1.0 (PDF, 35 pages, 2014-05-21)
* A33 User Manual v1.1 (PDF, 574 pages, 2014-09-22)
* A33 Datasheet v1.1 (PDF, 35 pages, 2014-09-22)
* R16 Hardware Design Materials (Source)
* A33 Development Materials
= External links =
* Allwinner Product Page A33
Allwinner D1-H

Allwinner D1, also known as D1-H (H stands for HDMI) is a RISC-V SoC that similar to D1s.
== Differences D1-H and D1s ==
D1s has 64 MB built-in DDR2 memory, while D1-H uses external DDR2/DDR3 memory.
Unlike D1-H , D1s has no Tensilica HiFi4 DSP, HDMI output and has one less I2S port.
D1-H uses LFBGA package, while D1s uses eLQFP128 package.
== Devices ==
== See also ==
D1-H on linux-sunxi.org
Linux kernel mainline status
Uboot Mainline status
Datasheet
Allwinner D1s
Allwinner D1s

Allwinner F133 (also known as D1s) is a soc that smaller to D1-H.
D1-H has hdmi but d1s dont.
== Differences D1-H and D1s ==
D1s has built in 64 MB of DDR2 memory but D1-H dont.
Unlike D1-H , D1s is leak of Tensilica HiFi4 DSP , HDMI output and 1x I2S port.
D1-H use LFBGA package . D1s use eLQFP128 package.
== Devices ==
== See also ==
D1s on linux-sunxi.org
Linux kernel mainline status
Uboot Mainline status
Datasheet
Allwinner D1-H
Allwinner H2+/H3

== Devices ==
==CPU==
*ARM Cortex-A7 Quad-Core 1.296 GHz
*512KB L2-Cache (shared between four cores)
*32 KB (Instruction) / 32KiB (Data) L1-Cache per core
*SIMD NEON, VFP4
*Virtualization
*Large Physical Address Extensions (LPAE) 1TB
==GPU==
*ARM Mali400 MP2 600 Mhz
*Featuring 1 vertex shader (GP) and 2 fragment shaders (PP).
*Complies with OpenGL ES 2.0
==Memory==
*DDR2/DDR2L-DDR3/DDR3L controller
*NAND Flash controller and 64-bit ECC
==Video==
*Ultra HD 4k and Full HD 1080p video decoding of MPEG-2, MPEG-4 SP/ASP GMC, H.263, H.264, H.265, WMV9/VC-1, and VP8
*BD Directory, BD ISO and BD m2ts video decoding
*H.264 High Profile 1080P@30fps encoding
3840×1080,1920x2160 3D decoding 
*Complies with RTSP, HTTP,HLS,RTMP,MMS streaming media protocol
*Video Engine/ Cedar Engine?
==Display==
*Integrated HDMI V1.4 with HDCP1.2 4K@30fps
*TV CVBS output
==Camera==
*Integrated parallel 8-bit I/F YUV422 sensor
*Support CCIR656 protocol fot NTSC and PAL
*5M CMOS sensor support
*Support video capture resolution up to 1080p@30fps
==Audio==
*Two audio digital-to-analog(DAC) channels 92dB SNR
*Two differential microphone inputs (one low-noise)
*Stereo Linein input
==Embedded Controller==
*AR100, an OpenRISC 1000 32-bit controller. Manages deep powersave modes and has closed Allwinner's BSP. Supports ORBIS32 base instructios set
*It seems to be tightly integrated with "RTC block"
==Miscellaneous==
*Thermal Sensor Controller (TSC) providing over-temperature protection interrupt and over-temperature alarm interrupt (but it's still has issues with overheating to 90°С so be careful)
*no PMU (its role is partially done by AR100 coprocessor)
*package: FBGA347, 14 mm x 14 mm, 0.65 mm Pitch
==H2+ and H3==
*H2+ is a variant of H3, targeted at low-end OTT boxes, which lacks Gigabit MAC and 4K HDMI output support. So, H2+ is cost-down version of already cheap H3
*H3 images are proven to run on H2+.
*According to the source code of BSP, variants differ by the last byte of the first word of SID. 0x42 and 0x83 indicates H2+, 0x00 and 0x81 indicates H3, and 0x58 indicates H3D (a still unknown variant).
== See also ==
* H3 on linux-sunxi
* H3 on Official product page
* AR100 on linux-sunxi
* AR100-info on Github
Amazon Fire-Phone (amazon-kodiak)

== Contributors ==
* Lucas Ramage <oxr463>
== Maintainer(s) ==
* Lucas Ramage <oxr463>
== What works ==
* Nothing yet..
== What does not work ==
* Kernel compilation
* Flashing
* Booting kernel
* SSH over USB
* Touch
* Screen
* WiFi
* Bluetooth
* Camera
* GPS
* Modem
=== Default Partition Layout ===
== How to enter flash mode ==
More details to this section are coming soon.
== Installation ==
Even though there is a custom recovery for this device (safestrap), it won't be able to flash custom kernels since the bootloader is locked. This means that pmOS can't be installed this way.
== Serial Debugging ==
More details to this section are coming soon.
== Known Issues ==
Bootloader is locked down.
== To Do List ==
=== Doing ===
* Fix Kernel sources not compiling
* Investigate boot process; attempt to get SSH over USB
* Investigate missing driver binaries
== See also ==
* postmarketOS amazon-kodiak fork on Gitlab
* Gentoo Wiki - Amazon Fire Phone (Draft)
Amazon Fire 7 2015 (amazon-ford)

Amazon Fire 7" is a cheap low-end tablet released back in November of 2015. It had specs similar to a Nexus 7 from 2012.
== Contributors ==
* BenTheTechGuy
== Users owning this device ==
== How to enter flash mode ==
* Your bootloader must be unlocked via this method: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
* TWRP can be reached by holding and at boot.
== Installation ==
 
pmbootstrap init
pmbootstrap install --android-recovery-zip
# Make sure you're booted into TWRP at this point and Started ADB Sideload on the device
pmbootstrap flasher --method=adb sideload
== See also ==
* Initial merge request
* 
*
Amazon Fire 7 2017 (amazon-austin)

== Users owning this device ==
== Unlock the bootloader ==
The bootloader can now be unlocked through a new hardware method:
https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
== How to enter recovery mode ==
Press and hold + 
== Installation ==
This assumes that you already have Linux distro installed and the bootloader on the tablet is unlocked. Don't worry if it looks complicated. If you are unsure of something ask on the postmarketos matrix or leave a comment for help.
# Install pmbootstrap as stated in the Installation_guide, does not matter which options or device you pick.
# Once that is done download and drag the two folders in the git repo into "/home/YOURUSER/.local/var/pmbootstrap/cache_git/pmaports/device/testing/" also displayed as "~/.local/var/pmbootstrap/cache_git/pmaports/device/testing".
# Run pmbootstrap init and select amazon as manufacture and austin as the device, mate, lxde, xfde, are confirmed working.
# Run pmbootstrap install
# Boot into twrp and wipe all partitions including data
# Boot into the hacked bootloader from the twrp options
# Run pmbootstrap flasher flash_rootfs --partition userdata (system partion is too small to flash!) and once it is done flashing run pmbootstrap flasher flash_kernel
# Unplug the device, wait 10 seconds and then hold the power button. Once it is powered on YOU MUST boot it into twrp at least once as it needs to restore the AMONET exploit, until you do that the device will not boot.
== Amonet ==
Amonet is an lk exploit used to boot an unsigned kernel. Sources of amonet are available here: https://github.com/xyzz/amonet/tree/mustang.
This exploit is installed by a bootrom exploit. But probably some 2nd stage bootloader is a good idea.
== Device problems ==
* Mainline will highly unlikely be ever supported.
* This device use exploit due to locked bootloader. See #Amonet.
* This device's bl is not very good for running linux, due to it appends much of bad cmdline params, and some things in device tree.
== See also ==
* Initial merge request
* https://forum.xda-developers.com/t/postmarketos-for-amazon-fire-7-hd-2017-austin.4315717/ Xda-Developers forum topic
Amazon Fire 7 2019 (amazon-mustang)

== Contributors ==
* NoriTech
== Maintainer ==
* NoriTech
== Users owning this device ==
== How to unlock bootloader ==
The bootloader can now be through a hardware method: https://forum.xda-developers.com/amazon-fire/orig-development/fire-7-2019-mustang-unbrick-downgrade-t3944365
== How to enter flash mode ==
Press and hold + 
== Installation ==
Due to the fact that fastboot doesn't work even after using the amonet exploit, you will need to export the boot image and flash it with twrp. Then flash this dummy zip which will force twrp to reapply the amonet exploit. 
Another option is exporting a flashable zip that can be flashed using twrp.
Refer to Installation Guide for postmarketOS
== Amonet ==
Amonet is an lk exploit used to boot an unsigned kernel. Sources of amonet are available here: https://github.com/xyzz/amonet/tree/mustang.
This exploit is installed by a bootrom exploit. But probably some 2nd stage bootloader is a good idea.
== Mainlining ==
There is some work on mt8163 mainline, for amazon-karnak, but it will be easy to get it on mustang. For now serial console and simplefb is working. Pwrap and pmic seems to be working. https://github.com/mt8163-mainline/linux
== Device problems ==
* Mainline is not yet usable.
* Panfrost (driver for mali-t720) is wip, and not avalible in downstream (Merged in linux 5.2)
* This device use exploit due to locked bootloader. See #Amonet.
* This device's bl is not very good for running linux, due to it appends much of bad cmdline params, and some things in device tree.
== Useful information ==
* Serial/UART
:* 921600 baud 8N1
:* RX & TX pads are on the back of the board clearly marked. A cheap RS232-to-USB will work.
Please approach with caution since the display flex cable (top center) is glued onto the board but the board can be flipped over while it is connnected.
== See also ==
* Initial merge request
* 
*