-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where to get sources of accessibility forwarder? #224
Comments
Hello @ex3ndr, the AccessibilityForwarder app is not open source yet, but we will work on it. There's no fundamental blocker, but we need to find someone with the time to do it and to iron out the details, especially around building it with open source tools (e.g. Bazel) instead of our internal build system (Blaze). @crawles is interested in getting it out because it's a critical component of https://github.com/google-research/android_world. I'll leave this issue open to track its progress. Cheers. |
Thanks! This would be insanely useful: i am trying to reimplement it (with slightly different networking) and normal usage of accessibility often misses some windows on some android versions and it would be very helpful to see how you guys achieved this. |
This change publishes the source code for `AccessibilityForwarder`, our app that receives accessibility events and trees and sends them externally via gRPC. This resolves issue #224. At the moment we do not have build files, this may come later. We are still deciding the build system (we'd like to use Bazel since it aligns with our internal build system), but for the moment this provides valuable information trying to use this, especially with [AndroidWorld](https://github.com/google-research/android_world). PiperOrigin-RevId: 686494976
This change publishes the source code for `AccessibilityForwarder`, our app that receives accessibility events and trees and sends them externally via gRPC. This resolves issue #224. At the moment we do not have build files, this may come later. We are still deciding the build system (we'd like to use Bazel since it aligns with our internal build system), but for the moment this provides valuable information for people trying to use this, especially with [AndroidWorld](https://github.com/google-research/android_world). PiperOrigin-RevId: 686494976
This change publishes the source code for `AccessibilityForwarder`, our app that receives accessibility events and trees and sends them externally via gRPC. This resolves issue #224. At the moment we do not have build files, this may come later. We are still deciding the build system (we'd like to use Bazel since it aligns with our internal build system), but for the moment this provides valuable information for people trying to use this, especially with [AndroidWorld](https://github.com/google-research/android_world). PiperOrigin-RevId: 686494976
This change publishes the source code for `AccessibilityForwarder`, our app that receives accessibility events and trees and sends them externally via gRPC. This resolves issue #224. At the moment we do not have build files, this may come later. We are still deciding the build system (we'd like to use Bazel since it aligns with our internal build system), but for the moment this provides valuable information for people trying to use this, especially with [AndroidWorld](https://github.com/google-research/android_world). PiperOrigin-RevId: 686494976
This change publishes the source code for `AccessibilityForwarder`, our app that receives accessibility events and trees and sends them externally via gRPC. This resolves issue #224. At the moment we do not have build files, this may come later. We are still deciding the build system (we'd like to use Bazel since it aligns with our internal build system), but for the moment this provides valuable information for people trying to use this, especially with [AndroidWorld](https://github.com/google-research/android_world). PiperOrigin-RevId: 686532420
Please see the newly added |
It seems that sources of APK are missing, is it opensource?
The text was updated successfully, but these errors were encountered: