Thank you for your reply. I don't say that the mapping is not correct because of your application, but because of the flysky mapping which is special, not like generic android gamepad.
I learnt in an other thread that android generic gamepad is using X, Y, Z and RZ axis. The flysky (and maybe other RC controler) has the yaw assigned to the RY axis.
So, for use flysky, aTelloPilots would need the possibility to map every stick with every axis, to work with RY axis, to have possibility to invert stick (invert up and down or left and right)...
If i am not wrong, aTelloPilots do nothing of that (it is not a reproach at all, your app is great). For me, the best solution for controller configuration is to ask to the user to move every stick and assign it to the axis the value has changed (Like Fpvfreerider, Picasim, or FPVTello but the RY axis is not yet managed in the current version).
Or have a tab which allows to change axis, something like that :
Yaw = -RY_Axis
Throttle = +X_axis
....
Sorry for my bad english, have a good day.