yashsingh1/xdaforums huggingface dataset:
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] theburrus1:
Elite TWRP???

Hi again, perhaps another stupid question here but exactly what is and where do I find the Elite TWRP? Also, if I may ask is what makes it any better than the standard one for the Honor 6x? Could you provide a link as I can't seem to locate the precise TWRP I need for this ROM. Thanks.
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] PalakMi:
Look in the Elite ROM thread, 2nd post. That's where the Elite TWRP is
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] theburrus1:
I found it. Thank you for taking the time to reply to I had seen that ROM thread but hadn't scrolled down far enough to the 2nd posting. Much obliged. Look forward to trying this (Validus) ROM out!
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] PalakMi:
You're welcome :D
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] Rishav Nath Pati:
How to download the ROM. Which file...????

I am new and I'm confused also. Help me. I just need the link to download the ROM.
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] shashank1320:
You need to check on PC. it wont show up in phone app.

here is the link BTW

https://xdaforums.com/devdb/project/dl/?id=27525
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] inuer:
ask

bokeh is work?
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] shashank1320:
No it wont. Only stock and elite have this
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] theburrus1:
Why after flashing Magisk (any verision- old or new) this ROM then never wants to boot and stays stuck with the wolf running. 'Tis a pity as I like this ROM. Anyone? Any ideas?
[General Topics] Jadel:
REDMOND, Wash. — Feb. 21, 2008 — Microsoft Corp. today announced a set of broad-reaching changes to its technology and business practices to increase the openness of its products and drive greater interoperability, opportunity and choice for developers, partners, customers and competitors.

Specifically, Microsoft is implementing four new interoperability principles and corresponding actions across its high-volume business products: (1) ensuring open connections; (2) promoting data portability; (3) enhancing support for industry standards; and (4) fostering more open engagement with customers and the industry, including open source communities.

"Ensuring open connections to Microsoft’s high-volume products. To enhance connections with third-party products, Microsoft will publish on its Web site documentation for all application programming interfaces (APIs) and communications protocols in its high-volume products that are used by other Microsoft products. Developers do not need to take a license or pay a royalty or other fee to access this information. Open access to this documentation will ensure that third-party developers can connect to Microsoft’s high-volume products just as Microsoft’s other products do. "

"Microsoft is providing a covenant not to sue open source developers for development or non-commercial distribution of implementations of these protocols. These developers will be able to use the documentation for free to develop products."

More after the jump, direct from Microsoft:

http://www.microsoft.com/presspass/press/2008/feb08/02-21ExpandInteroperabilityPR.mspx?rss_fdn=Press%20Releases

Thank you to anyone who takes the time to read this and explain if it means any positive news for our Windows Mobile devices. They aren't high-volume devices according to the press release, and they didn't specifically mention them, but they are opening up the APIs for Exchange Server. Will that help in making apps for our XDAs? Interesting read anyways.
[General Topics] liquidsilver:
Here's my take.

There are two reasons for doing this.

First, as the world business climate changes and MS grows, antitrust issues are not going away. With a high probability of a democratic presidency, you can pretty well plan on more probes into MS business practices. EU regulators have already stated that they are going to be watching this one closely. Open architecture would place MS in a better position to defend themselves.

Second, "open" increases dependency. If you are a developer and you build your tools around the "open" MS architecture, where are you going to send your customers to buy base applications? In theory this would increase the number of units sold (breadth) but not increase the number of functions provided (depth). The net impact would be a much more stable revenue base for MS and not an "all or nothing" approach. Remember, Microsoft does not do ANYTHING that they do not believe contributes to their long term viability or profitability.
[Verizon Samsung Galaxy S8+ Questions & Answers] thepcgod:
Ever since I upgraded my Verizon S8+ to firmware G955USQS1AQI6 two months ago, I have been noticing decreased battery life (last night my phone lost 22% with aod turned off, most of the drain coming from Android System and Android OS) and more stuttering in general, which is why I have been scared to install anymore updates on my phone. I want to downgrade to the G955USQU1AQGL firmware, which was what I had before installing the crippling update. The question is, if I flash the firmware to my phone from my computer using Odin, will I lose any data?
[Verizon Samsung Galaxy S8+ Questions & Answers] GuyInDogSuit:
Yes, you will lose your data. Although I believe if you don't flash a CSC file, it won't wipe it. Don't take my word for it, though.
[Verizon Samsung Galaxy S8+ Questions & Answers] eregev:
In most software packages, there will be a CSC file and a CSC_HOME (or HOME_CSC) file. If you flash the file with "home" in it, it should retain your userdata. It will still say "erasing" as it wipes out your cache but when it reboots it should still have your data. Be careful, though. Rolling backwards without a wipe might cause even more issues/drain as it's not an official upgrade path.
[Nexus 5 Q&A, Help & Troubleshooting] Deadmau73:
Hello

I bought my Nexus 5 about a year ago , and everything was fine , suddenly i've been facing some problems with network . The problem is i have EDGE with a small x next to meaning that i have no internet , when i change it to H+ it works but it's so slow "1mbps or 40~100Kb in download" sometimes i get LTE with that small x next to it and no connection keeps loading , and sometimes there's no "x" but still with no connection.

So i thought that the problem is with 3g and 4g wires "black and white " , so i changed them with my friend's wires "he has a nexus 5 too" but it didn't fix the problem . So i went back to stock rom and nothing happened

-Tried different modems nothing happened

-Cleaned the whole motherboard with some cleaning tools nothing happened

-Checked the contacts below the "speaker" cover

-Changed my firend's back cover

-changed the sim , tried my sim in another phone and it was working fine

-changed the network operator

-chcked the APN

-did some secret codes to put it on LTE only and i get no network .

I did everything but i still have this problem

I was reading something in some forums and they said that i have change the network IC ! But i'm not sure about it , i mean if i have "no service" problem i haveto change the IC , but i could make calls and H+ is slow but no EDGE or LTE .
[Nexus 5 Q&A, Help & Troubleshooting] Deadmau73:
Up
[Google Pixel 2 Questions & Answers] carsonlake:
Is anyone else having an issue with WiFi calling disconnecting itself, especially overnight? I'm using T-Mobile and when the WiFi calling will stay connected, it works as it should. But often it either won't connect to WiFi calling when reconnecting to my home network, or most often, by the time I get up in the morning, it has fallen off WiFi calling and either has "no service" or is trying to use the virtually non existent T-Mobile signal in my home. I see no indication that it's losing the WiFi connection overnight as it's not reconnecting when I wake the phone up in the morning. I've tried prioritizing the device through my Netgear R7000 router, updating the T-Mobile account settings including the e911 address, making sure my WiFi calling settings on the phone are on and set to WiFi preferred, and rebooting into Safe Mode to make sure a third party app wasn't somehow causing the issue. (The same issue occurred in Safe Mode)

Any ideas?

Thank you all for any assistance you can provide.
[Google Pixel 2 Questions & Answers] BinkXDA:
Wish I had an idea. All I can tell you is I share in your misery as Wi-Fi Calling is inconsistent for me as well. While it works most of the time, sometimes it’ll drop off for no apparent reason. When it does, I can usually force Wi-Fi Calling to reestablish by putting the phone in and out of airplane mode.

FWIW, I use high-end Wi-Fi gear at home and a custom-built firewall.
[Google Pixel 2 Questions & Answers] sweteg:
Not sure if this applies to you but take a look here:

http://www.androidpolice.com/2017/10/24/google-inexplicably-removed-keep-wifi-sleep-toggle-pixel-2/
[Google Pixel 2 Questions & Answers] giant22000:
It's been my experience that Google's implementation is poor at best for WiFi calling. Constant disconnects are common and sometimes reboots are the only thing that will get it working again. It's been this way since it's inception on the Nexus devices back in the day.

On other devices such as Samsung and OnePlus WiFi calling just works. But it's always been hit or miss on Nexus/Pixel deives.
[Google Pixel 2 Questions & Answers] carsonlake:
Thank you all for chiming on the matter. It does make it a little less maddening to know it's not unique to my particular device or network setup as Google customer service would imply. Their solution was to have me send in my several week old "defective" device and get a refurbished one from them instead. Besides offering no explanation as to what kind of hardware fault could possibly cause this issue, I think it's ridiculous that someone making a warranty claim on a device less than a month old for a manufacturer defect would be sent a used replacement, particularly a device at this price point.

If it helps anyone, I've found if I switch the phone to airplane mode, and turn on WiFi while leaving airplane mode on, WiFi calling has been a bit more stable so far.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] cute_prince:
Since Xiaomi has not released the kernel sources yet, I'm currently trying to port Redmi Note 4 (mido) kernel sources for Mi A1. The porting process may succeed because both these devices are based on same architecture and comes from the same manufacturer. I have shared my kernel sources and those who wanna contribute may send pull request to the same. I'm currently looking for testers and those who wants to volunteer please reply in this thread.

You can test with stock rom or TWRP recovery.

Steps for testing:

1. Download TWRP recovery / boot image of stock rom.

2. Unpack it and replace the prebuilt kernel with our testing kernel.

3. Repack it and reboot phone to fastboot mode.

4. Type fastboot boot <repacked_image_name.img>

5. If it boots, post here the dmesg and other helpful logs ;)

Status [Working]

Boots

Display

WiFi

Touchscreen

RIL

Vibration

IR

Bluetooth

Sensors

SD card

MTP

Charging

XDA:DevDB Information

Linux kernel 3.18.31 for Xiaomi Mi A1 (tissot), Kernel for the Xiaomi Mi A1

Contributors

cute_prince, [MENTION=4693838]ur0[/MENTION]

Source Code: https://github.com/cuteprince/android_kernel_xiaomi_msm8953

Version Information

Status: Testing

Created 2017-12-02

Last Updated 2017-12-02
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] sooti:
Nah... doesn't boot.. while it's true that we share the same SD625 with many other xiaomi devices, there are other things to consider here... different display, camera, etc... not a kernel expert but just what i think...

anyway thanks for the attempt... i'm sure Xiaomi will release the sources soon, they might be waiting for Oreo since there are some specific commits that only apply to oreo, if so, they are actually kinda doing us a favor, since they always release the kernel once and never bother updating the sources since...
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] SevenSlevin:
Yes I think it works. I've done it and boot on system, in system I have different kernel.

The stock is from 17/11/2017 and yours is 02/12/2017.

edit: fingerprint doesnt work

camera doesnt work (it opens but see only black screen)

led doesn't work

edit2: link dmesg https://mega.nz/#!JcBjjCSA!_xzviwYuyRBfOmmpx8eDPa9Q8Uvwn_uRu0Usx-w8Y1g

I dont know how to put it here so I've used my mega account, if have problem I can use google driver or dropbox
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] sooti:
Odd... Didn't boot for me.. maybe I missed something

I see why the FP failed... the selinux is denied it, OP needs to set it to permissive
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] SevenSlevin:
Normally with this kernel Can I boot in Miui rom from redmi note 4??
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] sooti:
OK, got it to boot, great work OP! this could give us some lead until Xiaomi releases kernel source.

EDIT: so as I said earlier, selinux needs to be disabled for now... otherwise wifi, fingerprint, audio and LED don't work...
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Gtxinsane:
Wouldn't it make more sense to Port from Mi5X?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Yash98:
They are porting kernel source, Mi 5X kernel source isn't available either.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] cute_prince:
Great :). So it booted the stock rom. Did you tried disabling Selinux ? What about wifi, vibration, audio, bt, ir etc ? Are they working ?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] cute_prince:
Thanks for testing. Are they working (wifi, bt, ir, led etc) after disabling selinux ?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Gtxinsane:
Oh wow Xioami is really slacking huh.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Hellrazoraj:
This is very good progress..thank u OP.i will try this out but could you tell me how much it will affect the performance?? If there any noticeable difference? Cause as it's a Redmi note 4 kernel the battery in rn4 is 4000mah.

---------- Post added at 05:46 AM ---------- Previous post was at 05:45 AM ----------

They r slacking very badly..they have too many products rolled out & developer team size might not be that big it seems due to which many things r not happening in the right manner.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] abhinavgupta371:
Send a screenshot..
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] sooti:
Ya, no change. Selinux needs to be disabled on your end, add it to the defconfig.

WiFi, bt, it, led not working.

Vibrate and ril work
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] cute_prince:
Ok. I'll push another build. B/w if you have Cpu-z installed can you check whether sensors are working ?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] cute_prince:
No problem. This kernel is using device tree file of Mi A1. So device specific configurations like battery, display etc are of Mi A1 itself.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] SevenSlevin:
don't work:

wifi, audio, camera, fingerprint, led notification, audio in jack earphones

work:

ril, ir, bluetooth, vibrate, audio in bluetooth earphones

I havent done nothing on Twrp recovery, I've just changed kernel like on description.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] FrenzyR:
error while compiling

C drivers/staging/prima/CORE/WDI/WPAL/src/wlan_qct_pal_api.o

CC drivers/staging/prima/CORE/WDI/WPAL/src/wlan_qct_pal_device.o

CC drivers/staging/prima/CORE/WDI/WPAL/src/wlan_qct_pal_msg.o

CC drivers/staging/prima/CORE/WDI/WPAL/src/wlan_qct_pal_packet.o

CC drivers/staging/prima/CORE/WDI/WPAL/src/wlan_qct_pal_sync.o

CC drivers/staging/prima/CORE/WDI/WPAL/src/wlan_qct_pal_timer.o

CC drivers/staging/prima/CORE/WDI/WPAL/src/wlan_qct_pal_trace.o

LD drivers/staging/prima/wlan.o

LD drivers/staging/prima/built-in.o

LD drivers/staging/built-in.o

LD drivers/built-in.o

LINK vmlinux

LD vmlinux.o

MODPOST vmlinux.o

GEN .version

CHK include/generated/compile.h

UPD include/generated/compile.h

CC init/version.o

LD init/built-in.o

KSYM .tmp_kallsyms1.o

KSYM .tmp_kallsyms2.o

LD vmlinux

SORTEX vmlinux

SYSMAP System.map

make[2]: *** No rule to make target 'arch/arm64/boot/dts/msm8953-qrd-sku3-d2.dtb', needed by 'arch/arm64/boot/Image.gz-dtb'. Stop.

make[2]: *** Waiting for unfinished jobs....

OBJCOPY arch/arm64/boot/Image

/home/ramesh/li/kernel/xiaomi/msm8953/arch/arm64/Makefile:98: recipe for target 'Image.gz-dtb' failed

make[1]: *** [Image.gz-dtb] Error 2

make[1]: Leaving directory '/home/ramesh/li/out/target/product/tissot/obj/KERNEL_OBJ'

Makefile:145: recipe for target 'sub-make' failed

make: *** [sub-make] Error 2

make: Leaving directory '/home/ramesh/li/kernel/xiaomi/msm8953'

[ 20% 9987/49431] host C: libicuuc-host <= external/icu/icu4c/source/common/umapfile.c

[ 20% 9987/49431] host C: libicuuc-host <= external/icu/icu4c/source/common/usc_impl.c

[ 20% 9987/49431] host C: libicuuc-host <= external/icu/icu4c/source/common/utrace.c

[ 20% 9987/49431] host C: libicuuc-host <= external/icu/icu4c/source/common/utypes.c

[ 20% 9987/49431] host C: libicuuc-host <= external/icu/icu4c/source/common/wintz.c

[ 20% 9987/49431] Export includes file: -- /home/ramesh/li/out/host/linux-x86/obj/SHARED_LIBRARIES/libicui18n-host_intermediates/export_includes

[ 20% 9987/49431] Export includes file: -- /home/ramesh/li/out/host/linux-x86/obj/STATIC_LIBRARIES/libfdlibm_intermediates/export_includes

ninja: build stopped: subcommand failed.

build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed

make: *** [ninja_wrapper] Error 1

make: Leaving directory '/home/ramesh/li'

#### make failed to build some targets (12:37 (mm:ss)) ####

Build step 'Execute shell' marked build as failure

FTP: Current build result is [FAILURE], not going to run.

Finished: FAILURE
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] cute_prince:
Hi, you have to symlink arch/arm/boot/dts/msm8953-qrd-sku3-d2.dtb file to arch/arm64/boot/dts/msm8953-qrd-sku3-d2.dtb

While pushing my sources, git ignored that symlink thats why build is failing for you.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] cute_prince:
As [MENTION=4460995]sooti[/MENTION] suggested I'll build another image with selinux disabled. Lets see if selinux is causing the issue. Also can you test whether sensors are working using cpu-z app ?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Blackheart151:
was trying to compile source.

when i use the repo init command i got fatal: manifest 'default.xml' not available

i know its off topic. i tried looking around couldnt find any help.

can u let me know what is wrong..

sorry for the noob question..
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] ur0:
Fortunately for us, Xiaomi didn't bother stripping the kernel.

ffffffc000b1ee5c t max98927_readable_register
ffffffc000b1ef0c t max98927_volatile_register
ffffffc000b1efa0 T max98927_get_i2c_states
ffffffc000b1efc0 t max98927_dai_set_sysclk
ffffffc000b1f044 t max98927_right_channel_enable_set
ffffffc000b1f0d8 t max98927_right_channel_enable_get
ffffffc000b1f1a4 t max98927_left_channel_enable_set
ffffffc000b1f220 t max98927_left_channel_enable_get
ffffffc000b1f2e4 t max98927_feedback_en_put_r
ffffffc000b1f37c t max98927_feedback_en_get_r
ffffffc000b1f420 t max98927_feedback_en_put_l
ffffffc000b1f498 t max98927_feedback_en_get_l
ffffffc000b1f534 t max98927_mono_out_put_r
ffffffc000b1f5ec t max98927_mono_out_get_r
ffffffc000b1f694 t max98927_mono_out_put_l
ffffffc000b1f724 t max98927_mono_out_get_l
ffffffc000b1f7c0 t max98927_digital_gain_get
ffffffc000b1f820 t max98927_spk_gain_get
ffffffc000b1fd60 t max98927_i2c_remove
ffffffc000b1fe00 T max98927_wrapper_read
ffffffc000b1fe70 t max98927_mono_out_get
ffffffc000b1feec t max98927_reg_get_w
ffffffc000b1ffbc t max98927_boost_voltage_get
ffffffc000b20038 t max98927_boost_input_limit_get
ffffffc000b200b4 t max98927_spk_src_get
ffffffc000b20130 T max98927_wrapper_write
ffffffc000b2019c t max98927_feedback_event
ffffffc000b2023c t max98927_probe
ffffffc000b203e8 T max98927_wrap_update_bits
ffffffc000b20460 t max98927_dai_hw_params
ffffffc000b20790 t max98927_stream_mute
ffffffc000b208e0 t max98927_dai_set_fmt
ffffffc000b20a68 t max98927_reg_put.isra.9
ffffffc000b20aec t max98927_mono_out_put
ffffffc000b20b30 t max98927_spk_src_put
ffffffc000b20b74 t max98927_boost_input_limit_put
ffffffc000b20bb8 t max98927_boost_voltage_put
ffffffc000b20bfc t max98927_reg_put_w
ffffffc000b20cb8 t max98927_digital_gain_put
ffffffc000b20d28 t max98927_spk_gain_put
ffffffc000b20fb4 t max98927_i2c_probe
ffffffc000efb200 r soc_codec_dev_max98927
ffffffc000efb358 r max98927_regmap
ffffffc000efb418 r max98927_of_match
ffffffc000efb5a8 r max98927_i2c_id
ffffffc000efb5e8 r max98927_audio_map
ffffffc000efb628 r max98927_snd_controls
ffffffc000efbe48 r max98927_enum
ffffffc000efbee8 r max98927_feedback_switch_text
ffffffc000efbf08 r max98927_monomix_output_text
ffffffc000efbf20 r max98927_speaker_source_text
ffffffc000efbf40 r max98927_boost_current_limit_text
ffffffc000efc040 r max98927_boost_voltage_text
ffffffc000efc128 r max98927_dapm_widgets
ffffffc000efc5d8 r max98927_dai_ops
ffffffc001403a48 R __ksymtab_max98927_get_i2c_states
ffffffc0014229a8 r __kcrctab_max98927_get_i2c_states
ffffffc001453c17 r __kstrtab_max98927_get_i2c_states
ffffffc0014b714c t max98927_i2c_driver_init
ffffffc0014cf6b4 t max98927_i2c_driver_exit
ffffffc001536ef0 t __initcall_max98927_i2c_driver_init6
ffffffc0017842c8 d max98927_i2c_driver
ffffffc001784658 d max98927_dai
ffffffc0017849e0 d max98927_digital_tlv
ffffffc0017849f0 d max98927_spk_tlv
ffffffc001c235f0 b max98927.31669

I'm dumping these ranges so that I can analyze them later.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] cute_prince:
Great job dude :) So these are the methods used/needed by max98927 codec. B/w i have updated my git with open source max98927 driver. Need to check whether aol these methods are present.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] theandroidguy:
someone please try this rom too https://xdaforums.com/project-trebl...pment/experimental-phh-treble-t3709659/page38
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] ashu00:
I think Mi A1 doesn't have separate vendor partition which is required by project treble.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] asoni474:
I guess Google will release sources for xiaomi a1 coz it's an android one device so I think that sources are to be released by Google and not xiaomi
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] UltimateBlade:
And why u guessing it on this thread?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] asoni474:
I just shared my opinion
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] UltimateBlade:
This is not a thread to do that. U must follow rules bro.This is a development thread.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] asoni474:
Extremely sorry for that..!

I was not knowing that I couldn't comment here
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] brajesh.sharma87:
There is an exception with A1 as Xiaomi is handling all the updates for it. Don't know why google made this exception.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] sooti:
I read "due to the lack of updates older Android one devices faced"

Google probably can't commit the man power to maintain this device, they tried with the older Android one, for example the infinix series which shipped with 5.0.1 and only got updated to 6.0.1... and then support was barley seen and there were no monthly updated, only small security updated every 4-6 months.

Since google committed to at least 2 years of updates, it makes sense to let xiaomi handle R&D and Google support and distribute the updates and make sure xiaomi doesn't mess up too bad.