yashsingh1/xdaforums huggingface dataset:
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
Adaptive-brightness definitely does not work as you'd expect, unless the LOS 19.1 behavior is what you'd expect/want.

Adaptive brightness not functioning as expected and is often far too bright (OnePlus 8T/kebab- LOS20) (#5361) · Issues · LineageOS / issues / android · GitLab

Expected Behavior Expected behavior would be a smooth, stock-like curve or screen luminance mapping vs. the light sensor's reading so that...

gitlab.com

If I compare the current behavior to either the stock software or other devices entirely with other and/or stock OS's, the LOS 20 behavior is extremely aggressive when it detects any source of light. It typically jumps to around 80% in many circumstances and rarely adjusts itself lower unless there is a massive drop in what the sensor detects. For the sake of argument, I've been keeping adaptive turned on and then manually adjusting the slider to try and help it "learn" but I've not seen anything that even resembles learned behavior.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] IAAxl:
Sorry to hear that you have an abnormal function...

I'm not a developer, but personally I can't reproduce this issue. I've tried turn extra dim on and off, but the adaptive brightness works on both.

My family use OnePlus 9 pro on stock ROM, I've compared the behavior between theirs and mine, but still found no major disability,. Although under the same darkness they don't always adjust to the same level brightness, the process is both quite smooth.

Do you think this might be related to dirty data or buggy firmware? Will you please try to do a backup and have a fresh install to test this function again?

Or, could you please record a video about this, for reference by developers and other users?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
Appreciate the thoughts, but I definitely don't think it's firmware related or from old data. Stock OOS 11/12 adaptive brightness worked completely expected, and then only a few minutes later after a full wipe and flashing LOS 19.1 for the first time the issue was immediately present. It's also not just myself that's reported/noticed this on the kb2005, and it's been discussed a little in the 19.1 thread also.

The only other thing of note I'd mention, though it may be completely unrelated, is that applications that have custom brightness adjustments also don't register a lux/luminance sensor for this device during setup once LOS is installed. (Velis is one example, and it also worked completely fine on the stock software, no issues)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] IAAxl:
I tried to install Velis APP and found something weird.

I'm running LOS 20 on kb2007 (with kb2005 firmware), adaptive brightness works for me, but Velis APP also can't detect brightness sensor on my device.

Then I checked AIDA64, the output shows:

Spoiler content hidden.

No matter I enable/disable "One shot auto-brightness" or "Extra dim", the "stk33502 wise Light Sensor" always stays off, but the adaptive brightness function still works! How? It can't be the front camera anyway...!

Am I aiming the wrong sensor, or is this a result of the new permission control?

My knowledge is limited at this level, sorry but I think you need help from a developer or a code reviewer...
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] erictmc:
Great stuff! Thanks a lot! I used this and now safetynet is passed and all apps can run properly.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] silverhazesupreme:
Same here, adaptive brightness just doesn't work well. It's like it has two points it moves to: too bright and too dim

Edit: Just wanted to add for those who are interested in battery life - it's not great, at 2 hours of SoT I'm at 60%.

And that's after turning adaptive brightness off and keeping the brightness fairly low, toggling off Bluetooth and location when not in use and leaving my phone to charge overnight for optimization
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
I noticed the same exact behavior with Velis, and I agree that I'd be surprised if it was using the camera when it actually has a luminance sensor.

When I spoke with the Velis dev they suggested it may be down to the way adaptive brightness is implemented in LOS for the kebab, perhaps requiring it to read kernel values instead of accessing the sensor directly.(that's something they had seen far in the past with older devices) If that is the case they also alluded to that being why it likely doesn't work incredibly well compared to other implementations/devices. While I wouldn't consider this particular thing alone a deal-breaker for using LOS, it does feel like a step backward to the days where adaptive/auto-brightness was unanimously terrible on almost every device.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
I'm seeing similar battery life to what you are, though truthfully I don't know that it is materially much different than stock was for me. (maybe slightly worse than stock) I'm at 51% remaining right now, 2hrs 15mins screen on time, BT/WiFi always on, and 5hrs BT use time.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] mal13:
I guess it depends what you do with your device as i have sot 4h 48min and i´m on 41% battery. I don't play any games or so. BT 4h 51min.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] paul4762:
I did a clean install on lineageos 20 but I did not update the stock firmware from Android 12. Is it possible to update the firmware without messing up lineageos or do I need to start all over somehow?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] OTAx1:
Upgrading now. Here goes nothing.

adb sideload [file.xyz]

Working!

Thanks Luk1337!

ps - OTA updater took 1/5 update no issues.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] stickmanChampion:
Updated without any problem <3.

Thanks for the work you put into this.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] exthomeboy:
me too
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] neniick:
Hi,

Im trying to get the play protect certification with ih8sn.

Used the instructions from the thread with the config file you shared, but still no luck.

Could you maybe assist me to get it working?

I am on the latest build (20-20230105) and my phone is a KB2003 model.

Im also rooted with magisk and tried shamiko and universal safetynet fix, but still the same result.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] qwe2968:
If you download APP named "Play Integrity API Checker" and pass the first two check, it means you get the play protect certification.

Sometimes the status will be delayed.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
For what it's worth, I did not pass safetynet without a modified version of kdrag0n's universal safetynet-fix. I used the fork here. If you're not comfortable with the fork, there is an official version of the safetynet fix in the works but it is not released at this point and is still being tested. (you can follow that thread here)

Also, after you set everything up and hide magisk from all the google services, you'll need to clear data/cache for google services and reboot before it'll show as passing since you've already tripped it. And if you need/want to change the device props you should probably use MagiskHide Props Config to make sure you're using a certified fingerprint for your device.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] neniick:
Thank you, the modded usnf worked.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] snaggen:
I had to reset the storage and cache for the application "Bakgrund och utseende" in my swedish phone, translates to "Background and appearance". I upgraded from LOS 19.1 following all the upgrade steps closely, and everything worked fine except that when I selected Background and Apperance in the settings menu (or by using the Trebuchet context menu) it the app crached. But by clearing the cache and data for it (by searching for the app in the settings menu) I was able to get it to work. Just if someone else runs in to the same crash.

EDIT: When I ran the app, I had to give it permissions to access the backgrounds, for it to view the current set lockscreen and background. Note, that I had already looked at the permissions, and ensured that no permissions were missing, still when I ran the app I had to explicitly allow this. Not sure if this is related to the crach or not, just another oddity I saw that might have been related. Anyway, when I granted it permissions things worked as expected and the settings worked.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] jjnova:
Are you using gcam now? After updating to LOS20, gcam crashes as soon as launched. So uninstslled and went with Greatness gcam, but same result.

Using snap versions. Not.sure what is going on. The new Aperture camera looks way better in the viewscreen than when the photo is processed.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] hhllss:
Hello,

Thank you again @IAAxl (and of course, thank you @LuK1337 ) ! I made the update in two steps and everything went nicely one in the morning, the second at the end of the afternoon (I just find a situation where slot b was empty, but that was my fault. "adb sideload copy-partitions-20210323_1922.zip" solved the problem, but that is well known). Anyway now running LOS20, nicely and smoothly, and did not loose anything.

Regards,

H
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] IAAxl:
Check this "https://lineageos.org/Changelog-27/", the camera API changed.

Suggest contact the author of ported gcam and see if there's an update.

Edit: Sorry the info above seems wrong. Please check others' suggestions.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] LuK1337:
...did this post say anything about camera API?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
I'm using Greatness Gcam 8 with no issues. It was installed on 19.1 and is still fine post 20.0 upgrade.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] jjnova:
Out of curiosity, are you using the version of Greatness in the OP? That build is from 2021 and I have been trying with builds from 2022, Starting with Greatness.20220901.2136Release_Snap

Perhaps I can just keep going back in time and eventually one will work. If you are using an older build, it would be interesting to see what changed that causes newer releases to crash.

And for clarity/posterity, this started immediately after updating to LS20, when my GCAM was Wichaya 8.1.101 V1.6
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
I'm using the latest port from here: https://www.celsoazevedo.com/files/android/google-camera/dev-greatness/ (2.204 / 220901.2136) I don't remember where exactly in the thread it is, but it's in there somewhere.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] jjnova:
Well shoot, I wonder why it works for you and not I.

I installed OpenCamera just to make sure something would work. No problems, seems to be working flawlessly.

I appreciate you doing the leg work so I could verify. Hopefully I think of something out of the blue.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] mal13:
From here i've using BMG's and it works. Tho no qr-codes work but i assume its related to gapps i installed. Nikgapps basic that is.

Recommended Stable Google Camera Port Versions

A list of suggested / recommended and known to be stable Google Camera apks.

www.celsoazevedo.com
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
That's really strange. So if you uninstall Gcam, wipe those folders on internal storage, reboot, and then install that one I linked and the associated config files...it just crashes and doesn't open?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] IAAxl:
Sorry for wrong info... I thought the migration from camera2 to camerax caused this but it seems not...

Original post edited...
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] angus6969:
hi . i ve a strange question i m on lineage 20 5/1/23 and when debug is active i can't see my phone on pc. in other android version iI always leave it on and when connect the phone i see it without problem. is a bug or i forgot something?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
This is interesting and I just noticed the same behavior. The MTP driver won't get recongnized correctly unless I turn off USB debugging. It was working fine on LOS 19.1 so I think we need to submit a bug report for this.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] hhllss:
Hello,

I noticed that F15 firmware was out, two or three days ago, just before upgrading to LOS20. I never did any firmware update after flashing a custom rom (I mean following https://wiki.lineageos.org/devices/kebab/fw_update), but I was asking myself if I should upgrade or not as a rule of the thumb ?

Regards,

H
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] JedidroidX:
Those fastboot commands regarding "fastboot flash --slot=all" never work for me. I just upgrade via MSM and Oxygen Updater app. Upgrading always ensures the best smooth user experience.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] LuK1337:
...they work fine unless you use 2015 fastboot.exe.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] hhllss:
Never had a problem, also. Well being on Linux (Arch derivatives), I am always up to date anyway 😁.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] IAAxl:
Personally, if I enable USB debugging in developer options and connect it to PC, adb won't get any permission unless I enable usb file transfer from the notification at the same time. (Default to no data transfer.)

Is this your case?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] mal13:
I had same problem (unknown option-error). I found i had old (dated to 2016) fastboot on android folder in my windows pc. Manually updated it and after that command started to work. Check your fastboot version.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] TheJabusz:
Anyone else having an issue with Night Light and setting a schedule? If I select 'None' to change it, it flashes momentarily with other options but none that I'm able to select.

Everything else is smooth though a few days in.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] mal13:
I have it set from 8pm to 6am and it's working nicely. Tho it doesn't seem to include lockscreen.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] TheJabusz:
Thanks for confirming, turns out I'm a dummy and had an app drawing over the menu so it was butchering the option. Woops!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] angus6969:
yes, I hadn't noticed this behavior before but I had to switch to another pc and I had to play a lot with connecting and disconnecting the cable and switching between data and charge only and only in this case did it ask me to enable the pc
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] angus6969:
After a day wiith no problem ,today i have a problem with bluetooth, android say bluetooth app stopped working and of course nothing can connect.. i tried to reboot sevveral times, clear cache ,reflash los and finaly reflash via fastbootd blutooth.img but same issue.. anyone else? solutions other than a clean install?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] dangerousnerdrays:
A few weeks ago I made the switch to LOS 19.1 and now I'm ready for LOS 20.

I started following the official LineageOS upgrade guide, found here: https://wiki.lineageos.org/devices/kebab/upgrade and, as that guide states, I need to be on Android 13. So, I need to follow the Update Firmware [on kebab] guide, found here: https://wiki.lineageos.org/devices/kebab/fw_update.

I was able to grab the latest Android 13 Full Stock ROM from LuK1337's post (#3, this thread) and extracted the files using payload-dumper-go.

I checked my DDR type (DDR4) in LOS Recovery with success. I then booted into Fastbootd and attempted to proceed with flashing the images mentioned in the guide (abl, aop, etc), but I kept getting an error because the option "--slot=all" isn't a valid option. My KB2005's current slot is 'b'. I'm on Linux Mint and tried issuing the commands using sudo, to no avail. USB debugging is enabled in LOS, along with Rooted debugging (located under USB debugging) in Dev options. ADB was also enabled in Recovery in the step prior.

One thing I noticed when I rebooted to Bootloader was seeing 'kona' (not kebab) - which I think is the result of picking a rollback package from LuK's reply in post #320, found here: https://xdaforums.com/t/rom-official-kebab-12-lineageos-19.4484387/page-16

I'm not sure what to do, so, any help would be welcome. Thank you.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] angus6969:
probably you downloaded some wrong file ,in my opinion at these points you can try the rollback which would save you half an hour compared to using the msm tool which you can still use as a last resort
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] LuK1337:
>but I kept getting an error because the option "--slot=all" isn't a valid option.

Maybe consider using newer fastboot...

>One thing I noticed when I rebooted to Bootloader was seeing 'kona' (not kebab)

It always said that.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] dangerousnerdrays:
That's an interesting thought. I'll look into it, but I only have the fastboot version available in my distro's repos.

Good to know.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] dangerousnerdrays:
I'm considering getting back to stock recovery and image, then proceeding with LOS20, but I'm not sure how to do that and some of the guides here are a little confusing.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] dangerousnerdrays:
How to I return to stock recovery and the latest stock OOS from LOS19.1? There are guides, but they are outdated.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] angus6969:
The safe method is msm tool, is very long but secure, it erase everything in your phone. After that you must unlock bootloader and upgrade step by step to last firmware... And at this point flash los20
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] card13:
@dangerousnerdrays Linux Mint is built on Ubuntu and the fastboot/adb in Ubuntu's Repos is old. I ended up having to manually copy files from platform-tools-latest-linux.zip to /usr/bin/, then reboot and that was all I had to do to update mine.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] LuK1337:
Unironically chatgpt has a better suggestion than this...
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] card13:
@LuK1337 I'm still using a script you helped me with awhile back :P But yes extracting it to a folder and then setting the $PATH is a good way too.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] JedidroidX:
I downloaded my fastboot adb drivers from here. Is there another website that may have the updated tool necessary anywhere? Thanks in advanced!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] angus6969:
Nobody else?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] M_Power01:
After installing the latest version of OOS13 F.15, I upgraded to LineageOS 20.

Perfect, no problem so far.

Everything is working (bluetooth,wifi...etc)

I noticed that the sound from the external speakers is low during a phone call compared to OOS, even when I turn it up to the maximum.

Is there a solution to increase the volume?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
What I'm seeing is as follows:

Still working, and no change from LOS 19.1

If I connect to a PC with USB debugging disabled and choose USB file sharing, MTP works as expected

If I connect to a PC with USB debugging enabled, the ADB interface works as expected

Change immediately after LOS 20.0 upgrade

If I connect to a PC with USB debugging enabled, and then switch on USB file sharing, the ADB interface still works as expected...but the MTP driver shows up with an exclamation mark in Device Manager and MTP does not function whatsoever. If I leave it connected and then just disable USB debugging, MTP begins functioning as expected. - This is new behavior and it started immediately after installing LOS 20.0

Notes: I did have to install ADB drivers after upgrading to LOS 20.0 as the PCs saw the device as something new. I've tried multiple PCs, all running Windows 11, and they all behave in exactly the same manner. I've changed nothing about the PC's configuration wise.

EDIT: After the latest LOS 20.0 update, I am no longer experiencing anything out of the ordinary with MTP/ADB.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
I actually had multiple Bluetooth issues with 19.1 which all appeared to be solved with 20.0 and/or the latest firmware.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] hhllss:
I had this problem but on LOS18.1 just the day before I was planning to upgrade to 19.1 and then 20. Nothing fixed it until I flashed the oos firmware (upgrading at the same time to LOS19.1 but that was not a clean flash). I did not have any problem so far. At that time, I did not take logs so it is hard to explain the problem now...

In fact, that problem was the start of my question about flashing new oos drivers version (f15 now, but I am using f13) when they are out.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] jfromeo:
Any else with the Orange State message on boot?

Orange state
your device is unlocked and can't be trusted
it will boot in 5 seconds (idk if it's write like this but it's)
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] hhllss:
I do, but nothing else than just the message. I was thinking that it was the new way to tell that the bootloader is unlocked. Does that mean anything else ?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] M_Power01:
Yes i have too
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] JedidroidX:
I second that, I notice the phone's sdcard does not appear as a partition in windows explorer as it did with Lineage 19.1.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] angus6969:
So i
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Daviteusz:
I'll just hint that you can flash abl.img from oos12 firmware

fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] hhllss:
What will be the result?
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] paul4762:
Has anyone be able to install the Pixel launcher? It installs but just crashes and won't let me go into anything. Tried a full wipe too.

Thanks!
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Daviteusz:
Check the message I am referring to and draw conclusions.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] PhantomApollyon:
Isn't there still more to it than simply flashing the legacy abl though, or is it that simple with this device? If I recall correctly, in the past there were other accompanying changes that you had to do in aggregate to eliminate that being displayed.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] hhllss:
Well, using your command will flash the original Bootloader from OOS12 on slot a and b, after having flash LOS20 (using OOS13 firmware). So I am just asking about the result since I am not sure. Will we have the "old" unlocked boot loader message, or no message at all, or anything else ? Sorry if I am missing something.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] Daviteusz:
@PhantomApollyon @hhllss In oos12 they removed the warning. A complete change of firmware. In oos13 beta there was no warning. In stable they added, but after flashing abl from oos13 beta or oos12 there is no warning.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] hhllss:
OK, I understand, thank you for clarifying this.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] jfromeo:
So abl.img just contains the boot warning image? I do not want to break anything by flashing a oos12 firmware module on a oos13 firmware-based custom rom.
[OnePlus 8T ROMs, Kernels, Recoveries, & Other Deve] dangerousnerdrays:
This worked like a charm.

Thank you!