yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] DEM0N Assissan7:
BUG REPORT: Battery status does not show in the notification shade while in portrait mode, but shows in landscape. (It does show when you go to the status bar settings and enable "show percentage," but it also shows the percentage on the status bar).

(both screenshots have "show battery percentage next to icon" off)

I don't know if this is intentional but it is extremely annoying and I would really like to see my battery percentage in the notification shade. Cheers!
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
What fingerprint did you use? I used the latest OnePlus 8 OOS 11 fingerprint and it didn't pass CTS profile matching. I then used the Pixel 6 Pro fingerprint and now it's passing...
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
I'd also like to report there's some issues with the light theme in QS. For example, the current time shows in a white color that's hard to see sometimes and the navigation buttons are also white. It's more of a nitpick of mine but would love to see it changed.

There's also a weird issue with brightness randomly lowering down a lot for no reason (unrelated to the issue above).
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] mvmike:
OnePlus 8 Europe IN2013 (10 & 11)
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I'm unable to replicate either of your notification shade bugs. I am able to see the battery percentage in the QS section with "Battery percentage" set to "Hidden", and in light mode, the time in the upper left corner changes to a black color. For @DEM0N Assissan7, are you running LineageOS without any modifications to SystemUI? If so, you might want to report this to our LineageOS GitLab Issues tracker, as I'm not familiar enough with platform side of things to know what's going on. For @cinnamonizer, I definitely know you're running Substratum Lite, since you mentioned that in an earlier post--see what happens if you disable that and other modifications.

As for the birghtness issues, @cinnamonizer, when you say "randomly lowering down", does it lower permanently until the next reboot? Or are you talking about Autobrigthness?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
I'm only using navigation bar overlay though, to make them look like OneUI buttons, that's all, no other active overlays.

As for the brightness, the screen randomly dims itself (a lot, almost to the minimum) although the brightness slider remains the same. I have adaptive brightness off.

Update: After disabling my navigation bar icons overlay in Substratum, I still get white time text and navigation icons in QS while using light mode. BUT, I noticed I have a live wallpaper on at the time. Replacing the live wallpaper for a static one fixes the white text in QS but the navigation icons still stay white as with all other A12 ROMs so I'm sure it's not a bug but a design decision. Would really enjoy it more if the navigation icons turned dark while QS is expanded to make them more noticeable. Would there be a root way to achieve this in case you don't want to change that behavior OP?

I should also report I don't see the battery percentage in QS using portrait mode but it shows in landscape view. Also the fingerprint reader doesn't always seem to work after all, sometimes I find myself having to input the code because it says my lens is dirty. I've never had fingerprint reader issues on ColorOS or OxygenOS. Always super smooth, never dropped phone either, no cracks, nothing. Lockscreen is laggy sometimes too, like it goes back to 60hz although I'm forcing 90hz constantly.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Oooh, yeah, now that you've mentioned live wallpapers, I am now able to reproduce the white clock text bug on LineageOS 19 on both my OnePlus 8 and OnePlus 6T, thanks! Unfortunately, I am not knowledgeable enough to know how to fix this bug. If you could file a ticket on LineageOS's GitLab Issues tracker, that would be appreciated; someone else who has the knowledge would be able to fix this.

As for the navbar icons, I might probably ask directly in the LineageOS Discord to see if someone can do something about that, because yes, that's not a very good design choice.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
It's just a small nitpick of mine haha! I appreciate the effort OP :)
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I forgot to address the brightness issue, oops.

That one sounds like its the same bug that I currently have in my 3rd post, where changing color modes seems to cause this odd brightness issue. Unfortunately, some apps like Google Photos seem to switch to an HDR color profile and trigger the bug as a result, so you can't just avoid watching HDR videos to avoid the bug. You can read that post for more information. (But yes, I'm currently trying to fix that bug right now.)
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
Thank you for addressing it :)

Yeah it seems like it only happens in certain apps, weird. What do you think could be the issue with my fingerprint reader situation? Also the lockscreen seems to be a bit laggy sometimes.

Appreciate the hard work in advance!
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
For the fingerprint issue, I can't say I really know what one could do about that, sorry. As far as I know, we're using the fingerprint service directly from OxygenOS, and I'm not sure if there is anything that I'd be able to change in terms of fingerprint accuracy, etc.

As for lockscreen lagginess, I can't say I've noticed its frame rate dropping. I have noticed times where when I try to wake my phone, the lockscreen fade-in freezes for a second or two, but that doesn't sound like the issue you're having...
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
The lockscreen fps only drops for a second or two, but it's definitely noticeable on my end. Does fingerprint always work alright on your OP8 for this build?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
For me, yeah. The only times where it doesn't work is when my thumbs are very dry (no skin oils or sweat). Wiping my thumb on my face to transfer some skin oils onto my thumb usually works (sorry if TMI).
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
You think it could be related to coming from COS12 C.32 instead of OOS12 C.33 perhaps? And yeah not really tmi don't worry haha.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
No idea, to be honest. You could flash the EU OOS 12 C.33 fw on your phone using this guide and see what happens, if you'd like? You will not need to wipe data afterwards, and if things don't work that great, you could follow the same guide to reflash the COS 12 C.32 fw afterwards.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
Ok I'll give it a shot later today and see how it goes, thanks. Do you think using an incremental build zip would work for extracting the partition images or would I need a full ROM zip? I found a download link for version C.33 but it's only around 800MB worth but checking the payload contents I see a lot of the partitions that the guide refers to.

(The latest version available on the OnePlus site is OOS11 and on Oxygen Updater it's OOS12 C.21)
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Zombify01:
I have IN2019 and currently on AICP. Does the SIM working on IN2019?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I believe a full OTA package for EU C.33 is available to download from this thread, so you don't have to deal with applying incremental OTAs.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I do not provide support for IN2019 at this point of time. You can read this post to see what happened when someone tried running this on their IN2019.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Zombify01:
Lineage OS 18.1 (Instantnoodle) worked fine on IN2019. So i was hoping Lineage OS 19 will work smoothly too.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
I have updated my firmware to EU C.33 and so far fingerprint is working okay. Will wait a day or two to confirm if my issue has been fixed. ROM still showing to be very stable after a couple days usage, if anything just need to check battery usage because I haven't been monitoring it. Props to the builder!
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Hi everyone! I've updated the 2nd post to contain much more detailed info about firmware upgrading for each supported and unofficially supported model. In addition, I've added a Telegram group invite link; you're welcome to join if you wish.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] OliverLew:
Thank you for these posts. I got a lot of valuable information like the brightness drop issue, and the removal of unlocked bootloader screen (haven't noticed before reading here).

As for the brightness drop issue, I also ran into it in the wallpaper setup view. Furthermore, back in LOS 18.1, besides lower brightness, the screen will also turn into greenish color(tint) after playing some HDR videos. I guess that's a similar issue to this one?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I think so? I realized I never actually tried playing HDR video back when we were using the OOS 11 based tree + kernel on Lineage 19 (before LuK paused development so he could wait for the OOS 12 kernel source drop), so I can't confirm the reason for that green tint issue back then.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] AnierinB:
Yes, the issue regarding green tint when watching HDR directly correlated with the iris bug, however it seems to have been resolved after some proprietary library updates. Sadly, the issue regarding brightness Is still present, however that's currently being worked on as pointed out by the OP.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] trillsp:
where did you see the ability to remove the unlocked bootloader screen, can you share that guide
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
That's not a feature you can toggle on or off; it's more like the OOS 12 bootloader will no longer show the unlocked bootloader warning no matter what.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jobrudo:
Thanks for the work on the update! I'm a little stuck and hoping for some help.

I have a OnePlus 8 - T-mobile version that in unlocked and just had Lineage 18.1 on it. I'm trying to upgrade to 19.1 and once I sideload the latest nightly build, it installs fine, but after the "reboot to recovery" step, it gets stuck showing the "The boot loader is unlocked and software integrity cannot be guaranteed..." screen. I can get back to fastboot and then flash the old 18.1 recovery to get it back to 18.1, but keep getting stuck on the boot loader unlocked screen again if I try to get to 19.1.

Any help would be really great! Please treat me as a complete noob if you know the fix :).

Thanks in advance
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Sure. Did you notice this warning when you were following the upgrade guide?

In any case, go to this post to learn how to upgrade your IN2017 (T-Mobile) to the required firmware.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jobrudo:
Thank you :) I did skip that warning. Thank you for the post link, I will try that out.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] thattechguy_69:
they should keep it like that, the message was bugging me and I wanted to remove it so bad but now that it is removed. I feel like the OS I installed came with the phone
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] AnierinB:
There is no guide. That's just how it is on OOS12 abl.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] cinnamonizer:
You have to upgrade to latest builds of ColorOS or OxygenOS. They automatically remove the bootloader unlocked screen that shows up on boot.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jobrudo:
Thanks again jabashque - after a few more bumps and bruises I got it working.

For some reason though, now my touchscreen isnt working - any thoughts on what could cause that? volume and power buttons and everything seems okay, just no touchscreen.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
What firmware version are you running? The post I linked mentions minimum firmware versions too--specifically, 11_C.20 or later.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jobrudo:
IN2015_11_C.11 - I'll get the 11_C.20 on
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Yeah... the post I linked to you back in the beginning specifically mentioned the minimum firmware version. I think I'll make that clearer by specifically mentioning minimum firmware versions in a larger font and explaining what issues one would see if they do not update to that version or newer.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jobrudo:
I should've read more clearly - I downloaded the most updated version on that list which was IN2015_11_C.11
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] KerbalNo15:
The unlocked bootloader screen seems to have been removed in the newer firmware versions.

Edit: oops wrong page
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] qutebrowsershill:
Has anyone tried to use this rom with dual sim cards? I'm using IN2015 with firmware from IN2013_11_C.33, and I'm not quite sure how to get dual sim cards back.... Unfortunately I can't figure out how to revert back to LOS 18.1 either so I'm stuck for now
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
That's odd... in adb shell, run getprop | grep multisim.config and paste the results you get here.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] qutebrowsershill:
I don't think grep got anything (I'm assuming the 1|prompt$ is just the return code), is there any way I can add it?

I'm now using the IN2015 modem.img though because I thought it might fix things, I can revert back for testing purposes
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I was just checking to see if vendor.radio.multisim.config ever got set. There's a bunch of init scripts that do the following:

check if simcardnum.doublesim=1 is in the kernel boot params, and sets the prop vendor.radio.multisim.config to dsds if true.

Copies the value of vendor.radio.multisim.config to persist.radio.multisim.config

checks the value of persist.radio.multisim.config and spawns a second RIL daemon for the 2nd slot if it's set to dsds or dsda

It looks like for whatever reason, something's going wrong in the 1st step. If you can join the Telegram group I linked in the 2nd post, I'd like to ask for some debugging help over the weekend to figure out what's going wrong there on your phone.

In the meantime, you can just bypass step 1 and 2 for now by manually setting the persist prop in a root shell and rebooting:

setprop persist.radio.multisim.config dsds
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] qutebrowsershill:
Hey thank you so much for the quick reply! It took me a bit too long to get a root shell (was I supposed to root my phone and use termux btw? or was there an easier way via adb?) but this did work, thank you so much!

I'll join the telegram server when I get my phone setup
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I guess for next time, you could go to Settings -> System -> Developer options -> Rooted debugging and toggle that on, then run adb root on your computer to restart adb in root mode. But yeah, what you did works too lol.

If you do join the Telegram group, do mention your XDA username in there if it differs from your Telegram one.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
I suppose for those who want to know what happened: qutebrowsershill's phone seems to show signs of being an IN2017 (T-Mobile) instead, not an IN2015, and the bootloader ends up reporting that it's not dual sim. But somehow, it has two distinct IMEIs, and the 2nd sim slot actually works if you force enable DSDS mode. Contrast that with literally all the other IN2017s where we still can't get the 2nd sim slot to work.

Yeah, I have no idea what's going on either.

EDIT: even weirder, the IMEIs apparently belong to an IN2015?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Ninua:
So I threw 19.1 on my new phone (with MindTheGapps) and it seems to work pretty well. Things I've noticed:

-The first OTA update I clicked on booted into an OS without a functioning touchscreen. Installing latest (not sure if was the same) via recovery worked again.

-Video over USB-c doesn't work with either HDMI or USB-c. As I understood the Oneplus 8 should support this? Could be a Oneplus issue, read reports it doesn't work on OO either.

-Downgrading to anything 18.1 (to test the above) doesn't work. The recovery image won't show and installing from the newer one fails. But I think this expected?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
That's... odd. Let me know if that happens again.

I remember this used to work on custom roms using OOS 11 firmware and blobs (including when I was running my own builds of Lineage 19 from before we moved over to using OOS 12 oplus fw and blobs). I haven't been able to test this that well because all my equipment for connecting my phone to a display has suddenly become defective... but I can try to find out if I decide to purchase a USB-C to HDMI cable.

Yeah, that's expected. Way too much was changed by OnePlus/Oppo on the backend side between OOS 11 and OOS 12.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] hammerhaigh:
Sideloaded this flawlessly with my T-Mobile OnePlus 8, not an issue so far (besides the aforementioned lowered brightness). The only difficulty I'm facing is that the fingerprint sensor is having slight troubles when I attempt to use it. In other words, it's not functioning as it would with OOS. It's slow and won't recognize my fingerprints 99% of the times.

EDIT: Regarding the fingerprint sensor, it randomly started working normally after this reply. Hopefully it stays that way!

Any explanation for this behavior?

While I'm here once more... From testing, the Clock application will ask for the "Power Off Alarm" permission, but the alarm will not go off at the specified time as the OOS Clock application would if the phone is turned off. Related to https://gitlab.com/LineageOS/issues/android/-/issues/3806?

Also, F.Y.I. I didn't need to use any modified firmware. I went from T-Mobile OOS 12 to LineageOS 12 by sideloading, with no problems! Added this just in case you wanted to edit your OP for the IN2017. I didn't flash any modems, just followed https://wiki.lineageos.org/devices/instantnoodle/install the whole way through.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Ekterm:
I seem to be having the same problem as this wonderful individual, I see that I need to flash IN2015 EU firmware and the IN2017 modem. I think I have the right ota zip files, just not sure of the specifics, would this be correct?

- Flash whole IN2015 zip with TWRP

- Extract modem.img from in2017 ota and flash to modem with TWRP

- Boot and let it load to setup?

- Factory wipe and format data and flash Lineage 19

Or would just loading OOS 12 first be better as the post above me mentions?

Edit: Ok i've tried flashing the IN2015 and the IN2017 firmware but TWRP throws an error with each, and thats from USB-OTG storage because it says it runs out of room when pushing to sdcard (which its not, its completely wiped) and says there are insufficient permissions when trying to sideload.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Ninua:
So do you take drivers/firmware from future OOS updates? That might solve it if Oneplus cares enough. I'm really hoping this gets turned on again as I need it in my daily workflow.

Yeah, too bad, bit of a pain as I can't easily get back to stock either to test due to the community server hosting the MSM tool being down and I'm hesitant to doing this manually.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Ekterm:
Which MSM tool is that? I found MSM tools here, are those not ones I should use?

https://xdaforums.com/t/step-by-ste...nternational-with-bootloader-re-lock.4345305/

Download MSM Download Tool: Unbrick any OnePlus Device [Video]

From this guide, you could download the MSM Download Tool for every OnePlus device and then use it to unbrick your OnePlus device.

www.droidwin.com
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Ninua:
The download links your second link states are down, and I haven't been able to find a mirror. Not sure about the first one though, seems to be another version, but I'll have a look into that, thanks!
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] golf174:
hello! I noticed a bug, sometimes while listening to music via Bluetooth (ldac) and moving between the uapp and poweramp applications, the music starts singing simultaneously via Bluetooth and from the speaker in any program (YouTube, Spotify), only a reboot helps. BT on/off not helped. Notice: USB audio player pro and poweramp use hi-res direct audio output.

Another bug: sometimes the fingerprint does not work well, a reboot helps.

Another bug: sometimes the phone does not charge, a reboot helps. Also, sometimes when connected to a computer, there is only charging and nothing else, a reboot helps.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Ninua:
So, I tried lots of solutions to get back to either stock or lineage 18.1, as I really need video out. The MSM tool linked to above requires a log in, and the "community" ones are down (I suspect OPPO). All recovery images but the Lineage 19.1, including TWRP, simply fail and return to the bootloader.

Can anyone point me in the right direction?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
What OnePlus 8 phone model do you have? (e.g. IN2013, IN2015)

Meanwhile, if you want to roll back firmware to OOS 11 to run Lineage 18.1 again, then follow the same "firmware upgrade" steps, but using the images from an OOS 11 OTA zip. I did that on my on IN2017 once and I was able to roll back to OOS 11 firmware that way, including getting the bootloader unlock warning screen again.

You could even flash stock OOS 11 again via Lineage Recovery's fastbootd probably, but I've never tried that myself. I only flashed stock OOS 12 via that way, and that required me to recreate the various Oppo-specific "my_*" partitions in the super partition.
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Ninua:
Yes, thank you, that actually worked! Did a firmware... downgrade, and after that 18.1 recoveries started to work again (and I got the bootloader warning screen back)!

Now I'm just hoping OnePlus fixes this issue so it can be integrated on LOS again!
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] drswan1:
I flashed my phone with MSMTool and updated to the lastest os12 update before trying to flash the recovery image for lineage. Once I did, I got the "the current image(boot/recovery) have been destroyed" message.

What did I do wrong here?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Did you follow the instructions, where it said to flash some extra partitions (dtbo, vbmeta) before flashing recovery?
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] drswan1:
Ah, I did not. I guess thats the problem. Thank you 😅
[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] Neoxal:
I had some issues as well until flashing these extra partitions. The instructions on lineageosroms.com does not seem to have those instructions but the instructions on wiki.lineageos.org does include them. I'm not sure who is the maintainer for lineageosroms, but it would be helpful to have that site updated as well, unless that is not an official website.