Related
Flashed this CM10 based ROM yesterday. Found that 2 key features that were baked into system in previous release are missing from this release.
First is Overclocking/underclocking of CPU through Settings->Performance. Now this options is missing altogether from the list.
Though this drawback can be mitigated by using Trickster Mod or similar app.
And second one is the option to "customize auto-brightness settings". There are some apps in the store that promise similar utility, but they never worked for me. This option wasn't needed if auto-brightness levels were not as super low as they are in this release.
Anyone noticed this?
Diljinder said:
Flashed this CM10 based ROM yesterday. Found that 2 key features that were baked into system in previous release are missing from this release.
First is Overclocking/underclocking of CPU through Settings->Performance. Now this options is missing altogether from the list.
Though this drawback can be mitigated by using Trickster Mod or similar app.
And second one is the option to "customize auto-brightness settings". There are some apps in the store that promise similar utility, but they never worked for me. This option wasn't needed if auto-brightness levels were not as super low as they are in this release.
Anyone noticed this?
Click to expand...
Click to collapse
1) I removed the CPU Settings because they're limited and don't work with this device as they should (Tegra needs a different kind of love).
2) I removed the auto brightness settings because they rely on the light sensor exposed to the rom... which we don't have. All the auto brightness is handled in the kernel (on ICS as on CM) so every operation in that menu is basically a no-op.
For 1, use CPU Adjuster or Trickster Mod from the market and you get a load more options that are guaranteed to work.
And for 2, check my kernel thread. You can mod the auto-brightness settings via sysfs, or wait a bit until wfd adds that feature to Kowalski Manager
Hope this clarifies why those two things are gone
pengus77 said:
1) I removed the CPU Settings because they're limited and don't work with this device as they should (Tegra needs a different kind of love).
2) I removed the auto brightness settings because they rely on the light sensor exposed to the rom... which we don't have. All the auto brightness is handled in the kernel (on ICS as on CM) so every operation in that menu is basically a no-op.
For 1, use CPU Adjuster or Trickster Mod from the market and you get a load more options that are guaranteed to work.
And for 2, check my kernel thread. You can mod the auto-brightness settings via sysfs, or wait a bit until wfd adds that feature to Kowalski Manager
Hope this clarifies why those two things are gone
Click to expand...
Click to collapse
Thanks for clarification. I appreciate it.
I've been reading here and there, and I've come upon that thread where you can enable DCI_P3 calibration for your display on your OP3T, only on OOS thou.
Why isn't it supported on any ROM where the Display Model doesn't even turn up, and why haven't any ROM Devs implemented it?
Cheers!
because not all 3/3T support dci-p3 color scheme ..
Only S6E3FA5 panel ID that supporting dci-p3
twentyfourinc said:
because not all 3/3T support dci-p3 color scheme ..
Only S6E3FA5 panel ID that supporting dci-p3
Click to expand...
Click to collapse
It's a simple thing to have the ROM detect the ID of the Panel, and then have ROM to choose whether to show the option in Calibration Settings under Settings.
thes3usa said:
It's a simple thing to have the ROM detect the ID of the Panel, and then have ROM to choose whether to show the option in Calibration Settings under Settings.
Click to expand...
Click to collapse
If you think simple enough, so make yourself...
It's added through the kernel not the ROM, Ex and Blu spark both have it in OOS and custom kernels. Lineage also have it in their kernels too.
It works really well in LineageOS, I like the not so over saturated coloring in this mode, it's really nice to the eyes.
A Magisk module is available for it. https://forum.xda-developers.com/showpost.php?p=72842349&postcount=11
@thes3usa DCI_P3 color profile is available in official Resurrrection Remix rom for OP3T
You can with this one:
https://forum.xda-developers.com/on...ment/rom-zenity-resurrection-remix-n-t3551384
It's in Live Display settings. Don't change the kernel though, or you won't have the option anymore.
Installed the Aug.31 build of Lineage on my 3T yesterday, and it's an option there in Live Display settings too. There also seems a bug where the selected colour profile reverts to default every time you turn the screen off and on though :/
Apparantly the dci-p3 should be available using Vertex OS. But since i dont have the supported panel(wierd, since i bougth it in June 2017, so probably didnt get the newer display).. But it should be possible to change even on the old display ?
EDIT:
I found out that i have the correct display which ends on a5, so it should be able. But cannot find the necessary files in the sys/devices/virtual/graphics/fb0 folder....
So my Mi5 has a severe screen burn-in (image retention, ghosting, or whatever you wanna call it) and I've been looking for solutions for sometime, for all the ROMs.
So I suppose this thread will be useful to you guys too.
** The permanent solution is to replace the display **
** I will be not responsible for any damages caused to your handset by flashing custom ROMs and/or custom kernels or by any other means. I didn't develop any of these nor I have any affiliation with them. This is just a guide. Try these at your own risk. **
Solution 1 - Live display feature in LineageOS
This is the easiest and hassle free solution. Just flash LineageOS and use the Live display feature and adjust the RGB values to 90.
LOS 14.1
LOS 15.1
Solution 2 - KCAL
This is a free colour correction tool developed by @savoca.
To use this you must have a supported kernel & root. This supports AOSP ROMs (but didn't try it on every ROM though ...)
Just install the apk grant access , turn on 'colour service' & 'set on boot' options. Then adjust the RGB values to 220-230 (more or less depending on the severity of your burn-in) and save the changes.
KCAL official XDA thread
Solution 3 - Colour Changer Pro
This is a paid app. but it's the only app that I found which supports MIUI with stock kernel. It also requires root.
select a custom profile and adjust the RGB values to 220-230 (more or less depending on the severity of your burn-in) and turn on the profile.
Only problem that I found is that if you install a new app it resets the values to default so you have to activate it again.
The free version give you pro features for a few days so you can try it before you buy it.(adjusting RGB requires pro version)
Get it on google play
** I didn't test the effect on battery life when using KCAL and Colour Changer Pro but according to my experience they are very insignificant **
I hope this will be helpful to you guys as burn-ins are a widespread feature ( ugh ! .. sorry, problem) in mi5 devices.
credits,
@bgcngm & LOS team - LineageOS
@savoca - KCAL
Omega Centauri Software - Colour Changer Pro
This is my fix from 4pda, please sindicate a link to the author...
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.
Just as the title says I'm just asking those of you who are rooted and a quick brief explanation of why? Even those not rooted I would also encourage to Express your reasonings.
Personally I'm not rooted right now because I don't have TWRP and Google pay is iffy at the moment but I would love to root for substratum, adaway, and Viper sound mods.
Thanks guys.
Google Pay works with a simple fix in Termux app - no issues with it unless you use EdXposed.
I'm rooted for modding, theming, ability to install custom kernel, Button Mapper capabilities, Swift Backup, ability to fix device ambient EQ, ability to mod Active Edge, ability to use Lawnchair with QuickStep recents. mod accent colors to cool neon colors, iYTPB YouTube mod.. Substratum (not using currently but will be soon), ability to hide navbar.. the list goes on.
I'm rooted because this is a Google device with open source code and active development so modding and customizing my device is easy, fun, and I am able to see the changes being made without the blind guesswork and hackery involved in trying to develop for so many half-baked source release devices.
rooted so I can use;
- AdAway
- ViPER4Android
- EdXposed
As previously mentioned, Gpay is working fine.
And you don't "need" TWRP to root the P4XL.
sharpz811 said:
Just as the title says I'm just asking those of you who are rooted and a quick brief explanation of why? Even those not rooted I would also encourage to Express your reasonings.
Personally I'm not rooted right now because I don't have TWRP and Google pay is iffy at the moment but I would love to root for substratum, adaway, and Viper sound mods.
Thanks guys.
Click to expand...
Click to collapse
wrongway213 said:
Google Pay works with a simple fix in Termux app - no issues with it unless you use EdXposed.
I'm rooted for modding, theming, ability to install custom kernel, Button Mapper capabilities, Swift Backup, ability to fix device ambient EQ, ability to mod Active Edge, ability to use Lawnchair with QuickStep recents. mod accent colors to cool neon colors, iYTPB YouTube mod.. Substratum (not using currently but will be soon), ability to hide navbar.. the list goes on.
I'm rooted because this is a Google device with open source code and active development so modding and customizing my device is easy, fun, and I am able to see the changes being made without the blind guesswork and hackery involved in trying to develop for so many half-baked source release devices.
Click to expand...
Click to collapse
Thanks for your input guys but I'm a little confused through googling I see a magisk module that supposedly does all the necessary scripting in the background and then like mentioned here I see manually editing via termux. So I'm just wondering what is the exact procedure or is there a thread I can't seem to find with the exact instructions?
sharpz811 said:
Thanks for your input guys but I'm a little confused through googling I see a magisk module that supposedly does all the necessary scripting in the background and then like mentioned here I see manually editing via termux. So I'm just wondering what is the exact procedure or is there a thread I can't seem to find with the exact instructions?
Click to expand...
Click to collapse
I recommend this Termux fix, believe spaceman860 from DU is the first I saw using this but could be wrong, copying this from Telegram
Gpay fix v2
1. Install Termux app and open the app
2. Type pkg install sqlite hit enter and let it install.
3. Type su hit enter
4. Copy and paste this then hit enter
am force-stop /data/data/com.google.android.apps.walletnfcrel && chmod 777 /data/data/com.google.android.gms/databases/dg.db && /data/data/com.termux/files/usr/bin/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';" && chmod 444 /data/data/com.google.android.gms/databases/dg.db
5. Reboot
I'm rooted mainly so I can install a custom kernel. I always end up rooting for one small reason or another.
Because i can
Adaway for now.
I root for,
AdAway
YouTube Vanced
Active Edge Mod
Custom Fonts
Themes (Swift Installer and Substratum)
Viper4Android
Centre Clock Mod
Build prop edits (just to change volume steps, really)
Screen recorder with internal audio recording
iOS Emojis
Some Tasker stuff that requires root
Swift Backup
SD Maid Pro
Main feature is custom kernel... It can realy provide a boost
@rickysidhu_ can you give me a link to the screen recording app please?
un9a7y said:
@rickysidhu_ can you give me a link to the screen recording app please?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.orpheusdroid.screenrecorder
- AdAway
- ViPER4Android
- EX Kernel
Yes, rooted.
Because I use:
Custom Kernels (battery saving)
BlackenedMod (battery saving)
AdAway (no ads!)
YouTube Vanced (YouTube without ads and other cool features!)
Custom Themes (just a better colour palate for OEM colours in styles)
Viper4Android (awesome sound on speakers/earphones)
Centre Clock Mod (purely aesthetic)
TiB (backing up and restoring apps)
I haven't rooted since the first pixel. Haven't needed to. Adguard premium does what I need along with YouTube vanced.
I'll never bother messing with my phones again.
Sent from my Google Pixel 4 XL using XDA Labs
I'm rocking a P3xl, but I rooted for...
Advanced Charging Control module - allows me to control how the battery is charged - (ie lower the max charge to 80% and other things that should increase overall battery life)
Active Edge Mod (mostly standard settings, but can squeeze to take a picture when the camera is open instead of having to press the shutter button on the screen. This really helps when trying to hold the phone with one hand).
Viper4Android
AdAway
YouTube Vanced
ExperimentalX kernel - great kernel and it has high brightness mode (HBM) support too. (Like the Pixel 4 series, the 3a series has a max brightness that is actually lower than the screen is capable of. HBM overrides this and truly maxes the brightness. It really helps when using the phone outside in bright sunlight).
With the Pixel 4 series, I think being able to map the Soli gestures for other things might be very interesting too.
FINGERFACE!!!!!! How can Google release a flagship model with no FP sensor before getting all the banking/security apps to support the Face-unlock API???
They don't call it the bleeding edge for nothing and something had to come first; there would never be support without need and there is no need until someone creates it. Realistically Google has used their power over the ecosystem to require support and it's going to be ubiquitous in the near future. For now, some of us have to bleed a little bit...
krabman said:
They don't call it the bleeding edge for nothing and something had to come first; there would never be support without need and there is no need until someone creates it. Realistically Google has used their power over the ecosystem to require support and it's going to be ubiquitous in the near future. For now, some of us have to bleed a little bit...
Click to expand...
Click to collapse
No need to bleed, just root and install EdXposed and Fingerface.
No longer feel the need to root. System is working just fine and I'm using DNS66 from f-Droid with AdAway hosts. It's working absolutely fine without rooting.
Sent from my Google Pixel 4 XL using XDA Labs