When a QuickQ protocol change never leaves Connecting, disable Kill Switch, disconnect fully, change Fast/UDP ↔ Compatible/TCP once, then connect once. Do not mash the control mid-handshake. Corporate firewalls and some venue APs silently drop UDP; if TCP comes up in 20 seconds, pin that SSID to Compatible. At home, a failed switch is TAP/Wintun until you prove otherwise.
Games and UDP: boost. Switch-window blackouts: Kill Switch. Office UDP: office. Drivers: TAP. 2.5.0: download.
Same node, only the protocol moves
Pin a pop, force global, switch off. UDP/Fast for 30 seconds, test page. Disconnect, TCP/Compatible, 30 seconds. Who reaches Connected, who buffers, who dies in a minute. Both Connecting: not protocol—permissions, TAP, account.
UDP dead only on one SSID, TCP alive: write the SSID down, default Compatible there. At home, try Fast again. Do not run office TCP on the living-room line “for safety.”
| Network | Try first | Then |
|---|---|---|
| Home broadband | Fast / UDP | Compatible; then TAP |
| Office / campus | Compatible / TCP | Still TCP on another node |
| Airport hotspot | Compatible | Cellular A/B |
| TV / router | Whatever that device documents | Do not copy the phone toggles—TV article |
Failure paths during the change
Some builds hot-swap; some require a new session. A failed hot-swap leaves “Connected” in the tray and the old IP on the test page. Fully disconnect for ten seconds. Smart routing can cache the old protocol’s split—global for three minutes—smart.
Android Always-on will not let you tear the tunnel down; the change looks like a no-op. Disable Always-on, switch, re-enable—Always-on. iOS denying the extension mid-switch makes every protocol look dead—permissions.
Linux protocol changes often mean a different binary and capabilities. Do not flip protocols over SSH with a firewall “switch” armed—Linux.
SMS and split-app sitting on the same click
A protocol change that drops the login session will ask for SMS while the tunnel is half-open. That is SMS, not “TCP blocks codes.” Split-app can leave a game bound to a UDP socket you just destroyed—per-app.
Three hot-swaps, then a cold one, then stop
Disconnect, wait for the key icon to die, change protocol, connect. Still failing: same experiment on a second node. Five tries: stop. Write SSID, protocol label, TAP health. Venue choices: public Wi-Fi. Guides: hub. FAQ: FAQ. Drop timelines stay in drops; do not mix them into the protocol minute.
Two lines in Notes: “office SSID + Compatible,” “home + Fast.” QuickQ is a one-tap client; protocol should not become a daily fidget spinner.