NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Android 8 Crashes Orbi
I've been tracking down an issue where my Orbi just suddenly drops wifi and reboots. I've isolated it to be associated with an Android device running 8.0 or higher. And I've proven it turning off w...
vreynolds wrote:
Let me clarify, I don't have any proof but I think it has something to do with the recent Android patch.
That isnt it either. My Samsung A7 are not Oreo and are not November / December 2017 Patch level. They are August 2017 patch level.
I've been having the same constant router crash -> reboot issues for the last 6 weeks or so. We have a Google Pixel 2 phone as well. When the phone is connected to Wi-Fi, the issues occur.
I went away over the holidays and when I returned home yesterday, my router crashed almost immediately. I then noticed that Google had released the January Security Patches for Pixel phones, so I downloaded the OTA file from Google and manually installed it. We are now about 16 hours later and the router has not had a crash or reboot since. My Logs go all the way back to yesterday afternoon. Fingers are crossed that the issue is fixed. If so, then the blame lies with Google. Even if you are not running a Google phone, if you have a Samsung you are running Google's software. The issue could lie somewhere in the security patches that they have released to manufactures or some of the underlying software that they silently update on all modern Android phones via Google Play Services. Time will tell, but if I don't report back, then the news is good.
I think I managed to stop the bleeding locally by taking the OnHub and putting it on an isolated VLAN on my switch - now that Orbi can't see _any_ traffic from the phone whatsoever, things stopped crashing.
That being said, I disagree with an earlier post that if the January security update from Google makes the crashes stop that "it means it was a Google problem". No...I'm afraid I have to agree with an earlier poster who said that a router should never crash in the presence of errant traffic, ever, period. I don't doubt there were bugs on *both* sides, but it's not the bug in OrbiOS that's aggravating...it's the appalling lack of attention to it by the vendor.
I having some issues too, but I might not be on Oreo, but it something that happened recently.
If y'all bothered to look back a page or two in this thread you will see that it's not Oreo or the January patch.
It happens to people with old unpatched phones that don't run Oreo. Like my Samsung A7, 2017 that runs Nougat and the patch Level is August.
While I respect your opinion sir or ma'am, I referring to the vast majority of the people on this thread, that is linking something with Android recently, including myself. Like multiple people have said, this started occurring in the last few weeks and stops when the phones wifi is turned off. So something, as the article state, a well known source of android news, it being cause be recent updates.
Prior to this, my Orbi has not dropped connection in months. So, forgive me if I, and this thread, disagree with you.
Thread doesn't disagree with me at all. I do not have a single Oreo device in the house and can make Orbi crash with Nougat devices as can be seen a page or two back and there are others who are in the same situation. They have Android devices that are pre-Oreo and waking them up from sleep crashes Orbi. Have you bothered reading the thread ?
- It sounds like both of you are saying the same thing. In a nutshell, it's not limited to Oreo or a recent patch, but rather something that happened in the last month or so. Is that right? My problem started about a month maybe a month-and-a-half ago. I have no Oreo devices, but a bunch of Android 7.0 devices. Anyway the most frustrating thing is netgear's lack of response. I just got my r7000 back from a friend, so the Orbis are going to be shut off soon. Plus I'm also advising everyone not to buy the Orbi's until they read these community threads.
- Going strong at 24 hours with no reboormts since applying the January patch to my Pixel 2. It may have nothing to do with Oreo. It may simply fix an underlying issue that didn't pop up until a recent under the hood update from Google, such as an update to Google Play Services. It could also be caused by an app that we all have in common. Either way, I am starting to get warm fuzzies about my Orbi again.
Agreed - as the battle rages on, the January patch does indeed seem to have addressed whatever the cause of the crash was.
- So with Android, if we don't have a pixel, or Nexus, I assume we are at the mercy of the carriers to roll out the security patch?
vreynolds wrote:
So with Android, if we don't have a pixel, or Nexus, I assume we are at the mercy of the carriers to roll out the security patch?That's always been the rub with Android - a zillion different vendors with a zillion different versions all choosing to update (or not) however they see fit. The joy of open source software! :)
Keep us updated on the status of the Janurary patches if you can. I still have december so not going to put to test yet.
Cheers!
It was too good to be true.
My Pixel 2 XL on the January patch just rebooted Orbi. *sigh*
Out of our curiosity, I set up my Orbi in AP mode with my Eero serving as the router to see if the January patch had fixed the issue. Nope. Still reboots after waking my phone from a long sleep.
I'm out. Eero is going to be my final solution. I wouldn't even feel good about reselling or gifting my 3 Orbis.
- Has anyone else tried wired backhaul (single satellite direct (no switch))? As I posted early on in this thread, I don't have the reboots when my Satellite is connected to do wired backhaul.
Pixel 2 on December Updates
Orbi on latest firmware 2.1.1.16 - Here's something new for me: no reboots on the main router for over 3 days but the single satellite is rebooting daily, sometimes more that once. I don't know what's changed... Other than I added more devices such as an Nvidia Shield. The satellite reboots are less problematic but still...
I tried wiring the router and the satellite directly and had a reboot occur in a short enough period of time that it didn't seem to help my situation
Okay...Add me to the list.
First thing did this morning (I live in Europe) was to pick up my phone (OnePlus 5T with Oxygen OS 4.7.6 Android 7.1.1 and December patching) and immediately the RBR05 with latest beta 2.1.2.10 rebooted. Already had this 3 or 4 times with 2.1.1.16 but wasn't sure about the trigger until I read this topic.
I'm using Orbi system in AP mode, fixed Wifi channels (1 & 36), Daisychain ON but other wireless options disactivated (Beamforming, MU-MIMO, Fast roaming).
Issue does not seem related to Android O but maybe with latest patched Android version.
I hope this will help troubleshooting.
- I have the Netgear Nighthawk r7000. Is there anything I can do with it? Can I use it in bridge mode or AP mode and just turn off the satellite until Netgear gets their act together? Anyone know if it fixes the reboots? I could use the r7000 by itself, but it just didn't have the range for all of my devices.
vreynolds wrote:
I have the Netgear Nighthawk r7000. Is there anything I can do with it? Can I use it in bridge mode or AP mode and just turn off the satellite until Netgear gets their act together? Anyone know if it fixes the reboots? I could use the r7000 by itself, but it just didn't have the range for all of my devices.Maybe? However, people in the Pixel forum are reporting reboot issues with R7000s as well (along with lots of other routers from other manufacturers). Problem isn't exclusive or Orbi. Can't hurt to try, though.
- I switched back to my R7000 and it has been fine. It is behind 2 or 3 firmware updates. My Orbi would reboot 20+ times a day. I have had none with a week back on the R7000. I returned my Orbi. I would flash some older firmware on the R7000 if it is rebooting and see if it goes away.