Database Develop

blueant x5i stereo headset mp3 playback problems

hello again everyone!!!
i just got a set of blueant x5i stereo bluetooth headphones yesterday... they look cool and feel cool... call quality is great...
but the mp3 sound through my tmobile wing is HORRIBLE!!! i tried the headphones on my co-worker's t-mobile dash and they sound awesome... i can't figure out why they sound so muddy and crackly on my phone... is there a setting somewhere that i am missing??? perhaps a firmware upgrade for my phone that would solve this issue???
any help or insight would be greatly appreciated...
thanks in advance,
bennie

How does playback sound through the included (if any headset) or through the loud speaker? If it sounds good (normal) through those then its most likely a blue tooth problem. When you sync it up are you around anything that could possibly interfere with it during the sync process? There have been a few times when I am making a call (rare) but it wont get a good connection and everything will sound like I am under water or worse. (more with my old phone having a crappy radio)
If you have sync'd the two a fair ammount of times and its always the same sounding quality might look on the T-Moble Wings forum (this is the HTC s730) and see if other users have had the same problem. I wouldnt see it having a bad HTC driver, but it might not be very compatable with that headset?

its hard to judge sound the the loud speaker... it sounds bad no matter what...
when hard wired through the headphones that came with the unit, the mp3 playback is fine... its not crackly like this headset is... i tried resyncing a few times as far away from everything as i could so there would be no interference... i never sync my music files though bluetooth so i know that the files aren't getting corrupted... they are going through usb...
i think it has something to do with the phone...

Double check the compatability on the headset, if it plays fine through the USB headphones, and the headset sounds perfectly fine on another phone...
What version is the heatset? blue tooth 2 or whatever the newer version is? I know the phone supports it but something else might have changed? Just something to look into.
Aside from a firmware flash or some software bug I cant think of anything else If the compatability show's up that it should work might try calling HTC's support line?

i contacted blueant before purchase and they assured me the headset is compatible... also tmobile claims that its compatible as well... they even have tmobile packaed oem boxes for this particular headset... the hardware protocols also line up... technically, everything should work!!!
i already contacted htc with regards to this issue... this was their reply:
Thank you for your inquiry in regards to Bluetooth headset stereo issue.
Ben, I know how important it is for you to have the bluetooth headset working properly, Unfortunately there is no updates or patch available for the T-mobile wing to fix the issue, although T-mobile might have a ROM upgrade. The reason why the T-mobile dash had no issues with the headset is because it has different drivers for bluetooth support. Look into possibly upgrading the device rom to try and resolve the issue, otherwise you'll need to purchase another headset which is compatible with the device.
i looked into updating the rom and it appears that i have the newest version: 4.10.531.3 WWE from march 15th 07... i wasnt' able to find anything newer... does someone else know of a newer version for the hera110???

Hmm, might be something in T-Mobiles software that is nerfing your set... Not sure of what though...

$100 if you fix it: Loss of speaker audio after BT connections

Hi all, I have had this bug in varying flavours with both the Wizard and now the Kaiser.
If I make a call via Bluetooth (certain devices only e.g. JVC in car stereo), after the call, all audio is lost on the device when using the speaker, e.g. no ringtones, no TomTom voice guidance. (Oddly the touchtone sounds on the phone dialler continue to work.)
Making another call via Bluetooth works fine and all audio is heard, but not if calling via the earpiece of the phone - all phone audio is still muted. A reboot is required. (Even after a reboot, sometimes all audio is muted, and 2 or 3 reboots are required.)
It is like Bluetooth is 'stealing' the audio from the phone's speaker (which is should), but not giving it back at the end, however turning off Bluetooth doesn't return it.
It happens with WM6.x on the TyTN II.
If you can fix it either via a workaround (reboot the audio service after every call?) or a direct fix (HTC are useless and have not emailed me back), I will pledge you $100 via PayPal. I am sure others will join me in pledging an amount also.

Yes. I've seen the same thing with the last stock Tilt ROM, too.

Same here. But is not happening very often.
The other issue for me is if I have A2DP enable and listening to music, then making a phone call will drop the A2DP connection and I have to reconnect A2DP again. It happens to both my JVC car unit and Sony HBH DS220.
I tried that w/ Dutty's WM6.0 and the latest 6.1 rom

I have the same issue, with bluetooth disconnects.

Just staying on-topic here (you can solve A2DP issues with A2DPToggle a great free app), has anyone found a solution to this Bluetooth loss of speaker audio issue, or a workaround to avoid it happening?
Rebooting the phone after every Bluetooth phone call is hardly what I consider a high-end smartphone to require.

Same here
What Radio's are you guys running? (Ignore my signature for the moment, been phoneless and away from here for a while and just getting back up to date )
Haz

My current radio is 1.64.08.21.
I have also tried 1.64.06.04.
Could we be closer to finding the problem? Does the Radio contain the Bluetooth stack?
Here are all available Radios:
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Radio
I'm going to try 1.58.26.20 now. I suggest others try the other 1.5x variants and report back if any of them solve the bug.

Update: I am now offering $100 to anyone who can fix this - see 1st thread.
I have used Windows Mobile since the first ever SPV phone. This one issue is making me look seriously at abandoning that loyalty and getting a Blackberry. If I can fix this for $100 I could be tempted to stay however.

Have you tried BT Audio Toggle ? (found at http://pdaphonehome.com/forums/sams...luetooth-headset.html?perpage=20&pagenumber=1)
Maybe if this helps with your problem then a mortscript could be written to automatically run the utility after a phone call.

What bluetooth headset do you have? Have you tried other headsets or just the one you have? What version of 6.1 are you using?

Thanks, I'll give the audio toggle a go. Might need some help with Mortscript though
I am using the JVC KD-BT1 car stereo with Bluetooth in-car kit. However I can also lose audio on a clean boot even when not in the car, although that is very rare. When using it with the car stereo, it happens after almost every call.
I am running Sleuth's WM6.1 but the other people in this thread are using a variety of BT devices, ROMs, and HTC models.

Can anyone help with how to create a MortScript to run BTAudioOff.exe after each phone call?

Flash a NIKI radio. I had a similar issue with my JVC in-dash CD player and I just got all the radios and tried them all. All the NIKI radios seem to work a lot of the time, while some work and others don't.

Kraize92 said:
Flash a NIKI radio. I had a similar issue with my JVC in-dash CD player and I just got all the radios and tried them all. All the NIKI radios seem to work a lot of the time, while some work and others don't.
Click to expand...
Click to collapse
Thanks, I'll try that too.

Rumball said:
Have you tried BT Audio Toggle ? (found at http://pdaphonehome.com/forums/sams...luetooth-headset.html?perpage=20&pagenumber=1)
Maybe if this helps with your problem then a mortscript could be written to automatically run the utility after a phone call.
Click to expand...
Click to collapse
Okay I tried this and before I even got in the car, chose to turn Bluetooth Audio off using the toggle. Since then I cannot recreate the issue! I am not having to toggle after every call, I only did it once and the problem won't come back!
Fingers crossed...

NP. 1 more thing. What do you mean all audio is lost? Do you mean that the auido goes through the bt device? Or just that there is no audio coming from either at all. If that's the case, then all you might have to do is go to Comm Manager>Settings>Bluetooth>JVC (or whatever you named it) and uncheck the Stereo sound and viola it should work unless you are not using A2DP >.> . I think it's either directing all sound to your bt device or trying to send sound to it but failing.

Kraize92 said:
NP. 1 more thing. What do you mean all audio is lost? Do you mean that the auido goes through the bt device? Or just that there is no audio coming from either at all. If that's the case, then all you might have to do is go to Comm Manager>Settings>Bluetooth>JVC (or whatever you named it) and uncheck the Stereo sound and viola it should work unless you are not using A2DP >.> . I think it's either directing all sound to your bt device or trying to send sound to it but failing.
Click to expand...
Click to collapse
The issue is there is no audio coming from either the phone or the Bluetooth device. I hear the Bluetooth device disconnect, and its display shows that it has also.
I see no 'Stereo' option to untick for the JVC in its Bluetooth settings, only Hands-free and Wireless Stereo (already unticked).

No progress
Okay, this is seriously getting me down now It all sounded so promising. I have tried the following:
Flashed Niki Radio 1.58.21.23
Tried using Bluetooth Toggle - it seemed to work once when I turned BT off before connecting, but after a reboot the problem is back
Tried a HFP extension PM'd to me (thanks anyway - didn't help)
Made sure Bluetooth Stereo is unticked in the JVC's settings on the phone
I am not sure if the problem is worse when taking a call as TomTom is running.
Here is an interesting development which might help someone narrow down the cause:
I make a few calls, and as always audio is lost, even for phone calls sometimes.
Touchtones on the keypad are the only sound that the phone continues to emit itself. Everything else (TomTom, ringtones, etc.) is dead.
I then go into the JVC's A2DP mode and 'Connect'. The icon appears on the mobile's title bar, and I can hear phone audio through the car stereo.
I 'Disconnect' and the phone's audio is still lost.
What this tells us is that the phone is putting out sound, just not through the speaker.
If someone can write something that will reset the speaker driver after a call, my offer for $100 still stands.

Just to update this, the issue still exists with a clean install of HTC's new 2-May-08 WM6.1 ROM from their website. To***rs!

CJSnet,
Since we got the similar setup w/ exact the same issue (Att Tilt w/ JVC BT-1), I think the problem is basically Kaiser does not switch back to A2DP profile properly after headset profile from phone call. The same issue happens to my Sony HBH DS-220 stereo headset too.
I tried my Eten M600 w/ JVC BT-1 and does not see this problem

Bluetooth sounds bad

Hey all,
I have Froyo 2.2 on my N1...anyone know why my bluetooth headset crackles and is really fuzzy sounding? Sounds like they are underwater sometime...I even tried a new bluetooth headset with same problem...any ideas? Thanks.

rayman121985 said:
Hey all,
I have Froyo 2.2 on my N1...anyone know why my bluetooth headset crackles and is really fuzzy sounding? Sounds like they are underwater sometime...I even tried a new bluetooth headset with same problem...any ideas? Thanks.
Click to expand...
Click to collapse
which FroYo ROM, and which kernel.

mine does the exact same, its not just you its probably a froyo issue.

ok so i was bored and did some tests, it seems it only happens to me when trying to send audio via bluetooth when playing a flash video, reg music and videos are no problem.

I also have same problem, but on CM 5.0.X (Android 2.1). I tried Motorola S9-HD (stereo) and Nokia HS-56W (mono). Every time connect the headset and the phone is very close (20-30 cm), the sound is fine, but as soon as the phone is to push further, the sound is choppy and stutters. And this happens on any headset.

is WiFi on or off?
WiFi and bluetooth operate on same frequency band and can cause issues.

i have wi-fi on and bluetooth on.

switch WiFi off and try.

arkavat said:
switch WiFi off and try.
Click to expand...
Click to collapse
I switched off Wi-Fi and connect Motorola S9-HD and it really workes. A will try today use more and write late about it.

Same problem here with Froyo.
I turned Wifi off and the sound problems went away.
I think is a hardware problem or design problem because I used to use the same headset (Motorola H-710) with an iPhone and never had this problem even with Wifi switched on.
Would be any way to get rid of this problem?, it really bothers me to turn off the Wifi every time I get a phone call.
Thanks

its a problem with flash, not bluetooth, adobe should fix it soon

Thank you for the suggestion I will be sure to try that tomorrow!
I have kernal 2.6.32.9-27220-g328f560 android build apa26 #1
Build number is frf50
I hear this is a test version of Froyo anyway...I don't think the real Froyo has been released yet? So maybe it will be fixed...thank you.

After two days of tests, with switched off Wi-Fi, it turned out that the problem does not disappear completely. Correctly identify the reason for failed. Since stuttering occurred on different songs (that is, perhaps, that stuttering is dependent on the bitrate), I sometimes felt that the problem with lowering the frequency of the processor in sleep mode, and it is not enough to encode mp3 and transfer data via Bluetooth.

Still bad with OTA
I got the froyo OTA for my stock N1 yesterday morning.
I can confirm that the distorted sound is present on the phone application only when wifi is turned on and you are using bluetooth. At first I thought it was only when wifi was on but not connected but it appears that you can get the distortion on a phone call whenever wifi is turned on.
All entertainment application seem to work fine with my A2DP bluetooth. Again it only seems to be bluetooth phone calls and wifi turned on. Believe me this is bad enough. This didn't happen on 2.1 and if it weren't so much hassle I'd probably go back.
Hopefully someone will come up with a workaround that will allow bluetooth calls and wifi turned on at the same time. Gees, if it weren't so basic

This just drives me nuts that Google makes major changes to parts of the OS, then doesn't think to actually TEST everything they changed. This would easily been detected if they actually tried it out. Duh.

I have the FRF91 update and all the blutooth distortions are GONE.

Blueman101 said:
I have the FRF91 update and all the blutooth distortions are GONE.
Click to expand...
Click to collapse
I updated from stock via the OTA to FRF91 and thats actually when the distortions showed up on mine? Well its good to know that there is hope but now I am wondering what possibly may be different between mine and yours?
Can anyone else tell us how their bluetooth is doing on FRF91?

Does anyone think a froyo factory data reset is worth trying?

Weird problem with speakers and mic

I have a problem with my unrooted Xperia Z with a locked bootloader. My main speaker does not work for any media like music games or videos, but works fine for loudspeaker calls. Also the earpiece speaker doesnt work at all. Another problem i found was that my microphone would not work at all unless it was in a call and i was using loudspeaker. The final problem is that when ever i plug in my earphones, google now pops up and sometimes my phone starts playing music automatically throught the earphones, when i remove the earphones, instea of stopping the music continues but the speakers dont work so it just keeps playing them silently. If anyone knows the soultion to this, please respond as ive searched everywhere and i have not found one solution yet.

UPDATE: i used the application soundabout to reroute the audio and the calls are now fine, the only problem is that when i plug in my earphones the google now problem persists. If i plug in earphones with a mic, i dont get any of these problems and everytime i want to use my internal speaker for media, i have to manually re-route the audio to them. Anybody know a solution to these 2 problems?

I do have the exact same problem, I tried different ROMs and Audio Mods (at the moment I've got a stock ROM) without any change.
Did you somehow fix it?

Exact same problem, i run stock android 5.1.1 build 10.7.A.0.222 locked boot loader. Problem suddenly came up last week during vacation, quite some time after I did OTA upgrade to 5.1.1 - so this is not related to ROM updates.
After installing soundabout (thanks for the hint) the rerouting did not work immediately - i had to set phone to earpiece and media to speaker in the app and reboot for it have an effect.
I think the root cause is, the phone thinks there are headphones connected, when there really aren't. If I use the UKW radio app, it starts and shows headphones as output-icon right away - it should actually complain that there is no reception without phones because the antenna (headphone cable) is missing. Since it doesn't complain I guess that's the culprit.
Any hints how to fix that, without using a rerouting app? (kinda stupid, using bluetooth speakers and so on now needs a manual setting change in soundabout).
I have that phone for more than 2 years now and used headphones maybe twice with it, so a busted headphone-jack is out of the question too.

Guys give it a try.

Thanks Ess Arr, that really works!

Google Home Mini + BT speaker = stuttering music

I encountered stutter when broadcasting music from GHM to my BT speaker. It's like buffering every second. With the Internet connection everything is ok. The router is located near the GHM. When connecting via BT to the phone or through AUX with any other source, my Marshall Acton plays music without any problems. The problem occurs only when the music is broadcast from the GH Mini. It started a couple of days ago. Up to this point, there were no problems for a week. It happens randomly, it can play an hour without stammering, and then start, or vice versa. The GHM itself plays without problems. Tried TuneIn and Google Music. I also tried to reset GHM.

CC Audio has no Bluetooth

Has anyone encountered this problem?

The same thing has been happening for me as well. It only occurs when playing to a Bluetooth speaker. Playback via the Google Home Mini speaker itself is fine and it is right next to the wifi router.
What firmware are you on? Mine are on 1.32.118652. I think it's a preview firmware so it may be a bug in the firmware as nothing I do has made it any better and it was working fine before and has only started over the last few weeks.

athua said:
The same thing has been happening for me as well. It only occurs when playing to a Bluetooth speaker. Playback via the Google Home Mini speaker itself is fine and it is right next to the wifi router.
What firmware are you on? Mine are on 1.32.118652. I think it's a preview firmware so it may be a bug in the firmware as nothing I do has made it any better and it was working fine before and has only started over the last few weeks.
Click to expand...
Click to collapse
The same version. Do you remember what version was before the problems started?
Created a topic in Google support - https://productforums.google.com/forum/#!topic/googlehome/e694YsvR9M8
Another person with the same problem - https://productforums.google.com/forum/#!topic/googlehome/wqB5eG1bwaI

I bought the Home Mini yesterday and found the same problem. Any update about it?

Same
Same here. Stuttering music. Thought I was the only one and there was something wrong with my BT speaker. Stuttering music. FW 1.32.118652
Managed to get it working by unpairing and forgetting, and re-pairing. Now it happens every time my BT speaker goes into sleep mode.
More irritating is that when this happens the Google Home Mini defaults back to its own speaker instead of trying to reconnect.
This is firmware basics. Let's hope they iron this out.

My BT speaker will start to studder with about 25% battery left now or when it's actually plugged in. Fresh charge will run fine.

I'm having this issue too. I'm at the latest update at the time and using Harman Kardon Aura speaker

I'm having the same issue on GHM in 2022, using an Anker Soundcore Flare 2. Seems like Google has not fixed this issue. Does anyone know if Google Nest Mini has the same issue too?