I'm sorry, if this is the wrong place to report an issue about nrf Mesh Sniffer for Android. I could not find another place...
Describe the bug
When receiving Battery Status messages using the app on Android, the flags are not properly parsed. See screenshot below where 0x00 is not get parsed correctly.
To Reproduce
Steps to reproduce the behavior:
- Create a node that sends
Battery Status messages
- Scan those messages with nRF Mesh Sniffer
- See that the
flags byte does not get parsed correctly
Expected behavior
When sending the following data encode into the flags byte I would expect the app to decode them correctly.
net_buf_simple_add_u8(&msg, 0b10110000); // flags
^ ^ ^ ^
| | | |_ Bits 6-7 (Reserved, 0b00)
| | |___ Bits 4-5 (No service needed, 0b00)
| |_____ Bits 2-3 (Charge level unknown, 0b11)
|_______ Bits 0-1 (Battery present, non-removable, 0b10)
Platform details:
- Device: Google Pixel 7a
- OS: Android 15
- App version:
1.0.0
Logs / Screenshots

I'm sorry, if this is the wrong place to report an issue about
nrf Mesh Snifferfor Android. I could not find another place...Describe the bug
When receiving
Battery Statusmessages using the app on Android, the flags are not properly parsed. See screenshot below where0x00is not get parsed correctly.To Reproduce
Steps to reproduce the behavior:
Battery Statusmessagesflagsbyte does not get parsed correctlyExpected behavior
When sending the following data encode into the flags byte I would expect the app to decode them correctly.
Platform details:
1.0.0Logs / Screenshots
