Fix your uConsole's
broken WiFi.

By default, Linux aggressively power-manages the WiFi chipset to save battery. On the uConsole, where signal is already marginal, this causes the radio to sleep at the worst possible times — triggering disconnects and slow reconnects.

# Check current power management status
$ iwconfig wlan0 | grep "Power Management"
  Power Management:on

# Disable it immediately
$ sudo iwconfig wlan0 power off

# Make it persistent across reboots
$ sudo tee /etc/NetworkManager/conf.d/wifi-powersave.conf << 'EOF'
[connection]
wifi.powersave = 2
EOF

# Restart NetworkManager
$ sudo systemctl restart NetworkManager

Why it works: Keeps the radio active at all times, preventing the chipset from entering low-power states that drop your already-weak connection. Trade-off: slightly higher battery drain (~5-8%).

The Broadcom/Cypress WiFi chipset on the CM4 has driver-level settings you can tune for better signal handling in low-signal environments.

# For CM4 (brcmfmac driver)
# Create/edit the driver config
$ sudo tee /etc/modprobe.d/brcmfmac.conf << 'EOF'
# Disable roaming (prevents needless scanning)
options brcmfmac roamoff=1
# Increase power output
options brcmfmac feature_disable=0x82000
EOF

# Apply without reboot
$ sudo modprobe -r brcmfmac && sudo modprobe brcmfmac

Why it works: Stops the driver from wasting time scanning for “better” access points (there aren't any), and pushes the radio to use maximum TX power.

The default regulatory domain is often set to “World” (00), which uses the lowest common denominator for TX power. Setting it to your actual country unlocks higher power output on legal channels.

# Check current regulatory domain
$ iw reg get

# Set to your country (examples)
$ sudo iw reg set US   # United States
$ sudo iw reg set GB   # United Kingdom
$ sudo iw reg set DE   # Germany
$ sudo iw reg set JP   # Japan

# Make persistent
$ sudo tee /etc/default/crda << 'EOF'
REGDOMAIN=US
EOF

# Verify the change
$ iw reg get | head -5

Why it works: Many countries allow up to 20 dBm TX power on 2.4 GHz, but the “World” default limits it to ~14 dBm. That's a significant difference when you're signal-starved.

5 GHz WiFi has shorter range and is more easily attenuated by the aluminum shell. If your router supports both bands, force the uConsole to stick to 2.4 GHz for better penetration through the case.

# Via NetworkManager (recommended)
$ nmcli connection modify "YourNetworkName" \
    802-11-wireless.band bg

# Or edit the connection file directly
$ sudo nano /etc/NetworkManager/system-connections/YourNetwork.nmconnection
# Under [802-11-wireless], add:
# band=bg

# Restart the connection
$ nmcli connection down "YourNetworkName"
$ nmcli connection up "YourNetworkName"

Why it works: 2.4 GHz signals have better wall/metal penetration than 5 GHz. Forcing this band prevents the chipset from hopping to a stronger (but more attenuated) 5 GHz signal.

When the connection drops (and it will), this watchdog automatically reconnects. It's not a fix — it's a bandaid. But a good bandaid while you decide on a hardware solution.

#!/bin/bash
# WiFi Watchdog for uConsole
# Save as /usr/local/bin/wifi-watchdog.sh

GATEWAY=$(ip route | grep default | awk '{print $3}')
INTERVAL=30  # Check every 30 seconds

while true; do
  if ! ping -c 1 -W 3 "$GATEWAY" &>/dev/null; then
    logger "wifi-watchdog: connection lost, restarting..."
    nmcli radio wifi off
    sleep 2
    nmcli radio wifi on
    sleep 10
  fi
  sleep $INTERVAL
done

# Make executable
$ sudo chmod +x /usr/local/bin/wifi-watchdog.sh

# Create systemd service
$ sudo tee /etc/systemd/system/wifi-watchdog.service << 'EOF'
[Unit]
Description=WiFi Watchdog for uConsole
After=NetworkManager.service

[Service]
ExecStart=/usr/local/bin/wifi-watchdog.sh
Restart=always

[Install]
WantedBy=multi-user.target
EOF

# Enable and start
$ sudo systemctl enable --now wifi-watchdog

The community's top pick. Tiny form factor, native Linux driver support (rt2800usb), and rock-solid on ARM. Plugs in and works immediately on both stock and community images. Low power draw (~180mA). The only downside: 2.4 GHz only, but that's actually what you want here.

$ lsusb | grep -i ralink
Bus 001 Device 003: ID 148f:5372 Ralink Technology, Corp. RT5372

$ iwconfig wlan1
wlan1     IEEE 802.11bgn  ESSID:"YourNetwork"
          Mode:Managed  Frequency:2.437 GHz

Extremely small — barely protrudes from the USB port. The v3 revision uses the RTL8188EUS which has mainline Linux support. Slightly weaker signal than the Panda, but the form factor is unbeatable for portability. Very low power (~120mA).

# Usually works out-of-box, but if not:
$ sudo apt install firmware-realtek
$ sudo modprobe r8188eu

# Verify
$ ip link show wlan1

The premium option. Dual-band, excellent Linux support (mt76 driver in-kernel), and Alfa's legendary sensitivity. It's bigger than the others and draws more power (~350mA), but if you need maximum range and speed, nothing beats it. Popular with the pentest crowd for a reason.

The CM4 has a U.FL antenna connector on the board that's not connected by default. The onboard PCB trace antenna is used instead. By connecting a U.FL cable to this pad, you can route a proper antenna to the outside of the case.

Step 1: Open the uConsole (6 screws on the back)
Step 2: Locate the CM4 module — find the U.FL pad
        (small circular pad near the WiFi chip, labeled "ANT")
Step 3: Connect the U.FL end of the pigtail cable to the pad
Step 4: Drill a small hole in the back panel for the SMA connector
        (bottom-right corner recommended — least visible)
Step 5: Route the pigtail through and mount the SMA bulkhead
Step 6: Attach your external antenna
Step 7: Reassemble and test

⚠ Important: The CM4 has a resistor (R47) that selects
  between the PCB and U.FL antenna. You may need to
  move/remove this resistor to switch to the external
  connector. Check the CM4 datasheet for your revision.

Result: Expect signal strength comparable to the bare CM4 board (-35 to -45 dBm). This is the gold standard fix if you're willing to modify your case.

A lower-effort mod that improves the antenna's ground plane without drilling holes. By placing copper tape strategically inside the case, you can reduce some of the destructive interference from the aluminum shell.

Step 1: Open the uConsole
Step 2: Apply copper tape along the inside of the back panel,
        creating a gap/window directly above the CM4's WiFi chip
Step 3: Do NOT cover the area directly above the antenna trace
Step 4: Ground the copper tape to the CM4's ground plane
        (use a short wire to a GND pad)
Step 5: Reassemble

Note: Results vary. Some users report 5-10 dBm improvement,
others see little change. It depends on your specific unit's
internal geometry.

Verdict: Worth trying if you're already opening the case. Low risk, low cost. But don't expect miracles — the U.FL mod or a USB adapter will give more reliable results.

Community members have designed 3D-printable brackets that mount a small external antenna to the uConsole's expansion port area. Combined with the U.FL mod above, this gives you external antenna performance without permanently drilling the aluminum shell.

Search “uConsole antenna bracket” on Thingiverse or Printables for community designs. The most popular design replaces the expansion module cover with a version that has an SMA bulkhead cutout.

The community consensus. Panda PAU05 or TP-Link TL-WN725N plugged in, onboard radio disabled. Simple, reversible, and reliable. This is what most daily drivers end up doing.

Power management off + regulatory domain set + 2.4 GHz forced + roaming disabled. No hardware needed. Good enough for home/office use where your router is nearby.

A 6-inch USB extension cable lets you position the adapter away from the aluminum body. Some owners velcro the adapter to the back of the screen lid, getting the antenna as far from the case as possible.

Use your phone as a Bluetooth PAN (Personal Area Network) hotspot. Bluetooth signal is less affected by the aluminum shell since it uses different frequencies and power levels. Not fast, but reliable for SSH and basic web.