futureware-tech / rover-android-client Goto Github PK

Travis build often fails because :connectedCheck can't establish connection with Android emulator. Perhaps the latter is getting OOM-killed?

Debugging idea: install sshd and reverse-tunnel it, so that one can ssh into the machine and probably see the issue.

Exact error: http://pastebin.com/raw/FLN5rc7X

http://build.sheremet.ch/dasfoo/rover-android-client/master/lint-results-debug.html

The settings are transferred using headers:

X-Capture-Server-WIDTH
X-Capture-Server-HEIGHT
X-Capture-Server-FPS
X-Capture-Server-PASSWORD

List of original modes:

Let the user choose the resolution from drop-down, then choose FPS from allowed range (using drop-down or slider).
Once a resolution is selected, show a comment (e.g. "sensor cropped" or "full FOV").

Video stream is decoded into NAL units and sent to the surface; the NAL splitting algorithm needs to be optimized.

Before we start with optimizations it is necessary to add some tests to make sure the optimizations don't break the pipeline.

Currently lint results are visible in Travis build log and are uploaded as artifacts externally; it's still very hard to spot a change there unless there was an error, and it's easy to miss out.

Ideas:

• fix all lint warnings and make lint fail on any warning (too tough at times)
• make a Required check to find lint errors (need external service)