add auto_connect for android

[tomaszduda23]

Pull Request Guidelines for Bleak

Before you submit a pull request, check that it meets these guidelines:

1. If the pull request adds functionality, the docs should be updated.
2. Modify the CHANGELOG.rst, describing your changes as is specified by the
   guidelines in that document.
3. The pull request should work for Python 3.8+ on the following platforms:
   • Windows 10, version 16299 (Fall Creators Update) and greater
   • Linux distributions with BlueZ >= 5.43
   • OS X / macOS >= 10.11
4. Squash all your commits on your PR branch, if the commits are not solving
   different problems and you are committing them in the same PR. In that case,
   consider making several PRs instead.
5. Feel free to add your name as a contributor to the AUTHORS.rst file!

[dlech]

Can you describe the intended use for this feature? Typically, with Bleak, we always scan and then connect.

[tomaszduda23]

There are restriction on scanning in android. It works each time when device is awake. When screen is off it fails in active and passive mode. Without this connect fails randomly when screen is off.

[dlech]

I'm not sure I fully understand. You are saying that the restriction is with scanning, but the change is in BleakClient, not BleakScanner.

[tomaszduda23]

I'm sorry form mixing this up. Those are two separate things.

1. If you know device address already it is possible to connect without scanning.
   a) E.g. you can have stored last device which was used in settings. Than you can connect without scanning.
   b) Or you can scan when screen is on and connect from time to time when screan is off. When using auto_connect = True android blocks until device is available.
2. BleakScanner.discovery fails if scan is done from service when screen is off. It is not related to this PR. I just mention this for reference. That might be caused
   https://developer.android.com/reference/android/bluetooth/le/ScanSettings#SCAN_MODE_LOW_POWER

[dlech]

1. When using auto_connect = True android blocks until device is available.

This is how all other OSes work, so it sounds like we want auto_connect = True all of the time (with a timeout). This way, Bleak works the same on all platforms.

[tomaszduda23]

It seems that both are needed depending on remote device configuration https://stackoverflow.com/questions/40156699/which-correct-flag-of-autoconnect-in-connectgatt-of-ble. If remote device do not advertise it would never be available I guess. Doc says.

autoConnect
boolean: Whether to directly connect to the remote device (false)
or to automatically connect as soon as the remote device becomes available (true).

My understanding is that true waits for advertisement from remote. false try to immediately connect to device which was "bonded" already. I can be wrong though.

[tomaszduda23]

It seems to go back to bluez/bluez@0f40779#diff-f936cc254469fe4d4a2cbca5892ebaeebe3e03fd1e7bfdc86d8a998477b20bbcR1946