Thingy Disconnects from GitHub Android App

[cprehn]

Details

Hardware: Thingy52, nRF52840 Dev Board, Samsung Tab A running Android 5.1.1

Software: Windows 10, using GCC for compilation, Thingy52 SDK, Android-Nordic-Thingy-master from GitHub

I'm trying to run the Android app from the GitHub to connect with a Thingy, but when the two try to connect, the Thingy says it connects.  Immediately, though, it disconnects.  Segger RTT reveals this:

The Thingy can connect to the app store versions of the Thingy app, but when I try loading the GitHub version and running it, the Thingy refuses to connect.  Eventually, I'd like to modify the Android app, but I need to be able to connect and send the default data first.

I've found someone else having the same issue.  The project is time sensitive so I decided to take it to a private forum.

What could the issue be?

Thanks!

[Bjørn Kvaale]

Hi Curtis,

Sorry for the delayed response. I saw the comment on your other case, but unfortunately the mobile apps developer was not available at the time. We are also currently understaffed due to summer vacation, so this case unfortunately slipped past my radar.

You mentioned previously in another comment that you had modified the Thingy code slightly. Are you now running the default thingy fw code v2.0.1 downloaded from Github or from the Nordic Semi homepage?

Did you erase the Thingy device first? Have you programmed the s132 v4.0.2 softdevice to the Thingy device? Did you then program the Thingy FW to the Thingy:52?

I talked to a developer in the mobile apps group & he said the Thingy Android application is the same as the version uploaded to our Github page.

Could you upload a sniffer trace of the Thingy device & the Android app downloaded from Github on your Samsung Tab A?

Do you also have the possibility to test the setup with another Android phone? That way, we can see if this problem is only related to the Samsung Tab A device.

Kind Regards,

Bjørn

[cprehn]

I flashed a Thingy with the default hex of the firmware to narrow down what the cause of the issue could be, but the app would still disconnect from the Thingy.  I also tried compiling the GitHub versions of the firmware and Android code, but that still produce the same issue.

I have been able to test the Android store app on another Android device, which was successful with both the custom and default firmware, but I haven't been able to try the custom Android app on a device other than the tablet.  However, I do suspect that it's the tablet causing the issues and not the app or firmware at this point.  I'm going to try getting a hold of another Android device to test on.  I'll also grab some sniffer trace data with the tablet.

 

Thanks!

[cprehn]

Just as an update: I'm not able to get any BLE packets to appear in Wireshark using the Nordic Sniffer extension.  The hardware shows up, and I've got the emulator version dates to match, but no data seems to be showing up when I run Wireshark.  I'm using the nRF52840 as the sniffer.  I loaded the hex for the nRF52832 from the extcap hex\ folder since there wasn't a hex for the nRF52840.

 

Like before, I'll get another Android device to test, but it won't be until tomorrow.

 

Thanks again!

[cprehn]

I was able to put the GitHub version of the Thingy app onto another Android device while running the default firmware on the Thingy, and it worked.  So it's likely that the fault is in the tablet.

Thanks again for your help!