R36S Not Charging? Here's the Fix
Your R36S has a USB-C port, but most USB-C chargers won't work with it. This is the single most common support question for the R36S — and the fix is simple once you understand why it happens.
Why Your USB-C Charger Doesn't Work with the R36S
The R36S has a USB-C charging port, which leads most people to grab their nearest USB-C cable and charger. The problem: those chargers almost certainly won't work, delivering zero power to the device.
The root cause is missing hardware. The R36S lacks CC (Configuration Channel) resistors on its circuit board. These resistors are what allow a device to participate in the USB-C Power Delivery protocol.
Here's what the USB-C PD handshake normally looks like: the charger asks "how much power do you need?" and the device replies with its requirements. Only then does the charger begin delivering voltage. Because the R36S has no CC resistors, it cannot reply to this question. The charger receives no response, assumes nothing is connected, and delivers 0V.
This affects all of the following:
- MacBook chargers and other laptop USB-C bricks
- Samsung fast chargers (USB-C)
- Any USB-C Power Delivery wall brick
- USB-C to USB-C cables of any kind
This is not a defect — it's a design limitation. The fix is simply using the right cable.
The Correct Way to Charge Your R36S
What You Need
The solution is straightforward: use a USB-A to USB-C cable. The rectangular end (USB-A) plugs into your charger; the oval end (USB-C) plugs into the R36S. When you use a USB-A port as the source, there is no PD handshake — the port simply outputs 5V, which the R36S accepts without issue.
For the charger, any basic 5V/1A or 5V/2A USB-A wall brick works perfectly. This includes old Android phone chargers, basic USB hubs, and PC USB ports. You do not need anything special.
| Charger Type | Cable | Result |
|---|---|---|
| Basic USB-A brick (5V/1-2A) | USB-A to USB-C | Charges correctly |
| MacBook/laptop USB-C charger | USB-C to USB-C | 0V — won't charge |
| Samsung/Qualcomm fast charger | USB-C to USB-C | Won't charge |
| Power bank with USB-A port | USB-A to USB-C | Works |
| Power bank with USB-C only | USB-C to USB-C | Won't charge |
| PC USB-A port | USB-A to USB-C | Works (slow) |
Step-by-Step Charging Check
- Use a USB-A to USB-C cable (not USB-C to USB-C)
- Plug into a basic USB-A charger with 5V output
- Wait — if the battery is fully drained, the LED may not light up for 30-60 minutes. This is normal trickle charging behavior, not a fault.
- A steady red LED means it is charging. LED off while plugged in means wrong cable or wrong charger.
- Expect approximately 2-3 hours from empty to full
Common R36S Charging Problems & Fixes
"No LED light when plugged in"
This is the most common complaint, and it almost always has a straightforward cause:
- Confirm you are using a USB-A to USB-C cable, not USB-C to USB-C
- If the battery is completely drained, the device enters a trickle charge mode — wait 30-60 minutes before concluding anything is wrong
- Try a different USB-A port or charger brick
- Clean the USB-C port gently with a toothpick — lint accumulation is a common culprit on devices carried in pockets or bags
If the battery is completely dead, the red LED won't appear immediately. Leave it plugged in for an hour before concluding it's broken.
"Charges sometimes but not reliably"
Intermittent charging almost always points to a cable or port issue rather than a battery problem:
- The cable is the most common culprit — try a different USB-A to USB-C cable before anything else
- The USB-C port may be loose from repeated use — try gently wiggling the cable while inserted to see if charging starts
- Port debris can cause intermittent contact — use compressed air or a soft brush to clear the port
"Red LED blinks during boot"
A blinking red LED at boot is not a charging error. This is the low battery indicator, triggered when battery charge falls below roughly 15%. Simply charge the device and the blinking will stop.
Note for ArkOS users: a firmware update released in July 2025 introduced a bug where the red blink behavior stopped working on some builds. If you are on a recent ArkOS version and the blink is absent even on a low battery, this is a known firmware issue, not a hardware fault.
"Battery drains faster than expected"
The R36S is advertised at 4-6 hours battery life, but real-world results vary significantly depending on what you are emulating:
- PS1, N64, and Dreamcast emulation drain the battery considerably faster than NES or GBA
- Screen brightness has a large impact — lower it with SELECT + D-pad Left
- Use power-saving RetroArch cores where available
- See our full battery life guide for a complete set of tips
Fast Charging: Is It Possible?
No. The R36S does not support any fast charging protocol — not USB Power Delivery, not Qualcomm Quick Charge, not any proprietary variant. The maximum safe input is 5V/2A (10W).
Attempting to force higher voltages through incompatible chargers risks damaging the charging circuit. Standard charge time from 0-100% is approximately 2-3 hours regardless of charger, since the device itself controls the charge rate.
You don't need a special charger — any old USB-A phone charger works perfectly.
Charging While Playing
Yes, you can charge the R36S while playing. The device handles simultaneous charging and operation without any special configuration required.
A few practical notes:
- With a 5V/2A charger, the battery will slowly charge even during active play
- With only a 5V/1A charger, the charge rate may not keep up with the discharge rate during intensive emulation — the battery will drain slowly even while plugged in
- The device does not get dangerously hot during normal charging combined with gameplay; mild warmth is expected and safe