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.
Hello all
I wanted some help on this matter. I want my Joying Intel unit to go to the home screen if there are no button presses or touches after 2 minutes. I looked online for similar tasker setups but could not find one for my particular case. I'm also not the brightest in matters like these so I thought I'd ask the experts here!
Thanks
Hello All
Thought I'd share that I figured this out through the help of Reddit. You need AutoInput and Tasker. Here are the instructions;
AutoInput Event > UI Action > Clicks and Long Clicks
In Task,
Task > Wait desired time
App > Go Home
Hit cog top right and set Task collision to Abort Existing.
My question now is, how do I prevent the Joying OS from killing Tasker and AutoInput when my Joying unit sleeps AND when I clear my apps from the app drawer?
If anyone runs through the same issue I have its the Sofia Server mods or "main server mods" in Joying Extra Tools, it's the "NoKill" mod.
Hopefully final question. How do I prevent the os from resetting my accessibility services? When the car is off for awhile and the unit enters sleep mode it resets the accessibility settings for my AutoInput plugin
I was asked by @rigattoni if I could write an app that allows to trigger Tasker after head unit wakes up from sleep (aka fast boot).
Why? Android has no reliable way for apps to be triggered when the device resumes from suspend-to-RAM state (aka fast boot).
Therefore a lot of Tasker users are missing a way to achieve that any Tasker jobs are started in fast boot.
My small little app tries to solve this.
This topic was first mentioned here: https://forum.xda-developers.com/showpost.php?p=82596933&postcount=6133
How it works:
When a USB mass storage device is attached, the app will be triggered by Android, both in cold boot, and also in "fast boot".
Then the app waits for 10 seconds and then fires a Tasker specific intent to Tasker and the app will finish itself.
This allows that any Tasker tasks will be triggered.
In the attachment you find both a ready APK and the source code of it.
Note: I will not maintain this app.
If the APK does not fit your needs, adapt the source code yourself.
If you want to send other intents additionally, adapt the source code yourself.
If you want to change the timeout of 10 seconds, adapt the source code yourself.
If you don't know how to do so, take an online Android App Development training.
Thanks for your effort and this post ?
I've simply used tasker with "Display on" event for starting the app I need, turning wifi on, etc.
Working flawlessly for cold boot or resume... why not this method?
themissionimpossible said:
I've simply used tasker with "Display on" event for starting the app I need, turning wifi on, etc.
Working flawlessly for cold boot or resume... why not this method?
Click to expand...
Click to collapse
For me and others, the Tasker background process is killed on resume so it's not "active" to know that the screen is on or otherwise.
In my case tasker always runs on start.
But if for somebody tasker is killed on resume, how another app instead should be able not to be killed as well?
This app here is started by Android itself if a USB stick is present and so resistent against the 'kill all running apps' issue.
Missing Accessibility activation
On CSN2, CSN2-D, RL7Ac units another issue is visible, according to the Android restrictions starting with Android 8, that accessibility settings are not stored. That means that Tasker is not allowed to work in background... This is a no go for us...
This can be "fixed" if the unit is rooted!
What is needed:
Preparation:
Unit is rooted
Tasker installed
Secure Settings installed and activated
Workflow:
Secure Settings:
Switch to tab "SYSTEM+"
Press the button "DISABLED" and wait until the system is set to "ENABLED"
Close the app
Tasker:
Open "Preferences" in Tasker, switch to tab "MISC", activate "Allow External Access" and deactivate "Reduce Resource Usage". There might be some popups afterwards when closing Tasker about battery usage... As we don´t care about that, please accept these changes.
Task:
Create a profile, Example:
"Screen on" with higher priority (otherwise the task may be scheduled)
Create new task
Press the "+" button to add a command
Choose "Plugin and there "Secure Settings"
Press the stylo and open "System + Action"
Choose "Accessibility Settings" and search for Tasker in the list (on some units, the field is really small to find any app)
Press the "DISABLED" button to get it changed to "ENABLED" and safe the setting.
You can add other accessibility changes too. In this case you need to add a wait of 100ms between the commands.
(FCC needs it, because otherwise some functionality of FCC does not work (automatic light, volume....))
Example added to import in Tasker.
not working for me on android 10 (( (825X_pro)
magicm3n said:
not working for me on android 10 (( (825X_pro)
Click to expand...
Click to collapse
Would you please precise what is not working?
What happens if you start the app manually?
...some information as given would really be useful, right?
rigattoni said:
Would you please precise what is not working?
Click to expand...
Click to collapse
Tasker does not start after waking up.
rigattoni said:
Would you please precise what is not working?
What happens if you start the app manually?
Click to expand...
Click to collapse
If I start app manualy its OK, tasker starts
You need a USB stick being attached to the head unit. Have you done this?
realzoulou said:
You need a USB stick being attached to the head unit. Have you done this?
Click to expand...
Click to collapse
Yes, of course, USB stick attached
magicm3n said:
Yes, of course, USB stick attached
Click to expand...
Click to collapse
If you pull out the stick and put it back in again. Do you get the popup to start the StartTasker automatically?
rigattoni said:
If you pull out the stick and put it back in again. Do you get the popup to start the StartTasker automatically?
Click to expand...
Click to collapse
So, here's what news.
After a long sleep (the car sleep for about 2 hours), I turned on the ACC and received a notification asking whether to launch the StartTasker when the UDisk device was connected. I checked the "allow" box.
But now if I turn off the car for just a couple of minutes, then nothing happens: the unit wakes up, all applications are killed and the StartTasker does not start.
When I take out the stick and insert it again, then OK, the StartTasker starts - I see the correspond popup notice below.
But now there is another problem: the StartTasker itself does not start the Tasker ((. Even if I manually start StartTasker , I can see the startup notification at the bottom, but the Tasker won't start. Hm...
magicm3n said:
So, here's what news.
After a long sleep (the car sleep for about 2 hours), I turned on the ACC and received a notification asking whether to launch the StartTasker when the UDisk device was connected. I checked the "allow" box.
But now if I turn off the car for just a couple of minutes, then nothing happens: the unit wakes up, all applications are killed and the StartTasker does not start.
When I take out the stick and insert it again, then OK, the StartTasker starts - I see the correspond popup notice below.
But now there is another problem: the StartTasker itself does not start the Tasker ((. Even if I manually start StartTasker , I can see the startup notification at the bottom, but the Tasker won't start. Hm...
Click to expand...
Click to collapse
StartTasker is NOT for starting Tasker, it´s to activate Tasker working in background. It just send an Intent, nothing else.
Check if in Accessibility settings Tasker is activated and in Tasker settings if "Allow External Access" is activated and "Reduce Resource Usage" deactivated.
Add a new profile with Display Orientation Landscape, write a short task with a Wait for 10 sec and add a Flash with some text and retest.
This should automatically activated after boot. and should show this flash on your unit.
Yes of course, a profile is written in the Tasker to launch another application. It works. When I rebooted the device, the StartTasker saw the connected USB and launched the Tasker, which completed the task.
But all this does not happen for some reason after exiting sleep mode.
I'll check settings tomorrow. Tnx!
rigattoni said:
StartTasker is NOT for starting Tasker, it´s to activate Tasker working in background. It just send an Intent, nothing else.
Check if in Accessibility settings Tasker is activated and in Tasker settings if "Allow External Access" is activated and "Reduce Resource Usage" deactivated.
Add a new profile with Display Orientation Landscape, write a short task with a Wait for 10 sec and add a Flash with some text and retest.
This should automatically activated after boot. and should show this flash on your unit.
Click to expand...
Click to collapse
My Head unit have not Accessibility settings (
All other is on.
Did not start after sleep.
If I reattach USB stick manually then Starter had starts, I see pop up message, but Tasker is not.
magicm3n said:
My Head unit have not Accessibility settings (
All other is on.
Did not start after sleep.
If I reattach USB stick manually then Starter had starts, I see pop up message, but Tasker is not.
Click to expand...
Click to collapse
I assumed that....
See my posting here: https://forum.xda-developers.com/showpost.php?p=82627859&postcount=7
You can import the task and then export as app afterwards.
In this case you just need a launcher which supports this app on start up. I use Fcc Car Launcher for that.
rigattoni said:
I assumed that....
See my posting here: https://forum.xda-developers.com/showpost.php?p=82627859&postcount=7
You can import the task and then export as app afterwards.
In this case you just need a launcher which supports this app on start up. I use Fcc Car Launcher for that.
Click to expand...
Click to collapse
FCC Car Launcher does not work on my Unit. No widgets support.
magicm3n said:
FCC Car Launcher does not work on my Unit. No widgets support.
Click to expand...
Click to collapse
Which unit?
Please don´t let us tear all information in small parts out of you.
which Unit, MCU version, Android version... please.
Use this app to configure the Accessibility settings and check if this is still activated after deep sleep.
Just now I don´t know any unit which does not work with Fcc... not completely may be with some missing features, but the standard things are working.
...and please read at least the first thread of the Fcc Car Launcher thread...
This thread gives a solution to rework the Tasker issue... and is a real Tasker fault.
I added a solution for getting it working if any Android unit forgets the accessibility setting in deep sleep.
Your problem now is a complete different thing, which needs to be discussed in the related thread.... and this is for fact the Fcc thread.
Bit of a strange problem, my head unit (JY-UQD11N4G) stops me getting sound notifications from any app! I can go into setting and turn up the notification sound but, as soon as I go back to the home screen, the volume is back to zero! I have managed to find a app that overrides this aggressive behaviour called Power Shade: Notification Panel & Quick Settings When this app is enabled I get sound notifications, unfortunately though this app interferes with the navigation bar, so I'm unable to press home buttons etc.
I'm guessing this app works because it has uses Accessibility services.
Can anyone advise it is possible to stop the head unit doing this or an app that could but, it mustn't swipe down from the top. Thank you