[ROM][OFFICIAL][kebab][12] LineageOS 19

Search This thread

bikeaholics

Senior Member
Apr 14, 2011
158
10
Maybe I am allowed to ask it one more time. Where can I find the faceunlock or what is needed to do so?
Maybe someone would be so nice to tell me.

Thanks in advance
 

PhantomApollyon

Senior Member
Jul 11, 2007
633
130
I installed this ROM on my KB2005. A couple of issues that made me go back to stock -

- autobrightness doesn't work correctly even after you adjust adaptive brightness. It always brightens to close to max after unlocking.

- if you use two SIMs and then temporarily disable one of them, you can't get that SIM back as the setting disappears completely.
I can confirm that adaptive brightness is also pretty wonky for me on the KB2005. It seems to consistently jump to 80% way more that I'd like it to.

Another thing I've noticed that didn't happen on the stock ROM is that sometimes when shutting off a Bluetooth device while the phone is locked with the screen off and audio playing, playback doesn't pause in various apps regardless of how it's set and it just starts playing through the phone speaker. (Not a big deal by any stretch but notable)
 

M_Power01

Member
Aug 25, 2022
18
4
France
This ROM is great !
It's smooth and I encountered almost no bugs.
Great work !
The battery consumption is very good, unlike Nameless which has a very high consumption. I'm going to stay on this ROM for a while .
 

Lomobasd

Member
Apr 12, 2021
10
1
I am really happy with this rom, everything is working grate except for one Problem.
My always on screen / ambient Display always goes to min brightness after a few seconds. Which makes it completely unusable when your not in a pitch black room.

Dose anybody have the same Problem? And is there a config file somewhere i could adjust the always on brightness in?

PS: adaptive brightness is also broken for me but it doesn't bother me because i am not using it
 

Lomobasd

Member
Apr 12, 2021
10
1
I got the 20221021-build, mine is older than yours. how did you find it?
yes i also got 20221021-build microg build but what i am saying is that i also tested the official 20221103-nightly before without microg which has the same problem.

But to come back to my original question do you also have the problem with the always on screen being ridiculously low?
 

deletriusster

New member
Nov 26, 2022
4
1
yes i also got 20221021-build microg build but what i am saying is that i also tested the official 20221103-nightly before without microg which has the same problem.

But to come back to my original question do you also have the problem with the always on screen being ridiculously low?
No, when I installed it and
yes i also got 20221021-build microg build but what i am saying is that i also tested the official 20221103-nightly before without microg which has the same problem.

But to come back to my original question do you also have the problem with the always on screen being ridiculously low?
Yeah, I got the same problem.
 

PhantomApollyon

Senior Member
Jul 11, 2007
633
130
@LuK1337 - I'm not sure if this is a bug or a behavioral issue, but this is about adaptive brightness.

Description: On a fully stock KB2005 device with OOS 12, adaptive brightness does exactly what you'd expect it would do, pretty much like every device/OS I've used. On LOS, adaptive brightness's default behavior is typically FAR brighter than you'd ever really want it to be in most circumstances, most of the time jumping up to ~80% if there's any notable light detected by the sensor. Toggling "extra dim" in accessibility features helps lower the ceiling, so to speak, but the unpredictable behavior of the luminance values at a certain light sensor reading remain. Would it be possible for this behavior to match the stock OOS 12/13 behavior vs. whatever it is doing now? If you need extra detail feel free to reach out and I'm happy to help. It didn't seem to me that logs would do anything with this behavior since I presume the settings are hard-coded, but am happy to take them in the device's current state if that helps.

LineageOS version: lineage-19.1-20221124-nightly
LineageOS Download url: https://mirrorbits.lineageos.org/full/kebab/20221124/lineage-19.1-20221124-nightly-kebab-signed.zip
Gapps version: N/A - behavior/ problem exists without Gapps being loaded at all - though I am using the latest mindthegapps package
wiped: Yes - initially to validate
restored with titanium backup: No
rebooted after having the issue: Yes- Many times
task killer: No
non-stock kernel: No
other modifications: N/A - I validated this occurs before doing any modifications, even Gapps, although I'm currently using Magisk and the patched boot image

Report on Gitlab: https://gitlab.com/LineageOS/issues/android/-/issues/5319
 
Last edited:
  • Like
Reactions: Quirken and LuccoJ

PhantomApollyon

Senior Member
Jul 11, 2007
633
130
Does anyone here know if there is a way to get bug reports to the dev? I submitted the previous post for adaptive brightness here and just a few days ago now on Gitlab but there doesn't seem to be a response in either place.
 

Quirken

Member
Feb 16, 2012
11
1
I'm having a weird intermittent issue with bluetooth - it pairs just fine, but sometimes, it seems to forget to mute the phone's speaker. This results in a weird echo that is very off-putting and distracting.

I have a KB2007. The issue has been present on every nightly build I've tried over the past 2 months ago.

It doesn't happen every time, though. Sometimes I can connect, start music without an issue, pause music, and resume music, and suddenly I have sound coming out of two places.

What is your--
LineageOS version: 19-20221208-NIGHTLY-kebab
LineageOS Download url: https://download.lineageos.org/kebab
Gapps version: MindTheGapps-12.1.0-arm64-20220605_112439

Did you--
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes. sometimes rebooting will help, sometimes even after rebooting several times it persists

Are you using--
a task killer: no
a non-stock kernel: no
other modifications: no

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
This seems to be worse on some bluetooth devices than others. My car's stereo system (which is a bit on the older side but has never had an issue with other devices) seems to trigger the issue the most often. I've also had this happen on brand new modern bluetooth headphones, though. I've tried fiddling with the bluetooth options under developer options, and none of them seem to have made a difference.
This seems to be present in all LineageOS nightly builds for at least the past ~2 months since I switched to LOS.
Weirdest part is nobody else seems to have mentioned this issue in this thread. Might be something related to the KB2007 model, since the T-Mobile variant is less common?
Today, a slight variant of this issue occurred... I was using bluetooth headphones, paused music for ~10 minutes, then when I resumed (via headset button)... music was only coming out of the phone speaker, not out of both phone speaker and bluetooth. This persisted after restarting my headphones.
 
Last edited:

PhantomApollyon

Senior Member
Jul 11, 2007
633
130
I'm having a weird intermittent issue with bluetooth - it pairs just fine, but sometimes, it seems to forget to mute the phone's speaker. This results in a weird echo that is very off-putting and distracting.

I have a KB2007. The issue has been present on every nightly build I've tried over the past 2 months ago.

It doesn't happen every time, though. Sometimes I can connect, start music without an issue, pause music, and resume music, and suddenly I have sound coming out of two places.

What is your--
LineageOS version: 19-20221208-NIGHTLY-kebab
LineageOS Download url: https://download.lineageos.org/kebab
Gapps version: MindTheGapps-12.1.0-arm64-20220605_112439

Did you--
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes. sometimes rebooting will help, sometimes even after rebooting several times it persists

Are you using--
a task killer: no
a non-stock kernel: no
other modifications: no

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
This seems to be worse on some bluetooth devices than others. My car's stereo system (which is a bit on the older side but has never had an issue with other devices) seems to trigger the issue the most often. I've also had this happen on brand new modern bluetooth headphones, though. I've tried fiddling with the bluetooth options under developer options, and none of them seem to have made a difference.
This seems to be present in all LineageOS nightly builds for at least the past ~2 months since I switched to LOS.
Weirdest part is nobody else seems to have mentioned this issue in this thread. Might be something related to the KB2007 model, since the T-Mobile variant is less common?
Today, a slight variant of this issue occurred... I was using bluetooth headphones, paused music for ~10 minutes, then when I resumed (via headset button)... music was only coming out of the phone speaker, not out of both phone speaker and bluetooth. This persisted after restarting my headphones.
While I've not noticed this behavior specifically, what I am noticing is very inconsistent connections with somewhat older Bluetooth devices, and even very specifically car stereos as you mentioned. What I'm seeing is an initial connection that seems fine for 60-90s, and then a hard disconnect wherein the headunit loses connection entirely. It will eventually re-connect itself and be fine again after a few cycles of that behavior. There also seems to be no rhyme/reason to how many times it'll happen. Sometimes it's just once and it's simple enough to overlook, but sometimes it'll happen for 10-15mins before whatever is happening clears up. Next time I have an opportunity to catch it happening and grab logs I plan to submit a bug report for this, though I'm not sure if there's really active support/maintenance here at this point.
 
Last edited:
Nov 9, 2021
23
1
I'm gearing up to make the move to LOS. Right now, I'm just reading through the wiki and gathering files I'll need. I have just one questions (for now). Thanks in advance for any help.

I'm currently on KB2005 [US/North America], running Android 11 (Build #: OOS 11.0.13.13.KB205AA) with Magisk root.

An OTA update is available, but it's Android 13 (KB2005_11.F.13_2130_202211142345). The software update available on OnePlus' support site is 11.0.13.13.KB05AA - which is 11.. Looks like I missed Android 12 completely.

Luckily, I found this XDA post and want to confirm that OxygenOS 12.1 (c.17) for kebab is going to meet installation requirements for LOS. Specifically, I'm wondering if the linked zip file is what I want, considering it has 'downgrade' in the file name. https://oxygenos.oneplus.net/OnePlus8TOxygen_15.O.29_OTA_0290_all_2110091944_downgrade.zip
 
Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,799
17,746
Samsung Galaxy S III I9300
Moto G 2014
I'm gearing up to make the move to LOS. Right now, I'm just reading through the wiki and gathering files I'll need. I have just one questions (for now). Thanks in advance for any help.

I'm currently on KB2005 [US/North America], running Android 11 (Build #: OOS 11.0.13.13.KB205AA) with Magisk root.

An OTA update is available, but it's Android 13 (KB2005_11.F.13_2130_202211142345). The software update available on OnePlus' support site is 11.0.13.13.KB05AA - which is 11.. Looks like I missed Android 12 completely.

Luckily, I found this XDA post and want to confirm that OxygenOS 12.1 (c.17) for kebab is going to meet installation requirements for LOS. Specifically, I'm wondering if the linked zip file is what I want, considering it has 'downgrade' in the file name. https://oxygenos.oneplus.net/OnePlus8TOxygen_15.O.29_OTA_0290_all_2110091944_downgrade.zip
Pick a rollback package from https://community.oneplus.com/thread/1200192365487718402
 

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    15
    Sry am now on Android 13 Evolution X 😎
    don't care didn't ask
    5
    Thread lightly cleaned.

    A friendly reminder to all. Please keep argumentative discussions relegated to PM's when possible out of respect for the Developer. Thank you.

    -Regards: Badger50
    4
    At this point you are just brainless. Period.
    Sometimes people just make silly mistakes / assumptions like one here https://forum.xda-developers.com/t/rom-official-kebab-12-lineageos-19.4484387/post-87374925 :)
    4
    Thank you for making this. Lineageos's been a blessing ever since the oxygenos became what it is now.

    I want to migrate from another rom and wanted to ask if lineageos 19 uses oos12 or oos11 firmware.
    I believe you can find the answer for that in the installation instructions.