• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 67 subscribers
  • Views 707 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 233464
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

komoot repeatedly disconnected again(based on Android)

Fridedrich
When I connected the development board with komoot (based on Android), komoot repeatedly disconnected again. The chip platform is nRF52832, and the protocol stack version is S332.
The reason for disconnection is BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION (0x16)
Does anyone know what is going on?
  • 0

    Hi,

    There is not enough information here to say anything about what is going on. Can you provide a sniffer trace, and perhaps also log from the nRF side? What is supposed to happen on the link, and how does this compare with what is actually happening (disconnect with reason 0x16)?

    Note that most of the BLE communication on the Android side is handled by the BLE stack, so it is probably not directly related to which app you are using (Komoot). 

  • 0 in reply to Einar Thorsrud
    Thank u for the reply,now I grabbed the packet with a sniffer and found that it was komoot (based on Android) actively disconnected (reason:0x13), instead of the device actively disconnecting, at the same time, I found that komoot (based on Apple) and the device connection is stable.So, it's very possible because some aspects of the Android machine optimized komoot, so I turned off the option for komoot optimization on my phone (one plus 3), but it still appears 0x13, but I use SAMSUNG GALAXYS In the S9 test, there is no disconnection (0x13 will appear if the battery optimization option is not turned off). So, probably because of the optimization of the Android battery.thank u,Have a nice day. 
Related