Bluetooth Error

If you are not a developer for Android, this app probably isn't for you. It's written do very basic operations and observe Androids behavior. Some phones have... issues.... and this tool aims to demonstration you are not an idiot.

It's open source. It doesn't spy on you. It doesn't show you adds. And the source code is here: https://bitbucket.org/millibit/eu.millibit.bluetootherror/src. Developers are more than welcome to contribute.

For now you have a number of buttons.

1. The first row you can use to start a classic BT scan. Only BLE units are shown

2. The second row starts a BLE scan. I've noticed this locks up Bluetooth a Huawei P8 Lite for 250 sconds. In that time it just keeps scanning whatever you do.

3. The third row is used to turn the BT adaptor off for a while. It AUTOMATICALLY TURNS BLUETOOTH ON AGAIN. Just to be clear. :-)

4. The forth row can be used to connect to a selected device.

When scanning for devices the devices found are listed below all the buttons. After scanning you can select one device. A selected device is marked with a gray start. When the phone is connected to that device the star turns golden.

You can use this tool to demonstrate a known problem with Android:

1. Scan for devices

2. After scanning is complete select a BLE device with RANDOM address. With random is meant random in a Bluetooth context.

3. Check you can connect to the device. Disconnect. Do this a couple of times to play around.

4. Disable the BT adaptor for a few seconds. Then enable it again. You can do this manually or by pressing the "Cycle" button.

5. On some phones, e.g. Huawei Nexus 6P running Android 8.1.0 you can't connect anymore. You need to do a scan again before connecting.

This problem is raised and answered here: https://stackoverflow.com/questions/52093667/how-to-make-android-connect-after-the-bluetooth-adapter-has-been-disabled-reen

It is the intention this app shall morph into an automated test utility that demonstrates the misbehavior of Android and uploads the test results to a public database. Other developers can then use the database to check whether a particular phone has a problem.

Everybody is very welcome to contribute, whether it be code, corrections, examples of incorrect behavior, documentation, suggestions, beer, pizza or whatever.