The fuzz testing found a file descriptor leak in the XMPP git push code. The assistant seems to hold up under fuzzing for quite a while now.
Have started trying to work around some versions of Android not letting
the am
command be used by regular users to open a web browser on an URL.
Here is my current crazy plan: Hack the terminal emulator's title setting
code, to get a new escape sequence that requests an URL be opened. This
assumes I can just use startActivity()
from inside the app and it will
work. This may sound a little weird, but it avoids me needing to set up a
new communications channel from the assistant to the Java app. Best of all,
I have to write very little Java code. I last wrote Java code in 1995, so
writing much more is probably a good thing to avoid.
Does the Android application use a WakeLock to ensure syncing happens even if the device screen goes off?
I'm under the impression that it doesn't since it took a very long time to sync the first time (before I used the terminal's options to prevent the phone from sleeping).
I think that option shouldn't be left on since it would waste the battery and I think the application should block sleep mode only when syncing.
I might be wrong. I never had to use a WakeLock on Android yet.
The terminal has options to take the wake lock, and also the wifi lock, in its menu.
Currently this has to be managed manually. The assistant does not try to deal with this.