Issue #107 solution candidate (Android service)

[b3b]

Service part implementation, with start and stop operations.
File 'service/main.py' from the application directory is treated as the service code.

Usage example, Kivy Remote Shell running in background: https://github.com/b3b/kivy-remote-shell .

[tito]

That's absolutely so cool. If i correctly read the PR, you need a service/main.py to automatically start this file as a service. And more than that, the service can be started/stopped by the main-ui app.

Do you confirm ?

I guess only the documentation would be missing, and maybe a little example on how we could communicate between UI and service.

THAT'S UBER COOOOOOOL!

[b3b]

File service/main.py is started/stopped as service, but not automatically, only when appropriate function is called from the main-ui.

Communication is limited in current state, service receive one string as argument when started - that's all. Seems it need to be improved.

Also, may be some part better be done with PyJNIus, but i was not using it (just not tried it yet).

[tito]

That's perfect for a PR. Thanks you very much for your contribution!

[akshayaurora]

@b3b would greatly appreciate it if you could a pull for the changes you did to the remote-shell too.

[b3b]

@akshayaurora Not sure. These changes restrict the remote-shell usage, since commands are executed in the non-UI thread. Attempt to use UI, like this:

Popup(title="simple UI usage").open()

will crash the app.