Adrian I am pretty sure that the code has been rolled out across all of the estate. I didn't answer because I didn't know the answer to the question but have £5 to you and Paul for your efforts! I've told paxman to re-grow his beard.
This bug affects a small minority of end users owing to the nature of it. It is not major or widespread, if it was I submit that we would have a hell of alot more people complaining. No that doesn't mean it's ok to have problems and we aren't happy about this either - but they do happen and despite rumours to the contrary we don't wake up in the morning with the sole goal of doing what we can to irritate Adrian Kennard! :) we do wake up in the morning to deliver the best service possible. The proper fix is more significant than you think, but that won't surprise anyone! It is actually a bug in the chipset not the actual code and these types of fixes require a lot of testing. The current expectation of a solution is in February but we have not road mapped the roll out of this as yet. As soon as it is clearer then I will post an update. Regards Neil. Sent from my iPhone > On 14 Jan 2014, at 10:18, "Adrian Kennard" <[email protected]> wrote: > >> On 14/01/14 10:10, Paul Mansfield wrote: >>> On 14 January 2014 09:59, Neil J. McRae <[email protected]> wrote: >>> Adrian >>> We are working on a fix and as usual you are entitled to your views - which >>> we all know and love! I'm sure you'd be the first to raise it if we >>> deployed a fix that causes other issues. >> >> you didn't actually answer this question: >> >>>> On 14 Jan 2014, at 09:40, "Adrian Kennard" <[email protected]> wrote: >>>> However, as you are here, Neil. Can you confirm - have BT plc at least >>>> stopped deploying this broken version of code to modems, or are you >>>> currently, knowingly, breaking modems by updating to this version, still? >> >> >> I think Neil has been reading the "Yes Minister Guide To Answering >> Difficult Questions" :-) > > I am inclined to agree. He evaded that question, to which I would love > to know the answer. Neil? > > I do hope, given your comments about how cautious BT are being, that BT > plc are not DELIBERATELY BREAKING SERVICE of existing customers right > now. That you can confirm you have stopped rolling out this KNOWN FAULTY > firmware? Please do confirm, Neil... > > Also, BT set themselves a target for fixing a fault of 40 clock hours - > I did not make that rule, and it is not an "opinion", it is part of BT's > service level guarantee. So I hope BT plc can now work to that > timescale, Neil. > > Or are you suggesting the brokenness is an "opinion" in some way? That > is a "fact" that we are able to reproduce and demonstrate and have done > so to BT and Huawei. > >
