zehnm
commented
2 days ago 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
Is there an existing issue for this?
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 directoryI'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
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 :)