So, I've just updated to the latest Pure Nexus - did a wipe and clean install - and I'm trying to get my apps set up again, but I can't grant permissions through system settings. If an app actually pops up and requests a permission, I can allow it; but for some apps, this doesn't happen. Home Remote Control, for example, won't request the storage permission it needs to access my ssh key. So I go into settings->apps, find the app, tap permissions, try to enable the storage permission, and..."screen overlay detected". Except there is no screen overlay active. I have disabled every app's "draw over other apps" permission. I even found the "show system" option in the list and disabled all system apps' ability to draw over other apps. At this point, SYSTEMUI can't draw over anything else! And I'm still getting "screen overlay detected" when I try to change permissions. Any advice? Is there another way to manage permissions in Marshmallow (like maybe an xposed module)?
EDIT: Thought I should also mention, the issue persists in Safe Mode.
tardis_42 said:
So, I've just updated to the latest Pure Nexus - did a wipe and clean install - and I'm trying to get my apps set up again, but I can't grant permissions through system settings. If an app actually pops up and requests a permission, I can allow it; but for some apps, this doesn't happen. Home Remote Control, for example, won't request the storage permission it needs to access my ssh key. So I go into settings->apps, find the app, tap permissions, try to enable the storage permission, and..."screen overlay detected". Except there is no screen overlay active. I have disabled every app's "draw over other apps" permission. I even found the "show system" option in the list and disabled all system apps' ability to draw over other apps. At this point, SYSTEMUI can't draw over anything else! And I'm still getting "screen overlay detected" when I try to change permissions. Any advice? Is there another way to manage permissions in Marshmallow (like maybe an xposed module)?
EDIT: Thought I should also mention, the issue persists in Safe Mode.
Click to expand...
Click to collapse
Do you have twilight or lux installed?
The reason it's warning you is BECAUSE they're disabled. Enable all the toggles and the prompts will go away. You can then choose to disable one by one until you figure which app is throwing the error.
Sent from my Nexus 6P using Tapatalk
Turned out to be because GravityBox pie controls were enabled. Doesn't show up in the "draw over" list, but trips the overlay detection regardless. Disabling pie controls in the GravityBox app let me change permissions.
Hi,
Try to flash this by Custom Recovery.
http://www.mediafire.com/?ouxua6rkkagi3g9
tardis_42 said:
Turned out to be because GravityBox pie controls were enabled. Doesn't show up in the "draw over" list, but trips the overlay detection regardless. Disabling pie controls in the GravityBox app let me change permissions.
Click to expand...
Click to collapse
Thanks man. I have been going crazy for the past few days trying to figure this out lol. Just posted asking for help as well. Such a random and rare issue, that i couldnt find anything on it.
**EDIT - THIS IS NO LONGER REQUIRED AS OF .025, ISSUE HAS BEEN RESOLVED VIA GOOGLE UPDATE**
Hey Guys,
I know a lot of you (myself included) are experiencing the NFC clicking issue on your Pixel 2's.
I wanted to show you a workaround, which will automatically disable NFC during a call, and re-enable it when the call ends. This is a temporary fix which you can use until the following promise is fulfilled...:
"Hey All,
We are validating a software update to address faint clicking sounds on some Pixel 2 devices. The update will be made available in the coming weeks. The clicking noise being reported does not affect the performance of your device but if you find it bothersome you can temporarily turn off NFC in Settings > Connected devices > NFC. "
Posted by Orrin - Community Manager, Found on:
https://productforums.google.com/fo...-place=topicsearchin/phone-by-google/clicking
This workaround uses the Macrodroid application. It requires root (Not yet available as far as I am aware) or an ADB Hack (What I used) for this to work.
You can grant Macrodroid "System" access by performing the following (ADB Hack):
https://www.tapatalk.com/groups/mac...23&p=10455&hilit=WRITE_SECURE_SETTINGS#p10455
This will allow Macrodroid to enable and disable NFC WITHOUT root.
Once access has been granted create the following macros:
Macro #1:
Name: NFC Off
Triggers: Call Active (Any Contact, Any Number, Non Contact, Unknown Caller)
Actions: NFC Off
Macro #2:
Name: NFC On
Triggers: Call Ended (Any Contact, Any Number, Non Contact, Unknown Caller)
Action: NFC On
You can disable the persistent notification icon by opening Macrodroid, going to settings > Notification Bar Options > Force Hide Icon.
This has been working great for me, and I know it looks like a lot of work but its a great alternative to manually toggling NFC off and on.
Macrodroid is also super useful in general so, enjoy!
Thanks for this. Very good idea until we get a fix from Google.
I too saw the MacroDroid page you refer to and was just going to post here about it - but saw you'd beaten me to it by several days! It works really well!
I also use Macrodroid to put my phone into silent mode overnight when it's charging AND connected to my home wifi AND it's after 9pm. Disconnecting the power reverts it to normal mode. I love MacroDroid - it's much easier to understand if you're not a programmer than any of its competitors like Tasker.
Is anyone else having the issue of TB schedules not being executed when the phone is sleeping? I have set all the Battery Optimizations set to manual for both TB and the TB root key app. Sometimes the scheduled task is started when I wake up the phone and sometimes (at night) it's being ignored entirely. I am on rooted Oreo stock but I saw the same on Nougat.
Fixed
khaberz said:
Is anyone else having the issue of TB schedules not being executed when the phone is sleeping? I have set all the Battery Optimizations set to manual for both TB and the TB root key app. Sometimes the scheduled task is started when I wake up the phone and sometimes (at night) it's being ignored entirely. I am on rooted Oreo stock but I saw the same on Nougat.
Click to expand...
Click to collapse
OK, fixed it - I had to activate it under Ignore Battery Optimizations
khaberz said:
OK, fixed it - I had to activate it under Ignore Battery Optimizations
Click to expand...
Click to collapse
Having the same problem. Where is the option for "Ignore Battery Optimizations", is it a Titanium option or a system option? Thanks
palosanto0 said:
Having the same problem. Where is the option for "Ignore Battery Optimizations", is it a Titanium option or a system option? Thanks
Click to expand...
Click to collapse
It's a system setting, somewhere under the Battery settings. I am not on EMUI anymore, so I can't tell you exactly. However, it didn't fix my problem permanently. I have moved on to LineageOS meanwhile, where these problems don't exist anymore.
khaberz said:
It's a system setting, somewhere under the Battery settings. I am not on EMUI anymore, so I can't tell you exactly. However, it didn't fix my problem permanently. I have moved on to LineageOS meanwhile, where these problems don't exist anymore.
Click to expand...
Click to collapse
Unfortunately it does not work in my Xiaomi redmi Note 4X.
I found the option to activate "Ignore Battery Optimizations", however if I don't leave the Titanium backup PRO running, the scheduled backups are not performed.
Last week I have been searching internet for a solution, however still I have not found a satisfactory one.
Kind regards and thanks for your advice,
Javi
<deleted - see next post for updated info>
Titanium Backup schedules not executed (or interrupted after being started) and/or its related notifications not being shown appears to be an issue that is caused by crazy additional 'features' as implemented at some devices to improve battery life. This especially happens at OnePlus devices running Oreo (Android 8), but may possibly also appear at devices of other brands (Xiaomi?). Therefore it actually isn't a shortcoming of Titanium Backup itself, but the result of some stupid app handling and killing behaviors that may be active at your device.
Also other apps that should permanently be kept running in background may be impacted by this behavior (being killed for the same reason) like Tasker, Sync-to-cloud apps, etc.
Especially at OnePlus devices running Oreo, following implemented crazy 'optimization' behaviors are playing a role here:
After a user has set Battery optimisation OFF for a specific app, it may automatically be set ON again after a reboot or after the app was updated
Background services may be killed EVEN when for the related app the Battery optimisation was set OFF
The 'Autostart' attribute may be ignored, so apps may be NOT automatically started in background after rebooting your device
SOLUTION
1. Make sure the 'Advanced optimisation' options are disabled
Go to Settings > Battery > Battery optimisation
Click the 3 dots in the upper-right corner and select 'Advanced optimisation'
Verify that the options 'Advanced optimisation' and 'Sleep standby optimisation' are both disabled
2. Set Battery optimisation OFF for any app that should continue to run in background
Go to Settings > Battery > Battery optimisation
Select the app that should never be killed, so in this example: 'Titanium Backup'
Select 'Don't optimize' and click DONE
Nb.
Above is not needed for the 2nd entry 'Titanium Backup PRO', which is just related to your PRO key payment and not the running Titanium Backup process itself.
However, disabling Battery optimization for an app is NOT enough for preventing that it could be killed when running in background at OnePlus devices!
This not only because the 'Don't optimize' setting may automatically be reverted to 'Optimize' after a reboot or after an update of the app, but EVEN when Battery optimisation is actually disabled it's nevertheless still candidate for being killed at OnePlus devices running Oreo! Therefore also next action is required in addition.
3. Lock the app in your 'Recent Apps' list
Open and then close Titanium Backup (or just touch the Home button at your device after opening the app)
Touch the 'Recent Apps' button at your device
This shows your recent apps, where Titanium Backup will now be included (as last / most recent entry)
Toggle the 'Lock' icon in the upper right corner of that Titanium Backup entry, to switch it to a closed lock icon symbol
(see attached screenshot)
This last action not only just prevents that the app could be removed from your 'Recent Apps' list, but it ALSO prevents the issues as described above, so:
The app will not be killed anymore when running in background
The 'Battery optimisation' setting for that app will not be reverted anymore to 'Optimize' after a reboot or after an update of the app
When done, Titanium Backup schedules should now run as defined. Also, its completion messages shouldn't disappear from your notification entries anymore, but kept until you remove them.
OTHER APPS
Because it's not just a specific Titanium Backup issue but the result of the stupid behavior as implemented at OnePlus devices running Oreo, it's highly recommended to repeat the steps above for any app that should never be killed when running in background (eg. Tasker, Sync-to-cloud apps, Alarm/Alert apps, etc.). Also apps that are making use of scheduled actions, or should awake at incoming messages, chats, mails, alarms, or Security/Anti-virus apps etc. could be candidate of not being able to react properly because they were killed when running in background and/or not started at boot. When such apps doesn't always correctly react/awake at your device, just perform same actions as described above to prevent them to be killed. When an app still doesn't work because it wasn't auto-started at boot, you could use Tasker to create a Tasker-profile that executes a Tasker-task to launch such apps at boot. Start-at-boot via Tasker appears to be not required for Titanium Backup, but for some other apps this was my only option to ensure that they were auto-started after a reboot of my device.
Nb.
Some apps have options included in their internal settings like 'Keep active in background', 'Run in Foreground' or 'Turn off battery optimisation'. Even when these types of internal app settings are selected, they could still be killed at some device brands (eg. OnePlus) when the actions as described above aren't implemented in addition for such apps.
OnePlus: Never settle, but also never be so stubborn...
Thanks
Much appreciated for the fix.
Never thought about locking the app, great idea ?
Just stumbled over this post through a link. Many thanks for the info; in my case it's not only TB that's effected but also several other apps like OruxMaps and Automagic.
For completeness I post some screenshots from OnePlus 6 / OOS 9.0.4 (Pie) showing the changed recent apps screens and dialogs (in German, but I guess you'll get the picture)
paarnoutse said:
Titanium Backup schedules not executed....
OnePlus: Never settle, but also never be so stubborn...
Click to expand...
Click to collapse
i was wondering why titanium is not executed in months.. and killed shortly even when i run it manually.
settings were great:
- no battery optimization
- no data optimization
- tons of free memory on RAM boasting 1+ (funny isn't it)
- recent app management=normal clear
- standby check=exempted
- keep activities
- deep optimization turned off
- sleep standby optimization turned off
and still it didn't help until i LOCKed the app. this is why 1+ and xiaomis achieve better battery scores than samsung
doggydog2 said:
...this is why 1+ and xiaomis achieve better battery scores than samsung
Click to expand...
Click to collapse
(Spoiler: heavy OT post)
...which is what I really love about my 1+: 3 - 4 days between charging aren't rare here.
For the very few apps that are having probs (like track recording) with heavy battery optimization I wrote myself a script (am using automagic, but this should be also possible with Tasker etc) to disable deep opt. then start my critical app. Works great for me, but as always: ymmv
I can't find the setting to lock an app in the recent list in Android 10. Anyone know how to do it?
James_Oakley said:
I can't find the setting to lock an app in the recent list in Android 10. Anyone know how to do it?
Click to expand...
Click to collapse
Each tile you see in the recents screen should show the app title and the usual three dots to open a pop-up menu. There you can lock the app, show app details etc
lm089 said:
Each tile you see in the recents screen should show the app title and the usual three dots to open a pop-up menu. There you can lock the app, show app details etc
Click to expand...
Click to collapse
Thanks for taking the time to reply. Appreciate it.
Still not seeing it.
Where do I click?
James_Oakley said:
Thanks for taking the time to reply. Appreciate it.
Still not seeing it.
Where do I click?
Click to expand...
Click to collapse
Your screenshot shows the app settings. You need to bring up the "recents" screen instead. If you're using the standard navigation bar that is the square button at the right end of the nav bar (screenshot #1, blue mark).
Then you flip through your recently opened apps until you find the one you're looking for. From then on it's as I described before: tap the 3 dots (screenshot #1, red mark). in the pop up menu select the "lock" entry (screenshot #2, green mark)
=== UPDATE: added some screenshots ===
lm089 said:
Your screenshot shows the app settings. You need to bring up the "recents" screen instead. If you're using the standard navigation bar that is the square button at the right end of the nav bar (screenshot #1, blue mark).
Then you flip through your recently opened apps until you find the one you're looking for. From then on it's as I described before: tap the 3 dots (screenshot #1, red mark). in the pop up menu select the "lock" entry (screenshot #2, green mark)
=== UPDATE: added some screenshots ===
Click to expand...
Click to collapse
Thanks - got it. When I read about "recents" in this thread earlier, I assumed it was when you go to Settings > Apps and you're first shown a list of recent apps. I've now got what everyone is talking about, thanks to your patient explaining. I'm sure this will help others too. On my phone, there's no nav bar it's all done with gestures, so you swipe up from the bottom of the screen - then lock Titanium in place. Bingo, and thank you.
Hi, I just got my x651 from China, it seems to be ok, except a few bugs I tried to manage but for only a few I found solutions so far. My rom seems to be somehow the latest one but it says x653 in some places, s28.
No OTA update available and scared to don't land in a far worst ROM...
1. EUI launcher was acting quite strange, the widget button was not working, the central button with LeEco stream could not be replaced, etc. so I got google now launcher which is clean and simple, but..
2. there are lots of apps (whatsapp) requesting normal permissions (contacts and local storage) but I cannot grant them because it is asking me to stop the draw over from settings, which I cannot do, since there is no way to do this (I don't have in menus options to disable this draw over thing), so I got locked in a damn loop.
q: is there any way to disable the draw over thing if there is no option in apps? or to grant permissions ignoring the draw over thing? because whatsapp is useless without contacts and saving abilities.
3. right after i started the phone I noticed the bold text used for titles is white with thick borders, as in other phones I saw in that option for high contrast text, also there is no way to change it since there are no options in accessibility regarding this.
q: is there any way to disable this or to unhide menu options? maybe a third party software like system optimizer?
any help greatly appreciated. as I said, I was tempted to try the last version of official rom but I have some bad experience with chinese apps in some former telephones so I'd rather check 10 times before cutting the rope, you know..
I have PRO 3 LEX653 (Helio x23), quite similar to yours since I don't know what the difference but we having the same problem.
For your question 1, EUI launcher is quite buggy for me too. You can use other launcher to use widget features.
Question 2, you need to disable "Swipe shortcuts" which can be found in "Setting > Accessibility > Swipe shortcuts".
Question 3, I don't understand, give screenshot might help.
Also, help me with my thread too!
https://forum.xda-developers.com/le-pro3/help/pro3-ai-edition-lex653helio-x23-t3759318
I wanted to share this with everyone in hopes that my solutions helps at least one person.
I have an LG G6 running Android 8.0. A few apps I use require Draw over other apps to be turned on. One of those apps is Keeper Security, which needs permission to Draw over other apps so that its Keeper Fill feature can read the screen and go find my username/password for that website/app I am trying to login to. Since around December 2018 it has started acting 'flaky'. Even though I had enabled Draw over other apps for the app already, it kept notifying me that I needed to turn it on. After some random setting changes of turning the draw over apps setting ON/OFF, along with the Keeper Fill setting from within the source app that needs this permission, I could eventually get it to work again, but it would always break again very soon after.
As I am getting ready to go on a trip, I installed Google's Datally app. It, too, wants me to turn on Draw over other apps, but when I tap "next" to be taken to the Android settings page to enable Draw over other apps, nothing happens (I usually expect an app detects it has been enabled and gives "success" message).
So I started disabling the 3 possible suspects listed by kapil1100 in this post. I had LG's Comfort View and some Accessibility options enabled, so I turned them off and: no change.
I disabled all other apps that have permission to Draw over other apps via: Settings > Apps & notifications > Special access > Draw over other apps, and: no change.
I use Evie launcher, so I went back to the stock one: no change.
I got thinking about what else could be modifying/accessing the screen and realized that LG has custom Home touch buttons.
I went to: Settings > Display > Home touch buttons > Hide Home touch buttons and DISABLED Show lock/hide icon and then tried enabling Draw over other apps for Datally and IT WORKED!.
I was then able to turn Show lock/hide icon back ON and everything has been working as expected. I suspect that, because I had Show lock/hide icon turned on during an upgrade, something got messed up and my turning it OFF and back ON fixed the issue.
I hope this helps someone!