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

[21prods]

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]

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]

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]

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]

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.

 

[Hellskull]

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?

 

[GraphMatix]

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]

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]

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]

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]

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.

 

[derekn13]

Thanks for confirming. It seems like the last update broke all haptic feedback as well now.

Do you mean the keyboard and button "clicks"? I'm on the 20211125 version, and that feedback is working fine for me.

 

[the00guy]

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]

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

 

[captain_nemodroid]

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]

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]

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

 

[RacketIDE]

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]

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

 

[GraveDigger176]

fastboot flashing unlock

This is command to unlock bootloader on OP8T

I use always fastboot oem unlock never had any issues with the command.
Maybe he should use adb reboot bootloader instead of reboot fastboot