Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ordan77

macrumors member
Original poster
Jun 11, 2009
45
0
Well, I took the plunge last night and updated my 2G Touch to 3.0. So far, quite happy ... but ...

I successfully paired my i.Tech Blueband A2DP headset with the Touch, and all seemed fine, however I'm noticing a lot of stutters and jumps in music through the headset.

Has anyone else seen anything similar with a 2G Touch paired with an A2DP headset?
 
Yes, although it's not the same with everything I've paired. Turning OFF WiFi helps. Make sure you've got the Nike thing OFF.

Apple still has work to do with Bluetooth. I own several devices with bluetooth, and so far this is the worst implementation I've encountered.
 
Can't pair

I have the same i.tech headset and an upgraded iPhone 3G, but I can't even pair it!
I'm pretty sure it worked as a headset before...
I hold the button to get the red/blue flashing light, it is correctly identified by the iphone as "i.Tech BlueBAND", but when I enter the pin (0000) it just says "Could not pair with "i.Tech BlueBAND""....

Did you do anything differently to pair your headset? If I can get it working I'll let you know what the quality is like :p

Update: It seems contrary to what the manual says, you have to use 8888 as the pin.

Update2: I've been using it for a good few hours now and I too get drop outs. The headphone go quiet for a few seconds and then you hear the music again. I find this only seems to happen when I'm walking about with my iPhone in my pocket, if I'm sitting down at a desk I never have any problems. I've had the wireless etc. on the whole time.
I don't think we can blame the iPhone however. I used to get exactly the same problem, but about 4 times worse when I used the same headset with my (now very) old HTC Wizard. I think the blueBAND must have a feeble antenna or other such fundamental problem. I'm willing to bet if you had your iPhone, or iPod Touch in one of those sports holders that go around the top of your arm you wouldn't have any problem.
 
Bluetooth at it's best will only have about 30ft of range. Most earpieces don't have a good enough antenna, as they were only expected to have to reach from your belt to your ear. Throw in walls, bodies, Microwave ovens, and all the other radio interference you'll be shocked to find in your house and you'll wonder how it works at all.
 
That's my point about this headset, it seems to struggle just from trouser pocket to head, and if you've not just crossed the event horizon of a black hole then that's probably a lot less than 30ft!
 
Thanks for the replies - at least it's not just me.

It does seem to be slightly better with WiFi off, but not a lot - less dropouts, but the dropouts that did happen were longer.

Distance isn't a factor, as the iPod was in my shirt pocket.

In my latest test, RFI isn't a real factor either - tested on a train, very few passengers, travelling through the wilds of Scotland, nothing of note in the relevant EM bands.

I've used the same headset paired with my N95 for ages, with the phone on my belt, no real issues. Based on experiment, I'd be inclined to agree with 4DThinker - Apple's BT stack needs work.
 
I've noticed this as well with my 3G. On my drive to work this morning, the phone would not connect to my car stereo so I restarted my phone. After that it connected via Bluetooth and did not stutter for the rest of my drive.

Maybe it's a memory issue? Try restarting your phone and see if that helps.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.