New Alpha release, version 1.40.0

[Henrik "The Developer" Lindqvist]

Please test, report any issues, and give feedback. Opt-in for Alpha testing here.

What’s new:

• Bluetooth device active set block (Android 9+)
• Display power mode set block (Android 4.3+)
• Google Drive file exists block
• Wi-Fi hotspot clients connected block (Android 9+)
• Display query block got Connection input argument (Android 12+)
• Interact touch block got Display id input argument (Android 11+)
• Interact touch block got Record gesture button
• App package/component pick dialogs got search field
• Bluetooth GATT read block also works with “notification” only characteristics
• App kill background block requires the “privileged or (full) superuser access…” privilege on Android 14+
• Fixed privilege service to work on Android 14+

[P. Andreas Schmidt, IVE]

Hello Henrik, thanks for another update!

I have tried the ones I can try:

• Bluetooth device active set block (Android 9+)

I guess my device is not compatible with this, since I got the following error trying to set as active a non active BT device when paired to two simultaneuousy:

java.lang.NullPointerException: Attempt to invoke virtual method 'android.bluetooth.IBluetooth android.bluetooth.BluetoothAdapter.getBluetoothService(android.bluetooth.IBluetoothManagerCallback)' on a null object reference

When paired to just one and leaving all fields blank so as to set inactive, the following:

java.lang.ClassNotFoundException: com.android.bluetooth.x.com.android.modules.utils.SynchronousResultReceiver

• Google Drive file exists block - Works
• Wi-Fi hotspot clients connected block (Android 9+) - works
• App package/component pick dialogs got search field - works, and it's a great thing to have!!!
  
• App kill background block requires the “privileged or (full) superuser access…” privilege on Android 14+ - it didn't throw any errors/exceptions, but since the window remained in the list of apps, I don't know how to actually check if it really killed the app...?

As regards the BT GATT: it's not so relevant to the new feature and in this sense kinda late I guess, but I've tried reading the battery value in all kind of possible ways for my Soundpeats T2 earbuds, but all fail with the Connection Error 255...??!!

running Android 13 on LG Velvet 5G

[Henrik "The Developer" Lindqvist]

Thanks for the feedback.

The NullPointerException must originate from some internal Android API, maybe due to BT device being found/resolved, try specifying only the address, as picked using the Bluetooth device pick block.

I'll investigate the ClassNotFoundException. Its seems the API is repackaged somehow, i.e. with the odd "com.android.bluetooth.x." prefix, maybe that's only for the emulator,. I'll let it also look the non-repackaged.

BT, and GATT especially, is problematic on Android, but the error is certainly not caused by this update as the change was minimal.

Please try the new "record gesture" button in the Interact touch block as well, as that will probably see much use.

[P. Andreas Schmidt, IVE]

I'll try with just specifying the address (without the device name, then, right?)

About GATT, what I meant with "kinda late", that I had those issues from the beginning, but I never reported them, so I didn't mean to be related to this update. But since GATT was on the list, that reminded me.

I tried the record gesture: if it's meant to record more than just swipes, than that's not working well or at all on my device (see first post), and a double click is definately not possible, but I can understand if that's not the idea.

What defenitely is not as it should is that the speed is recognised inversely, meaning that the slower I swipe, the higher the speed will be and inverse. So that's definately something to fix!

[Henrik "The Developer" Lindqvist]

Yes, as the name may not have been resolved.

Sorry didn't get that. Error 255 (0xFF) could mean "out of range" or simply "undefined error", but since Android BT is so fubar it's difficult to tell, see:

https://cs.android.com/android/platform/superproject/+/master:packages/modules/Bluetooth/system/stack/include/gatt_api.h

https://cs.android.com/android/platform/superproject/+/master:packages/modules/Bluetooth/system/stack/include/hci_error_code.h

No, it's just Swipe for now, to help user get the screen coordinates. The speed calculation will probably never be accurate, but it shouldn't be inverted as you say, i'll investigate. What kind of speeds  do you get?

[P. Andreas Schmidt, IVE]

As for the record gesture speed (roughly speaking): if I swipe from bottom to top in 1 second around 1000, same movement in 10 seconds around 20000. It doesn't seem to make a difference which way I swipe. I thought perhaps it just picks up that last speed and that even though I take 10 seconds at the end I make a faster movement or so, but that doesn't matter. If I swipe a short bit very fast, I get 500 or so.

Perhaps it's not so much inverse as that it adds up with the time? The longer you take to make the swipe, that it doesn't measure the speed but just keeps adding it up, it's a sort of sum of speeds?

[Henrik "The Developer" Lindqvist]

Indeed, i forgot to account for the true distance.

[P. Andreas Schmidt, IVE]

Back again Henrik, unfortunately no change with changing the BT block settings, always the same error, no matter what.

[Henrik "The Developer" Lindqvist]

I'm working on it. New release coming soon.