[nRF Connect SDK] Disconnected by reason code 0x3d

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

slot pk app — Sun, 22 Jun 2025 20:39:33 GMT

The slot pk download took just seconds and gave me access to a full world of slot excitement. Everything in the app is designed for Pakistani players—from payment gateways to regional bonuses. I was impressed by how well the slot pk download worked even on my older Android device. The app is stable, fun, and constantly rewarding. It also includes social features like leaderboards and friend invites, which makes the experience even better. For real entertainment and a smooth user experience, slot pk download is definitely worth it!

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

nhancho — Fri, 10 May 2024 18:17:17 GMT

I'm also facing the same problem for my device and I've spent a wordle lot of time trying to figure out how to fix it, it's disheartening that until now I still haven't solved this problem.

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

dorrdle12 — Mon, 11 Sep 2023 10:27:18 GMT

Prepare yourself with dordle, a new spin on Wordle that includes entertaining puzzles and user-friendly enhancements! To win, the player must first guess the new word, followed by selecting the best response. Every round, players are limited to seven incorrect guesses, so try to finish the puzzle as quickly as possible. So you think you can figure out the dordle game language? Now put yourself to the test!

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

Tim Hwang — Thu, 03 Nov 2022 05:50:02 GMT

Hello.

I got Nokia5.3 and I found Nokia5.3 have some issue with handling BT connection when WiFi disconnect not only my project but classic and other BLE.
We will reopen this case if we need further question.

Thank you.

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

Hung Bui — Wed, 26 Oct 2022 10:58:44 GMT

Hi Tim,

It's normal that the phone disconnect after you put it into a shield box. Depends on the connection timeout and depends on the latency on the phone on when it report the disconnection, a 4-5 seconds time out is normal.

Regarding the 0x3d issue, please try to capture sniffer trace , not just snoop log.

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

Tim Hwang — Wed, 26 Oct 2022 10:55:01 GMT

Hello.

We did test and got result code 0x8 this time.
So one of my colleagues is testing to get another log as well. I can get new log soon.

In addition, I also test link loss timeout.
I made connection and put Android into shield box.
It disconnected 4~5 seconds later.
Here is my source code.

#define INTERVAL_MIN 15
#define INTERVAL_MAX 15
static struct bt_le_conn_param *conn_param = BT_LE_CONN_PARAM(INTERVAL_MIN, INTERVAL_MAX, 0, 400);

bt_conn_le_param_update(current_conn, conn_param);

I think it's okay. What's your opinion?

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

Hung Bui — Wed, 26 Oct 2022 10:32:27 GMT

Hi Tim,
Please double check and confirm if the disconnection reason was 0x3d (MIC error) or 0x08 (connection timeout).
If it's a connection timeout it's normal to explain it. It's just that the Nokia phone was out of range.

I assume the SPP device was a Bluetooth Classic device ?

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

Tim Hwang — Wed, 26 Oct 2022 04:22:45 GMT

devzone.nordicsemi.com/.../hci_5F00_snoop20221025194512.cfa

Hello.

Now I just have heard how this issue made.

Android: Nokia 5.3 (Android 11), Galaxy was fine.
Steps:
1) Connect Nokia5.3 to wifi. Nokia5.3 connect to Nordic too.
2) Nokia5.3 move to weak signal area so that wifi disconnected.
3) BLE disconnected (code 0x3d) this time 0x8(timeout)
4) We always made this issue.
BTW SPP device but not Nordic BLE was fine with this test.

Here is snoop log regarding this issue.
Can you please let us know any special thing in this log?
#938 Disconnection message

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

Tim Hwang — Tue, 25 Oct 2022 10:16:32 GMT

Thanks. I'm waiting for log as well. I'll update it soon.

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

Hung Bui — Tue, 25 Oct 2022 10:10:48 GMT

Hi Tim,

If it was the log from the nRF52 saying the disconnected reason was "reason: 0x003d". Then it's the indication that the Android had sent a packet with MIC failure.

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

Tim Hwang — Tue, 25 Oct 2022 09:04:13 GMT

Hello.

1. sniff log
It is not easy that we provide it immediately.

2. sample
Actually, we are using custom throughput sample with custom UUID but not HID.
Today, one of our engineer visit customer and get RTT log.
Then I believe we can provide disconnection reason code.

If Android(Nokia5.3) made MIC error, what kind of error code Nordic BLE will have?
Or Nordic made MIC error, what kind of error code Nordic BLE will have?

Thanks.

RE: [nRF Connect SDK] Disconnected by reason code 0x3d

Hung Bui — Mon, 24 Oct 2022 09:20:53 GMT

Hi Tim,

Error code 0x3d means: a message failed a Message Integrity Check (MIC)
So for some reason the message passed CRC check but failed the MIC check. It's required by spec that the nRF52 would need to disconnect when receiving this type of packet.

We would need to have a sniffer trace to really see which device causing this. There could be a chance that the Nokia 5.3 is doing something wrong.

Please ask the customer to test with the default example from the SDK without any modification. They can also try with other example (that require bond) instead of peripheral_hids_keyboard. Just so we can verify if the HID profile would cause any problem.