[Windows] Crash on writeValue

[ivs]

Hi! This code gives me sigterm on Windows:

void handleConnection(String deviceId, BlueConnectionState state) {
    d.log('handleConnection ' + state.value);
    QuickBlue.discoverServices(deviceId);
    QuickBlue.setNotifiable(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
        BleInputProperty.notification);
    QuickBlue.writeValue(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
        Uint8List.fromList(key_cmd + key), BleOutputProperty.withResponse);
  }

  void handleService(String deviceId, String serviceId) {
    d.log('handleService ' + serviceId);
  }

  void handleValue(String deviceId, String characteristicId, Uint8List value) {
    d.log('handleValue ' + characteristicId);
  }

  @override
  void initState() {
    super.initState();
    QuickBlue.setConnectionHandler(handleConnection);
    QuickBlue.setServiceHandler(handleService);
    QuickBlue.setValueHandler(handleValue);

    QuickBlue.scanResultStream.listen((result) {
      d.log('onScanResult ' + result.name);

      if (result.name == "Mi Band 3" && !bandFound) {
        bandFound = true;

        d.log('onScanResult ' + result.name);
        QuickBlue.stopScan();
        QuickBlue.connect(result.deviceId);
      }
    });

    QuickBlue.startScan();
  }

The output:

Launching lib\main.dart on Windows in debug mode...
lib\main.dart:1
Connecting to VM Service at w[s://127.0.0.1:56503]()/sOU5DQmnXDg=/ws
flutter: startScan invokeMethod success
4[log] onScanResult [Monitor] Samsung M7 (32)
[log] onScanResult Amazfit GTS2 mini
[log] onScanResult [Monitor] Samsung M7 (32)
flutter: stopScan invokeMethod success
2[log] onScanResult Mi Band 3
[log] handleConnection connected
Lost connection to device.
Exited (sigterm)

How I can debug it?
I'm new to BLE maybe I do something wrong. I'm trying to port this project:
https://github.com/4lhc/MiBand_HRX/blob/master/base.py#L103

Is setNotifiable with BleInputProperty.notification the same as writing 0x01 to 0x2902 descriptor?

There's no crash if I set BleOutputProperty.withoutResponse for writeValue but no response from device too.

[Sunbreak]

Could you post flutter doctor -v?

Try DebugView if you need OutputDebugString result, for example:

quick_blue/quick_blue_windows/windows/quick_blue_windows_plugin.cpp

Line 221 in acc2142

OutputDebugString((L"HandleMethodCall " + winrt::to_hstring(method_name) + L"\n").c_str());

[ivs]

> flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.10.4, on Microsoft Windows [Version 10.0.22000.613], locale ru-RU)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.9)
[√] Android Studio (version 2020.3)
[√] VS Code (version 1.66.2)
[√] Connected device (3 available)
    ! Device emulator-5562 is offline.
[√] HTTP Host Availability

• No issues found!

DebugView logs:

[39572] HandleMethodCall startScan
[39572] Received BluetoothAddress:207251698759179, Name:Bluetooth bc:7e:8b:e2:36:0b, LocalName:
[39572] Received BluetoothAddress:207251698759179, Name:Bluetooth bc:7e:8b:e2:36:0b, LocalName:
[39572] Received BluetoothAddress:207251698759179, Name:Bluetooth bc:7e:8b:e2:36:0b, LocalName:
[39572] Received BluetoothAddress:207251698759179, Name:Bluetooth bc:7e:8b:e2:36:0b, LocalName:
[39572] Received BluetoothAddress:207251698759179, Name:Bluetooth bc:7e:8b:e2:36:0b, LocalName:
[39572] Received BluetoothAddress:257642978838462, Name:Mi Band 3, LocalName:
[39572] HandleMethodCall stopScan
[39572] HandleMethodCall connect
[39572] HandleMethodCall discoverServices
[39572] HandleMethodCall setNotifiable
[39572] HandleMethodCall writeValue
[39572] ConnectionStatusChanged 1

[Sunbreak]

Is setNotifiable with BleInputProperty.notification the same as writing 0x01 to 0x2902 descriptor?

I think so according to Android implementation of setNotifiable

quick_blue/quick_blue/android/src/main/kotlin/com/example/quick_blue/QuickBluePlugin.kt

Lines 287 to 298 in acc2142

	private val DESC__CLIENT_CHAR_CONFIGURATION = UUID.fromString("00002902-0000-1000-8000-00805f9b34fb")
	fun BluetoothGatt.setNotifiable(serviceCharacteristic: Pair<String, String>, bleInputProperty: String) {
	val descriptor = getCharacteristic(serviceCharacteristic).getDescriptor(DESC__CLIENT_CHAR_CONFIGURATION)
	val (value, enable) = when (bleInputProperty) {
	"notification" -> BluetoothGattDescriptor.ENABLE_NOTIFICATION_VALUE to true
	"indication" -> BluetoothGattDescriptor.ENABLE_INDICATION_VALUE to true
	else -> BluetoothGattDescriptor.DISABLE_NOTIFICATION_VALUE to false
	}
	descriptor.value = value
	setCharacteristicNotification(descriptor.characteristic, enable) && writeDescriptor(descriptor)
	}

[Sunbreak]

    QuickBlue.setNotifiable(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
        BleInputProperty.notification);
    QuickBlue.writeValue(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
        Uint8List.fromList(key_cmd + key), BleOutputProperty.withResponse);

You'd better await the result

    await QuickBlue.setNotifiable(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
        BleInputProperty.notification);
    await QuickBlue.writeValue(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
        Uint8List.fromList(key_cmd + key), BleOutputProperty.withResponse);

[Sunbreak]

    QuickBlue.discoverServices(deviceId);
    QuickBlue.setNotifiable(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
        BleInputProperty.notification);
    QuickBlue.writeValue(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
        Uint8List.fromList(key_cmd + key), BleOutputProperty.withResponse);

Try this on Android before Windows. Android BLE is much reasonable

[ivs]

The same crash with await.
I've tried to debug plugin with Visual Studio, found out this method:
https://stackoverflow.com/questions/71406447/flutter-desktop-windows-plugin-debug-native-c-code
I copied my code into quick_blue_example app and attach VS debugger, it gives me this stack trace:

Maybe it helps.

Seems I'm unlucky user:) Android code do not work at all, my device Realme SuperZoom, RMX2086. QuickBlue.scanResultStream.listen lamda do not called neither in my app nor in quick_blue_example app(windows build works just fine), this breakpoint never stops:

If you point me how, I can debug android and windows code.

[Sunbreak]

Could you try below APPs on Android as peripheral?

• LightBlue: https://punchthrough.com/lightblue-features/
• https://github.com/Sunbreak/ble-test-peripheral-android

[ivs]

Finally I resolved all my issues!
Android code didn't work because of permissions. Complete list of permission for AndroidManifest.xml

<uses-permission android:name="android.permission.BLUETOOTH" />  
<uses-permission android:name="android.permission.BLUETOOTH_PRIVILEGED" />  
<uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />  
<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>  

I got permissions exception on another phone TECNO CC7 and I have to give Location permission manually in App Info.

The crash reproduced on Android too. I've fixed it by adding await and delays. It seems my device needs some time to respond and without delays it disconnected and cause library crash.

This code works both on Windows and Android:

void mibandAuth(String deviceId) async {
  await QuickBlue.setNotifiable(deviceId, SERVICE_MIBAND2,
      CHARACTERISTIC_AUTH, BleInputProperty.notification);
  await Future.delayed(const Duration(seconds: 1));
  await QuickBlue.writeValue(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
      Uint8List.fromList(key_cmd + key), BleOutputProperty.withoutResponse);
  await Future.delayed(const Duration(seconds: 1));
}

void handleConnection(String deviceId, BlueConnectionState state) {
  d.log('handleConnection $deviceId');
  if (defaultTargetPlatform != TargetPlatform.windows) {
    QuickBlue.discoverServices(deviceId);
  } else {
    mibandAuth(deviceId);
  }
}

void handleService(String deviceId, String serviceId) {
  d.log('handleService $serviceId');
  if (serviceId == SERVICE_MIBAND2) {
    mibandAuth(deviceId);
  }
}

void handleValue(String deviceId, String characteristicId, Uint8List value) {
  d.log('handleValue $characteristicId $value');
}

@override
void initState() {
  super.initState();

  QuickBlue.setConnectionHandler(handleConnection);
  QuickBlue.setServiceHandler(handleService);
  QuickBlue.setValueHandler(handleValue);
  QuickBlue.isBluetoothAvailable();
  QuickBlue.scanResultStream.listen((result) {
    d.log('onScanResult ' + result.name);
    if (result.name == "Mi Band 3" && !bandFound) {
      bandFound = true;

      QuickBlue.stopScan();
      QuickBlue.connect(result.deviceId);
    }
  });

  QuickBlue.startScan();
}

Is this right way to use library? If it so I can make an example from it to library README.md.

[Sunbreak]

Android code didn't work because of permissions. Complete list of permission for AndroidManifest.xml

e907904 is here

I don't think <uses-permission android:name="android.permission.BLUETOOTH_PRIVILEGED" /> is needed

[Sunbreak]

void mibandAuth(String deviceId) async {
  await QuickBlue.setNotifiable(deviceId, SERVICE_MIBAND2,
      CHARACTERISTIC_AUTH, BleInputProperty.notification);
  await Future.delayed(const Duration(seconds: 1));
  await QuickBlue.writeValue(deviceId, SERVICE_MIBAND2, CHARACTERISTIC_AUTH,
      Uint8List.fromList(key_cmd + key), BleOutputProperty.withoutResponse);
  await Future.delayed(const Duration(seconds: 1));
}

When using with our product authentication on Windows, Future.delayed is not needed. Maybe a debug vs profile/release problem?

[Sunbreak]

I got permissions exception on another phone TECNO CC7 and I have to give Location permission manually in App Info.

If it so I can make an example from it to library README.md.

Agreed. Location permission on pre-Android-12 is quite cumbersome and needs documentation

https://developer.android.com/guide/topics/connectivity/bluetooth/permissions#declare-android12-or-higher

[ot-repo]

Hello,

I got the same error, when I use writeValue on Windows with more than 233 chracters. By 234 characters the app is crashing with Exited (sigterm)

That's why I chunk my data into 233 characters and send them to device as follows:

var chunks = _chunkData(data, 233);
for (var chunk in chunks) {
    await QuickBlue.writeValue(
      address,
      "49535343-fe7d-4ae5-8fa9-9fafd205e455",
      "49535343-8841-43f4-a8d4-ecbe34729bb3",
      Uint8List.fromList(chunk),
      BleOutputProperty.withoutResponse,
    );
    await Future.delayed(Duration(milliseconds: 250)); // this delay is only necessary on windows
}

static _chunkData(List<int> list, int chunkSize) {
    var chunks = [];
    for (var i = 0; i < list.length; i += chunkSize) {
      chunks.add(list.sublist(i, i + chunkSize > list.length ? list.length : i + chunkSize));
    }

    return chunks;
  }

The code above works perfectly on Android, IOS and MacOS. However on Windows, if I do not wait the tread, although I await the writeValue call, the chunks will not be received in the same order. For example, the second chunk will be printed before the first chunk. I beleive the function writeValue on Windows is not really async.

The questions here are, why the characters I can send to the device is limited on all platforms?
why writeValue is not behaving as a real async function on windows?

Is there anything better I can try?

Thank you!

[Sunbreak]

quick_blue/quick_blue_windows/windows/quick_blue_windows_plugin.cpp

Lines 274 to 285 in 1083edc

	} else if (method_name.compare("requestMtu") == 0) {
	auto args = std::get<EncodableMap>(*method_call.arguments());
	auto deviceId = std::get<std::string>(args[EncodableValue("deviceId")]);
	auto expectedMtu = std::get<int32_t>(args[EncodableValue("expectedMtu")]);
	auto it = connectedDevices.find(std::stoull(deviceId));
	if (it == connectedDevices.end()) {
	result->Error("IllegalArgument", "Unknown devicesId:" + deviceId);
	return;
	}
	RequestMtuAsync(*it->second, expectedMtu);
	result->Success(nullptr);

Some useful doc

• https://punchthrough.com/maximizing-ble-throughput-on-ios-and-android/
• https://punchthrough.com/maximizing-ble-throughput-part-2-use-larger-att-mtu-2/
• https://punchthrough.com/maximizing-ble-throughput-part-3-data-length-extension-dle-2/
• https://punchthrough.com/ble-throughput-part-4/

[ot-repo]

Thank you for the quick answer and links.

I really don't understand what requestMtu is or whether I should call it before calling writeValue method.

I have seen that the WriteValueAsync method is not awaited. Could this be the reason of the problem which is the data not received in the same order I send it via writeValue?

quick_blue/quick_blue_windows/windows/quick_blue_windows_plugin.cpp

Lines 312 to 313 in 1083edc

	WriteValueAsync(*it->second, service, characteristic, value, bleOutputProperty);
	result->Success(nullptr);