(2016-08-01, 23:30)touser Wrote: Yup, same issue for me with the same solution. No idea wtf is causing it, just another awesome bug that came along with the amazing 3.2 update.
Good to hear I'm not the only one, bought this shield last weekend.
Hopefully they will fix this soon
