OnePlus 6 (oneplus-enchilada): Difference between revisions
Link GPS status |
Undo revision 44722 by Nt8r (talk) It seems this breaks our tables on pages like Devices, so reverting for now. Tag: Undo |
||
Line 35: | Line 35: | ||
| status_bluetooth = Y | | status_bluetooth = Y | ||
| status_camera = N | | status_camera = N | ||
| status_gps = P | | status_gps = P | ||
| status_trustzone = N | | status_trustzone = N | ||
| status_mobiledata = Y | | status_mobiledata = Y |
Revision as of 17:29, 1 June 2023
![]() Running Phosh | |
Manufacturer | OnePlus |
---|---|
Name | 6 |
Codename | oneplus-enchilada |
Model | ONEPLUS A6000 |
Released | 2018 |
Type | handset |
Hardware | |
Chipset | Qualcomm Snapdragon 845 (SDM845) |
CPU | Octa-core (4x 2.8 GHz Kryo 385 Gold & 4x 1.7 GHz Kryo 385 Silver) |
GPU | Adreno 630 |
Display | 1080 x 2280 AMOLED |
Storage | 64/128/256 GB |
Memory | 6/8 GB |
Architecture | aarch64 |
Software | |
Original software | Android |
Original version | 8.0 |
Extended version | 11 on Linux 4.9 (OxygenOS 11.1.2.2) |
postmarketOS | |
Category | community |
Pre-built images | yes |
postmarketOS kernel | Mainline |
Unixbench Whet/Dhry score | 6029.9 |
Flashing |
Works |
---|---|
USB Networking |
Works |
Internal storage |
No data |
SD card |
No data |
Battery |
Works |
Screen |
Works |
Touchscreen |
Works |
Multimedia | |
3D Acceleration |
Works |
Audio |
Works |
Camera |
Broken |
Camera Flash |
No data |
Connectivity | |
WiFi |
Works |
Bluetooth |
Works |
GPS |
Partial |
NFC |
Broken |
Modem | |
Calls |
Works |
SMS |
Works |
Mobile data |
Works |
Miscellaneous | |
FDE |
Works |
USB OTG |
Broken |
HDMI/DP |
No data |
Sensors | |
Accelerometer |
Broken |
Magnetometer |
No data |
Ambient Light |
No data |
Proximity |
No data |
Hall Effect |
No data |
Haptics |
Works |
Barometer |
No data |
This device is based on the Snapdragon 845. See the SoC page for common tips, guides and troubleshooting steps |
The OnePlus 6 is an incredibly powerful and efficient mobile device, well regarded and (bar the notch) an excellent portable work horse, getting mainline Linux working means not only freedom from proprietary software, but also continual security patches and the ability to boot any mobile or desktop Linux distro.
After the OnePlus 6 reached End-of-Life by OnePlus in December 2021, running newer Linux kernel versions is the only way to ensure that the device can continue to be safe and usable for years to come. The Snapdragon 845 is still an incredibly capable SoC, likewise the OnePlus 6 is a well-built and perfectly adequate device. That the millions of sold units have been dropped, destined for Landfill (or at best recycling) by OnePlus is abhorrant, join us in doing our best to continue to make devices like the OnePlus 6 safe and usable.
The phone is currently capable of booting modern Linux with only a few patches, check the table on the right (or above on mobile) for the hardware support checklist.
Despite being able to run an up to date kernel, we are still dependant on the now aging firmware for features like the bootloader, modem, wifi and bluetooth to function, whilst it is relatively unlikely that a vulnerability is discovered in this firmware, it is absolutely a possibility. Until OnePlus release the signing keys used to sign new versions of the firmware - allowing us to potentially make use of future security patches - we're stuck with what we've got.
How to enter flash mode
Unplug from USB and hold START
and information about the device.
For the OnePlus 6T, hold and both volume buttons.
![]() |
If you're struggling to enter fastboot, ensure that you have unplugged the USB cable and do not release the button combination until after the START text appears on screen |
Installing
![]() |
The bootloader is the only firmware that postmarketOS doesn't install itself, all other firmware (devicetree, gpu, modem etc) is supplied by postmarketOS. In contrast to custom Android ROMs, it is incredibly unlikely that any bugs or issues you encounter are caused by whatever OS you previously had installed on the device. |
Prerequisites
To install prebuilt images, you will need:
1. A computer with fastboot
This can be obtained by installed the android-tools
package on Linux or by installing the Android SDK Platform-Tools on Windows, Mac (or Linux).
Upgrade
Before installing postmarketOS, it's recommended that you upgrade your device to the latest release of OxygenOS (OnePlus's version of Android). This is not a requirement but is heavily recommended. Try this first if you encounter issues with fastboot.
Unlock the bootloader
Before installing postmarketOS you have to unlock your bootloader. For the T-Mobile version of the device in the US, refer to Google for guides on obtaining an unlock code. If your device is not carrier locked, the following is all that's needed to unlock the bootloader:
1. Open setting, go to "About" and tap on the "Build number" box ~10 times until the "You are now a developer" toast message appears.
2. Go back to the main settings page, go to "System" and then "Developer options" (it might be hiding behind a dropdown menu). Toggle the switch to "Enable OEM unlocking"
3. Refer to "How to enter flash mode" above to get into fastboot mode, then re-attach your USB cable. Run the following command on your host:
fastboot oem unlock
If you see < waiting for any device >
, try running as sudo
and restart your device into fastboot mode again.
4. Read the message displayed on your device screen. Once read, confirm the unlock if you're willing to proceed. THIS WILL ERASE YOUR DEVICE'S INTERNAL STORAGE.
All done! You can now continue with this guide.
Pre-built images
Follow the installation article to download image files, note that the device code-names are oneplus-enchilada
for the OnePlus 6 and oneplus-fajita
for the 6T.
Once downloaded, decompress the files with unxz
. On Windows you can use a tool like 7zip.
Finally, use fastboot to flash:
![]() |
Erasing the dtbo partition will make Android (and ALL Android-based software like Ubuntu Touch or TWRP recovery) unbootable on the current slot (read this page if you're not sure what that means). You can re-flash an Android ROM via fastboot by extracting the payload.bin from the OTA zip and using a tool like android-ota-payload-extractor to get the individual partition images. It is almost never necessary to resort to extreme measures like "MSM Download tool" to reflash the device via EDL |
fastboot erase dtbo fastboot flash boot [the file that ends in -boot.img] fastboot flash userdata [the other file]
If you see < waiting for any device >
, try running as sudo
and restart your device into fastboot mode again.
It can be effective to select "Restart Bootloader" on the phone's bootloader after each command succeeds, to avoid above "waiting for device" connection problem.
Manual build
The vendor is OnePlus, the codename is "enchilada" for the OnePlus 6 and "fajita" for the OnePlus 6T.
Follow the pmbootstrap article, until you have done the install action (note that `--fde` stands for full-disk-encryption - this can also be left out).
pmbootstrap install --fde
Reboot back into flash mode as explained above. (If you encounter weird behaviour like the command getting stuck before the flashing starts, reboot into flash mode or select "Restart Bootloader" on the phone itself)
By default the rootfs will be flashed to system, this doesn't leave much free space for your applications / data, if you don't mind factory resetting the device you can instead flash to userdata by specifying the partition like below.
fastboot erase dtbo pmbootstrap flasher flash_rootfs --partition userdata pmbootstrap flasher flash_kernel
Reboot and you're good to go!
If you have flashing or booting issues, try first flashing the latest OxygenOS to the slot you want to install postmarketOS to (ie, flash in TWRP from your other slot). If you still have no luck, try flashing OxygenOS 9 as the bootloader can be more forgiving.
Dual booting
The OnePlus 6 uses an A/B partitioning scheme, duplicating most important partitions. Because this includes the boot partition (which contains the kernel) we're able to re-use it to dual boot with some other OS such as Android, if you don't mind jumping through a few hoops.
See more on how A/B slots work and how to interact with them here.
Flashing to system
It is possible to dual boot with Android when flashing postmarketOS to the system partition, although this severely limits the space available (i.e. to ~2GB).
In fastboot mode run fastboot getvar current-slot
to get the currently active slot (the slot that has your current Android installation). For this example we'll assume that it's slot a
(for b
simply swap the slots in the commands below). To install postmarketOS to the inactive slot, we run
fastboot set_active b
before following the flashing steps, as well as replacing userdata
in the flashing commands with system
to avoid overwriting your android data (and preventing Android from booting).
You can now switch back to Android by entering fastboot mode and running
fastboot set_active a
Note: Substituting system for vendor is also fine. This setup also allows for a recovery pmOS install, since all partitions are accessible on any booted OS, so long as there is root access.
Sharing userdata with Android
It's possible to share the userdata partition with Android, using it as the postmarketOS rootfs as well as the Android data partition at the same time. This may come with unintended side effects but initial testing shows that it works well enough.
The postmarketOS rootfs image is not actually an ext4 image, it's actually a full disk image containing two partitions, Android obviously doesn't know how to handle this so we have to split it up. You can do this manually with a prebuilt but that is left as an exercise to the reader...
This method will erase your userdata partition, it is also non-trivial to "uninstall" postmarketOS.
Before continuing, flash your Android ROM of choice and ensure that it boots. Don't go through setup as these steps will erase userdata.
Run through pmbootstrap init like explained above, but instead of running pmbootstrap install
run
pmbootstrap install --split pmbootstrap export
You can now manually flash the boot and root partitions, note that the "boot" partition here isn't the Android boot partition, it's the postmarketOS boot partition which is used to keep the kernel, initramfs etc. We can place the boot image on vendor on the slot with postmarketOS. Make sure not to run this on your Android slot.
fastboot flash userdata /tmp/postmarketOS-export/oneplus-[enchilada|fajita]-root.img fastboot flash vendor /tmp/postmarketOS-export/oneplus-[enchilada|fajita]-boot.img
The postmarketOS initramfs will automatically detect these during boot. You can now flash the boot partition, erase dtbo and boot postmarketOS as usual! You must boot postmarketOS so that it can resize the userdata partition before you boot Android. Once pmos first boot is done you can reboot and use fastboot to switch slots.
If pmOS does not resize the partition properly, run the following on pmOS
sudo resize2fs /dev/sda17
Advanced Partitioning
WARNING: This is a dangerous process that may hard-brick your phone, requiring the use of poorly documented EDL-mode recovery tools to fix |
More information on partitioning userdata available at OnePlus 6 (oneplus-enchilada)/Custom Partitioning.
Fastboot bugs
If you encounter "weird" errors from fastboot, such as "device does not support slots":
Once the device is in fastboot mode unplug it, run your fastboot / flasher command and wait for the "<waiting for device>" message, now choose "reboot bootloader" on the device and press the power button to select, plug in the device while it reboots.
Upgrading
Upgrading can be done through Alpines package manager "apk", to upgrade everything simply open a terminal and run sudo apk upgrade -a
. This includes kernel upgrades.
Building
Feel like helping? Want to learn kernel development?
Check out the mainlining guide SDM845 Mainlining for detailed SDM845 specific instructions on initial device porting and building.
Feel free to contact @caleb (or anyone) in the #postmarketos-mainline matrix channel if you're stuck.
Info
Hacking
See Hacking for details.
Partition map
oneplus-enchilada:~$ ls -lah /dev/disk/by-partlabel/
Upgrading firmware without Android installed
When you install postmarketOS and all you get is just blank screen after a reboot or you have some other problems it is possible that firmware was not upgraded. Follow these steps to upgrade firmware.
- Download newest firmware from here
- Extract payload.bin file from zip you downloaded in a previous step
- Extract firmware with payload-dumper-go or payload_dumper
- Run command:
payload-dumper-go payload.bin
- Enter fastboot mode
- Unlock partitions for flashing
fastboot flashing unlock_critical
- Run below commands to update firmware
fastboot flash abl abl.img fastboot flash aop aop.img fastboot flash bluetooth bluetooth.img fastboot flash cmnlib cmnlib.img fastboot flash cmnlib64 cmnlib64.img fastboot flash devcfg devcfg.img fastboot flash dsp dsp.img fastboot flash fw_4j1ed fw_4j1ed.img fastboot flash fw_4u1ea fw_4u1ea.img fastboot flash hyp hyp.img fastboot flash keymaster keymaster.img fastboot flash LOGO LOGO.img fastboot flash --slot=all modem modem.img fastboot flash oem_stanvbk oem_stanvbk.img fastboot flash qupfw qupfw.img fastboot flash storsec storsec.img fastboot flash tz tz.img fastboot flash xbl xbl.img fastboot flash xbl_config xbl_config.img
The big list of issues
In no particular order...
Tri-state key support
First support was in userspace: https://github.com/michele-perrone/postmarketos-oneplus6-tristatekey
A kernel device driver for the tri-state key has now been developed, and it emits EV_SW with codes 17/18/19 for the top/middle/bottom states.
It has been suggested that the kernel driver is converted to using the ABS_MISC codes rather than introduce more "generic" input events.
The next step is to write hkdm configs for it but this may need to wait for the driver to get upstreamed. hkdm itself needs support for EV_SW devices added.
One can get around this quirk by tweaking the file ~/.config/gtk-3.0/gtk.css
with something such as:
.phosh-topbar-clock { padding-left: 130px; }
to move the clock slightly to the right of the notch.
The rounded corners on the 6T can be annoying as well.
OTG doesn't work
"OTG" (USB-C role switching to host mode) is blocked on USB-C power delivery support in the charger driver. Host mode can be forced by modifying the DTS when building a kernel, but it isn't clear what this fixes or may break (e.g. charging).
See this matrix post by User:Kalube:
no, OTG isn't really a thing anymore anyway - it's technically specific to micro USB, usb-c has role-switching where a device can either be a host device or a peripheral device. Right now we force peripheral mode always. Once support for the full USB-C power delivery system is implemented in the charger driver, we can negotiate a role with the other device, e.g. if it's a powered dock we want to charge but also be the host device.
Once that's done we can implement DP alt mode on top which requires talking to the dwc3 driver I think, and configuring some external orientation switch for the USB SBU pins which are directional and required by displayport
that's all the missing pieces, that will give us displayport on the SHIFT6mq, neither the pocophone F1 nor OnePlus 6 support DP alt mode
Host mode can be enabled by changing the dtb, to do this install dtc and decompile the appropriate file for you device like so:
# apk add dtc # cd /boot/dtbs/qcom # dtc sdm845-oneplus-<model>.dtb -o temp.dts
Now edit the temp.dts file and change dr_mode from "peripheral" to "host", recompile it and run mkinitfs to regenerate and flash the boot image:
# dtc temp.dts -o sdm845-oneplus-<model>.dtb # mkinitfs # reboot
To revert the changes just do the same thing again but change the line back to peripheral, kernel updates will also revert it.
The phone won't supply its own power, so you need either a powered hub or an extension cable wired up to 5v. Some hubs may refuse to work without power being supplied from the port however.
Third party displays and touch panel issues
Some manufacturer realised they could cheap out on touch controllers, so 3rd party touch panels don't actually implement the synaptics rmi4 spec properly. The rmi4 driver will need some hacks to deal with this.
My regular 6 with a display replacement also seems to fail to init the display after its been reset.
RMI4 attempting to probe on a fake touch IC will look something like the following:
[ 3.502580] rmi4_i2c 12-0020: registering I2C-connected sensor [ 6.081770] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: unknown, product: , fw id: 0 [ 6.094861] rmi4_f12 rmi4-00.fn12: Behavior of F12 without register descriptors is undefined.
GPS
Depending on the carrier config, GPS with ModemManager can work: mmcli --location-enable-gps-nmea
followed by mmcli --location-get
returns NMEA phrases. Keep in mind that modem only works when a sim card is inserted.
Normally, information about which satellites are where to expect (satellite almanac of orbit) is retrieved from the GPS satellites themselves and that can take at least roughly 12 min with a good signal, however here is were A-GPS (assisted GPS) steps in by providing internet services to augment GPS with those generic data.
The carrier config selected by ModemManager (mmcli -m any | grep 'carrier config'
) also contains configuration for A-GPS. Whether the config is complete in that regard can be checked with mmcli -m any --location-status
as it should contain assistance servers. If not, you might experience not continuous and only infrequent GPS fixes and other problems regarding GPS.
See this comment thread for more details.
Camera
Have to dump sensor init sequence from downstream and pray, need more time for tweaking this but it should be possible to make it work
Sensors
Initial sensor support is/will be added in pmaports!4050
TrustZone
Drivers to communicate with the QSEE (Qualcomm Secure Execution Environment) are not on mainline and you can't flash OP-TEE because XBL_SEC checks the signature. Those drivers are called QSEECOM in the CAF kernel but there is the need to standardize them using the generic interface defined in include/uapi/linux/tee.h
. You can use the OP-TEE implementation as an example. More documentation here https://www.kernel.org/doc/html/latest/staging/tee.html.
Having a TrustZone is useful to do a lot of things related to security, but mainly fingerprint management, secure encryption involved in NFC, useful to emulate contactless smart cards, and Widevine L1 to watch premium streaming services with the best resolution!
Regarding DRMs and userland, on Waydroid or Android mainline you need to develop oemcrypto.so
with the support of the standard API for the TEE; manufacturers implement it with their custom interfaces. Look at this https://source.android.com/devices/drm#drm-plugins.
On GNU/Linux, you need to implement/enable Widevine L1 on players. For example on Firefox, if you want to watch Netflix or other in-browser streaming services, but you might also want to use an extension like https://github.com/lkmvip/netflix-4K-DDplus to spoof the device and so make Netflix give you the encrypted stream. Another good implementation opportunity is on FFMPEG/VLC, it would be cool to make VLC able to stream Netflix and also having the possibility to save decrypted streams.
Fastboot flashing issues
The fastboot implementation leaves some to be desired... If you encounter issues flashing with fastboot getting stuck or displaying weird errors like device does not support slots
, prepare the fastboot flash command in your terminal, on the device choose the "reboot bootloader" option from fastboot, press the power button to confirm and then run the command while the device reboots.
You'll see a "waiting for device" message in your terminal, the flashing should start as soon as the device gets back into fastboot mode.
Modem bugs
The recent enablement of ModemManager enables SMS and mobile data to work on supported SDM845 devices including the OnePlus 6 and 6T. It isn't possible to test these extensively due to the number of region specific and carrier specific issues that could arise.
If you're encountering modem issues, perform the following steps to collect logs and submit them so that I or someone else can review:
On your device with SIM card inserted:
sudo service modemmanager stop sudo service msm-modem-uim-selection restart sudo ModemManager --debug 2>&1 | tee mm.log
If your device requires SIM unlocking, perform that in Phosh settings, wait for a few seconds and then stop modemmanager again.
Create a new issue in ModemManager here to explain your issue, include a link to a pastebin containing the logs you captured (they're in mm.log in your home directory on device). At the bottom of your issue add Cc: @calebccff
so that I'll be notified.
Please also include the output of uname -a
and sudo qmicli -d qrtr://0 --uim-get-card-status
in your issue.
Sim not appearing
Some SIM cards or modem firmwares might take longer to initialize. If the SIM card does not appear, but sudo qmicli -d qrtr://0 --uim-get-card-status
shows that the card is present (Card state: 'present'
), one possible solution is to increase the wait time for the SIM card to appear after starting the modem. Edit the file: /etc/conf.d/msm-modem-uim-selection
and change: sim_wait_time=1
to sim_wait_time=30
and reboot.
Dual Sim
Some users have reported issues with dual SIM causing modemmanager issues, whilst modemmanager should automatically select the first SIM, it lacks proper dual SIM support and sometimes can get confused. Currently the best workaround is to make sure you only have one SIM card inserted.
Community Info
postmarketOS users that own the device
- Aa13q
- Aleksander (Notes: WWAN stack tinkering)
- Antonok
- AppleCross (Notes: PostmarketOS Gnome)
- BenTheTechGuy (Notes: On loan)
- Blacklight
- BotchedRPR (Notes: dead (crashdump mode))
- Breakfastisready (Notes: 128GB)
- CalcProgrammer1
- Caleb (Notes: 256GB postmarketOS daily driver)
- Caleb (Notes: 3rd party touch screen to be fixed)
- Caleb (Notes: lab rat)
- Chainbits (Notes: daily driver, available for testing)
- Chayleaf (Notes: 8/128; runs NixOS)
- Clygro (Notes: 8GB/128GB, current main pmOS)
- Craftyguy
- DanSman (Notes: pmOS (v24.12 + FDE) UI: plasma-mobile)
- Deathmist (Notes: 8/128 GB model)
- DevelLevel
- DrGit (Notes: 256GB)
- DylanVanAssche (Notes: LineageOS)
- E-v (Notes: [available for testing] 128 GB, dual boot with DivestOS, userdata partition split in two)
- Earboxer (Notes: formerly sxmo-sway on pmOS edge. current daily driver(2023). Still using pulseaudio, custom alsa UCM to fix thing. using Hyprland)
- Elagost (Notes: family device running Android, can't wipe)
- Emacsevangelist (Notes: Runs pmOS with a custom EXWM-based UI)
- EnderNightLord
- EspiDev (Notes: 8/128 GB Plasma Mobile)
- Fossdd (Notes: edge, systemd, gnome mobile: experimental device for testing purposes)
- Frankwalter (Notes: [6GB/128GB] I bought it to experiment with Linux mobile, so I can help mainlining it and learn about drivers development in the process! (fajita))
- FuchtelJockel (Notes: daily driver (DivestOS))
- Gbhdrew (Notes: About to start testing for daily use)
- Giannidunk (Notes: 128 GB)
- Hacker420 (Notes: Daily driver, dualbooted with Android and pmOS on the other slot. (8/128))
- Hastalavista (Notes: LineageOS)
- Haui2 (Notes: Running pmOS stable and phosh)
- Iramosu (Notes: 8/128GB GNOME)
- Jrg
- Juliaff7 (Notes: Testing pmOS)
- JuniorJPDJ
- Kbingham
- Ksqeib (Notes: Using as Minecraft Server)
- Langfingaz (Notes: Running PostmarketOS edge)
- Linmob (Notes: Kupfer with Phosh)
- Lolgzs (Notes: 128GB, PMOS daily driver)
- Manut (Notes: edge, phosh)
- Mattdaha (Notes: 1x pmos, 1x lineageos daily driver)
- Memoryfile (Notes: spare phone running GNOME mobile)
- Naproxen (Notes: Daily Driver)
- NekoCWD (Notes: 6/64GB postmarketOS daily driver)
- No112 (Notes: currently non-functional with a dangerous looking battery)
- Okias (Notes: 8G/128G)
- Operachi (Notes: Android + PostmarketOS (Main PostmarketOS Phone))
- PanzerSajt
- Plata (Notes: Plasma Mobile)
- Proycon (Notes: daily driver with sxmo)
- QC8086
- R00t (Notes: running ubuntu touch, screen blacks out randomly)
- Rabbit (Notes: Daily driver, GNOME mobile, 128GB)
- Retourmy (Notes: Powerfull indeed, but no VoLTE. Reinstalled "from" OOS 9.0.8 to have GPS working with all cariiers)
- Robert.mader (Notes: Development / Testing)
- Russanandres (Notes: PMOS)
- Sado1 (Notes: x4, one with screen replacement)
- SevralT (Notes: My second phone for Linux ;p)
- Some Chinese Guy (Notes: daily driver)
- StephanieBread (Notes: pmOS edge with Gnome-Mobile, daily driver)
- Sulu
- Susurrus (Notes: Broken front camera)
- Syboxez (Notes: (128G/8G) Daily driver on one slot, kupfer on the other)
- Techwizz (Notes: Running postmarketOS)
- ThatGeekZen (Notes: PMOS Daily Driver)
- Thenightterrorx (Notes: Now running lineageOS,pmOS used as daily driver for a while, but call audio kept breaking)
- TQMatvey (Notes: Third-party Touchscreen, dualboot linux and CrDroid)
- Usia (Notes: running e/os/)
- Usia (Notes: running PostmarketOS)
- WhyNotHugo (Notes: Running postmarketOS. Mostly for experimentation.)
- Wjtje (Notes: Second phone for running PostmarketOS edge)
- Xanadul (Notes: 128 GB)
Maintainers
See also
Internal pages
- OnePlus 6 (oneplus-enchilada)/Hacking
- OnePlus 6 (oneplus-enchilada)/Multi Booting and Custom Partitioning
External links
- Kernel sources
- pmaports!1221 Initial merge request.
- pmaports!1271 Updates to add panel mode and WiFi support.
- pmaports!2088 Move the OnePlus 6 to "community" devices category
- pmaports!1967 Switch to common linux-postmarketos-qcom-sdm845 kernel instead of device specific kernel
- pmaports!2206 Update to 5.12.8 and add support for the speaker / headphone jack on the OnePlus 6
- pmaports!2215 Support automatic kernel updates for Android devices (including A/B!)
- Enchilada device package
- Fajita device package
- Kernel package
- postmarketOS podcast interview with Caleb about mainlining the OnePlus 6
- Documentation on A/B slots