Got a response from Google that they will review the information I have provided and will get back to me when their evaluation is completed.
I'll keep you updated.
@Desmanto: Thanks for the list. Many very good examples! I'll send Google a few of your use cases when they should decide that I have to remove the accessibility features.
Accessibility Problem
Moderator: Martin
Re: Accessibility Problem
So only need to wait for the last confirmation from Google. I wish to see the good news soon.
Before using automagic, I almost never use accessibility. Now, I have used it to enhance a lot of daily activities, I don't want to lose it now.
Hope my thread also helps in convincing Google.
Before using automagic, I almost never use accessibility. Now, I have used it to enhance a lot of daily activities, I don't want to lose it now.
Hope my thread also helps in convincing Google.
Index of Automagic useful thread List of my other useful posts (and others')
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
-
Autumn-Leigh
- Posts: 67
- Joined: 15 Mar 2018 19:23
- Location: UK
- Contact:
Re: Accessibility Problem
Im not sure if its a solution, But I had that problem, but since its been rooted and I moved it to system app via titanium backup pro. its no longer a problem
YouTube Channel - https://youtu.be/fui3RO9EmNU
If anyone wants a shoutout, or has a flow they want me to do, be it theirs or a new one, let me know
If anyone wants a shoutout, or has a flow they want me to do, be it theirs or a new one, let me know
Re: Accessibility Problem
That's good idea too, but unfortunately not everyone can do that.
And the main problem here is from google. About half year ago, google sent a threatening email (as in first post) to remove/ban accessibility feature from the app (Automagic is one of them of course). Google has retracted what they have done, and now make some consideration and review. But until today, no one has know the final decision yet from Google. It is kinda a death sentence to the Control UI/UI Event feature (and other), but the judge delay the execution until undefined of time.
If I have app and have accessibility feature inside too, I won't develop anything more around those feature until I got a very clear statement from Google that I am allowed to continue to use it in the future. I don't want wasting so many time, and suddenly google email me the execution date, and all my works will be in vain. Even I can split out the accessibility feature, I need to start from scratch again.
This is what Martin faces right now. He had submitted the required information, including some example usage of the accessibility. Google said they will review, but no result yet till date. They just hang the case, giving uncertain outcome. We as user only can voice out our opinion in forum or report to the google. And I tried to help by creating a list of useful usage of accessibility from Automagic. Hoping that should google choose to block the accessibility for most other app, they will be at least lenient to Automagic since it is useful for its users. So we can still use the Automagic accessibility without any limitation. Till date, I have 73 Control UI and 18 UI event usages. By losing these functions, probably half of my 128 flows will become useless.
I don't want that to happen, so if next time Google send another threatening email about this accessibility, please help by voting against the ban.
And the main problem here is from google. About half year ago, google sent a threatening email (as in first post) to remove/ban accessibility feature from the app (Automagic is one of them of course). Google has retracted what they have done, and now make some consideration and review. But until today, no one has know the final decision yet from Google. It is kinda a death sentence to the Control UI/UI Event feature (and other), but the judge delay the execution until undefined of time.
If I have app and have accessibility feature inside too, I won't develop anything more around those feature until I got a very clear statement from Google that I am allowed to continue to use it in the future. I don't want wasting so many time, and suddenly google email me the execution date, and all my works will be in vain. Even I can split out the accessibility feature, I need to start from scratch again.
This is what Martin faces right now. He had submitted the required information, including some example usage of the accessibility. Google said they will review, but no result yet till date. They just hang the case, giving uncertain outcome. We as user only can voice out our opinion in forum or report to the google. And I tried to help by creating a list of useful usage of accessibility from Automagic. Hoping that should google choose to block the accessibility for most other app, they will be at least lenient to Automagic since it is useful for its users. So we can still use the Automagic accessibility without any limitation. Till date, I have 73 Control UI and 18 UI event usages. By losing these functions, probably half of my 128 flows will become useless.
I don't want that to happen, so if next time Google send another threatening email about this accessibility, please help by voting against the ban.Index of Automagic useful thread List of my other useful posts (and others')
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Re: Accessibility Problem
hello solved the problem with Android 9.0 by installing "Accessibilty Settings Shortcut" from dogfooder.
Re: Accessibility Problem
Uhhh, why? Accessibilty currently still working fine till now. Automagic has been exempted. In fact, after Android 10, Accessibility seems to be working much faster than android pie 9.0.
Index of Automagic useful thread List of my other useful posts (and others')
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Re: Accessibility Problem
Ewig schade, dass das weltbeste Programmierwekzeug so auf den Müllhaufen geworfen wird ( blöde accessibility). Ich habe 1971 das Programmieren gelernt, damals in Assembler. Automacig hat all das, was wir Generationen lang gesucht haben, einen grafischen Ablauf, eine einfache aber sehr potente Programmiersprache, super Testmöglichkeiten. Bin tief traurig, gibt es Hoffnung?