Related
My screen dims when the background is black or when there are only few images or texts present in the screen. Is it normal even though adaptive brightness is off? Please help.
I have the same question but with the Adaptive Brightness ON. Can anyone explain how adaptive brightness and screen dimming works in MI A2? I'm a little confuse.
@Calamity.exe
Just tested and I noticed the exact same behavior on mine as well.
I'm using a black background and have 'Adaptive brightness' in 'Settings' disabled.
I also went as far to disable 'Content Adaptive Backlight Settings' and this changed nothing.
Using a third-party tool like 'Lux Lite' helps somewhat but don't expect massive gains.
I did more research and found that many of the Xiaomi devices released in 2017 and onward use one the following display manufacturers:
Tianma OR BOE
The specifications differ (Screen Size/Resolution) but it appears the problems don't; specifically input latency, touch and color accuracy.
However I couldn't find any reports concerning 'Dark Mode' on other models (specifically the Mi 6x which uses built-in themes courtesy of MIUI) so my only hypothesis is a software-related bug.
REQUEST: Can ANYONE who switched their Mi A2 to a 6X confirm this behavior?
ADDENDUM: Keep in mind that none of these displays are high quality. So to achieve a specific price point, Xiaomi could have easily cut corners in both manufacturing AND software testing.
I found the solution. Posting in a moment.
Mi A2 Screen Dimming - No Longer Relevant
EDIT: Clarified explanation of problem statement, restructured text and remove third step.
Scenario:
In some circumstances, where a User has a black background/wallpaper, they may encounter unnecessary screen dimming after switching back from a bright background (e.g., colorful image/video) on the Mi A2.
'Content Adaptive Backlight' appears to be the issue and, as such, may need to be disabled.
Due to how Content Adaptive Backlight operates, this, in many cases, is the intended behavior.
NOTE: Before proceeding further, please ensure you have the latest software updates installed.
What is 'Content Adaptive Backlight'?:
'Content Adaptive Backlight' evaluates the content displayed (e.g., a black background) and actively reduces the amount of light to the display in order to save battery without diminishing quality of the image.
Possible Solution:
Disabling 'Content Adaptive Backlight' via ADB/third-party tool or uninstalling it with root permissions ISN'T the solution. Nor is 'Force Stop', 'Clear Data' or 'Clear Cache'.
We NEED to explicitly access 'Content Adaptive Backlight Settings' via an 'Activity'.
I will NOT be providing support/troubleshooting for ANY of the two available options. Step 1 & 2 are amongst the safest/easiest but you proceed at your own risk. If you are unfamiliar with them, I strongly suggest researching first before attempting. Alternately please use the XDA search as these functions/utilities have been covered in multiple posts. If I am, however, unclear in my instructions, please ask and I will better explain.
There are TWO steps we can utilize to disable 'Content Adaptive Backlight Settings':
1.) Third-Party Launcher (e.g., Nova)
See attached video (20181206_011734.7z). You will need 7zip to decompress.
2.) Using an ADB command
adb shell am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences
Once you've launched 'Content Adaptive Backlight Settings, uncheck 'Enable Content Adaptive Backlight', exit the application and restart your device.
I think it's Qualcomm Assertive Display that doing that.
A_H_E said:
Cause:
'Content Adaptive Backlight' appears to be the issue and, as such, needs to be disabled.
However, due to how Content Adaptive Backlight operates, it is actually behaving correctly.
So this isn't a bug.
'Content Adaptive Backlight' evaluates the content displayed (e.g., a black background) and actively reduces the amount of light to the display in order to save battery without diminishing quality of the image.
However disabling 'Content Adaptive Backlight' via ADB/third-party tool or uninstalling it with root permissions ISN'T the solution. Nor is 'Force Stop', 'Clear Data' or 'Clear Cache'.
We NEED to explicitly access 'Content Adaptive Backlight Settings' via an 'Activity'.
Resolution
I will NOT be providing support/troubleshooting for ANY of the three available options. Step 1 & 2 are amongst the safest/easiest but you proceed at your own risk. If you are unfamiliar with them, I strongly suggest researching first before attempting. Alternately please use the XDA 'Search' as these functions/utilities have been covered in multiple posts. If I am, however, unclear in my instructions, please ask and I will better explain.
There are three steps we can utilize to disable 'Content Adaptive Backlight Settings' with Nova being the preferred and easiest method.
1.) Third-Party Launcher (e.g., Nova)
See attached video (20181206_011734.7z). You will need 7zip to decompress.
2.) ADB
adb shell am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences
3.) Build.prop
Add ro.qualcomm.cabl=0 to the bottom, save the file and reboot the device.
Nova is preferred, followed by ADB and only if need be, build.prop (not preferred).
Once you've launched 'Content Adaptive Backlight Settings, uncheck 'Enable Content Adaptive Backlight', exit the application and restart your device.
Click to expand...
Click to collapse
@ A_H_E, Thanks for the response.
I've tried disabling it through Nova Launcher but the problem still persists. Should I still perform ADB and Build.prop?
I've also contacted the local Mi service center and they're saying that it's probably hardware (LCD problem).
Well I'm not sure I know exactly what the problem is but I tried the Nova method - CABL was enabled. When I disable it, I see no change. Also a I didnt notice my screem dimming when using my phone... I have stock A2 on 2nd November update Oreo. Can you point to situation, where this occurs? The phone only changes to black theme when I have black wallpaper. Also, is there CABL setting available ,,normal" way (e.g. from Settings menu)?
@Calamity.exe
No, there's no further steps you need to take. The only other suggestion I would recommend is removing the black wallpaper and seeing if the problem persists. If it does, head to the repair center.
@Infernus-cz
The issue, based on my testing, only occurs when a User has a black background (wallpaper). In Oreo, this will enable 'Dark Mode' (e.g., Drop-down Menu/Quick Settings changes from white to dark). When a User switches from a black background to a more colorful image, the dimness decreases however when they switch back to their black background, the screen dims again.
If you aren't seeing the problem, there's no need to disable CABL.
If you want to access CABL without Nova, use the following line in ADB to call the CABL settings:
adb shell am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences
You raise an interesting point. The issue MAY be dependent on the version of software (e.g., I'm using the October update and see it) but you are on the November release and haven't encountered it.
A_H_E said:
@Calamity.exe
No, there's no further steps you need to take. The only other suggestion I would recommend is removing the black wallpaper and seeing if the problem persists. If it does, head to the repair center.
@Infernus-cz
The issue, based on my testing, only occurs when a User has a black background (wallpaper). In Oreo, this will enable 'Dark Mode' (e.g., Drop-down Menu/Quick Settings changes from white to dark). When a User switches from a black background to a more colorful image, the dimness decreases however when they switch back to their black background, the screen dims again.
If you aren't seeing the problem, there's no need to disable CABL.
If you want to access CABL without Nova, use the following line in ADB to call the CABL settings:
adb shell am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences
You raise an interesting point. The issue MAY be dependent on the version of software (e.g., I'm using the October update and see it) but you are on the November release and haven't encountered it.
Click to expand...
Click to collapse
@ A_H_E
Removing the black wallpaper or any black background solves the problem (I guess). But whenever I open apps that have a default black background, the problem recurs.
I also have the November release like @Infernus-cz
Interesting.
On my device, once I disable CABL, I see the difference.
However, in your case, I need to understand if this is intended behavior or not.
If disabling the black background somewhat fixes the problem, we at least have a workaround.
Let me do some more digging on my end.
If anyone else has theories, I'd be interested in hearing them.
---------- Post added at 09:19 PM ---------- Previous post was at 08:48 PM ----------
For the interim, I've reached out to Xiaomi directly to inquire further. Will update when I have more details to share.
I don't think this is a software problem. The problem is that the screen doesn't employ local dimming technique for dark and light area of display. Therefore, the brightness of the screen is derived from the object displayed. So, while using dark theme, if any light image comes to any part of the screen, brightness of the whole screen is adjusted to display that lighter part.
This is more of a hardware condition than a software problem.
@kandarpjha
Do you have a source for this information? I've seen this exact problem referenced numerous times between the Mi A1 and Mi A2 on multiple forums but this is the more (most even) sensible answer I've encountered.
A_H_E said:
@kandarpjha
Do you have a source for this information? I've seen this exact problem referenced numerous times between the Mi A1 and Mi A2 on multiple forums but this is the more (most even) sensible answer I've encountered.
Click to expand...
Click to collapse
I don't have a source currently. But i wrote what i observed. I use all the apps in dark mode wherever available. This thing is happening in all the apps, especially in apps using pure black background than dark grey one. I'll post again if i find the source.
Xiaomi Response
Hello,
Writing to update thread.
@kandarpjha has the correct answer.
I am attaching a redacted email (personal details hidden) of a back & forth conversation I had with their Support department (their first response wasn't relevant nor helpful).
We now have an official explanation (although very short) and an excellent explanation given by kandarpjha.
Found a very good guide here https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-havoc-evolution-gsi-t4040607 posted by @ospeto
1) For fixing Bluetooth audio - my method is a little bit different than what [URL="https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-havoc-evolution-gsi-t4040607" @ospeto[/URL] posted.
I simply removed
Code:
/vendor/overlay/BluetoothResCommon.apk
in TWRP AFTER flashing GSI. That's it!! Bluetooth Audio is working fine with my headphone audio devices. The sound is no longer coming from the phone speakers. Mine is CN variant.
2) Always on display (AOD)
BEFORE TURNING ON Always on display - I noticed the AOD stays at the same position, I am worried about the burn-in issue if the position isn't dynamic/movable. If someone knows if it is ok to use it? Thanks
Download the attachment https://forum.xda-developers.com/showpost.php?p=75630470&postcount=38
move the
Code:
framework-res__auto_generated_rro.apk
file to /vendor/overlay and chmod 0644 in TWRP
You will find AOD option in - Display->Lock screen display->Always on
There seems a bug if you enable both Always on and New notifications, disable "New notifications" to keep AOD on without issues. Lift to check phone is not working for me.
Thanks a lot!
Maybe something to fix FP sensor?
Thanks for the share!
PROXIMITY SENSOR FIX
Warning :-
I AM NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER YOU MAY CAUSE TO YOUR DEVICE WHILE USING OR RANDOMLY EXPERIMENTING WITH THIS FIX, DONT TINKER WITH DEVICE IF U DONT KNOW WHAT U R DOING.
1. What is this fix about?
Ans. Poco F3 has an issue, that while calling screen turns on/off randomly due to proximity sensor malfunction , so to fix it I made a Tasker profile which disables proximity sensor when call is continuing, and re-enable it when call is discontinued.
2. Why to re-enable proximity sensor?
Ans. Without proximity sensor phone will have issues with deep sleep function, so to avoid it proximity sensor is to be re-enabled.
3. Any draw back of this fix?
Ans. Yes, you have to manually turnoff and turn-on the screen during call.
4. Minimum requirements for this fix?
Ans. a. Tasker app
b. Any mi device which shipped with Android 10 or 11 out-of-box , if u have any other device u can test this fix if it works , most probably it would since m using sysfs interface shell script implimented by linux kernel, which is quite universal  both miui n custom roms are compatible;
c. Root;
d. Working mind 
5. PROCEDURE :-
0. Download the "proximity_fix2.XML" from below given link n copy it to "/storage/emulated/0/Tasker/configs/user" ;
1. Go to Tasker app;(all permission to Tasker app should already be given)
2. At the right corner of Tasker app u will see menu button (3 dot button) press it;
3. Go to "Data";
4. Go to "Restore";
5. Now select the "proximity_fix2.xml" that u have downloaded;
6. Press back button repeateadly till the app is closed;
7. That's it from here on my Tasker profile will take care of things;
6. Resources
A. XML file :-
{Mod edit}
B. Tasker app
{Mod edit}
PROXIMITY SENSOR FIX
Warning :-
I AM NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER YOU MAY CAUSE TO YOUR DEVICE WHILE USING OR RANDOMLY EXPERIMENTING WITH THIS FIX, DONT TINKER WITH DEVICE IF U DONT KNOW WHAT U R DOING.
1. What is this fix about?
Ans. Poco F3 has an issue, that while calling screen turns on/off randomly due to proximity sensor malfunction , so to fix it I made a Tasker profile which disables proximity sensor when call is continuing, and re-enable it when call is discontinued.
2. Why to re-enable proximity sensor?
Ans. Without proximity sensor phone will have issues with deep sleep function, so to avoid it proximity sensor is to be re-enabled.
3. Any draw back of this fix?
Ans. Yes, you have to manually turnoff and turn-on the screen during call.
4. Minimum requirements for this fix?
Ans. a. Tasker app
b. Any mi device which shipped with Android 10 or 11 out-of-box , if u have any other device u can test this fix if it works , most probably it would since m using sysfs interface shell script implimented by linux kernel, which is quite universal  both miui n custom roms are compatible;
c. Root;
d. Working mind 
5. PROCEDURE :-
0. Download the "proximity_fix2.XML" from below given link n copy it to "/storage/emulated/0/Tasker/configs/user" ;
1. Go to Tasker app;(all permission to Tasker app should already be given)
2. At the right corner of Tasker app u will see menu button (3 dot button) press it;
3. Go to "Data";
4. Go to "Restore";
5. Now select the "proximity_fix2.xml" that u have downloaded;
6. Press back button repeateadly till the app is closed;
7. That's it from here on my Tasker profile will take care of things;
6. Resources
A. XML file :-
{Mod edit}
B. Tasker app
{Mod edit}
Perform this at your own risk. You might LOSE all data on your phone.
( I'm not responsible for any damage to your device )
This is a tutorial for the best configurations to get the best from the GSI roms on the Xiaomi 11T Pro
If you are searching on a tutorial on how to install GSI roms on Xiaomi 11T Pro you can check this post
The reason why I made this guide is that there is no custom rom currently for Xiaomi 11T Pro and the only way to get custom roms is by installing a GSI rom and try to tweak with it to get it working.
List of contexts
A- Phh Settings
1. Fix broken audio
2. Fix Whatsapp audio
3. Turn on Double-Tap-To-Wake-Up
4. Enable 120Hz
5. Fix Auto-Brightness
6. FIx SMS/MMS
B - Other Ways
1. Installing Dolby Atmos
2. Fix volume steps
3. Fix Vibration and Haptics
4. Fix 5G if you have LTE working
5. Fix LTE/4G
6. Fix Always-On-Display (With Low Dim fixed!)
A- Phh Settings
Open Phh Treble Settings from settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1) To fix broken audio go to Qualcomm features and make sure "Disable soundvolume effect" is on
2) To fix broken audio on Whatsapp, Telegram, SIgnal go to Qualcomm features and make sure "Use alternate audio policy" is on
3) To fix Double tap to wake feature go to Xiaomi features and check "Enable DT2W"
4) To enable 120hz go to Misc features and click on "Force FPS" and select "1080*[email protected]"
5) To fix auto brightness go to Misc features and check on "Force alternative backlight scale"
6) To fix SMS go to IMS features and click on "Install IMS APK for Qualcomm vendor" then install the APK
B - Other Ways1) Install Dolby Atmos using Magisk by flashing this file
2) Fix the volume steps by flashing this file using Magisk
3) To fix vibration you need to reboot your phone after you have applied the changes on section A and search for "vibration" on settings and click on "Ring Vibration"
Then deselect all the switches and then select them all
4) If LTE/4G is working for you. You can flash this file using Magisk to get 5G
5) If LTE/4G is not working go to Settings < Network and Internet < Sims < Preferred Sim 1 or 2 < Access point names and click on the "+" icon on top corner of the screen
Then manually enter your sim's provider APN and click on the three points and save -You can check it from your provider's website-
Do the same for MMS and save it. You will suppose to have mobile data working!
6) FIx Always-On-Display
You can now fix always on display and set the statusbar height to a value that covers the hole punch by flashing this magisk module by diogotc.
Know IssuesCurrently the issue that I am still experiencing with GSI roms are:
1. GCam can record up to 1080p 60fps. 4K is not working.
2. The proximity sensor is not working always especially in AOD, So I recommend to disable DT2W (A- Phh Settings step 3).
Credits:
Google -AOSP-
Phhusson -Phh Treble Settings-
diogotc -Making an overlay to solve some problems in the GSI roms for this device-
Me -Making this tutorial-
What are bugs? Fast charging is working? How is battery?
Edoardo001 said:
What are bugs? Fast charging is working? How is battery?
Click to expand...
Click to collapse
Battery life is good, Fast charging works nearly as Miui and bugs are minimilise.
TheRomFan said:
Battery life is good, Fast charging works nearly as Miui and bugs are minimilise.
Click to expand...
Click to collapse
And how is the câmera driver/quality?
You can use Gcam from this thread
But the only issue is you can record video up to 1080p 60fps
Vibration working ? and 4k record in gcam working ?
MIUI13 or MIUi 12 base ?
morpheus620 said:
Vibration working ? and 4k record in gcam working ?
MIUI13 or MIUi 12 base ?
Click to expand...
Click to collapse
I am using Miui 13 as base. Yh this is another issue 4k doesn't work
TheRomFan said:
I am using Miui 13 as base. Yh this is another issue 4k doesn't work
Click to expand...
Click to collapse
Thank you for information. Some questions:
1. Haptic works?
2. You said "minimilise bags" – which bags?
3. What ROM do you use?
PS: where can I find step by step instruction to setup GSI for 11T Pro?
Thank you so much
dimashorokhov said:
Thank you for information. Some questions:
1. Haptic works?
2. You said "minimilise bags" – which bags?
3. What ROM do you use?
PS: where can I find step by step instruction to setup GSI for 11T Pro?
Thank you so much
Click to expand...
Click to collapse
1. Yes I explained how to fix in the post above
2. I just saw 3 or 4 bugs such it bugs a bit when I change from/to dark mode
3. Pixel experience plus
4. Here is the link for how to install GSI
hello what gcam do you recommend? app + config?
also, i can't get root. i flahsed patched boot.img and in magisk manager it says ramdisk yes but installed no. i tried multiple boot.img files but with no luck. base miui 12.5.0.5 global.
also the autobrightness adjustes the brightness too high
i don't have xiaomi settings in phh treble settings.
aod works but brightness is very very low i can barely see anything
can you help me with some of my issues? i'm using pixel experience plus as well
Link for Dolby Atmos module is off... Could you update it please? Thanks
lecomiquelin said:
Link for Dolby Atmos module is off... Could you update it please? Thanks
Click to expand...
Click to collapse
Thank you.
Here is the new link
TheRomFan said:
Thank you.
Here is the new link
Click to expand...
Click to collapse
Could you test ANX camera?
Ultra-wide video is a very important for me
dimashorokhov said:
Could you test ANX camera?
Ultra-wide video is a very important for me
Click to expand...
Click to collapse
Unfortunately it doesn't work as the developer has stopped updating it since October
But ultra wide works fine with gcam if use with its config file
TheRomFan said:
Unfortunately it doesn't work as the developer has stopped updating it since October
But ultra wide works fine with gcam if use with its config file
Click to expand...
Click to collapse
Okey. Is there any GCam with working ultra-wide video?
I know that photo is working, but video on ultra-wide sensor not
hello i have a question how can i fix the charging so that it is fast charging i have the crdroid gsi s20 fe thank you
Ailton2541 said:
hello i have a question how can i fix the charging so that it is fast charging i have the crdroid gsi s20 fe thank you
Click to expand...
Click to collapse
Sorry I don't know the answer of your question. You need to ask on the Samsung S20 FE thread as this is only for Xiaomi 11T Pro.
Hi, thanks a lot for your tutorial, it fixed most issues!
However, I've noticed two things:
The proximity sensor doesn't seem to be working. I've used the Sensors app to check it, and it always says 5.0cm no matter what. This means the Always On Display is always on, and doesn't turn off if it's in your pocket or face down on a table (which at night is annoying, since the light bleeds out from the transparent case).
The auto brightness fix makes the Always On Display very very dim, which renders it pretty useless since it can't be seen at an angle. I've had to avoid doing that fix for that reason, but it's very annoying that now auto brightness is just not working correctly.
It'd appreciate if anyone could find a fix for these issues. Everything else works perfectly (except for Android Auto, which I found a fix, see below).
Also, since Android Auto isn't installed as a system app, it shows "Connection error 22" when you plug it into the car and doesn't work. The fix is to convert it to a system app. I've used Lucky Patcher for this, but it was a bit sketchy, so if you find another way, go for it (and reply here so I know next time). EDIT: TheRomFan mentioned below that you can use the Systemizer Magisk Module.
Since it might be relevant, I'm using Pixel Experience Plus Slim.
diogotc said:
Hi, thanks a lot for your tutorial, it fixed most issues!
However, I've noticed two things:
The proximity sensor doesn't seem to be working. I've used the Sensors app to check it, and it always says 5.0cm no matter what. This means the Always On Display is always on, and doesn't turn off if it's in your pocket or face down on a table (which at night is annoying, since the light bleeds out from the transparent case).
The auto brightness fix makes the Always On Display very very dim, which renders it pretty useless since it can't be seen at an angle. I've had to avoid doing that fix for that reason, but it's very annoying that now auto brightness is just not working correctly.
It'd appreciate if anyone could find a fix for these issues. Everything else works perfectly (except for Android Auto, which I found a fix, see below).
Also, since Android Auto isn't installed as a system app, it shows "Connection error 22" when you plug it into the car and doesn't work. The fix is to convert it to a system app. I've used Lucky Patcher for this, but it was a bit sketchy, so if you find another way, go for it (and reply here so I know next time).
Since it might be relevant, I've using Pixel Experience Plus Slim.
Click to expand...
Click to collapse
Yes I know as this is an Generic System Image with phh's patch to make it work on maximum android phones.
Some of these issues can be reported to Phh and he will try fix it.
So I guess we will have to wait untill he releases an update to fix these issues
For system apps you can systemizer magisk module to install apps as system.
I've created an overlay for this device, which fixes the status bar not covering the entirety of the cutout and the brightness of the AOD being low (you still need to enable the alternate brightness scale on settings).
I've opened a PR on the phh's overlays repo, but it still hasn't been merged.
Meanwhile, you can use this overlay by flashing the attached Magisk module, or building it yourself from the PR.
In case someone is interested (even if it's not for this device), I'll leave here the build instructions (these are not required, you can just use the attached zip file).
Spoiler: Overlay Build Instructions
Keep in mind I'm using Linux, so build instructions might be a bit different for Windows/Mac.
Start by cloning my repository in the mi11tpro branch:
Bash:
git clone https://github.com/diogotcorreia/vendor_hardware_overlay.git -b mi11tpro
Then build the overlay for this device (alternatively you can build all of them by omitting the folder):
Bash:
./build/build.sh Xiaomi/Mi11TPro
This will generate an APK that'll be written to build/treble-overlay-xiaomi-mi11tpro.apk.
You can now put this in the attached Magisk module (unzip it first), by replacing the APK there with the built APK.
Then, zip it again, and make sure the root of the zip file is not a folder but the actual files of the module.