my phone is a HTC touch cruise, WindowsMobile6.1.
it was no problem playing mp3 music before. i got a bluetooth stereo headset recently, and i connected it with the phone and tried play music via the headset and it worked. but after i turn off the headset windows media cannot play music any more. it always popup with this 'Unspecified error' message. i tried soft reset the phone but still cannot play. and when i connected the headset again it worked with the bluetooth again.
the interesting thing is if i put the mp3 into application data\sounds, then i can play it in notification setting preview without blutooth.
how can i get the player working without the bluetooth headset? i guess this may because the player still try to play via bluetooth while it is disconnected, but how can i set it back to normal?
THis is a wierd problem i havent heard before.
I use Sony bluetooth headphones with my t cruise with now problems at all. The only ***** was having to go thru settings/connections etc to connet them, which i solved using a2dp toggle switch (see my post).
As for your problem, mm wierd. You say ur using wm6.1, so obviously a cooked rom yes?? what rom are you using? I havent flashed my cruise yet as i am waiting for the official wm6.1 from htc to come out first to try and compare.
This is probably a bug in your cooked rom. From my understanding of a2dp drivers it is only turned on when bluetooth headset is connected. When the headphones are off, the driver is not on meaning u should be able to use media player normally (or am i talking ****??)
You might be in for a hard reset......
Let me know how u got on please.
looks like a2dp is not turning off after disconnecting the bluetooth headset. If it was me I would hard reset and try again. if the problem comes back, try a different rom.
the rom was put in by seller when i got the phone,, i'm still new to the WinMobile, don't know how to load the rom again. i installed the TCPMP now, it seems working ok. i'll try some other headset and see how it goes..
Let me start off by saying this is more of a workaround than a fix. I have been hoping that the release of Donut may have fixed the A2DP skipping problem but until late I had rendered my Plantronics Voyager 855 useless for listening to music. I could not listen to anything with out i skipping so bad that it would have been better to turn off bluetooth and hold the phone to my head to listen to media. I have found a fix that may hopefully lead to someone figuring out what is actually wrong.
Step 1: turn off bluetooth and unpair your headset
Step 2: start a song on a media player
Step 3: go back turn bluetooth on and pair your headset
you may or may not have to unpair your headset sometimes it works if you just turn bluetooth off start a song and then go turn it back on again
Once it connects your media will start playing perfectly through the headset for as long as the media is playing. Unfortunately once you stop playing media for more than a few minutes and then try to start it again the skipping will also start again.
Have you also tried using a task manager to kill everything BEFORE you start the music player? That works 60% of the time for me.
Another solution that generally works the other 40% of the time is to go into your bluetooth settings, press and hold on your BT device, at menu pop-up, touch "Options" then just unlink the Media, and then re-link it.
Hope this saves you some time in the future!
q426669 said:
Have you also tried using a task manager to kill everything BEFORE you start the music player? That works 60% of the time for me.
Another solution that generally works the other 40% of the time is to go into your bluetooth settings, press and hold on your BT device, at menu pop-up, touch "Options" then just unlink the Media, and then re-link it.
Hope this saves you some time in the future!
Click to expand...
Click to collapse
its funny that unlinking media works for you because i tried that and it does nothing for me. The fastest way i can get it to work is turning bluetooth of and back on again.
I'm having the same problems with my JVC car stereo.. It skips pops etc.. with no way to fix.. i'll try this work around tomorrow but does anyone know what causes this?
I see one of you is running latest Cyanogenmod. I'm not sure what the issue is you are having with A2DP maybe your paired hardware? i typically have Pandora streaming to my car stereo in the background with Telenav running.
EDIT: I use Tunewiki instead of Music player if that makes a difference.
Well actually it does happen in CyanogenMod although its not a skipping issue... Its more of a faint popping issue that I get.
I dont hear it using the aux headphone jack on my htc adapter but i do when i switch over to bluetooth.
Right now i'm running Enomther's ASOP+ADP rom because CyanogenMod has been having freezing and rebooting issues (thanks to the switchrom script for letting me switch back and forth) and this is where i'm really getting a skipping and popping issue big time.
For both I use Tunewiki as well, for m4a's that i buy on iTunes or SHOUTcast radio (gotta love internet radio on the go...)
I thought it was because I was running Google Maps as well as tunewiki (I have a car GPS mount) but even just letting it run only Tunewiki it still has issues (although far worse at times running Google Maps)
I just can't seem to pinpoint the issue.. I could just use the aux headphone jack to my car stereo yes, but then since I have the charger connected I get the annoying ground loop noise which is far worse than the bluetooth popping and skipping issue...
EDIT: This is my Car Stereo: JVC KD-A805
Check out for workarounds in http://code.google.com/p/android/issues/detail?id=2807
os2baba said:
Check out for workarounds in http://code.google.com/p/android/issues/detail?id=2807
Click to expand...
Click to collapse
Those workarounds don't work for me. It is good to know this issue is known though and is being reported by more than one.
My Tunewiki still skips either way.. even turing off most background apps do not help.. I was looking into editing the audiopara4.csv file possibly (someone apparently added a line for his BMW and it fixed his issue) but don't know where to start.
q426669 said:
Have you also tried using a task manager to kill everything BEFORE you start the music player? That works 60% of the time for me.
Another solution that generally works the other 40% of the time is to go into your bluetooth settings, press and hold on your BT device, at menu pop-up, touch "Options" then just unlink the Media, and then re-link it.
Hope this saves you some time in the future!
Click to expand...
Click to collapse
After intense observation, I realized I experience the skipping only after I place a call. The following two steps always work for me ( I prefer #2)
1. Turn of bluetooth and turn in it back on while the music is playing
2. In bluetooth settings unlink the phone and thats it; you might have to turn off bt and back on and it works until you use the bt for phone again
I also noticed that the skipping is not ROM specific with me; I tried it when my G1 was unrooted, thru XROM. I'm not sure what causes the skipping, I experience no skipping with my S9 (works flawlessly), however my Jabra BT3030 is what gives me all the grief (better headset IMHO)
Just found a really easy way to get a2dp to work perfectly. Once you have what ever you want playing just make a call to your voice mail, once the call gets transfered to your headset hang up and what ever you are playing will play perfect through the headset.
eclair rom.
bluetooth works perfectly on them.
This application is a hotfix for a really annoying (and potentially unsafe!) bug in the Epic4G:
http://code.google.com/p/android/issues/detail?id=11372
http://forum.sdx-developers.com/epi...audio-routing-on-epic-4g/msg115990/#msg115990
The long and sort of it is that when anything is plugged into the 3.5mm headphone jack, the phone will only play call audio over that jack.
In order to route the audio through the earpiece, bluetooth or speakerphone, you must pull the plug out of the jack. This is at the very least annoying, and at the very worst potentially dangerous if, for example, you're driving.
How-To
Download the APK attached below for your android version.
Install like any other APK using adb or your favorite file manager.
What it does
This simple application allows you to pick the audio device to use for call audio to override this behavior, and can be changed on the fly.
All in-call audio will be routed to the device you specify when something is plugged into the 3.5mm headphone jack. If nothing is in the jack, the default behavior for the phone applies.
This also allows you to use the Speaker Phone when the headphone jack is occupied, even though the button on the call screen is disabled!
Your configuration should persist between reboots.
What it doesn't do
This app does not route any other type of audio. Your music, notifications, etc will still play over the headphone jack or phone speaker.
Again, this *only* affects in-call voice audio, and only when something is plugged into the headphone jack.
Notes
This app completely overrides the options on the call page! If you want to switch outputs during a call, you will have to do it from this app - your call will not be dropped when changing the output device.
In order to route the call audio properly, the system's mediaserver service must be restarted, however.
This means that any other audio you have playing when you apply the change will be disrupted, and related services may force close. For example, Pandora will skip to the next song. Other applications may not behave that well.
Disclaimer
This app modifies files in the /system partition, so use this at your own risk! I am not responsible for any problems that arise from this hotfix on your device!
This is currently for the EPIC4G *ONLY* - Do not use this on any other device. Please contact me if you have a different phone which experiences this bug and I will see if I can get it working for you as well.
This is *BETA* software, a work in progress, please post here if you experience any issues, but I cannot guarantee it will work for you!
ROM DEVs, feel free to bake this into your roms in whole or part, I encourage it as this provides a workaround for a safety issue, but please give credit if you use or derive from this application.
Special thanks to UberPinguin - his initiative, debugging, code-diving and testing helped make this happen every step of the way!
Many, many thanks to everyone in #samsung-epic for helping me test and work this out.
Be sure to download the APK for the right android version on your phone!
epicBT - v0.3.5 (Froyo)
* Fixed crash/reboot when applying settings in DK17 roms
epicBT - v0.3
* Layout cleanup when root is unavailable
epicBT - v0.2
* Requires root!
* Superuser compatible
* auto-remounts /system RW if necessary
* Sends call audio to wired device ( default ), speaker phone, or bluetooth
Sources
https://github.com/cicada/epicBT
If this works as described above I will be so f-ing happy. One of my biggest gripes, solved.
No sh#t! I was just about to start searching the Market for an app like this! Downloading now to test.
Thank you!
bigdbag said:
If this works as described above I will be so f-ing happy. One of my biggest gripes, solved.
Click to expand...
Click to collapse
I agree
updated OP with source link
First of all,...Thank you, Thank you, Thank you for working on this... This was one of my biggest gripes with this phone and I couldn't understand why the "geniuses" at Samsung/Sprint couldn't get this right.
I've done some extensive testing in my car for the Eclair version and wanted to share my results:
For the most part, the app does what it's supposed to...but I did notice that:
1) the "on the fly" feature doesn't work so well. That is, when changing from one mode to the other, I had to reboot the phone to get the new setting to take effect. This feature would be great with an app like Tasker, which could automatically open up the app and ask you which setting you want to use when a headset/aux jack is plugged in,...thus giving you the flexibility to use the best option depending on your situation. Is there a way to tweak the app to recognize the switch without rebooting by resetting something like the mediashare service?
2) For some reason, the mic volume (volume heard on the opposite end of call) on the bluetooth setting is lower when the headset/aux jack is plugged in. I'm not sure whether the regular phone mic, speaker phone mic, or the bluetooth mic is utilized in this setting, but the volume is definitely harder to hear on the other end than when the headset jack is unplugged. I would guess about 20-25% lower. I tested this effect during the call as well by plugging and unplugging the jack while counting 1 to 10 and it's the same. Is there away to increase the sensitivity of the bluetooth mic when the headset jack is plugged in?
Donation coming if you can get this working! Thanks again.
sinman02 said:
1) the "on the fly" feature doesn't work so well. That is, when changing from one mode to the other, I had to reboot the phone to get the new setting to take effect.
Click to expand...
Click to collapse
Strange, it works well for me - it takes a second to switch outputs while mediaserver is restarting, but never had to reboot. I'll look into this, may have accidentally tweaked something in the last build.
UberPinguin and I are still looking at the sources to find a better fix that works the way it's supposed to - the trouble seems to be that Phone.apk is actually selecting the 'correct' source and setting options appropriately, but the underlying OS isn't switching outputs. Restarting mediaserver was the only workaround I could find for this.
sinman02 said:
2) For some reason, the mic volume (volume heard on the opposite end of call) on the bluetooth setting is lower when the headset/aux jack is plugged in. I'm not sure whether the regular phone mic, speaker phone mic, or the bluetooth mic is utilized in this setting, but the volume is definitely harder to hear on the other end than when the headset jack is unplugged. I would guess about 20-25% lower. I tested this effect during the call as well by plugging and unplugging the jack while counting 1 to 10 and it's the same. Is there away to increase the sensitivity of the bluetooth mic when the headset jack is plugged in?
Click to expand...
Click to collapse
I hadn't noticed any volume issues but truthfully I haven't been using the BT often because of this bug - I've just been letting my calls go to VM instead of crashing my car Volume selection should be working properly so I'll see if I can add something to select volume as well.
To be clear on the MIC, input should always be the proper input for whichever mode you choose - phone MIC for speakerphone and BT mic for BT HP/HS.
If you're on stock then the phone mic should be used when your wired device doesn't have it's own, however this is broken in all of our custom community kernels - Wired Headset mode should only be used when you actually have a wired headset with a MIC of it's own if you're using one of these, otherwise the phone doesn't enable any MIC at all.
I should note, that all my tests were conducted on outgoing phone calls. I don't know if incoming calls are any different. I am using the Syndicate rom.
If you can get the bluetooth volume issue resolved, I'll likely leave it there, but it would be nice to be able to switch on the fly to speakerphone mode when bluetooth isn't handy.
Question: Does the froyo version have the same implementation?
Please keep up the good work!
Sent from my SPH-D700 using XDA App
sinman02 said:
Question: Does the froyo version have the same implementation?
Click to expand...
Click to collapse
Yes, the froyo version is the same - Samsung used a different asound.conf in froyo ( added in some interesting VOIP pcm ), so this is the only difference between versions currently.
cicada said:
This application is a hotfix for a really annoying (and potentially unsafe!) bug in the Epic4G:
The long and sort of it is that when anything is plugged into the 3.5mm headphone jack, the phone will only play call audio over that jack.
In order to route the audio through the earpiece, bluetooth or speakerphone, you must pull the plug out of the jack. This is at the very least annoying, and at the very worst potentially dangerous if, for example, you're driving.
Click to expand...
Click to collapse
...So this should work on for Sip/VOIP apps like Sipdroid, 3CX, and Fring? I managed to pick up 3CX and Sipdroid through my bluetooth headset but no mic...meaning the other end could not hear me... There aren't that many good sip/voip soft wares out there for the Android today.. I rated Fring the BEST but with no bluetooth support.
EDIT: Nevermind... I read the post again.. I don't think this will do the job other than support for the actual phone.. but it would be nice to have that option for sip/voip as well.
The SIP/VoIP stuff may work better in Froyo considering there are dedicated PCM devices listed in the asound.conf - however I've never used any of these applications, so this is pure speculation.
You're correct, this does only effect in-call phone audio, those applications would be handling (or in this case, not) the bluetooth audio routing directly. I've found lots of other similar quirks with BT on the Epic4G, such as the << and >> buttons on my A2DP headphones not working.
cicada said:
The SIP/VoIP stuff may work better in Froyo considering there are dedicated PCM devices listed in the asound.conf - however I've never used any of these applications, so this is pure speculation.
You're correct, this does only effect in-call phone audio, those applications would be handling (or in this case, not) the bluetooth audio routing directly. I've found lots of other similar quirks with BT on the Epic4G, such as the << and >> buttons on my A2DP headphones not working.
Click to expand...
Click to collapse
I am using Froyo the DJ29 Build on the epic... Dare I try?
****ing yea! Thanks, downloading now. This has been my biggest complaint with the phone
Sent from my SPH-D700 using XDA App
Hell Yea! You rock! I Threw out a fairly long search sentence in google and actually found your post here. No sooner did I install and set it up that my phone rang while plugged into the car audio and FINALLY I can use my friggin BT headset without yelling hold on hold on I gotta unplug the stereo cable. This has really peeved me off since I got the phone. Now what I don't get is why this obvious flaw has been ignored by Samsung and Sprint. Nice job on making it work like it should. BTW running stock 2.1 with root. No bugs so far.
THANK GOD. someone fixed this. bugged me so much in the car when i'm receiving a call. will report any bugs.
bump, updated to fix crash in DK17 based roms
cicada said:
I hadn't noticed any volume issues but truthfully I haven't been using the BT often because of this bug - I've just been letting my calls go to VM instead of crashing my car Volume selection should be working properly so I'll see if I can add something to select volume as well.
To be clear on the MIC, input should always be the proper input for whichever mode you choose - phone MIC for speakerphone and BT mic for BT HP/HS.
If you're on stock then the phone mic should be used when your wired device doesn't have it's own, however this is broken in all of our custom community kernels - Wired Headset mode should only be used when you actually have a wired headset with a MIC of it's own if you're using one of these, otherwise the phone doesn't enable any MIC at all.
Click to expand...
Click to collapse
As others, I'm very grateful for this fix. After trying it out, if it works for me, donation on the way.
Regarding the MIC: My experience, all the way back to pure stock (IIRC) is that there is no MIC at all when a two-channel, stereo plug is inserted (headphones, cassette adapter, etc.). Every time I've been driving, listening to something via the headset jack, when a call comes in I can hear the other party, but they can't hear me at all until I unplug from the jack. So, even though there was no mic plugged in and the device was correctly sending 2-channel audio out through the jack (usually to a cass adapter, so I can listen via my car stereo), but doesn't "do the right thing" with the mic, even though the hardware and drivers are capable of detecting the absence of the mic.
It should, of course, default to the BT mic if there is a BT connection, or the built-in mic otherwise. For some reason this simple flow-diagram logic eludes Samsung.
So I got my first experience with this today...worked great. I was streaming Pandora, phone call came in, music was paused and I answered the call. Once I finished the call, the music continued playing. Minor detail, but since I was on WiFi, is there anyway that the music could have kept on playing while I was still on the call for the sake of my guys who were still working while I was taking the call? It's great that the music paused and resumed by itself, but it would have been cooler to have it keep going while I was on the call.
m5james said:
.. is there anyway that the music could have kept on playing while I was still on the call .. ?
Click to expand...
Click to collapse
Unfortunately Pandora's phone-state listeners control that, it'd have to be modified or their devs would have to add options for it. Would be cool though, I agree
I've got a hacked version of Pandora that allows unlimited skips, I'll have to ask the guy who did it to see if they can tweak that as well. Come to think of it, it'd be nice to have it keep going for the times I'm driving down the road as well so whoevers in the car doesn't have to sit there and listen to me blah blah blah.
Getting a "Paired but not connected" issue with my bluetooth ear-piece and I've tried everything to get it to connect, even force closing wiping all the data from the bluetooth application and rebooting several times. I've only had this problem since switching from cyanogen mod to vegan tab (Love vegan tab btw) does anyone know some fixes or solutions?
Thanks in advance :3
come on :\ doesnt even one person have a suggestion?
I was able to pair my phone with the Vegan Beta 5.1 gTablet without issue...
I just bought a new headset and will try it and let you know...
Working fine for me as well but when I disconnect I have to re-boot to get audio over speakers on the GTAB
hmmm, thats really odd, maybe my headset itsself is being stupid. Thanks for the feedback guys.
lifeisfun said:
Working fine for me as well but when I disconnect I have to re-boot to get audio over speakers on the GTAB
Click to expand...
Click to collapse
I've found if you plug and unplug a regular wired headset into the headset jack, thst usually fixes the audio be muted on internal speakers.
bluetooth help
I am having the same problem. Tried 2 different headsets, netbook, and my moto droid - but everything says "paired but not connected". nothing works! please help
may be a direction for a fix; DEVs could you clarify for us
I found this in a post today by enigma0456:
More research finally revealed something. BlueGPS4droid at sourceforge not the market. So, the external gps was "paired but not connected" until there was an application (bluegps) to "connect" to. Once that was installed I turned on the bluetooth and it immediately saw the hollux remote gps receiver. Tested it with Maps and it worked beautifully. So theories:
1. If there isn't an app waiting to use the bluetooth device it will pair but not connect until something asks for it.
now I realize this has to deal with gps but as i understand all phone apks have been removed that can be and not lose functionality in order to save battery life in Vegan 5.1 so if the above quote is right then there is no app (phone.apk etc.) to ask for the use of the ear piece and thus the paired but not connected issue.
now some people have mentioned not having issue getting their BT headset to work and maybe this is because the headset offers another use in their programing like they are designed to work like headphones or something and then there would be and app to ask for them and so they connect
the ones that do not work on the other hand like mine are only designed for phone audio; ever notice that on your Droid cell that your headset will say connected to phone audio, well in our case if the phone.apk/s are not there then there is nothing asking to connect to it.
DEVs are there any ideas to get functionality back even it that means adding back the phone.apks--and is that possible to do with our re-flashing a rom like side installing it or an update.zip
Thanks
wnbowman said:
I've found if you plug and unplug a regular wired headset into the headset jack, thst usually fixes the audio be muted on internal speakers.
Click to expand...
Click to collapse
There is an app on the market, called "headset toggle widget" and that will do the trick and unmute your speakers
Possible workaround...
Don't know if this will help but, after I paired my BT headset with GTAB, I then paired it with another device (my phone) after which GTAB started giving me the paired but not connected message when I tried to connect back to the GTAB. What worked? Well, now before I select the headset device in GTAB's bluetooth device menu, I put the headset itself back into pairing mode. THEN, I select it in GTAB's bluetooth device menu and voilà, it connects. Downside, I have to put the headset into pairing mode everytime I want to connect it to GTAB. (Haven't bothered trying to unpair the headset with my phone yet to see if it makes a difference.) Hope it works at least as temp fix for ya.
Hi you all, I have a non common bluetooth problem. My S6 is running Xtrestolite with android 6.0. My phone can connect BT to my cars, my earset and my soundbar to play music and it work well even on my earset. BUT, nothing for voice call, the call connect and silence for everyone. There is no voice at all, but BT is connected, and all infos on my cars radio like timer, mute and others work well ( okay mute cannot be more muted ). So I tried 1/8 headset for music it works, did not try yet one with a mic, but I'll do it ASAP. I tried to reprogram with odin default OS, with factory settings, and that way force all components to be re-write ( Bootloader, Radio , etc ), issue still present !!! Try to clean micro usb connector, nothing !! Try to clean audio jack, but wasn't really sure if it was well cleaned.
Do anybody here have an idea of what I could try, test or do to eliminates possibilities ??
I am thinking that maybe some corosion could be in the audiojack, somewhere and let the phone think that there is an audio jack connected, and then sent the voice to it...but how it could be tested before to try to open the phone to clean it properly and risk to damaged the LCD ???
Thank a lot for all of your advices