I know it was a big loss when Dave left and I am continuing to push to get additional representation back on the forums because you are right, your feedback and input is invaluable. That said there are at times challenges trying to align on priorities and I do apologize that we have not done a better job with this.
Although I cannot provide complete visibility to the D3.1 challenges or roadmap I can say, as with the current D3.0 firmware there are issues that need to be worked out before pushing out code that supports D3.1, not just from the device perspective but also on the network side (we want to make sure that we won't have to roll that code back...). Code is currently under test and as soon as we have confirmed its performance we will be pushing it out... i know this is not what you want to hear... but it's still going to take a bit more time.
On the other side.. we are continuing to work on the D3.0 firmware which has not gone very well. We had successfully rolled out the 35T2 firmware only to encounter a network impacting issue that forced us to roll it back.
I am working with our vendor to fix these issues so we can move forward with getting out the latest updates as soon as possible... still a few weeks out.
And the above is just on the CODA... we are also working on new code for the AC devices and the CGN3ROG units.
Totally agree @JohnBeaudin ....Few months ago I had speeds of over 1GB and close to 50Mb down without Netflix streaming issues. Now rolled back to 34T6 two months ago.....pings are terrible and cannot even get 400MB with plenty Netflix streaming issues. @RogersSergio has promised to fix these issues - which we have - but not delivered. As a PM he's simply a broker of information between us, the developers and Rogers management. He's not a Network Architect like @RogersDave , who could give us Technical details and insights we loved. This is why most of us liked this Forum we signed-up for 2 plus years ago, we had patience and tolerated Rogers. Now it's regressing back to the early days....and just a matter of time for all of us to look at options. Rogers enough lip service....It's time to deliver.
@RogersSergio thanks for the update on all this - I am not a beta tester, but have followed the process closely from the beginning.
I can relate to your situation as a Project Manager - this is the first time I picked up on what your role is. I have been project manager in many large projects over the year, even trained way back when under PMP training. I often felt a bit like a powerless monkey in the middle of management, the consumer (stakeholders as they like to say), and the development team and engineers and all other professionals involved.
Much of what is going on you can't communicate to the "users", in this case, Rogers customers, some who have kindly agreed to be involved in the process of beta testing, and it appears they are starting to grow in frustration and any desire to be a part of the process.
They just want to see a stable functioning basic system - go ahead and develop and test, but it is not unrealistic that customers should be able to see stable Internet performance standards in place, and of course as a beta tester, one would expect to get hit by surprises now and then, but just in my opinion, it is time to step back, stabalize what is going out to the general user, and keep the beta users up to date, and maybe that is best in a private forum.
As a final question, what is the current firmware on the Coda white box - regular user and beta user.
Again, thanks for the clarifications, and I don't envy your situation at this moment, but maybe if you could emphasize that people who are paying good money for services are getting frustrated as you iron out the bugs, and maybe dedicate some time to getting a stable delivery to all regular users of download and upload speeds, wifi performance - do we have ability for USB data services or not (turn it off and announce if we don't), and since they now have acknowledged that a gateway alone, no matter what level it is can often lead to performance in output, and maybe when a customer contacts saying that they are having issues with WIFI, a tech comes and tests signals of WIFI, adjusts placement of the modem if that solves the problem, or recommends the wall to wall solution.
And possibly narrow down the beta testing and develop a communication line for that group. As a beta tester, having been one before, not with Rogers, I expect that things may not go as predicted, but you can always opt out, but they need to be able to opt out to a stable well functioning solution while Rogers figures out the future.
Just my opinion.
I don't know how hard you or Rogers are working on firmware updates for your Internet modems, but from a customer's perspective it's not hard enough.
According to Page 1 of this post, Your production firmware for the CODA is 8 months old and for the CGN3X series, 9 months old.
That makes me wonder whether all the beta firmware since then are unworkable or not required or whether no effort has been made to incorporate them into production. Or has the page simply not been updated?
According to Page 1, 33T3 is the production version for the CODA. Yet a hardware reset of the CODA leaves you with 34T6 (beta), not 33T3 (production). I though a hardware reset of the CODA puts you back to the production version. Have you just not updated the page? And if 34T6 is production, why hasn't had the bridge mode disappearance act (can't access it from 192.168.100.1 after a few days without rebooting) been addressed in 3 months?
What is going on? It appears that Rogers won't dedicate the resources required to address issues that are so critical to the successful operation of their network?
Rogers is a large corporation not a small startup and their President has said he is very committed to customer service.
so ya, when the 2.4G drops, the SSID keeps broadcasting, but I cannot get any internet thru it, and the DHCP assigns an IP completely out of range to my devices.
I can still use my wired devices fine, and I can connect to the 5Ghz and access the CODA login and refresh the wireless channel to get back the 2.4.... but this is very annoying as the 5 G doesnt reach my garage so I need to constantly come into my office to reset the wifi almost twice a day now.....
Im just completely disheartened with these problems, I cant believe after 1.5years of testing and feedback, the development team cant come up with better firmware.
Id also like some kind of time line on the next update, as its been 3 months since we've had anything, as the May update was rolled back. even still its been almost a full 2 months since that update.
As manager of a business myself, if I had told one of my departments that there was serious issues with somthing, and it took them more than 1 month to fix it, never mind 2 or 3, and they were not giving me atleast WEEKLY, DETAILED reports as to why and whats been worked on, i'd be replacing those employees very quickly.
As others have mentioned, Rogers is not a small start up, and the CEO has said he is dedicated too customer service, so why are customers being left in the dark and not getting their issues fixed after now, 1.5years, all the while, we are paying for service we are not getting, and we are not being actively saught out by Rogers for a discount for our troubles and efforts to help, we have too call and demand constantly to just get $10 off....
I've been writting a long letter too the CRTC about Rogers and their sales and customer service practices, and I am interested if anyone else would like to be involved with this and help me add more details and direct customer experiences. If i recieve enough interest, I am willing to purchase a website to post the finished letter and allow the public to view and digitally sign if they also agree, like a petition. Im out of ideas for any other way to show Rogers we mean business.
Put the CODA in bridge mode and buy you won router dude.
@you can lead a horse to water but it’s not possible to have the horse drink that water if they chose not too .... I agree that getting your own router is the best choice BUT many here want to believe that Rogers and it’s Gateway suppliers will produce a quality integrated device. ... will NEVER happen. However, @Makaveli99, you are one lucky dude because you still have firmware 35T1 which firmware in BRIDGE mode was the best firmware ever produced by Hitron.