Hi,
I've recently bought an Ainol Novo9 Spark, and I've been having issues with some apps crashing. Upon investigation in one of them (SpaceChem) and contact with the developer, it looks from the logcat as though GPU Rendering is always forced even though the option is disabled in Settings > Developer Options and even if I turn all developer options off wholly. Does anyone happen to know if there's a config file or such that this points at that I could check to verify whether the option is on or off (and plausibly disable it manually)?
Related
like the title says. how do i make developer options permanent thru reboots power offs. Because some of those settings are the only way I can run, certain aspects of my Samsung i727 running CM 10.2 stable, smoothly.
Also why won't my games run efficiently without HW overlays enabled, what gives?
drago10029 said:
like the title says. how do i make developer options permanent thru reboots power offs. Because some of those settings are the only way I can run, certain aspects of my Samsung i727 running CM 10.2 stable, smoothly.
Also why won't my games run efficiently without HW overlays enabled, what gives?
Click to expand...
Click to collapse
I'm not an expert by any means...but the best way I've found to make 'disable HW overlays' persistent (on my Rikomagic MK802IIIs) is to use Tasker and Secure Settings. Create a task and name it whatever you like. Then create an action / plugin / Secure Settings / Hardware Overlays (under Root Actions). Set the desired state to Off and save. Then make a Profile to trigger that task. I tried doing the system / boot event, but that failed horribly. So instead I currently use Wifi connected state. When my device boots, as soon as the wifi sees my network SSID, Tasker checks the Disable HW Overlays option in Developer Options. Works slick for my purposes.
loadedlen said:
I'm not an expert by any means...but the best way I've found to make 'disable HW overlays' persistent (on my Rikomagic MK802IIIs) is to use Tasker and Secure Settings. Create a task and name it whatever you like. Then create an action / plugin / Secure Settings / Hardware Overlays (under Root Actions). Set the desired state to Off and save. Then make a Profile to trigger that task. I tried doing the system / boot event, but that failed horribly. So instead I currently use Wifi connected state. When my device boots, as soon as the wifi sees my network SSID, Tasker checks the Disable HW Overlays option in Developer Options. Works slick for my purposes.
Click to expand...
Click to collapse
will this work for JB4.12?
loadedlen said:
I'm not an expert by any means...but the best way I've found to make 'disable HW overlays' persistent (on my Rikomagic MK802IIIs) is to use Tasker and Secure Settings. Create a task and name it whatever you like. Then create an action / plugin / Secure Settings / Hardware Overlays (under Root Actions). Set the desired state to Off and save. Then make a Profile to trigger that task. I tried doing the system / boot event, but that failed horribly. So instead I currently use Wifi connected state. When my device boots, as soon as the wifi sees my network SSID, Tasker checks the Disable HW Overlays option in Developer Options. Works slick for my purposes.
Click to expand...
Click to collapse
I think this would work better with the activate on boot option, what's wrong with that? I'm not always on Wifi :/
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.
EDIT: Added a 4th option that didn't work!
Hi ,
Does anyone know how to prevent the A8 from auto closing Pokemon Go? I've tried the following:
1. Settings, battery, settings, and disabling
1.1. Adaptive battery
1.2. Put unused apps to sleep
1.3. Optimise settings
2. Settings, battery, memory, setting, and adding Pokemon Go to the list of apps that aren't checked.
3. Settings, apps, Pokemon Go, battery, optimise battery use, not optimised
4. Lock the app in the recents menu
Yet after a short while of switching the screen off, it still gets killed. Is there some other arcane setting I have missed or do Samsung (they're not the only ones) that add GUI settings to make it look like you're in control but actually the setting does nothing?
Note: phone is not rooted, but I am happy to root it if necessary - it used to be rooted, I just couldn't be bothered after the recent update!
TIA
m
No one? OK, how about a different angle: if I re-root it doe anyone know which process I'd need to remove / kill to stop Samsung killing apps?
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
I caught someone with my phone connected to their laptop via data cable. Now developer options are open, and some are turned on. My phone started randomly opening apps rapidly or when I type, random letters and numbers typed themselves. If I restart my phone it solves the problem temporarily. Someone told me he could have been trying to root my phone, and to see if it is unlocked. How do I find out? These are the dev options that were turned on, should I leave them be or turn them off? Verify bytecode of debugable apps....Bluetooth AAC white list.....adaptive notification priority. Thanks so much for any help you can give.
With regards to Developer Options: Undo all options enabled, then disable Developer Options.
global | How to Enable or Disable Developer Options on Android
Learn how to disable or enable developer options on android phone to unlock more features on your mobile phone such as usb debugging, checking cpu usage, etc.
www.carlcare.com
jwoegerbauer said:
With regards to Developer Options: Undo all options enabled, then disable Developer Options.
global | How to Enable or Disable Developer Options on Android
Learn how to disable or enable developer options on android phone to unlock more features on your mobile phone such as usb debugging, checking cpu usage, etc.
www.carlcare.com
Click to expand...
Click to collapse
Thank you very much for your help.