NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Feedback for R7000 New firmware 1.0.9.18
Hi All,
Please post here for any update/issue related to the latest firmware 1.0.9.18.
You should review this and maybe revert back to this recommended version of FW:
Alfikwrote:I've looked here again after a while and I can't belive the problem is still not solved....
Since I've flashed Tomato a few weeks ago I've forgotten that I have a router- it's working perfectly getting dust because i do not touch it at all :-)...
Parental control works perfectly, 0 drops, strong signal - save your time and do a similar thing!
So, I have been following this thread for a long time now. My take is that TerryPH has it right that it is a memory issue due to volume and introduced at some point after v1.07. So, the latest beta hotfix release notes from netgear seem to indicate that they have now agreed that this is the issue (instead of blaming it on Android) and tried to fix it. But, I am stuck in the following state:
1. Many of you seem to have updated to the latest beta and still experience the issue. Is this true?
2. I don’t like betas and am scared to move off of 1.07 for fear the issue will come back with the latest release
3. I am unclear what risks and security holes exist in 1.07 and am worried about being on this old version too long
4. I have seen nothing from netgear that officially admits to the problem, explains the root cause, and communicates to all of us when an official fully 100% tested release will be available
Do any of you have any answers here? Netgear, are you still out there? Do you still care? Will you be releasing an official version that solves the issue and communicate with transparency to all of us?
1. Many of you seem to have updated to the latest beta and still experience the issue. Is this true?
2. I don’t like betas and am scared to move off of 1.07 for fear the issue will come back with the latest release
3. I am unclear what risks and security holes exist in 1.07 and am worried about being on this old version too long
4. I have seen nothing from netgear that officially admits to the problem, explains the root cause, and communicates to all of us when an official fully 100% tested release will be available
Do any of you have any answers here? Netgear, are you still out there? Do you still care? Will you be releasing an official version that solves the issue and communicate with transparency to all of us?
Hi Redtarheelhawk ,
1. Many of you seem to have updated to the latest beta and still experience the issue. Is this true? -Many users have confirmed that the issue has been fix with the latest hotfix. You have to check as well if you have google home devices or chromecast or any other device the uses casts feature that contributes to the issue. There is a known issue with those devices.
2. I don’t like betas and am scared to move off of 1.07 for fear the issue will come back with the latest release. - This is considered as official firmware since it is released in official website.
3. I am unclear what risks and security holes exist in 1.07 and am worried about being on this old version too long. - Then you might have to consider upgrading to the latest firmware. Please take note that not all users have the same environment and network setup.
4. I have seen nothing from netgear that officially admits to the problem, explains the root cause, and communicates to all of us when an official fully 100% tested release will be available. - It has been confirmed by NETGEAR that it is an issue that is why the firmware was released.
1. Many of you seem to have updated to the latest beta and still experience the issue. Is this true? -Many users have confirmed that the issue has been fix with the latest hotfix. You have to check as well if you have google home devices or chromecast or any other device the uses casts feature that contributes to the issue. There is a known issue with those devices.
The hotfix is by no means a complete solution as evidenced by those with continuing problems. I used screen cast on an earlier firmware without problems. It's Netgear that has the problem, trying to pass it to others is pretty poor.
2. I don’t like betas and am scared to move off of 1.07 for fear the issue will come back with the latest release. - This is considered as official firmware since it is released in official website.
If it is considered official firmware why does the broken 1.0.9.18 remain as the first download available?
3. I am unclear what risks and security holes exist in 1.07 and am worried about being on this old version too long. - Then you might have to consider upgrading to the latest firmware. Please take note that not all users have the same environment and network setup.
Or you may consider moving to a third party frimware that does not have the issues provided by Netgear
.
4. I have seen nothing from netgear that officially admits to the problem, explains the root cause, and communicates to all of us when an official fully 100% tested release will be available. - It has been confirmed by NETGEAR that it is an issue that is why the firmware was released.
Has it been admitted by Netgear that they have not completely fixed the problem, because they can't find what they did to break it? I've seen no explanatory communication from them, has anyone? An apology would be a start.
- I have in fact seen the opposite from netgear. Rather than admit fault they blamed Google. They released firmware that caused the problem for me. While I have Google products I had no problems until I upgraded and then I could not make it more than a few hours.
I downgraded after trying the betas and still having the problem. Granted I did have an issue a few times after downgrading (twice in two weeks) it was not every few hours like I was seeing. I believe the continued issues were based on the Google products because after updates were released I have been stable again on old firmware. Since I am not paid to be a beta tester I bought a new router, not netgear sadly, but it seems this has spread to other devices of theirs as well so I am now out.
I also have issues that the problematic firmware continues to be posted with no warning or updates and this is not an acceptable practice to me as I work in the wireless industry and if we did this it would be in the news. Communication from netgear is poor. I have seen a few posts from them that you need to hunt for but nothing on their support pages press releases and they continue to act as if this should be business as usual.
