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!
brdoddsjr wrote:Folks, my final update. 6 days on the .20 Hot Fix and stable with good speeds. New lease last night and the router resovled correctly. Not errors in the logs.
Good luck all.
My attempt with .20 failed this morning. I've seen one other report of failure that I can recall, and yours is the only success. I would beware if I were you - this firmware / problem must be fragile. If yours doesn't break in the coming days, perhaps some change to your network or device behavior will likely break it in the future. Until Netgear acknowledges the issue, communicates its cause, and points to a fix, no one should assume it's fixed.
Seconded, and I've been wondering about this myself. There's a small subset of users claiming that .20 works well for them, though in my own experience I upgraded to every stop of 1.0.9.x (From memory, .6, .12, .14 & .18). All of them behaved fine, maybe with a device reboot here and there because a minimal issue (ie, a device that strangely can't get to the internet).
I ended up running 1.0.9.18 for some time as well, maybe a week or two, and it ran decently; up until the moment that it lost it's damn mind. Once the problem triggered, getting ANYTHING to connect reliably to 2.4Ghz was impossible, even after a reboot.
So I'm curious as to how many people running on 1.0.9.20 simply haven't had the issue fully trigger yet...
- I am running since christmas night, but had to unplug everything last night to move my office around. I am no longer a good judge of how long it lasts. Im sure unplugging the router basically reset the clock on .20.
I just wanted to give you my view on your question.
I'm running .20 now as my router crapped out after the .14 upgrade. My 2.4ghz doesn't fail to connect, but it fails to get internet sometimes and , whilst that is resolved on .20, the speeds from certain Android-based devices on 2,.4ghz are atrocious....just really bad.
I've been running .20 since release and touch wood, ignoring 2.4ghz, the router is largely stable. However as I started typing this, (oh the irony) the router rebooted. Nothing in logs, no real reason, it just rebooted.
Other than that though it's honestly not too bad, but I'd prefr a proper fix to get more than 20Mbit on Android devices.
I've always had issues with NEtGear devices, however I have a marketing contact there and they are suggesting this is rather widespread , including other models.
- As version 1.0.9.20 didn't solved 2.4GHz drop, I decide to follow this procedure:
Reset R7000
Install 1.0.0.96 (original firmware)
Reset
Install V1.0.9.6_1.2.19
Reset
Setup my router
I will report about 2.4GHz stability.
I hope that Netgear will provide new working firmware ASAP. Otherwise I will return back my router and ask for pay back.
