Woooooooah. That is totally unfair NS.
Think about how many ECI modems there are out there and how many HomeHub5A users. This affects a lot of people, and if it had gone live on the ECI cabs it would have been even more disastrous.
You think its good because you gained about 3Mbps, However, if you lost >10Mbps of sync speed and suddenly found your latency at anything up to 50ms then Im sure you would be joining in with the moaners too. The only reason you weren't affected was you bought a HG612 and unlocked it.
BT had to halt it because even Openreach engineers diagnostic tools such as the EXFO's and Infineon JDSU's wouldnt work either.
i don't understand why the short line ECI users are so anti g.inp
This is why... and for those on ECI cabs there would be no solution and a swap of routers wouldn't fix it. So anyone who previously had a rock steady 80/20 connection with 10ms of latency would end up with 60Mbps speed and a high level of interleaving and absolutely no way of getting rid of it.
That is a vast deterioration of their line and makes 1500 E/S per day a drop in the ocean by comparison. Would you be happy getting 60Mbps on an 80Mbps line and 45ms pings? Now perhaps you understand why ECI users are unhappy?
the needs of the few outweigh the needs of the many.
If it had gone live to the ECI cabs, then if you include the Huawei cab users with ECI equipment then that would be
well over half of the FTTC users who find themselves in a
FAR worse position than getting a few E/Secs per day
With all due respect your'e upset because you've (temporarily) lost a couple of Mbps that g.inp gave you. Now just imagine how you would feel if you lost >10Mbps and got stupid levels of Interleaving through no fault of your own. Think also how many people would be affected and its not a minority by a long shot.
----
PS
Ive split this off because its not really that the EE2 isnt g.inp compatible.