Using default sound handling on Android rather than manual functions

[shamilovtim]

Current functionality in the plugin looks to be that there have been devs who contributed functions to manually route audio to bluetooth, manually route to speakers or elsewhere. However, in a standard Android app which uses audio this shouldn't be necessary. The end user configures in their OS where the sound goes and that's where the app should route the sound. It shouldn't require a manual bluetooth button, manual headphones or speaker button, the user should be able to handle this on the OS side. Is there a way to add a setting so the plugin uses the default sound handling and output device of the OS so we aren't using buttons to control the sound inside plugin? If the user has a bluetooth device connected the sound should be going there automatically.

Bug which inspired this issue: sound does not go to to bluetooth devices automatically. It seems something is preventing it?

[slycoder]

If you were to remove all the calls to setSpeakerPhoneOn would that solve the problem? AFAIK that is the only place in which we might be setting the route....

[owenadley]

@shamilovtim did you get bluetooth working without manual intervention? Having the same issue.

[shamilovtim]

Nope. I thought about making a PR but had no time