Looks great, too bad it comes up as incompatible with my phone.
Must be an ics app
Tasker PluginIt would be great if you would develop a stand-alone Tasker plugin that would allow a Tasker user to force a connection to a Bluetooth device. No other features of A2DP Volume, such as location detection, automatic volume control, etc., would be needed since these could be handled by Tasker.This would have the advantage of eliminating the need for the A2DP Volume service to be running all the time and occupying memory, because Tasker is already running all the time and could detect the conditions a user wants to act on.
One issue however: In order for any app to receive an intent (like from Tasker) it must have an activity running. So, the service will still need to be running anyway to use any features of A2DP Volume. So you might as well use A2DP Volume to handle all of those things anyway.I presume you are using Tasker for many other things too. In that case it would be better to submit an issue to the Tasker team to just implement the Bluetooth force connect like I have done. A2DP Volume is open source so as long as they follow the OS license agreement they can just use the functions from my app in Tasker.
I see Tasker is not free or open source. Too bad. So, they cannot directly implement my code. They could still implement similar functionality though.
I did start another app called A2DP Connect. http://code.google.com/p/a2dp-connect/It would make far more sense to integrate that with Tasker. It is just a widget that does the force connect. Nothing more. If you just want the force connect, then this issue needs to move to the A2DP Connect issues list to be worked. That said, I have not worked on that app in quite a while. However, another developer did get it working recently and he said he would push the code and APK. Lets move this issue to A2DP Connect for implementation.
I've been ignoring this thread since I don't use bluetooth for anything. But I may have a use for it soon. Once paired, don't bluetooth device connect automatically when within range? Obviously I'm missing something.
Can you autoconnect during statup?
Does your car BT have different addresses or ID's for the two connection types which A2DP connect can recognize? If not, is it a separate app that you have on your phone to ask how you want to connect?
Once connected though, it is not entirely clear to me why you are turning bluetooth off when the phone is idle unless you are concerned with battery usage. Even that should be fairly minimal if not transmitting any data.
What's your goal with those profiles?
Why don't you leave bluetooth on while you're in the car?
Because I forget to switch it on and then I forget to switch it off when I'm out of the car..............if I have it on constantly it just sucks my battery.
I am the developer of A2DP Volume and I would be happy to integrate with Tasker. Just add it to my issues list here: http://code.google.com/p/a2dpvolume/issues/list
I am busy with some unrelated stuff for the next month or so but when I get back to working on this app I work the issues in priority so launch an issue to integrate with Tasker and star that issue so i can see the interest level.
On Tuesday, July 17, 2012 10:40:10 AM UTC-5, baudi wrote:Bluetooth auto connect doesn't work on my Galaxy S3 with ICS 4.004.BUT, I found something that does work: A2DP VolumeIt doesn't have a Tasker Plugin, but it does have settings that allow you to specify that the A2DP output should automatically connect when, for example, you enter Car Mode.Seems to work fine for my phone, when nothing else I tried would work.Thanks to Ada in this thread for pointing the way.