-
Notifications
You must be signed in to change notification settings - Fork 417
Update bluetooth.md #1051
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Update bluetooth.md #1051
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would only apply to desktops, and not many laptops have (easily) removable batteries these days. It also sounds like overkill. What if we just told users to fully power off the machine, wait a bit, then power it back on with the power button? The motherboard will have to re-initialize PCIe and USB, which would re-initialize any bluetooth adapters that may be present.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not certain if a shutdown and wait approach would actually discharge the capacitors quickly enough. Eventually it would work, but we'd need to provide a reasonable time frame. In my case though, I did try to shutdown (also unplugged my machine), then waited 5 minutes before rebooting. That didn't have any impact. I ended up having to do the same, but also hold the power button to clear out any remaining voltage before rebooting.
That said, I believe holding the power button is sufficient whether the machine is plugged in to the wall or connected via battery to discharge the capacitors quickly. So a more universal approach could be to simply shut down, press and hold the power button, then reboot to see if bluetooth is working again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still not certain discharging the capacitors is something that has to be done to fix bluetooth for the vast majority of machines. Is this something you have to do on your machine regularly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a new machine that I built last week and have experienced the same issue twice so far. Both times after waking from suspend after putting it to sleep for the night.
I completely agree that it may not affect a majority of users, but I think it's an important and simple step to try 1st before doing any of the software changes described in the rest of article. The reason I submitted is because I tried those changes myself (along with several other solutions from various sources) to no avail, but this simple trick worked. Hoping I can help save another person from hours of research and testing different solutions, only to end up getting frustrated that all their work did nothing and they end up dropping pop_os or gnu/linux altogether because they couldn't figure out Bluetooth - when all they needed to do was hold the power button for 30 seconds. :-)
To be clear though, this is specific to anyone who had a previously working Bluetooth that has suddenly stopped. If Bluetooth had never worked, then this solution won't solve that. In either case though, it is still a non-destructive step to take to ensure there aren't any hardware issues before users start messing around with config files, deleting files/folders, installing other software, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI - Another user impacted for which this fix worked:
https://www.reddit.com/r/pop_os/comments/xsh8w3/comment/iqri222/?context=3