-
Notifications
You must be signed in to change notification settings - Fork 23
Suggested changes for bluetooth information #110
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
Conversation
Eeems
left a comment
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.
restructured text doesn't like to render properly when codeblocks don't have a whitespace before them, but wont raise a warning or exception. I haven't tested to see if this renders properly as-is, but it's probably best to be consistent. There was also a spelling mistake that spellcheck made me aware of.
Co-authored-by: Nathaniel van Diepen <Eeems@users.noreply.github.com>
Co-authored-by: Nathaniel van Diepen <Eeems@users.noreply.github.com>
Co-authored-by: Nathaniel van Diepen <Eeems@users.noreply.github.com>
Co-authored-by: Nathaniel van Diepen <Eeems@users.noreply.github.com>
|
You've got this marked as a draft still, was there anything else it was waiting on? |
|
I'm still testing the udev solution out in practice - there are sometimes disconnects with this solution anyway, I'm trying to confirm that this is the external device which disconnects (and then adding information on that). I guess these things could be a separate PR except for the first comment. |
|
I haven't got more time to dig deeper the next couple of weeks, so I think this could be merged now. |
Here are some suggested changes for the bluetooth page with information on how to avoid "random" disconnects (they are actually not random at all, but completely deterministic and expected).