I agree. You can’t tell us you fixed the issue and not release a fixed firmware for the next 8 months. This is also security-wise a very bad decision. I mean, seriously, come on, you can’t be serious on this.
We are dealing with this problem since December, 17 and have been ignored for a very long time and now we should wait for another 8 months?
I would have to replace a lot of hardware just because you do not want to release an update.
Please think about it, and also do not forget, 1+3+8 is officially supported and affected as well.
Just update the firmware now, there is no reason to delay this further. People are paying customers for almost 2 years now, without a proper working device.
If it’s an easy fix, then a fast firmware release would be no problem I guess. If it’s harder to fix - so be it - but at least tell us.
Nope, they are ignoring us again. Great customer service. I thought they are finally taking our problems serious, but apparently not… Sad … That’s almost ZTE level customer service.
Time for another entry on my “Do Not Buy” list. I am done with this.
After reading this, I spit out my drink. Are you kidding me? I’m in the US and bought this modem SPECIFICALLY to be able to leverage 2+66 and yet I run into this issue constantly. What in the world would drive you to tell us that you found the fix and then tell us you’re going to sit on it for 8 months? This has to be a joke…
I was gifted an EM7455 and thought “cool, it supports simultaneous use of GPS, Glonass, Galileo and Beidou” and would have been perfect for my project. But of course, GNNS is totally broken as well. Positioning tracking works fine to a certain degree but the output of used satellites on the NMEA interfaces is FREAKING broken. Documented AT commands aren’t implemented or printing wrong data.
Now as a last ressort there would be the SDK. But its amazing documentation is full of mistakes and copy and paste errors … Not to mention it requires the unstable GobiNet driver … Unplugging the modem = Kernel panic or “stuck” driver.
It’s been a month since my last message. I’m going to try following up on this thread monthly in the hope that someone from Sierra Wireless will change their mind about making us wait until June 2019 for this problem to be solved.
The only reason why I haven’t migrated to another vendor by now is because I don’t really need that amount of bandwidth. The way you are dealing with your customers is still a joke though.