Interesting. This is a bit of a tale, apologies. Maybe related, perhaps not; I'm not savvy enough in these matters to know.
My Air arrived last week and from Sunday till now I've had multiple tries, I think four all told to establish control of it.
Connection was far from easy, initially. But after the usual set up hiccups with updates and so on (I already have a DJI account) and after trying out the simulator without drama I have now, as said above, had four ultra short take-offs and forced-grabs to curtail the process, because the only thing this controller seems able to do is to start the motors and initiate a take off. And killing the motors, that works. Outside the simulator, the right stick has zero function, absolutely nothing. But that's only feeding to the app itself in the phone, not to the aircraft. Which only proves (I suppose?) that the control itself has function. But apparently not able to feed that function to the Air.
The lights that should be green are green when connected, the screen announces it's ready to go (amber - vision) when indoors as expected, but there is zero direction control function after takeoff's been started. The last try I had the phone in place with all other comms turned off in "flight mode" and connected via the shortie cable to the usual side connector.
With the single attempt at outside flight, the pattern was identical although once off the deck it was stable horizontally, as GPS lock was present. If I'd not grabbed the bloody thing it'd have been hovering there till the battery died. I've been bringing my grabhand up from underneath quickly.
I've looked through the menus in search of something obvious, with no result. Except that the channel being used is 5.8ghz - no.153. Since the two devices connive to announce things are ready for take off, I'd thought that essential data was all being fired via this one channel, which seemed odd. The phone's a Galaxy S6.
Another oddity is the RC refuses to connect to DJI Assist, although the drone registers and shows its update history and status. Googling around shows plenty of issues to do with connecting but none I could see were similar to what's going on with mine. I can't see any way around a return. It's sapped my DJI confidence no end.
I guess it's possible I'm guilty of some bonehead oversight, but if so I've been unable to ID it. My other craft is a
P4, but I'd claim no expertise with it - even so, have never had a single issue with its behaviour, which has been impeccable so far.