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!
Related
I've owned my T-Mobile HTC Sensation 4G for about 10 days and I've noticed that the Google Maps Navigation does not completely speak the turn by turn directions through my bluetooth headset (Jawbone Icon) when connected. For example, if a diretion is supposed to be: "Take Exit 148 in 1,000 feet" all that I will hear is about 1/2 the sentence: "in 1,000 ft". This happens all the time when the Sensation 4G is connected via bluetooth. It happened to me the 1st time I used it and it happens all the time at every turn voice prompt.
When the navigation is through the speaker phone, it speaks the complete directions just fine. However, I use my bluetooth most of the time while driving because in Washington State it is illegal to drive while talking on your cell phone, unless you have a bluetooth.
Is this issue just with the HTC Sensation 4G? My previous phone was a Samsung Galaxy S 4G and the Google Maps Navigiation directions worked fine with my same Bluetooth headset. I've tried a phone restore and I also updated the Google Maps app (6/30/11) and I am still experiencing these turn by turn bugs via bluetooth. Anybody else experience this or can anyone please test the Google Maps Navigation with their headset?
Out of curiosity, is it the same voice? You may want to try re-installing the text to speak app.
The device is establishing an a2dp connection which takes a second or two. This causes the start of the directions to be missed. This is designed to save power by only connecting when audio is played. One workaround is to play music through Bluetooth from the player in the background. Music will be silenced while the directions are announced.
Sent from my HTC Sensation Z710e using XDA App
DeezNotes said:
Out of curiosity, is it the same voice? You may want to try re-installing the text to speak app.
Click to expand...
Click to collapse
What he said. By default it appears to want to use the telenav lady voice. I had to install/update the e-speak app for it to work properly.
familyhousing said:
The device is establishing an a2dp connection which takes a second or two. This causes the start of the directions to be missed. This is designed to save power by only connecting when audio is played. One workaround is to play music through Bluetooth from the player in the background. Music will be silenced while the directions are announced.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Thanks for the reply. I did notice that when I played music through Pandora that the Turn by Turn directions did speak just fine. I just find it annoying that the start of the directions are missed on the Sensation 4G when it worked just fine on my Galaxy S 4G.
The voice I hear is the same and it is the lady.
As for the post that said to try and reinstall the TTS. I only have Pico TTS on my phone and I couldn't find the option to uninstall it. I looked in settings & applications and also in the Market under My app, but it doesn't show up. I'll give eSpeak a try tonight on my way home to see if that works.
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.
So I'm not sure if this is an issue in the Doggcatcher app or not. So here's my setup and details.
Nexus 5 completely stock 6.0. Phone has never been rooted, bought new from Play store. Bootloader is locked.
I am using an LG HBS-730 bluetooth stereo headset
I have 2 numbers on this phone, one is the carrier number (T-Mobile), the other is a Google Voice number that is managed by the most recent version of Hangouts with the Hangouts dialer.
Twice today, I have been listening to a podcast using the Doggcatcher app when an incoming call from my Google Voice number happens through Hangouts. The Doggcatcher app will pause, I will push the call answer button on the headset, and the phone call will begin but the podcast will resume playback at the same time. I can pause the podcast via the app controls on the phone and the call will continue as normal. The caller can hear the podcast as well.
Not sure if it's the app or the OS/bluetooth causing this but it's really confusing. I reported the issue with the developers of the Doggcatcher app, but I haven't posted it to Google yet.
Any ideas?
Yaz75 said:
So I'm not sure if this is an issue in the Doggcatcher app or not. So here's my setup and details.
Nexus 5 completely stock 6.0. Phone has never been rooted, bought new from Play store. Bootloader is locked.
I am using an LG HBS-730 bluetooth stereo headset
I have 2 numbers on this phone, one is the carrier number (T-Mobile), the other is a Google Voice number that is managed by the most recent version of Hangouts with the Hangouts dialer.
Twice today, I have been listening to a podcast using the Doggcatcher app when an incoming call from my Google Voice number happens through Hangouts. The Doggcatcher app will pause, I will push the call answer button on the headset, and the phone call will begin but the podcast will resume playback at the same time. I can pause the podcast via the app controls on the phone and the call will continue as normal. The caller can hear the podcast as well.
Not sure if it's the app or the OS/bluetooth causing this but it's really confusing. I reported the issue with the developers of the Doggcatcher app, but I haven't posted it to Google yet.
Any ideas?
Click to expand...
Click to collapse
I have a slightly different problem with bluetooth, after update to 6.0 on my nexus 5 (stock) my polar running watch can't sync with the companion app. I can see the watch listed on blue tooth settings but when i click pair nothing happens.. Not sure if it's an app of OS /bluetooth issue.
I have an even more weird situation.
Ever since I updated my nexus 5 to android M, I started to experience google now voice input on android wear showing frequent disconnected in car, and I am streaming music at the same time.
Weird thing is this behavior only happens in car. If I try the voice input without phone BT connected to my car, everything is fast and fine.
I'm not sure what triggered this and I have done several experiments already.
- Even if I pause streaming music to car BT, Google now voice input on wear still shows disconnected in car.
- Weird thing is I can still use Google translate voice input on wear, while streaming music to car BT.
- My wear on Google now used to be able to recognize chinese (I think it's because I add chinese in google now setting on my phone). Now it only recognize english while google now on my phone takes chinese/english mixed. I set english as primary language and chinese as secondary on phone google now. In Google translate wear app, I can speak both english and chinese.
- I have reset/ connect/ disconnect wear multiple times. End result is still the same. Google now voice input on wear shows disconnected in car.
- Add Android Wear app to ignore list of battery optimization seems to make no difference.
Hmmm....strange stuff indeed. Hopefully someone smarter than myself can take a look at the issues. I know that I never had this problem on the final version of 5.1.1.
guavajuice said:
I have a slightly different problem with bluetooth, after update to 6.0 on my nexus 5 (stock) my polar running watch can't sync with the companion app. I can see the watch listed on blue tooth settings but when i click pair nothing happens.. Not sure if it's an app of OS /bluetooth issue.
Click to expand...
Click to collapse
I solve my syncing issue between my watch and nexus 5 , it turns out i have to have my location service on along with bluetooth.
Source:
"If you are running OS 6.0 (Marshmallow), please note that Google has changed the permissions required for Bluetooth syncing. You must turn on location services to sync your tracker (Settings > Location). For more information about the latest Google permission requirements, see Google's Android 6.0 Changes document. "
http://help.fitbit.com/articles/en_...s-not-syncing-with-the-Fitbit-app-for-Android
The Problem: On many non-Samsung phones, all calls, even when answered on the phone itself, get sent to the watch's speakerphone, requiring the user to manually switch the sound back to the handset every time a phone call happens. As a side problem, the watch conflicts with other Bluetooth devices capable of of being used for calls, like car stereos and headsets. Several threads on xda and elsewhere discuss these issues; however, the only solution posted is to disable the "Phone Audio" profile of the watch in settings. This is sub-optimal because it completely disables the ability to use the watch as a phone speaker.
The Solution: I have put together a series of Tasker profiles and tasks that utilize the BlueTask plugin to control the connection of the Gear S3. A convenient detail about BlueTask's disconnection method is that it only seems to affect the "Phone Audio" component of the Gear S3, leaving all other functionality untouched during a call. I use the proximity sensor to determine whether or not the call is being made/answered on the phone itself vs the watch. The assumption is that if you leave you phone in your pocket, bag, or face down on the desk, then you answered the call via the watch. I understand this is not a perfect method for determining which device is answering the call, but it works pretty well in my testing. In addition, an exception is made for when a wired headset is hooked up to the phone, as one may leave their phone in their pocket while answering using such a headset. Finally, an additional profile I call the "Car profile" will automatically disconnect the watch and disable its Tasker profiles while connected to specified Bluetooth devices like a car stereo, Bluetooth headsets, etc.
Setup:
Re-enable "Phone Audio" for Gear S3 if you previously disabled it (Settings>Bluetooth>Gear S3)
Install Tasker (if you haven't already)
Install BlueTask
Go to Tasker>Preferences>UI>Beginner Mode. Disable it (if it is not disabled already).
Go to Tasker>Preferences>Monitor>Display Off Monitoring>Proximity Sensor. Set it to "Yes"
Download the Tasker project attached to this post to your phone
Import the project into Tasker (Press and hold the home tab in the bottom left corner of tasker and then click Import)
Enter the new "Bluetooth" project and open "Car Profile" in "Profiles"
Delete the Dummy MAC address in the Profile and replace it with the MAC addresses of any car stereos and/or bluetooth headsets you use with your phone. If you have multiple of such devices, separate each address with a "/" (the magnifier glass icon does this for you). If you have no such devices, feel free to disable or delete this profile.
Open "Disconnect Gear S3" in "Tasks"
Open the "BT Connection" action
Replace the dummy information with your Gear S3's Name and MAC address
Repeat steps 10, 11, and 12 for the "Connect Gear S3", "Car Mode", and "Exit Car Mode" tasks.
Complete!
Let me know if this works for you. Also, suggestions for how this project could be improved are welcome.
Its works fine on #LGV20 so no need for this fix.
Sent from my LG-H990 using Tapatalk
I've downloaded the project to my phone but when I launch tasker and try to import the profile I can't find the file, even though I can see it using a file explorer. I've changed the.Prj to .prf and Tasker sees it but when I try to import it it gives me an error that says the for contains multiple projects.
Any help would be appreciated, thank you
OneRealDaniel said:
I've downloaded the project to my phone but when I launch tasker and try to import the profile I can't find the file, even though I can see it using a file explorer. I've changed the.Prj to .prf and Tasker sees it but when I try to import it it gives me an error that says the for contains multiple projects.
Any help would be appreciated, thank you
Click to expand...
Click to collapse
Is it downloading as a .prj or .prj.xml ? It should be the latter. If it isn't, rename it to have a .prj.xml extension. Otherwise, not really sure what is going on. I haven't had any trouble importing Tasker projects in the past.
Beginner mode
MehStrongBadMeh said:
Is it downloading as a .prj or .prj.xml ? It should be the latter. If it isn't, rename it to have a .prj.xml extension. Otherwise, not really sure what is going on. I haven't had any trouble importing Tasker projects in the past.
Click to expand...
Click to collapse
Thanks for getting back to me. Im new with Tasker, the only reason I bought it was because of this issue and because I saw your post. All I needed to do was disable beginner mode in preferences, under Ui, and the house icon appeared, from there it was very simple to follow the instructions. Thank you for sharing your solution to this very inconvenient problem.
Once I get to test it ill make sure to give you feedback.
OneRealDaniel said:
Thanks for getting back to me. Im new with Tasker, the only reason I bought it was because of this issue and because I saw your post. All I needed to do was disable beginner mode in preferences, under Ui, and the house icon appeared, from there it was very simple to follow the instructions. Thank you for sharing your solution to this very inconvenient problem.
Once I get to test it ill make sure to give you feedback.
Click to expand...
Click to collapse
Thanks for letting me know about that, I'll add that to the steps.
Hi i downloaded the App but seems it doesnt work for me. I set it up according your instructions but still no change. But i háve an idea i spoted that when i make call from phone i háve an option to choose which audio divice to use if i select my phone it doest work but when someone picks up and then i select it it Works. So i am thinking is there a way to make this automatic? That once someone picks up a call that it select this option right after.
Added 2 screenshots one from the Standard run and one of the option to select an audio divice when making a call.
Thx for any help.
Edit: Works Now thx alot i had an incorrect name set for the device... i will test it if it works always but so far so good. thx alot
Jafabibe said:
But i háve an idea i spoted that when i make call from phone i háve an option to choose which audio divice to use if i select my phone it doest work but when someone picks up and then i select it it Works. So i am thinking is there a way to make this automatic?
Click to expand...
Click to collapse
I wanted to use this system as part of the automation workflow. The problem is that, when dialing someone, it switches the audio output when they pickup, instead of during Phone Offhook (the moment you hit dial). As a result, I can't detect the actual moment the audio device is switched, so I disable the watch audio entirely to prevent it from from happening.
Hello guys. I have non rooted stock nexus 5x. I have followed steps from first post but I always get error (attached).
Please any ideas what's going on?
Edit: Sorry guys. Please ignore it. I have added wifi mac for gear instead of bluetooth mac. I'm going to test it.
I am trying to use this for my phone.
I opened the prj.xml in notepad, edited my MAC address and name of bluetooth for car and gear s3.
When i press the play button in the bottom left corner i get the error non-existing plug-in code type Action: 704475526.
Any idea what i can do?
Thanks.
GabrielAK89 said:
I am trying to use this for my phone.
I opened the prj.xml in notepad, edited my MAC address and name of bluetooth for car and gear s3.
When i press the play button in the bottom left corner i get the error non-existing plug-in code type Action: 704475526.
Any idea what i can do?
Thanks.
Click to expand...
Click to collapse
Probably install Bluetask as per the instructions.
I solved the problem using Macrodroid.
GabrielAK89 said:
I solved the problem using Macrodroid.
Click to expand...
Click to collapse
Can you tell us, the other users, what you did to get it solved ?
As we are in a forum, others can benefit using your solution.
So please share.
I just got my Nokia 8 Sirocco, and I thought it was bad BT performance on my new device, when it probably is my Gear screwing me over. Thank you for this Tasker-project, I've just finished setting it up, and l am looking forward to seeing is effect!
Unfortunately, the macrodroid way don't work anymore for me.
Don't know why.
I am retrying the Tasker way. I get the error:
12.53.42/E FIRE PLUGIN: Connection / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 8 bundle keys
12.53.42/E Connection: plugin comp: com.balda.bluetask/com.balda.bluetask.receivers.FireReceiver
12.53.42/E add wait type Plugin1 time 60
12.53.42/E add wait type Plugin1 done
12.53.42/E add wait task
12.53.42/E Error: 2
Does anyone know what it means?
LE: When i am in the car i don't get this error. Everything seems to be with green dot. But the magic never happen. The tusker is not triggered. Should i make other settings to work?
I also tryed Bluetooth auto connect. Bad luck with that also.
Hi!
I've been meddling with Tasker for the past few days and discovered that choosing the Headset profile to connect to and disconnect from the Gear S3 works better for me.
I've started out with MehStrongBadMeh's guide and tasker xml file (many thanks by the way!), but found out my phone was unable to connect the Gear S3. It disconnected OK to connect the car bluetooth, but would not reconnect Gear S3. Running the task also gave errors as reported by few others on this thread.
But everything seems to be in order when Headset profile is selected for Gear S3. Will test out extensively and will report back if I need to change anything else.
I believe I created that xml was created before bluetask handled specific profiles, hence the need to explicitly set headset now. I don't actually use this profile anymore, as calls started being routed properly when I updated my HTC 10 to Oreo (and continue to be routed properly on my OnePlus 6).
Just wanted to say a massive thank you for this. I have just bought the Galaxy Watch and have a Samsung S6 Edge with lineageos. I was having the issue where everything was being rooted through the watch. Your guide has got this working as it was designed.
My notes would be for anyone trying this - do not change the device name as it doesn't seem to work (i am guessing this is referenced in other profiles) - just change the mac address to your watches Bluetooth mac address.
Any update on this I still get an Error 2 and it never seems to connect on its own to my car audio
Solved with MacroDroid:
Trigger: Call active (any contact)
Action: Kill application Galaxy Wearable
Constraints: Trigger fired Call active
AND In call
App Alive BG Galaxy Wearable
Hello,
I just took my first video using the phone today, then I noticed audio is not recorded. I tried several times, both high-res and 3D audio, but there was no audio. Checked both on my phone and my laptop. I even installed Google Camera app, but the video from there still didn't have audio.
Then I used Voice Recorder app to record audio, and interestingly it did not record audio either. 3rd party voice recorder app didn't record audio either!
There is no problem when I call, my voice is heard clearly from the other phone. I checked the permissions of the camera apps / recorder apps, and microphone is ticked.
What could be the problem? This is very frustrating. Please help!
EDIT:
I just installed a 3rd party camera app, took a video, and the app gave a video with audio. Then I tried stock camera app, which also gave audio. Then voice recorder app, which also gave audio. It seems to work now. I didn't do anything special, didn't reboot the phone, etc. I have no idea what happened...
It is quite possible that one of the apps didn't release the connection to the microphone "for whatever reason". If you encounter problems with hardware the first option is reboot. The reason for this is all of the external and internal connections to hardware get reset. Most apps rely on the drivers within the os and sometimes those connections don't get closed because of crap coding or bugs in the os itself.
Most phones will have a hidden self test menu. It is worth a Google to find that code and test the hardware when things go a bit wierd.
Hope that helps.
shivadow said:
It is quite possible that one of the apps didn't release the connection to the microphone "for whatever reason". If you encounter problems with hardware the first option is reboot. The reason for this is all of the external and internal connections to hardware get reset. Most apps rely on the drivers within the os and sometimes those connections don't get closed because of crap coding or bugs in the os itself.
Most phones will have a hidden self test menu. It is worth a Google to find that code and test the hardware when things go a bit wierd.
Hope that helps.
Click to expand...
Click to collapse
Now that I thought about it again, I think you are right. One of my apps might have been in love with the microphone so that it did not allow other apps to use the mic. I have no idea which app had that kind of love, but anyway, yeah thank you for the comment!