HI, All
Remote control of non-rooted Android 8+ (like TeamViewer Host):
1) A central server that passes the data between User-client and Host-client via mobile 4G Internet
2) User-client - app or webpage that shows Android's screen from the Host-client
3) Host-client: foreground service on controlled Android device, it is woke up by push-messages from a server (Firebase ?) when and if the user is successfully logged in into his server's account. Connection is without Android's user confirmation, immediatelly.
4) Android's screen is sent to server by screenshots, anyhow
5) BUT - how to make taps ?
TeamViewer system (with their Host app) works as needed - but how it works on non-rooted devices ?
TeamViewer Host installs extra addon depending on the device brand. Maybe is this addon somehow signed by the brand's key to be system for tap simulation ?
Remote control of non-rooted Android 8+ (like TeamViewer Host):
1) A central server that passes the data between User-client and Host-client via mobile 4G Internet
2) User-client - app or webpage that shows Android's screen from the Host-client
3) Host-client: foreground service on controlled Android device, it is woke up by push-messages from a server (Firebase ?) when and if the user is successfully logged in into his server's account. Connection is without Android's user confirmation, immediatelly.
4) Android's screen is sent to server by screenshots, anyhow
5) BUT - how to make taps ?
TeamViewer system (with their Host app) works as needed - but how it works on non-rooted devices ?
TeamViewer Host installs extra addon depending on the device brand. Maybe is this addon somehow signed by the brand's key to be system for tap simulation ?
Last edited: