yashsingh1/xdaforums huggingface dataset:
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
What is your--

LineageOS version: 20-20230309 custom build but it shouldnt be a issue

LineageOS Download url: I rather not

Gapps version: No Gapps installed, only minor apps like Gboard and Messenger.

Did you--

wipe: no

restore with titanium backup: no

reboot after having the issue: yes

Are you using--

a task killer: no

a non-stock kernel: no but I down-clocked the cpu to regular 855 levels

other modifications: magisk, root, microG

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

I updated the vendor firmware then sideloaded 19.1 and then right after LOS20. I kept all files and backups from Android 11.

Bugs I noticed is that ReadingMode/monochrome doesn't work with lock screen.

IMS is bananas as WiFi-Calling isn't prioritized even with airplane mode enabled. On 18.1, VoWIFI was persistant even with Wifi enabled, IMS service or telephony still priorities VoLTE.

weird media trans-coder where re-added with the update from 18.1->OOS bin update ->19.1 -> 20 yet no EVS trans-coder for VoLTE. Left is 18.1, right is 20. Av1 decoder was added.

Annoying UI bug, the name in the lock-screen is under the fingerprint scanner icon. Pls move it up, see example.

Battery has the wrong powerprofile, kernel says 3588mah, phone charges up above 4000mah. I added a example.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] nagarajsherigar:
hi everyone

i installed LOS 20 on oneplus 7t last weekend

Some of my apps are not working because of safetyNet

solution i found was to install magisk

can some one guide me how to do it?

thanks in advance
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] sdor4ever:
here you go

Pass SafetyNet on Rooted Android 12/13/14

In this comprehensive tutorial, we will show you detailed steps to pass the SafetyNet Test on your rooted Android 12/13/14 device.

www.droidwin.com
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
Is it still common that Wireguard doesn't work on Android 13? Or do I need to refresh the token for the VPN?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] mikefnz:
Perhaps Tasker could be set to automatically push volume back up?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
ehhhhh dumb question but this device kernel 4.14 EOL date is January 2024 , so after that date it over for support? Is there any active thirdparty porject trying to port newer kernel version to the Snapdragon 855?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] orangepowerpokes:
Today I got a new battery, replaced the broken back glass, and upgraded to LOS 20 from 18! It's like a brand new phone, so happy!! Thank you once again LuK1337 and the LOS team.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Rowethren:
Updated to the latest Nightly and have come across a bug so here is my report:

Model: HD1901

LineageOS version: 20-20230312-NIGHTLY-hotdogb

LineageOS Download url: https://mirrorbits.lineageos.org/fu...eage-20.0-20230312-nightly-hotdogb-signed.zip

Gapps version: MindTheGapps-13.0.0-arm64-20221025_100653

Did you--

wipe: No

restore with titanium backup: No

reboot after having the issue: Yes

Are you using--

a task killer: No

a non-stock kernel: No

other modifications: Magisk, GCam, Viper4Android.

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

The green location pop up in the status bar is constantly visible regardless of whether any apps are accessing your location. This issue only started in the latest nightly updated and didn't happen in lineage-20.0-20230305-nightly-hotdogb. I have tried to change the status bar location indicator off in the developer settings but it didn't make a difference. The only fix I have found is using a Magisk module that runs the below command blocking the popup:

cmd device_config put privacy location_indicators_enabled false default
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] oggly.:
There is problem with addin finger print. It's saying "Fingerprint setup timed out" but older fingerprints working on lockscreen etc.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
I deleted my old fingerprint before sideloading 19 and 20. It could be a AWOL variable but always go with a new fingerprint.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] dor_pauli:
I updated lineageos from 19 to 20 with a clean install in January (wiped everything). I used the provided instructions back then.

There where no part that told me to flash additional partition.

So i think the device don't have

dtbo.img

vbmeta.img

But the phone got no problems (updates to the latest version worked flawlessly) and is great.

Could it be, that I will get problems in the future with updates? What is the case of those two images? They appeared in the new version and there are not many info about them in the instructions...

Thanks.

Edit: I noticed, that I cannot boot into recovery with pressing Volume down + power button. If I do so, I enter fastboot mode and then I can change to recovery.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Slappy123:
Hello everyone, many thanks to begin with for porting this device !

I’m currently using a 7T on LOS 18.1 and bought a second one I wanted to flash on LOS 20 since it reached EOL.

Unfortunately I’m facing an issue I cannot fix myself, after multiple days of researches and tries.

The phone works perfectly fine on OxygenOS 10 and OOS 11 but doesn’t seem to boot, whatever I’m trying to flash on it.

There are similiar topic talking about this issue, without finding any fix.

Reddit and OnePlusCommunity repporting devices in Bootloop after OOS 12 official update. (issue I’m confronted to as well) :

https://community.oneplus.com/thread/1072689

https://community.oneplus.com/thread/1122597

https://www.reddit.com/r/LineageOS/comments/uohs4y

https://www.reddit.com/r/oneplus/comments/11ovmpt

To summurize :

From OOS 10 to OOS 11 : OK

From OOS 11 to OOS 12 black screen (only Bootloader accessible)

From OOS 10 to LOS 20 black screen (only Bootloader accessible)

From OOS 11 to LOS 20 black screen (only Bootloader accessible)

Basically the device vibrates, screen flashes in dark grey and then nothing.

The device is visible through ADB Devices but unauthorized (sounds good). Can access bootloader with Level Up + Down + Power.

What I tried :

Software used : platform-tools r34.0.1 and payload-dumper-go 1.2.2 (thanks again Luk)

From OOS11 and 10 :

- Bootloader :

oem unlock

- OnePlus fastbootd :

fastboot flash --slot=all dtbo dtbo.img

fastboot flash --slot=all vbmeta vbmeta.img

fastboot flash recovery recovery.img

(dtbo.img, vbmeta.img, recovery.img and LOS20.zip coming from the same release date)

Lineage Recovery : Factory reset (wipe data and cache)

Lineage Recovery → Lineage Fastbootd (to flash manually OOS 12 firmware) :

fastboot flash --slot=all abl abl.img

fastboot flash --slot=all aop aop.img

fastboot flash --slot=all bluetooth bluetooth.img

fastboot flash --slot=all cmnlib64 cmnlib64.img

fastboot flash --slot=all cmnlib cmnlib.img

fastboot flash --slot=all devcfg devcfg.img

fastboot flash --slot=all dsp dsp.img

fastboot flash --slot=all hyp hyp.img

fastboot flash --slot=all imagefv imagefv.img

fastboot flash --slot=all keymaster keymaster.img

fastboot flash --slot=all LOGO LOGO.img

fastboot flash --slot=all modem modem.img

fastboot flash --slot=all multiimgoem multiimgoem.img

fastboot flash --slot=all oem_stanvbk oem_stanvbk.img

fastboot flash --slot=all qupfw qupfw.img

fastboot flash --slot=all storsec storsec.img

fastboot flash --slot=all tz tz.img

fastboot flash --slot=all uefisecapp uefisecapp.img

fastboot flash --slot=all xbl_config xbl_config.img

fastboot flash --slot=all xbl xbl.img

(dump coming from OOS12 F.17 EU)

Then adb sideload LOS20, all OK until then.

Reboot system then stuck into the state I mentioned earlier.

I tried switching active partition from a to b and b to a, reflashing the recovery with no success.

Is there any way I forgot to fix my problem ? What is the use of boot.img or super_empty.img visible on the website ?

Many thanks !
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] orangepowerpokes:
Successful install of LOS20 from here. then had issue with bootloader loop after flashing magisk modded boot.img, stuck. stuck, continued stuck with bootloader boot loop. Tried to forgive myself for flashing bootloader to the wrong partition (maybe??l LIKELY ??? All it takes is a few characters/wrong syntax and, you know ...).

So then, gave a whirl at fastboot boot to twrp (from pc), and to my surprise it booted to twrp. Fom twrp, I dirty flashed LOS20, and everything is bliss. It's only fun rolling dice when you win.

Of coarse if the phone was bricked, off to iphone lol :)
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] xdabushrang3r:
iPhone?!?!?!?! 😮

Someone report @orangepowerpokes for using dirty, filthy language in the thread 🤣🤣
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Slappy123:
Hello and thank you for your answer. I really hope I can fix it by checking twice the syntax (I'll do further researches tonight).

By contrast, the exact same issue happens after doing a clean MSM flash :

- when flashing OxygenOS10 or 11, everything works absolutely perfectly ;

- updating the device from OOS10 to OOS11 using OTA updater works perfectly as well ;

-- > But when I update from OOS11 to OOS12 using the same OTA updater, it leads the phone into the state I described in the last message, even if no syntax error occurred according the fact everything is automated from the Phone.

This observation let me think the issue can be somewhere else (I hope I'm wrong) seeing that I'm not the only one facing this exact same issue after OOS12 update.

Have a great day !
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
Might as well explain how I did it.

1 year ago I bought this phone and updated it to the latest OOS11.

I immediately unlocked the bootloader and sideload LOS18.1 and kept using it until last February.

I updated the vendor firmware from the latest oxygen OS 11 with bin and updated to LOS19 and then immediately LOS20.

No issue yet.

OnePlus does something weird with updating to OOS12, it's regional and they beta test with the Indian market. Testing in EU and NA open another can of worms. LineageOS updates the OOS12 vendor blob better then OnePlus.

TL;DR, OOS11 -> 18.1 -> bin dumper go of the lastest OOS11 firmware -> 19 -> 20.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
OP what adb and fasstboot are you using? Or to be more precise, from what date is the software from?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Slappy123:
Thanks for all the informations and idea, I'll try to do that :

"OOS11 -> 18.1 -> bin dumper go of the lastest OOS11 firmware -> 19 -> 20"

Unfortunately, I cannot find any 18.1 release anymore since LineageOS's website has been updated. I tried Archive.org, but cannot find any 18.1 zip and recovery for hotdogb as well.

If someone still have a release, let me know !

I'm using platform-tools 34.0.1 (March 2023) in a terminal running on Manjaro Linux (mAid 4.0 : https://xdaforums.com/t/live-iso-ma...ndroid-devices-without-driver-hassle.3526755/) which is installed on the computer, no LiveISO or VM.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Eric_Lev:
Eric_Lev - Browse /OnePlus_7T_T-Mobile_Tools at SourceForge.net

sourceforge.net
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Slappy123:
Hello,

First of all, thank you Eric_Lev for the files.

I managed to understand a bit better the issue now.

To summarize :

- Starting with Oxygen OS 11.0.9.1.HD65BA : working fine

- then Upgrade to LineageOS 18.1 (20221016) and Recovery 18.1 : working fine

(oem unlock ; recovery flashing ; sideload copy-partition ; factory reset ; sideload LOS 18.1)

- flashing only recovery to LOS 20 recovery : recovery works, but phone is not booting to LOS 18.1 anymore.

- then whatever I do = problem (phone restarts, vibrate, flash grey and nothing) :

upgrade LOS 19.1 (20221225) while keeping OOS 11.0.9.1 firmware : problem

upgrade LOS 20 while keeping OOS 11.0.9.1 firmware : problem

flashing F.20 firmware following Eric_Lev tuto or LineageOS wiki : problem even if I keep LOS 18.1 that was previously working fine.

What I noticed once the problem occurs :

- the bootloader is still operationnal

- I can reach Recovery and LineageOS Fastbootd while the screen is black : adb Devices shows the phone but I cannot go into sideload ; but adb reboot bootloader works, adb reboot fastboot reboots the phone into fastbootd and can flash everything I want.

Unfortunately, whatever I try to flash, the state remain the same : black screen.

So my conclusion :

The origin of the problem doesn’t seems to be the recovery, but is clearly correlated to Android 12 or later. There is something shared between F.17-F.20 firmware and Android 12+ that brakes the display.

Simplified : what brakes the phone : upgrade to Android 12+ NOR upgrade Android 12 firmware from OOS dump)

I’m wondering if the problem isn’t linked with that former warning on LineageOS's website : “Important: The device may reboot to a blank black screen, fear not, this is a known bug on some recoveries, proceed with the instructions.”

If you have any ideas that can fix the problem, I’m open and ready to try.

Many thanks !
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
Hi general question, how big is system in Storage for you? My phones system storage is around 30GB and I didn't do a clean refresh install. Will it decrease with every nightly as most redundant software is removed one by one?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] oggly.:
26.03.2023 build has some problems. 19.03.2023 was just perfect. Here is the problems:

Brightnes control by sliding status bar just gone :( That was my favorite.

The menu that fingerprint animation can choose is gone.

Some menus just gone espessialy about the customization ones. I was read the changelog and there is so many customization updates I think this is the reason.

Last apps looking jus aweful. There was a blury main screen look but now its just plain color :(.

But the apps that working with screen content (like OCR on screen)working well now. There was a problem about it but it's fixed. But it's takin long time to start tha action.(I'm using 1 Edge's screen text sellecter.)

I got some problem with picture in picture apps. This is the first time with this rom.

I update tomthis build via LOS updater.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] access9:
I've been updating this rom with the weekly builds via the built-in updated, but I skipped the last few weeks due to time, etc. Well, I just updated using the most recent nightly, re-applied magisk like I always do with these updates and boom, it goes to recovery with "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factor reset and erase all user data stored on this device".

Then I made the mistake of side-loading the whole rom again and forgot gapps so I'm a whole new world of pain. But I'll figure that out, probably just wipe and reset. ugh, but oh well.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
In app update is done like this but enable USB-debug just incase something goes wrong:

Download the update from the settings portal.

Install and don't reboot.

Go to Magisk and install directly to the inactive slot.

Flashing GApps isn't needed as it will stay with the update.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] access9:
I've been updating using that exact method for a long time now, it's just that this time it bootlooped and dumped me to recovery. The only way i could get out was sideloading the update through recovery. But doing that caused a ton of errors from any google apps I had installed because now none of the google services were installed. So i tried to sideload the gapps package bit it didn't help.

I ended up wiping, reflashing from scratch and re-rooted.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] AnkeshReborn:
Pixel Launcher is kinda borked in the latest build. Any fixes?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] AnkeshReborn:
Anyway to downgrade to a previous nightly build?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
if you use Magisk there is the bootloop protection module. But I dont know what variable is causing this issue.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] morfin--:
I need help please how can I enable the second sim
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Emhyr:
Hello there,

I've been using LOS20 for about 2 or three months, coming from probably 6 months with Aospa. Since LOS20 I'm suffering from quite battery drain (3 hours screen on time maximum) and always need to plug my phone by the evening. Before switching to LOS it would generally take 5~5.5 h SOT before needing to charge, and the drain in idle was minimal (while now whether or not I use it, the battery drains and needs to be charged at the end of the day).

Am I the only one with this problem? It's like the battery lost 40% of its capacity the day I switched. I tried reformatting everything, removing some stuff, and nothing changes. Some app (FK Updater, I'm not rooted but I have access to the battery monitor, and AccuBattery from what they're worth) estimated the battery around 2000mAh, which is definitely lower than the 3800mAh from the original capacity. I can understand that it has deteriorated, but not that it happened at the exact moment and drastically I flashed LOS20/Android 13.

As anyone experienced it before too?

My last resort is to revert back to a previous android version/other rom (even OxygenOS tout be honest), once I've have some time for that.

Thank you!

And thank you a lot @LuK1337 for maintaining the device :)
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] PiranhaPhish:
Is it really required to update to A12 to install this? Does this imply OOS12? Or will any A12 ROM do the trick?

I've read that the fingerprint/green-tint issues on HD1907 exist even in the stock OOS12 and, if that's the basis for everybody's upgrade to LOS20, is that the sole explanation for these issues in LOS? Or if people are coming from other A12 ROMs (are there any for the HD1907? I honestly don't know), are the issues still there?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] HueyT:
This has oos12 firmware embedded and can be installed via sideloading from LOS recovery without coming from oos12. You can then jump to PE13 if desired
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Ayoub hd dx:
Can you please add support for kernelsu
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] oggly.:
Customization menu (Under Wallpaper & syle) just begone. It's bugged gor a while. I can't even change fingerprint animation...

View attachment 5884983View attachment 5884985
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Emhyr:
In the end I ended up switching to AOSPA Topaz (Android 13, but based on OOS11 firmware), and it indeed solves by a lot the battery drain and I came back to what I experienced battery-wise before switching LOS.

Could it be OOS12 that introduced these battery issues? (or I really am the only one experiencing it)
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
PA uses Qualcomm Code Aurora base, so it should be different then AOSP LOS. The hardware is optimized for Android 13, see Pixel 4 and S10lite.

Android 12 has been bad for all, Oneplus delivered on purpose the update late so people didn't demand Android 13 earlier as it would fix the issue.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Snoere:
I don't have any issues with battery runtime and I haven't heard of such a problem. So I suppose it was a specific issue with your config.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] elvin3:
I have just installed lineage-20.0-20230416 update and if it seems to be really stable (no battery problem except a two hour loss compared to Oxigen original rom: 6 hours instead of 8) but I have to say that adaptive lighting's behaviour has become totally crazy... it changes all the time in automatic mode (the original Oneplus rom was not especially good either) but the worst is in manual mode: everytime my phone screen switches off, it returns totally black when I put it on, and totally opposite next time: adaptive lighting comes at 100% !

Does anyone has the same problem ?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] warlord2045:
Is there a way to turn on VOLTE?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] parknich081:
hello, I have a HD1907, is that not supported? i do not see it on the list of supported models
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] parknich081:
hello, I have installed LineageOS 20 on my HD1907 [US T-Mobile branded], everything is working fine so far. Please add the HD1907 to the list of supported models at https://wiki.lineageos.org/devices/hotdogb/#supported-models @LuK1337

EDIT: i have talked with them on irc, theres a reason it isnt listed
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Is there a reason you don't share the reason here? By the way, does this apply just to the T-Mobile 1907 model. I, like many others, have the B & H unlocked 1907 variant, which since updating to Android 12 reads as a 1901.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
So in the changelog for LOS20 hotdogb, I see something called built-in FM radio. So is it unofficial support for FM radio without a jack?
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] LuK1337:
Just saying, but changelog isn't 100% aware of what given device uses.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] borisSweden:
Yeah I'm gonna take this with a grain of salt, no way Qualcomm would allow backporting blobs after so many years of BS, it all encrypted and signed. It's the worst part of Qualcomm, they only release some potential and tries to sell the rest some time later.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] asad0x01:
Trying to install Instagram, play store says device is not compatible. So, downloaded instagram apk from apkpure, still same issue.

Build Number: lineage_hotdogb-userdebug 13 TQ2A.230505.002 c7c3212cfc
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] js-xda:
I have a. o. the same question and can't seem to find an answer here (or also on same/similar questions in LOS 19.1 thread):

Is this ROM out-of-the-box able to access only the main camera or more? In the past, it was default only the main camera.

How is this ROM handling the camera notch? As OOS or simply putting a black section in the top part of the screen?

Has anyone by chance experience using DKB TAN2go app? It is not a banking app but a proprietary push OTP app.

Planning anyway to move my HD1903 from stock to LOS 20 soon but want to be a bit prepared and screened the whole thread just now.
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] PiranhaPhish:
All three back cameras work as well as the front. This includes the default camera app (Aperture) as well as GCam and Open Camera. Quality seems fine.

I don't believe I installed anything in particular to make them all work, but I can't promise it wasn't part of the GCam install.

The notch is not hidden. In other words the status bar contents are shown to the left and the right of the camera bump, not below it. The full screen real estate is being used and you will see the notch in full screen apps. Fortunately, this is my preference.

AFAICT, there is no option to hide the notch by, say, putting a black bar across the top. The Developer option to do this ("Display cutout") has many options to draw a black spot in various places, some of which move the status bar down a little bit, but it's strangely missing the "Hide" option which I understand would do the black bar across the entire width of the top.