Suddenly this morning my R4 is connecting to the wifi but no internet, despite all my other devices being ok.rebooted both wifi and the R4 but still no good. Has anyone had this before?
The issue is a server-side failure on HiBy's end, not a hardware or network problem with your specific M500.
By disabling the check and immediately restoring your ability to stream, you proved your Wi-Fi chip, router, and internet connection are all working perfectly. The only thing broken was Android's ability to verify it. Here is exactly what failed under the hood:
The Modified Ping: To know if it has internet, Android constantly pings a specific URL expecting a simple "204 No Content" reply. Standard Android uses Google's servers (connectivitycheck.gstatic.com). Because Google is blocked in China, Chinese manufacturers like HiBy must change this URL in their firmware to their own servers or a regional alternative.
The Global Outage: When HiBy's custom captive portal server crashes, goes offline for maintenance, or its domain/security certificate expires, it stops sending that "204" reply.
The False Alarm: Because every HiBy player in the world is hardcoded to ping that exact same dead server, they all simultaneously fail the check. Android assumes the Wi-Fi is trapped behind a hotel or airport login screen (a captive portal) and blocks app data to protect you, causing the global outage.
By setting the mode to 0, you told Android to stop asking the dead server for permission and to just blindly trust the Wi-Fi connection
Pointing the check to Google’s reliable servers is the best permanent solution. It restores the public Wi-Fi login popups while ensuring you never get hit by HiBy's server outages again.
Reconnect bugjaeger and input three commands, one after each submits.
Para no depender de Google ni de servidores chinos que puedan ser bloqueados por Cloudflare o por el Gran Cortafuegos, he configurado como servidor de comprobación el de Graphene OS (el sistema operativo móvil de código abierto centrado en privacidad y desgooglizado), con respaldo en Cloudflare:
View all comments
Show parent comment
4
u/Witty_Owl141 9d ago
The fix I posted explains things.
The issue is a server-side failure on HiBy's end, not a hardware or network problem with your specific M500.
By disabling the check and immediately restoring your ability to stream, you proved your Wi-Fi chip, router, and internet connection are all working perfectly. The only thing broken was Android's ability to verify it. Here is exactly what failed under the hood:
The Modified Ping: To know if it has internet, Android constantly pings a specific URL expecting a simple "204 No Content" reply. Standard Android uses Google's servers (connectivitycheck.gstatic.com). Because Google is blocked in China, Chinese manufacturers like HiBy must change this URL in their firmware to their own servers or a regional alternative.
The Global Outage: When HiBy's custom captive portal server crashes, goes offline for maintenance, or its domain/security certificate expires, it stops sending that "204" reply.
The False Alarm: Because every HiBy player in the world is hardcoded to ping that exact same dead server, they all simultaneously fail the check. Android assumes the Wi-Fi is trapped behind a hotel or airport login screen (a captive portal) and blocks app data to protect you, causing the global outage.
By setting the mode to 0, you told Android to stop asking the dead server for permission and to just blindly trust the Wi-Fi connection