This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Thingy Disconnects from GitHub Android App

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:

Bluetooth Disconnect

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!

Parents
  • 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

Reply
  • 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

Children
No Data
Related