Bluetooth issue x30

Hi gipo, same issues here.. Twice had same problem today..

Without restart BT does not get on, seems like the service is down or driver crashes. And that's 599€ device in Finland.. What the crap quality!

The issue is with the Device driver or Bt SoC..

After some time Bt cannot be switched on due to Initializing failure:

[email protected]_dl_manager: ReadNewHciEvent: Got an invalid proto byte: 255

[email protected]_handler: InitTimeOut: SoC Initialization stuck detected

[email protected]: SetRecoveryStartTime: recovery start time set

[email protected]_dl_manager: ReadNewHciEvent: Got an invalid proto byte: 255

[email protected]_dl_manager: ReadNewHciEvent: Got an invalid proto byte: 255

[email protected]_transport: CheckForUartFailureCode: UART driver returns err code = 0x51

[email protected]_controller: SsrCleanup: SSR triggered due to 3 skip sending special buffer

[email protected]_controller: ReportSocFailure: reason 3

[email protected]: BtPrimaryCrashReason:Init failed

[email protected]_dl_manager: ReadNewHciEvent: Got an invalid proto byte: 255

[email protected]: BtSecondaryCrashReason:SetBaudRateStuck

[email protected]: TS for SoC Crash:Fri Jan 20 15:03:45 2023

[email protected]: FrameCrashEvent: for primary 3 - secondary 26 crash reason with TS:Fri Jan 20 15:03:45 2023

[email protected]: FrameBqrRieEvent : pkt size = 6

[email protected]_handler: operator(): Resetting Rx thread stuck prop

[email protected]: FrameBqrRieEvent: for crash reason code :0x1a

[email protected]_dl_manager: ReadNewHciEvent: Got an invalid proto byte: 255

[email protected]_controller: SendBqrRiePacket sending vendor specific crash reason to the client

[email protected]_dl_manager: ReadNewHciEvent: Got an invalid proto byte: 255

[email protected]_dl_manager: ReadNewHciEvent: Got an invalid proto byte: 255

[email protected]_controller: ReportSocFailure send H/W error event to FM/ANT/BT client

[email protected]_handler: OnPacketReady: packet discarded and not handled

[email protected]_handler: OnPacketReady: discarded packet[0] = 0x1a 

[email protected]_handler: OnPacketReady: discarded packet[1] = 0x01 

[email protected]_handler: OnPacketReady: discarded packet[2] = 0x0f 

[email protected]_handler: OnPacketReady: packet discarded and not handled

[email protected]_handler: OnPacketReady: discarded packet[0] = 0x1c 

[email protected]_handler: OnPacketReady: discarded packet[1] = 0x01 

[email protected]_handler: OnPacketReady: discarded packet[2] = 0x0f 

[email protected]: Rx HW error event::Crash reason not found

[email protected]_handler: KillInitThread: Killing init thread

[email protected]_handler: usr2_handler: exit

[email protected]_handler: operator(): Resetting Rx thread stuck prop completed

[email protected]_controller: UnlockControllerMutex: unlocking controller_mutex

[email protected]_interface: UnlockDiagMutex: unlocking diag mutex

[email protected]_controller: HciTransportCleanup: deleting hci_transport

[email protected]_transport: Disconnect: discard unsent data

[email protected]_transport: DeInitTransport: Voting for clock OFF

[email protected]_transport: DeInitTransport: Transport is being closed!

[email protected]_transport: SendWakeupSignal: Opening port for sending wakeup signal

[email protected]_transport: InitTransport: opening /dev/ttyHS0

[email protected]_transport: userial clock on

Diag_Lib: BluetoothDeathRecipient: Calling HAL close

[email protected]_handler: StackTimeoutTriggered: Stack was not properly closed

[email protected]_hci: BluetoothHci::close()

[email protected]_transport: GetBaudRate: Current Baudrate = 38400 bps

[email protected]_transport: InitTransport: device fd = 8 open @38400 bps

[email protected]_transport: SendWakeupSignal:sent out wakeup signal

[email protected]_transport: DeInitTransport: Voting for clock OFF

[email protected]_transport: DeInitTransport: Transport is being closed!

[email protected]_transport: CleanUp:> soc_type: 3, need_reload: 1

[email protected]_transport: InitTransport: opening /dev/ttyHS0

[email protected]_transport: userial clock on

[email protected]_transport: GetBaudRate: Current Baudrate = 2400 bps

[email protected]_transport: InitTransport: device fd = 8 open @2400 bps

[email protected]_transport: CleanUp:send out shutdown signal

[email protected]_transport: DeInitTransport: Voting for clock OFF

[email protected]_transport: DeInitTransport: Transport is being closed!

[email protected]_lock: Release wakelock is released 

[email protected]_lock: CleanUp wakelock is destroyed 

[email protected]: DeleteDumpsIfRequired: Cannot open dump location /data/vendor/ssrdump/

[email protected]: DeleteDumpsIfRequired: Cannot open dump location /data/vendor/ssrdump/

[email protected]: ReadSsrLevel: ssr_level set to 3

/vendor/bin/hw/[email protected]: type=1400 audit(0.0:80647): avc: denied { read } f

/vendor/bin/hw/[email protected]: type=1400 audit(0.0:80648): avc: denied { read } f

/vendor/bin/hw/[email protected]: type=1400 audit(0.0:80649): avc: denied { search }

[email protected]: DumpBtState: File open (/data/vendor/ssrdump/ramdump_bt_state_2023-01-2

[email protected]_manager: SetPower: enable: 0

[email protected]_manager: 

[email protected]_manager: PowerUpChip enable(0) retentionMode(0)

[email protected]_controller: Killing daemon as SSR is completed!

So, it keeps re-starting, but magic does not happen :-).

What a crap quality! No testing done for the product.

Dear Nokia, what is the ETA to fix it?

After successful connect BT SoC goes to sleep and never wakes up anymore. HW issue? Can it be fixed with BT FW update / BT Device driver? Another option to make an ugly fix - keep it "awake" and eat more battery to be alive. That's unbelievable in 2023 these basics are not working and cannot be fixed for months with having OTA in place.

The New build Android 12 ( V1.310 ) with Security patch January 2023 doesn't solve the problem with 2K/4K video reproduction.

The bluetooth is still failing.....

Hi all,

The exact same problem here on my X30 (February patch installed).

After certain period I can't start blueotooth, only device restart helps.

Nokia dev team, seriously?!

Same here with all updates installed as of today.

I'm not completely sure, but I think that the NFC reader has the same Problem

Hi guys,

How does it look after the march update?

So far looks good on my side, I've installed the update couple of days ago.

I happens less for me since the March update, but still occurs.

Got android 13 today so will see if that helps....but seems likely it's a HMD driver issue rather than the OS.

It is ridiculous. If you just bought your Nokia, then send it back for a refund. Mine just updated to Android 13 and as a result I cannot connect my X30 5G to my Toyota via Bluetooth any more. It connects, but if a call comes in/goes out, it cuts the connection after 1-10 seconds.

This is the kind of problem where you would expect a hotfix within a few days but as I can see, people have had Bluetooth problems for months now, just plain crazy.

I think you should visit the Gulf Expats website. I have seen so many articles related to mobile issues. I think we should visit there to find a viable solution.

The exact same thing started yesterday on my Nokia X30! I connect my phone to the Renault's R-Link system in my car and the connection drops out every 1-10 seconds. Previously I "only" have had problems starting bluetooth, now suddenly another **** problem. The same thing occurs on my wife's X30!

Can we get an official explanation from someone from Nokia please?! This became a major issue now.

1. Ensure Bluetooth is enabled in your phone's settings.
2. Make sure the device you're trying to connect to is within range.
3. Restart your phone and try enabling Bluetooth again.
4. Check for any software updates for your Nokia X30 and install them if available.
5. Reset your phone's network settings, which can sometimes resolve connectivity issues.

https://www.mybkexperience.one/