yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Heads up, got a few fixes in the pipeline for the following bugs:

Ambient Display (Always-on Display) may not work properly if panel can't freely switch between 60Hz and 90Hz

thank you @javelinanddart for helping to identify the part of the LP1 command that blanked the screen

While WiFi calling is enabled, VoIP calls (Google Voice, TextNow, etc.) starts stuttering frequently on WiFi

thank you Andrea for helping with creating a simpler patchset than the one I initially wrote

CPU scheduler becomes reluctant to schedule tasks on the Gold and Prime CPU clusters 15-30 minutes after boot

thank you @V3NK4135H for pointing me toward the kernel commit that fixes this

Hopefully the last two bugs will make it in time for next week's build. Not sure when I can get the first one merged.

EDIT: all of them are merged. Expect to see them in next Saturday's build on 2023-01-21.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
Merge them all.

Spoiler content hidden.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] wawanRedblack:
besttt
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
Managed to flash LineageOS using EDL Mode after I somehow converted my IN2017 to an IN2019 and couldn't boot anymore 😀

MSMed once, then the BOOTLOADER thought it could lock on me 🥱 I followed the steps to unlock an IN2019 because https://oneplus.com/us/unlock_token seems to be down. Somehow, it worked, but I ended up bricking my IN2017 and ended up converting it to an IN2019.

I attempted to use the MSM Tool for the IN2017 and it failed because the DEVICE TARGET (not sure where this changed) was Verzion, therefore I was unable to flash T-Mobile Software. In the end, through a ton of steps, I somehow just got LineageOS working after going through Crash Dumps, "This device is corrupt and can't boot," and many more errors that have been forgotten.

The confusing thing is, I wasn't even able to use the Verizon MSM Tool, as I kept getting an error stating something relating to image mismatches.

EDIT: Suddenly the website is now working...

EDIT: Failed miserably, FINGERPRINT SENSOR no longer works 😀
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] vuittion:
Can anyone tell me why this rom does not support aptX Adaptive sound codec.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I don't have a BT audio device that supports aptX Adaptive, so I can't check to see if it's actually broken. Thus, I can't answer this question, sorry.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] vuittion:
If you look at the bluetooth codec support in the developer options your see it's missing.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] 7ORO:
Thank you for the rom.

I have some questions regarding the install instructions

- If I flash the provided vbmeta partition will I lose the vb-verified status?

- Will vbmeta be upgraded using OTA updates or do I need to manually upgrade the partition?

- Is it the same for the dbto partition?

- If I just boot the recovery image using adb, can I backup these partitions before flashing the new ones? Or do I need to boot an old TWRP image?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Q: If I flash the provided vbmeta partition will I lose the vb-verified status?

A: You already lose verified status by unlocking the bootloader (orange state). In addition, the vbmeta partition provided is more or less an empty one, and so it would not provide any sort of hashes or anything like that to do verified boot against.

Q: Will vbmeta be upgraded using OTA updates or do I need to manually upgrade the partition?

A: Yes.

Q: Is it the same for the dbto partition?

A: Yes.

Q: If I just boot the recovery image using adb, can I backup these partitions before flashing the new ones? Or do I need to boot an old TWRP image?

A: You technically can with `dd` while in adb shell, since LineageOS recovery provides root adb access.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] 7ORO:
Thanks.

Was able to create a backup of the original partitions using "adb pull" after booting the LinageOS recovery and enabling adb shell.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] MarkiMarko2221:
Okay so got the code.

I got the Qualcomm crash error when I boot in, so I need to unbrick it.

I CAN boot into Fastboot, and flashing TWRP seems to work too.

Any solutions I should try? Should I flash Stock and go with that? Try my luck with Lineage? What should I do? (Using Linux with a Windows VM via QEMU and MSM's giving me errors when I try that

EDIT: Flashing using the flash-all.bat, for Android 11 let me boot back into stock, but now I don't have any wifi or mobile data, so not sure what else I need to fix for that. Sometimes it stays stuck on the T-Mobile boot logo too

EDIT 2: Well now it won't even let me boot into fastboot anymore, MSM gives me Sahara errors and I don't have any hardware I can run MSM reliably on, if that requires a USB 2 port (everything I have uses 3.0)
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
When you first saw Qualcomm Crash Dump mode show up, what had you done prior to that? Also, if you can find a USB 2.0 hub to plug into one of your USB 3.0 ports, that may help a lot with your issues with MsmDownloadTool.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] MarkiMarko2221:
If I recall right, I used the flasher tool from Step 3, which seemed to go well but after that, I ended up with a Qualcomm crash, I updated to OTA 11 but ended up inadvertantly using the A10 flashrom so that might have bit me.. For awhile it booted in to the firmware but had no internet or data, but now I can't get it to boot period.

I can get it into Fastboot, TWRY works if I flash that, same with the stock recovery if I flash it. But that's the best I'd gotten for a good few hours.

Don't have any usb 2.0 hubs, I do have an old laptop but that doesn't have a hard drive so that complicates matters.

EDIT: I went back to the flashable file (10.5.9-EUROPE-OnePlus8Oxygen_15.E.18_OTA_018_all_2007160043_913306-FASTBOOT) and manually ran all the commands by hand using ADB tools, and it actually *worked*, so now it boots back into stock. (Model still says IN2017 when I check settings).

EDIT: Updated by one of the zips in the Step 3 thread (specifically Global 11) and now it shows up as IN2015, so good sign.

Updated to 12 via OTA, am I good to try and flash Lineage? Or should I update to A13 first? It does show up when I check system update.

Also if I want MicroG, what's the best way to approach that?

EDIT: NEvermind, stuck in a fastboot loop now, says the image is destroyed.

EDIT 2: Okay booted back to stock again, had to flash all the way to A10 using the previous fastboot files but I got in, wifi works but it doesn't see my SIM anymore.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] MarkiMarko2221:
So I literally can't update anymore, neither locally or via OTA, both fail. IMEI is totally gone too and SIM no longer works, even after reflashing again. I don't have a spare drive to use MSM (virtual machines didn't work at all when I tried that) so at this point I think my phone is just completely busted (it at least boots and connects to wifi now, so it's not a *complete* brick), I'll just have to send it in and failing that, just make due without a phone a good while.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
I restored my IMEI using some QCOM Tool, but unfortunately, it's now applied to SIM 2, even though it doesn't exist.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] MarkiMarko2221:
It's still under a plan with TMO so I'm gonna cut my losses and take it in, if I'm lucky it might be fixable, worst case scenario they can't, then at best I can get it traded in, at worst I'll have to get a new device entirely, which would suck though I'm looking at pixels for Graphene, so there's that at least.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
The second SIM IMEI is annoying me because I can't figure out how to get rid of it.

EDIT: If your lease is over with T-Mobile (after the device replacement), I'd switch to Google Fi (assuming you have no other ongoing leases). I just made the switch, and it was relatively easy, it's also cheaper. You're still getting T-Mobile coverage, without the pricing! You'd have to switch before the end of your current billing cycle, if you don't want to pay for the next month. Also, if you choose to port all or one number, make sure you do the account holder number last. Not sure how Sprint/T-Mobile handle account closures when that number is transferred while other lines are active.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] MarkiMarko2221:
I'm not the only one on the plan so I'd have to see how that goes. But I go on monday so I'll see.

I also drudged up an old laptop with a kind of busted hard drive, I can try running MSM on that, but I don't know if I should do that first or if I should wait and check with TMO first.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
You should try to MSM first, it'll be faster than visiting a T-Mobile Store!

EDIT: They might also make you pay for a replacement, in full because, as OnePlus mentions, your warranty could not be voided.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
Does LineageOS support Google Fi? I can't activate my SIM with Pixel Experience.

EDIT: LineageOS does because it doesn't spoof whatever Pixel Experience does.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] wawanRedblack:
light sensor is sucked on latest version sir
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I don't know what you're talking about... light sensor has always sucked on this device ever since LineageOS 18.1; it's even mentioned in the bug list at the start of this thread.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] wawanRedblack:
high brightness mode sir

suddenly turn on and blow my face

not on previous version
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] AnierinB:
Disable automatic brightness.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] wawanRedblack:
still happening sir
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Go to the Settings app, then navigate to Display -> LiveDisplay -> Display mode and select "Off" to disable automatic high brightness mode.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] wawanRedblack:
ah thanks sir

my savior

bess 😘
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] MarkiMarko2221:
So I used MSM and so far it seemed to work, had to use my old junk laptop but everything seems to be in working order for now, SIM included.

Should I try my luck installing Lineage on it again? Or should I just cut my losses on that and save up for a GrapheneOS phone when my finances are alright? I'm super cautious on this rn

EDIT: Got into a long loop at the logo, but after clearing cache in recovery, it boots in, flashed and updating to A11, my current plan is to upgrade to A12 and await further steps from there to make sure I do everything right (fatal mistake last time was "fastboot flash boot twrp" instead of "fastboot boot twrp"), I know the step for LineageOS recovery but I don't know if there's a way to flash it without flashing recovery, in case something goes wrong again.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
Use the same thing you'd do for TWRP, fastboot boot recovery.img and it will boot instantly or within two minutes. Should it not, just reboot by holding a combination of hardware keys and your device will reboot normally.

Theoretically, I think this should let you adb sideload while not using LineageOS Recovery as a permanent recovery.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] MarkiMarko2221:
Just tried it a bit ago, the Lineage19/20 recovery didn't load (I did *update* to A12 but trying to flash recovery from there reverted me back to A11), so a thread suggested flashing a Lineage 18 recovery, which worked (flashed instantnoodle*p* by mistake but it was an easy fix at least after finding the right file), sideloaded a the relevant zip file and it worked (I'm on Lineage 19 and I'm not really in the mood to do more flashing anytime soon)

So now I'm on lineageOS (I used a MicroG build specifically) so that's good now. Not sure if I should go further and try to root it (not really confident in doing that but being able to better backup stuff wouldn't hurt), but for now it's fairly alright.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
There are two ways you can root, by adb sideload (easier, safer in my opinion) or patched boot.img.

Using the adb sideload method, will install Magisk (the application) alongside the patch. You'll have to download and install the full application after #7 by tapping on the base APK from the launcher.

BY ADB SIDELOAD​

Connect your device via USB.

Download the latest Magisk release on your computer (preferably GitHub).

Rename it from magisk.apk to magisk.zip.

Run adb reboot recovery.

Select Apply update, then Apply from ADB.

Using adb sideload <file>, sideload the file from #3.

Reboot.

BY BOOT.IMG​

On your device, download the required boot.img.

Open Magisk, then tap Install at the top right corner.

Choose Select and Patch a File, then LET'S GO.

Transfer the patched boot.img to your computer.

Run adb reboot fastboot, then fastboot flash boot patched_magisk_boot.img.

Reboot.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] vip77:
There is a safer way.

- Install Magisk.

- Patch boot.img

- Save it to PC

- adb reboot bootloader

- fastboot boot patchet_magisk_boot.img

- if loaded fine you are on root. Just patch system boot.img with Magisk.

Thats all.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
Those are nearly the same exact steps I had in my post...
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] vip77:
If this step failed, you will get bootloop or stuck in fastboot mode . After that solution is either a clean reinstall or flash backup boot if you have it. Otherwise have to do dump img to extract correct boot.img.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] sanderrvb:
I've just done a fresh install + MindTheGapps after a factory reset on OxygenOS 13. I noticed that the Gallery app doesn't seem to be affected by the Media volume (or any volume for that matter). When I use it to play a video, it plays sound at a constant volume, even if all volumes in the settings are set to 0. Does anyone else observe this?

Other apps (e.g. VLC) do seem to respect the media volume. In practice I probably won't use the gallery app much, but I thought I'd report it so that if it does turn out to be a wider issue, it can be included in the known issues overview.

I'm not entirely sure if this is an issue with this ROM, with GAPPS, or something else still.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
Can someone help me out and backup their QCN, then upload it? I'm using an IN2017, but I'm willing to try any model as long as it's IN2013, IN2015, or IN2017.

[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.

Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...

xdaforums.com
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I just tried with the default gallery's video player, and I don't seem to have an issue with volume control at all.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] sanderrvb:
Interesting. I just did another factory reset to no avail. I installed the Google Photos app because that's the one I tried for my battery health measurement on this same device before I flashed Lineage, and it suffered from this same problem. I might try a clean flash one of these days. Should it be safe to just wipe all partitions through recovery and then flash using the official install documentation?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Pask95:
I have installed the lineage recovery but when I go into recovery/Apply update/Apply from ADB the computer don't find my adb device. What's wrong?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] samhhmobil:
You need to install the correct windows-device-driver for the OP8.

Or -- better -- don't use a windows desktop. IMHO one should use a Linux desktop instead, to avoid such trouble.

samhhmobil
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Pask95:
Solved using Ubuntu terminal. I can't belive I went crazy for a while day. thanks a lot!
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] foldren:
Just installed last version (18.03)

And gpay is not working, any methods how to fix it?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] sanderrvb:
I encountered similar issues (not with gpay but another mobile pay app). I don't think it has anything to do with this ROM specifically. That said, I solved it by rooting with Magisk and installing the universal safetynet fix. I didn't want to root the device initially, but it was the only solution I could find to pass safety net, which is, I believe, what's going wrong in your case.

I did come across a post with an alternatuve approach earlier today. I might have preferred this over rooting myself but it was already done at that point. So I haven't tried it, and it's not verified to work on this device but the author of the post expects it should, so it may be of interest to you: https://xdaforums.com/t/rom-official-hotdogb-12-lineageos-19.4509251/post-87666693

If you want to go the rooting approach, here are the steps I wrote down for myself in case I need to do this again. Please bear in mind that my experience here is very limited, so I can't guarantee this is the best approach.

- install Magisk according to its docs

- pass safetynet through Magisk app

- settings -> hide the Magisk app -> give it another name

- settings -> enable systemless hosts

- settings -> Zygisk -> reboot

- double check status says yes next to Zygisk

- settings -> enforce denylist

- settings -> configure denylist -> show system apps

- Google Play Store

- Google Play Services

- any apps you want to hide root and custom rom status from

- download Universal SafetynetFix module from GitHub. Install via Magisk's modules page -> reboot

- clear these apps' data, but exclude Play Services, it messes up back up
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] foldren:
neither way helped me, so i assume it's because of Orange state when booting, any ideas how to fix it without unlocktools? cuz it's not free lol
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] sanderrvb:
Mine is in still in orange state as well, so I'm not sure that's it. Perhaps if you clear cache for Play Services after all? But like I said before, for me it was a different app so it might just be that Google Pay has more strict checks.

I'm not familiar with unlocktools so I can't comment on that.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Xiaomimitt:
[MODULE] [MOD] Universal SafetyNet Fix

Universal SafetyNet Fix [MOD] Magisk module Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n. Created for the (temporary?) restoration of working capacity in the conditions of constant change...

xdaforums.com
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] The0919:
After freshly installing the lastest build I seem to have an issue with video playback. Video in all apps (gallery, Google photos, YouTube, etc) takes ~10 seconds before it starts playing any video. Glancing at the log file, it seems to be related to initializing the vp9 codec. Is this a known issue? I haven't found anything Googling around, I've attached the log file, I'm wondering if there's anything I can do about it.

Log file: https://paste.c-net.org/TabithaExpress
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] osetiopica:
Hi, I want to know the location of the battery charge control file for battery charge limiting. Thanks for your development.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Hi all, the chain of AoD related fixes has now been merged: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8250/+/348992

Expect the next upcoming build on 2023-03-11 to have them.

According to https://review.lineageos.org/c/LineageOS/android_hardware_oplus/+/350382, it's under `/sys/class/oplus_chg/battery/mmi_charging_enable`. Other LineageOS devs are working on implementing charging control into LineageOS.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] osetiopica:
The screen rotation direction of the gesture navigation bar does not switch when switching between landscape and portrait apps in the gesture navigation bar.

-

This is the default behavior of Android. I just found out. sorry.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] sanderrvb:
I updated this morning to the latest nightly and now one of my banking apps no longer accepts my fingerprint. I had skipped the past two or three upgrades. Did something change that may have caused this? There is of course also the possibility that the cause has nothing to do with this ROM, this specific banking app isn't known for its stability.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] sanderrvb:
Nevermind, this turned out to be a classic instance of PEBKAC: the update process unrooted my device, disabling the universal safetynet fix. Reinstalling Magisk resolved my issue. Sorry for the noise.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] CurlyTemple:
How do I enable OTG storage so my USB-C headphones work. They worked with LOS 18.1 on my OP8. I have tried disablingUSB debugging and USB audio routing I've downloaded a few OTG checker programs and the OTG capability seems to be working on the phone, but I don't have a device to test it with. My main problem that I'm trying to fix is the headphones not working.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] CurlyTemple:
FYI, on researching how to do it with ADB commands, I found out that

adb shell settings get global oneplus_otg_auto_disable

already returns 0, meaning that the auto timeout is already disabled.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] samhhmobil:
Really?? I don't know what's wrong with your device.

For me it's working without anything to do.

USB-Connection to wired Headphones, external Speakers or Car-Infotainment via AUX on that side works without any trouble. I didn't configure anything for that.

samhhmobil
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] CurlyTemple:
Many OP8 users have had the problem of USB-C headphones not working after update to Android 12 and 13, as the OnePlus Community forum and reddit shows. I'm the same.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] baha900913:
What is "super_empty.img" for?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] CurlyTemple:
Anyone have any ideas on this? I lost a boatload of data updating to LOS20.0 and now I don't want to go back to LOS18.1 just because I can't get my headphones to work. A lot of OP8 users have had the same problem after updating to A12 or A13, so an answer would help a lot of people.

After using ADB commands, I find my OTG storage is already enabled...
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] osetiopica:
I'm having the same problem with usb-c earphones.

phone - usb-c to aux adapter - aux earphones < is working good.

but

phone - usb-c earphones < is not working.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Ygrek178:
I have a problem connecting a bluetooth keyboard via otg. everything worked well on the A11
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] clearview58:
New to all this.

Does this mean Lineage 20 model IN2015 has a background connection to Google?

This was not on Lineage 18.1 & 19.1.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] samhhmobil:
obsolete