NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi App
Hello- I have just started having a problem opening the Orbi App. I click on the app and it comes right back and says "Orbi has stopped" with two choices. The first is to close app and the sec...
rbyrdman wrote:
Hello-I have just started having a problem opening the Orbi App. I click on the app and it comes right back and says "Orbi has stopped" with two choices. The first is to close app and the second is send feedback.
Was this after the latest app update?
Which app? iOS or Android?
I ask because the same thing has started happening to me on a Samsung on Android 8. Similar symptoms.
No problem on a Huawei tablet on Android 9.
I have the same problem on the Nighthawk App.
Both started after the latest update to 2.10.6.1635.
Android app 2.10.6.1635 is working for me on
Android 11
Android 10
Android 8.1.0
Android 7.1.1
The RBR50 remains on firmware 2.7.2.104 (I have seen the notice occasionally about "New Firmware" and am waiting to see if Netgear forces it on me). I have never activated Armor or Parental Controls.
I have been running Version V2.7.3.22 firmware on my Orbi without any performance issues.
Regarding the mentioned app issue on Android, I have read multiple reviews of the Orbi app posted by users on Google Play who are having this identical issue: no problems at all with the app in the past (like me and the OP) and then over the course of just a few days a sudden app failure as it refuses to launch at all. This is most likely related to the latest update in some way.
Netgear has so far failed to address this issue even once on Google Play. They really should address it here on the user forums.
V2.7.3.22 is for the Orbi router. The problem is the v2.10.6.1635 for the app. The NETGEAR TEAM has reached out to me for more information and I gave it to them. Maybe they will come back with an answer or a fix. If the do I will pass it on.
Yes, the latest Version of the app (v2.10.6.1635) does appear to be the problem at least for some users. Thanks for the update. I hope Netgear finds a solution.