This particular issue seems to be with verizon 3.0...We are looking into the issue and have sent it to the Devs to have them investigate and correct the issue. Unfortunately we don't have an eta at this time. I'll update the thread here when the issue is found and then when resolved.
↧