3%, I'm happy you have a retired technician certificate, I applaud you. However, I was a technician before I became a hardware engineer, then a software engineer. Technicians are great at 1st level support people but when they can't resolve the issue, the issue is turned over to second tier, then third tier, then eventually works its way back to the engineers like myself, who resolve the issue. Technicians don't handle complex tasks like developing software, re-engineering software applications, comparing module changes to test application conflicts amongst each other, let alone the OS or hardware platform. This is what I do and I do it very well. I can tell you with 100% certainty that the issue is not the tablets. The issue is easy for me to see, yet somewhat complex to explain since it does manifest itself as a tablet issue at first, so I can see how you might think it's a tablet issue. After performing test after test after test with every variable imaginable and speaking with 3 different DJI reps, we've discovered that it has to do with the latest remote control firmware not playing well with DJI GO. I agree that there are people out there that have had the "no signal" issue because they had a bad controller cable, a bad gimbal cable, or didn't have their settings correct. However, for the majority of us that are having this "no signal" issue, ours is directly related to the latest RC firmware update not playing well with the latest versions of DJI GO. I don't work for DJI, or have access to open their scripts and analyze their program, but if I did I would like to test the addition of the lightbridge 2 modules that were built into the latest 2 or 3 versions of DJI GO. I have a funny feeling that could be part of the culprit. So you say it's the tablet, I say it's the RC. To be technical, it's the DJI GO application running on the tablet that doesn't play well with the latest firmware update for the controller, and that's why you mistake this for a tablet issue.