Android 9 - Brightness Flicker Solutions for All CPU - Android General

Hello XDA, I've recently purchased an Android 9 device and like so many others, I've found the new Android 9.0 Intelligent Adaptive Brightness to be a massive headache when it's turned Off and manually adjusted below [50%] brightness.
I have tried for Literally months to track down the cause of this issue on so many various handsets and CPU manufacturing companies.
To begin with, it seemed like this was not a Device Dependent problem, but a problem with Android 9's Changes into Artificial Intelligence for Brightness Control - Mostly because it was a problem being found across-the-board..
How could it be a device problem and not a Firmware problem ?
It seemed very convincing that the cause was Android 9 because people have multiple reports online of this happening after updating the firmware, but not previously happening on any Prior Firmware.
After a while, I remembered having this problem Years Ago, When Android Devices did not have a Hardware Light Sensor - "Luckily I remembered what the cause was back then, it was called Content Aware Backlight"
The idea was that the Phone or Tablet doesn't need a Light Sensor, it can adjust the screen based on Content.
However, this feature provided to be More Problematic than Useful in Android 2.3 days, so they Removed the feature in Further builds up to Android 8.1
After Android 8.1 these features have enabled again to target Battery Consumption.
The Adaptive Brightness features are enabled permanently to enhance the Adaptive Battery AI.
Remember that these are not Simple A.i ... These are Advanced Neural Networks.
So enough with the background, here's the Juice.
Let's look at a Qualcomm CPU Device,
• Qualcomm
A Qualcomm Android uses a brightness feature called CABL "Content Aware Backlight", this feature is Fighting with Android 9's Adaptive Brightness feature and causes a Flickering Effect for the lack of a better word.
What About Others like MTK & Intel ?
• Intel
An intel device also has a built-in feature that fights with Androids Adaptive Brightness, called "Intelligent Backlight Control"
• MediaTek
MediaTek CPU's also have a feature called AAL "Advanced Adaptive Lighting"
To disable these features, is to make your Firmware Android 9.0 Compatible.
DISABLING GUIDES AND TIPS,
UNKNOWN DEVICE GUIDE,
Hi, I bought this phone six months ago and until today I struggled with the adaptive brightness. Even in dark rooms I had very high brightness if I set to adaptive brightness.
Click to expand...
Click to collapse
Today I found out how to solve. I had to edit a file located in /persist/sensors/registry/registry. If you have root access you have to edit the file tcs3701_platform.als.fac_cal so that it looks like that:
Code:
{"tcs3701_platform.als.fac_cal":{"owner":"sns_tcs3 701","scale":{"type":"flt","ver":"1","data":"0.905 537"},"bias":{"type":"flt","ver":"0","data":"0.000 000"}}}
If you aren't able to acces that file you can go to TWRP, copy it to internal storage, modify it with a text editor, go back to recovery and restore the file.
Before touching anything a persist partition backup is highly recommended.
GENERIC DEVICE DISABLE,
You've certainly noticed that when you're outside the screen brightness goes at max level and contrast is over saturated.
It comes from adaptive display, personally I don't like that so I've found a way to disable it in build.prop
Open build.prop and edit this:
Code:
ro.vendor.display.ad=1
Change value to 0, save and reboot
NO ROOT ?
People have reported that Disabling or Clearing Data for "Device Health Services" in Settings > Apps helps significantly... however I did not have improvements myself.
QUALCOMM
Seems that this service controls black vibrance and overall screen sharpness. In lg g2 forum i ve read that this is the dynamic screen contrast. I ve added those line in my build prop, changed everything to 0, but i cant notice any difference.
Code:
ro.qualcomm.cabl=1
hw.cabl.level=Auto
persist.qcom.cabl.video_only=1
If disabling this in Build.prop doesn't work, or you would like to try disable without ROOT ACCESS ..
• Open Settings
• Open Apps
• Open Content Aware Backlight App
• Select DISABLE to disable the Application
ROOT ?
• Try a removal of the APK File that handles Content Aware Backlight in Either System/App or System/Priv-App
More for G2 - https://forum.xda-developers.com/showthread.php?t=2466268
MEDIATEK CPU & AAL
I have tried multiple AAL Disabling methods in Build.prop and nothing works.
The only Sure-fire way to Remove or Disable it is by Removing the AAL Binary File
Code:
system/system/bin/aal
on my device, system is actually a subdirectory of system - so I write system/system/ as an example. Your device may use
system/bin/aal
And disable using build.prop Props,
Code:
ro.vendor.mtk_aal_support=0
persist.vendor.sys.mtk_app_aal_support=0
I'm still looking for Samsung and Speadtrum Props.
Please remember that this is a common issue found on everything... Personal Computers, Smartphones and T.V's.
I've found reports online for both Intel's Intelligent Backlight in products like T.V's, Laptops, Desktops, Smartphones.
The same goes for CABC, CABC is the most notorious for both Android and PC User's, Dominating the Google Search Results for Adaptive Brightness Issues.
CABC or Content Aware Brightness Control, is an absolutely disgusting design that they should have fired someone over a long time ago... The feature has reported up to 15% battery consumption improvement, however user's have reported up to 100% of headaches from viewing the screen are attributed to uncontrollable brightness and flickering - especially while gaming.
A PC Guys Write-up,
http://www.anandtech.com/show/8983/dell-xps-13-review/5

Related

[APP] Custom Auto Brightness - tame that auto brightness.

Here it is, a simple app to set auto brightness curve. It works on it's own, so disable system auto brightness first.
It doesn't have any widgets, only brightness curve setting in the app
Works with actual backlight, so does help battery even on LCD screens.
You may even not set anything, just enable the service, adjust the curve as you like and go. Or you may play with detecting values from your sensor and setting sensor readings filter etc.
The app is in early stages, so bugs may arise. They will be fought upon.
Android Market: market://search/?q=pname:com.nnevod.loggraph
Android Market Web: https://market.android.com/details?id=com.nnevod.loggraph
Current version: 0.83
I'm not currently providing the APK here, but if anyone really needs, I would.
Internet and coarse positioning permissions are used for ads. Other are required to read sensors / adjust values.

App optimization - What is it & why does Smart Manager change settings UI?

Most of you will be aware that a new "app optimization" feature was added to a recent 5.1.1 based firmware update.
I've been trying to research exactly what this does because Samsung have not updated their user manual (you can access this via the user manual widget) to cover this new feature. After searching online, I've come to the conclusion that I'm not the only one who isn't sure what this feature does and there's a lot of incorrect information out there.
Below is some examples of what I've read:
It's Samsung's implementation of doze - I think this is incorrect as doze is a system wide state that uses sensors and screen off information.
Someone on AC forums was told by a Samsung employee that for example, it will make taxing games black and white so they don't require so much processing power - I really don't think this is the case.
It's Samsung's implementation of app standby - I think this is the most likely.
Does anyone have any concrete evidence as to what this setting actually does?
Furthermore, I've noticed that the "app optimization" implementation will change depending on if you have Smart Manager enabled or disabled. Not only that, but the battery sub menu layout (settings > battery) is also different depending on Smart Manager running or not. Has anyone else noticed this?
From what I can gather, the "app optimization" feature is there regardless if Smart Manager is enabled or disabled, but you can only manually select wether an app is optimised or not. Smart Manager appears to only provide automation of the process by monitoring which apps have not been used for x number of days and then changing the optimisation setting for each app for you.
Based on your screenshots, system apps can now be optimized by default?
Tricks25 said:
Based on your screenshots, system apps can now be optimized by default?
Click to expand...
Click to collapse
Second screen is the 'Optimization Screen' under Setttings > Battery > Battery Usage > Battery Optimization. First one is from the 5.1.1 update, and the second is only present in Marshmallow Beta.
I don't think it's exactly an App Standby, as this keeps the apps 'unoptimized' if they have background services. Samsung's optimization only takes days since last usage for determining if an app should be optimized. Also, I think Samsung's optimization is more aggressive, like Greenify, an it shuts down apps shortly after user lefts them.
Oh, and it seems that you can't explicitly turn App Standby for an app, like you can do it with the Samsung alternative. Putting an app on/off on App Standby only activates App Standby for that app (If conditions are met) or disables it completely.
bregan90 said:
Second screen is the 'Optimization Screen' under Setttings > Battery > Battery Usage > Battery Optimization. First one is from the 5.1.1 update, and the second is only present in Marshmallow Beta.
I don't think it's exactly an App Standby, as this keeps the apps 'unoptimized' if they have background services. Samsung's optimization only takes days since last usage for determining if an app should be optimized. Also, I think Samsung's optimization is more aggressive, like Greenify, an it shuts down apps shortly after user lefts them.
Oh, and it seems that you can't explicitly turn App Standby for an app, like you can do it with the Samsung alternative. Putting an app on/off on App Standby only activates App Standby for that app (If conditions are met) or disables it completely.
Click to expand...
Click to collapse
You're not quite correct on the screen shot front. All screenshots were taken from Android 6.0, the reason they're different is one was taken with Smart Manager running and the other was taken with Smart Manager disabled via Package Disabler.
What it does is that after an app has not been started for 3 days (this is configrable), it freezes (disables) it.
This is really problematic for small apps acting as unlocker of a main app and not supposed to be launched by user, as it prevents the main app to communicate with the unlocker app (bindServices() fails), preventing license verification to work.
This cancer acting in the back of apps used to only be possible on root devices, but Samsung generalized to mainstream devices.

Tasker Guide to Auto Brightness

Follow this Guide at Your Own Risk.
I am not responsible for bricked devices, lost data, thermonuclear war or getting fired for missed alarm or whatever happens to your device by following my instructions​
I have been a long time Lux user. But what I found, that Lux is bugged with some compatibility checking wakelock. Also, Lux uses screen overlay which is a problem. For a lot of system features in Marshamllow loaded S7edge alerts that an screen overlay has been detected and this must be disabled. Therefore, I configured Tasker (Paid software available on android market), my most favourite automation tool for android. So, where is the catch?
Process:
1. Disable Auto Brightness and Create a New Task in Tasker.
2. Select Action Category > Display > Display Brightness
3. Then Set Brightness Level value at 15 (Or whatever lowest brightness you're comfortable at)
4. Below, set if parameter as "%LIGHT < 20 (Or whatever brightness level you want for 15% of brightness)
Repeat Process 2-4 to create multiple steps for your brightness level adjustments.
Now, in Tasker profiles, you add a new profile to be triggered by "Events > Display > Display On and assign the created Task.
You can also adjust your brightness on per app basis when you want a specific app to have a set brightness level by following the same process except when creating a profile you have to select "Applications" and assign the created Task or a similar task created separately.
Update:
I have attached a Tasker configuration xml to get started with.
Please note that this guide will setup auto brightness to be adjusted on device wake. You can hook this update to any event as you want.
Tested working on SM-G935FD. Should work on any Tasker compatible android device with Light Sensor.
What's wrong with auto brightness?
drummerman said:
What's wrong with auto brightness?
Click to expand...
Click to collapse
+1.... I think that Android is great because of the customization option available, but sometimes people just over-customise.
There is nothing wrong with Auto-Brightness, and in case you have a problem with it, just override it using the bar on the notification panel.
Still, although I will never use it, this is a nice tutorial.
drummerman said:
What's wrong with auto brightness?
Click to expand...
Click to collapse
Default Auto brightness implemented in S7 edge is buggy. here on xda you can check it out.
Teio said:
+1.... I think that Android is great because of the customization option available, but sometimes people just over-customise.
There is nothing wrong with Auto-Brightness, and in case you have a problem with it, just override it using the bar on the notification panel.
Still, although I will never use it, this is a nice tutorial.
Click to expand...
Click to collapse
But this is not over-customization, at least in my opinion. It means taking more control. I have been using (and many other people are) Lux to adjust the auto brightness behavior which polls sensor data at a specific period, whenever the screen is on. But if you use this guide, it will give you a auto brightness customization solution without polling light data from sensor all the time. even though the sensor will be on, it will not be active. I am not sure that it will impact on battery or not, but it gives me more control over the brightness adjustment.
cheers!
izephyr said:
Default Auto brightness implemented in S7 edge is buggy. here on xda you can check it out.
But this is not over-customization, at least in my opinion. It means taking more control. I have been using (and many other people are) Lux to adjust the auto brightness behavior which polls sensor data at a specific period, whenever the screen is on. But if you use this guide, it will give you a auto brightness customization solution without polling light data from sensor all the time. even though the sensor will be on, it will not be active. I am not sure that it will impact on battery or not, but it gives me more control over the brightness adjustment.
cheers!
Click to expand...
Click to collapse
Good point. Though I don't see the issue on my device, Auto-Brightness works as I expect it to. It gets very bright on sun, and dim on dark rooms (though I would like it to go a tiny bit dimmer to be perfect). Will this Task auto adjust or you need to select the desired brightness yourself?
Teio said:
Will this Task auto adjust or you need to select the desired brightness yourself?
Click to expand...
Click to collapse
You can select the desired brightness level according to your comfort.
Teio said:
Good point. Though I don't see the issue on my device, Auto-Brightness works as I expect it to. It gets very bright on sun, and dim on dark rooms (though I would like it to go a tiny bit dimmer to be perfect). Will this Task auto adjust or you need to select the desired brightness yourself?
Click to expand...
Click to collapse
According to http://www.greenbot.com/article/303...brightness-fixes-a-major-mobile-headache.html and this: http://www.displaymate.com/Galaxy_S7_ShootOut_1.htm you can customize according to your liking .. hadn't tried it though all I need is the AOD to shine a lil bit dimmer
The drawback to this is that it only adjusts brightness based on the level when you turn the screen on. If the ambient light changes, the screen brightness won't change with it.

OnePlus 7 - OxygenOS 11 stable - Issues

Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Hem981,
I can confirm #7 is an issue on mine as well.
The power menu is an android 11 change not an OOS change.
I upgraded from OOS 10 to OOS 11 no wipe and don't seem to experience the other issues that you are having, except the obvious changes they made to the firmware. Have you tried clearing the dalvik-cache and rebooting? Mine was super buggy before doing this, but then again I just upgraded without wiping.
One issue I've personally noticed is the cell radios were a lot better on OOS 10, and I'm assuming that is the cause of the battery life to be worse.
Another that could be due to doing some debloating is when I take a screenshot and the little preview pops up in the bottom right corner if i click on it the UI will freeze after clicking back. The Nav buttons still work, like you can click on recents and the recent menu appears, back and home work but the screen is frozen otherwise until I force a reboot.
Yeah, I've tried factory reset and then wiping dalvik-cache... The performance was better before i performed the factory reset, i think. Anyway, there are quite a few games/apps where the performance impact is easily visible. Also, the power button thing is an Android change, but i really hoped OnePlus to have done something to make it more easily accessible (OOS is not pure Android). I couldn't find the issue with the cell radio you mentioned (as I've tried in areas in which i already had poor reception, and the performance was what was expected). Anyway, I really hope some of these (at least the performance, battery drain and the brightness slider issue) will be fixed soon over updates.
(For me, the SOT has gone down from 9.5 hours to 7 hours under similar use cases)
Yeah SOT has definitely taken a hit on mine as well, standby time seems the same. I also have noticed that the screen brightness needs to be set higher for the same brightness as OOS 10. The cell radio sometimes seem normal, but most of the time they are about 5-10 dBm higher at my house. I'll probably give a clean flash a try this weekend to see if it clears up.
One more issue found:
Weird red tint on screen auto dimming
The whole display has a weird red tint just before the device is about to lock/turn off screen after the timeout, when the display dims. It is easily noticeable if you have a white screen displayed. It only happens if you have set the brightness slider to anything other than the bare minimum (even a single step above the minimum brightness is able to replicate this issue)
I found something interesting: issue #3, the brightness slider being slow to respond to changes, seems to be fixed by disabling all animations from developer options. Should the window animator duration scale have any effect on the responsiveness/quickness of display brightness adjustment? I think that's stupid.
Also, I am starting to thing we need something like 0.1x duration scale for the animations (all animations on Android, or at least OOS), because honestly, with each new implementation, the animations are being too slow that it degrades the whole experience. 0.5x feels a bit better, but i really think something like 0.4x would match the animation speed of android 10.
You forgot to mention the vibration motor effect which has deteriorated since the update. The device now feels like any other cheap device.
It's kinda weird in my situation, just upgrading from 10.3.8 using an old version of xXx NoLimits to 11.0.0. The phone was super buggy when I first installed, but after rooting, wiping the delvik cache, debloating, removing the xXx module, and time to settle in the only issues I have are the screenshot popup, and the lower cell signal which I'm sure is causing a hit on battery life.
I was going to reinstall this past weekend, but for the time and inconvenience it's not worth the time compared to the minor issues I have.
Edit: Even the screen resolution seems normal now.
Again, don't know if this is an issue for anyone else (and i don't think OnePlus is going to change this): While everything else became bigger on the phone, the buttons/number keypad for typing in the screen lock pin became too small.
Hem981 said:
Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Click to expand...
Click to collapse
Hi! Oneplus 7 ownere here.
Try to answer all the points:
1) i don't notice any difference between OOS10 and OOS10 on the heat of the phone
2) I don't know for the gaming performance but i don't play any games...overall, the performance are good, no system lags or freeze BUT I have the same issues with the notification...when i tap a notification, I often have delay, maybe it's just the animation but I remember the same issue on a Oneplus 8t that i tried for 20 days in last November
3) same issue here, very annoying
4) not just you, have same issue
5) battery drain is the same in my case, in standby maybe is less than before
6) me too, but maybe they change this as they planned?
7) yes, same thing. i changed the DPI from developer options too
8) no crashes here
9) this is an Android 11 change from Google, maybe they don't want your device to power off ahahah
10) never had this problem luckily
11) don't know, never tried this
12) i noticed this after reading this point, true on my device too
13) i faced the same issue on the notification sound, the other things works fine
14) me too, if i wanted One UI, i would have bought a Samsung...
15) sometimes happens to me, maybe it's bad ram management?
16) this is ridicolous, why they doesn't remove this app??
17) never tried
I also have an issue on the vibration. Now it's HORRIBLE, i have disabled because it's unusable
So, this is my question: change phone or rollback on android 10?
There's one more addition to the list: Always on display sometimes seems to override the notification lockscreen privacy settings. I have some notifications put as "view private content only when unlocked", but the notification contents are visible just when it arrives on the always on display (though it's content is hidden in the actual lockscreen)
I've reported almost all of these bugs, and hopefully we will see new updates fixing most of these.
Can someone on OOS 10 on OnePlus 7 confirm if the "style preferences" settings in sound settings is greyed out while the output is phone speakers (or no other sound output devices connected)?
New hotfix patch OTA rolling out now...
Here is what's fixed and what's not:
1,2 : Yet to test
3: Not fixed
4:Fixed
5: Yet to test
6: No changes
7: No changes(or not easily noticeable maybe?)
8: Not encountered any "ghost" app crashes yet
9: No change
10: DC Dimming is not back, so no change
11: Not fixed Is it that hard to remove 'headset' text from the UI?
12: Don't know if it's because my eyes adjusted to it, but it seems a bit better now
13: Not yet tested
14: What can I say?
15: Fixed
16: The ghost of Google Play Music still remains
17: Not fixed
Edits: Nothing much is fixed
Performance: Marginal improvements
SoT/Battery: Even worse. Getting almost half the SoT I got on OOS 10 under similar use case and network/tenperature conditions
Ghost app crashes reduced a lot (that might be the only fix) , but is not completely gone (saw that 1 or 2 times)
Haptics is still as bad as before
I'm just worried about this weired bug which has rendered my parallel whatsapp very difficult to use to share media. Any fix for this is highly appreciated - https://forums.oneplus.com/threads/whatsapp-media-problem.1411292/
Thanks and regards
OOS11 - Stable
I have no problems on my device until now (for games I dont know why I do not play)
I noticed, because I have tried both roms(beta4 & stable).Open Beta4 has better "battery management" than stable! Αs strange as it may seem but is a real for me..
Well yes .Battery drain higher than openbeta4
wifi works fine to 5ghz band & generally my device works quite well so far. Patience is needed and all problems will be fixed...
https://postimg.cc/gallery/YtQpVDm
After the recent OS 11 update ,the media in my device ( photos and videos) not being shown properly in Whatsapp. Some of the videos and pictures which I've already deleted in the gallery are appearing again only in whatsapp in unsupported file format.
I'll be glad if someone confirms that it's a bug in OOS 11.0.2 and that my phone is not the only one which is affected.
I'm using WhatsApp and Parallel Whatsapp. Also have setup a Work/Office profile on my phone.
Does anyone have any solution to this issue?
Thanks and regards!
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
itdiestoday said:
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
Click to expand...
Click to collapse
Try wiping cache from recovery
Update 11.0.1.1
I feel like this is a big joke.
Even more battery drain (yes, i did a factory reset).
Brightness slider issue still not fixed.
Performance still degraded (but i think there is a little bit of improvement)
Not sure about Wifi issues as i never had them.
Weird red tint on screen dimming
Still many ugly and inconsistent ui elements
Color profile is back to being broken (the yellow tint returned)
Update: I've started having the wifi disconnection issues, after 11.0.1.1 update. This is way too annoying.

[DISCONTINUED] Google Pixel Experience - Optimization Guide

THIS IS A SUGGESTED CONFIGURATION FOR GOOGLE DEVICES​OUT OF SUPPORT/CLOSED​RECOMMENDED SETTINGS​To Start With​- Factory Reset (RECOMMENDED)
- Remove SIM before first boot
- Follow setup OFFLINE (DON'T restore anything during setup)
- Reboot, insert SIM then continue setup online.
System Settings​- Auto-Rotate: DISABLED
- Notification Bubbles: DISABLED
- Notification History: DISABLED
- Synchronization: DISABLED (turn it off again when not in use).
- Location: DISABLED (turn it off again when not in use).
- Display Resolution: FHD/1080p
- Advanced features: ALL DISABLED
- Motions and Gestures: ALL DISABLED
- Auto download System Update over Wi-Fi: DISABLED
- Bluetooth Scanning (Location services): DISABLED
- Usage & Diagnostics: DISABLED
- Advertising ID: RESET & DELETE
- System Sound/Vibration feedback: OFF
- Network Mode: 4G
- Always On Display (AoD): DISABLED
- Dark Mode: ENABLED
- Trust Agent: DISABLED
- Turn Screen On: DISABLED
- Suggestions/Recommendations: ALL DISABLED
- Gestures/Shortcuts: DISABLED.
- Adaptive Battery: DISABLED
- Adaptive Connectivity: DISABLED.
Google Settings​- Nearby connections: DISABLED
- Devices: DISABLED
- Nearby Share: DISABLED (turn it off again when not in use).
- Nearby Share Notification: DISABLED
- Location Services: ALL DISABLED
Developer Options:​- Allow window-level blurs: DISABLED
- Background Check: DISABLED
- Suspend execution of Cached apps: ENABLED
- Animation scale (3 entries) : x0.5
- Logger Buffer Sizes: OFF
- Predictive Back Animations: ON
Camera Settings​- Turn off location permission for the camera app.
- Face Beautification: DISABLED
- Video Stabilization: DISABLED
- Video Resolution: 4K30
- Social share: DISABLED.
- Google lens suggestions: DISABLED
Advanced
- Show dirty lens warning: DISABLED
- Store videos efficiently: DISABLED
Google Play Store Settings​- Google Play Protect: DISABLED
- Autoplay: DISABLED
- Auto Update Apps: DISABLED
- App Installation Optimization: DISABLED
Google Chrome Settings​Settings
- Page Preloading: DISABLED
Chrome Flags
- Smooth Scrolling: ENABLED
- Parallel Downloading: ENABLED
Social Media Apps Settings​- Theme: AMOLED/DARK
- Autoplay videos: DISABLED
- Log out of all Old sessions.
- Delete old logged in devices.
Spotify Settings​- Canvas: DISABLED
- Gapless: ENABLED
- Normalize volume: DISABLED
- Device broadcast status: DISABLED
- Spotify connect in the background: DISABLED
Add "Sync" Quick Toggle​- Download Quick Settings
- Enable it under "System no root"
- Add the tile normally through the edit button
GENERAL FIXES​Diagnose Your Problem​- Go to Device care, battery, check your battery usage. If nothing shows, it's battery leak.
Fix Battery Leak (IMPORTANT)​- Go to Permission Manager, enable "Show system apps" and check for any excess permissions, especially hardware like location, camera or nearby devices.
Fix Battery Calibration​- Use your phone normally till it dies off automatically.
- Plug it into the charger and leave it charging for 2h while it's still off.
- Turn it on, calibrate the battery then unplug your phone and use it normally until it dies again.
- Plug it into the charger and leave it charging for 2h while it's still off.
- Turn it on, calibrate the battery again and unplug it, enjoy
Fix Google Apps Battery drain​Go to Settings, Apps. Enable "Show system apps" then look for each of:
- Google Play Store
- Google Services Framework
- Google Play Services
- Android System WebView"
Uninstall Updates, Clear data & Cache, Force Stop, Reboot, update and follow setup.
Fix Camera Experience​- Wipe Data & Cache, reboot to Safe mode, do it again, then reboot normally.
Fix OLED Burn-in/Ghosting​- Download LCD Burn-in Wiper
- Disable Auto-brightness & set Brightness to 100%
- Leave on for at least 1 hour
Fix Speaker crackling​- Download Speaker cleaner
- Set your volume to max
- Put your phone face down & launch
Remove Ads System-Wide​Go to settings, connections, more connections settings, look for Private DNS.
- dns.adguard-dns.com or dns.adguard.com
- Close all apps then reboot.
Apps Alternatives​- Apps list
What's wrong with Adaptive Battery? AFAIK it just slows down charging through the night when u have alarm turned on.
reas0n said:
What's wrong with Adaptive Battery? AFAIK it just slows down charging through the night when u have alarm turned on.
Click to expand...
Click to collapse
That's adaptive charging you're describing
What kind of battery improvement/screen on time can we expect from these optimizations? I'm currently getting 6-8h of screen time or 40~ hours of standby with 4~ hours of screentime.
devilsshadow said:
What kind of battery improvement/screen on time can we expect from these optimizations? I'm currently getting 6-8h of screen time or 40~ hours of standby with 4~ hours of screentime.
Click to expand...
Click to collapse
All kinds actually, from smoother phone to longer battery life.
I wouldn't follow this guide, especially since it recommends malware (ccleaner hasn't been good for a looooong time).
There's also no need for draining your battery until the phone turns off multiple times to "calibrate" it, and disabling stuff that many people find useful (like location for Maps)... going through ADB to turn off settings available through the UI is also strange... Seems like snake oil.
Reserved
rydare said:
I wouldn't follow this guide, especially since it recommends malware (ccleaner hasn't been good for a looooong time).
There's also no need for draining your battery until the phone turns off multiple times to "calibrate" it, and disabling stuff that many people find useful (like location for Maps)... going through ADB to turn off settings available through the UI is also strange... Seems like snake oil.
Click to expand...
Click to collapse
Then don't .
rydare said:
I wouldn't follow this guide, especially since it recommends malware (ccleaner hasn't been good for a looooong time).
There's also no need for draining your battery until the phone turns off multiple times to "calibrate" it, and disabling stuff that many people find useful (like location for Maps)... going through ADB to turn off settings available through the UI is also strange... Seems like snake oil.
Click to expand...
Click to collapse
Agreed. CCleaner is garbage malware and most of the tips cripple your device's capabilities. One example from the rec'd settings... Turn off WiFi/Bluetooth scanning/GPS. Sure you'll save battery.. at the expense of losing location results. Also many apps require GPS permissions so this suggestion isn't even really practical.
Battery Calibration Pro? Hasn't been updated since 2017. If you want to know what's going on with your battery get a relevant app like Ampere. And why do we even need to "calibrate" our batteries?
And many of the apps listed in PixelSafe.txt marked as "bloatware" are definitely not safe to uninstall..
com.android.omadm.service
com.google.android.ims
com.google.android.carrier
Good luck using your phone without these.
And if AppControl OP is suggesting to use to uninstall the listed apps is doing so by modifying system partition say goodbye to passing safetynet.
100% do not use anything suggested here lol
bobbarker2 said:
Agreed. CCleaner is garbage malware and most of the tips cripple your device's capabilities. One example from the rec'd settings... Turn off WiFi/Bluetooth scanning/GPS. Sure you'll save battery.. at the expense of losing location results. Also many apps require GPS permissions so this suggestion isn't even really practical.
Battery Calibration Pro? Hasn't been updated since 2017. If you want to know what's going on with your battery get a relevant app like Ampere. And why do we even need to "calibrate" our batteries?
And many of the apps listed in PixelSafe.txt marked as "bloatware" are definitely not safe to uninstall..
com.android.omadm.service
com.google.android.ims
com.google.android.carrier
Good luck using your phone without these.
And if AppControl OP is suggesting to use to uninstall the listed apps is doing so by modifying system partition say goodbye to passing safetynet.
100% do not use anything suggested here lol
Click to expand...
Click to collapse
Im going to call bull**** on you here
Ive had omadm disabled for over 2 months with zero issues
OMA DM server development cooperation in the air, mobile phones and wireless devices to provide remote configuration, configure and update device management (DM) client enables operators and handset manufacturers outbreak system dependencies between DM tight.
if you can explain exactly why something should not be disabled and why it will cause a bootloop or failure to boot great.
if you are just blowing smoke out your ass because you think your phone should wipe your ass for you and everyone else.
then go away you are not helping the discussion.
i also dont think any non opensource app should be used as snake oil to fix issues unless we know exactly how it works.
people should always do their own research on everything, XDA is not for sheep following a guide word for word because they don't understand why things work or don't work
bobbarker2 said:
Agreed. CCleaner is garbage malware and most of the tips cripple your device's capabilities. One example from the rec'd settings... Turn off WiFi/Bluetooth scanning/GPS. Sure you'll save battery.. at the expense of losing location results. Also many apps require GPS permissions so this suggestion isn't even really practical.
Battery Calibration Pro? Hasn't been updated since 2017. If you want to know what's going on with your battery get a relevant app like Ampere. And why do we even need to "calibrate" our batteries?
And many of the apps listed in PixelSafe.txt marked as "bloatware" are definitely not safe to uninstall..
com.android.omadm.service
com.google.android.ims
com.google.android.carrier
Good luck using your phone without these.
And if AppControl OP is suggesting to use to uninstall the listed apps is doing so by modifying system partition say goodbye to passing safetynet.
100% do not use anything suggested here lol
Click to expand...
Click to collapse
PLEASE, READ OP CAREFULLY BEFORE COMMENTING. THANK YOU​- CCleaner does the job, also, uninstalling it right after you're done using it is a key step.
- Doesn't matter when has it been updated, it does the job.
- I actually have a pixel 6, and those apps listed are ALREADY UNINSTALLED for me, and i'm running fine as you can see .
- Bootloader locked, no root, and you're worried about system partitions ? And safetynet too ?
- OMADM was shipped disabled for me, i never needed to take it out.
- Literally NO ONE forced you to do what i said, all of those are suggestions, feel free to do, or not do them.
- You don't like my suggestions ? Skip them, go away, don't come posting nonsense, please, i want to keep my thread clean of bull****.
- 100% nobody asked your opinion.
nutzfreelance said:
Im going to call bull**** on you here
Ive had omadm disabled for over 2 months with zero issues
OMA DM server development cooperation in the air, mobile phones and wireless devices to provide remote configuration, configure and update device management (DM) client enables operators and handset manufacturers outbreak system dependencies between DM tight.
if you can explain exactly why something should not be disabled and why it will cause a bootloop or failure to boot great.
if you are just blowing smoke out your ass because you think your phone should wipe your ass for you and everyone else.
then go away you are not helping the discussion.
i also dont think any non opensource app should be used as snake oil to fix issues unless we know exactly how it works.
people should always do their own research on everything, XDA is not for sheep following a guide word for word because they don't understand why things work or don't work
Click to expand...
Click to collapse
As i already stated in the past post, those apps are already uninstalled on my phone and i don't have any problem. Everything is working as intended, but with less heat, faster charging and better battery life
OMA DM and it's associated apps are frozen out of the box (for my carrier anyway). Can't speak for all carriers.
Lol I just copy/pasted from where I saw in the txt to uninstall com.google.android.ims and
com.google.android.carrier.. my bad if I included one that can be removed "safely".
Though how would it be beneficial to battery life to remove a frozen system app?
You missed my point. There are apps in the txt that should never be removed or even be suggested to be removed because without them, you no longer have a phone.
This entire battery optimization guide is full of bad advice at best and changes that will break your phone. What's the point of having a phone with amazing battering life but no functionality?
Don't believe me than go ahead and disable/remove com.google.android.ims and the other ims services. See how well sms/mms/telephony work through an IP network.
Literally NO ONE forced you to do what i said, all of those are suggestions, feel free to do, or not do them. You don't like my suggestions ? Skip them, go away, don't come posting nonsense, please, i want to keep my thread clean of bull****.
Click to expand...
Click to collapse
XDA is a community with lots of people who don't have in-depth knowledge of Android. Some people may not know better.
So as a community, we also want to stop the spread of bad information. You can't post a guide for better battery life and then say "but no one look into them or question them they work 100%". That's not how things work.
And with that not wasting more time on this thread. Best of luck!
To everyone coming here, please, if you don't have serious issues with your battery, never ever drain it to 0. And over all, never ever try to start a phone with a 0% battery.
A battery is always better at 40-60%, not more, not less (you can find a lot of battery care articles on the web explaining why).
This calibration method is probably a way to solve a problem after flashing your phone with a custom ROM and after that, you see wrong battery percentage (like if your phone switch off before 3% remaining).
But please note that draining your battery to 0 will decrease its capacity permanently (and it can be by a huge amount if you insist to much). Also charging it to 100% everyday can decrease your battery life faster.
In an everyday use of your phone, it's better by a huge amount to charge your phone as often as you can and unplug it around 60-80%. You will see a difference after years.
Do you know why a new phone is around 50-60% battery when you buy it and switch it on for the first time ? Now you know
bobbarker2 said:
XDA is a community with lots of people who don't have in-depth knowledge of Android. Some people may not know better.
So as a community, we also want to stop the spread of bad information. You can't post a guide for better battery life and then say "but no one look into them or question them they work 100%". That's not how things work.
And with that not wasting more time on this thread. Best of luck!
Click to expand...
Click to collapse
The OP isn't going to love me at all. I just know I'm going to get a "nobody asked for your opinion" comment from him. He's right, nobody did ask my opinion, but that doesn't mean I'm not allowed to give it anyway. So, while I thank the OP for his enthusiasm and his attempts to provide something useful for Pixel 6 owners, I strongly advise caution in following these tweaks.
Out of the OP's list, the only things I could agree with would as follows: advertising ID, always on display, system dark mode, animation scale, and systemwide removal of ads. That last one however, I use Blokada for as I feel it's more effective.
OP should explain his reasoning behind each and every one of these changes in this list, so the people he is trying to help can understand his reasoning here. I've been mucking around the guts of Android devices since Android 2.1 and even I would like to know why he chose these things. I'd like to know because most of them seem to cripple the functions of the unit, i.e. negatively impact the Google experience. For example, gestures - gesture navigation - he says to disable. Why?
Some of these tweaks have little to no effect, could actually do more harm than good, or have better options available.
Battery Calibration - Totally unnecessary and only serves to waste battery charge cycles, which you do NOT want to do with a battery trapped in an aluminum frame between two slabs of glass. Battery calibration apps are unnecessary as the only thing they do is delete batterystats.bin, which Android automatically does upon removing the unit from a charger. This has been a known fact since around 2012.
Apps lag using CCleaner - Ignoring CCleaner's reputation since its purchase by Avast, lag from apps on a Pixel 6 is debatable. In any event, SDMaid I feel is a better option than CCleaner, especially as it functions quite nicely for debloating.
Fix OLED Burn-in/Ghosting - The disable gestures tweak could accelerate burn-in along the bottom of the display as the device would have to revert to the 3-dot navigation option. Any burn-in the screen does acquire would have to be rather light in order for an app to fix it, but so long as the wear is light an app will work. I have seen some very extreme examples of burn-in on an OLED screen, and no app would help those.
And then there is the bloatware section. Why in the hell is it that everyone and their mother still recommends deleting apps from the system partition instead of disabling them? Seriously, in the early days of Android it made sense. Now, it's only a waste of time, especially on a device whose system partitions are set to read-only in the first place. Using SDMaid or Titanium Backup and freezing, i.e. disabling, apps is far less likely to cause problems. If I recall correctly, the freezing function does not require root access to work.
My thoughts...take them as you will. Most of this stuff I won't bother with, and the things I do bother with I've already done.
I use the following :
Nova launcher pro
Appdash pro
SD Maid pro
Adaway
Modules - systemless and safety net V2.
Updated Google Pixel debloat list:​- Added overlays
i smell snake oil.
Hamid Chikh said:
From the author of ​Complete Samsung OneUI Optimization​
GENERAL BATTERY/PERFORMANCE SETTINGS​To Start With​- Factory Reset.
Settings App​- Adaptive Battery: DISABLED.
- Synchronization: DISABLED (turn it off again when not in use).
- Location: DISABLED (turn it off again when not in use).
- Advanced features/Gestures: DISABLED
- Bluetooth Scanning (Location services): DISABLED
- Usage & Diagnostics: DISABLED
- Advertising ID: DELETE
- Sound/Vibration feedback: ALL OFF
- Network Mode: 4G
- Always On Display (AoD): DISABLED
- System-Wide Dark Mode: ENABLED
Google Settings​- Nearby connections: DISABLED
- Devices: DISABLED
- Nearby Share: DISABLED (turn it off again when not in use).
- Emergency Location Service: DISABLED
Developer Options:​- Background Check: DISABLED
- Suspend execution of Cached apps (under dev options): ENABLED
- Animation scale (3 entries) : x0.5
Home Screen​- Apply dark black Amoled Wallpaper
- Apply dark theme to Wallpaper
GENERAL BATTERY/PERFORMANCE FIXES​Battery Calibration (Method #1)​- Fully charge your phone, then use it normally till it turns off automatically.
- Wait a few minutes, try to turn it on again, to make sure it's really dead.
- Plug it into the charger and leave it charging for 2h while it's still off.
- Unplug it, turn it on, use it normally it dies again
- Wait a few minutes, try to turn it on again, to make sure it's really dead.
- Plug it into the charger and leave it charging for 2h while it's still off.
- Unplug it, turn it on, and you're done! Enjoy.
Battery Calibration (Method #2)​- Download Battery Calibration Pro
- Fully charge your phone
- Calibrate
- Restart
- Unplug your phone
Other calibration methods can be found here
Fix General Battery Drain​- Go to Permission Manager, check for any excess permissions, like location, camera or nearby devices.
Fix Apps Lag​- Download CCleaner
- Give it all permissions required
- Delete all apps caches
- Go to apps and Force stop all apps
- Uninstall CCleaner then reboot.
Fix Google Apps Battery drain​Go to Settings, Apps. Enable "show system apps" then look for each of:
"Google Play Store", "Google Services Framework", "Google Play Services", "Chrome", "WebView" & "Google App".
- Clear data & cache
- Uninstall Updates
- Force Stop
- Reboot, let them update and follow setup.
- Turn Sync Off
- Auto Update Apps: DISABLED
Fix Camera Experience​- Wipe Data & Cache of Camera app, reboot to Safe mode, do it again, then reboot normally.
Fix Spotify Battery Drain​- Under Spotify settings, turn off "Spotify connect in the background" (This won't stop background music playing).
Remove Ads System-Wide​Go to settings, connections, more connections settings, look for Private DNS.
- Set: dns.adguard.com as custom dns & save.
- Close all apps then reboot.
Fix Slow App Install Time​Under General Google Play Store settings
- "App Install Optimisation": DISABLED
Fix OLED Burn-in/Ghosting​- Download LCD Burn-in Wiper
- Disable Auto-brightness
- Set Brightness to 100%
- Launch a 2 hours session
Fix Speaker Crackling​- Download Speaker cleaner
- Set your volume to max
- Put your phone face down
Fix Google Chrome​- Page Preloading: DISABLED
Chrome Flags
- QUIC protocol: ENABLED
- Smooth Scrolling: ENABLED
- Parallel Downloading: ENABLED
- Auto Dark Mode for Web Content: ENABLED
Fix Reddit​- Theme: AMOLED
- Autoplay videos: OFF
REMOVE BLOATWARE​You're gonna need:
- ADB AppControl (Windows)
- Samsung USB Drivers
- Latest presets attached at the bottom of this post
- You have to enable USB debugging and "Always authorise" on your phone
In AppControl
- Load "PixelSafe"
- Take a look at all what's going to be removed then unselect apps & features you need.
- Apply Uninstall while checking "delete data & cache".
- Restart your phone.
Important Notes
- Uncheck features and apps you need.
- You can always go to "Uninstall" section in AC, search and restore the features you need.
- Keep in mind that deleted apps stay in the phone and will all be restored after factory reset.
- Restore all apps before updating your phone
ADB OPTIMISATIONS​#BACKUP FIRST​- adb devices
- adb shell settings list global > global_stock.txt
- adb shell settings list system > system_stock.txt
- adb shell settings list secure > secure_stock.txt
If you want to check parameter's state, replace "put" with "get" and remove value.
Ex: For "animator_duration_scale"
- adb shell settings get global animator_duration_scale
Change Refresh rate​- adb shell settings put system peak_refresh_rate 90.0
- adb shell settings put system min_refresh_rate 60.0
Change Animation scale​- adb shell settings put global window_animation_scale 0.35
- adb shell settings put global transition_animation_scale 0.35
- adb shell settings put global animator_duration_scale 0.35
Enable Suspend execution of cached apps​- adb shell settings put global cached_apps_freezer enabled
Change Adaptive Brightness Bias (1 = Brighter, -1 = Darker)​- adb shell settings put system screen_auto_brightness_adj 1
Disable Gestures​- adb shell settings put secure double_tap_to_wake 0
- adb shell settings put secure wake_gesture_enabled 0
- adb shell settings put secure camera_double_twist_to_flip_enabled 0
- adb shell settings put secure volume_hush_gesture 0
- adb shell settings put secure hush_gesture_used 0
- adb shell settings put secure silence_gesture 0
- adb shell settings put secure skip_gesture 0
Disable Sound Effects on Interaction​- adb shell settings put system sound_effects_enabled 0
Disable Haptic Feedback​- adb shell settings put system haptic_feedback_enabled 0
- adb shell settings put system haptic_feedback_intensity 0
Disable Screen Saver​- adb shell settings put secure screensaver_enabled 0
- adb shell settings put secure screensaver_activate_on_sleep 0
- adb shell settings put secure screensaver_activate_on_dock 0
Enable Hidden Wifi/Data Toggle​- adb shell settings put global settings_provider_model false
- adb shell settings put secure sysui_qs_tiles "wifi,cell,$(settings get secure sysui_qs_tiles)"
Stay tuned, more is coming ...
#I'M NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE​
Click to expand...
Click to collapse
Bravissimo !
thanks a lot my friend !!!

Categories

Resources