airport signal goes down when bluetooth is on/active

[loko__loko]

hi,

anybody has this experience?

when my pbk has 1 bar left on its signal (connected to aebs) -but whenever i connect my bluetooth to any phone, the signal just drop... as in 0, it cant find the aebs anymore.

then i have to turn OFF the bt so that my airport signal will go up again, can detect the aebs again.




help?

[loko__loko]

happened last night and earlier, now it's ok..

my phone is connected via bluetooth, and my signal is back (after the signal dropped)

now, signal is gone again..

[andrefournier]

your wifi and bluetooth are conflicting since both operate on the 2.4Ghz frequency . Try changing the channel on your airport (trial and error) to find the best channel that will not interfere with your BT

[loko__loko]

will experiment..

thank you.

[loko__loko]

using channel 3... so far its slow, but tolerable

[piedad]

I heard from the Attack of the Show that Apple designed the powerbook with two internal antennaes shared between the wifi and bluetooth. When wifi is on, it will check which of the two antennae is getting a better signal, then allocate it to itself and leave the other one for bluetooth to use when needed. I guess what happens in your case is that with bluetooth off, wifi uses both antennaes so signal is better...then when bluetooth turns on you loose the other antennae.

[loko__loko]

at home.. w/ apple airport extreme base station, i have to use channel 1

at office.. w/ apple base station snow, i have to use channel 3 or 6 (better)

will experiment at office some more.. as i have solved the problem at home.

[loko__loko]

i was able to use bluephonemenu again yesterday...
when i was connected via bluetooth, i noticed that my internet connection was dropped.. no data coming in.. my airport signal drops

i just remember this topic that i posted before.. this is the reason why i stopped using bluephonemenu and instead i use megacellx

anybody else notice this on their powerbook or ibook?

help

thanks

[loko__loko]

after major update to 10.4.7 this issue was resolved...