This happened to our team during the first qualification match at the Canadian regional. It's too bad too 'cause we would have won the round easily: it was two vs one, and both of our robots were disabled from the getgo. Our alliances had an untested autonomous which gave them a code error (probably an infinite loop) so they were immobile for the round. And we had that radio problem. To the best of my recollection, the "receiving" light would blink for a few seconds, then cut out for a few seconds. It was very aggravating; couldn't really do anything.
We tested everything before the match, and the radio worked fine in the practice area setup in the pits. But when both of our robots got on the field, BOTH of us seemed to have the same radio error lights come up. I don't know if our alliance partner would have had the same error while driving around though 'cause of that code error. We took the robot back to the practice area after the loss, had the same problem, and the Innovation FIRST guy couldn't figure it out. I think we just tightened our connections and then it was working fine.
What cheeses me off the most though is that when both of our robots were having the same error lights when we were setting up on the field, the FIRST employees tried to fix things... they had us setup our tether (for some reason beyond me) and we both still had the same radio error lights coming up and they decided to start the match anyways when it seemed as though it was a FIRST error. I understand there's a schedule to keep to, but it hardly seems fair to me that teams should suffer because of a silly problem like the radio transmissions. If I remember, Simbotics had a radio error too and they were going to start the match anyways, but then their field mentor ran out and was adament about delaying the match until they fixed it (which they did) Good for you!
Of course... we all know it's hard try and make the competition fair... just easier to remember the bad luck you get than the good luck
