I guess what my issue with firmware is...is that something recently caused significant range decrease and I am trying to get back to before that happened. I am not sure if it was aircraft or rc firmware or both...and maybe the app as well ..
Sometimes when the Go app or RC firmware is updated, this can reset the settings in the GO app. Your original settings can sometimes go back to default, so beware of this possibility. If you haven't disabled auto-update in your device, you may get surprised.
Range performance is relative to each person's comfort zone. Some guys never go beyond VLOS, in which case most any settings are acceptable in GO to reach a half mile. They might say, I have no problem if they don't fly farther than half mile. But for others that expect a range of 2 miles or farther, the settings in GO can significantly affect range. Some swear by auto for channel selection, arguing that it's dynamic. I'm not in that group, I've had poor range (dropouts at starting at 3000') experiences using auto. I always select a custom channel that has the least traffic, minimizing interference from WiFi signals in the area. However, I also use the 32ch hack that lets me fly on channels 30, 31 and 32, which are usually always very quiet. The GO app shows you the activity on each channel, making it easy to select the least busy channel. FYI, without the 32ch hack, I find ch 22 is usually good to use in most areas.
Here's the key setting.....With a custom channel selected, you will then see the option to reduce the bit rate, or "Transmission Quality". The lower the bit rate the farther you can go, because the radio has less work to do, receiving less data. A slower bit rate inherently increases range with little affect to the image quality on the display device (I use iPads). The lowest setting is 4mbps, which is what I always fly with. So every time you update the Go app, you need to remember to check your settings and make sure they are set to your preference.
I rarely update my GO app or firmware in the RC or craft. There has to be a really good reason to risk changing something that's not broke. My versions are in my signature.
