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
Android 10 support #49
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
+1, this is a big blocker for me. I would love to know if anyone has any plans for how Android 10 support could be achieved. The engineers I work with believe a fundamental rearchitecturing of minitouch would be necessary due to a change in how permissions are structured for writing to IO driver files:
|
Hi, guys! Any updates in plans for android 10? |
Hi @Litsvin , As libevdev cannot access input devices anymore, the suggested workaround is to rely on STFService apk to inject the touch events through the Android InputManager (minitouch in this case, simply forwards the event to STFService) |
in that case,we need to develop a jar/dex run on /data/local/tmp which executed by app_process, and open a simple server on the jar/dex, then listen touch/tap/drag events send by websocket side, and transfer those events to MotionEvents, inject then to android side. |
@pcrepieux I see that both PRs above are merged. I would like to help, but I am not sure how. Should we just add instructions on how to run STFService (since it's needed on Android 10 devices) or should we also package the service, so minitouch "just works". |
Sorry for the delay. |
@stoefln I understand your point. The primary goal was to be able to have openstf controlling Android 10 devices. It should be possible to extract the MinitouchAgent from STFService.apk and put it in its own apk (or jar). It could actually completely replace the minicap binary but I didn't want to take the risk of breaking something. I'll give it a try but not sure when ... |
All the related PRs were merged and Android 10 support is available on openstf/stf HEAD. |
I don't get why this was closed. I don't see how people could use minitouch on Android 10 the way it is documented now... Isn't there something missing guys? Or am I missing something? |
In case of minitouch alone nothing has changed. Prebuilt minitouch binaries are available in minitouch-prebuilt-beta npm package. This one is not documented but also not officially supported. |
@koral-- Sorry, but I am still confused. Here is what I know: I use minicap without STFService in my application. Starting with Android 10 I realised that there is a problem which is not easily fixable. |
@stoefln , As explained here, it could be improved to ease minitouch standalone usage but the priority (at least mine) was to have it running together with openstf. Meanwhile, I agree a small paragraph could clarify a bit more, will try to do it. You could also submit a PR for this once you verified the above steps are correct (hoping they are...). |
@pcrepieux ok, basically it was clear to me already before, but now I am sure I got it. I just wondered about why this ticket was closed.. I will try to get it running and send you a PR.. Thanks |
OK now I understand, reopening. |
#58 was merged, so I guess this can be closed as well. |
I think the same problem is on LGE phones, 64 bit and 32 bit phones
|
ooh sorry did not see the issue is closed |
@man4567890 I get the exact same errors; "Unable to find device data", following be a series of minitouch permission denied errors. I get it for 2 different Android 10 phones: A Essential PH-1 phone, and a Samsung Galaxy Note 9. |
Thanks @nanoscopic , are you aware of any kind of fix for this? It's driving me insane, but I don't have the technical abilities to fix this... |
Those "errors" are actually expected and appear even when everything is "working properly". You do have additional errors though besides the ones I mentioned. "Frame producer died" specifically should not happen and indicates that you won't get video in stf. I can verify though that Android 10 support is working though, and this ticket is correctly closed. You should open a new ticket with your other specific errors, and then see who can help you there. You should mention in your ticket how you setup your system, specifically which commit of the project you are using, what platform you are running on, and how you are starting everything up. Also mention what model phone you are using and the android version. |
as far as I know inject inputs from "InputManager" is not the same as direct touch screen. |
Do you guys have plan to support Android 10? Since version 10 have been quite popular? Thank you!
The text was updated successfully, but these errors were encountered: