Skip to content
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

Introduce more verbose logging #304

Closed
8 tasks done
uKL opened this issue Nov 2, 2017 · 3 comments
Closed
8 tasks done

Introduce more verbose logging #304

uKL opened this issue Nov 2, 2017 · 3 comments

Comments

@uKL
Copy link
Collaborator

uKL commented Nov 2, 2017

Currently, the library mostly logs the state of the operations. This is helpful for debugging the library itself. Additionally, I think that we could have logs with:

  • Scan results
  • Applied scan filters
  • Service discovery result
  • Characteristics UUIDs
  • Hex dump of the data written & read
  • MTU change request details
  • Notification occurrences
  • Details on checking the adapter, permissions, etc.
@RobLewis
Copy link

RobLewis commented Nov 2, 2017

Bravo! Fantastic help for debugging. Would these be output to separate files, and/or logcat? I assume there would be an API for choosing options—maybe just a bitfield?

Maybe include connection state changes, if not already covered.

@uKL
Copy link
Collaborator Author

uKL commented Mar 16, 2018

Related to #367 on the API level.

@uKL uKL added this to the 1.6.0 milestone Mar 16, 2018
@dariuszseweryn dariuszseweryn removed this from the 1.6.0 milestone Jun 8, 2018
@dariuszseweryn dariuszseweryn self-assigned this Feb 15, 2019
@dariuszseweryn dariuszseweryn added this to the 1.9.0 milestone Feb 15, 2019
@dariuszseweryn
Copy link
Owner

Released in 1.9.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants