How to charge your Android while streaming the screen (USB Power Delivery explained)

April 29, 2026 · ~9 min read

Disclosure: we make ChargeCast, a Windows tool that mirrors Android screens to OBS. The "charge while streaming" angle is our thing, but the underlying USB-PD physics applies to any tool you choose.

Why streaming the screen drains your phone faster than gameplay alone

A typical mobile gaming session pulls 4–6W from the battery. Add live screen mirroring over USB and that climbs to 6–9W: the encoder is now running continuously at high quality, the display stays at full brightness because the screen-off optimization is disabled, and the radio stays awake to keep the USB session up.

The result, on a 4500 mAh phone, is roughly:

For a hobby session that's fine. For a 4-hour Twitch stream or a tournament, that's a phone shutting down mid-broadcast — the moment that turns viewers away.

The USB-C Power Delivery basics that matter

USB-C is a connector. USB Power Delivery (USB-PD) is the negotiation protocol that decides how much power flows through it. They are not the same thing, and the difference is why so many "USB-C cables" don't charge phones during streaming.

Three things have to align:

1. The cable

A passive USB-C-to-USB-C cable rated for "data only" caps power at around 3W (5V/0.6A) — barely enough to slow the drain. A cable rated for PD passes 15W (5V/3A) at minimum, often 60W (20V/3A) or higher with the right markings. The cable that came with your phone is usually fine; the cheap one in the drawer often isn't.

2. The PC port

A laptop USB-A port is typically 5V/0.9A = ~4.5W. That's less than what a streaming workload pulls. The phone shows a charging icon, the percentage drops anyway. Modern USB-C ports on laptops and desktops handle 7.5W–15W and will actually keep the battery flat or rising.

3. The streaming tool

This one surprises people. The tool's --max-fps, --video-bit-rate, and --audio-source flags affect encoder load on the phone, which moves the dial between "draining slowly" and "actually charging." A 1080p 60fps stream at 12 Mbps draws meaningfully more than 720p 30fps at 4 Mbps — sometimes enough to flip from "+0.5%/min" to "−0.5%/min" on the same hardware.

Why scrcpy alone often isn't enough

Raw scrcpy over USB charges the phone only when the PC port can outpace the encoder draw. On a desktop with a beefy USB-C PD-capable port and a quality cable: yes, the phone charges. On a 5-year-old laptop's USB-A port: the phone drains, even though Android shows the charging indicator (because some current is flowing — just not enough).

The default scrcpy settings are tuned for low latency, not low power:

scrcpy --max-fps 60 --video-bit-rate 8M
# Roughly 7–9W phone draw.

Drop to a streaming-friendly profile and the math changes:

scrcpy --max-fps 30 --video-bit-rate 4M --no-audio
# Roughly 5–6W phone draw — within range of most USB-C ports to overcome.

The trade-off: 30fps looks fine on a Twitch viewer's screen, but feels less responsive when you're playing the game. Most streamers happily accept this; some don't. Knowing the dial exists is half the battle.

The "do these tools actually charge?" matrix

Tested on a Pixel 9a with a quality USB-C cable, plugged into the same desktop's front-panel USB-C port (15W capable). All values are after 30 minutes of continuous mobile gameplay capture.

Three takeaways:

• Wi-Fi mirroring forces you into a separate charger anyway, which is fine but ties up an outlet.
• USB streaming at lower presets reliably charges. At maxed-out presets, you're trading capture quality for battery life.
• "Charging icon visible" ≠ "battery actually rising." The percentage is the only honest signal.

How to verify charging is actually working

Before you commit to a 4-hour stream, run this 5-minute check:

1. Charge the phone to 50%. (Not 100% — Li-ion charging slows near full, which masks any drain.)
2. Start your streaming tool with the exact settings you'll use live.
3. Open a heavy game and play normally for 5 minutes.
4. Note the battery percentage at start and end.

If the percentage rose, even by 1%, you're net-positive — you can stream as long as you like. If it stayed flat, you have ~3–4 hours of margin from a 50% start. If it dropped, change one variable (cable, port, preset) and retest.

A trick that works: test from 50% upward. The charging curve is steepest in the 30–80% range, so you're seeing the system at its most generous. If it can't gain there, it definitely won't gain at 80%.

Common reasons the phone shows "charging" but the % drops

Old USB-A port on the PC

USB-A is capped at 4.5W on standard ports, sometimes 7.5W on "fast charge" labeled ports. Streaming pulls 6–8W. Math doesn't work. Switch to a USB-C port if you have one.

"Power-only" or "data-only" cable

Some USB-C cables are physically wired to do one job well and the other badly. The cheap ones from accessory bundles often skip the data lines that USB-PD uses for negotiation. Buy a known-good 60W+ rated cable and keep it labeled.

USB hub in between

Unpowered hubs split the upstream port's wattage across all connected devices. If your phone shares a hub with a webcam, an external SSD, and a microphone, the phone gets whatever's left over. Plug the phone directly into the PC.

The phone's own thermal throttle

When the phone gets warm, it deliberately accepts less charge to avoid overheating. A heavy 3D game can push the SoC above 40°C, at which point USB-PD negotiates down to a slower charge rate. This is normal and protective, but it means your "should be charging" config drains anyway when the room is warm. A small fan blowing on the phone case is the world's silliest fix that works.

Where ChargeCast fits in this picture

ChargeCast is a Windows wrapper around scrcpy with three things tuned for streaming:

• Streaming-friendly presets out of the box. The 720p preset (3 Mbps, 30fps) is specifically picked to net-positive on most USB-C ports. The 1440p preset is for users with strong PD setups who want headroom.
• 3-channel audio mixing inside the app. No virtual cable plumbing. Game audio, your mic, and PC audio each have their own slider.
• Survives the laptop-USB-A scenario. If the user's PC can't deliver enough power, the lower presets keep the phone net-positive instead of silently failing.

If you're already comfortable on the command line, raw scrcpy with the right flags does the same job for free. The trade is your time vs. the price of a Microsoft Store app.

Quick decision checklist

• Streaming < 1 hour, hobbyist? Don't worry about charging — start with 100% and finish before you're empty.
• Streaming 1–3 hours weekly? Lower-preset USB streaming + a known-good cable works fine. Verify with the 5-minute test.
• Streaming 3+ hours, frequently? Get a USB-C PD-capable port on your PC, a quality cable, and pick a tool that exposes preset profiles (scrcpy flags or ChargeCast presets — same idea).
• Streaming on a laptop that only has USB-A? Either dock with a powered USB-C, or stream over Wi-Fi with the phone in a charger. USB-A alone won't keep up.