nyuuzyou/wikis huggingface dataset:
Valve Steam Deck (valve-jupiter)

== Contributors ==
* craftyguy
== Users owning this device ==
== Installation ==
Use pmbootstrap to build your own installation image.
At the moment, only installing postmarketOS to SD card is supported. Installing pmOS to the NVMe drive in the Steam Deck will wipe existing SteamOS partitions, and hasn't been tested.
$ pmbootstrap init
$ pmbootstrap install --sdcard /path/to/sdcard
To boot the SD card, the boot option menu can be reached by holding down the Vol- button while pressing the power button. 
== Known issues ==
A list of known issues can be found in the pmaports repository. Notably, there's a full disk encryption quirk where the boot password dialog is shown sideways, but it's still usable otherwise with no functionality lost.
== See also ==
* Initial merge request
* Valve project with SteamOS source code
Category:Game Console
Valve Steam Link (valve-steamlink)

== Contributors ==
* MayeulC
== Users owning this device ==
== Installation ==
This page is under construction.
I am not quite sure about the code name.
It should be possible to provide a rootfs on external storage, as well as a newer kernel, and kexec into the newer kernel.
This requires compiling a kexec kernel module for the built-in kernel (version 3.8.13), as well as the userspace application.
It should also be possible to make it persistent.
== Information regarding the built-in OS ==
It is quite easy to gain root ssh access to the built-in OS:
* Find a fat32 or vfat-formatted usb stick
* create an empty file at /steamlink/config/system/enable_ssh.txt
* Boot the steamlink with the USB stick plugged in
* You can ssh as root, password is steamlink123 (don't forget to change it)
* This persists across reboots until you manually delete /etc/init.d/startup/S01config/enable_ssh.txt or factory reset.
# uname -a
Linux steamlink-1CCE 3.8.13-mrvl #157 PREEMPT Thu Sep 28 21:33:24 PDT 2023 armv7l GNU/Linux
# cat /proc/cpuinfo
processor	: 0
model name	: ARMv7 Processor rev 0 (v7l)
BogoMIPS	: 995.32
Features	: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x3
CPU part	: 0xc09
CPU revision	: 0
Hardware	: MV88DE3108
Revision	: 0000
Serial		: 0000000000000000
# cat /proc/cmdline
console=ttyS0,115200 root=/dev/mtdblock5 rootfstype=yaffs2 ro root_part_name=rootfs init=/sbin/init mtdparts=mv_nand:1M(block0),8M(bootloader),11M(env),512M(sysconf),32M(factory_setting),32M(bootimgs),128M(recovery),32M(fts),384M(factory),1G(rootfs),1924M(cache),8M(bbt) initrd=0x1a00000,0x4ba58 macaddr=00:0C:52:XX:XX:XX steamlink.boardid=-1 steamlink.boardid_count=XXXX
== See also ==
* Some details on how to boot a more recent kernel with Arch userspace trough kexec
* Valve cannot disable boot image verification
* Official SDK
Category:Game Console
Category:Set-top box
Verizon Ellipsis 7 QMV7B (verizon-qmv7b)

All information here applies to the final revision of the board, QMV7B.</br>
== Software ==
The U-Boot and Linux sources are unavailable.
Information from Android 4.4.2 settings:
* Kernel Version: 3.4.67, wormboss@midgard #1, Fri Dec 26 13:41:13 CST 2014
* Build Number: ALPS.KK1.MP5.V1
* SW Version: MV7B_41D37_442
* HW Version: D3A
== Hardware ==
Battery: 4,000 MAh "McNair" branded Li-ion battery
Most or all components manufactured by Quanta Computer.
== UART ==
These terminals seem to connect to a UART with output disabled on all firmware stages:
UART has been disabled in kernel cmdline:
root@QMV7A:/ # cat /proc/cmdline
console=ttyMT3,921600n1 vmalloc=496M slub_max_order=0 lcm=1-nt35521_n070icn_gb1 fps=6592 lcm_type=1 pl_t=3616 lk_t=1584 printk.disable_uart=1 boot_reason=0
== See also ==
* MT65xx mainlining/reverse-engineering information
Verizon Wear24 (verizon-dorado)

== Contributors ==
* Lazcode
== Maintainer(s) ==
* Lazcode
== Users owning this device ==
== How to unlock bootloader ==
This will factory wipe your device.
This requires disassembling the device. Source for method is here. Opening the device will, of course, void the waterproofing aspect.
# Remove the four screws on the back of the device with a Y000 Tri-Point screwdriver.
# Use a heat gun to heat the back of the device and use a suction cup to create a gap to put a guitar pick in. Alternatively, chip the plastic backing to allow a razorblade to create the gap.
# Use a guitar pack to gently pray the wireless charging coil from the back of the device. Do not remove it, allow it to hang to the side.
# Remove the clear and kapton over the SIM card, as well as the black adhesive slightly above it. This will unveil the TP points.
# Using a spare USB 2.0/3.0 cable, remove the non-type A port and strip the wires, revealing Red/White/Green/Black wires.
# Using male to male breadboard connectors, connect the now stripped wires onto the following points. Do not attempt to solder directly to the watch as you highly risk removing the solder pads.
Note that the XDA thread has a wrong configuration of data wires. The below configuration is what rendeko was able to use to unlock bootloader.
Red-TP1
White-TP2
Green-TP3
Black-TP4
# Power on the device. Go to Settings > System > About and tap Build Number 5 times to enable Developer Options
# In Developer Options, toggle ADB debugging and debug over wifi.
# Using adb, connect to your watch's IP address (viewable in developer options) `adb connect 192.168.0.xxx`
# Reboot the device into bootloader mode. adb reboot bootloader
# Run `fastboot oem unlock`
# Connect device through USB. Your device will format.
== See also ==
* Port progress
Videostrong KII Pro (videostrong-kii-pro)/DVB

This page documents the tuner and demodulation hardware found on the Videostrong KII Pro (videostrong-kii-pro), 
to hopefully support the DVB hardware on a mainline linux kernel.
The Videostrong KII Pro (videostrong-kii-pro) has the following tuner/demodulation combination:
* Demod: Availink AVL6862TA
* Tuner: RafaelMicro R912 (despite the board being named "S2&T2_R848_REV1.2")
== Availink AVL6862 ==
The AVL6862 (AVL6862TA-CA23(?)) is a demodulation chip from Availink. It supports terrestrial television (DVB-T/T2), satellite television (DVB-S/S2), as well as cable television (DVB-C). 
=== Drivers and firmware ===
The AVL6862 has drivers that will eventually get upstreamed by Availink.
* AVL6862 driver (from CoreELEC's downstream media_tree repository)
* AVL68X2 and AVL62X1 drivers (from Availink, apparently temporary as they will upstream those)
** chewitt's modifications (just adds a Kconfig and Kbuild)
* Firmware (also from Availink, will be upstreamed)
== RafaelMicro R912 ==
=== Drivers and firmware ===
* R912 driver (from CoreELEC's downstream media_tree repository)
* R848 driver (taken from a downstream kernel)
== See also ==
* Availink AVL6862 brief documentation
* GitHub tickets about support for embedded DVB cards
* Repository branch
Vivo Y21L

== Contributors ==
* Raihan2000
== Users owning this device ==
== Bootloader Unlocking ==
First unlock bootloader by using modified fastboot tool for vivo:
For Linux Download Fastboot tool from: https://drive.google.com/file/d/1SA-6FcUHnwZRzKky720Wx5zIwoq0vE-E/view
use modified fastboot tool to unlock bootloader
$ adb reboot bootloader
$ ./fastboot bbk unlock_vivo
== How to enter flash mode ==
* Fastboot: Power on the device with both and buttons.
* Recovery: Power on the device with and buttons.
* lk2nd Fastboot: Power on the device. After it vibrates, hold .
* lk2nd Recovery: Power on the device. After it vibrates, hold .
* EDL: Connect device via USB as a peripheral with both and buttons.
== Installation ==
# Make sure you have latest firmware flashed. Download latest Update and install it using stock recovery.
# Install lk2nd. Although Vivo already provides a Fastboot interface, lk2nd contains various quirks for booting mainline.
# Follow Qualcomm_Snapdragon_410/412_(MSM8916)#Installation. (Flash from lk2nd Fastboot, not the stock Fastboot.)
== See also ==
*Fonearena page
* msm8916 mainline kernel package
* Mainline kernel tree for msm8916 devices
Vodafone 858 Smart (huawei-u8160)

== Contributors ==
* joshas
== Maintainer(s) ==
* joshas
== What works ==
* Kernel compilation (2.6.32.61)
== What does not work ==
* Everything else
== How to enter flash mode ==
* While holding Volume down, press and hold Power for 5-10 seconds. There are no visual cues when fastboot loads.
== Recovery mode ==
* While holding Volume up, press and hold Power button until recovery options appear.
== Installation ==
* Install system partition to SD card pmbootstrap install --sdcard=/dev/sd?
* Boot kernel using pmbootstrap flasher boot
== Issues ==
* Current assumption is that CPU is not supported by armhf architecture, so it won't boot 
* boot.img that can be booted using fastboot boot command is the one from stock device image. CyanogenMod boot.img fails to boot, but works when flashed to device.
== See also ==
* Device package: 
* Kernel source: 
* Device information:
Volla Phone X (volla-yggdrasilx)

== How to enter flash mode ==
* Fastboot: Power on the device with both and buttons held down. Then select Fastboot by pressing and confirm with .
* Recovery: Do the same as for Fastboot, but select the Recovery option in the menu instead.
* MediaTek Preloader: The preloader triggers automatically everytime the phone turns on or reboots.
== Partition layout ==
volla-yggdrasilx:~# fdisk -l -o Device,Start,End,Sectors,Size,Name /dev/mmcblk0
 Disk /dev/mmcblk0: 58.25 GiB, 62537072640 bytes, 122142720 sectors
 Units: sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disklabel type: gpt
 Disk identifier: 00000000-0000-0000-0000-000000000000
 
 Device Start End Sectors Size Name
 /dev/mmcblk0p1 64 6207 6144 3M proinfo
 /dev/mmcblk0p2 6208 8255 2048 1M boot_para
 /dev/mmcblk0p3 8256 73791 65536 32M recovery
 /dev/mmcblk0p4 73792 74815 1024 512K para
 /dev/mmcblk0p5 74816 115775 40960 20M expdb
 /dev/mmcblk0p6 115776 117823 2048 1M frp
 /dev/mmcblk0p7 117824 183359 65536 32M nvcfg
 /dev/mmcblk0p8 183360 314431 131072 64M nvdata
 /dev/mmcblk0p9 314432 379967 65536 32M metadata
 /dev/mmcblk0p10 379968 396351 16384 8M protect1
 /dev/mmcblk0p11 396352 425983 29632 14.5M protect2
 /dev/mmcblk0p12 425984 442367 16384 8M seccfg
 /dev/mmcblk0p13 442368 540671 98304 48M persist
 /dev/mmcblk0p14 540672 544767 4096 2M sec1
 /dev/mmcblk0p15 544768 675839 131072 64M md1img
 /dev/mmcblk0p16 675840 708607 32768 16M md1dsp
 /dev/mmcblk0p17 708608 710655 2048 1M spmfw
 /dev/mmcblk0p18 710656 712703 2048 1M sspm_1
 /dev/mmcblk0p19 712704 714751 2048 1M sspm_2
 /dev/mmcblk0p20 714752 747519 32768 16M gz1
 /dev/mmcblk0p21 747520 780287 32768 16M gz2
 /dev/mmcblk0p22 780288 911359 131072 64M nvram
 /dev/mmcblk0p23 911360 913407 2048 1M lk
 /dev/mmcblk0p24 913408 915455 2048 1M lk2
 /dev/mmcblk0p25 915456 980991 65536 32M boot
 /dev/mmcblk0p26 980992 997375 16384 8M logo
 /dev/mmcblk0p27 997376 1013759 16384 8M dtbo
 /dev/mmcblk0p28 1013760 1023999 10240 5M tee1
 /dev/mmcblk0p29 1024000 1048575 24576 12M tee2
 /dev/mmcblk0p30 1048576 2686975 1638400 800M vendor
 /dev/mmcblk0p31 2686976 10027007 7340032 3.5G system
 /dev/mmcblk0p32 10027008 10911743 884736 432M cache
 /dev/mmcblk0p33 10911744 122109918 111198175 53G userdata
 /dev/mmcblk0p34 122109919 122142686 32768 16M flashinfo
== Community Info ==
=== postmarketOS users that own the device ===
== See also ==
* Downstream v4.9 Ubuntu Touch kernel source
* Ubuntu Touch devices page of the device
* mtkclient
Volte camera compatibility

Volte and camera check compatibility
This list is especially established for common users whom have to experience postmarketos with a device that *should* be able to do volte calls, and have both front/rear camera working (photo+video)
 volte and camera support for devices
device 	volte 	front photo	front video	back photo	back video	Notes
pixel3A 	no audio 	yes 	yes 	no 	no 	-
pinephone	depend, see notes	yes 	yes 	yes 	yes 	Depends of location/operator, see at both : 
https://forum.pine64.org/showthread.php?tid=12560&pid=121458 
and https://wiki.pine64.org/wiki/PinePhone_Carrier_Support#Europe
Example 	Example 	Example 	Example 	Example 	Example 	Notes
Example 	Example 	Example 	Example 	Example 	Example 	Notes
Example 	Example 	Example 	Example 	Example 	Example 	Notes
Example 	Example 	Example 	Example 	Example 	Example 	Notes
Vpn

== VPN ==
A VPN (Virtual Private Network) is a technology that creates a secure and encrypted connection over a less secure network, such as the Internet. VPNs are used to protect private web traffic from snooping, interference, and censorship.
There is an issue in ModemManger which will not route your GSM traffic through VPN, so VPN is only working over Wifi, carefully read the linked issue and test its solution. (Due a broken sim slot, i can not test this...please update this section after testing with sim/gsm).
== Setup and Usage ==
=== OpenVPN ===
 Via NetworkManager
1. Add your openvpn config to NetworkManager:
nmcli connection import type openvpn file ~/myconfig.ovpn
2. Add username to the imported config:
nmcli connection modify "myconfigname" +vpn.data username="myusername"
3. Launch it with asking for password:
nmcli connection up vpn "myconfigname" --ask
There is also the option to add the password directly to the config so we can enable vpn from sxmo networks menu (sometimes its a bit buggy!):
nmcli con modify "myconfigname" vpn.secrets "password=mypassword"
set the: cert-pass-flags=0
otherwise it will not work:
nmcli con mod "myconfigname" +vpn.data "password-flags=0"
=== OpenVPN ===
Via openvpn
Install OpenVPN support:
sudo apk add openvpn openresolv
if you trust protonvpn, install the dns leak fix (otherwise you have dns leaks and the vpn is worth nothing!):
sudo wget "https://raw.githubusercontent.com/ProtonVPN/scripts/master/update-resolv-conf.sh" -O "/etc/openvpn/update-resolv-conf"
sudo chmod +x "/etc/openvpn/update-resolv-conf"
There is another, yet untested dns leak fix.
Start vpn with configuration file:
sudo openvpn <config.ovpn>
== Testing ==
To make sure your Vpn is doing what it should, visit ip.me and check your virtual location, visit vpntesting to check for dns leaks.
In Iran settings from here worked quite well... while the famous protonvpn was blocked.
== Other Options ==
=== Wireguard ===
See this wiki page, keep in mind that wireguard is blocked by default in some networks e.g. Irancell
=== Tor ===
See this wiki page.
=== Yggdrasil ===
See here.
Vsmart Star 4 (vsmart-willowpro)

This device have no kernel sources available and I haven't tried asking for the kernel source. I'm porting using prebuilt kernel.
== Contributors ==
* realdtn
== Users owning this device ==
== Unlocking bootloader ==
There isn't an offical way to unlock the bootloader,but you can use mtkclient
Steps:
Run "mtk e metadata,userdata,md_udc"
Then hold all VOL UP,VOL DOWN and power button until the screen goes black then plug in the device
Run "mtk da seccfg unlock"
Your device should be unlocked now
== TWRP ==
You have to first flash an empty vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img.empty
Then flash TWRP
TWRP image
fastboot flash recovery willowpro-twrp.img
== Flashing ==
You can flash through fastboot or mtkclient
== Installation ==
Your device must be running stock android 10 : 
To be continued
== See also ==
* Experimental ported kernel source
Vvave

vvave is a mobile-friendly music player made in Mauikit.
==Installation==
 # apk add vvave
==Media format support==
===FLAC===
By default, FLAC-encoded audio will not play in vvave. To play FLAC in vvave, install gst-plugins-good, like so:
 # apk add gst-plugins-good
== See also ==
* VVave on mauikit.org
Category:Apps
Wallpapers

This article lists, which wallpapers are being used in which release. If you are particularly fond of a specific wallpaper from an older release, grab it here!
= v24.12 =
* All UIs use the Dawning wallpaper by dikasp
= v24.06 =
* All UIs use the Meadow wallpaper by dikasp
= v23.12 =
* Phosh and GNOME (not the mobile variant) use pmos-grass.jpg again
* No changes in wallpapers for other UIs
= v23.06 =
* GNOME Shell on Mobile was added for the first time, this wallpaper was specifically created for the release by Tobias Bernard
** Phosh and GNOME used it too, this was a side-effect of the way the wallpaper settings were packaged.
* Plasma Mobile uses pmos-grass.jpg by Martijn Braam
* Sxmo uses its own wallpaper
Web browsers

Overview of browsers that are packaged in Alpine Linux and thus can be used with postmarketOS:
browser 	armv7 	aarch64 	x86_64 	engine 	library 	notes
firefox / firefox-esr 	works (firefox-esr) 	works 	works (firefox-esr)	gecko 	 	needs ui tweaking
chromium 	not anymore available 	works with sandbox disabled	works 	blink 	 	
qutebrowser 	untested 	works 	works 	blink 	qtwebengine	keyboard controlled browser
falkon 	runs, but takes forever	works 	works 	blink 	qtwebengine	issue with url-bar input, reported.
angelfish 	? 	works 	works 	 	qtwebengine	missing cookie/cache delete
epiphany 	works 	works 	pages not loading 	webkit 	webkit2gtk 	crashes on gestures (sxmo)
luakit 	works 	crashes 	pages not loading 	webkit 	webkit2gtk 	keyboard controlled browser
surf 	works 	not in xwayland/sway 	works 	webkit 	webkit2gtk 	keyboard controlled browser
dillo 	works 	works 	works 	dillo 	 	not HTML5, no SSL support
netsurf 	works 	works 	works 	netsurf	 	not HTML5
w3m 	works 	works 	works 	 	 	not images under wayland
links-graphics (Links2)	works 	works 	works 	links 	 	not HTML5, no SSL support
the ARMv7 column has been updated on 2019-07-15 with the Nokia N900 as test device. Falkon might work on devices with more memory.
List of not packed but tested browsers:
browser 	armv7	aarch64	x86_64	engine	library 	notes
mobilized-dillo	works	works 	works 	dillo 	libcurl 	TLS/SSL + touch support, no javascript
midori 	works	works 	works 	webkit	webkit2gtk	
Interesting but not yet tested browsers:
* Servo
* Ladybird does not seem to support musl yet.
== Firefox ==
Add the MOZ_USE_XINPUT2=1 environment variable to make firefox handle touchscreen events properly.
Category:Apps
Weston

Weston is the reference implementation of a Wayland compositor.
=== Installation ===
* pmbootstrap init
* User interface: weston
This will package weston libraries as well as demos for your device, see weston* commands.
Weston will be launched automatically on boot by TinyDM.
=== RDP (Remote Desktop Protocol) ===
Prerequisite:
* apk add weston-backend-rdp
* apk add openssl
Create a Self-Signed SSL Certificate:
* sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout mypublic.key -out mycrt.crt
Start weston with RDP backend:
* weston --backend=rdp-backend.so --rdp-tls-cert=/path/to/mycrt.crt --rdp-tls-key=/path/to/mypublic.key --socket=wayland-1 --width=540 --height=600
On host:
* xfreerdp /v:172.16.42.1 /sec:tls
== Guide ==
Follow the Display guide to change and fix display related issues.
== Troubleshooting ==
Weston is very commonly used for testing new ports and as a demo (:Category:Interface). Unfortunately, upstream changes can make maintenance difficult. The common backend fbdev has been deprecated and disabled by default in weston 10.0.0.
Choosing weston as the interface (pmbootstrap init) on an unmaintained or irregularly maintained device that uses the fbdev backend will likely result in blank screen after the "pmbootstrap loading" splash screen. Log in via ssh and check the file /etc/xdg/weston/weston.ini for an entry such as backend=fbdev-backend.so. Compare this to the value in weston.ini.default, likely backend=drm-backend.so.
The tinydm.log in case of fbdev may have entries such as:
Session: /usr/share/wayland-sessions/weston.desktop
Desktop: weston
Exec: dbus-run-session start_weston.sh
...
failed to connect to Wayland display: No such file or directory
failed to create display: No such file or directory
The logread command may show entries such as:
Using config file '/etc/xdg/weston/weston.ini'
...
Loading module '/usr/lib/libweston-10/fbdev-backend.so'
Failed to load module: Error loading shared library /usr/lib/libweston-10/fbdev-backend.so: No such file or directory
fatal: failed to create compositor backend
Widevine

== Introduction ==
Widevine is a proprietary DRM system, used to secure media content.
It is needed to use various video and audio streaming services (ie. Netflix or Spotify).
Running it on Linux and/or ARM devices is possible, however it requires the Linux system to be based on glibc library, which Alpine and PostmarketOS does not use.
== Installation ==
=== Using Distrobox workaround ===
As noted in Alpine Linux wiki, Distrobox is a good way to run glibc-dependent software. Choose a glibc-based distribution (most of the wwell known ones will be fine) and find its official Docker image on Dockerhub.
After you configure Distrobox, as noted in the link above, you can install a web browser inside the container.
Keep in mind that you will likely need to set a user agent string of a Chrome+Chromebook device to make ARM Linux Widevine binary work.
To run it from the host system, you can use the following command - you can add it to a .desktop file to have a convenient shortcut.
 distrobox enter your_container_name -- /usr/bin/bash -l -c firefox
See Google for hints on creating webapp links for your DRM-dependent websites.
Above procedure was tested with Fedora container and Asahi Linux' Widevine Installer (from Fedora repos).
=== Other methods ===
Alpine Linux lists multiple ways to run glibc programs, others can still be tried out, in hopes of finding a more comfortable workaround.
Wiko Fever (wiko-fever)

== Contributors ==
* Danacus
== Maintainer(s) ==
== Users owning this device ==
== How to enter flash mode ==
Appears to be the same story as for other Wiko devices with MediaTek chipset. Fastboot is broken, it doesn't boot anything at the moment, so I might have to use SP Flash Tool.
Looks very similar to Wiko U FEEL in terms of specification, although I'm claiming that the architecture is aarch64 and they're saying it's armhf. I'm not really sure,
Cortex-A53 is a 64-bit processor from what I can tell.
== Installation ==
Installing doesn't work with fastboot, because the file is too large. I tried installing on an external SD card, but it's still not booting.