Flysky module users - You need to read this

As of the nightly build eb9ea9f1006f (released just now) the flysky module will be disabled unless you update your tx.ini.
If you look at the current tx.ini you will see this:
[modules]
# enable-cyrf6936 = B12
# has_pa-cyrf6936 = 1
# enable-a7105 = A13
# has_pa-a7105 = 1
# enable-cc2500 = A14
# has_pa-cc2500 = 1

you must un-comment the 2 'a7105' lines to re-enable the flysky/hubsan protocols If you are using a flysky module without a poweramp (like the xl7105) then only uncomment the 1st line.

For users with a devo7e who haven't modified it, I recommend adding: has_pa-cyrf6936 = 0

There is no need to uncomment the 'enable-cyrf6936' line. for anyone. This is automactically enabled by the firmware.

You can tell if the protocol is enabled on the model page by looking to see if the protocol has an '*' in front of it. Those with an '*' are NOT enabled because the module is not properly configured.

After Tx setup and check tx.ini, I see that all lines enabled. Is it normal?

[modules]
enable-cyrf6936 = B12
has_pa-cyrf6936 = 1
enable-a7105 = A13
has_pa-a7105 = 1
enable-cc2500 = -0
has_pa-cc2500 = 0

I don't see this. I see that I get 'None for a7105 and cc2500
did you uncomment the entire module section or just the a7105 lines?

I replace tx.ini without modification. Then setup Tx and check tx.ini. I meant that all # disappeared.

current_model=1
language=10
music_shutdown=0
mode=2
brightness=6
contrast=5
volume=9
vibration=0
batt_alarm=4300
batt_critical=3800
batt_warning_interval=10
[modules]
enable-cyrf6936=B12
has_pa-cyrf6936=1
enable-a7105=-0
has_pa-a7105=0
enable-cc2500=-0
has_pa-cc2500=0
[calibrate1]
max=3691
min=448
zero=2112
[calibrate2]
max=3627
min=361
zero=1981
[calibrate3]
max=3649
min=476
zero=2028
[calibrate4]
max=3614
min=368
zero=2012
[touch]
xscale=187245
yscale=137625
xoffset=-379
yoffset=-17
[autodimmer]
timer=20000
dimvalue=1
[countdowntimersettings]
prealerttime=15000
prealertinterval=5000
timeupinterval=2000
[telemetry]
temp=celcius
length=meters

Seems all OK. If I uncomment lines before replace tx.ini, # disappeared, but values changed to 0 for cc2500. If I replace tx.ini without uncomment lines for a7505, these lines also have values 0.

[modules]
enable-cyrf6936=B12
has_pa-cyrf6936=1
enable-a7105=A13
has_pa-a7105=1
enable-cc2500=-0
has_pa-cc2500=0
[calibrate1]

yeah it should have been a ';' instead of a '#' in the tx.ini.
I've also fixed it so wit will write 'None' for unused modules

I updated the release notes which is where this info belongs.
If your module has a metal cage it has a power-amp. if it cost more than $5 it probably has a power amp. If it is advertised as '500m' or '1000m' it has a power-amp. If you know the link of the module you bought, I can tell you as well. If you still don't know, try enabling the power amp, and set the power to 1mW. If it still works at over 2 meters, you have a power-amp.

I think something wrong with editing tx.ini file. Try fresh 'tx.ini' from archive, uncomment two lines for A7105 and replace 'tx.ini' in Tx. Then recalibrate and retune Tx.

If you are using 2.0 make sure to verify that the model is still setup properly. the 3.0 models are generally not compatible with 2.0. If it was working before, there is nothing in the 3.0 upgrade that would actually damage the module. Also, my experience is that they are fairly robust to mishandling.