yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 9 Questions & Answers] leduard:
Seems that Vodafone romania is using band 1, 3, 20 (2100,1800,800). As i see in LTE Discovery, all 3 bands are used sometimes.

When i bought the phone it was on stock MIUI 10 and the problem was present. After a few days i got announced that MIUI 11 is available and i upgraded to that. Unfortunately nothing has resolved. So i decided to try the MIUI EU stable 11.0.4 rom. But download speeds are the same across all roms.

It is strange, cos i don't see anyone having these issues.
[Xiaomi Mi 9 Questions & Answers] leduard:
Here-s a screenshot:
[Touch CDMA Windows Mobile ROM Development] dave68:
I was trying to take a shortcut to that AAA Authentication issue while cloning a phone and used CDMA workshop to copy ALL NVM to my soon to be replacement Touch for the one that has a broken power button on it...Now the clone says "Searching" at top left of HTC Home. I've checked all settings and I cann see what I did. I know that CDMA workshop had scribbled over some NVM incorrectly, and I need to know which program is best for reading and writing to NVM

Uhmmm, yea, Bitpim doesn't work with The Vogue - Errors on reading filesystem...

14:13:17.500 Other CDMA Phone: Listing subdirs in dir: 'htc'

14:13:17.500 Other CDMA Phone: Listing subdirs in dir: 'hdr'

14:13:17.515 Other CDMA Phone: Listing subdirs in dir: 'sms'

14:13:17.515 Other CDMA Phone: Listing subdirs in dir: 'sfs'

14:13:17.530 Other CDMA Phone: Failed to list dir sfs

14:13:17.530 Other CDMA Phone: Listing subdirs in dir: '.efs_private'

14:13:17.530 Other CDMA Phone: Failed to list dir .efs_private

14:13:17.530 Other CDMA Phone: Listing subdirs in dir: 'export'

14:13:17.546 Other CDMA Phone: Listing subdirs in dir: 'DMU'

14:13:17.562 Other CDMA Phone: Listing subdirs in dir: 'nvm'

14:13:17.562 Other CDMA Phone: Failed to list dir nvm

etc...

Tried COM6:

This port is available and can be selected.

Property

Value

Description

active

True

Your operating system shows this driver and port is correctly configured and a device attached

available

True

It was possible to open this port

class

serial

This is a serial connection

description

HTC Diagnostic Interface (PID 0B03) (COM6)

driverdate

2007-1-5

driverdescription

HTC Diagnostic Interface (PID 0B03)

driverprovider

HTC Corporation

driverversion

2.0.3.1X

hardwareinstance

USB\VID_0BB4&PID_0B03&MI_01\6&BFE545B&0&0001

This is how the device is named internally. For example USB devices include the vendor (VID) and product (PID) identities

name

COM6

This is the name the port is known to your operating system as

Even tried Modem mode, and that's when Bitpim crapped out...

What program works best for reading NVM? :confused: Please, and Thanks.
[Touch CDMA Windows Mobile ROM Development] BottleNeck:
Bitpim is useless for Vogue. Let use Qualcomm QPST 2.7 build 264

Software Download program (backup/restore functions).
[Touch CDMA Windows Mobile ROM Development] dave68:
Reading NVM in HTC Touch?

Nogo - QC epst shows filesystem, but just like bitpim it will display nothing in the NVM folder (has a red circled line thru it)... :rolleyes:
[Touch CDMA Windows Mobile ROM Development] chrispipe:
try throwing your phone into bootloader mode (power, camera, pinhole buttons simultaneuosly) and then read it with bitpim

that folder seems to lock.

not sure if this will work but it might help you. or at least be a shot in the right direction
[Touch CDMA Windows Mobile ROM Development] dave68:
Nein, Mein Freuind. 1st off, the Modem/Serial port not detected in either Dev-Man, or BitPim. and QPSTConfig says "waiting" on COM 2 - N/A for device... :confused: uhh, but I think I know what I did wrong...

1st off would like to kindly ask if anyone here has a copy of their NVM (with ESN 0'd out of course :) ) from a Telus P3050 (Vogue.) that they'd be willing to share?

Why I need a copy is this:

I have a Bell MP8900 that when I dropped, I broke the power switch. So I bought a Telus P3050 (also a Vogue.) Cloned the E$N and the phone worked like a charm, but I wasn't (Like everyone else...) getting EVDO Authentication. There was a long and ardurous task of fixing that, but I decided to try using CDMA workshop to copy the NVM from the Bell to the Telus phone. I didn't realize that the Telus Phone has a DIFFERENT MEMORY MAP than the Bell. IE:

Telus NV Ram =

[NV Items]

[Complete items - 417]

(has more items like: )

0081 (0x0051) - OK

01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

whereas Bell NV Ram =

[NV Items]

[Complete items - 404]

(and the Bell does not: )

0081 (0x0051) - Inactive item

and the Telus phone will read to the end of NV Ram while the Bell phone resets when you try reading past address CE30:

Scanning memory for readable areas:(Bell)

Unreadable area from: 0000:0000

Readable area from: 0134:0000

Unreadable area from: 01C3:0000

Readable area from: C000:0000

Unreadable area from: C0D0:0000

Process is stopped at: C3E0:0000

Scanning memory for readable areas:(Telus)

Unreadable area from: 0000:0000

Readable area from: 0134:0000

Unreadable area from: 01C3:0000

Readable area from: C000:0000

Unreadable area from: C0D0:0000

Readable area from: C3E0:0000

Unreadable area from: C4B0:0000

Of course silly me, I didn't make a backup, because I thought VOGU100 on both phones meant that they SHOULD be physically the same. They are not. Now all The Telus does is "searching..." for Signal. Everything else matches SID/NID pairs, MSID, etc, all same. E$N Matches.

So if some one has a copy fof the NVM from their Telus P3050 that they'd be willing to share, it'd be appreciated.

TIA
[Samsung Galaxy A20 Questions & Answers] RealBrianDuong:
I have searched everywhere on the web and none of the tutorials work to enable OEM Unlocking on my device. I'm trying to unlock the bootloader so that I can install TWRP and a custom rom. Any suggestions?
[Samsung Galaxy A20 Questions & Answers] physwizz:
Sorry, Samsung have blocked the 205U
[Samsung Galaxy A20 Questions & Answers] HammieSlice:
[MENTION=10431347]RealBrianDuong[/MENTION] [MENTION=5440376]physwizz[/MENTION] have y'all heard of any changes with this or any genius moves? lol

---------- Post added at 08:32 AM ---------- Previous post was at 08:21 AM ----------

Could some also try to sum this up for a half ass noob with rooting and everything i've only rooted two devices but,

with this knox system i'd hate to trip something or whatever.

meanwhile this https://boycracked.com/2019/10/19/official-samsung-galaxy-a20-sm-a205u-stock-rom-for-usa-region/

website shows something that looks promising but what does this mean and is this bluff or workable?

if it could work please tell a dummy the best way lol

---------- Post added at 08:35 AM ---------- Previous post was at 08:32 AM ----------

on another note, if you can not unlock bootloader, how can you get to reflashing the stock rom like this site says and apply the cf auto root anyhow??? https://boycracked.com/2019/10/19/official-samsung-galaxy-a20-sm-a205u-stock-rom-for-usa-region/ :rolleyes::confused:
[Samsung Galaxy A20 Questions & Answers] physwizz:
You can't do anything much without unlocking the bootloader and Samsung have blocked the 205u
[Mogul, XV6800 ROM Development] jshaas2:
DCD...your last post says "don't post here yet". i hate to post there if you asked us not to yet, but i had a few questions on 3.2.0 before i ran the kitchen.
[Mogul, XV6800 ROM Development] drew826:
It's open now. Post away. I think he just wanted a chance to finish editing/updating his initial post before people flooded with questions like "how come your screenshot still shows 3.1.6?"
[Mogul, XV6800 ROM Development] hoothrewpoo:
running 3.20 now. Seems a bit faster than 3.04 which is what I was running previously. I'm having a slight problem with my Start menu disappearing, but it's pretty awesome otherwise.
[Mogul, XV6800 ROM Development] jshaas2:
gotcha. well kitchen is here open..just waiting to ask a few questions. i'll update the signature as soon as i'm on 3.1.2
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] GorgaWWs:
I have a N8000 tablet and need to expand the runtime of the battery.

The battery has 5 pins (two red, two black and one blue cable from the battery). The other battery I bought is also a 3.7V battery (powerbank).

My idea was to attach another battery in parallel with the internal (no power outlet at the location available).

I was expecting that the tablet will run but the internal battery has now 1 percent and when i attach the powerbank battery it still turns off.

What am i not seeing / why is it not working?

Edit: When I unplug the internal battery and directly attach the battery from the powerbank the tablets boots up fine.

Edit2: Forgot the most obious. Why am I not charging the tab with a powerbank via USB? The USB port is in use (OTG) the whole runtime on the tablet.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] GorgaWWs:
SOLVED!

For documentation:

In the meantime I've switched to a Galaxy Tab 3 but this should work for all androids.

Battery has 6 pins

Two red, two blue, two black.

Ive removed the battery and put some cabling to the outside red and black and connected it to a power-supply.

-> Tab wont turn on.

Then i found a couple threads that mentions that there should be a resistor between the ground (black) cable and the blue. These blue lines are NOT the same. So I pulled one cable out of the plug and reattached the battery to see if the tablet switches on. It didn't. Then i plugged the blue cabled back in and removed the other one - reattached ... the tabled switches on!

So now i know which of the blue wires is important. Ive charged the battery completely and measured the resistance between the blue line and ground -> 100kOhm.

Resoldered my cables and installed a resistor to ground. Tablet starts with external power supply .. 64 % battery ... and going down slowly!

After it reached 1% it switches off!

After A LOT research and days Ive found an explanation here:

https://android.googlesource.com/pl...s/java/com/android/server/BatteryService.java

private void shutdownIfNoPowerLocked() {
// shut down gracefully if our battery is critically low and we are not powered.
// wait until the system has booted before attempting to display the shutdown dialog.
if (mBatteryProps.batteryLevel == 0 && !isPoweredLocked(BatteryManager.BATTERY_PLUGGED_ANY)) {
mHandler.post(new Runnable() {
@Override
public void run() {
if (ActivityManagerNative.isSystemReady()) {
Intent intent = new Intent(Intent.ACTION_REQUEST_SHUTDOWN);
intent.putExtra(Intent.EXTRA_KEY_CONFIRM, false);
intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
mContext.startActivityAsUser(intent, UserHandle.CURRENT);
}

There it is. If battery is 0 and no power-supply is attached then android is shutting down itself - even if the voltage is up.

Honestly I havent understand how the capacity is determined - voltage was always good.

Anyway after a couple more days just before giving up i've had the idea of instead finding the reason why the battery is going down to simply fake it.

Ive found a stackoverflow post (sadly cannot find it anymore) which basically said you can set the battery to any percentage you want with this command (root):

dumpsys battery set level 99

There you go. Your tablet runs with an external power supply.

Hope this saves someone a lot headache.
[Xiaomi Mi Max 2  Questions & Answers] Noexcusses:
Hello everyone, witch is the best kernel for mi max2 ?

Also are there any nee drivers witch i can flash?

Thank you all!
[LG G8X ThinQ Questions & Answers] kevin_23:
Do you know the exact sony imx model that mounts the new lg g8x? Is it the same as that of the Korean G8?
[LG G8X ThinQ Questions & Answers] harysviewty:
Main rear yes imx363

Wide angle is identical to v30. Samsung sensor
[Touch Diamond, MDA Compact IV General] norvillerogers:
For those of you that have a Diamond I have a question for you please.

When you receive an email/sms message, do you receive a pop-up on the screen like the 2007 devices provided (which gave you the option to continue to the message or dismiss it) or do you just get a notification next to the email/sms icon?

Any feedback is greatly appreciated.

Thanks.
[Touch Diamond, MDA Compact IV General] mital:
Just get a notification next to the icon. Actually I'm going to stop using HTC home because although it looks really nice, I hate that it's not customisable.
[Touch Diamond, MDA Compact IV General] czbird:
You can enable the popup message in Options -> Sounds and Notifications -> Notifications -> Messaging: New e-mail message -> check "Display message on screen".

In diamond, these popups are disabled by default, hence this extra step.
[Touch Diamond, MDA Compact IV General] norvillerogers:
Awesome. Thanks for the feedback.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
/*
* Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!!
* NOTE:
* I allow off topics in my thread. I'm also open for any fun.
* But still, discussion about the ROM itself is still would be prefered.
* However, what isn't tolerated is belittling of ANY developers and/or their work.
*
* Thank you. :)

DerpFest 10 For Redmi K20 Pro

About

Derpfest is a heavily customized build of AOSiP.

It uses AOSiP as a base and add more features on top of it.

note: AOSiP and DerpFest teams are in no way related.

Bug reporting

DO NOT REPORT BUGS DIRECTLY VIA PM/TELEGRAM PM.

DO NOT Report bugs if you're running a custom kernel, Xposed, or any external mods

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 dmesg. (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 issues that already known

Download

Google Drive

Gapps : included, no need to flash gapps again

Vendor Recommended : 11.0.4.0 (because 11.0.5.0 are known to have some bt connection issues)

Installation

Clean Install

Wipe system and data

Flash the required vendor zip

Flash the ROM

Flash DFE (if decrypted)

Reboot into the system

Dirty Install (update)

Wipe dalvik cache

Flash the ROM

Flash DFE (if decrypted)

Reboot into the system

Source code

DerpFest Github

Devices Tree source

Kernel source

Credit and Thanks to

- [MENTION=5974762]NurKeinNeid[/MENTION] (DerpFest Founder) and all of the DerpFest Team

- [MENTION=7652613]UtsavTheGreat[/MENTION] for the raphael device-tree and vendor blobs

- [MENTION=7030080]Star_king12[/MENTION] for the F1xy kernel

- [MENTION=7190920]okitavera[/MENTION] for the helps and guidance

- Google for Android and AOSP

- Mike Williams (founder and creator of AOSiP)

- LineageOS

- AICP

- ABC ROM

- AquariOS

- BootleggersROM

- PixelExperience

- OmniROM

- Cory Collins

XDA:DevDB Information

DerpFest 10 for Redmi K20 Pro, ROM for the Redmi K20 Pro

Contributors

nullxception

Source Code: https://github.com/nullxception/device_xiaomi_raphael

ROM OS Version: Android 10

ROM Kernel: Linux 4.x

ROM Firmware Required: 11.0.4.0

Version Information

Status: Stable

Current Stable Version: 20200105

Stable Release Date: 2020-01-05

Created 2020-01-03

Last Updated 2020-01-05
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
Notes

- This ROM uses F1xy kernel which known to be blocking Screen OC by default. So, if you're fan of oc (I don't), you can flash other custom kernel :)

Changelogs

- Build 20200105

https://xdaforums.com/showpost.php?p=81392363&postcount=27

- Build 20200103

An initial public release with some additional fixes and stuff under the hood like :

* Better UI paddings

* Fixed RIL (opt/Telephony)

* Fix USB Debugging not restored (vendor initscript problems)

* San Francisco Pro Fonts Added

* Follow dalvik-vm configurations from frameworks/native

* Included PixelExperience's Custom ANXCamera

* etc
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] sam00561:
is screen OC screen overclock?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
Yup
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] sceryavuz:
Any screenshot for rom based customizations?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] sam00561:
Good I don't over clock anyhow
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] classofbody:
How's the fingerprint performance? Are you able to post some screenshots of this ROM?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
Here's some screenshots, sorry can't post it all since it would be too much.

About fingerprint; on me, it quite fast just like any other aosp-based rom.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] classofbody:
Amazing rom, it has everything I need to be a daily driver! But the FOD isn't working for some reason and the brightness is overall kinda finicky, is it a bug or just me? And can you please link the wallpaper that you're using?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
Yes, the auto brightness is kinda sucks for now (still can't find the right solution for it), but I don't have any issues for the FOD, what's your vendor version ?

About that earthview wallpaper, it's a paid wall on the app called Abstruct.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] hopeallison:
no
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] classofbody:
I'm on the latest global V11.0.1.0 firmware, fingerprint is working perfectly but in the always on display it's not. Also even without auto brightness, the brightness seems all over the place. Other than that it's a pretty good rom.

Edit: Flashing Immensity kernel seems to have fixed the FOD. But the brightness is still glitchy.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] leosinfinity:
An initial public release with some additional fixes and stuff under the hood like :

* Better UI paddings

* Fixed RIL (opt/Telephony)

* Fix USB Debugging not restored (vendor initscript problems)

* San Francisco Pro Fonts Added

* Follow dalvik-vm configurations from frameworks/native

* Included PixelExperience's Custom ANXCamera

* etc[/QUOTE]

GREAT WORK DEV.:good:
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
Nice to know, thanks.

Will diff utsav's implementation later.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] dsahai:
Finally, the first custom ROM in which my FOD worked!
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Rydberg1:
Many thanks for this ROM! It runs great aside from the mentioned brightness issue.

One super minor thing that you might want to consider is the icon for the ANX camera that you include. Right now it's the Google Camera icon, and it gets a little bit confusing for us that use a real Gcam app aside ANX. It's customisable in the launcher, but not when choosing standard app, for example setting the app for double tap to open camera.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Psych Engel:
Is this based on the ROM from kunalshah912?

I've found a prop called "magic brightness" or something like this. I can't remember in which file it was/is, but I could search and give feedback, if I found it. Maybe this will fix the autobrightness bug which is also in the ROM from kunalshah912.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] grimpy:
Shortly played with it looks like a nice rom, keep up the good work dev.

Just wanted to let you and other people know that Android Auto is giving same problems as most other AOSP roms :(

I had high hopes seeing that the device tree had a bunch of commits of the guy from PE.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] P12AV33N:
Is mannual brightness working fine for you?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] pete80pro:
Brightness is a big issue in this build. Its changing too often and manual brightness is like 0% is 40% on other Roms. Its too Light.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Psych Engel:
Sry, I actually using the official build, which I mentioned in my post, but in my case, it's working fine, in manual mode, it's a little bit stuttering if I switch, but every percent is displayed fine.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
Yeah, I'll do something with that in the next build

This build is 100% using official DerpFest sources (except device-tree, vendor proprietary files, and kernel source).

Developers can make their own changes private since most of android components are using public domain licenses.

So if the previous developer has some fix privately, there's no way that I can do with it until I figured out myself, sorry.

I don't think I can figured out what's going on with that since I can't test such things like android auto :rolleyes:

----

Oh btw, the fingerprint on AOD issues is addressed already and maybe fixed in the next build.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Psych Engel:
I don't think he did own fixes, because he developed it official and canceled it, because he couldn't push the fixes directly. Maybe you can ask him, he seems a pretty good guy :)
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
Yeah I saw the drama, which I don't really mind about it as long as I get the ROM (which now it turns out to be abandoned because of it, sucks :rolleyes:). But I think I'll ask him later :good:
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Rydberg1:
One thing I've noticed with all the ROM:s, which is a bit strange to be, is if the phone is locked and I double tap on a notification to open it, I never get promted to use the FOD, but rather input my PIN. Is this something that's "fixable"?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] t0m2k:
Working fine here:svetius:
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
Changelog build : 20200105

ROM

- Bring navbar editor back to DerpQuest Navbar tuner

- Cover-up dalvik heap configuration for 6GB devices too

- Enable burn-in protection by default

- Implement Scaled Brightness (fix brightness issues)

- Ported several FOD fixes and enhancements (fix FOD on AOD not working)

- Several fixes and enhancements on the Telephony and System UI

- Switch to regular ANXCamera (currently: v164.FamiliarBlondCollie)

Kernel

- Switch to qualcomm drm notifier for fingerprint drivers (Fix FOD issues too)

- Fix several memory leaks

- Several improvement and fixes for entropy, zram, ext4, etc

- Update SLMK to the latest version

Download link are in the OP, enjoy :highfive:
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] betalaga:
hi, where i can find vendor 11.0.4?

here https://downloads.akhilnarang.me/MIUI/raphael/ there isn't
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
if your device SKU is CN, here's the 11.0.4.0 vendor : https://github.com/TryHardDood/mi-v...RAPHAEL_V11.0.4.0.QFKCNXM_0c612efa47_10.0.zip

But someone's reported that 11.0.1.0 and 11.0.3.0 is also good to use.
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] betalaga:
no, it is Europe version. 11.0.3 it's good?
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] nullxception:
Yes
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Rydberg1:
So this is not happening to you? I wonder what's the difference between our phones then? You're not unlocked already with smartlock or anything, right?

Had to upload with Firefox Send cause XDA won't allow .mp4.

https://send.firefox.com/download/e62666ef559c6f89/#e81H2zznuQHGdVgdNhXo1g
[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] betalaga:
Good work! Anx camera work fine

so far I have not found any bugs and it is the only AOSP without any bugs