NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Android App takes much time to load connected devices
Hi All, I have Orbi RBK754 system, I have experienced this since always but I want to know if there's anyway to fix this. I have noticed that devices takes a lot to refresh in android app their c...
There is no documentation about the internals of the Orbi firmware. My sense is that the actual functioning of the network is separate from the process of formatting information to display on the web or 'app' interface. Constantly rebuilding the web page when most (perhaps all) of the data is not changing might put a huge load on the processor. (especially if the system has a large number of active devices)
Another consideration is that Netgear appears to put together a new software engineering team when they introduce new products and much of the firmware and web code is created almost from scratch. I have compared the web code from the original Orbi WiFi5 routers (802.11ac) against the web code for the WiFi6 (802.11ax) and was astounded at how much was totally different. (do not have access to the WiFi7 products)
My experience does not match yours. For me, both the web and smartphone app take longer than I had expected to update the status of connected devices. For certain, the smartphone app gets information from the router, so it cannot possibly update status faster than the router. My impression is that there is some sort of timer in the router firmware that updates an internal table at regular intervals.
So my answer to:
javiersalasf wrote:
Is there a way to fix that in the android app?
Is, "no". It is what it is and we just have to live with it. Sorry.
Thanks for your reply!
I thought that it could be possibly to a hardware constraint that is not updating attached devices in a timely manner. I hope they can give at least in a future release a fix to that, I have seen other mesh system that updates instantly as soon as devices are connected/disconnected. That would make perfect Orbi if you could monitor it in real time without that delay.
Thanks for your response
There is no documentation about the internals of the Orbi firmware. My sense is that the actual functioning of the network is separate from the process of formatting information to display on the web or 'app' interface. Constantly rebuilding the web page when most (perhaps all) of the data is not changing might put a huge load on the processor. (especially if the system has a large number of active devices)
Another consideration is that Netgear appears to put together a new software engineering team when they introduce new products and much of the firmware and web code is created almost from scratch. I have compared the web code from the original Orbi WiFi5 routers (802.11ac) against the web code for the WiFi6 (802.11ax) and was astounded at how much was totally different. (do not have access to the WiFi7 products)