By the way, I'd like to inquire about the behavior of BLE_permListDevConnect_allAndroid_2a.apk.
In a previous post, I replied with "It works fine on the Xiaomi Pad 6 device," which was consistent with the screenshot.
However, when I touch the ESP32 scanned in the ListView, can I confirm whether the BLE connection was successful?
In my initial post, I wrote, "freezes on touch of list view." but "freeze" was incorrect. To rephrase, it means "no response from ESP32," which is the same state as "received data not displayed in the TextBox."
Also, the meaning of "true, Perm. grated, Perm. grated" displayed at the bottom is unclear.
Dear
Many thanks for your help.
I have a similar issue with companion and extension.
only with Android 14 Samsung A72, Samsung A53 and Motorola G23 ) i have this isseue:
as described from 818macot when you add an aextension the companion stop to refresh the display on smrtphone.
i have tried with different extensions: bluetoothLE (different version), LocationStatus from ANKE.
I think there have been changes to A2I that have created this problem.
I have other projects compiled on July 16, 2024 that have the same extensions that if I install them on the smartphones listed above using the apk generated in July do not cause any problems, if I open the projects and run them with companion I do not even get to the main screen.
Are you comfortable using adb logcat? If you log the connection process to the point where the main screen should display in the companion and send it to me it might help me narrow down the issue.
This app was created with the current AI2 version (targetSdkVersion=34) and the latest version of the BLE extension (Date Built: 2024-08-22). And as you can see from my screenshot, it runs perfectly on an Android 14 device.
On the Xiaomi Pad 6 Android 14 device, the ListView that scanned the device should close after a successful BLE connection, but it did not close and the communication process failed.
I suspected the MIT AI2 Companion app because the time when this problem occurred coincided with the up grade of “MIT AI2 Companion Version:2.72/2.72u”.
So I searched to see if it was possible to down grade to Version:2.71, but could not find it.
I thought that the version of the app was available for download along with the version history, but since they did not exist, I did not search deeply enough to find out if down grading was not possible due to the consistency with MIT's server.
In the meantime, if I downgrade to Version:2.71, AI Companion is fine, but the next version 2.73 or later, remains a problem.
Also, bug fixes in the current version 2.72 and later may affect the project.
Dear ANKE, I love you.
we already meet on this forum for another issue on ble entension.
I respect you so much and I want to tell you so.
after that, now i'm trying to use logcat as sugeest from ewpatton, but for now i have a lot of debug rows and i must understand how extract some significative data.
please can you try now to open your project on a2i and test if you can connect and run with companion?
my main problem is that the companion stops works (not refresh smarthphone display) if i add an extension.
if i install a previous project already compiled in apk it works perfectly. But if i recompile it it doesn't work the companion screen disappears.
is it possible to have the aia file of your project to see if it works with the companion?
here is the aia of a simple test.
i have tryed a old version of comapnion app (2.66) and with this works fine
I think like 818macot "I suspected the MIT AI2 Companion app because the time when this problem occurred coincided with the up grade of “MIT AI2 Companion Version:2.72/2.72u”."
