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

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

Parents
  • Hi again

    So, I reproduced it on my end as well, and created an internal case on it with our mobile apps team. However, from my Ellisys sniffer trace, the error seems to be due to an unexpected packet length, which initially leads me to think it's related with the same specification breach we discovered earlier this summer. It is still strange that it only occurs with the nRF Mesh application on the A8 side. It seems to be related to some timing of tasks in the combination of A8 tab, nRF Mesh application, and nRF5 SDK. 

    Our mobile app developers are starting to look into it, but I can't guarantee a patch/fix right away I'm afraid.

     packet length error nRFMesh.btt

    Best regards,

    Simon

Reply
  • Hi again

    So, I reproduced it on my end as well, and created an internal case on it with our mobile apps team. However, from my Ellisys sniffer trace, the error seems to be due to an unexpected packet length, which initially leads me to think it's related with the same specification breach we discovered earlier this summer. It is still strange that it only occurs with the nRF Mesh application on the A8 side. It seems to be related to some timing of tasks in the combination of A8 tab, nRF Mesh application, and nRF5 SDK. 

    Our mobile app developers are starting to look into it, but I can't guarantee a patch/fix right away I'm afraid.

     packet length error nRFMesh.btt

    Best regards,

    Simon

Children
Related