Samsung Galaxy Tab A8 does not work with nRF Mesh Android App

[Alex Ross]

Hello,

Not sure where to direct this (we can open a GitHub issue but wanted to clear it here first), basically everything works great on our Galaxy Tab S6 Lite (SM-P610), can provision, everything. Same for the iOS version. However on the Samsung Galaxy Tab A8 (SM-X200) can see the device to be provisioned, but fails to provision it after the first steps.

We're using the 833 dev kit with soft device 140.  

Thanks,

Alex

[Roshan Rajaratnam]

Hi could you elaborate on where exactly it fails on the Galaxy tab A8?

[Alex Ross]

This step here. On the firmware side I see it disconnects and the provisioning is aborted. 

[Mttrinh]

Hi,

Could you provide us with a sniffer trace to see what is happening over the air? That will be helpful to figure out what is causing this issue.

[Alex Ross]

I'm slowly getting around to the sniffer however I'm pretty swamped with other parts of the project at the moment. Could we mail you a tablet? 

[Mttrinh]

Hi,

Sorry for the late response. Due to summer holidays there have been a delay in response during the summer.

Have you had any progress on this issue? 

[Alex Ross]

None yet, for now we're switching back to the S6. I sort of get the impression that this is a Samsung issue that they need to solve.

[JonasJ]

I'm experiencing the same issue with Samsung Galaxy Tab A8. I'm using version 3.2.4 of nRF Mesh and tested this against the dimming server example in nRF5 SDK For Mesh v5.0.

I've attached a log from nRF Mesh app, a pcap file showing the broken PB-GATT session, screenshot with info about the phone and a screenshot from Wireshark showing the numerous retries done by the tablet where Wireshark indicate CRC error. Finally the connection timeout.

I've tested the ST Mesh app on the same device and that works fine. I've also tested the nRF Mesh app with an example from NCS which also works.

So it seem to be the combination of Samsung Galaxy Tab A8, nRF Mesh app and NRF5 SDK For Mesh that doesn't work.

nrf_mesh-2022-09-16T14.12.38+02.00.log

nrf_mesh_provision_dimming_server_crc_error.pcapng

[JonasJ]

Noticed that 104 bits in the middle of Public Key Y changes for every retransmission but the CRC value remain the same.

Also, the nRF Mesh App log contain a couple of tries to provision various nodes, check the times in pcap to sync with the entries in the log.