APM Telemetry using an Android Smartphone


A big enabler for UAVs going forward, especially with respect to commercialization, will be improving telemetry range. On that note, I've released my MAV Downlink Android application and associated tools today.

MAV Downlink opens up a new communication pathway for you to talk to your UAV while it is on a mission. This pathway uses an on-board Android smartphone to push MAVLink communications onto the Internet, then adds an intermediate server that hosts these communications and binds them to interested Mission Planner applications.


Pictured above is the general gist of the application.

I have been using it for the last few months to be able to communicate with my Sky Hunter in flight at essentially any range as long as I am at a field with good cellular service.

I know this idea isn't totally unique as there are several guides on how to enable UAV telemetry using cellular modems. To my knowledge, though, this is the first application that enables you to accomplish this easily using an old Android smartphone you probably have laying around. The big gotcha is that the smartphone must have an OTG compatible USB port. Fortunately, there are many cheap phones with these, notably the Galaxy Nexus:

Right now, this application requires you to run your own dedicated server to host communication between the onboard smartphone and your MAV mission planning application. It also sends MAV commands in the clear with no authentication or encryption over public wireless airwaves. As such it is only really useful for hobbyists with good knowledge of networking.

It has also been brought to my attention that the Pixhawk cannot be connected to a standard Android phone via OTG. You may be able to put together a custom powered hub that connects to the Android phone but I cannot make any gaurantees. This has been tested on APM 2.6 and 2.5 boards.

I would like to develop this application further by adding dedicated servers so that virtually no set-up is required on the end-user's side. This would also enable me to add authentication and encryption to the communications channel so people using this do not risk their UAV being hacked.. no matter how unlikely that might be.

However, it works fine for me right now. Before I put any effort or money into improving it, I wanted to gauge public interest in it. Please let me know if something like this interests you by dropping a comment below.

You can try the application now. Here is a link to the Android application:
And the users manual:

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones


  • What doesn't work? You should not be using MavMapperCmd.jar, it is for command line usage only, intended for running on a server. Windows users should be using LocalMavMapper.jar. If you did run MavMapperCmd.jar, you'll need to force kill the Java process on your computer or restart it before LocalMavMapper.jar works again.

  • Right, and not on win 8.1 64bit either

  • Now is not working on Windows7 64bit.

  • That did it. Thank you.

  • Whoops - my bad. Had an unclosed infinite while instead of sleeping a thread out as I should have. Updated the application; same place: http://applieduas.com/MavMapperCmd.zip

  • James, 

    I just noticed that the MavMapperCmd.jar you sent goes to 100% CPU usage while running with nothing connected. Is it possible to get a fix for that? Even a small delay in the main event loop would help.

    I haven't been able to test with the drone connected yet, so I'm not sure if that would change things.

  • @nick

    Both Nexus7 tablet and Samsung S5.


    Thank you.

  • @playfieldofangels - what mobile device are you using?

  • Honestly I don't know then. I will really have to get my own Pixhawk to figure that out. Sorry to those of you using this autopilot..

  • Problem with Pixhawk for me is not power related but connectivity via ODG..

    If Pixhawk powered via main battery there is no problem  regarding power.

    The problem as i say is connectivity via ODG.

    The APP does not recognize the Pixhawk when connected.

This reply was deleted.