Database Info

[APP][4.0+] AudioBT: Use Bluetooth headset for GPS and notification audio

Hi
I've created a small app that automatically switch your device into Bluetooth call mode when an app is playing an audio or when your GPS is giving directions. The benefit is that it will cut what you're currently listening from your car audio system to play the incoming call audio and go back to your current listening on your CD, MP3, FM radio, etc.
There are two ways of using AudioBT.
-One is a background service that monitors the audio focus and turn on the Bluetooth SCO proile when another app is temporarily requesting the audio focus. Unfortunately the first second of the audio might be cut when using this service (to be fixed with upcoming Xposed hook). Some applications do not request the audio focus properly so this might not always work.
-The other approach is an integrated TTS engine. Any app using tne Android TTS service can use the AudioBT TTS service for sending text to speech. AudioBT will automatically turn on the Bluetooth SCO profile before playing the text. Any TTS service or language can be selected in the AudioBT TTS parameters.
It is still experimental and user's feedback is appreciated.
Thank you!
https://play.google.com/store/apps/...51bGwsMSwxLDEsImNvbS50dXJib2xlZC5hdWRpb2J0Il0
Service intents (for use with Tasker)
com.turboled.audiobtplus.ON : Cat = Default, Target = Service. Turns ON the AudioBT Plus service.
com.turboled.audiobtplus.OFF: Cat = Default, Target = Service. Turns OFF the AudioBT Plus service.
com.turboled.audiobtplus.SCO_ENABLE : Cat = Default, Target = Service. Enables Bluetooth SCO channel audio.
com.turboled.audiobtplus.SCO_DISABLE : Cat = Default, Target = Service. Disables Bluetooth SCO channel audio.
com.turboled.audiobtplus.PLAY : Cat = Default, Mime Type = audio/*, Data = file uri (file:///*), Target = Service. Plays an audio file through the bluetooth channel. No need to call SCO_ENABLE or SCO_DISABLE. Specify file name in Data.
To play notifications through Bluetooth with Tasker, create a new task with the following steps:
-Say to file (Misc), text = %NTITLE, file = /sdcard/Download/1.wav. Use standard TTS engine (Pico, Google, SVox, etc...), EnhancedTTS or AudioBT+ TTS are not supported.
-Send an intent (Misc), action = com.turboled.audiobtplus.PLAY, cat = Default, Mime type = audio/*, Data = file:///sdcard/download/1.wav, Target = Service.
Add a new profile with Event -> UI -> Notification and link with the task created above.
Add the task to any profile triggered on Notification *,*. Make sure Tasker is enabled in your Accessibility parameters.

Re: [APP][4.0+] AudioBT: Use Bluetooth incoming call for GPS audio
TurboLed said:
Hi
I've created a small app that automatically switch your device into Bluetooth call mode when an app is playing an audio or when your GPS is giving directions. The benefit is that it will cut what you're currently listening from your car audio system to play the incoming call audio and go back to your current listening on your CD, MP3, FM radio, etc.
There are two ways of using AudioBT.
-One is a background service that monitors the audio focus and turn on the Bluetooth SCO proile when another app is temporarily requesting the audio focus. Unfortunately the first second of the audio might be cut when using this service. Some applications do not request the audio focus properly so this might not always work.
-The other approach is an integrated TTS engine. Any app using tne Android TTS service can use the AudioBT TTS service for sending text to speech. AudioBT will automatically turn on the Bluetooth SCO profile before playing the text. Any TTS service or language can be selected in the AudioBT TTS parameters.
It is still experimental and user's feedback is appreciated.
Thank you!
Click to expand...
Click to collapse
Links please
Sent from my GT-N8000 using XDA Premium HD app

hoss_n2 said:
Links please
Click to expand...
Click to collapse
Well, it was right there on the Google Play image... I added an hyperlink below.

New version 2.2.0 to be published soon on Google Play. Attempt to fix compatibility issue with some devices. If you tried this app on your phone and it didn't work, try the upcoming version.
Thanks

I've tried your app with my alpine cde 133bt, but the tts-messages were still send to the normal bluetooth audio-out channel, so I have to manually switch from tuner to bluetooth mode. Both the service and the custom tts-engine didn't work. Your app is exactly what i've been looking for, so let me know if there is anything I can do, to help fix this.
my setup: I have a motorola razr running on android 4.0, which connects to the radio with the HFP and with the A2DP profile. turning a2dp off in the bluetooth settings redirected the tts-messages to the mobile speaker.

sebistan said:
I've tried your app with my alpine cde 133bt, but the tts-messages were still send to the normal bluetooth audio-out channel, so I have to manually switch from tuner to bluetooth mode. Both the service and the custom tts-engine didn't work. Your app is exactly what i've been looking for, so let me know if there is anything I can do, to help fix this.
my setup: I have a motorola razr running on android 4.0, which connects to the radio with the HFP and with the A2DP profile. turning a2dp off in the bluetooth settings redirected the tts-messages to the mobile speaker.
Click to expand...
Click to collapse
Hi,
I've got other similar complains from Motorola users. I have not been able to figure out the problem yet. Are you able to provide me with a Logcat when you start the AudioBT service ?
Also can you test BTMono, which is a similar app but that leaves the audio channel open (incoming call) ? If BTMono works my app should work. However BTMono is from a different author and uses more permissions.
Thanks

i tried btmono yesterday, it works. I will get back to you with the logcat later

sebistan said:
i tried btmono yesterday, it works. I will get back to you with the logcat later
Click to expand...
Click to collapse
At the same time, you could try 2 test versions I created. The first one adds more permissions (Bluetooth_admin and network_access). The second one use Call mode instead of Communiation mode. Please tell me if one of these works on your device.
Here's the link to both APK:
https://docs.google.com/folder/d/0B2XwV7ab33OAY2tiVVRTWGRRTVE/edit?usp=sharing

here is the logcat record, i hope it helps. i started recording, started your service and pressed the test audio button.
i also tried the two test versions, they both did not work, same behaviour as the original one
edit: aparantly i'm not allowed to post external links (or edit my post for 5 minutes). i've attached the logcat output

sebistan said:
here is the logcat record, i hope it helps. i started recording, started your service and pressed the test audio button.
i also tried the two test versions, they both did not work, same behaviour as the original one
Click to expand...
Click to collapse
Thanks for your help. Where's the log ? Ah there it is

sebistan said:
here is the logcat record, i hope it helps. i started recording, started your service and pressed the test audio button.
i also tried the two test versions, they both did not work, same behaviour as the original one
edit: aparantly i'm not allowed to post external links (or edit my post for 5 minutes). i've attached the logcat output
Click to expand...
Click to collapse
Hey sebistan, thanks A LOT for your logcat. I saw an error about a missing BROADCAST_STICKY permission. I've create a new version AudioBT-Sticky at the same link: https://docs.google.com/folder/d/0B2XwV7ab33OAY2tiVVRTWGRRTVE/edit?usp=sharing
Your help is a blessing. Now if that works, I'll be more than happy to give you the unlimited version if you send me your email address (in a private message).

yay, that would be great. unfortunately, it is still not working, but we are getting closer
when i start the new version, my car audio system switches briefly to calling mode and back to the tuner. But after that, all other sounds are still beeing routed to the standard speaker. I've attached the logcat

sebistan said:
yay, that would be great. unfortunately, it is still not working, but we are getting closer
when i start the new version, my car audio system switches briefly to calling mode and back to the tuner. But after that, all other sounds are still beeing routed to the standard speaker. I've attached the logcat
Click to expand...
Click to collapse
There is something odd going on, now that it successfully go into communication mode, it cannot track the audio focus. Your phone/ROM is acting way differently than some others.
I've attempted a fix (AudioBT-focus.apk), please test. I turn off commuication mode between audio, however I fear that it will take too long to switch on and you will lose the first seconds of audio when a message is playing.
I believe the TTS should work (even without the fix above) as it doesn't use audio focus. You can test by playing the sample in the settings.
Thanks!

After looking at Android source code I figured out the focus problem was fixed in JB Android 4.1.1 and up, so anyone running my app with ICS have the same problem. If you have success with my fix above and you don't see a significant delay when playing the audio I could publish a new version with a workaround for ICS, otherwise I will have no other choice than to put a notice regarding incompatibility with ICS.

the fix also does not work, the audio test is still coming from the music channel. the tts-service is not working either. in none of the test versions. i guess i have to wait for the jb update.

sebistan said:
the fix also does not work, the audio test is still coming from the music channel. the tts-service is not working either. in none of the test versions. i guess i have to wait for the jb update.
Click to expand...
Click to collapse
Please provide me with a logcat with the focus fix... There's probably something else going on. If you get the incoming call to come up during initialization, that's a good start.

sorry, i had a lot to do, could not make it any faster. Here is the logcat from my focus-fix-test, same procedure as last year

sebistan said:
sorry, i had a lot to do, could not make it any faster. Here is the logcat from my focus-fix-test, same procedure as last year
Click to expand...
Click to collapse
Hi seb,
I finally decided to install ICS on my phone. And indeed, it doesn't work well. I see that I cannot prevent the call mode to steal the audio focus in this Android version. For now I don't have any idea out of my head.
However, TTS works on my phone with ICS but not with the fix version. Make sure you turn off the AudioBT service when testing TTS. And maybe send me a logcat while testing the TTS (playing the "Listen to an example" in the TTS settings).

Hi I just wanted to tell you that I recently bought a dice mediabridge for my car and the only issue I was having and it was really bothering me was that when I was in Sirius satellite mode and my phone connected through Bluetooth that the phone calls would come right through but not the navigation if in use.This bothered me because it was a lack of integration that should be there. I searched the web for a few weeks pretty thoroughly and discovered that this was a very common issue reported in threads but no solution at all from anyone.The other day I came across your app and it is wonderful it does exactly what I was looking for and I'm sure once word gets out it will get alot of downloads. My only issues with it is that it does seem a little buggy which I totally understand.A few times the other day it wouldn't activate and I had to reboot my phone to get it to work I have a Verizon note 2. And also a few times the audio just came through as static and not understandable but after playing with it got it to work again.Is development still being worked on for the app? Thanks again.

bman12479 said:
Is development still being worked on for the app? Thanks again.
Click to expand...
Click to collapse
Hi bman.
First thanks for your comments, those are always appreciated. I wrote the app for myself after knowing that some older non-Android phones and iPhone had this capability. Thanks to Android, the API allows to route audio through Bluetooth SCO although only in very recent versions of Android. Hopefully someday it will be better supported by the OS.
My app has an unexpected success since the beginning, however sales have decreased in the last few weeks. About half the people downloading the trial have ICS 4.0 which is not very well supported except for the TTS engine and nothing I can do to fix it yet.
I've pretty much stopped doing updates as the app has become stable enough on most devices; however I don't have much feedback from users and am not aware of all the bugs and if they are fixable. I'm still ready to publish fix whenever one is found.
Cheers!

BT problems with nightly CM10.1 on xt926

XDA rules prevent me from posting this with the dev thread. It even prevents me from posting the link to the complete logcat... Tweeted it to dh.
Captured a logcat with interesting looking errors when A2DP is started and right before phone crashes/reboots:
Code:
I/audio_a2dp_hw( 310): start_audio_datapath: state 3
W/bt-btif ( 1358): bta_dm_rm_cback:1, status:7
W/bt-btif ( 1358): new conn_srvc id:18, app_id:1
E/GKI_LINUX( 1358): ##### ERROR : timer_thread: tick delayed > 5 slots (-78216086,-50000000) -- cpu overload ? #####
E/GKI_LINUX( 1358): ##### ERROR : timer_thread: tick delayed > 5 slots (-69620023,-50000000) -- cpu overload ? #####
E/GKI_LINUX( 1358): ##### ERROR : timer_thread: tick delayed > 5 slots (-62672060,-50000000) -- cpu overload ? #####
E/GKI_LINUX( 1358): ##### ERROR : timer_thread: tick delayed > 5 slots (-54503282,-50000000) -- cpu overload ? #####
Complete logcat here: pastebin.com / YyMiEq6c. Googling only brought me to a ulibc version. My C is a pretty rusty but it appears the timer isn't the problem but hopefully will point to where in the stack the panic is might be happening.
-Chris

Seems the today's nightly (20130724) solves the BT problems I was experiencing. The phone remains stable after connecting to my headphones as well as my car's headunit. I'm also able to use navigation and get audio alerts to play through BT. So far so good!
-Chris

cacack said:
Seems the today's nightly (20130724) solves the BT problems I was experiencing. The phone remains stable after connecting to my headphones as well as my car's headunit. I'm also able to use navigation and get audio alerts to play through BT. So far so good!
-Chris
Click to expand...
Click to collapse
@Chris, are you using Skrilax builds ?
Thanks

Harley_Rider said:
@Chris, are you using Skrilax builds ?
Thanks
Click to expand...
Click to collapse
I doubt it. I'm using skrilax's 07/25 nightly build and I just tested my Bluetooth headset. Caused the phone to lock up and reboot immediately.
He's probably on dhacker's.

killrhythm09 said:
I doubt it. I'm using skrilax's 07/25 nightly build and I just tested my Bluetooth headset. Caused the phone to lock up and reboot immediately.
He's probably on dhacker's.
Click to expand...
Click to collapse
This is so strange, I'm on skrilax's 07/17 build and don't have the BT problem. I tried dhacker's 07/24 build and had the BT problem, phone locked up about 3 min of using BT, then would not boot. Got stuck on Moto logo.
Thanks

So is the symptom of this bt problem that the phone completely locks up and reboots itself randomly when connected with bt? On cm 7/11 from epinter I have the problem sometimes and other times it works just fine, but when I do have the problem the phone won't be stable until I disable its bluetooth or the car's bluetooth; otherwise it just reboots again after a few minutes. My understanding is currently there is not a consistent fix? Do one of the 3 cm builds do better than the other 2?

empoweredh22 said:
So is the symptom of this bt problem that the phone completely locks up and reboots itself randomly when connected with bt? On cm 7/11 from epinter I have the problem sometimes and other times it works just fine, but when I do have the problem the phone won't be stable until I disable its bluetooth or the car's bluetooth; otherwise it just reboots again after a few minutes. My understanding is currently there is not a consistent fix? Do one of the 3 cm builds do better than the other 2?
Click to expand...
Click to collapse
There is a lot info in the developers forum about this, and there was a recent post stating they think they have a fix for the BT problem. I was on Skrilax 07/17 and didn't have the BT problem. I just updated to 07/25 and seem pretty solid; although some are having problems with it.
here is some good info on the different builds: http://forum.xda-developers.com/showthread.php?t=2344417

Harley_Rider said:
@Chris, are you using Skrilax builds ?
Click to expand...
Click to collapse
I'm using my own builds so I can generate changelogs and know the builds are in sync. I believe everyone (dhacker, epinter, skrilax and mine) are ultimately based from their repo (https://github.com/razrqcom-dev-team/). There were a few posts that eluded to slight differences as each dev might experiment but I haven't found any proof of this. When I get a moment I will try to pull the build manifest from his build and compare.
-Chris

Harley_Rider said:
There is a lot info in the developers forum about this, and there was a recent post stating they think they have a fix for the BT problem. I was on Skrilax 07/17 and didn't have the BT problem. I just updated to 07/25 and seem pretty solid; although some are having problems with it.
Click to expand...
Click to collapse
For me, it seems the earlier builds were much more stable with repects to BT but suffered from issues when running nav, docked and in landscape orientation. The 7/24 build seems to heading in the right direction but I still managed to crash over the weekend, so its not perfect yet. I'm still learning how all the pieces fit, but in the 7/24 build there were changes to ALSA (Linux's sound subsystem) upstream in CM so that might have been what helped. Since then there hasn't been anything major until the build last night which merged in the latest kernel, 3.0.88. But even that doesn't seem to have any commits that deal with BT or audio.
epinter's post here states him and dhacker recent efforts have been on CM 10.2 which explain why the commits have been pretty thin lately.
-Chris

CM 11 BT audio

Hi guys I have been using CM 11 on my Galaxy Note 8.0 for some time, since I prefer the stock UI to TouchWiz. It is also convenient to be able to mount an NTFS formatted external drive w/o any third party solution. However, I noticed that BT audio skips quite a bit to the point where it would make listening to music through my BT adapter or headphones annoying or unbearable. The issue appears only when the screen is locked (no skipping occurs when the screen is on) Has anyone else encountered this issue?
I believe I found a way to fix this issue. I basically enabled development settings by tapping build number a couple times, then I went into performance and changed the governor from pegasusq to ondemand. This appears to have resolved the BT audio skipping. If anyone else has experienced this problem, I would like for them to try this quick fix and let me know if it works!
EDIT - the performance governor also seems to resolve the BT issue while at the same time improving game performance.
The thread was moved to an incorrect device forum. This only refers to the GT-N5110 - Galaxy Note 8.0 WiFi. I let a forum administrator know.

There are 3 CM11 ROMs for the 3 variants of the Note 8.0. Which one are you referring to?

CafeKampuchia said:
There are 3 CM11 ROMs for the 3 variants of the Note 8.0. Which one are you referring to?
Click to expand...
Click to collapse
My bad for not specifying. I was referring to the N5110

[Q] Relay can't hear input from any bluetooth device, LAME

Am I the only Relay user having trouble using voice command thru bluetooth?
I'm running Cyanogenmod 10.2, on tmobile, and using google voice/talktone for calls.
On both bluetooth car kits I've tried (Blueant Commute and Kinivo BT450), things work fine (music, navigation, reading incoming texts, taking calls) until I try to voice command the phone thru the BT unit.
I've tried:
~ google now, voice search, voice dialer
~ turning on talkback (hate that constant reading of each page, AGHH!)
~ blueant app (does F%&&% all)
~ every tip on both gear's support pages
~ tmobile's support page (HA!)
~ even reverted back to stock (in case it was CM), and IT STILL SUCKED MY @**#&#$
I am ready to throw this POS phone against the nearest underpass..... if someone can solve this, I will send you thanks, and a present. Seriously.
(I appreciate all advice, but feedback from those who have this prob, or solved this prob are the most helpful. THX)

Epiclectic said:
Am I the only Relay user having trouble using voice command thru bluetooth?
I'm running Cyanogenmod 10.2, on tmobile, and using google voice/talktone for calls.
On both bluetooth car kits I've tried (Blueant Commute and Kinivo BT450), things work fine (music, navigation, reading incoming texts, taking calls) until I try to voice command the phone thru the BT unit.
I've tried:
~ google now, voice search, voice dialer
~ turning on talkback (hate that constant reading of each page, AGHH!)
~ blueant app (does F%&&% all)
~ every tip on both gear's support pages
~ tmobile's support page (HA!)
~ even reverted back to stock (in case it was CM), and IT STILL SUCKED MY @**#&#$
I am ready to throw this POS phone against the nearest underpass..... if someone can solve this, I will send you thanks, and a present. Seriously.
(I appreciate all advice, but feedback from those who have this prob, or solved this prob are the most helpful. THX)
Click to expand...
Click to collapse
We (TeamApexQ) have thrown ourselves against this wall a few times, to no avail. This is a known issue in our sound configuration. It really comes out of the fact that getting this to work would involve having a bluetooth device work in two separate profiles (A2DP for output, SCO for input) at once which is not a trivial or easy thing to implement. What we need are more logs of this issue, and probably some direct communication in IRC with a couple of testers to bang this one out.

Magamo said:
We (TeamApexQ) have thrown ourselves against this wall a few times, to no avail. This is a known issue in our sound configuration. It really comes out of the fact that getting this to work would involve having a bluetooth device work in two separate profiles (A2DP for output, SCO for input) at once which is not a trivial or easy thing to implement. What we need are more logs of this issue, and probably some direct communication in IRC with a couple of testers to bang this one out.
Click to expand...
Click to collapse
OK, so I'm not a retard. hehe, thanks for that, I was going crazy thinking it must be some setting I overlooked. Strange though, it still didn't work when I reverted to stock.... no? (THAT must be something I am doing wrong...)
After 6 months enjoying CM10 (big thumbs up for TeamApexQ!!), I can't bear the thought of trying to suffer thru stock rom....what's the closest rom to CM that has good bluetooth integration..?

Epiclectic said:
OK, so I'm not a retard. hehe, thanks for that, I was going crazy thinking it must be some setting I overlooked. Strange though, it still didn't work when I reverted to stock.... no? (THAT must be something I am doing wrong...)
After 6 months enjoying CM10 (big thumbs up for TeamApexQ!!), I can't bear the thought of trying to suffer thru stock rom....what's the closest rom to CM that has good bluetooth integration..?
Click to expand...
Click to collapse
Now, someone can correct me if I am wrong on this, but I believe all of the community images are using the same sound configuration that TeamApexQ has been developing since CM 10.1, so... None of them. Again, with some community assistance, logcats, testing, and patience we can fix it.

Magamo said:
Now, someone can correct me if I am wrong on this, but I believe all of the community images are using the same sound configuration that TeamApexQ has been developing since CM 10.1, so... None of them. Again, with some community assistance, logcats, testing, and patience we can fix it.
Click to expand...
Click to collapse
I thought I heard CM9 had working BT... if not, what can I do to help? how do I capture and send you the logs?

Epiclectic said:
I thought I heard CM9 had working BT... if not, what can I do to help? how do I capture and send you the logs?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1726238
Please, please, please issue a 'logcat -c' before doing this proceedure to capture a log of the issue, to clear the log, and to avoid having us to sift through every log your phone has taken since reboot.
Also, send us the contents of the 'dmesg' command after encountering the issue, just to rule out anything on the kernel side.

Mi4, CM13 echo in calls

Hello,
I have a Mi4 with TWRP and CM13, latest nightly from today, but the problem also occured on the nightlies before.
During calls the other party complains about hearing himself. On the internet I found ideas like:
- disabling the "OK Google"-recognition on every screen (although this held true for Skype-video-calls)
- lowering in-call volume
I did not find any other ideas. Do you have an idea?
EDIT: I also tried two things:
1. entering the following things -> no changes
su
setprop persist.audio.fluence.mode false
setprop persist.audio.handset.mic analog
reboot
2. disabling the mic while calling -> success, the other party has no echo anymore
This of course is no useful solution, as normally a mic is needed for calling.

I'm facing the same problem. Did you find a solution?

nope

Same here.
Posted this in another forum. After trying a few things it appears that microphone is relaying sound from the speaker back to the caller. It's like the microphone is too sensitive so it picks up the callers voice from the speaker.

yes, it is definitely a problem with the mic. as soon as you deactivate it, the other party has no echo anymore.
EDIT: I wonder if this is the case, because in the native MIUI there was a noise-suppression and dual-mic option which may be good for avoiding this problem. I highly doubt CM will implement this specifically for this phone. Right now I am always calling with a headset which works fine.
EDIT: Headset isn't working anymore too. Callers say I am way too silent. Soundrecorder App confirms that mic sensitivity is too low.

I think the solution might be here, thought I am not able to understand completley what they are doing there: https://jira.cyanogenmod.org/browse/NIGHTLIES-2619

It should be solved after installing the next nightly:
https://www.cmxlog.com/13/cancro/
http://review.cyanogenmod.org/#/c/139932/
Could someone pls give a feedback after installing it? I switched from nightly to snapshot-channel and therefore am not able to check.

hsquare said:
It should be solved after installing the next nightly:
https://www.cmxlog.com/13/cancro/
http://review.cyanogenmod.org/#/c/139932/
Could someone pls give a feedback after installing it? I switched from nightly to snapshot-channel and therefore am not able to check.
Click to expand...
Click to collapse
Is the problem still existing with the new snapshot release?

I'd like to know that too! I switched to nightlies now and some people I talked with say it's still there, some don't.

hsquare said:
I'd like to know that too! I switched to nightlies now and some people I talked with say it's still there, some don't.
Click to expand...
Click to collapse
I heard from some guys using latest Snapshot that the echo is gone but when they make a hands free call, the speaker and mic is very quiet/ low. So probably the problem is not totally fixed right now.

I'm on Nightly 13/04 right now, no echo at all but the phone is turning of during call (after I tried to turn on the display). Is there another behaviour on the Nightly you are using?