Ever since I updated from 10.5.6 to 10.5.7, I'm now loosing my Apple wireless keyboard and mighty mouse bluetooth connection with my MacBook Pro.
At least once a day, my keyboard and mouse both loose connection. There is no lag going on before it happens, it just happens suddenly.
I can get connection back to both my mouse and keyboard by simply using the trackpad to turn bluetooth off then on again from the menu bar.
Up until last week this was happening on my 17"/2.6GHz/4GB previous gen MacBook Pro. I have now sold that and as I'm sitting here setting up my new 17" uMBP, I just lost keyboard and mouse connection. Grrr. Obviously it's not my machine and obviously it's not my keyboard or mouse as they both loose connection at the same time - it's 10.5.7
I'm using airport wireless 'n' 5GHz only. I also have bluetooth enabled on my iPhone, but always have - and never had issues when running 10.5.6 (or earlier).
I have searched here but haven't found anyone else mention this exact problem. Strange. I would have thought that it would be common now that I've experienced it with two MacBook Pro's running 10.5.7
Can anyone help me with this? Can I go back to 10.5.6 somehow without having to rebuild?
At least once a day, my keyboard and mouse both loose connection. There is no lag going on before it happens, it just happens suddenly.
I can get connection back to both my mouse and keyboard by simply using the trackpad to turn bluetooth off then on again from the menu bar.
Up until last week this was happening on my 17"/2.6GHz/4GB previous gen MacBook Pro. I have now sold that and as I'm sitting here setting up my new 17" uMBP, I just lost keyboard and mouse connection. Grrr. Obviously it's not my machine and obviously it's not my keyboard or mouse as they both loose connection at the same time - it's 10.5.7
I'm using airport wireless 'n' 5GHz only. I also have bluetooth enabled on my iPhone, but always have - and never had issues when running 10.5.6 (or earlier).
I have searched here but haven't found anyone else mention this exact problem. Strange. I would have thought that it would be common now that I've experienced it with two MacBook Pro's running 10.5.7
Can anyone help me with this? Can I go back to 10.5.6 somehow without having to rebuild?