I want to use Tasker to switch on an off the flashlight LED. When I try to do so Tasker tells me that there is a missing permission: "To use Set Light Tasker need the permission to set light. Open settings now to grant this permission?" When I do so I'm unable to find a suitable permission. I've granted "camera" without success. How to fix this?
Toggling WiFi tethering does not work for me in Tasker. Is there a way to get it with the 8 pro without rooting?
Related
Well, as you may or may not know, CM10 has an option to slide your finger on the status bar on the top to change brightness. I enabled that, and initially it worked. I then started using the brightness button in the notification bar, and after like 3 clicks it got stuck on auto mode. Now no matter how many times I click it or go into display and turn off auto, restart, remove the button from the notification bar, etc, the widget stays on auto (it still changes brightness, it just says its on auto) and I can't enable the status bar brightness slide, which I personally favor over the button. Does anybody know how to get rid of the glitch? Would reflashing work?
Thanks,
thejrcrafter
thejrcrafter2 said:
Well, as you may or may not know, CM10 has an option to slide your finger on the status bar on the top to change brightness. I enabled that, and initially it worked. I then started using the brightness button in the notification bar, and after like 3 clicks it got stuck on auto mode. Now no matter how many times I click it or go into display and turn off auto, restart, remove the button from the notification bar, etc, the widget stays on auto (it still changes brightness, it just says its on auto) and I can't enable the status bar brightness slide, which I personally favor over the button. Does anybody know how to get rid of the glitch? Would reflashing work?
Thanks,
thejrcrafter
Click to expand...
Click to collapse
I had this same issue on CM9. For some reason once you turn on auto with the notification bar you cannot turn it off with the other setting. The way I fixed it was to use SQLiteEditor (a paid app by root explorer) to manually edit the settings database. Then I went into the setup for the notification bar to remove the option to toggle through auto so it would not happen again. If you don't want to use the paid app, another solution is to wipe data and start over, then immediately go to the notification setting and disable the auto toggle.
leapinlar said:
I had this same issue on CM9. For some reason once you turn on auto with the notification bar you cannot turn it off with the other setting. The way I fixed it was to use SQLiteEditor (a paid app by root explorer) to manually edit the settings database. Then I went into the setup for the notification bar to remove the option to toggle through auto so it would not happen again. If you don't want to use the paid app, another solution is to wipe data and start over, then immediately go to the notification setting and disable the auto toggle.
Click to expand...
Click to collapse
Thanks. I already tried removing data for the "Settings Data" App. Should I disable auto toggle first? It also has this error in the homescreen widget (the one with all the system toggles like btooth, wifi, brightness, etc). Also, would any SQLite or other database editor work? Where would the database file be found?
Thanks again!
thejrcrafter2 said:
Thanks. I already tried removing data for the "Settings Data" App. Should I disable auto toggle first? It also has this error in the homescreen widget (the one with all the system toggles like btooth, wifi, brightness, etc). Also, would any SQLite or other database editor work? Where would the database file be found?
Thanks again!
Click to expand...
Click to collapse
Yes it is probably a good idea to turn off the toggle first.
Any database editor that works will do. But I don't know of any free ones that have a GUI to make it easy. The free ones are command line apps that are a pain.
The settings database is in /data/data/com.android.providers.settings/databases/settings.db
leapinlar said:
Yes it is probably a good idea to turn off the toggle first.
Any database editor that works will do. But I don't know of any free ones that have a GUI to make it easy. The free ones are command line apps that are a pain.
The settings database is in /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Had the same problem on my Nook HD running CM10.1 on the hybrid install and this fixed it today. My issue was that I think I clicked "auto" while adjusting on the slider and then the brightness was stuck and the "auto" was not checked nor was it selectable. Flipped the bit from 1 to 0 and now it's working ok. Doing a CWM backup now so I'll have the fix in my gold install.
Had this problem on my Samsung T679. Just fixed it and figured I'd record the steps for my own and other's reference. I'm cheap and like doing things the hard way, so I didn't spring for SQLiteEditor. I found that sqlite3 was already installed on the phone.
Before starting: use cwm to make backup, just in case.
1. Force-stop Settings app.
2. Get /data mounted read-write.
3. Open a shell (recommend via ssh/adb, because we have some typing to do).
4. cd /data/data/com.android.providers.settings/databases
5. rm settings.db-shm settings.db-wal (not sure about this step, but the change didn't seem to stick otherwise.)
6. sqlite3 settings.db
Here is my session, you should get the idea:
Code:
sqlite> .tables
android_metadata bookmarks system
bluetooth_devices secure
sqlite> select * from system
...> where name like "%bright%";
71|status_bar_brightness_control|1
278|screen_brightness_mode|1
605|expanded_brightness_mode|0OV=I=XseparatorX=I=VO1OV=I=XseparatorX=I=VO3OV=I=XseparatorX=I=VO5
607|screen_brightness|30
sqlite> update system
...> set value=0
...> where _id=278;
sqlite> .quit
screen_brightness_mode needs to be changed to 0. Don't forget the semi-colons. Now fire up the Settings app and you should be able to enable the status-bar swipe brightness control. I had to toggle it once before it worked.
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.
When he tries to enable the debugging mode he gets a "because an app is obscuring a permission request settings can't verify your response" what to do?
For me it was LMT Launcher that was blocking... Just exit the app and it worked.. maybe some other app you have... Try force closing some app with permission to draw over other apps...and try again...
Polluktus said:
When he tries to enable the debugging mode he gets a "because an app is obscuring a permission request settings can't verify your response" what to do?
Click to expand...
Click to collapse
1. Apps such as Blue light filter apps constantly appear on the top of your screen thus breaking some of the on screen functionalities. Try disabling display over other apps permission of such apps and you should be fine.
2. If you have custom ROM installed such as Resurrection Remix(which was my case) who provides Smart Pixels feature under Settings ->Configurations -> Interface -> Smart Pixels , try disabling that too and you will be able to toggle device admins as well as accessiblity of apps.
3. Also, sometimes it is because of your custom launcher, so try switching to your stock launcher if above solutions don't work.
4. If Accessibility for some apps are on then try disabling them first then try to enable for the apps you wanted to.
P.S. : Of all the above 4 possible solutions, try the ones which are more suitable to your condition. For eg. you can't try solution number 2 if your ROM doesn't have Smart Pixels[\B].
Hope it works.
Hi, I went from huawei mate20pro to s10+ two days ago and got the following problem.
when I export a task to turn off screen as an app in tasker and want to open the created app, there is a notification with Missing Permissions for Accessibility Access.
Normally I would expect that the new created app would be shown in "installed services" in settings, so to enable it. this was the way i did it on the huawei device.
Does anyone know how to solve in oneui?
Many thanks.
Regards,
arct1s