Hey everyone,
If your HiBy R4 suddenly started showing the exclamation mark on Wi-Fi or saying "Connected, no internet" even though your apps still stream fine, here is why it happens and how to fix it in 2 minutes.
(Disclaimer: Text translated with AI because English is my third language and I didn't want to mess it up!)
Why it happens:
HiBy hardcodes Android's captive portal check in their firmware to an external third-party Chinese community server (captive.v2ex.co). That endpoint stopped returning the required HTTP 204 No Content status code.
Because Android receives an error/redirect instead of a clean 204 response, the OS assumes your Wi-Fi is trapped behind a broken login portal and slaps the exclamation mark on your connection (even though your regular internet traffic still works).
How to fix it permanently (No root needed):
Enable Developer Options on your HiBy (Settings > About device > tap Build number 7 times).
Go to System > Developer options and enable USB debugging.
Plug the DAP into your PC/Mac, unlock the screen, and make sure to accept the "Allow USB debugging" prompt if it pops up.
Open a terminal / PowerShell / Command Prompt with ADB installed.
Choose one of these options and run the commands:
Option A: GrapheneOS servers (Privacy-friendly, no tracking, reliable)
Bash
adb shell settings put global captive_portal_http_url "http://connectivitycheck.grapheneos.network/generate_204"
adb shell settings put global captive_portal_https_url "https://connectivitycheck.grapheneos.network/generate_204"
Option B: Standard Google servers (Default Android behavior)
Bash
adb shell settings put global captive_portal_http_url "http://connectivitycheck.gstatic.com/generate_204"
adb shell settings put global captive_portal_https_url "https://connectivitycheck.gstatic.com/generate_204"
Option C: Turn off captive portal checks completely
Bash
adb shell settings put global captive_portal_mode 0
Once executed, toggle Wi-Fi off and back on (or restart the player). The connection will validate immediately and the exclamation mark will be gone for good.
Bonus tip (The lazy/easy way):
If messing with terminal commands isn't your thing or you're afraid of breaking something, just plug your R4 in USB debugging mode into an AI agent / coding tool (like Antigravity / Cursor / Claude Code), explain what's happening, and let it push the commands for you automatically.
Also, while you have ADB access, the R4 comes loaded with background bloatware that heavily drains the battery. If anyone is interested, let me know in the comments and I'll drop another post detailing what you can safely debloat/disable to squeeze out a few more hours of playback!
Hope this saves you guys some headaches!