At least according to this post:
I feel that Telus mishandle the 10.3.1 rollout and needlessly delayed it. The boilerplate response is that they test the OS beforehand, but that's all done from the source, and then BB opens its servers to carriers. If Telus tested, they wouldn't have rolled out the version of 10.3.1 that contained the flicker issue. Any hold up is solely the responsibility of the carrier at that point, not BB.
Telus, do the right thing with 10.3.2 and make up for the semi-botched 10.3.1 rollout, please.
Solved! Go to Solution.