yashsingh1/xdaforums huggingface dataset:
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Klaus_Trophobie:
Hey there. First I have to say thanks for your effort and the time you spent in the last years, @LuK1337 and all the other maintainers. I really enjoy LOS on my Hotdog since v17... An I also use the LOS build for the Tab5e ;) You seem to have an impact on my life ;)

Now I have a problem for the first time! I updated my HOTDOG to the most recent firmware blobs I could find (they are in the CDroid repository and seem to reflect the last FW released in december: HD1911_11.F.18_A12).

crDroid Android - Browse /hotdog/9.x/vendor_firmware at SourceForge.net

Highly customizable Android Platform

sourceforge.net

I then dirtyflashed LOS20 via "adb sideload" comming directly from LOS18.

Everything seemed smooth until I realised that modem is not connecting to GSM at all. ;( Everything else seem to work fine - even the fingerprint sensor seems to work which was ALWAYs a problem before (somehow I managed to have a fp-sensor-problem with all my Oneplus devices so far - but could be my fingers though... ;)

So my system is now on:

LOS 20 - 20230110 nightly

Baseband Q_V1_p14

by the way IMEIs of both SIMs are shown. Bluetooth works. But trying to call or sending an SMS says: Turn off Airplane mode - but its NOT enabled.

I hoped to get around the fact to reset all settings and migrate my 18 -> 20 - But I guess I was wrong... :)

Is there something I can do or I forgot ? Is dirty flashing a bad idea in this case ?

Hope to get some help here - lost for the first time ;)

Thank you all!

Klaus
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] felagund:
I did the dirty flashing without a problem but with f17 firmware as F18 was not out yet.

I have no idea what the root cause is for your problem but my non-educated approach would be to try redo the fastbootd flashing (fastbootd opened within recovery and the commands taken from the LOS device page where it was doing them for both slot A and B) and if it doesn't work then to potentially downgrade to F17 as at least one person here (me) has confirmed it works for them on F17. But again as a disclaimer - I don't have sufficient info and this approach might be counterproductive - I don't know if downgrades can cause issues for example.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] torben5247:
About to install los 20. Currently running 11.0.9.1. i will upgrade to hd1913.11.f17 before flashing los. But i am confused about the twrp i should flash there are 2 versions. Are you guys using twrp-3.7.0_11-0-hotdog.img or twrp-3.7.0_11-0-hotdogv2.img.

Thanks in advance
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] akanee:
If youre confused about TWRP, you should use the recovery that comes with LineageOS instead as the instructions say, should clear things up.

I've noticed it too, putting it on permanent battery saver seems to kinda work? I think this issue would need more data/logs to be diagnosed easier, which I can undoubtedly provide.

This battery issue seems to be exclusive to LineageOS 20, as I didn't notice anything similar to this bad battery drain on LineageOS 19 or 18.1.

Overall, excellent release and amazing upkeep on LuK1337's side for this device. I've been using it since it dropped on Jan 1, and I saw very little to no problems on this device. The only issue I had besides the battery drain was the navbar being too cramped, it's been fixed now. REALLY enjoying the CameraX in this release, finally good enough photos on custom ROMs.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] felagund:
A couple of times during fingerprint unlock I've had the unlock animation stop halfway or remain dark and I'm unable to unlock the phone or do anything but forcing a reboot with the volume up+power combination.

I'll try to see if adb works the next time it happens so I can fetch some logs.

For the battery I got used to topping up and to prevent charging over 80% ACC (the frontend from fdroid) seems to do a good job.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MRoose:
Good day. Why is it important to switch to the LineageOS from the official latest firmware (OOS) ?

Region of official firmware (India/EU/Global) is matter?

F18 available now only for India, don't know, wheather to wait F18 Global.

Now my phone on PE+, will have to go back through the MSM to Android 11.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] torben5247:
Installed los 20 on my hd1913 yesterday.

Installed magisk Extracted boot.img using “payload-dumper-go_1.2.2_windows_amd64”

Patced the boot.img with magisk app and flashed it using fastboot.

It looks fine so far almost all bank apps are running except “revolut” I simply isn´t allowed to download it from play store.

I am thinking that it is because the rom is from another region than Europe and the there are some apps that is not allowed to download or use?

So can i change the region somewhere?

Another thing that I can´t get to work is google pay. If I try to open the app it says ”updating app” and nothing happens.

Edit "i just downloaded and installed a google pay from january 2022 and it works fine, so the newest google wallet app has some security that are more hard to cheat??"

I have 3 other bank apps working fine. And my cts and safetynet are all ok.

I had to modify the build.prop in order to change “userdebug” to “user" in order to get a identity app working.

Another thing I never was able to install was twrp. I simply couldn´t get to work so I am using los recovery. But I miss the functions from twrp, anyone who can guide me to get twrp installed?

If someone has google pay/Wallet woking please advice.

I have used “MindTheGapps-13.0.0-arm64-20221025_100653

btw: Battery use is a little bit worse than stock os11 I think, but I have to give it a little time to test.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] torben5247:
Is it possible to change a setting so the auto brightness is lower?

I think the sensor is very sensitive and the backlight is much to high compared with stock.

Maybe there is a setting in a file somewhere where the value can beadjusted??

Thanks in advance

Torben5247
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] akanee:
TWRP is busted on this device, don't use it. It really only worked on Android 11 while they had a maintainer.

You can achieve most if not all TWRP features from manual adb commands in lineageos recovery.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Ginosius:
When comparing this to Pixel Experience, what are the main differences aside from the Pixel launcher?

If I flash this+gapps, will I get the same kind of 'stealth'?

- no 'this device has been tempered with' message when turning on the phone

- all safetynet checks passing

- banking apps and Google Pay not complaining about unlocked bootloader
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] akanee:
All the points you mention work for me, although that might be heavily dependent on your bank but yeah, no bootloader warning, safetynet working and google pay
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Shreeshail:
plz add switch sim card for mobile data . and double tap to sleep/lock anywhere on the screen.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] krauser2:
我可以使用 nfc 和 otg 更新程序嗎？ plz ans me thanks
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Shreeshail:
Battery percentage increases or drops by 3 or 5 percentage and takes much more time to charge, heats during charging.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] grenskul:
Can I dirty flash from 18.1 or should I go trough 19.1 first ?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] torben5247:
I am strugling with loosing lte network. No data, No text messages. I have to switch flight mode on and off. It happens approximately every 30 minutes. Any idea how to fix it?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] fanticgamerw633:
so safetynet passes and google play is certified right?

edit: got safetynet to pass, google is certified and wallet is working. Too bad widvine is l3, I was unlucky when unlocking ig.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
Since the build lineage-20.0-20230110-nightly-hotdog-signed.zip has been released, I have problems with Bluetooth connection between my 7T Pro and my Renault Megane 3 car radio. In general, the device constantly tries to connect and sometimes, after several iterations, it becomes active, but not always. I've tried to reset the Bluetooth on the phone and also on the car radio, but it doesn't change anything. I also have Skullcandy Indy headphones and have no problems with Bluetooth connection, but they use newer Bluetooth version, so I suppose that maybe the issue is related to Bluetooth 3.0.

Does anyone have an idea how to solve this issue? Any changes in the Developer options for Bluetooth settings can help?

Kind regards,

Tomek
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Ginosius:
The same happens when I try to connect with my dads Renault. You have to press connect many times for it to work.

In my own car it works great though.

And I'm using Pixel Experience btw.

I think some of these issues like these and the messed up brightness slider are kernel related and shared across all A13 roms.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
Thanks. Nice to know I'm not alone, however the problem is really a bit frustrating. I read in the changelog that 2 fixes (merges) for Bluetooth were deployed on February 5 and are available in the latest builds of LineageOS, unfortunately I don't see any changes, and the problem still occurs as it was in previous build.

PS: I use MacroDroid and I have a macro that automatically sets some properties on my device and launches the Waze app when connected to my radio, but currently it doesn't work, because it depends on Bluetooth.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MRoose:
Hello.

After update (rom with recovery via settings) from 20230131 to latest 20230207, the screen became very dim.

Up to 90% of the brightness scale, there is practically no difference.

95% current brightness scale on 20230207 = 60% brightness scale on 20230131.

Does anyone know where the brightness limit is set?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
I don't see this problem, moreover, I can't find any changes in the changelog that could affect the brightness of the screen. Most of them are related to Aperture. Are you sure that you didn't enable the extra dim option in the Settings -> Accessibility?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MRoose:
Hello.

Didn't know about this section. Checked - disabled.

Auto-brightness is also disabled.

The problem is that in the range of 10-80%, the brightness changes very little.

I can assume that when updating, the old brightness was registered as maximum (almost)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
Hi,

I always have adaptive brightness enabled, but I turned it off for a while and tried the slider. I don't see a problem in the entire brightness range, increasing and decreasing works linearly. My display settings are: Dark theme - enabled; LiveDisplay -> Color profile - Vivid; LiveDisplay -> Display mode - automatic; Smooth Display - enabled.

I use LineageOS 20 also in my Samsung Galaxy Tab S5e and for this device, I also see no problems with brightness.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
The issue with Bluetooth has been fixed in the latest build 20-20230214-NIGHTLY. As I suspected, it depended on January security patch and changes related to the Bluetooth package.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Ginosius:
Very nice!

Thats one of the benefits of running LineageOS.

You get updates very quickly.

I'm currently on Pixel Experience 13, its rock solid but ROM updates take a bit longer.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] ChrisLane:
I just switched from a OnePlus 3 running Lineage OS to a OnePlus 7T Pro Mclaren running OOS 12 and have noticed that GPS accuracy isn't as good.

Can anyone confirm for me that they get better GPS accuracy on Lineage OS than on OOS? 🤞
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Ginosius:
I was running Pixel Experience 13 and here are the steps I took to restore and flash LineageOS 20.

For the record my device was originally running the EU (HD1913) firmware.

- Using the MSMTool package from here to restore 11.0.5.1 (EU firmware): https://xdaforums.com/t/op7tpro-oos...l-to-restore-your-device-to-oxygenos.4002909/

- Then I updated to 11.0.9.1 using the builtin updater

- When I was on 11.0.9.1 I've verified that Widevine was showing L1

- Unlocked the bootloader using fastboot oem unlock

- Using the oxygen updater app I've installed OOS12 version HD1913_11_F.17 (I believe this is MP2).

- Being on OOS12 with a unlocked bootloader I pretty much followed the steps here to the letter: https://wiki.lineageos.org/devices/hotdog/install

The strange thing is that flashing the dtbo.img and vbmeta.img will softbrick my phone.

From this point on, the phone will always boot into recovery.

But after following the rest of the instructions (flashing the lineageOS recovery etc), I successfully installed LineageOS 20 and MindTheGapps version 20221025 from here http://downloads.codefi.re/jdcteam/javelinanddart/gapps

Now running LineageOS20 I noticed that unlike all other users, Safetynet CTS profile was NOT passing at all!

Also Widevine reverted back to L3.

My banking apps would work though (as I didn't root my phone).

Without CTS profile passing I couldn't setup my Google Pay Wallet...

I wonder if this is because the Android 12 firmware (modem etc) are from the OOS EU HD1913_11_F.17 release while LineageOS identifies as HD1911 or some other reason?

Anyways I'm really curious whether other users are passing all checks (including CTS profile) and which base firmware they were on before flashing LineageOS (e.g. global, india or EU).
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
In the case of LineageOS, it is a bit more complicated. No one has CTS attestation right after the first boot, because LineageOS does not provide it. In general, you need to force a basic attestation using the MagiskHide Props Config module, where you can also set the corresponding fingerprint to HD1913. Then you need to install the Universal SafetyNet Fix module, after which you will be able to use Google Pay, and Widevine should be L1. As a root manager, I suggest using Magisk Delta. For terminal operations, Termux is quite good. YASNAC can also be useful. 😉
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] LuK1337:
Just saying but Widevine is L1 without doing any of that...
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Ginosius:
So I've flashed the latest Magisk Canary release.

I've enabled Zygisk and added the nessesary apps and services to the denylist.

After installing the Universal Safetynet Fix MOD by Displax: https://github.com/Displax/safetynet-fix/releases

and the MagiskHide Props Config modules, everything started working again.

I'm passing CTS and I can use all of my banking apps and Google Pay.

Widevine is still showing L3 though.

This could be due to LineageOS identifying as a HD1911 while my phone is running the HD1913 (EU) firmware.

I've tried to set the HD1913 (Android 10/11) fingerprint using props but that didn't fix it either.

Another reason could be that it misses the Android12 fingerprint (its not maintained anymore).

But I can live without Widevine L1.

The ROM runs like butter and has amazing battery life :)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
I suggest using the original SafetyNet Fix by kdrag0n: https://github.com/kdrag0n/safetynet-fix This module is currently in version 2.4.0 and supports auto-update in Magisk.

In terms of fingerprint, you can use that one for Android 11, it does not matter.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
Steps to go enable Widevine L1 on custom ROMs :-

• Flash OOS 11 stable. eg.11.0.5.1

• Flash Magisk then enable Zygisk + denylist.(in denylist you should select show system apps in three-dot menu,then search gms, select com.google.android.gms and .gms.unstable).

• Reboot.

• Verify if you have L1 working using app like DRM info.

• Local upgrade OOS 11 stable (preferably same build).

• Reboot.

• Verify if you have L1 working using app like DRM info.

• Flash custom ROM and you should have L1 there as well.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Ginosius:
Thanks for your suggestions.

When I was on OOS 11.0.5.1 and 11.0.9.1, Widevine L1 was working fine.

But the LineageOS wiki says you have to be on A12 firmware in order to flash LineageOS 20.

And that's exactly where I lost it... after upgrading to OOS 12 (with an unlocked bootloader).
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
You don't need to upgrade to OOS12 and that's the problem. All you have to do is update the firmware via fastbootd. This means you have to extract payload.bin file from the latest OOS zip file and use payload dumper to extract firmware *.img files. https://github.com/ssut/payload-dumper-go

After that, boot the device in recovery mode, start fastbootd and use the bash script from the LineageOS website.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Ginosius:
Ah yeah.. fastboot reboot fastboot, then you can follow the instructions from the wiki to manually flash all the .img files from the payload dumper.

But this means I have to start all over again by reverting back to 11.0.5.1 using the msmtool.

I'll do this over the weekend and report back :)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Ginosius:
@LuK1337 and @devourerOfBits80 Think with me please :)

So I've attempted to reinstall LineageOS while trying to keep my Widevine L1 certification.

The first thing I did, was restore 11.0.5.1 using the MSMTool package from here: https://xdaforums.com/t/op7tpro-oos...l-to-restore-your-device-to-oxygenos.4002909/

This worked fine and the stock firmware seems to restore L1.

Then I upgraded to latest OOS 11.0.9.1 release using the builtin updater and I still have L1.

The next step was to copy the 11.0.9.1 update zip-file from the ".Ota" folder to my computer, extract the zipfile and dump the boot.img using the payload-dumper tool.

I then installed Magisk to create a patched boot.img and copied that to my computer.

I've unlocked the bootloader using "fastboot oem unlock" (which clears the whole phone again) and flashed the patched boot.img using: "fastboot flash --slot=all boot magisk_patched.img".

Now I get the warning screen regarding the unlocked bootloader but I have magisk up and running on 11.0.9.1.

So I enable Zygisk, the Denylist and I add com.google.android.gms/.gms.unstable and Google Play Store to the denylist followed by a reboot.

And voila!

I'm now running OOS 11.0.9.1 with an "unlocked bootloader" and Magisk while retaining Widevine L1 :)

So far so good!

Now I proceed to install LineageOS 20, which is pretty much: https://wiki.lineageos.org/devices/hotdog/install

1. Reboot into the bootloader: adb reboot bootloader

2. Flash dtbo.img, this fails because dtbo_a and dtbo_b don't exist on OOS 11 firmware yet, so I flash it later on with OOS 12 firmware files

3. Flash vmbeta.img

4. Flash recovery.img

5. Reboot into LineageOS recovery

6. Format data / Factory reset

7. adb sideload lineage-20.0-20230314-nightly-hotdog-signed.zip

8. Reboot into recovery again

9. adb sideload Magisk-v25.2.zip

10. adb sideload MindTheGapps-13.0.0-arm64-20221025_100653.zip

11. Enter LineageOS fastboot

12. Flash dtbo (which failed before): fastboot flash --slot=all dtbo dtbo.img

13. Use the payload-dumper tool and dump the OOS 12 EU firmware: HD1913_11_F.17

14. Follow the instructions here: https://wiki.lineageos.org/devices/hotdog/fw_update to flash the OOS 12 firmware files

15. Reboot into LineageOS for the first time

16. Run Magisk: enable Zygisk, setup Denylist, Hide the Magisk App and install the Universal Safetynet Fix module

Now I have a fully working LineageOS 20 phone:

- No warning screen when I turn on my phone

- SafetyNet check passing ALL checks

- Google Pay and banking apps working

But Widevine still turned into L3 :(

So I'm wondering... Did I mess up at one point?

Just a random thought, my phone is originally a EU HD1913 and I'm also flashing the HD1913_11_F.17 OOS12 vendor firmware.

However LineageOS 20 identifies as HD1911.. perhaps this breaks the Widevine certification?

Which firmware were you guys running before switching to LineageOS?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
Hello, 😉

Sorry for the delay, but I have a lot of different things on my mind. I don't understand why did you need to install Magisk for OOS 11.0.9.1. As far as I know, you don't need even to update OOS from 11.0.5.1 to 11.0.9.1. All you need to do is install OOS 11, check if Widevine is L1, unlock the bootloader via fastboot, load the LineageOS recovery image via fastboot, upgrade firmware via LineageOS recovery's fastbootd mode, install LineageOS.

For HD1913 you can install the latest firmware version HD1913_11.F.20_3200_202301310042. To change the model from HD1911 to HD1913 use MagiskHide Props Config.

Kind regards,

Tom
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Ginosius:
Thanks Tom!

So for the record.

After unlocking on 11.0.5.1 you only flash the LineageOS recovery and enter LineageOS' fastbootd to flash the OOS 12 firmware?

Did you also flash the vbmeta.img and dtbo.img during this step? Or did you skip it all together?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] devourerOfBits80:
Yes, I have flashed LineageOS immediately after unlocking the device's bootloader. I didn't flash vbmeta.img and dtbo.img because these images are available to download from approximately 3 weeks, but I don't think so you need them. Use only the latest recovery image and signed nightly build. 😉
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] felagund:
Hi, jumped a few versions to the 04 04 build and the option to control brightness by slidng on the status bar has disappeared.

It's still present on a march LineageOS version on another phone I have.

Is this related to the Make battery and clock clickable again change?

Actually is change 353375 in the 0404 build as it shows for next build but I can click on battery and clock without pulling down on the quick settings?

Or was I confused and was it ever an option to slide for brightness on the status bar on lineageos 20?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Bar987:
Hi, can anybody tell me what the battery control file is for Battery Charging limit on LineageOS 20 on this device?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] felagund:
With ACC I use battery/mmi_charging_enable for battery control.

Here is the output for it from the charging switch tests

3/21: battery/mmi_charging_enable 1 0

switch: off (0)current: -413mA (Idle)

switch: on (1)current: -627mA (Charging)

Switch works ✅

- battIdleMode=true

Previously I used it with the ACC frontend from fdroid but now I just have it with the Magisk module.

This one also works

4/21: battery/step_charging_enabled 1 0

switch: off (0)current: -448mA (Charging)

switch: off (0)current: 230mA (Discharging)

switch: on (1)current: 230mA (Discharging)

switch: on (1)current: 1562mA (Discharging)

switch: on (1)current: 1562mA (Discharging)

switch: on (1)current: -1942mA (Charging)

Switch works ✅

- battIdleMode=false

For me it's easier to use ACC as this way I have control if I want to override and charge to 90+% etc.

But also if I'm not mistaken the documentation said different switches work for different charger and cable pairs sometimes.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Bar987:
Strange, ACC is working for me, and input suspend tests positive in ACC, however with BCL the same CTRL file won't work. Nevermind, I'll use ACC for now, thanks for your input!
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Amjadh:
@LuK1337 Thank You so much for the charging health control and battery idle mode functionality in the latest update. I was struggling with ACC and its terminal input function for changing configs. Now I can remove them all and sleep peacefully. You're a hero... 😇😇🥳