Endercraft
Moderator
That seems like a library issue to me. Check if all the files that come with the adb executable are present (should be lib(something)).
ADB Hack - Granting extra capabilities via the ADB tool
- Thread starter MacroDroidDev
- Start date
Yes, they are all there.
What's odd is adb claiming it's looking in a place for a file when adb (& all associated files) are right where it's supposed to be. Really, you can place the adb package anywhere & the terminal acknowledges it's there. But why it's referencing that other file I don't understand.
If you just want to do an adb hack, there are ways to do it without a PC.
www.macrodroidforum.com
ADB hack without a PC (Android 11+)
This section describes how to perform ADB hacks on Android 11+ devices using Shizuku and aShell. 1.Install Shizuku from the Play Store 2.Tap Pairing 3.Tap Developer options 4.Tap Wireless debugging 5.Tap Pair device whith pairing code 6.Enter pairing code
My goal is wanting to initiate GPS if a Bluetooth connection is established in my car. I can setup the script easy, but "location" functions need adb hack & so if I can use that app, I'll just do that.If you just want to do an adb hack, there are ways to do it without a PC.
ADB hack without a PC (Android 11+)
This section describes how to perform ADB hacks on Android 11+ devices using Shizuku and aShell. 1.Install Shizuku from the Play Store 2.Tap Pairing 3.Tap Developer options 4.Tap Wireless debugging 5.Tap Pair device whith pairing code 6.Enter pairing code
Update; I have it running now with Shizuku
Last edited:
Abrahamchi
New member
Hi. I need help. I do everything correctly but when I open again the MacroDroid App and configure a new Macro (Open Gmail - when - Device Turn On) but is not working
I don´t have errors when install ADB Hacks, My devices is detected but idk what can i do
I don´t have errors when install ADB Hacks, My devices is detected but idk what can i do
dhj49er
Well-known member
Abrahamchi
New member
I do again everything
- First, Download abd from https://developer.android.com/tools/releases/platform-tools?hl=es-419#downloads (And Copy - Paste on my C: Folder the files, next i add to path the url "C:\adb")
- I open CMD like admin and run the command "adb devices" with my devices connected
- Next, I run the coomands
- Next, I finish CMD and go to my device and configure the Macro again
- Next I reboot, TurnOff and TurnOn or just run the Macro, but is not working
Idk if i need do something else
Qarboz
Well-known member
First of all, when you need to run the ADB commands taken to the directory C:\ADB
In the macro, before launching Gmail add a wait of 30s...1m (to be tested) to give time for the device to load all background services
Endercraft
Moderator
On newer devices, immersive mode may not work.
Because of secure boot, the device boot trigger may not fire unless the device is unlocked quickly. The MacroDroid initialized trigger should work.
Because of secure boot, the device boot trigger may not fire unless the device is unlocked quickly. The MacroDroid initialized trigger should work.
Bonjour,
macrodroid m'indiquait un message d'erreur et me demandait de remettre la permission d'accessibilité avec adb. En cherchant je suis arrivé sur cette page
j'ai suivi les points cités plus haut et, depuis, j'ai un problème avec le talkback qui est activé en permanence. Quand je le désactive, il se réactive tout seul instantanément et en boucle infinie.
Peux-tu m'aider si tu veux ?
---------------------
Good morning,
macrodroid gave me an error message and asked me to reset accessibility permission with adb. While searching I came to this page
I followed the points above and, since then, I have a problem with the talkback which is permanently activated. When I turn it off, it reacts immediately himself and endlessly.
I ran all the adb commands from the previous message
Can you help me please t?
Last edited:
Endercraft
Moderator
MacroDroid --> Settings --> Keep Accessibility Services Running. Uncheck everything and check if it still happens.
That works
I stopped talkback, thank you very much
I had done the adb manipulation because for 5 days my macros have no longer been triggered. adb commands didn't change anything
Any idea of the problem?
The macros are validated (check mark). It worked perfectly for a long time and one day nothing works anymore
macro triggers are not in the system log
Last edited:
DISCLAIMER TO ANYONE TRYING THIS: PLEASE MAKE SURE THE "UNIVERSAL SWITCH" AND "TALKBACK" BOXES UNDER "KEEP ACCESSIBILITY SERVICES RUNNING" IN MACRODROID ARE UNTICKED BEFORE AND THAT ALL IMPORTANT MACROS ARE BACKED UP.
Have had the most frustrating two hours trying to get out of being stuck in Talkback.
To anyone with the talkback issue: as @Endercraft said above, it's because the Talkback (and Universal Switch) boxes are ticxked under "Keep Accessibility Services Running". You get into a loop that is hard to break of Android denying permissions to use it and MacroDroid reaffirming them again (and you get it saying "Talback on" loudly every few seconds and you can't do anything - even a restart doesn't help". In the end, lost patience and paid way too much for a subscription to a dodgy app (Coolmuster) to delete Macrodroid from my PC. Then, restarted and, whilst Talkback was still on, it was actually usable (if you search up instructions on how to online - three fingers for swipe etc.) and could finally turn it off through accessibility settings.
Have had the most frustrating two hours trying to get out of being stuck in Talkback.
To anyone with the talkback issue: as @Endercraft said above, it's because the Talkback (and Universal Switch) boxes are ticxked under "Keep Accessibility Services Running". You get into a loop that is hard to break of Android denying permissions to use it and MacroDroid reaffirming them again (and you get it saying "Talback on" loudly every few seconds and you can't do anything - even a restart doesn't help". In the end, lost patience and paid way too much for a subscription to a dodgy app (Coolmuster) to delete Macrodroid from my PC. Then, restarted and, whilst Talkback was still on, it was actually usable (if you search up instructions on how to online - three fingers for swipe etc.) and could finally turn it off through accessibility settings.
Winny57
Active member
If you have Shizuku enabled, I modified an existing macro to grant all possible permissions to the selected application.
Once triggered, you must choose which application will receive all possible permissions. The application will work and provide you with a result based on the permissions granted.
Once triggered, you must choose which application will receive all possible permissions. The application will work and provide you with a result based on the permissions granted.