2 check boxes.
One says; Phone. Use for phone audio. (this is the one I want to
change)
The other; Media. Use for media audio.
The vehicle BT device only has the the Phone check box.
Thanks for digging!
Definately looks like ConnectSpecificProfilesActivity is where I want
to be.
Interesting here
/**
* Gets the summary that describes when checked, it will become a
preferred profile.
*
* @param profile The profile to get the summary for.
* @return The summary.
*/
Wonder what might be contained in @param & if there is anyway to
manually build a set of them with different options that Tasker could
then switch out depending on which options you want?
On Oct 22, 1:44 am, Matthieu Berthomé <
matthieu.berth...@gmail.com>
wrote:
> each profile is associated with a given profilemanager,HeadsetProfileManager,
> A2dpProfileManager, etc.
> When you connect your BT headset, what do you see in the profile settings ?
> I'd say A2DP corresponds to media audio and Headset to Phone audio, but I'm
> not sure.
> For A2DP:
> A2dpProfileManager.connect launches a mService.connectSink(device) where
> mService is a BluetothA2DP object, which interfaces with the bluetoothA2DP
> private system API. The interface gets written on. So the trick is to
> initiate this interface writing from Tasker, or interface with the private
> system API.
> Interface with the private system API can be hacked into a user app with
> some difficulties, but apparently doable (I've seen some code for accessing
> hidden private GPS API). SL4A might have some stuff to write to interfaces
> or interface with the system API.
> System API is described therehttp://
www.google.com/codesearch#cZwlSNS7aEw/frameworks/base/core/jav...