Posted this on a Moto owners forum earlier, but can't hurt to ask here if anyone's had similar issues.
I have just received a Moto X pure edition (XT1575) & have been spending some time getting acquainted with it. I have also updated to Android 6.0 & so far, liking the device immensely.
But I have just discovered a bizarre issue when it is connected to my home wifi network.
It causes my browser (safari) to hang on my macbook. As soon as I turn the Moto's wifi off, the browser leaps back into action.
I tried with chrome & firefox & those both seem unaffected. It's just safari that has a hissy fit.
Readers will probably point me straight at safari being the culprit (& I will pose the same question to them), but I am curious as to why the wifi being activated on the Moto is the trigger for this effect. I have a 1st gen Moto X too & never had any conflict issues with that.
Tried reboots, IPv6 set to local only, the works, but no dice.
Anyone got any ideas what's causing this & what I can try to resolve it? Safari is v 9.0.2 & OSX is 10.11.2
I checked that & all devices are working on the same frequency (2.4GHz) & same wifi channel . I'm trying to see if there's anyway I can tweak my DHCP reservations in my router so that they can't both be assigned the same IP addy, but seems that options not available in my router. But I am becoming more convinced it's a safari setting, as nothing else is affected.
The thing is I can't find any settings in Safari on my MacBook. Have you tried a different channel?
No I didn't yet. Just tried it now & didn't make a difference. It has to be the browser, but what is super weird is that none of my other devices do that to it
El Capitan was the upgrade from Yosemite & the latest Safari came bundled with it, so it's all the latest versions. Yosemite had some minor wi fi bugs in it that El Capitan sorted out..... I hope.....
El Capitan was the upgrade from Yosemite & the latest Safari came bundled with it, so it's all the latest versions. Yosemite had some minor wi fi bugs in it that El Capitan sorted out..... I hope.....
Might have made a breakthrough limur suggested I change the wifi standard on the router from 11n to 11g & that seems to have done the trick I also have Moto's wifi engineers looking into this, as it shouldn't be the case a phone can cause all this hassle