[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] monojp:
Sorry for responding that late, I had to switch back to stock but today I installed your ROM again.

Bluetooth was apparently already fixed, thx

Encryption was fine from the beginning, I just did not understand it fully because Android was asking for the password later than I was used to

Yes. I just use those apps with the built-in speaker and without any headphones. And after the first loud sound or noise apparently the mic gets turned off completely and the other person cannot hear me any more

I was debugging the mic problem some more, got logcats (with the app jitsimeet) and found out something interesting I guess that I want to confirm over the following days.

logcat while using jitsimeet: https://gist.github.com/monojp/2829cb26063430fca16811662888ad83

I noticed those ACDB (Android Audio Calibration Database) related messages.

Then I pulled `etc/acdbdata` from the stock vendor image and pushed it to my phone after remounting vendor read-write and rebooted. And apparently my problem is now gone (to be verified over the coming days) :)

logcat after I changed acdbdata while using jtisimeet: https://gist.github.com/monojp/089bd3125665dae07cab3543b6cbbd30

acdb files from stock (from /vendor/etc/acdbdata)

001e0dbe57e0feb44d75d5543ae9ef8a ./MTP/MTP_General_cal.acdb
10d5e3d91804ec53f59c1436d8d1b01a ./MTP/msm8953-tasha-snd-card/MTP_WCD9335_General_cal.acdb
179db6a7267fda1f1e9a8ad9be25c9f0 ./MTP/MTP_Speaker_cal.acdb
305d6815d79258a3757c1098f59a5cbf ./QRD/QRD_Bluetooth_cal.acdb
32616bdf5229da9cee58e872c84967ba ./MTP/msm8953-tasha-snd-card/MTP_WCD9335_Headset_cal.acdb
33eb4d3040f1200849b3ce4fd8c9a073 ./QRD/QRD_General_cal.acdb
36e1939d3756c148df0106d98dfb4778 ./MTP/msm8953-tasha-snd-card/MTP_WCD9335_Bluetooth_cal.acdb
55cbe456a1de8e66c68891c014006653 ./QRD/QRD_Speaker_cal.acdb
5cc2faa81a8893c045ad2eb68ab5d921 ./MTP/MTP_Bluetooth_cal.acdb
6c52a6114ed5419bb7d08b2d902029e5 ./QRD/QRD_Global_cal.acdb
77cbfd7475ca8217bb86d567bd57c88c ./MTP/MTP_Global_cal.acdb
7d5a54e74983eee6666609db963c51ae ./QRD/QRD_Headset_cal.acdb
89360f721969b2fd99f2f1a826aca3fe ./MTP/msm8953-tasha-snd-card/MTP_WCD9335_workspaceFile.qwsp
8d5f440b2d5813e832ea17399f247b81 ./MTP/msm8953-tasha-snd-card/MTP_WCD9335_Handset_cal.acdb
92f70de9f61474520ed41b2c26e36389 ./MTP/MTP_Handset_cal.acdb
966c693ca617fc5fa34556fa7a61810f ./MTP/MTP_Hdmi_cal.acdb
a261f01073b43e19c9f3b9f31a81e5ec ./MTP/msm8953-tasha-snd-card/MTP_WCD9335_Global_cal.acdb
b058c3fca156e634e256cf1367094fd9 ./MTP/msm8953-tasha-snd-card/MTP_WCD9335_Hdmi_cal.acdb
b36fc8ad9735088e087ce107d91df3c5 ./MTP/msm8953-tasha-snd-card/MTP_WCD9335_Speaker_cal.acdb
c3781eae2acd46b6658c4430f510d025 ./QRD/QRD_workspaceFile.qwsp
cc2b53564632dd6ba99253d1ead25cfb ./MTP/MTP_workspaceFile.qwsp
d1d23022793342d504bc14d0de5f9010 ./adsp_avs_config.acdb
deedc3980f604ca2fa25f95c9dac910b ./QRD/QRD_Handset_cal.acdb
e219656b042a6b489ca5895bbcb73c88 ./MTP/MTP_Headset_cal.acdb
f52917c10f6ed842a6c4647e5ba01f76 ./QRD/QRD_Hdmi_cal.acdb

acdb files from this rom

001e0dbe57e0feb44d75d5543ae9ef8a ./MTP/MTP_General_cal.acdb
179db6a7267fda1f1e9a8ad9be25c9f0 ./MTP/MTP_Speaker_cal.acdb
305d6815d79258a3757c1098f59a5cbf ./QRD/QRD_Bluetooth_cal.acdb
33eb4d3040f1200849b3ce4fd8c9a073 ./QRD/QRD_General_cal.acdb
55cbe456a1de8e66c68891c014006653 ./QRD/QRD_Speaker_cal.acdb
5cc2faa81a8893c045ad2eb68ab5d921 ./MTP/MTP_Bluetooth_cal.acdb
6c52a6114ed5419bb7d08b2d902029e5 ./QRD/QRD_Global_cal.acdb
77cbfd7475ca8217bb86d567bd57c88c ./MTP/MTP_Global_cal.acdb
7d5a54e74983eee6666609db963c51ae ./QRD/QRD_Headset_cal.acdb
92f70de9f61474520ed41b2c26e36389 ./MTP/MTP_Handset_cal.acdb
966c693ca617fc5fa34556fa7a61810f ./MTP/MTP_Hdmi_cal.acdb
c3781eae2acd46b6658c4430f510d025 ./QRD/QRD_workspaceFile.qwsp
d1d23022793342d504bc14d0de5f9010 ./adsp_avs_config.acdb
deedc3980f604ca2fa25f95c9dac910b ./QRD/QRD_Handset_cal.acdb
e219656b042a6b489ca5895bbcb73c88 ./MTP/MTP_Headset_cal.acdb
f52917c10f6ed842a6c4647e5ba01f76 ./QRD/QRD_Hdmi_cal.acdb

The logcat says "ACDB-LOADER: ACDB -> Not correctly initialized!" though, so maybe I just broke something and disabled a non-working feature or so.. :)

UPDATE: well looks like my "fix" breaks normal incall volume without speaker. It is always at max now.. but at least this is somewhat related, maybe @reujea0 has another idea