The tests are organised into a number of categories, covering:
adb communication functionality to the deviceadb to control wrtcAssuming your maemo device is a n810 and is connected on the 192.168.2.118 address, add to your client’s (desktop) /etc/hosts:
192.168.2.118 n810
Then export ADBHOST=n810.
From android-sdk_r3, adb
supports the explicit connect command.
hendry@x61 ~$ adb connect n810:5555
connected to n810:5555
hendry@x61 ~$ adb devices
List of devices attached
n810:5555 device
| id | summary | comment |
|---|---|---|
| 1 | connectivity | |
| 2 | push/pull | |
| 3 | port forwarding | |
| 4 | passing shell commands | |
| id | summary | key adb shell command(s) |
|---|---|---|
| 1 | install widget file | adb push <widget>; adb shell wrtc -i <install uri> <absolute file location> |
| 2 | prints full path to widget install directory | adb shell wrtc -P <INSTALL ID> |
| 3 | list all installed widgets | adb shell wrtc -l |
| 4 | run a widget | adb shell wrtc -r <INSTALL ID> |
| 5 | stop a widget | adb shell wrtc -k <INSTANCE ID> |
| 6 | validate widget | adb push <policy xml>; adb shell wrtc -v <INSTALL ID> |
| 7 | show widget configuration | adb shell wrtc -c <INSTALL ID> |
| 8 | setup security policy from file | adb shell wrtc -p <policy xml> |
| 9 | list running widgets | adb shell wrtc -L <INSTANCE ID>s |
Step by step instructions for testing the debugging functionality is kept on m5.2-test-steps.
Note that the debug connection runs over wifi and ssh, and can be transferring surprisingly large amounts of data during debugging. This makes the experience very slow.
There are workarounds to make the maemo device more alert, by making the device playback Internet radio.