[ROM][OFFICIAL][kebab][13] LineageOS 20

Search This thread
By:
Advanced…
PhantomApollyon

PhantomApollyon

Senior Member
Jul 11, 2007
634
134
KrazyKlutt said:
Really awesome to see such amazing development!



Some questions:



Do AoD / Ambient display have issues?



Is Fingerprint is slower than OOS?



Do Adaptive brightness have major issues so it's better not to use?
Click to expand...
Click to collapse
I don't use AoD so I can't speak to that one.

The fingerprint reader seems to work just fine vs. OOS, I don't notice any difference.

For stock adaptive brightness I would steer clear entirely as it's not even remotely close to OOS. If you read back in the thread you'll see a lot of conversation about it.
 
  • Like
Reactions: KrazyKlutt
G

gdfajkldfkwfj

Senior Member
Sep 28, 2008
98
9
Is there a working version of Google Camera for LOS 20? The one from Google play store keeps crashing, LOS's stock camera is lacking (can't select between multiple cameras, landscape photo saved as vertical, no panorama / photosphere)
 
Max-P

Max-P

Member
Dec 25, 2015
8
4
Montréal
KrazyKlutt said:
Really awesome to see such amazing development!

Some questions:

Do AoD / Ambient display have issues?

Is Fingerprint is slower than OOS?

Do Adaptive brightness have major issues so it's better not to use?
Click to expand...
Click to collapse
AoD works just fine, although it does need to be manually enabled and it's not easy to find in the settings. Fingerprint is about as responsive as stock. I don't use adaptive brightness but reports in this thread say it's pretty buggy anyway.

gdfajkldfkwfj said:
Is there a working version of Google Camera for LOS 20? The one from Google play store keeps crashing, LOS's stock camera is lacking (can't select between multiple cameras, landscape photo saved as vertical, no panorama / photosphere)
Click to expand...
Click to collapse
Aperture (LineageOS' included camera app) does support switching cameras. It's the "0.6", "0.9" "1x" and "1" zoom options, which is separate from the software zoom control. Because that's what those cameras effectively are: 2 wide cameras, the regular one, and the macro one.

If you want GCam, you need Arnova's GCam from here with the matching profile: https://www.celsoazevedo.com/files/android/p/camera-unlocker-oneplus-8-9r/

No need for the Magisk module, LOS comes with the cameras unlocked.

GCam is still extremely buggy in my opinion, so I just use Aperture for most uses, unless I really want to make a 48MP picture or want the advanced processing.
 
  • Like
Reactions: dagustl and gdfajkldfkwfj
R

Recall0317

New member
Feb 7, 2023
3
0
Hi guys, first post on the forums!

I have LOS20 installed on my 8T and have been liking it, but I do have some problems. I am currently running the latest OS version (February 2nd) with stock LOS recovery and the devices is not rooted.

First is the automatic brightness which just does not work. I have Velis installed and it does not detect the brightness sensor. This is not a deal breaker for me, but somewhat annoying still.

The other one is the bigger problem, and new with the LOS20. The proximity sensor is not working at all. Velis reports it too as "not found" like the brightness sensor.

I've read through this topic and it seems that the auto brightness is a complicated issue but some of the users have a working proximity sensor. I too had it working with LOS19.1 with the same device. Is there any way to get the proximity sensor working without rooting the devices? I prefer not rooting my daily phone for app usability.
 
L

luspi

Member
Jul 28, 2017
19
4
Adaptive brightness is working pretty well for me on my 8T+. Using the app "Sensors Toolbox", it lists a light sensor by name "stk33502 wise Light Sensor Non-wakeup" and correctly lists the current lx value. For proximity it lists the "stk33502 Proximity Sensor Wakeup", however, it only two value options, 5cm or 0cm, although they at least show up as expected.

I also installed the Velis app, but this app is not able to detect any sensors, so it might be an issue with that particular app...?
 
R

Recall0317

New member
Feb 7, 2023
3
0
luspi said:
Adaptive brightness is working pretty well for me on my 8T+. Using the app "Sensors Toolbox", it lists a light sensor by name "stk33502 wise Light Sensor Non-wakeup" and correctly lists the current lx value. For proximity it lists the "stk33502 Proximity Sensor Wakeup", however, it only two value options, 5cm or 0cm, although they at least show up as expected.

I also installed the Velis app, but this app is not able to detect any sensors, so it might be an issue with that particular app...?
Click to expand...
Click to collapse

Said app doesn't show the sensor. Tried checking with AIDA64 and found some info.

Ambient light sensor is listed with name "tcs3408 Ambient light sensor rear Non-wakeup". That code tcs3408 is also tied to bunch of other sensors such as RGB Sensor, Flicker Sensor etc. Proximity sensor is not found at all. Also none of those tcs3408 show any data though, just the name.

Basically any sensor readings I get from AIDA are related to gyroscope and accelerometer. This seems a bit weird. Is there anything to be done?
 
L

luspi

Member
Jul 28, 2017
19
4
Recall0317 said:
Said app doesn't show the sensor. Tried checking with AIDA64 and found some info.

Ambient light sensor is listed with name "tcs3408 Ambient light sensor rear Non-wakeup". That code tcs3408 is also tied to bunch of other sensors such as RGB Sensor, Flicker Sensor etc. Proximity sensor is not found at all. Also none of those tcs3408 show any data though, just the name.

Basically any sensor readings I get from AIDA are related to gyroscope and accelerometer. This seems a bit weird. Is there anything to be done?
Click to expand...
Click to collapse

Hm, it looks like we have two different sensors... that probably explains why they work for some but not others.
 
J

JedidroidX

Senior Member
Jan 30, 2015
181
67
Been using Lineage for about 5 days on my Oneplus 8T TMO variant. My current network is Verizon.
It seems I stop receiving text after some time and the only way to receive text is by either rebooting the device or enabling and disabling airplane mode. Sending text always works, is there a fix for this or perhaps maybe using a different sms app would resolve the issue.... (SIgnal)
 
G

gdfajkldfkwfj

Senior Member
Sep 28, 2008
98
9
bluetooth audio in Google Voice stopped working in latest LOS build, same issue as OOS

How can I revert back to KB2007's official rom and re-lock bootloader?
 
Last edited:
S

silverhazesupreme

Member
Oct 13, 2022
19
14
Been itching to get off stock OxygenOS and give LineageOS another try. I want to use gapps but the bare minimum and I found that NikGapps has a core package that has less Google bloat than MindTheGapps. Has anyone tried it on Android 13? Will it work?
 
T

thefanum

Senior Member
Dec 27, 2011
196
70
Samsung Galaxy Tab S2
OnePlus 3T
JedidroidX said:
Been using Lineage for about 5 days on my Oneplus 8T TMO variant. My current network is Verizon.
It seems I stop receiving text after some time and the only way to receive text is by either rebooting the device or enabling and disabling airplane mode. Sending text always works, is there a fix for this or perhaps maybe using a different sms app would resolve the issue.... (SIgnal)
Click to expand...
Click to collapse
Have you tried Google messages?
 
jabashque

jabashque

Senior Member
Feb 17, 2017
240
241
Nextbit Robin
LeEco Le Pro3
Recall0317 said:
Hi guys, first post on the forums!

I have LOS20 installed on my 8T and have been liking it, but I do have some problems. I am currently running the latest OS version (February 2nd) with stock LOS recovery and the devices is not rooted.

First is the automatic brightness which just does not work. I have Velis installed and it does not detect the brightness sensor. This is not a deal breaker for me, but somewhat annoying still.

The other one is the bigger problem, and new with the LOS20. The proximity sensor is not working at all. Velis reports it too as "not found" like the brightness sensor.

I've read through this topic and it seems that the auto brightness is a complicated issue but some of the users have a working proximity sensor. I too had it working with LOS19.1 with the same device. Is there any way to get the proximity sensor working without rooting the devices? I prefer not rooting my daily phone for app usability.
Click to expand...
Click to collapse
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.
 
exthomeboy

exthomeboy

Senior Member
Apr 13, 2015
133
48
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?
 
K

KrazyKlutt

Senior Member
Jul 30, 2014
144
24
exthomeboy said:
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?
Click to expand...
Click to collapse
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
 
  • Like
Reactions: thefanum and exthomeboy
You must log in or register to reply here.

Similar threads

LuK1337
[ROM][OFFICIAL][kebab][11] LineageOS 18.1
Replies
1K
Views
193K
T
thefanum
firebird11
ROM[OFFICIAL][kebab][11.0]**crDroid**[V7.14]
Replies
583
Views
91K
3MrBojangles3
3MrBojangles3
theincognito
  • Locked
[CLOSED] [No longer maintained] [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project (8T / Kebab) (2022-03-09)
Replies
566
Views
107K
shadowstep
shadowstep
chandu dyavanapelli
[ROM][OFFICIAL][OOS CAM][OnePlus 8T/9R][12.1.0_r11]Nameless AOSP[2022/07/23]
Replies
1K
Views
151K
7
706mix
rounak1619
[ROM][12.1][kebab/lemonades][OFFICIAL] Pixel Extended 4.5[19/05/2022]
Replies
273
Views
69K
micber67
micber67

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 2
    T
    thefanum
    tastysushixd said:
    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 🥰
    Click to expand...
    Click to collapse

    That's correct, custom firmware is absolutely not for beginners. And the posts clearly state that.
    View
    1
    21prods
    21prods
    uaiclout said:
    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.
    Click to expand...
    Click to collapse

    uaiclout said:
    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.
    Click to expand...
    Click to collapse
    Strange behaviour... I use USB type c headphones and they work very well, I have never suffered anything similar to that.
    View
    1
    T
    thefanum
    uaiclout said:
    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)
    Click to expand...
    Click to collapse
    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 play.google.com
    View
    1
    T
    thefanum
    tastysushixd said:
    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
    Click to expand...
    Click to collapse
    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
    View
    1
    T
    thefanum
    SkogstaTarzan said:
    Just wanted to share my experience after a week as my daily driver.
    I should mention that I'm running this with with microG.
    Smooth rom and the most of the things is working fine.
    What I noticed is this:

    Screen brightness is no good, sucked the battery out of the phone in no time.
    This is despite having the stk33502 proximity sensor that is reported to be working.
    Velis auto brightness solves this though.
    One little thing is that all the permissions is revoked after a reboot, which makes me do the set up all over again, any ideas?

    Another source of battery drain is notifications, since I don't use google services.
    I haven't enabled cloud messaging (push notifications) in microG settings but is this drain normal?
    Seems a bit high I think.
    This is the f-droid version of element.
    I'm thinking of maybe flashing another kernel with battery optimisation or maybe that won't help?

    Another thing is that file transfer via USB can be a bit finicky, there's a temporary solution somewhere in the thread.

    View attachment 5874105
    Click to expand...
    Click to collapse

    Do you have root? I'm not having that issue with velies, but I'm rooted. Wondering if that's the difference.

    Regardless, the first step of troubleshooting is to just uninstall velis, and reinstall. Sometimes that's all it takes to fix autoboot issues. And make sure it starts automatically, and with it's configuration. Otherwise something is wrong with the app.

    For the notifications battery drain, you can check the offending app's settings, and see if you can set notification intervals manually. Set it to 15-30 min. Or enable "cloud messaging" in microg, and rule that out. Or, just use Nano Gapps. Not the answer you're looking for, I know, but it is an answer. Nano if you want Google assistant, Pico if you don't care about Google assistant, and want the minimal Google in your phone.

    Also, make sure you've checked settings> battery and figure out if it's an app or the OS itself that's draining battery, and report back. Once we know what the offenders are, we can help troubleshoot further.

    Anecdotally, I've had issues with microg every time I've tried to use it. And the trade offs were not worth it for me (I can't miss notifications, even occasionally, work wise). So unfortunately I don't have much feedback. I do know lots of people use it, so hypothetically it's possible to find a good balance. I've just never found it for me, personally.

    And MTP (the USB file transfer protocol) is so buggy it's unusable. And neither Google, nor Apple, seem to be doing anything about it. This is not just an Android issue, it also effects iPhones. And it's been in this semi broken state for years. So I wouldn't expect that to get fixed any time soon.

    I use Solid Explorer, and SFTP to transfer data, because all of my devices are Linux (and one Mac), and that's the protocol I use (SSH) everywhere else in my network for absolutely everything, not just file transfer. So it's nice to have Android fit right in to my existing configuration. macOS also supports SSH/SFTP, but if you're a Windows user, and don't have WSL2, Solid Explorer supports a TON of different protocols.

    You can use SMB (CIFS), FTP, and even WEBDAV.

    And if you want to connect to your Android from a computer, not the other way around, you can use solid explorer to set up an FTP server on your phone. I'm not affiliated with Solid Explorer, just a big fan of power user tools.
    View
  • 21
    LuK1337
    LuK1337
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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 :
    GPL compliance :
    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:
    View
    10
    LuK1337
    LuK1337
    ALGOPOP said:
    Where can i find the "latest Android 13 full stock ROM" for KB2003 as mentioned in the Instructions? On the Oneplus Site i only find a Android 11 ROM for download. I am on LOS 19.1 atm.

    Thanks...
    Click to expand...
    Click to collapse
    KB2001_11_F.13 - https://gauss-componentotacostmanua...22/11/15/71ff9f8989a040d58e73869a9e078c43.zip
    KB2003_11_F.13 - https://gauss-componentotacostmanua...22/11/18/83d837a54bd647c3902634d271f6cc2d.zip
    KB2005_11_F.13 - https://android.googleapis.com/packages/ota-api/package/e61f1cf7c6a55e531113091deadfb7acb96901da.zip
    View
    5
    PhantomApollyon
    PhantomApollyon
    netusername said:
    Does this rom have full support for dual SIM AKA enabling and disabling SIMs on the go. The previous version did not have that.

    Also, does auto brightness work as expected on KB2005?


    Thanks in advance.
    Click to expand...
    Click to collapse
    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...
    gitlab.com 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.
    View
    5
    LuK1337
    LuK1337
    nico2195x said:
    Do you also have these links for F.15?
    Click to expand...
    Click to collapse
    KB2003 - https://gauss-componentotacostmanua...22/12/06/8bf764b7dbac43408244e167c64d6226.zip
    View
    4
    CDI-78
    CDI-78
    erictmc said:
    Anyone know where to download just the firmware for Android 13 for 8T KB2003? Don't feel like downloading the full ROM (over 4GB). Thanks in advance.
    Click to expand...
    Click to collapse
    Hi,
    Take a look here,

    MediaFire

    MediaFire is a simple to use free service that...
    www.mediafire.com www.mediafire.com
    View

New posts