nyuuzyou/wikis huggingface dataset:
Generic x64 UEFI device

This device allows postmarketOS to run on common x86_64 hardware if the device uses 64-bit UEFI.
== Contributors ==
* MartijnBraam
* FlashTeens
== Installation ==
Prebuilt images for generic x86_64 devices can be found on our downloads page, alternatively you can follow the Installation Guide to build an image from scratch. The process is usually fairly straight forward, select generic as the manufacturer when prompted.
When instructed to run pmbootstrap install, insert your target medium (sdcard, USB thumbdrive, etc) and specify --sdcard /dev/sdX where /dev/sdX is the target device.
The on-device installer is not currently supported. You will need to install directly to your target storage device. The simplest is to flash an image to a flash drive or SD card, and use pmbootstrap from there to access it. Alternatively, you can remount the rootfs as readonly after first boot and use a tool like dd to copy the disk image over to the internal storage device.
== See also ==
* initial merge request
* 
* :Category:Convertible‏‎
* :Category:Desktop
* :Category:Laptop
* Generic x86 UEFI device
Geniatech MyGica V1200 / Geniatech MyGica ATV1200 / Geniatech MyGica A6 (geniatech-rmx0312)

#REDIRECT Geniatech_MyGica_V1200_/_Geniatech_MyGica_ATV1200_/_Geniatech_MyGica_A6_/_Geniatech_MyGica_A300_(geniatech-rmx0312)
Geniatech MyGica V1200 / Geniatech MyGica ATV1200 / Geniatech MyGica A6 (geniatech-v1200)

#REDIRECT Geniatech_MyGica_V1200_/_Geniatech_MyGica_ATV1200_/_Geniatech_MyGica_A6_/_Geniatech_MyGica_A300_(geniatech-rmx0312)
Geniatech MyGica V1200 / Geniatech MyGica ATV1200 / Geniatech MyGica A6 / Geniatech MyGica A300 (geniatech-rmx0312)

== Contributors ==
== Users owning this device ==
==Current State==
Non-Booting Device
==Wifi==
It use MLK 003a Usb wireless module for the wifi function.The MLK001A's fccid was printed on MLK 003a.However,MLK001A look diiferent from MLK 003a. Also MLK 003a use rtl8188cus chip.
== How to enter flash mode ==
== Installation ==
== Different bewtween Geniatech MyGica V1200 / Geniatech MyGica V1200 / Geniatech MyGica A6 / Geniatech MyGica A300==
Geniatech MyGica V1200 seem to only sold at hk and it come with air mouse that has a keyboard build in.
Geniatech MyGica A6 (Simple Chinese Name : 美如画A6) seem to only sold at china and it dont come with a air mouse.
Geniatech MyGica AV1200 seem to sold internationaly and seem to be identical to Geniatech MyGica A6(expect for storage).
Geniatech MyGica A300 (Simple Chinese Name : 美如画A300) seem to sold internationaly and seem to be identical to Geniatech MyGica A6. It is sold only in china.
==YPBPR==
Some variant of atv 1200 dont have YPBPR RCA port.
==Internal USB==
There are a internal usb port in V1200 and the internal usb port was pluged a air mouse receiver by default.
A6 dont have internal usb port.
ATV1200 seem to dont have internal usb port.
==UART==
File:Geniatech-rmx0312-uart.png|thumb|left|3.3v,baud rate:115200
== Pictures ==
File:Pcb of Mygica v1200.jpeg|thumb|left|Pcb of Mygica v1200
Pcb of Geniatech MyGica A6.webp|thumb|left|Pcb of Mygica a6
==Mainline Support==
There r mainline in the linux-edge. However it is very borken.
== See also ==
* A review about V1200 (Traditional Chinese)
* A6 on Baidu Baike(百度百科)(A china wiki) (Simplify Chinese)
*A review (that has some pcb pic of a6) about a6 on znds (a china smart tv forum) (Simplify Chinese)
*A300 on Baidu Baike(百度百科)(A china wiki) (Simplify Chinese)
*A info of a300 on a china tv box database website. (Simplify Chinese)
*A ruissia forum post that had mentioned MyGiga RMX0312(MyGica ATV120/V1200/A6/ATV300)(not sure which one) (Ruissia)
*Mainline device tree
Category:Devices with known UART pinout
Geniatech MyGica V1200 / Geniatech MyGica ATV1200 / Geniatech MyGica A6 / Geniatech MyGica V1200 (geniatech-rmx0312)

#REDIRECT Geniatech MyGica V1200 / Geniatech MyGica ATV1200 / Geniatech MyGica A6 / Geniatech MyGica A300 (geniatech-rmx0312)
Geniatech MyGica V1200 / Geniatech MyGica V1200 / Geniatech MyGica A6 (geniatech-v1200)

#REDIRECT Geniatech_MyGica_V1200_/_Geniatech_MyGica_ATV1200_/_Geniatech_MyGica_A6_/_Geniatech_MyGica_A300_(geniatech-rmx0312)
Get notifications for upstream releases

Fedora provides a great service at release-monitoring.org, that monitors upstream projects for new releases and sends out e-mail or IRC notifications whenever there is a new release.
=== Set up notifications ===
* Create a Fedora account (here)
* Login with your Fedora account at release-monitoring.org for the first time (here)
* Login at Fedora Notifications (here)
* Navigate to update your E-Mail notifications
* A huge intimidating page opens. Don't get discouraged. The example filters on the left can be deleted.
* Type in a new filter name (e.g. "release monitoring") and hit "Create a new filter"
* Add as filter rule Anything regarding a particular "upstream project"
* In the comma separated list of projects, add the ones where you want to receive notifications. Use the names from release-monitoring.org. For example:
 chatty,phoc,feedbackd,kgx,wys,phosh,squeekboard,purple-mm-sms,Calls
* (There is even a preview with 'Searching for example messages that match this filter', though it takes forever to load)
* Hit "Save" and it should be active.
=== Add new projects ===
It's quite convenient to add new projects. Log into release-monitoring.org and make sure that the project doesn't exist yet with the search function. Then hit add project.
=== pmbootstrap aportupgrade ===
Related: pmbootstrap aportupgrade can use the same database to automatically bump the version in a pmaport to the next version. For that to work, the name of the package either needs to be the same as on release-monitoring.org. Or you can simply add the name in Alpine/pmOS to the package, after logging into release-monitoring.org and searching for the software name.
Category:Guide
Getting started

postmarketOS is based on Alpine linux so some questions that may seem unanswered here on our wiki can be supplemented by the Alpine wiki. Currently, postmarketOS is still in heavy development so it is not suitable for daily use, nor for non-technical (or at least willing to learn) users. 
== Users/Newbies ==
Currently, postmarketOS is still in heavy development, whilst it is able to provide the basic functionality you'd expect from a phone (on supported devices) it is definitely not competitive with mainstream mobile Operating Systems. If you're an early adopter looking for a more stable device to get familiar with postmarketOS, it is recommended that you get a PinePhone (Mobile) or a Raspberry Pi 4 (single board computer) to use, as their open nature has enabled more stability than other hacked devices. Check out the Devices page to see what other devices are supported.
* Understanding Alpine linux, the upstream distribution (redirects to Alpine linux wiki) 
* search installable packages
== Hobbyists/Tinkerers ==
Understanding the differences between postmarketOS and a standard Linux distribution is instrumental in tinkering around. It is strongly recommended that you read through Alpine linuxs wiki to understand the differences like BusyBox, musl libc, and OpenRC
* Bug reporting and tracking fixes you make are very important to the health of the project. Read through the Git workflow
* You can build and run python programs on device, even using libraries Kivy or Pocketsphinx if you want a more complex setup
* Waydroid allows a user to install Android applications on their device. We recommend against using closed source proprietary software such as Android applications, but if you need certain apps for your device to be a daily driver (such as Uber) then this may be an approach you want to consider
* UI frameworks
== postmarketOS Developers/Kernel Hackers ==
* Understanding the boot process
* Porting to a new device
* Dumping your device
* Getting started with low level
* Information for Qualcomm based devices
* Understanding device firmware
Giara

Giara is a reddit app, built with mobile Linux in mind.
Giara is available from Alpine's community repository, and can as such be installed on postmarketOS v20.03 (and newer) and Edge via the following command:
 # apk add giara
== Tweaks ==
=== Nothing happens when I try to log in ===
Ensure that you have a default browser set. You can check if you do by running the following:
 $ xdg-settings get default-web-browser
Category:Apps
Gini w5 (gini-w5)

== How to enter flash mode ==
Unplug from USB and power off the phone, hold and until you see "Android system recovery <3e>" text followed by a simple text menu.
Select "reboot to bootloader".
=== Unlock bootloader ===
 $ fastboot oem unlock
A warning dialog would ask you whether to unlock the device.
Press to unlock the device.
== See also ==
Git repository move

We have moved from gitlab.com to gitlab.postmarketos.org. See this blog post for reasoning.
Newer pmbootstrap versions should automatically configure the repository changes for you, but if not, please configure your git repositories to point to the new location by editing .git/config in your pmbootstrap (or other postmarketOS git repository) folder.
Simply replace gitlab.com with gitlab.postmarketos.org, then run:
$ git checkout master
$ git pull
If this fails run:
$ git merge --abort
$ git reset --hard origin/master
If that does not work for whatever reason, you can also delete your pmbootstrap folder and do a fresh clone:
$ rm -r $HOME/.local/var/pmbootstrap
$ pmbootstrap init
Category:Technical Reference
Gitlab project configuration

This is the reference for how we configure our gitlab projects.
== GitLab configuration ==
=== Group mapping ===
How the team maps to gitlab groups:
postmarketOS 	GitLab Group
Core Contributors 	Maintainer
Trusted Contributors	Developer
Active Contributors 	Reporter
=== Settings per repository ===
# Settings / General
## Merge Requests
Merge Method:
[x] Fast-forward merge
Merge options:
[ ] Automatically resolve merge request diff discussions when they become outdated
[x] Enable "Delete source branch" option by default
Squash commits when merging:
[x] Do not allow
Merge checks:
[ ] Pipelines must succeed
[x] All discussions must be resolved
## Merge request approvals
[ ] Remove all approvals when commits are added to the source branch.
# Settings / Repository
## Protected Branches
master:
	Allowed to merge:	Developers + Maintainers
	Allowed to push:	Developers + Maintainers
	Allowed to force push:	False
	Code owner approval:	False (we only use it for notification)
(stable branches):
	Allowed to merge:	Maintainers
	Allowed to push:	Maintainers
	Allowed to force push:	False
	Code owner approval:	False
## Protected tags
*:
	Allowed to create:	Maintainers
Category:Admin
Glacier

Glacier is a phone shell based on Jolla's Mer stack. It can be used as a FOSS alternative to the proprietary UI on SailfishOS, and it can also be used on other distributions.
== Status ==
This UI has been temporarily dropped as of , due to lack of interest from the maintainer, and it also was broken for some quite time.
If somebody wants to take over the maintenance, MR can be reverted and the respective packages in Alpine restored.
== See also ==
* NemoMobile
* Nemo/Glacier - Mer Wiki
GoClever Orion 70L (goclever-gcta741l)

== Contributors ==
* JuniorJPDJ
== Maintainer(s) ==
* JuniorJPDJ
== How to enter flash mode ==
Flashing postmarketOS to NAND memory inside this device is not supported.
== Installation ==
Just flash it on sdcard using pmbootstrap:
$ pmbootstrap install --sdcard /dev/YOUR_SDCARD_DEVICE
eg.
$ pmbootstrap install --sdcard /dev/mmcblk0
== Booting ==
Put your sdcard inside tablet and turn on the device while holding button. U-Boot screen should show up and boot should proceed.
== Gallery ==
File:goclever-gcta741l-uboot.jpg|thumb|600px|
File:goclever-gcta741l-splash.jpg|thumb|600px|
File:goclever-gcta741l-pmos-splash.jpg|thumb|600px|
File:goclever-gcta741l-mate.jpg|thumb|600px|
File:goclever-gcta741l-neofetch.jpg|thumb|600px|
File:goclever-gcta741l-otg-tty.jpg|thumb|600px|
== TODO ==
* fix audio
* add HDMI to device tree
* fix LCD panel timings (those from FEX file aren't real, didn't find datasheet, panel name: KR070PB2S)
* add LCD backlight control (PWM for A31 missing in mainline, patches, software workaround)
* make accelerometer driver (MMA7660) respect mount-matrix
* add camera autofocus len to device tree: Analog Devices AD5820
* send DTS to upstream
* 3D acceleration with PowerVR
* write touchscreen driver: Awinic AW5306
* write camera sensor driver: GalaxyCore GC0329
== Internals ==
File:goclever-gcta741l-internals1.jpg|thumb|600px|
File:goclever-gcta741l-internals2.jpg|thumb|600px|
File:goclever-gcta741l-internals3.jpg|thumb|600px|
File:goclever-gcta741l-internals4.jpg|thumb|600px|
File:goclever-gcta741l-internals5.jpg|thumb|600px|
File:goclever-gcta741l-internals6.jpg|thumb|600px|
== See also ==
* 
* Initial merge request
* pcformat.pl tablet specification
* goclever.com bigger brother's official page
* gitlab.com android dumps and detailed info repository
* archive.org backup of factory and modified firmware files
Goclever Quantum2 400 (goclever-quantum2400)

== Contributors ==
* Illen
== Users owning this device ==
== Bootloader ==
This device uses U-Boot running a fastboot gadget. Bootloader is unlocked by default.
== Mainline kernel ==
BCM23550 is supported in mainline. There is also mainline work on the device with same SoC.
== See also ==
* TWRP port
Google Glass (Explorer Edition)

== Contributors ==
* kaendfinger
== Maintainer(s) ==
== How to enter flash mode ==
Note that the the device gives no indication of being in fastboot mode, just a blank screen.
Also note that fastboot devices may show no permissions in place of a serial number. If this is the case, you may need to run fastboot as root. If it still shows no permissions then you probably need to install the android udev rules package, AND copy the file to /etc/udev/rules.d/ AND add the Google Glass product ID to the Google vendor ID section. The Glass has at least 9001 and 9002 as adb and fastboot product identifiers.
=== Method #1 ===
* enable debugging
* adb reboot bootloader
=== Method #2 ===
* power off device
* hold button
* press 
* wait 10-15 seconds
(this method is somewhat tricky since pmbootstrap devices is the only way of determining if it was successful)
=== Method #3 ===
* power off device
* enter recovery mode
** hold button
** press once
** continue holding button for 10 seconds
* select 
== Installation ==
Installation to flash seems to be challenging/broken at the moment, but pmbootstrap flasher boot does work to get pmOS running on the device, and you can access the device via SSH over USB networking to connect the wlan0 interface to a network using wpa_supplicant and then should be able to sudo apk add postmarketos-ui-i3wm if it didn't automatically start (which it didn't for dragon788).
== Interesting notes ==
i3wm does work on the device, the touchpad on the temple is mapped like an absolute positioning mouse (emulates touchscreen behavior sort of). dragon788 was able to drag the i3wm initial config window to the center of the workspace, because it was way off at the far bottom right since it assumed a resolution higher than 640x360 (probably 800x600 or 1024x768 was the minimum the i3 guys expected).
SXMO doesn't show up as an option, possibly because the device is currently configured as armhf rather than arm7 so changing that per the note at the top of this page may open more options.
== See also ==
* Initial merge request
* 
* 
*
Google Gru Chromebook (google-gru)

== Contributors ==
* Jenneron
== Installation ==
See for general information Chrome OS devices page.
Tested installation on Acer Chromebook Tab 10 (google-dru):
* Unlock bootloader by following https://www.youtube.com/watch?v=qRQ9gBGmw3c (Note: You can not get into the unlock procedure when device is off. You have to first turn it on and while its on hold all 3 buttons pressed like in video)
* There are prebuild images named 'Google Gru Chromebooks' for download if you do not want to compile an own image here https://postmarketos.org/install/ (Note: Stable release v24.12 and probably newer do not have graphical issues in Wayland any more)
* You need at least a 4GiB MicroSD card or USB-drive (for example with USB-OTG adapter drive) to install it to eMMC memory. Unpack the .img.xz image to a single .img file and use for example dd to write it to the MicroSD card or USB-drive.
* Connect the MicroSD card or USB-Drive to the Chromebook and turn the Chromebook on
* Choose in bootloader mode under developer options 'Boot From USB or SD Card'
* PostmarketOS is booting now and is in a working state. If you do not want to install it to internal eMMC memory, you are ready now.
* For eMMC installation: After PostmarketOS have boot once, it resized the external memory. Turn off the device and remove external memory. Copy the same unextracted .img.xz file you download from the PostmarketOS website to for example the Download directory of the user.
* Boot again external memory with 'Boot From USB or SD Card'
* In PostmarketOS look what is the /dev/xxxxx link for the internal eMMC drive for example with the preinstalled tool 'lsblk'
* In PostmarketOS change with command line ('cd' command) to the directory containing the .img.xz file you copied on there a moment ago and write PostmarketOS to eMMC memory with a command like this:
xzcat 20241226-0322-postmarketOS-v24.12-phosh-22.5-google-gru.img.xz | sudo dd of=/dev/xxxxxxxx status=progress bs=1M oflag=direct iflag=fullblock
* Now the whole eMMC containing ChromeOS have been wiped and replaced with PostmarketOS. You can power off the PostmarketOS running from external memory and remove the external memory.
* When you turn now the device, it would show the developer mode. You can either go into developer options and choose 'Boot From Internal Disk' or just wait after powering it on. After some short time it would beep loud and boot without any 'Boot From Internal Disk' the PostmarketOS eMMC installation.
== Audio ==
See:
* 
* 
We have a workaround for laptops, but not for tablets. Headphones and headset mic are currently broken on tablets.
HDMI codec is currently not supported.
Also, the working range for volume is 0-10%, with 10%-100% providing no additional gain.
== Camera ==
The cameras in the tablet devices are unusable, see .
== Devices ==
== See also ==
* Initial merge request
Google Kukui Chromebook (google-kukui)

== Contributors ==
* Jenneron
* Bonfire
* WeirdTreeThing
== Installation ==
See Chrome OS devices page.
== Audio ==
Overall in good condition, but it is missing jack detection support and sometimes headphones or/and headset mic. See device pages for more details. There is also a known high pitch sound that rarely occurs when waking up from suspend. To stop the high-pitch sound, you can either restart the Chromebook, or disable suspend.
There are also may be audio problems in the 23.12 release, if you have any of those it may be reasonable to try edge
== Camera ==
It currently works only on laptops and convertible devices and doesn't work on tablets. This is because of camera being USB on laptops and CSI on tablets.
A Linux kernel RFC related to camera support has been open since 2019, but has not yet been upstreamed .
== Type C DP Out ==
it6505dptx is responsible for Type C DP Out on this device but for some reason the device tree missing the it6505dptx node.
== Devices ==
== See also ==
* Initial merge request
Google Nest

The Google Nest has been made in several different versions, this page tries to document some initial research.
For the Nest Learning Thermostat, two tarballs where released for version 5.7:
* for the i.MX version, DTS files attributed to Nest Labs are located in /arch/arm/boot/dts/onyx-*
* the OMAP version is based on board files, some Nest Labs attributed files are located in /arch/arm/mach-omap2/board-diamond-* According to board-diamond.c the board is forked from an OMAP3 EVM. This file contains quite some documentation about the board.
The Nest userspace has been implemented in an open source project: https://github.com/luke-jr/freeabode
== TODO ==
* document revisions/SKUs of the Nest per SoC
* add unlock info
== External links ==
* https://en.wikipedia.org/wiki/Nest_Learning_Thermostat
* https://nest.com/legal/compliance/
* https://www.blackhat.com/docs/us-14/materials/us-14-Jin-Smart-Nest-Thermostat-A-Smart-Spy-In-Your-Home.pdf
Google Nexus 10 (samsung-manta)

== Users owning this device ==
== How to enter flash mode ==
=== fastboot ===
* Connect a USB cable
* Power the device off
* Hold power + volume up + volume down
* You should get a bootloader screen
=== heimdall ===
* Connect a USB cable
* Power the device off
* Hold power + volume down
* You should get a bootloader screen saying "Downloading... Do not turn off target !!"
== Installation ==
See Installation guide.
Flashing can be done using Fastboot (preferred) or Heimdall.
=== From a prebuilt image ===
# Download an image from https://images.postmarketos.org/bpo/edge/samsung-manta/
# Uncompress files, e.g.:
#* xz -d 20240222-1756-postmarketOS-edge-phosh-22.3-samsung-manta-boot.img.xz
#* xz -d 20240222-1756-postmarketOS-edge-phosh-22.3-samsung-manta.img.xz
# Then flash files with fastboot:
#* fastboot flash boot 20240222-1756-postmarketOS-edge-phosh-22.3-samsung-manta-boot.img
#* fastboot flash userdata -S 1G 20240222-1756-postmarketOS-edge-phosh-22.3-samsung-manta.img
# Reboot
=== From pmbootstrap ===
==== fastboot ====
pmbootstrap flasher flash_kernel
pmbootstrap flasher flash_rootfs
If rootfs partition is bigger than 1 GiB:
pmbootstrap export
cd /tmp/postmarketOS-export
fastboot flash boot boot.img
fastboot flash -S 1G userdata samsung-manta.img
 
==== heimdall ====
pmbootstrap flasher --method heimdall-bootimg flash_kernel --partition boot
pmbootstrap flasher --method heimdall-bootimg flash_rootfs --partition userdata
== Main board UART ==
To simplify getting logs when doing development, it can be useful to connect to UART directly on the main board. UART can be found at a 12 pin connector close to edge of board. The same connector is used for many of samsung's devices, but pinout varies, see Serial_debugging#Main_board_UART_on_exynos_devices. Pad number 1 where the tiny triangle is pointing, and TX (from manta's perspective) is then pad 10, and RX pad 12. The device uses 1.8 V signal strength.
== Links ==
* 
*
Google Nexus 7 2013 LTE (asus-deb)

== Contributors ==
== Users owning this device ==
== Other information ==
* This device is identical to asus-flo, except that it has a modem.
* To install to this device, simply use the asus-flo image, which obviously doesn't support the modem.
* See Google Nexus 7 2013 (asus-flo)
== Photos ==
File:Asus_flo_plasma.jpg|thumb|left|Flo running Plasma Mobile
Google Nexus 9 (htc-flounder)

== Contributors ==
* lillywho
* Segfault
== Device owners ==
== How to enter flash mode ==
Hold + , press to confirm Fastboot mode
Note that in Fastboot mode you can check from the text in the header if your device is the Wifi (htc-flounder) or LTE (htc-flounder_lte) version.
== Installation ==
$ pmbootstrap flasher flash_kernel
$ pmbootstrap flasher flash_rootfs
== LTE version ===
The LTE version won't boot with the kernel of the wifi version because the bootloader only loads the kernel image if the device tree blob (DTB) has a compatible property field.
That is `google,flounder64` for the WiFi version and `google,flounder64_lte` for the LTE. (see )
After that change the LTE will boot as well.
== Mainlining notes ==
An ongoing mainline port is available here
https://github.com/TuxThePenguin0/linux/tree/htc-flounder
* A sector with a GPT partition table is provided by the bootloader but that GPT is empty, instead TegraPT is used
* Broadcom BCM4354XKUBG wifi module
* Broadcom BCM4752 GPS
* Broadcom BCM2079x NFC (enable on PB1, irq on PR7, wake on PS1, i2c addr 0x77)
* NXP tfa9895 audio amp (enable on PX5, i2c addr 0x34)
* NXP tfa9895l amp (i2c addr 0x35)
* Realtek rt5677 codec (enable on PX3, i2c addr 0x2d)
* USB port is EHCI1, id pin is PW2
* On the LTE version the modem is on EHCI2
== See also ==
* Initial merge request
* Mainline merge request
* Kernel panic
* https://en.wikipedia.org/wiki/Nexus_9
* 
*