yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Yeah, lineageosroms.com is not an official website at all. I don't know who maintains that, but they sure like to pretend that they're somehow officially related to LineageOS, with deceptive statements like this:

Anyway, I'm gonna update my 1st post to make it clearer to not trust instructions from any site that is not wiki.lineageos.org.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] DavidWolfen:
Hi! I've been running LOS 19 with MindTheGapps too for a couple weeks and I must say I faced the same issue every OTA update I installed ever since. As soon as I reboot, touchscreen doesn't work.

It happened when I updated to Aug 28th nightly, which was fixed by sideloading full update and then sideloading Gapps, and then again today with Sep 10th nightly, which is stuck in a bootloop I can't seem to get out of with or without gapps, or even flashing the previous version again.

Edit: BTW, I'm not even rooted. I only flashed Lineage Recovery, LOS and MindTheGapps.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Did you flash the latest OOS 12 fw on both slots? If you installed OTA updates on OOS to get to the latest OOS 12 firmware, then did you sideload the copy-partitions zip to copy your fw to the other slot? If you have C.16 or earlier firmware on your other slot, then the kernel will not be able to properly parse the information that the C.16 or earlier bootloader passed to the kernel via QCOM SMEM, including the project number. Without the project number, the kernel doesn't know which touchscreen driver to load.

As for the bootloop, I'm not sure what's happening there.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] DavidWolfen:
Thanks for your answer, jabashque! I went back to OOS with MSM since I needed the device for work, but I flashed IN2013_11.C.33 on my global device. I probably did something wrong along the way while updating which caused the bootloop.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Neoxal:
Looking forward to the next build, looks like there are lots of updates and fixes. Thanks for all your hard work!

Is anyone else having issues opening PayPal? It seems to force close immediately when I open it on the 20220910 build + MindTheGapps. Otherwise everything is working great and super smooth.

EDIT: Got it working. Needed to pass SafetyNet. I did it with the instructions here.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Jô$èph D:
Just tried to upgrade from 18 to 19, im using the T-mobile model and was using 18 fine. when i flashed the new software and tried to reboot into recovery to install gapps the phone is stuck on this screen, i tried to force reboot again but am still stuck on this screen, any help would be appreciated.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Neoxal:
You'll need the latest firmware from OOS C.33 build to run LOS 19. See more information here. I'm not sure exactly if you can directly flash IN2013 (EU model) firmware onto IN2017 (T-Mobile model), but that's what I needed to do for my IN2015 (global/NA model).
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Jô$èph D:
I cant seem to find the C.33 file closest i found was C.17.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Sithex:
Hello! I'm having a problem with audio and microphone levels. My speaker volume and microphone are very low in comparison to when I was on OxygenOS. I used MSM download tool to set my phone back to OEM, updated to latest OxygenOS, then flashed this ROM. Not sure what I should do to increase my audio and mic db. I've seen a couple people post about microphone levels on the reddit too about other oneplus devices

OnePlus 8 in2015

Clean install with latest oxygenos

No titanium backup

Yes rooted magisk (problem existed before root)

lineageos version: 19-20220917-NIGHTLY-instantnoodle

build number: lineage_instantnoodle-userdebug 12 SQ3A.220705.004 80760bac94
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Neoxal:
See information in the second post about IN2017. Apparently the latest OTA is C.41 from Aug 28. I'm not sure where to find it though.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] drspinderwalf:
Where are we supposed to be finding these downloads? I've been scouring the web trying to find *any* version that will work and can't find it anywhere.

I love and appreciate all the work put into this phone but it's a little disheartening to have accidentally flashed the old version served by oneplus and sitting without a functional phone because I can't find the right download link. The upgrade instructions make it seem like the oneplus package is the correct one. :(
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] drspinderwalf:
Not having a great time today, apparently. I downloaded the North America (IN2015_11.C.11) version and flashed all the firmware..... but forgot to run step 8 and flash xbl_config. Now the phone rapidly boots a logo with a small vibrate and instantly reboots.

I fear I may have hard bricked the device. Is that so?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Sithex:
You may want to wait for another answer as there might be a simpler way to fix your problem, but you can always reset your phone to stock with MSM Download tool.

link for op8
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] itchydroid:
Very happy with these builds since its first week of release but with app permissions seem to reset after every OTA.

So Im on OP8 Global (2015) with a fresh install since this rom was released last month using the following:

Revert to stock Android 11 from MSM Download tool

Perform all OTAs until fully updated to latest Android 12 stock as of 8/30/2022 (OOS C.33)

Followed instructions on wiki.lineageos.org to the T (including updating to the custom dtbo and vbmeta images listed on the page)

Sideloaded LineageOS 19.1

Sideloaded NikGapps SL

Rebooted and setup phone

Rebooted and sideloaded Magisk

Everything has been performing rock solid however, with every OTA, all custom app permissions seem to reset. I have to allow or block permissions and apply battery restrictions. I have noticed this for the past 2 weekly OTAs. Not sure if anyone else is facing this issue.

Thank you for your efforts. Much appreciated.

Edit: Clarified installation. Also, I'm using LOS recovery and not custom recovery like TWRP.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Neoxal:
If you're able to boot up the phone in fastboot mode by pressing all the buttons, you may be able to flash the firmware again. Btw, you'll need the IN2013 C.33 firmware as the IN2015 C.11 firmware is too outdated to run LOS 19. See more details in the second post in this thread.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] drspinderwalf:
Sadly, it won't boot into fastboot or any other mode. It can't make it past the first 0.5 seconds of boot.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] captain_nemodroid:
Is anybody else having issues with the fingerprint sensor not working very well? It wasn't ever very great, but it seemed like it was worse after I upgraded from los 18 to 19.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Sithex:
yes, my fingerprint scanner is only working after a restart, and it only works for a little bit
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] graycorgi:
Read the 3rd post in this thread (the 'known issues' post) for a solution. The brightness issue impacts the under display fingerprint scanner as well. As a result, when the bug happens it will not be able to read your fingerprint anymore. You need to flash the patched boot.img that disables softiris until this bug is resolved.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Nova_Mast:
I was also having issues with the audio while I was on los 18, but then I finally figured out the reason why my sound was so quiet.

It turned out that while playing around in Dolby Atmos, I accidentally set the profile to custom and somehow turned my audio levels all the way down so I couldn't hear anything.

Once I restored the profile back to the default setting, my audio started working again!

Does this help at all?

If your settings are normal, then does increasing the dB on the audio levels improve the audio?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Sithex:
how would I change Dolby Atmos? Is this an app from the play store or a setting. I turned off my audio fx as I thought I had a different profile. Right now I'm using an app called "Volume Booster GOODEV", which fixes my problem for now
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Nova_Mast:
Oops, I forgot the app was called Audio FX not Dolby Atmos. (I'm currently using a different rom that uses Dolby Atmos as an equalizer instead of Audio FX)

If you found a workaround with a third party app, then you should be good.

If you have any more issues, try checking Audio FX to see if there's something you might have accidentally messed up.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Hi everyone. I would just like to reiterate that my 2nd post has instructions on what minimum firmware version is needed, along with where to download said firmware for most of the OnePlus 8 models.

I'm currently running OOS 12 on my OnePlus 8 at the moment, since I'm trying to figure out what OOS does different in regards to display modes. Hoping I can figure out how to deal with that brightness bug.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] captain_nemodroid:
Can anyone explain to me how I flash this properly? I soft bricked the one partition when I tried.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Eelviny:
Hey there, got a bug to report. It might be a combo of this and Mindthegapps; happy to give debug info, but not sure how.

I use Android work profiles, but I can't get it set up. Steps to reproduce:

Go to settings > accounts, and add a new Google account

Put in details of a work Google account that has Work Profile enabled

The actual profile setup seems to work, but then as it gets to the end...

Error stating that there is no internet connectivity, and gives me a button to go to the Internet settings panel.

Enabling/disabling WiFi and 5G does nothing. Rebooting and going again has the same issue.

Would love to get work profile working so I can have my work stuff in its own separate area :)

Edit: yeah... I should actually just Google stuff. https://gitlab.com/LineageOS/issues/android/-/issues/5019 it's being worked on, I hope.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Yeah, this is a weird issue that I ran into on both my OnePlus 6T and OnePlus 8 on LineageOS 19.1. It creates the work profile and installs the Device Policy app into the work profile, but for some reason, it doesn't actually grant network access to the work profile's Device Policy app by default. You have to manually enable that, and then reattempt provisioning your work profile. If you want more detailed instructions, I could walk you through that on the Telegram group chat.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Eelviny:
Ah yeah, I'll remember that for next time! Makes sense. In the end, I went a different route - I got my company to disable work profiles for me, then used the app Shelter to make a work profile that I manage, and put my work apps in there. That worked around the issue for me, plus I have a little more control. Thanks for the offer though :)
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
It took a while to figure out, but I finally have a fix for that bug where the perceived brightness would lower if you change color modes.

It's currently up at https://review.lineageos.org/c/LineageOS/android_device_oneplus_sm8250-common/+/341740 and I'm hoping I can get it merged soon.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cjvzla:
Hello,

I'm on Zephyrus 12.1 ( https://xdaforums.com/t/rom-12-1-oos-cam-oneplus-8-project-zephyrus-12-1_r8.4458891/ ) which has dropped support for OP8 and want to switch to lineage, can I just follow the instructions for clean install? I tried to check if I'm on C33 with fastboot getvar all command, but didn't find any C33 anywhere, how do I check? I succesfully installed zephyrus when coming from stock OOS11 so I correctly flashed OOS11 to both slots. am I clear to clean flash this or should I msm to OOS11, then official OTA to OOS12, then flash lineage? ( I have a global IN2015 OP8)
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Fix is merged, and now the "Lowered brightness when switching between SDR color profiles" bug can finally be put to rest. It should be there starting with the 2022-10-22 build.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jasonv23:
Let me ge this straight, in order to flash Lineage OS 19.1 to my Oneplus8(IN2017), I have to flash the IN2015 image but the cellular data won't work unless I flash the stock IN2017 modem image?

How do I do all this, I dont know how to compile and don't have Linux. I only have Windows 10 with adb, and a OnePlus 8(IN2017) updated to Android Oxygen OS 12.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
For the question:

"Did you migrate to IN2011/IN2013/IN2015 OOS back when you were on OOS 10? And if you did, did you flash the IN2011/IN2013/IN2015 modem too before OTA updating to OOS 11 or later?"

Is your answer "no" to at least one of the questions? If so then yes, you need the IN2017 modem. If you answered "yes" to both, then no, you do not need IN2017 modem.

If you want an easier time, then use the MsmDownloadTool packages for IN2017 to rollback to OOS 10, then just follow this guide to convert to global: https://xdaforums.com/t/step-by-ste...nternational-with-bootloader-re-lock.4345305/

And once you get OOS 10 running, OTA update all the way to OOS 12 11.C.33 or 11.C.35. Your modem may not be working properly on OOS 10, but after you OTA update to at least OOS 11, it will start working correctly. Then, you don't have to care about the modem situation.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jasonv23:
Thank you!
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Important Notice​

Starting with the 2022-10-29 build, we will be including the required firmware as part of the OTA zips. What does this mean?

If you have a IN2010, IN2011, IN2013, or IN2015:​

You will no longer have to worry about ensuring that you have the required firmware version for LineageOS. For example, if you are coming from OOS 11, you can just flash LineageOS and the required OOS 12 firmware partitions will be installed as part of LineageOS.

If you have an IN2017:​

Regardless whether you have converted fully to Global / EU OOS 10 previously, this change will actually not cause any negative effects. In the telegram chat, b`owow tested the following two migration paths:

upgrade from T-Mobile OOS 10 to T-Mobile OOS 12 11.C.42, installed LineageOS, then migrated to EU OOS 12 11.C.33 fw, modem included

upgrade from T-Mobile OOS 10 to T-Mobile OOS 11 11.0.0.9, then flash EU OOS 12 11.C.33 fw in fastbootd (modem included), and then install LineageOS

Both paths not only resulted in modem still working, but also 5G SA for T-Mobile still working. Both b`owow and I found this weird, since the 2nd migration path used to result in broken modem, but we aren't going to try and investigate this further. You should be fine once we start including firmware in our OTA zips.

Spoiler content hidden.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] nastaliq:
On my OP8 (IN2013) running LineageOS 18.1, I had flashed IN2013_11_C.33 firmware, and then upgraded to LineageOS 19.1.

Does this mean that with the 2022-10-29 build, my OP8's firmware will be updated to IN2013_11_C.35?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
It will be updated to whatever firmware we end up deciding you should be on. In this case, the upcoming build will ship with 11_C.33, so you'll just have that same firmware flashed again during the update.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] vip77:
Should i sideload installed gapps after every OTA update? Or only after dirty update?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
For future updates, you sideload gapps in recovery after rebooting only if you installed the update in recovery instead of the OTA updater. If you installed in the OTA updater, then backuptool will run to copy over your gapps from your current slot to the new slot. In recovery, backuptool will NOT run, hence the need to reflash gapps there after rebooting into recovery a second time.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] vip77:
This is weird because gapps broke after every update. I had to make clean reflash after that. Maybe it's because i was on NikKGapps. Now I'm on MindTheGapps, like recommended. Will see... Thanks for answer.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
As I've stated before, Power Off Alarm doesn't work. This time, it's a fresh install of LineageOS that I'm testing with. I've come back with part of the logcat I've captured after setting an alarm:

11-09 19:58:31.017 1280 1516 W BroadcastQueue: Permission Denial: broadcasting Intent { act=org.codeaurora.poweroffalarm.action.SET_ALARM flg=0x10000010 pkg=com.qualcomm.qti.poweroffalarm (has extras) } from com.android.deskclock (pid=7711, uid=10119) to com.qualcomm.qti.poweroffalarm/.PowerOffAlarmBroadcastReceiver requires oplus.permission.OPLUS_COMPONENT_SAFE

This comes from the PowerOffAlarm.apk that's shipped with LineageOS, where an intent requires the permission:

oplus.permission.OPLUS_COMPONENT_SAFE

LineageOS Version: 19-20221105-NIGHTLY-instantnoodle, but this has appeared in earlier releases.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
My apologies, I somehow missed your original post from September. Just by chance, I was also looking at power-off alarm since it wasn't working for me either, and I saw the same issue you spotted. I'm going to modify the PowerOffAlarm apk to require the org.codeaurora.permission.POWER_OFF_ALARM permission instead of the oplus.permission.OPLUS_COMPONENT_SAFE permission, since it starts working properly once I do that.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] baha900913:
In some games and applications (for example Apex Legends Mobile) vibration is enabled for a very long duration (10-15 seconds), when for example a match is begin in the Apex game.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Is this the only app where you were able to reproduce this issue? If so, could you maybe post the logcat output here as an attachment? I am not very inclined towards trying to run Apex Legends Mobile myself to reproduce the bug.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
So, apparently, LuK1337 had already patched the apk w/ this change before, but some time ago, when updating blobs, the patched apk got overwritten with the original. That old patched apk got lost to time, so he just went and repatched it. You should see it fixed in the next build.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] baha900913:
Yes I can, I'm currently on Oxygen OS

I'll post logs here in a few days.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] ziom5510:
Oneplus 8 in2013

Aster update 05.11 volte and vowifi not work
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
You are going to need to provide more details than just that, such as what country and what carrier. VoLTE and VoWifi work just fine on T-Mobile US, for example.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
Pulling logs after waking the display, while also looking at a clock, the reason for freezing might be related to the DisplayPowerController or DreamManagerService.

11-13 12:41:56.775 1196 1826 I PowerManagerService: Powering on display group fromDozing (groupId=0, uid=1000, reason=WAKE_REASON_POWER_BUTTON, details=android.policy:POWER)...
11-13 12:41:56.775 1196 1826 I PowerManagerService: Waking up from Dozing (uid=1000, reason=WAKE_REASON_POWER_BUTTON, details=android.policy:POWER)...
11-13 12:41:56.780 1196 1606 I DisplayPowerController[0]: Blocking screen on until initial contents have been drawn.

...

11-13 12:41:58.457 1196 1823 I DreamManagerService: Leaving dreamland.
11-13 12:41:58.457 1196 1573 I DreamManagerService: Performing gentle wake from dream.
11-13 12:41:58.457 1196 1573 I DreamController: Stopping dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0, reason='finished self'(from 'requested stopDream')

android_frameworks_base/services/core/java/com/android/server/display/DisplayPowerController.java at b6ce47054c0770ce028e44b165610a65417dfd33 · LineageOS/android_frameworks_base

Contribute to LineageOS/android_frameworks_base development by creating an account on GitHub.

github.com

android_frameworks_base/services/core/java/com/android/server/dreams/DreamManagerService.java at b6ce47054c0770ce028e44b165610a65417dfd33 · LineageOS/android_frameworks_base

Contribute to LineageOS/android_frameworks_base development by creating an account on GitHub.

github.com
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Thanks for looking into this. I'll use this info as a reference when I get into tackling this bug; for now, I'm working on USB-PD and HDMI/DP out.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Also, new update:

Haptics have been completely redone. We now have proper implementations for CLICK, DOUBLE_CLICK, TICK, HEAVY_CLICK, and TEXTURE_TICK. In addition, custom vibration durations should be working more properly now. bgcngm merged in my changes just now, so you should be seeing the new haptics on this upcoming Saturday's build.

EDIT: er, forgot that it's merged only in lineage-20. Not sure if I may pick it into lineage-19.1...

EDIT 2: now merged into lineage-19.1. The above message is accurate again.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] bermudist:
Hey guys! I'm new to the forums, and fairly new to the world of custom roms (I somehow stumbled into correctly installing CherishOS before though on my first try??) so I'm going to try and be thorough and informative with the issues I'm facing and try not to look absolutely foolish:

So I have the T-Mo variant OP8 (IN2017_11_C.43), and my bootloader is unlocked, I'm on MacOS and I have adb and fastboot in place. In fact everything works fine up until the last part of the LOS guide when I need to flash the rom in recovery. A few things occur:

I will receive an error in recovery saying "Could not find "META-INF/com/google/android/update-binary" in the zip file" if I'm flashing LOS from my platform-tools folder. That happens when I compress the rom. (I don't seen anywhere in the guide that tells me that I explicitly need to do this, but the guide says the Lineage rom being flashed needs to be a .zip, so I compress the folder into a .zip). Additionally if I try to flash the folder (the rom files not compressed but rather how it comes from the Lineage site) I get an error in adb saying that it's a "directory", and nothing else happens in adb or on the OP8.

Lastly if I flash the rom from my Downloads folder (instead of placing it in the platform-tools folder) I see the most progress here: I get as far as a signature verification error upon initiating the flash, but recovery lets me bypass it by selecting "Yes". However, it kicks me back to the recovery main menu with no further installation. When I go to reboot as it instructs in the LOS guide, I'm sent back to OOS12 setup. I'm having a hard time replicating this to be able to share the error log, but I recall seeing an "ERROR 21" and "ERROR 2" specifically on two separate attempts. Will reply back with the error info once I can replicate the results.

Anyways, I've spent a whole evening with this and can't figure this out. Any help would be greatly appreciated.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
W... What exactly are you downloading from the LineageOS website? You are downloading a file that has the following file name lineage-19.1-20221119-nightly-instantnoodle-signed.zip right?