Revision history [back]

The robot remocon is not just a way of starting android apps, you can also use it to just fire up launch configurations on the robot. That's what you are seeing here (albeit unintentionally). You'll note that there are two rocon rapps available, one is talker, one is listener.

The talker rapp has a launcher that starts a ros tutorials talker on the robot. In that configuration file, you'll also see it has a defined pairing client for android - a listener android app. i.e. the robot starts the launcher, the android starts the pairing client.

The listener rapp doesn't have a pairing client (yet - simply because we never got around to writing it). So it fires up the listener on the robot, but doesn't do anything on the robot side.

This behaviour can be useful if you just want to use the robot remocon for starting and stopping launch configurations on your robot.