I don't have this bug on my Aura HD. Never did. I've been told that for people who did have it, assigning a DHCP address fixed it. BTW, the people in the beta (not a very big group, but they had a large internal group checking too) that did have this problem in the last build found that it was resolved in 3.2.0. YMMV. Did you do a power cycle after the update? You might want to do that and see if it helps.
|