Talkback bug

[Shiffo]

Hello, new here. I've been using macrodroid for some time now with no problems. Today i enabled adb hack to unlock more features and keep accessibility services running, that went well, but now there's a bug where talkback activates on its own and macrodroid doesn't let me disable it, it just lunches it again right away. The only solution i found is to revoke WRITE_SECURE_SETTINGS for macrodroid and then it allows me disable talkback.

Some times it boots with talkback mode on (for blind people), but it wasn't on when i turned off the phone.

Has anyone else had this problem?
Does anyone know of a possible solution?
Thank you all! Your help is very much appreciated!

Sorry for my terrible English

 

[Endercraft]

Check if talkback is enabled in keep accessibility services running and if any macro is causing that.

 

[Shiffo]

Hi, thanks for your answer! I have that option disabled, I even reinstalled the app just in case.
I was also thinking it could be a bug with a certain action from my macros, but I'm currently testing, haven't found what it is yet.

But I think it could be a macro that has some clicks on the screen, I have it set it to trigger on boot with a constraint "time since boot greater than 10s".
Is it possible that the macro keeps firing infinitely after the 10s?

I now added a constraint "time since boot greater than 10s" and "time since boot less than 20s" I'm checking if that solves it.

Thank you very much for you reply, i will keep you updated!

 

[Shiffo]

Update
I did some more testing and managed to reproduce the bug consistently.
In fact it is a macro that causes it, although I can't figure out why. I will adjunct screenshot.

The bug happens when device boot trigger fires on this macro (haven't tested if it does the same on any other macro, since I only use it there) and disabling the macro after the bug started doesn't solve it. Only solution is disabling the macro and rebooting the phone and then turn off talkback.
Any idea why this happens? The macro works as intended if it weren't for that.


Pd: you may notice that it's two macros in one, one for shake turn on torch and one to automatically write secure Folder password after boot, separated by if clauses. That's because i can't buy the premium app (i wish i could) and I already have 5 macros . Maybe the problem is there? Thanks

 

[MacroDroidDev]

Are you 100% sure you have not gone into the keep accessibility services enabled page in the settings and accidentally enabled the talkback accessibility service?

I can't see any reason the attached macro can have any effect on any accessibility service.

 

[Shiffo]

Are you 100% sure you have not gone into the keep accessibility services enabled page in the settings and accidentally enabled the talkback accessibility service?

I can't see any reason the attached macro can have any effect on any accessibility service.

effect on any accessibility service.

I was about to post one last update. It wasn't macrodroid settings, and also wasn't any of my macros , since I uninstalled the app and reinstalled with no macros, and the problem persisted. I figure it wasn't a bug , but most likely a malware that was abusing macrodroid privileges. I ended up reseting the phone to factory settings.
I don't have a pc ATM so I installed LADB (local adb) from a not a very trustworthy source.
Thank you very much for your interest in helping us! I will keep using macrodroid, I find it marvelous !

 

[WatermanGarry]

Hello, I just encountered the same issue. I confirm issue is not related to Microdroid 100% but related to Accessibility Service usage. I had exactly the same behavior with Automate. Didn't find any solution and removed the app. Then started Microdroid and history repeated. Not possible to disable TalkBack while Macrodroid is running and using Accessibility. Of course I checked TalkBack configuration and it was is disabled in the Settings before MD start. Just launching the application already causes the issue. For WRITE_SECURE_SETTINGS I used original ADB from Google SDK. Mobile antivirus scanning does not detect any problems. I cannot do a factory reset because have a few auth apps linked to hardware ids, resetting will force me to get each new token from scratch and ask many people to help.. I hope additional info will help to identify the problem (obviously between Google Services).
To exclude MD I did a simple test:

1. I disabled Android Accessibility Suite in Settings>Apps>Manage Apps>Android Accessibility Suite>Disable
2. Made sure MD stopped and unloaded from memory: MD App Info>Force Stop, no app in Recent menu
3. Enabled Android Accessibility Suite in Settings>Apps>Manage Apps>Android Accessibility Suite>Enable
4. Then Settings>Additional Settings>Accessibility>Vision>TalkBack, Option Enabled, I want to switch off it to prevent loading after restart, tapped Disabled>Stop in Confirmation Dialog
5. And TalkBack surprisingly starts! Now it's not possible to stop it without Accessibility Suite service disabling and MicroDroid was not used as you noticed.

If somebody has any comments - welcome)

 

[Shiffo]

Hello, I just encountered the same issue. I confirm issue is not related to Microdroid 100% but related to Accessibility Service usage. I had exactly the same behavior with Automate. Didn't find any solution and removed the app. Then started Microdroid and history repeated. Not possible to disable TalkBack while Macrodroid is running and using Accessibility. Of course I checked TalkBack configuration and it was is disabled in the Settings before MD start. Just launching the application already causes the issue. For WRITE_SECURE_SETTINGS I used original ADB from Google SDK. Mobile antivirus scanning does not detect any problems. I cannot do a factory reset because have a few auth apps linked to hardware ids, resetting will force me to get each new token from scratch and ask many people to help.. I hope additional info will help to identify the problem (obviously between Google Services).
To exclude MD I did a simple test:

1. I disabled Android Accessibility Suite in Settings>Apps>Manage Apps>Android Accessibility Suite>Disable
2. Made sure MD stopped and unloaded from memory: MD App Info>Force Stop, no app in Recent menu
3. Enabled Android Accessibility Suite in Settings>Apps>Manage Apps>Android Accessibility Suite>Enable
4. Then Settings>Additional Settings>Accessibility>Vision>TalkBack, Option Enabled, I want to switch off it to prevent loading after restart, tapped Disabled>Stop in Confirmation Dialog
5. And TalkBack surprisingly starts! Now it's not possible to stop it without Accessibility Suite service disabling and MicroDroid was not used as you noticed.

If somebody has any comments - welcome)

Thanks for your reply. Exactly that!
Im now using MD with ADB after factory reset and havent had any issue so far..