@Desmanto : Thank you very much for the information you have shared here!
Desmanto wrote: ↑14 Aug 2020 11:14
@richaardvark : Those permission/features require manual toggling. Usually the features are moved to other location, you can find it using action Launch App, choose the default setting app, then try to to find accessibility/notification access in the class name. Automagic can't recognize it from the adb shell secure setting because these toggling require the special app permission from the setting itself. The same reason why some secure setting modification won't be reflected by the OS (such as toggle mobile data, airplane, wireless adb). This is android limitation, can't be fixed from Automagic part.
Thanks. I have used the Launch App action before to find the activity to launch the GUI to modify those accessibility features/permission, but it simply does not exist :-/ I have spent a lot of time probing the "FireOS" structure, mainly using the application "Activity Launcher," which lets you see all activities for each user-installed and system apk and lets you launch them directly. There simply are not activities for the typical Android settings menu-area for these features - it can only be done via ADB. That's why nothing happens when I try to use the Automagic "Features & Permissions" area of the Automagic Settings menu to try to enable these features - there does not exist a GUI menu or settings activity to enable these features, only ADB. And this is how I have always been successful in the past, when initially installing and configuring Automagic, to have Automagic working correctly and having permission to view notifications, have accessibility service access, etc. I run into this problem every few months: Automagic will crash for one reason or another (not often, but perhaps a Flow ran into an error too many times or something just happened and there is a "contact the developer" type error message/java error but than at that same time Accessibility Service is no longer recognized by Automagic as being enabled. I've had to fix this only maybe four times in the last year or so of successfully running Automagic on this device, but I cannot remember for the life of me how I have been able to resolve this each time. When I delete the Automagic apk and reinstall, all of my data is still there. I have tried deleting the main "Automagic" when deleting and reinstalling Automagic but it is still not recognizing ADB as enabled. I have been able to successfully make Automagic recognize that Accessibility/notification access/IME keyboard etc. permissions are granted and enabled via ADB before, but I just can't remember how I have done this.
I think for now I am going to see if I can fix this by restoring a previous instance of Automagic using Titanium Backup, from when the permissions were properly recognized by Automagic, and then importing my latest Flow/Widget data. Maybe this will work. It's such a pain to have to go through this every time there is a big crash of the app though...
.......
Edit: Ok, I am back up an running again! ✔ I remember now how I was able to get all permissions/features properly working... I used a separate/third-party app called "Settings Database Editor" which lets you directly modify the system databases/tables and I was able to manually type in the Automagic notification listener, keyboard, and accessibility services and I guess this more-or-less was able to act as my GUI-way of doing it, without using ADB, and as such Automagic recognized that the features/services had been enabled and everything is working fine again.
I'll have to remember this for the future... use "Settings Database Editor" app to fix Automagic permissions.
Thanks again for your help! Also, copying the .bin file worked perfectly for the glovars.