[ROM][OFFICIAL][kebab][11] LineageOS 18.1

Search This thread

21prods

Senior Member
Sep 2, 2013
71
20
Thank you for all your hard work.

I have recently bought a Oneplus 8T (KB2003) and have installed LOS 18.1 on it. I have even managed to modify the modem settings in order to enable 5G (both SA and NSA) following a guide to do so (the guide is for the OOS, but I found a way to enable the use of QPST thanks to adb commands so I could follow it). Though, I don't get 5G connection even if I think I should.

Just a couple of quick questions, has anyone got 5G connection on LOS 18.1 with this model? Or AOSP is missing something and it is just not possible at the moment? In case it is possible, could someone shed some light as to what I could be missing?

Thank you very much
 

LuccoJ

Senior Member
Aug 6, 2010
80
48
I'm considering getting an 8T, but after reading this thread, I'm unclear on whether I'll be able to use
  • the main camera at the native 48mp, to zoom into it and simulate telephoto
  • the other secondary cameras, especially the wideangle ones
without resorting to some hacked GCam. In fact, I'd like to use Open Camera, which someone recommended in the thread but without really specifying whether it gets full access to the camera. Otherwise, does the default LineageOS camera have this access? Or are the Oneplus drivers/APIs still "secret" like https://www.celsoazevedo.com/files/android/google-camera/f/post-05/ alleges?
 

21prods

Senior Member
Sep 2, 2013
71
20
Thank you for all your hard work.

I have recently bought a Oneplus 8T (KB2003) and have installed LOS 18.1 on it. I have even managed to modify the modem settings in order to enable 5G (both SA and NSA) following a guide to do so (the guide is for the OOS, but I found a way to enable the use of QPST thanks to adb commands so I could follow it). Though, I don't get 5G connection even if I think I should.

Just a couple of quick questions, has anyone got 5G connection on LOS 18.1 with this model? Or AOSP is missing something and it is just not possible at the moment? In case it is possible, could someone shed some light as to what I could be missing?

Thank you very much
I reply to myself. Yes, I missed something, it is necessary to have a SIM card inserted in the phone BEFORE modifying the modern settings. Now it works.
 

the00guy

Senior Member
Jul 14, 2010
226
32
Has anyone with the unlocked 8T and the latest lineage noticed visual voicemail not working with T-Mobile? I haven't seen any other posts about it but VVM won't activate for me.

I'm on basically a clean install having followed the instructions after installing the latest OOS for the vendor firmware out of the box. Only modification is magisk/lsposed. Thanks all
 

derekn13

Member
Jun 26, 2014
10
10
Has anyone with the unlocked 8T and the latest lineage noticed visual voicemail not working with T-Mobile? I haven't seen any other posts about it but VVM won't activate for me.

I have the same problem. I upgraded from a 6T (running an older version of LineageOS) to an 8T (LineageOS with the latest updates + Magisk), and I haven't been able to get VVM working on the 8T. I don't get much voicemail, so I've just been ignoring the problem, but it would be nice to have it back.
 
  • Like
Reactions: the00guy

Hellskull

Member
Sep 19, 2019
18
3
Hi guys,
I'm newbie here with stock rom - kb2000. My device got battery standby drain so fast. As i see in oos they have lots of feature require background service.
I lost about 15% every morning when i waked up :(
Will this rom improve my battery life? Any1 long used here can tell me your sot time and stand by % after wake up?
 
I don't understand the Wiki maybe it's been so long since I flashed a custom rom. But t also says to us a recovery other than TWRP which confuses me.
I am coming from stock the Wiki mentions flashing copy-partitions-20210323_1922.zip using some other recovery I don't know and then later about flipping sides. Can someone please help me I just want TWRP with lineageos and magisk to root.
 

the00guy

Senior Member
Jul 14, 2010
226
32
I have the same problem. I upgraded from a 6T (running an older version of LineageOS) to an 8T (LineageOS with the latest updates + Magisk), and I haven't been able to get VVM working on the 8T. I don't get much voicemail, so I've just been ignoring the problem, but it would be nice to have it back.
Thanks for confirming. It seems like the last update broke all haptic feedback as well now.
 

BillGoss

Senior Member
Sep 2, 2010
5,156
4,524
Sydney
OnePlus 3T
I don't understand the Wiki maybe it's been so long since I flashed a custom rom. But t also says to us a recovery other than TWRP which confuses me.
I am coming from stock the Wiki mentions flashing copy-partitions-20210323_1922.zip using some other recovery I don't know and then later about flipping sides. Can someone please help me I just want TWRP with lineageos and magisk to root.
A lot of rom documentation was written before we had a working TWRP (only became available in late August of this year). That's why there no mention of TWRP.

The 8T TWRP thread has documentation on installing custom ROMs, coming from OOS.

And read this post which explains why you need copy-partition and other important stuff: https://forum.xda-developers.com/t/...ebab-2021-29-11.4302449/page-18#post-85910241
 

Daisuke1988

Senior Member
Sep 16, 2012
143
52
I'm considering getting an 8T, but after reading this thread, I'm unclear on whether I'll be able to use
  • the main camera at the native 48mp, to zoom into it and simulate telephoto
  • the other secondary cameras, especially the wideangle ones
without resorting to some hacked GCam. In fact, I'd like to use Open Camera, which someone recommended in the thread but without really specifying whether it gets full access to the camera. Otherwise, does the default LineageOS camera have this access? Or are the Oneplus drivers/APIs still "secret" like https://www.celsoazevedo.com/files/android/google-camera/f/post-05/ alleges?
Yeah, so pretty much on LinOS the cameras cant be fully accessed. It really sucks because although I like the stock rom, i rather use LinOS. However, I use Filmic Pro a lot and the app wont fully open on LinOS, it immediately crashes. With Open Camera, it works but cant access all of the cameras. Pretty lame
 

LuccoJ

Senior Member
Aug 6, 2010
80
48
Yeah, so pretty much on LinOS the cameras cant be fully accessed. It really sucks because although I like the stock rom, i rather use LinOS. However, I use Filmic Pro a lot and the app wont fully open on LinOS, it immediately crashes. With Open Camera, it works but cant access all of the cameras. Pretty lame
I see. Unfortunately I was misled when I asked this question also on Reddit before buying the phone, by someone who later turned out to actually own an 8 Pro, not an 8T, who said the main camera would be locked down to 12mp, but that you could access the other cameras. I bought it based on that answer, but maybe that's true for the 8 Pro, definitely not usefully true for the 8T at this time. They also said even at 48mp, there really wasn't more detail than at 12mp, which I found perplexing at least for daytime pictures, but I thought, what do I know, they have the phone, and I don't...

I normally wouldn't even consider using the OEM OS, as all my phones have used LineageOS for many years, but the camera as available in LineageOS seems to be really quite bad. Even if I accept the other cameras just aren't available, the main one at 12mp looks much worse than I'd expect from 48mp binned down to 12. Quite unfortunate that a "modding friendly" brand like Oneplus would lock things down like this.

Interestingly, in OxygenOS, Open Camera could at least access the wide-angle camera (though it would apply no geometric corrections resulting in strong distortion), but now in LineageOS, Open Camera simply doesn't offer any cameras except the main back and front. I can access the wide-angle (but not any of the others) from GCam or FreeDCam, but it's underwhelming.
 

the00guy

Senior Member
Jul 14, 2010
226
32
Do you mean the keyboard and button "clicks"? I'm on the 20211125 version, and that feedback is working fine for me.
Earlier it seemed that none of the haptic feedback in general (ui clicking as well as keyboard) was working. It may have been that I simply didn't feel the ui clicks, but they seem to be working now (though still very gentle and hardly noticeable). The keyboard haptic were disabled, I enabled that and that's now working as well.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,571
17,176
Samsung Galaxy S III I9300
Moto G 2014
I see. Unfortunately I was misled when I asked this question also on Reddit before buying the phone, by someone who later turned out to actually own an 8 Pro, not an 8T, who said the main camera would be locked down to 12mp, but that you could access the other cameras. I bought it based on that answer, but maybe that's true for the 8 Pro, definitely not usefully true for the 8T at this time. They also said even at 48mp, there really wasn't more detail than at 12mp, which I found perplexing at least for daytime pictures, but I thought, what do I know, they have the phone, and I don't...

I normally wouldn't even consider using the OEM OS, as all my phones have used LineageOS for many years, but the camera as available in LineageOS seems to be really quite bad. Even if I accept the other cameras just aren't available, the main one at 12mp looks much worse than I'd expect from 48mp binned down to 12. Quite unfortunate that a "modding friendly" brand like Oneplus would lock things down like this.

Interestingly, in OxygenOS, Open Camera could at least access the wide-angle camera (though it would apply no geometric corrections resulting in strong distortion), but now in LineageOS, Open Camera simply doesn't offer any cameras except the main back and front. I can access the wide-angle (but not any of the others) from GCam or FreeDCam, but it's underwhelming.
FYI, aux cameras are locked out by `vendor.camera.aux.packagelist` property, you can unset it but don't cry if some app starts crashing after doing so. On stock, OnePlus hardcoded in frameworks/base/core/java/android/hardware/Camera.java a list of apps and how many cameras they can access, just because some apps would crash if they tried to switch past certain camera id.
And as for 48MP, you'd need some magic hacks in frameworks/av for that (and app that can use them), since it's not a real camera mode. Perhaps Android 12 (+OOS12 blobs) will finally let third party apps use that, see: https://developer.android.com/about/versions/12/features#camera-sensor-support
 
May 21, 2021
13
4
Planning on getting the KB2007 T-mobile version. going to use official LOS recovery, not planning on flashing magisk or rooting. Will be used in US on T-mobile network.

Is there anything else I should know? Do I need to flash the T-mobile modem to get 5G or anything?

Thanks.
 

Daystars

Member
Mar 4, 2011
25
6
Planning on getting the KB2007 T-mobile version. going to use official LOS recovery, not planning on flashing magisk or rooting. Will be used in US on T-mobile network.

Is there anything else I should know? Do I need to flash the T-mobile modem to get 5G or anything?

Thanks.
Everything works just fine with the T-Mobile version on Lineage, some of the issues with the T-Mo device still occur though, like the hand off between wifi-calling and cellular, other than that it is rock solid.
 

janmrog

Member
May 19, 2019
5
0
Hi, are there any known bugs, features missing in the rom? Also, can you go back to stock and retain l1 widevine?
 

RacketIDE

Member
Jun 24, 2012
22
6
Code:
C:\Windows\system32> adb reboot fastboot

C:\Windows\system32> fastboot devices
xxxxxxxx        fastboot

C:\Windows\system32> fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed


brand-new KB2003, updated on 11.0.11.11.KB05BA.
Clean windows 10 installation.
 

dpryor88

Senior Member
Nov 4, 2015
1,263
440
San Pedro
Google Pixel 3a
Google Pixel 4
Code:
C:\Windows\system32> adb reboot fastboot

C:\Windows\system32> fastboot devices
xxxxxxxx        fastboot

C:\Windows\system32> fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed


brand-new KB2003, updated on 11.0.11.11.KB05BA.
Clean windows 10 installation.
fastboot flashing unlock

This is command to unlock bootloader on OP8T
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    tomorrow afternoon 3 p.m 😆
    More like few weeks after OOS12 kernel source is out.
    4
    Yea this is interesting. Maybe we can try to pinpoint things we have in common. What is your 8T device model, firmware model and version, etc? I downgraded my YouTube version to the last v16 version and it seems to have helped somewhat, although it's not completely gone (and this could be placebo effect, I'm not sure).

    I tried rewinding and replaying the video/audio when these drops/boosts occur, and it seems like it is occurring with the same pattern each listen, so I don't think this is some semi-random effect of another installed app interfering with the audio.
    I'm currently on a KB2000 on 11.0.13.13.KB05AA, but I wouldn't pay too much attention to that since this has been an issue for me since this ROM was first released. I've been back to it 3 times in the hope the issue was magically fixed, but alas no. So long story short, it's not firmware specific.

    It's also not Youtube specific for me, so I'm convinced you're right about the placebo effect. If I download a video from Youtube (using an external program) I experience the exact same issue when playing that video in VLC (or MXPlayer) and for me that points to something in the audio signal path. It's definitely something related to either auto-volume leveling or audio compression. Something designed to prevent sudden loud noises that's overcompensating.

    But yeah, it is really annoying and a dealbreaker for me. It's such a hassle to return to stock that I'm not going down the road of installing this again. Just wanted to add a +1 to your comment in the hope it helped it get noticed.

    Don't try Lineage Microg or CalyxOS builds either in the hope it'll be better-- They have the exact same issue. Just giving you a heads-up there.
    i had the same problem. I read somewhere that Dynamic Range Control could couse these issues and confirmed that it was active on the build for oneplus 8t. After i flashed this : https://github.com/Magisk-Modules-Alt-Repo/drc-remover which set drc to disabled, my issues with speaker volume is gone!
    4
    Are you saying some (or all?) OOS12 firmware image files can still be used to be applied as upgrade? That would be great (but perhaps needs some documentation).
    I don't think you really understand what you're talking about...
    3
    I had not checked layout but obviously the block devices are the ones to upgrade and I see, for example, imagefv.img 11.0.13.13.KB05BA has size 20480 and imagefv.img KB2003_11.C.16 has size 1191936 so I am hesitant to fastboot flash a bigger one ...
    Let's just defer that discussion until builds that require Android 12 firmware are out, otherwise you'll just hurt yourself.
    3
    @LuK1337 : I wonder : OOS 12 changed partition layout ... is LOS for 1+8T going to do so as well? I ask because 1+8T has some bright years and upgrades to come, so I wonder how LOS will keep up to date with specific OOS firmware partitions. Thanks for your amazing work.
    GPT is still the same and super partition layout doesn't matter.
  • 44
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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 /proc/last_kmsg. (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:
    10
    tomorrow afternoon 3 p.m 😆
    More like few weeks after OOS12 kernel source is out.
    10
    Yaay. The thread is back. :D
    5
    How do you do backups? What would be a good way to keep backups if I wanted to flash this ROM on a semi daily basis? I noticed after flashing the ROM it asks if I want to restore from a backup.

    Another observation as I flashed the GMS version last night is there was no gallery app. Maybe this is normal.

    I would suggest Swift Backup. Was a titanium user, but I find Swift Backup to be better performing on Android 11.
    4
    You could try to run fastboot --version and ./fastboot --version in your platform-tools directory and compare the output.

    Adding ./ did it. Thanks! :cool:

    IMG_20210228_102128.jpg