[bug] Remote2 bluetooth constantly loses paired status

[addd45]

Is there an existing issue for this?

• I have searched the existing issues

Description

Bluetooth is showing as unpaired from the web config, however on my nvidia shield it says connected. This has occurred 3 times and this most recent time was within 24 hours. I am on the latest beta firmware (1.9.4), but the issue has occurred on the all 3 beta releases so far.

I've seen this error log seem to point to an issue with SIGPIPE -
2024-07-20 15:00:33.770387 +00:00 bt INFO E | socket_connection.c:754 | socket_connection_init: failed to ignore SIGPIPE, error: No such file or directory

I've reached out in the discord unsuccessfully multiple times without getting any responses regarding this issue, I would be surprised if I'm the only one experiencing it?

Happy to share any relevant logs if someone is willing to look into this

How to Reproduce

1. follow steps to pair new bluetooth device
2. use remote per normal
3. wait awhile (say 24 hours) - remote can be docked or undocked
4. check web ui to see bluetooth unpaired

Expected behavior

Remote stays paired. bluetooth on the remote should never become spontaneously unpaired. Signal reception issues can be expected in scenarios where the remote is far away from the paired device, but the remote shouldn't lose paired status.

System version

1.9.4

What part of the system affected by the problem?

Core

Additional context

My 'watch tv' integration is dependent on bluetooth. Thus it is unusable for watching tv and pretty much a paper weight. wife happiness is at an all low :)

[zehnm]

Bluetooth implementation is in Beta status.
See Beta Release 1.8.0 release notes:

- Known device issues:
  - Playstation 4: does not work, reports "not compatible" after pairing
  - Playstation 5: pairing issues, under investigation
  - Shield TV: occasional "bonding lost" issues, under investigation
  - LG TV, Samsung smart monitor M7: cannot be powered-on with Bluetooth. Most likely this 
    applies to many other devices as well.

Please provide more information:

• does it only happen with nvidia shield?
• was the nvidia shield powered on all the time, or switched off / restarted after pairing?
• multi-connection mode enabled?
  • if yes: max connections & how many connections are used
• did you change the BT sleep behaviour settings?
• full Bluetooth driver log. (web-configurator: settings, development, logs: Bluetooth driver, DEBUG)
• It would be a big help if you could provide the Bluetooth HCI log from BT device pairing until it's no longer working. This helps us to track down this issue and eventually get help from the Bluetooth software stack provider.
  • Enable in web-configurator, settings, network, Bluetooth
  • Restart remote after enabling it, pair with device, wait until no longer working, download HCI logs.

If you don't want to post the logs publicly due to MAC addresses etc, we can switch to a private channel.

The mentioned log message can be ignored (BT library tries to ignore SIGPIPE signal, which fails).

[addd45]

Thanks for the quick reply, I am aware of the beta status, but I guess I didn't see the nvidia shield was more unstable than others.

does it only happen with nvidia shield?

unfortunately I don't really have any other devices to confirm this with, but for now yes.

was the nvidia shield powered on all the time, or switched off / restarted after pairing?

the nvidia shield goes into sleep mode when the activity is turned off, so in this case the shield would have been in sleep mode between successful pairing and the loss of pairing

multi-connection mode enabled?
if yes: max connections & how many connections are used

I believe I have this set to 1, if this is the setting under network -> bluetooth?

did you change the BT sleep behaviour settings?

I'm not sure how to change BT sleep settings, but I can check this as well.

I just enabled HCI logs, so unfortunately don't have any to share yet. I am attaching the full set of bluetooth/core logs from the past 3 days, which should include the time from when the remote was paired to when the remote became unpaired.

Let me know if I can help any further. Thanks again for your help.

UCR2_logs_2024-09-19.txt

[addd45]

BT logs:
UCR2_logs_2024-09-25.txt

Pairing lasted less than 24 hours this time 😞 Also important to note, Shield still sees the device as connected, even shows the correct battery %.

Attached full bluetooth logs with HCI enabled.

HCI dump:
hci_dump.zip

[addd45]

@zehnm Not to be pushy here but have you had a chance to look at the logs I've shared? Want to make sure you aren't waiting on more details from my end. I understand you are probably very busy, but I do feel stabilizing bluetooth has got to be a top priority?