yashsingh1/xdaforums huggingface dataset:
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Have you tried Google messages?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] JedidroidX:
seems to be working with Signal, has been about 2-3 days with no issues!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] jabashque:
Just to check, did you migrate over to OOS 13 firmware when you updated to LineageOS 20? The issue with broken sensors in general happens if you're on OOS 12 firmware still.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] exthomeboy:
I am very satisfied with LOS20. It runs smoothly and is not overcrowded with features. But two things bother me. One is automatic lighting. Is mentioned again and again. The manual solution doesn't help either. Second is the battery consumption. In standby apparently like OOS. But when used, a lot of energy is sucked from the battery. Am I alone or have other people noticed this as well?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] D€INOS:
I use Velis auto brightness 5.00 with Evolution X, works great when I learned how to use it.

I wrote about a nice tip here: My latest post in the xda thread
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
Velis is great and fixes this critical shortcoming of this ROM in my opinion.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
I know this is normally frowned upon since I'm not on this ROM (I'm still on LineageOS 18.1, I've been building my own since support ended, waiting on 19.1 or 20 to stabilize) but I had to let everyone know that this app "Velis auto brightness" has been working great for me on LOS 18.1. So, fingers crossed, we've finally found a solution to the long standing brightness issue. assuming your sensor is compatible, and it might not be (before you get your hopes up).

My sensor is listed as "stk2232" and the other person who said theirs was working was "stk33502".

tcs3408 was reported to NOT work by a previous comment, but I would guess any of the "stk*****" will probably be compatible with the Velis auto brightness app. It's not a guarantee, but I would say it's worth trying.

I'm planning on finally upgrading to LineageOS 20, as auto brightness was the last deal breaker for me, and I'll absolutely report back if it's still working for me.

Here's the app I used to check my sensor chipset (listed under "light"):

Sensors Toolbox - Apps on Google Play

Test all Sensors in your mobile device

play.google.com

Here's the app itself:

Velis Auto Brightness - Apps on Google Play

Get the fun back to your auto brightness...

play.google.com
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] tostah:
Reg. battery consumption: I noticed an increase in battery consumption as well (compared to LOS 19).

In my case (KB2003), the battery drain was caused by a wakelock (rmnet_dfc wakelock).

Changing to a different kernel with a fix for that issue solved it for me. I am now on 1% battery drain per hour in standby and a good full day of usage.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] exthomeboy:
I've never flashed the kernel, but it shouldn't be a problem. Which kernel can you recommend?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] tostah:
I use the Meteoric-V9.4 kernel.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] exthomeboy:
what do I have to consider, how about the regular updates? does the kernel have to be flashed every time? Thanks
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Shmi117:
Since no one was replying, I decided to test myself.

I was able to OTA update while on a custom kernel, after reboot I was back on stock lineageOS kernel. Next time I OTA update I will test to see if its possible to flash the kernel to the other slot before rebooting.

I did all this from my phone using the Kernel Flasher app and blu_spark kernel.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
i currently have an 8t running havoc os from 2020. what would the steps be to get this running with meteoric kernel? i assume i have to flash a newer stock rom, and then follow new install procedures?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
MSM to newest stock (or just find it and flash it manually), unlock BL, follow official instructions, flash kernel
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
hey i'm sorry i've been googling for about half an hour and can't seem to find the most recent stock rom. am i nuts?

EDIT; it's the third post in this entire thread. whoops!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
sorry to necro-reply, but my model shows as kb2007. would something else work?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] TheNewHEROBRINE:
You can download the firmware for your exact device model by using the Oxygen Updater app.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
the app shows kb2005_11_f.13 as the one to download, so i guess i'll do that and hope for the best
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] TheNewHEROBRINE:
You can set the device model in the app settings.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
damn this all got so much more complicated than i ever remember custom roms to be. payload dumper now requires python? msm tool requires a login?

EDIT; oh i figured out msm by reading instructions. my mistake!!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] BillGoss:
You could use https://github.com/ssut/payload-dumper-go which is an executable and doesn't require Python.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
thats exactly what i tried following the instructions but i just do not see an exe file, i thought it needed python because thats what i saw when looking it up on youtube
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] BillGoss:
Did you click on this?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
the exe for payload dumper just launches and closes so i went with mdm tool, and i'm getting "device not match image" error.

im not even sure where to go from here
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] TheNewHEROBRINE:
For the payload dumper, I think you need to run it on the cmd and specify the path to payload.bin as an argument after the command.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
i got msm tool to work, im stock. thank you so much for trying to help my braindead ass
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
it's a little late to just be noticing this on the supported devices page. im hoping this is just an oversight? no kb2007

EDIT: to make things worse, i got back to stock and followed the system updates, but it only gets me to android 12, kb2007_11__C.45

i also checked oxygen updater only shows kb2001 kb2003 and kb2005

should i move forward and install this, only having gotten up to android 12 (oxygen os hardware version 13?) as a base? is there an android 13 update i can use?

EDIT 2; found some previous stuff in the thread to set me on the right path
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
it's a good thing i decided to try this on my day off from work. took a couple hours to get my kb2007 successfully running stock kb2005 android 12. but the system updater keeps failing getting to android 13. system download works fine but when it restarts, it says congrats on your system update, but is still on 12, and shows an update to 13. i did this 4 times not realizing. here i go down another rabbit hole

EDIT; scratch that. miraculously the 5th time just magically worked. finally at stock. 9 hours later, im ready to start with the custom rom process ahhahahhahhaa
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
What is your--

LineageOS version: 20

LineageOS Download url: https://xdaforums.com/t/rom-official-kebab-13-lineageos-20.4536037/

Gapps version: https://wiki.lineageos.org/gapps 20

Did you--

wipe: not sure what to wipe

restore with titanium backup: havent gotten that far

reboot after having the issue: thats the issue

finally got everything booted but once i set up magisk and did the whole patched boot.img and then fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

and now the phone won't boot. it goes to fastboot by default, and i can get to recovery mode. i don't even know where to start
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
DISCLAIMER: I HAVEN'T FLASHED 20 YET SO MAYBE DON'T LISTEN TO ME.

Giant freaking disclaimer aside, here's what worked for me on LineageOS 18.1.

First, I don't think you need to do all that. Just boot TWRP to wipe everything:

THIS STEP WILL DESTROY ANY DATA ON YOUR PHONE PERMANENTLY:

Wipe everything means "factory reset" (from recovery custom recovery like TWRP, or just fastboot, but TWRP is easier if your phone/LOS build supports it, I don't know if this build does, but I do know the phone does)

AND then format (NOT just wipe) the data partition. Can also be done in TWRP under "wipe".

adb sideload (can be done from TWRP I think, also just adb) the LineageOS zip, reboot recovery, sideload gapps, reboot recovery (I think this reboot can be skipped, but just in case), rename magisk.apk to magisk.zip, adb sideload magisk.zip

Reboot (or do the "both slots zip" or whatever it's called, if the wiki tells you to).

I haven't done 20 yet, so maybe wait till someone corrects or confirms my instructions here, and if you want to try anyway, listen to the official instructions over mine here. Like I said, I'm still on 18.1, and doing these wrong can break stuff.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
i didnt expect anyone to respond so i just went through everything again from step 1 and applied magisk as a zip instead of doing the apk route.

thank you so much for trying to help me

edit; after a second read that is exactly what i did. you were absolutely right
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] f2bacon:
finally got it running and damn is it SMOOTH. feels great but im already noticing some differences. i know lineage is less feature/customization based and more about stability. and i need that in my life at this age, but i noticed a lot of what i thought were standard features aren't there (or maybe aren't on by default and buried in a settings menu?)

no detailed charging info? no AOD settings or customizations at all? is there a way to get rid of the little bar at the bottom of the navbar? i think its called like navbar tips or something

it took me forever to find the settings shortcut in the qs panel, i went from android 10 to 13 so that redesign sure is a hell of a surprise
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] exthomeboy:
The Kernel Flasher needs root, which I don't have and don't want to do. Can the kernel also be installed via sideload?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] TheNewHEROBRINE:
I think you can patch a boot image with Magisk and then boot it instead of flashing. This will make you have temporary root until you restart your phone.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] mattmcbeardface:
Anyone else apply the recent OTA update and get stuck in boot loop?

Update:

For anyone else who may have experienced this issue when updating via OTA from lineage-20.0-20230223-nightly-kebab-signed to lineage-20.0-20230302-nightly-kebab-signed...while using LiteGAPPS version [RECOVERY]LiteGapps_arm64_13.0_v2.6_official. I had to sideload the LOS update and update LiteGAPPS to v2.8 before reboot to system. All works now.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] uaiclout:
Does anyone else have the problem that USB type c headphones are not detected?

They only work when I reboot with the headphones connected. After a reboot with headphones connected, I can unplug them, plug them in again, and everything works as expected. Only when I charge my phone and afterwards try to connect the headphones, they are not detected anymore.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Are you using a generic charger/cable? Might be that not the headphones
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] uaiclout:
I'm using the OnePlus charger that came with the device. (But the problem also occurs after using any other charger or connecting the phone via USB to a computer.)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Very strange. Next step of diagnostic would be to rule out some other devices. Do you have an OTG adapter? Test some thumb drives, make sure they and

Show up during the conditions you've mentioned the headphones don't (and do).

And maybe rule out some other headphones, if you have them. Standard to USB adapter if needed
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] 21prods:
Strange behaviour... I use USB type c headphones and they work very well, I have never suffered anything similar to that.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] uaiclout:
Thank you for helping me with debugging.

Connecting a USB type C SSD does work and does not affect the headphones (if headphones work after a reboot with them being connected, they still work after connecting the SSD - and if they do not work e.g. after a reboot without anything connected, they also do not work after connecting a SSD).

Unfortunately, I do not have any other type C headphones or an adapter and my type C to A OTG adapter is buggy (works on my computer, but also does not on any other Android device I've tested)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Ok! Progress.

Unfortunately (fortunately?) that's pretty definitively the headphones then. If other devices work as they should when the headphones don't, before and after, then it's at least safe to make an educated guess that the headphones themselves are the issue.

Are they new? You might be able to get a refund, based on these diagnostics.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] uaiclout:
They work on other Android devices and on my computer. They also used to work on LinageOS 18.1 on my OP8T.

(Samsung AKG Type C Headset)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
That's not uncommon in hardware diagnostics. It could be a flaw in the LineageOS build, or a hardware flaw that doesn't have the same outcome on different codebases.

But either way the outcome is probably the same. This will probably not be fixable.

If you want to do some further diagnostics, and see if we can find a bug to file (I can show you how to do that also). The next step would be a reboot of the phone, trigger the "bug" and then check your phone logs.

This is my fav app for doing so.

If you want help looking at the logs, don't post the text in the thread here. Upload it to pastebin or similar service, and post a link to that log.

I can help take a look

I've had the app installed forever, so I'm not 100% sure on this, but I think you can use root or adb to give it access to your phone logs. At least I know root isn't mandatory, but you might have to jump through some hoops to get it running with the appropriate permissions

Logcat Reader - Apps on Google Play

View your device's logs

play.google.com
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] tastysushixd:
Hi people! I'm having a big problem and would like to know if it happens to you too.

I did all the installation steps listed in the Lineage OS wiki. Installed it, everything was working fine at first. But lately since the original installation + the new updates my device randomly hangs in a black screen, like if you couldn't exit the standby mode, and have to reset it pressing the power button for a really long time. Even using Android auto happens 🥲

It's starting to happen with some frequency. Didn't have this problem in oxygen is rom.

I tried saving logcats, but since the device gets stuck with no previous advice I don't actually know how to read them and the possible error.

Any help or guidance would be appreciated :)

Here is some info:

Lineage Version: 20-20230302-NIGHTLY-kebab

Compilation: lineage_kebab-userdebug 13 TQ1A.230205.002 3a48ea0afd

Model: Kb2003

Sim1 carrier: None

Sim2 carrier: Yoigo
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Post the logs. We will always need an exact error or logs to be able to help. Instructions are in my comment right above your
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] tastysushixd:
I recorded the logs of the device right now. I don't know what might cause that failure neither how to trigger it. And can't record the logs in that exact moment because the system becomes unresponsive. But here are recent logs. Thanks for helping me out :)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Check my comment before your first one for instructions. The short version is, upload them to pastebin and post the link here.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] tastysushixd:
I've already managed to upload them. Thanks 👍
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Please upload them to pastebin as instructed. This is not a medium that will allow us to analyze them effectively. And it clutters up the thread.

If you posts a link to them on pastebin, or in a text file as an attachment, I'm still willing to try and help you diagnose this.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] tastysushixd:
I had to use another too to paste it. Logs are too big for pastebin

Log - 4ed54823

<<< log_count = 2682 >>> [03-05 03:07:53.546 3464:3602 I/CryptauthV2] [HaveKeyWithKeyNam - 4ed54823

controlc.com
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
That works, thank you! Give me a bit to review the logs. I'll get back to you tomorrow at latest
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Ok I'm not seeing anything specific that would account for that behavior, but there's an awful lot of telegram errors in here.

I would try uninstalling the telegram app, and see if it goes away.

If not, the catchall solution for these ambiguous issues is to backup the data, flash back to stock with MSM tool, and then redo the LineageOS install from scratch. It's not ideal, but it almost always solves these issue. Assuming it's not hardware failure.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] tastysushixd:
Thanks for your help. I think I'm going to end flashing stock when I can. I prefer lineage os. But I want something more stable 😅
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] tastysushixd:
Whilst I love the Lineage Os project, there should be a way to report errors to not so technical users. I think that's the obstacle of the today roms landscape and why it's a bit in decadence. Technology evolved and most OEM roms have mechanisms for reporting errors without any hassle.

I'm a developer myself, but I just don't specialize in Android, so don't know a lot of the tool or how to use them. Just to make android apps...

This is not a rant at all, but just what I've been feeling since I've been installing custom roms from 2014/2015...

In the lineage os gitlab there are a lot of errors that I think would be valid. Logcat, description of problems, etc... But just because they don't exactly follow a template are closed in a determined time. Even if the necessary info is present.

This is a hassle for normal users. And some of them might go back to their oems skin like I'm about to do.

Thanks for the help anyways 🥰
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
That's correct, custom firmware is absolutely not for beginners. And the posts clearly state that.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Vipe838:
USB-C Audio devices not being correctly recognized at times has been an issue since at least LineageOS 19.

I personally only use a USB-C to 3.5mm adapter in my car for playing music and to me it happens intermittently.

Sometimes it doesn't happen for weeks other time's it happens daily.

When it happens I think the phone doesn't detect the device getting connected correctly.

After which it starts handeling the audio output inverted.

Audio device connected -> Phone plays audio through speaker.

Audio device disconnected -> Phone tries to play audio through disconnected device.

99% of the time it can be fixed by reconnecting the audio device a few times or if that doesn't work rebooting the phone.

I've been wanting to make a Bug Report on the issue for a while but as it happens intermittently and only in my car I haven't been able to get a log file.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] molendus:
Hello, there is a small bug on oneplus 8t, on both 2023-03-09 and 2023-03-02 versions

When you connect to computer or usb otg

it fails to switch usb modes "use usb for" and "usb controlled by"

temporary solution:

1. developer options

2. default usb configuration

3. set to charge

4. change from charge to file transfer

5. reconnect usb

6. all usb controls work again

This fix works untill you change to charge and reboot your phone, then you need to do this again.

video here
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Recall0317:
Few months ago I posted that with LOS20 I don't have a working ambient light sensor. After that I also noticed that the proximity sensor did not work. Now I noticed that not even GPS is working with Sensor Test app. Also some app notifications (Pushover in my case and I use it a lot) are working only sometimes.

I am wondering if OP built the phone to different markets with such a difference in sensors that many features are just plain broken with LOS20 for good. Navigation works with data instead of GPS, backlight can be adjusted with Velis (but it needs to use camera as an ambient light sensor) and the proximity sensor is only a pain during phone calls. None of these issues are a dealbreaker by themselves but all together the phone just feels clunky to use.

I absolutely hate OOS, but I am really starting to think that the stock OS, for me, is more usable than this. Unless anyone has a fix in mind or other OS to recommend.

Am I the only one running on these issues?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] linrunner:
Transition from 19.1 went super smooth. Just followed the official instructions. No issues with 20 so far. Great ROM, great maintainer. Thank you @LuK1337 (y)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] troypulk:
Hello,

So after I updated the firmware and flashed lineage-20.0-20230323-nightly-kebab-signed.zip from here https://wiki.lineageos.org/devices/kebab/upgrade

I got this warning

"Orange state

your device is unlocked and can't be trusted

it will boot in 5 seconds "

and it will not restart and adb will not work and it stays in fastboot.

What do you think I should do next?

Thanks
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Don't tag devs. Your issues are not that important. There's plenty of us tech savvy people in here to help who didn't already spend hundreds of hours of their life to build you a free operating system.

Start over. Follow the instructions/wiki.

MSM back to stock.

Flash LineageOS as instructed in the official documentation (the wiki) unless the post here tells you otherwise.

Reboot to recovery/fastboot and flash the arm64 gapps linked for this specific firmware, if you want Google play and normal Android apps to work.

Boot.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] troypulk:
Thanks,

I removed the dev.

adb does not work

I'm on linux how do I proceed without the MSM tool?

Thanks
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
Unfortunately you can't use MSM tool on Linux (but great choice of OS! I'm a Linux fan myself).

You can still fix this on Linux, you'll just need find the stock firmware file and flash it manually.

Here's instructions:

https://xdaforums.com/t/msm-or-return-to-stock-on-linux.4433433/
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] thefanum:
And here's the stock firmware files for the OnePlus 8t

[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds

Added 11.0.5.6 KB05AA full zip from support website to OP

xdaforums.com