Jump to content

OnePlus 6 (oneplus-enchilada): Difference between revisions

From postmarketOS Wiki
Exkc (talk | contribs)
No edit summary
Susurrus (talk | contribs)
Add specific model numbers
 
(105 intermediate revisions by 31 users not shown)
Line 7: Line 7:
| releaseyear = 2018
| releaseyear = 2018
| category = community
| category = community
| originalsoftware = Android
| originalsoftware = Android (OxygenOS/HydrogenOS)
| originalversion = 8.0
| originalversion = 8.0
| extendedversion = 11 on Linux 4.9 (OxygenOS 11.1.2.2)
| extendedversion = 11 on Linux 4.9 (OxygenOS 11.1.2.2)
Line 18: Line 18:
| architecture = aarch64
| architecture = aarch64
| type = handset
| type = handset
| model = ONEPLUS A6000
| model = A6000, A6003
<!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) -->
<!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) -->
| status_usbnet = Y
| status_usbnet = Y
| status_flashing = Y
| status_flashing = Y
| status_emmc = Y
| status_sdcard = -
| status_touch = Y
| status_touch = Y
| status_screen = Y
| status_screen = Y
| status_wifi = Y
| status_wifi = P
| status_xwayland = Y
| status_xwayland = Y
| status_fde = Y
| status_fde = Y
Line 30: Line 32:
| status_battery = Y
| status_battery = Y
| status_3d = Y
| status_3d = Y
| status_accel = N
| status_accel = Y
| status_haptics = Y
| status_haptics = Y
| status_audio = Y
| status_audio = Y
| status_bluetooth = Y
| status_bluetooth = Y
| status_camera = N
| status_camera = P
| status_gps = P
| status_gps = P
| status_trustzone = N
| status_trustzone = N
| status_mobiledata = Y
| status_mobiledata = P
| status_sms = Y
| status_sms = P
| status_calls = Y
| status_calls = P
| status = Maintained, supported and upstream!
| status = Maintained, supported and upstream!
| booting = yes
| booting = yes
| pmoskernel = Mainline
| pmoskernel = Mainline
| whet_dhry = 6029.9
| whet_dhry = 6029.9
| status_otg = N
| status_otg = P
| status_nfc = N
| status_nfc = P
}}
| status_cameraflash = Y
{{Based on SoC|Qualcomm_Snapdragon_845_(SDM845)|Snapdragon 845}}
| status_dvb = -
| status_fossbootloader = N
| status_irtx = -
| status_irrx = -
| status_stylus = -
| status_ethernet = -
| status_hdmidp = -
| status_usba = -
| status_touchpad = -
| status_keyboard = -
| status_light = Y
| status_proximity = Y
| status_magnet = Y
| status_hall = N
| genericdevice=Qualcomm SDM845 (qualcomm-sdm845)
| optionalgenericdevice = yes
}}<!--
-->{{Based on SoC|Qualcomm_Snapdragon_845_(SDM845)|Snapdragon 845}}


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.
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.
Line 55: Line 74:
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.
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.
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. While it is relatively unlikely that a vulnerability is discovered in this firmware, it is absolutely a possibility. Until OnePlus releases 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 ==
== How to enter flash mode ==
Line 67: Line 86:
== Installing ==
== Installing ==


{{Notice|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 <strong>incredibly unlikely</strong> that any bugs or issues you encounter are caused by whatever OS you previously had installed on the device.}}
{{Notice|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 <strong>incredibly unlikely</strong> that any bugs or issues you encounter are caused by whatever OS you previously had installed on the device.}}


=== Prerequisites ===
=== Prerequisites ===
Line 75: Line 94:
1. A computer with fastboot
1. A computer with fastboot


This can be obtained by installed the <code>android-tools</code> package on Linux or by installing the [https://developer.android.com/studio/releases/platform-tools Android SDK Platform-Tools] on Windows, Mac (or Linux).
This can be obtained by installing the <code>android-tools</code> package on Linux or by installing the [https://developer.android.com/studio/releases/platform-tools Android SDK Platform-Tools] on Windows, Mac (or Linux).


==== Upgrade ====
==== 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.
Before installing postmarketOS, it's recommended that you upgrade your device to the latest release of OxygenOS (OnePlus's version of Android) on both slots. This is not a requirement but is heavily recommended to get GPS working. Try this first if you encounter issues with fastboot.
 
{{Notice|If you have a very old version of OxygenOS (for example after using the "MSM Download tool" for android 10), you probably need to [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/1825#note_1223990136 update twice], because the device uses A/B partitioning ([[Android_AB_Slots|read this page if you're not sure what that means]]). First do a normal update, then find the latest version of OxygenOS OTA signed zip, upload it to the phone, go to the updater in the settings and do a local update of the latest version again ([https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/1825#note_1224052491 source]). OnePlus' [https://www.oneplus.com/us/support/softwareupgrade support/softwareupgrade] page seems to be inaccessible at this moment, so look at [https://forum.xda-developers.com/t/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.3792244/ this XDA thread for 6] and [https://forum.xda-developers.com/t/oneplus-6t-global-rom-ota-oxygen-os-repo-of-oxygen-os-builds.3865396/ this one for 6T]}}


==== Unlock the bootloader ====
==== Unlock the bootloader ====
Line 85: Line 106:
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:
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.
1. Open Settings, 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"
2. Go back to the main settings page, go to "System" and then "Developer options" (it might be hidden 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:
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:
Line 109: Line 130:
Finally, use fastboot to flash:
Finally, use fastboot to flash:


{{Notice|Erasing the dtbo partition will make Android (and <b>ALL</b> Android-based software like Ubuntu Touch or TWRP recovery) unbootable on the current slot ([[Android_AB_Slots|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 [https://github.com/tobyxdd/android-ota-payload-extractor 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}}
{{Notice|Erasing the dtbo partition will make Android (and <b>ALL</b> Android-based software like Ubuntu Touch or TWRP recovery) unbootable on the current slot ([[Android_AB_Slots|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 [https://github.com/tobyxdd/android-ota-payload-extractor 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.}}
 
{{Hint|If you are using Arch Linux and getting errors like <code>std::out_of_range</code>. Uninstall [https://archlinux.org/packages/extra/x86_64/android-tools android-tools] and install [https://aur.archlinux.org/packages/android-sdk-platform-tools android-sdk-platform-tools] from the AUR<ref>https://xdaforums.com/t/some-std-out_of_range-error-with-fastboot-on-linux.4626285/</ref><ref>https://gitlab.archlinux.org/archlinux/packaging/packages/android-tools/-/issues/4</ref> or build and flash your own build with [[pmbootstrap]]}}


<pre>
<pre>
Line 119: Line 142:
If you see <code>< waiting for any device ></code>, try running as <code>sudo</code> and restart your device into fastboot mode again.
If you see <code>< waiting for any device ></code>, try running as <code>sudo</code> 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.
It can be effective to run <code>fastboot reboot</code> after each command succeeds, to avoid above "waiting for device" connection problem.
 
{{warning|Do not reboot via the power button on the device! This can result in not all data being properly written to storage, corrupting the rootfs and resulting strange behaviour like postmarketOS getting stuck during boot!}}
{{note|Always use <code>fastboot reboot</code> after flashing.}}




Line 126: Line 152:
The vendor is OnePlus, the codename is "enchilada" for the OnePlus 6 and "fajita" for the OnePlus 6T.
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).
Follow the [[pmbootstrap]] article, until you have done the install action.
 
With FDE (it stands for Full Disk Encryption)
<pre>
<pre>
pmbootstrap install --fde
pmbootstrap install --split --fde
pmbootstrap export
</pre>
</pre>
 
Without
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.
<pre>
<pre>
fastboot erase dtbo
pmbootstrap install
pmbootstrap flasher flash_rootfs --partition userdata
pmbootstrap flasher flash_kernel
</pre>
</pre>


Reboot and you're good to go!
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)


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.
Without FDE by default, the rootfs will be flashed to the system partition. This doesn't leave much free space for your applications / data, so if you don't mind factory resetting the device you can instead flash to the userdata partition by specifying the partition like below.


== Dual booting ==
{{warning|Do not reboot using the power button on the device! This can result in not all data being properly written to storage, corrupting the rootfs and resulting in strange behaviour like postmarketOS getting stuck during boot!}}
{{note|Always use <code>fastboot reboot</code> after flashing.}}


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.
==== With FDE ====
By booting [https://twrp.me/oneplus/oneplus6.html twrp] from bootloader/fastboot mode you can do the partitioning.


[[Android_AB_Slots|See more on how A/B slots work and how to interact with them here]].
If you install pmOS only to the slot b you can install twrp as recovery.<br>
After partitioning you will need to format userdata in twrp.<br>
You can install to both slots if you prefer.


=== Flashing to system ===
In twrp (Android 11 version ie. 3.7.0) in <code>Advanced->Terminal</code> you can use <code>sgdisk</code>, it has long flags only e.g. <code>--print</code> and not <code>-p</code>.<br>
Or you can use <code>adb shell</code> (when booted into twrp) to run these commands from your computer.


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).
<pre>
 
#Get userdata number and info on the disk
In fastboot mode run <code>fastboot getvar current-slot</code> to get the currently active slot (the slot that has your current Android installation). For this example we'll assume that it's slot <code>a</code> (for <code>b</code> simply swap the slots in the commands below). To install postmarketOS to the inactive slot, we run
sgdisk /dev/block/sda --print


<pre>
#Delete userdata partition to remake it smaller
fastboot set_active b
sgdisk /dev/block/sda --delete=17
</pre>


before following the flashing steps, as well as replacing <code>userdata</code> in the flashing commands with <code>system</code> to avoid overwriting your android data (and preventing Android from booting).
#Make userdata 2 gigabytes, minimum size unknown
sgdisk /dev/block/sda --new=0:0:+2G --change-name=0:userdata


You can now switch back to Android by entering fastboot mode and running
#Make pmOS boot partition 256 megabytes (default size)
sgdisk /dev/block/sda --new=0:0:+256M --change-name=0:pmOS_boot


<pre>
#Make pmOS system partition uses the rest of the disk
fastboot set_active a
sgdisk /dev/block/sda --new=0:0:0 --change-name=0:pmOS_root
</pre>
</pre>
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 <code>pmbootstrap install</code> run


<pre>
<pre>
pmbootstrap install --split
#Both slots
pmbootstrap export
fastboot erase dtbo
</pre>
fastboot flash pmOS_boot /tmp/postmarketOS-export/oneplus-enchilada-boot.img
fastboot flash pmOS_root /tmp/postmarketOS-export/oneplus-enchilada-root.img
fastboot flash boot /tmp/postmarketOS-export/boot.img
fastboot reboot


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.
#Slot b only
 
fastboot erase dtbo_b
<pre>
fastboot flash pmOS_boot /tmp/postmarketOS-export/oneplus-enchilada-boot.img
fastboot flash userdata /tmp/postmarketOS-export/oneplus-[enchilada|fajita]-root.img
fastboot flash pmOS_root /tmp/postmarketOS-export/oneplus-enchilada-root.img
fastboot flash vendor /tmp/postmarketOS-export/oneplus-[enchilada|fajita]-boot.img
fastboot flash boot_b /tmp/postmarketOS-export/boot.img
fastboot set_active b
fastboot reboot
</pre>
</pre>


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.
==== Without FDE ====
 
If pmOS does not resize the partition properly, run the following on pmOS


<pre>
<pre>
sudo resize2fs /dev/sda17
fastboot erase dtbo
pmbootstrap flasher flash_rootfs --partition userdata
pmbootstrap flasher flash_kernel
pmbootstrap chroot fastboot reboot
</pre>
</pre>


===Advanced Partitioning===
If you have flashing or booting issues, try flashing the latest version of OxygenOS to the slot you want to install postmarketOS to (i.e., flash the ROM using TWRP from your other slot). If you still have no luck, try flashing OxygenOS 9, as the bootloader can be more forgiving.


{{Warning|This is a dangerous process that may hard-brick your phone, requiring the use of poorly documented EDL-mode recovery tools to fix}}
== Dual booting ==
 
(See [[OnePlus_6_(oneplus-enchilada)/Dual_Booting_and_Custom_Partitioning]])
More information on partitioning userdata available at [[OnePlus 6 (oneplus-enchilada)/Custom Partitioning]].


== Fastboot bugs ==
== Fastboot bugs ==
Line 213: Line 233:
If you encounter "weird" errors from fastboot, such as "device does not support slots":
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.
Once the device is in fastboot mode, unplug it, run your fastboot / flasher command and wait for the "<waiting for device>" message, then choose the "reboot bootloader" option on the device, press the power button to select that option and 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 <code>sudo apk upgrade -a</code>. This includes kernel upgrades.


== Building ==
== Building ==
Line 226: Line 242:


Feel free to contact @caleb (or anyone) in the [[Matrix and IRC|#postmarketos-mainline]] matrix channel if you're stuck.
Feel free to contact @caleb (or anyone) in the [[Matrix and IRC|#postmarketos-mainline]] matrix channel if you're stuck.
See [https://wiki.postmarketos.org/wiki/User:Magdesign#Compile_Kernel this] quick and dirty tutorial on how to build the kernel.


== Info ==
== Info ==
Line 346: Line 364:
</div>
</div>
</div>
</div>
=== Camera Flash ===
Two leds (yellow and white), both functionnal, at the back of the phone.
Their max brightness value is 255.
A simple extension for Gnome mobile adds a button to the activities overview : https://gitlab.com/NekoCWD/nekotorch
See [[LEDs|LEDs]] for more details.


== Upgrading firmware without Android installed ==
== Upgrading firmware without Android installed ==
Line 382: Line 410:
fastboot flash xbl_config xbl_config.img
fastboot flash xbl_config xbl_config.img
</pre>
</pre>
* If you are not able to write via fastboot, even after <pre>unlock_critical</pre> [https://wiki.postmarketos.org/wiki/User:Magdesign#Install_Stock_Android_9.0.8 use edl mode] instead (turn off phone, push volume +/- and plugin the usb cable):
<pre> edl w abl_a abl.img </pre>
and so on with all the mentioned files.


== The big list of issues ==
== The big list of issues ==


In no particular order...
In no particular order...
=== Audio in calls ===
There are issues with audio disappearing in calls.


=== Tri-state key support ===
=== Tri-state key support ===
Line 395: Line 433:
It has been suggested that [https://lore.kernel.org/linux-arm-msm/YvQyOhgSGjQLHHvv@google.com/ the kernel driver is converted to using the ABS_MISC codes] rather than introduce more "generic" input events.
It has been suggested that [https://lore.kernel.org/linux-arm-msm/YvQyOhgSGjQLHHvv@google.com/ the kernel driver is converted to using the ABS_MISC codes] rather than introduce more "generic" input events.


The next step is to write [https://gitlab.com/postmarketOS/hkdm 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.
The next step is to write [https://gitlab.postmarketos.org/postmarketOS/hkdm 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.
 
=== Phosh clock hidden by notch ===
 
One can get around this quirk by tweaking the file <code>~/.config/gtk-3.0/gtk.css</code> with something such as:
 
<pre>
.phosh-topbar-clock {
  padding-left: 130px;
}
</pre>
 
to move the clock slightly to the right of the notch.


The rounded corners on the 6T can be annoying as well.
If you use Phosh with systemd, the tri-state button should work out-of-the-box (if {{MR|5969|pmaports}} is merged).


=== OTG doesn't work ===
=== 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).
"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.


See [https://matrix.to/#/!xgUMIsYnSIXklwbhrG:postmarketos.org/$DEx89n6NY1ERE6TrCKe6Q_tkTOwiylXpKzDwOFY7cC8?via=postmarketos.org&via=matrix.org&via=kde.org this matrix post] by [[User:Kalube]]:
See [https://matrix.to/#/!xgUMIsYnSIXklwbhrG:postmarketos.org/$DEx89n6NY1ERE6TrCKe6Q_tkTOwiylXpKzDwOFY7cC8?via=postmarketos.org&via=matrix.org&via=kde.org this matrix post] by [[User:Caleb]]:
<blockquote>
<blockquote>
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.
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.
Line 420: Line 446:
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
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
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
</blockquote>
</blockquote>


Host mode can be enabled by changing the dtb, to do this install dtc and decompile the appropriate file for you device like so:
{{note|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.
}}
Host mode can be enabled by Dts method and Sysfs method.
==== Dts method ====
Install dtc and decompile the appropriate file for you device like so:
<pre>
<pre>
# apk add dtc
# apk add dtc
Line 438: Line 468:
To revert the changes just do the same thing again but change the line back to peripheral, kernel updates will also revert it.
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.
==== Sysfs method ====
 
Change "device" to "host" in "/sys/kernel/debug/usb/a600000.usb/mode" :
== Third party displays and touch panel issues ==
<pre>
 
# echo host | sudo tee /sys/kernel/debug/usb/a600000.usb/mode
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.
</pre>


My regular 6 with a display replacement also seems to fail to init the display after its been reset.
To revert the changes just do the same thing again but change host to device or reboot the device.


RMI4 attempting to probe on a fake touch IC will look something like the following:
==== Verify ====
Run the command as below to verify:
<pre>
<pre>
[    3.502580] rmi4_i2c 12-0020: registering I2C-connected sensor
# sudo cat /sys/kernel/debug/usb/a600000.usb/mode
[    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.
</pre>
</pre>
If the command return <code>host</code> then congratulation you have enabled the host mode successfully.


== GPS ==
== GPS ==
Depending on the carrier config, GPS with ModemManager can work: <code>mmcli --location-enable-gps-nmea</code> followed by <code>mmcli --location-get</code> 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.
{{warning| To use and test GPS functions,
make sure a SIM card is inserted (mmcli v1.22.x), GPS is enabled in mmcli, geoclue is executed. Then disable suspend, go outside for 15min. until you get a fix}}
 
'''Carefully read [[Troubleshooting:GPS]] for more details on how to activate the GPS using ModemManager's CLI and enabeling Geoclue.'''


The carrier config selected by ModemManager (<code>mmcli -m any | grep 'carrier config'</code>) also contains configuration for A-GPS. Whether the config is complete in that regard can be checked with <code>mmcli -m any --location-status</code> as it should contain ''assistance servers''. If not, you might experience not continuous and only infrequent GPS fixes and other problems regarding GPS.


See [https://gitlab.com/postmarketOS/pmaports/-/issues/1505#note_1161541916 this comment thread] for more details.
As discovered in [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/1505#note_1161541916 this comment thread]: if you want GPS to work, you may need to flash OxygenOS in a specific version, before flashing postmarketOS; 9.0.8 for OP6, 9.0.16 for OP6T. Its recommended to flash it to both slots (ie. use copy-partitions from LineageOS) although it is not proved that it is necessary.


== Camera ==
== 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
It is possible to make it work since libcamera has everything in place and pre-installed on the OP6 images for basic support (like on [https://gitlab.com/sdm845-mainline/linux/-/commits/joel%2Fwip-pocof1-camera-imx363 Poco f1]) once the required kernel bits for the IMX519 driver are upstreamed, see [https://lore.kernel.org/linux-media/20230908124344.171662-1-umang.jain@ideasonboard.com/ this patch] as an example and see [https://gitlab.com/sdm845-mainline/linux/-/commits/sdm845/6.9-camera-axolotl this branch] where we are stuck.
 
The driver source is available [https://github.com/raspberrypi/linux/blob/rpi-5.19.y/drivers/media/i2c/imx519.c here] see also [https://github.com/ArduCAM/IMX519_AK7375 this].
 
Help and discussion can be found in [https://gitlab.com/sdm845-mainline/linux/-/issues/21 sdm845-mainline!21] or on the matrix channel.
 
Listen [https://cast.postmarketos.org/episode/34-Events-Fairphone-5-FF-UA-SDM845-CI-Camera-MSM8953-initramfs/ pmOS podcast #34] for information (Sep 28 2023).
 
== Wifi ==
 
Wifi works out of the box, until it doesn`t anymore. The whole modem goes offline at irregular intervals (minutes to weeks after a fresh boot).<br>
One, or sometimes multiple reboots are required to get the modem working again.<br>
See: [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/3486 #3486]
 
Wifi monitor mode works, but requires reloading the driver with <code>frame_mode=0</code> and enabling raw mode in <code>firmware-5.bin</code>.
The commands to do this can be found here: [https://github.com/biemster/pmos-openbox-conky/blob/1409c16efe08e360dffc78020ac52dcc78daf0b8/phone.py#L471]. Packet injection however does not work.
 
When creating a hotspot you might encounter the [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/2620 issue] that you are not be able to connect to it. In this case, create it from command line with <code>wifi-sec.pmf</code> disabled:
<pre>
nmcli dev wifi hotspot ifname wlan0 ssid hotspotname password "password"
nmcli c modify Hotspot 802-11-wireless-security.pmf 1
nmcli connection modify Hotspot wifi-sec.pmf disable
</pre>


== Sensors ==
== Sensors ==


Initial sensor support is/will be added in {{MR|4050|pmaports}}
Initial sensor support was added in {{MR|4050|pmaports}}.
Which works nice but constantly sucks 1-2% of CPU. To fix this we need [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/2455#note_453587 your help].
 
== NFC ==
 
As written [https://gitlab.com/sdm845-mainline/linux/-/merge_requests/62#note_1807750385 here], NFC is working on OP6/OP6T devices.
 
<pre>
sudo apk add dtc
cd /boot/dtbs/qcom
sudo dtc sdm845-oneplus-enchilada.dtb -o sdm845-oneplus-enchilada.dts
patch < NFC.patch
sudo dtc sdm845-oneplus-enchilada.dts -o sdm845-oneplus-enchilada.dtb
sudo reboot
</pre>
 
get [https://raw.githubusercontent.com/biemster/pmos-openbox-conky/main/NFC.patch NFC.patch here].
 
More info by contacting [[User:Biemster]] or opening an issue in [https://github.com/biemster/pmos-openbox-conky the repo]
 
We just miss an userspace application and the [https://github.com/NXPNFCLinux/linux_libnfc-nci libnfc-nci] as Alpine package.


== TrustZone ==
== 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 <code>include/uapi/linux/tee.h</code>. You can use the OP-TEE implementation as an example. More documentation here https://www.kernel.org/doc/html/latest/staging/tee.html.
Drivers to communicate with the QSEE (Qualcomm Secure Execution Environment) are not on mainline and you can't flash [https://optee.readthedocs.io/en/latest/general/about.html 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 <code>include/uapi/linux/tee.h</code>. You can use the OP-TEE implementation as an example. More documentation here https://www.kernel.org/doc/html/latest/tee/op-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!
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!
Line 480: Line 553:
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.
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.
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.
== Battery/Power ==
While battery and charging are working, we sometimes get inaccurate power percentage values reported. In particular, if you have a replacement battery in your device, the BMS (battery management system) chip may differ from the original one, and the battery indicator may always show 100% and charging. In this case, the following might help:
You will decompile/edit/recompile your device tree blob (.dtb) file. Add the dtc package:
<pre>
sudo apk add dtc
cd /boot/dtbs/qcom
sudo dtc sdm845-oneplus-enchilada.dtb -o temp.dts
sudo sed -i 's/bq27441/bq27541/' temp.dts
sudo sed -i 's/bq27411/bq27541/' temp.dts
sudo dtc temp.dts -o sdm845-oneplus-enchilada.dtb
</pre>
Then run mkinitfs to incorporate the changes into your initramfs:
<pre>
sudo mkinitfs
</pre>
Charging on variable powersources like solarpanel/dynamo [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/3023 does not work as expected].


== Fastboot flashing issues ==
== Fastboot flashing issues ==
Line 513: Line 606:


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.
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.
=== Countries Where Device Fails To Connect To Mobile Network ===
Australia - Since 3G closure this device is rejected due to SOS calls needing 3G network. See this forum for possible workarounds depending on the model of OnePlus 6: https://forums.whirlpool.net.au/archive/9m01z7np
Also see this issue tracker for VoLTE progress: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/1878


== Renegade Project ==
== Renegade Project ==
Has support in main tree, can boot PostmarketOS.
Has support in main tree, can boot PostmarketOS.


See also [OnePlus 6 (oneplus-enchilada)/Dual Booting and Custom Partitioning#Dual booting pmos with other uefi based os (like openbsd , netbsd , freebsd,windows,etc) via Renegade Project] and [https://renegade-project.tech/en/devices/OnePlus/sdm845 Oneplus 6/6T Renegade Project Page]
See also [[OnePlus 6 (oneplus-enchilada)/Dual Booting and Custom Partitioning#Dual booting pmos with other uefi based os (like openbsd , netbsd , freebsd,windows,etc) via Renegade Project]] and [https://renegade-project.tech/en/devices/OnePlus/sdm845 Oneplus 6/6T Renegade Project Page]


== Community Info ==
== Community Info ==
Line 526: Line 625:
=== Maintainers ===
=== Maintainers ===


* [[User:Kalube|Caleb]]
* [[User:Caleb|Caleb]]


== See also ==
== See also ==
Line 535: Line 634:
{{Special:Prefixindex|prefix=OnePlus 6 (oneplus-enchilada)/|hideredirects=1|stripprefix=0}}
{{Special:Prefixindex|prefix=OnePlus 6 (oneplus-enchilada)/|hideredirects=1|stripprefix=0}}
* [[OnePlus 6T (oneplus-fajita)]]
* [[OnePlus 6T (oneplus-fajita)]]
* [[Sxmo:Oneplus6|OnePlus 6 sxmo tricks]]
* [[Android_AB_Slots|Documentation on A/B slots]]


=== External links ===
=== External links ===
Line 545: Line 647:
* {{MR|2206|pmaports}} Update to 5.12.8 and add support for the speaker / headphone jack on the OnePlus 6
* {{MR|2206|pmaports}} Update to 5.12.8 and add support for the speaker / headphone jack on the OnePlus 6
* {{MR|2215|pmaports}} Support automatic kernel updates for Android devices (including A/B!)
* {{MR|2215|pmaports}} Support automatic kernel updates for Android devices (including A/B!)
* [https://gitlab.com/postmarketOS/pmaports/-/tree/master/device/community/device-oneplus-enchilada Enchilada device package]
* [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/master/device/community/device-oneplus-enchilada Enchilada device package]
* [https://gitlab.com/postmarketOS/pmaports/-/tree/master/device/community/device-oneplus-fajita Fajita device package]
* [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/master/device/community/device-oneplus-fajita Fajita device package]
* [https://gitlab.com/postmarketOS/pmaports/-/tree/master/device/community/linux-postmarketos-qcom-sdm845 Kernel package]
* [https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/master/device/community/linux-postmarketos-qcom-sdm845 Kernel package]
* [https://cast.postmarketos.org/episode/08-Interview-Caleb-Connolly-SDM-845-Mainlining/ postmarketOS podcast interview with Caleb about mainlining the OnePlus 6]
* [https://cast.postmarketos.org/episode/08-Interview-Caleb-Connolly-SDM-845-Mainlining/ postmarketOS podcast interview with Caleb about mainlining the OnePlus 6]
* [[Android_AB_Slots|Documentation on A/B slots]]
* Recent updates concerning [https://mastodon.social/@tbernard/112679666265497509 USB C role switching on Oneplus 6]
 
=== Footnotes ===


__FORCETOC__
__FORCETOC__
[[Category:Devices with known UART pinout]]
[[Category:Devices with known UART pinout]]
[[Category:Trailblazer]]

Latest revision as of 15:29, 15 March 2025

Note This page is about the dedicated port of this device. There is also an optional generic port available for this device - see Qualcomm SDM845 (qualcomm-sdm845).
OnePlus 6
Running Phosh
Running Phosh
Manufacturer OnePlus
Name 6
Codename oneplus-enchilada
Model A6000, A6003
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 (OxygenOS/HydrogenOS)
Original version 8.0
Extended version 11 on Linux 4.9 (OxygenOS 11.1.2.2)
FOSS bootloader no
postmarketOS
Category community
Pre-built images yes
postmarketOS kernel Mainline
Unixbench Whet/Dhry score 6029.9
Optional Generic Port Qualcomm SDM845 (qualcomm-sdm845)
Features
Flashing
Works
USB Networking
Works
Internal storage
Works
Battery
Works
Screen
Works
Touchscreen
Works
Multimedia
3D Acceleration
Works
Audio
Works
Camera
Partial
Camera Flash
Works
Connectivity
WiFi
Partial
Bluetooth
Works
GPS
Partial
NFC
Partial
Modem
Calls
Partial
SMS
Partial
Mobile data
Partial
Miscellaneous
FDE
Works
USB OTG
Partial
Sensors
Accelerometer
Works
Magnetometer
Works
Ambient Light
Works
Proximity
Works
Hall Effect
Broken
Haptics
Works
Barometer
No data

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. While it is relatively unlikely that a vulnerability is discovered in this firmware, it is absolutely a possibility. Until OnePlus releases 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 Power and Volume Up until you see a screen showing the word START and information about the device.

For the OnePlus 6T, hold Power and both volume buttons.

Notice 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

Notice 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 installing 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) on both slots. This is not a requirement but is heavily recommended to get GPS working. Try this first if you encounter issues with fastboot.

Notice If you have a very old version of OxygenOS (for example after using the "MSM Download tool" for android 10), you probably need to update twice, because the device uses A/B partitioning (read this page if you're not sure what that means). First do a normal update, then find the latest version of OxygenOS OTA signed zip, upload it to the phone, go to the updater in the settings and do a local update of the latest version again (source). OnePlus' support/softwareupgrade page seems to be inaccessible at this moment, so look at this XDA thread for 6 and this one for 6T

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 Settings, 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 hidden 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 by selecting "Restart Bootloader" on the device.

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:

Notice 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.
Hint If you are using Arch Linux and getting errors like std::out_of_range. Uninstall android-tools and install android-sdk-platform-tools from the AUR[1][2] or build and flash your own build with pmbootstrap
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 run fastboot reboot after each command succeeds, to avoid above "waiting for device" connection problem.

Warning WARNING: Do not reboot via the power button on the device! This can result in not all data being properly written to storage, corrupting the rootfs and resulting strange behaviour like postmarketOS getting stuck during boot!
Note Always use fastboot reboot after flashing.


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.

With FDE (it stands for Full Disk Encryption)

pmbootstrap install --split --fde
pmbootstrap export

Without

pmbootstrap install

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)

Without FDE by default, the rootfs will be flashed to the system partition. This doesn't leave much free space for your applications / data, so if you don't mind factory resetting the device you can instead flash to the userdata partition by specifying the partition like below.

Warning WARNING: Do not reboot using the power button on the device! This can result in not all data being properly written to storage, corrupting the rootfs and resulting in strange behaviour like postmarketOS getting stuck during boot!
Note Always use fastboot reboot after flashing.

With FDE

By booting twrp from bootloader/fastboot mode you can do the partitioning.

If you install pmOS only to the slot b you can install twrp as recovery.
After partitioning you will need to format userdata in twrp.
You can install to both slots if you prefer.

In twrp (Android 11 version ie. 3.7.0) in Advanced->Terminal you can use sgdisk, it has long flags only e.g. --print and not -p.
Or you can use adb shell (when booted into twrp) to run these commands from your computer.

#Get userdata number and info on the disk
sgdisk /dev/block/sda --print

#Delete userdata partition to remake it smaller
sgdisk /dev/block/sda --delete=17

#Make userdata 2 gigabytes, minimum size unknown
sgdisk /dev/block/sda --new=0:0:+2G --change-name=0:userdata

#Make pmOS boot partition 256 megabytes (default size)
sgdisk /dev/block/sda --new=0:0:+256M --change-name=0:pmOS_boot

#Make pmOS system partition uses the rest of the disk
sgdisk /dev/block/sda --new=0:0:0 --change-name=0:pmOS_root
#Both slots
fastboot erase dtbo
fastboot flash pmOS_boot /tmp/postmarketOS-export/oneplus-enchilada-boot.img
fastboot flash pmOS_root /tmp/postmarketOS-export/oneplus-enchilada-root.img
fastboot flash boot /tmp/postmarketOS-export/boot.img
fastboot reboot

#Slot b only
fastboot erase dtbo_b
fastboot flash pmOS_boot /tmp/postmarketOS-export/oneplus-enchilada-boot.img
fastboot flash pmOS_root /tmp/postmarketOS-export/oneplus-enchilada-root.img
fastboot flash boot_b /tmp/postmarketOS-export/boot.img
fastboot set_active b
fastboot reboot

Without FDE

fastboot erase dtbo
pmbootstrap flasher flash_rootfs --partition userdata
pmbootstrap flasher flash_kernel
pmbootstrap chroot fastboot reboot

If you have flashing or booting issues, try flashing the latest version of OxygenOS to the slot you want to install postmarketOS to (i.e., flash the ROM using TWRP from your other slot). If you still have no luck, try flashing OxygenOS 9, as the bootloader can be more forgiving.

Dual booting

(See OnePlus_6_(oneplus-enchilada)/Dual_Booting_and_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, then choose the "reboot bootloader" option on the device, press the power button to select that option and plug in the device while it reboots.

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.

See this quick and dirty tutorial on how to build the kernel.

Info

Hacking

See Hacking for details.

Partition map

oneplus-enchilada:~$ ls -lah /dev/disk/by-partlabel/

total 0      
drwxr-xr-x    2 root     root        2.0K Jan  7  1970 .
drwxr-xr-x    8 root     root         160 Jan  7  1970 ..
lrwxrwxrwx    1 root     root          10 Jan  7  1970 ALIGN_TO_128K_1 -> ../../sdd1
lrwxrwxrwx    1 root     root          10 Jan  7  1970 ALIGN_TO_128K_2 -> ../../sdf1
lrwxrwxrwx    1 root     root          11 Jan  7  1970 ImageFv -> ../../sde72
lrwxrwxrwx    1 root     root          11 Jan  7  1970 LOGO_a -> ../../sde20
lrwxrwxrwx    1 root     root          11 Jan  7  1970 LOGO_b -> ../../sde48
lrwxrwxrwx    1 root     root          10 Jan  7  1970 abl_a -> ../../sde8
lrwxrwxrwx    1 root     root          11 Jan  7  1970 abl_b -> ../../sde36
lrwxrwxrwx    1 root     root          10 Jan  7  1970 aop_a -> ../../sde1
lrwxrwxrwx    1 root     root          11 Jan  7  1970 aop_b -> ../../sde29
lrwxrwxrwx    1 root     root          11 Jan  7  1970 apdp -> ../../sde63
lrwxrwxrwx    1 root     root          10 Jan  7  1970 bluetooth_a -> ../../sde5
lrwxrwxrwx    1 root     root          11 Jan  7  1970 bluetooth_b -> ../../sde33
lrwxrwxrwx    1 root     root          11 Jan  7  1970 boot_a -> ../../sde11
lrwxrwxrwx    1 root     root          11 Jan  7  1970 boot_aging -> ../../sde58
lrwxrwxrwx    1 root     root          11 Jan  7  1970 boot_b -> ../../sde39
lrwxrwxrwx    1 root     root          10 Jan  7  1970 cdt -> ../../sdd2
lrwxrwxrwx    1 root     root          11 Jan  7  1970 cmnlib64_a -> ../../sde13
lrwxrwxrwx    1 root     root          11 Jan  7  1970 cmnlib64_b -> ../../sde41
lrwxrwxrwx    1 root     root          11 Jan  7  1970 cmnlib_a -> ../../sde12
lrwxrwxrwx    1 root     root          11 Jan  7  1970 cmnlib_b -> ../../sde40
lrwxrwxrwx    1 root     root          11 Jan  7  1970 config -> ../../sda12
lrwxrwxrwx    1 root     root          10 Jan  7  1970 ddr -> ../../sdd3
lrwxrwxrwx    1 root     root          11 Jan  7  1970 devcfg_a -> ../../sde14
lrwxrwxrwx    1 root     root          11 Jan  7  1970 devcfg_b -> ../../sde42
lrwxrwxrwx    1 root     root          11 Jan  7  1970 devinfo -> ../../sde61
lrwxrwxrwx    1 root     root          11 Jan  7  1970 dip -> ../../sde62
lrwxrwxrwx    1 root     root          10 Jan  7  1970 dsp_a -> ../../sde9
lrwxrwxrwx    1 root     root          11 Jan  7  1970 dsp_b -> ../../sde37
lrwxrwxrwx    1 root     root          11 Jan  7  1970 dtbo_a -> ../../sde18
lrwxrwxrwx    1 root     root          11 Jan  7  1970 dtbo_b -> ../../sde46
lrwxrwxrwx    1 root     root          10 Jan  7  1970 frp -> ../../sda6
lrwxrwxrwx    1 root     root          10 Jan  7  1970 fsc -> ../../sdf5
lrwxrwxrwx    1 root     root          10 Jan  7  1970 fsg -> ../../sdf4
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_4j1ed_a -> ../../sde21
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_4j1ed_b -> ../../sde49
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_4u1ea_a -> ../../sde22
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_4u1ea_b -> ../../sde50
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs3_a -> ../../sde23
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs3_b -> ../../sde51
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs4_a -> ../../sde24
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs4_b -> ../../sde52
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs5_a -> ../../sde25
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs5_b -> ../../sde53
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs6_a -> ../../sde26
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs6_b -> ../../sde54
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs7_a -> ../../sde27
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs7_b -> ../../sde55
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs8_a -> ../../sde28
lrwxrwxrwx    1 root     root          11 Jan  7  1970 fw_ufs8_b -> ../../sde56
lrwxrwxrwx    1 root     root          10 Jan  7  1970 hyp_a -> ../../sde3
lrwxrwxrwx    1 root     root          11 Jan  7  1970 hyp_b -> ../../sde31
lrwxrwxrwx    1 root     root          11 Jan  7  1970 keymaster_a -> ../../sde10
lrwxrwxrwx    1 root     root          11 Jan  7  1970 keymaster_b -> ../../sde38
lrwxrwxrwx    1 root     root          10 Jan  7  1970 keystore -> ../../sda5
lrwxrwxrwx    1 root     root          11 Jan  7  1970 limits -> ../../sde67
lrwxrwxrwx    1 root     root          11 Jan  7  1970 logdump -> ../../sde71
lrwxrwxrwx    1 root     root          11 Jan  7  1970 logfs -> ../../sde69
lrwxrwxrwx    1 root     root          10 Jan  7  1970 mdtp_a -> ../../sde7
lrwxrwxrwx    1 root     root          11 Jan  7  1970 mdtp_b -> ../../sde35
lrwxrwxrwx    1 root     root          10 Jan  7  1970 mdtpsecapp_a -> ../../sde6
lrwxrwxrwx    1 root     root          11 Jan  7  1970 mdtpsecapp_b -> ../../sde34
lrwxrwxrwx    1 root     root          11 Jan  7  1970 minidump -> ../../sde57
lrwxrwxrwx    1 root     root          10 Jan  7  1970 misc -> ../../sda3
lrwxrwxrwx    1 root     root          10 Jan  7  1970 modem_a -> ../../sde4
lrwxrwxrwx    1 root     root          11 Jan  7  1970 modem_b -> ../../sde32
lrwxrwxrwx    1 root     root          10 Jan  7  1970 modemst1 -> ../../sdf2
lrwxrwxrwx    1 root     root          10 Jan  7  1970 modemst2 -> ../../sdf3
lrwxrwxrwx    1 root     root          11 Jan  7  1970 msadp -> ../../sde64
lrwxrwxrwx    1 root     root          11 Jan  7  1970 odm_a -> ../../sda15
lrwxrwxrwx    1 root     root          11 Jan  7  1970 odm_b -> ../../sda16
lrwxrwxrwx    1 root     root          10 Jan  7  1970 oem_dycnvbk -> ../../sda8
lrwxrwxrwx    1 root     root          10 Jan  7  1970 oem_stanvbk -> ../../sda9
lrwxrwxrwx    1 root     root          11 Jan  7  1970 op1 -> ../../sde59
lrwxrwxrwx    1 root     root          10 Jan  7  1970 op2 -> ../../sda7
lrwxrwxrwx    1 root     root          10 Jan  7  1970 param -> ../../sda4
lrwxrwxrwx    1 root     root          10 Jan  7  1970 persist -> ../../sda2
lrwxrwxrwx    1 root     root          11 Jan  7  1970 qupfw_a -> ../../sde15
lrwxrwxrwx    1 root     root          11 Jan  7  1970 qupfw_b -> ../../sde43
lrwxrwxrwx    1 root     root          11 Jan  7  1970 reserve1 -> ../../sda10
lrwxrwxrwx    1 root     root          11 Jan  7  1970 reserve2 -> ../../sda11
lrwxrwxrwx    1 root     root          11 Jan  7  1970 sec -> ../../sde60
lrwxrwxrwx    1 root     root          11 Jan  7  1970 splash -> ../../sde66
lrwxrwxrwx    1 root     root          11 Jan  7  1970 spunvm -> ../../sde65
lrwxrwxrwx    1 root     root          10 Jan  7  1970 ssd -> ../../sda1
lrwxrwxrwx    1 root     root          11 Jan  7  1970 sti -> ../../sde70
lrwxrwxrwx    1 root     root          11 Jan  7  1970 storsec_a -> ../../sde19
lrwxrwxrwx    1 root     root          11 Jan  7  1970 storsec_b -> ../../sde47
lrwxrwxrwx    1 root     root          11 Jan  7  1970 system_a -> ../../sda13
lrwxrwxrwx    1 root     root          11 Jan  7  1970 system_b -> ../../sda14
lrwxrwxrwx    1 root     root          11 Jan  7  1970 toolsfv -> ../../sde68
lrwxrwxrwx    1 root     root          10 Jan  7  1970 tz_a -> ../../sde2
lrwxrwxrwx    1 root     root          11 Jan  7  1970 tz_b -> ../../sde30
lrwxrwxrwx    1 root     root          11 Jan  7  1970 userdata -> ../../sda17
lrwxrwxrwx    1 root     root          11 Jan  7  1970 vbmeta_a -> ../../sde17
lrwxrwxrwx    1 root     root          11 Jan  7  1970 vbmeta_b -> ../../sde45
lrwxrwxrwx    1 root     root          11 Jan  7  1970 vendor_a -> ../../sde16
lrwxrwxrwx    1 root     root          11 Jan  7  1970 vendor_b -> ../../sde44
lrwxrwxrwx    1 root     root          10 Jan  7  1970 xbl_a -> ../../sdb1
lrwxrwxrwx    1 root     root          10 Jan  7  1970 xbl_b -> ../../sdc1
lrwxrwxrwx    1 root     root          10 Jan  7  1970 xbl_config_a -> ../../sdb2
lrwxrwxrwx    1 root     root          10 Jan  7  1970 xbl_config_b -> ../../sdc2

Camera Flash

Two leds (yellow and white), both functionnal, at the back of the phone.

Their max brightness value is 255.

A simple extension for Gnome mobile adds a button to the activities overview : https://gitlab.com/NekoCWD/nekotorch

See LEDs for more details.

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
  • If you are not able to write via fastboot, even after
    unlock_critical
    use edl mode instead (turn off phone, push volume +/- and plugin the usb cable):
 edl w abl_a abl.img 

and so on with all the mentioned files.

The big list of issues

In no particular order...

Audio in calls

There are issues with audio disappearing in calls.

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.

If you use Phosh with systemd, the tri-state button should work out-of-the-box (if pmaports!5969 is merged).

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.

See this matrix post by User:Caleb:

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

Note 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.

Host mode can be enabled by Dts method and Sysfs method.

Dts method

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.

Sysfs method

Change "device" to "host" in "/sys/kernel/debug/usb/a600000.usb/mode" :

# echo host | sudo tee /sys/kernel/debug/usb/a600000.usb/mode

To revert the changes just do the same thing again but change host to device or reboot the device.

Verify

Run the command as below to verify:

# sudo cat /sys/kernel/debug/usb/a600000.usb/mode

If the command return host then congratulation you have enabled the host mode successfully.

GPS

Warning WARNING: To use and test GPS functions, make sure a SIM card is inserted (mmcli v1.22.x), GPS is enabled in mmcli, geoclue is executed. Then disable suspend, go outside for 15min. until you get a fix

Carefully read Troubleshooting:GPS for more details on how to activate the GPS using ModemManager's CLI and enabeling Geoclue.


As discovered in this comment thread: if you want GPS to work, you may need to flash OxygenOS in a specific version, before flashing postmarketOS; 9.0.8 for OP6, 9.0.16 for OP6T. Its recommended to flash it to both slots (ie. use copy-partitions from LineageOS) although it is not proved that it is necessary.

Camera

It is possible to make it work since libcamera has everything in place and pre-installed on the OP6 images for basic support (like on Poco f1) once the required kernel bits for the IMX519 driver are upstreamed, see this patch as an example and see this branch where we are stuck.

The driver source is available here see also this.

Help and discussion can be found in sdm845-mainline!21 or on the matrix channel.

Listen pmOS podcast #34 for information (Sep 28 2023).

Wifi

Wifi works out of the box, until it doesn`t anymore. The whole modem goes offline at irregular intervals (minutes to weeks after a fresh boot).
One, or sometimes multiple reboots are required to get the modem working again.
See: #3486

Wifi monitor mode works, but requires reloading the driver with frame_mode=0 and enabling raw mode in firmware-5.bin. The commands to do this can be found here: [1]. Packet injection however does not work.

When creating a hotspot you might encounter the issue that you are not be able to connect to it. In this case, create it from command line with wifi-sec.pmf disabled:

nmcli dev wifi hotspot ifname wlan0 ssid hotspotname password "password"
nmcli c modify Hotspot 802-11-wireless-security.pmf 1
nmcli connection modify Hotspot wifi-sec.pmf disable

Sensors

Initial sensor support was added in pmaports!4050. Which works nice but constantly sucks 1-2% of CPU. To fix this we need your help.

NFC

As written here, NFC is working on OP6/OP6T devices.

sudo apk add dtc
cd /boot/dtbs/qcom
sudo dtc sdm845-oneplus-enchilada.dtb -o sdm845-oneplus-enchilada.dts
patch < NFC.patch
sudo dtc sdm845-oneplus-enchilada.dts -o sdm845-oneplus-enchilada.dtb
sudo reboot

get NFC.patch here.

More info by contacting User:Biemster or opening an issue in the repo

We just miss an userspace application and the libnfc-nci as Alpine package.

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/tee/op-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.

Battery/Power

While battery and charging are working, we sometimes get inaccurate power percentage values reported. In particular, if you have a replacement battery in your device, the BMS (battery management system) chip may differ from the original one, and the battery indicator may always show 100% and charging. In this case, the following might help:

You will decompile/edit/recompile your device tree blob (.dtb) file. Add the dtc package:

sudo apk add dtc
cd /boot/dtbs/qcom
sudo dtc sdm845-oneplus-enchilada.dtb -o temp.dts
sudo sed -i 's/bq27441/bq27541/' temp.dts
sudo sed -i 's/bq27411/bq27541/' temp.dts
sudo dtc temp.dts -o sdm845-oneplus-enchilada.dtb

Then run mkinitfs to incorporate the changes into your initramfs:

sudo mkinitfs

Charging on variable powersources like solarpanel/dynamo does not work as expected.

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.

Countries Where Device Fails To Connect To Mobile Network

Australia - Since 3G closure this device is rejected due to SOS calls needing 3G network. See this forum for possible workarounds depending on the model of OnePlus 6: https://forums.whirlpool.net.au/archive/9m01z7np

Also see this issue tracker for VoLTE progress: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/1878

Renegade Project

Has support in main tree, can boot PostmarketOS.

See also OnePlus 6 (oneplus-enchilada)/Dual Booting and Custom Partitioning#Dual booting pmos with other uefi based os (like openbsd , netbsd , freebsd,windows,etc) via Renegade Project and Oneplus 6/6T Renegade Project Page

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

External links

Footnotes