Java SDK BluetoothGatt very chatty same line every 3 seconds
challgren opened this issue · 7 comments
challgren commented
Using the Java/Android SDK the "BluetoothGatt" is extremely chatty with readRssi() - device: 00:21:AD:13:12:6E every 3 seconds when connected to a device
In my application in the event of an exception the last 100 lines of the logcat output are sent along with the event crash. However because BluetoothGatt is extremely chatty being able to debug my crashes is extremely difficult is there anyway suppress/silence this unnecessary Log.d messages?
2019-04-30 19:36:46.868 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:36:49.873 11460-11460/com.truepedigree.newportreader I/chatty: uid=10153(u0_a153) com.truepedigree.newportreader identical 1 line
2019-04-30 19:36:52.880 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:36:54.516 11460-11460/com.truepedigree.newportreader I/BleScanner: onScanFinished() mScanning true; mListeners 0
2019-04-30 19:36:54.521 11460-11460/com.truepedigree.newportreader D/BluetoothAdapter: isLeEnabled(): ON
2019-04-30 19:36:55.888 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:36:58.901 11460-11460/com.truepedigree.newportreader I/chatty: uid=10153(u0_a153) com.truepedigree.newportreader identical 1 line
2019-04-30 19:37:01.910 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:04.919 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:13.958 11460-11460/com.truepedigree.newportreader I/chatty: uid=10153(u0_a153) com.truepedigree.newportreader identical 3 lines
2019-04-30 19:37:16.967 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:19.978 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:29.013 11460-11460/com.truepedigree.newportreader I/chatty: uid=10153(u0_a153) com.truepedigree.newportreader identical 3 lines
2019-04-30 19:37:32.023 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:35.037 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:44.070 11460-11460/com.truepedigree.newportreader I/chatty: uid=10153(u0_a153) com.truepedigree.newportreader identical 3 lines
2019-04-30 19:37:47.080 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:50.095 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:53.109 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:56.119 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
2019-04-30 19:37:59.129 11460-11460/com.truepedigree.newportreader D/BluetoothGatt: readRssi() - device: 00:21:AD:13:12:6E
AriPoy commented
You'll just need to use logcat filter to include only those message you want to see. Set your own "TAG" for Log.x function in your app and you can see your log messages in logcat.
In case of crash, use filter "FATAL" and you'll see exception causing crash.
challgren commented
Understandable when debugging with the device connected to my computer.
However in production using PushLink I can't filter the logcat output. And
in the matter of 5 minutes the entire log cat can be filled with this
chatty output that is unnecessary for a developer. Thus reducing the number
of lines I can use in logcat that can be useful for my own debugging.
Bottom line it's noisy and unnecessary output for a software developer.
Please allow an option to enable/disable it. I would fix it myself but the
jar source is not publicly available.
…On Thu, May 2, 2019, 01:28 Ari Pöyhönen ***@***.***> wrote:
You'll just need to use logcat filter to include only those message you
want to see. Set your own "TAG" for Log.x function in your app and you can
see your log messages in logcat.
*In case of crash, use filter "FATAL" and you'll see exception causing
crash.*
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAVWTLPG3KVVDT6R5AAUB3PTKCX7ANCNFSM4HJRE75Q>
.
AriPoy commented
ok, yes, you're right. It's unnecessary. Will be removed..
challgren commented
Thank you! Otherwise love the SDK so far very easy to understand and work
with
…On Thu, May 2, 2019, 01:47 Ari Pöyhönen ***@***.***> wrote:
ok, yes, you're right. It's unnecessary. Will be removed..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAVWTNMW3B5YGDHHXPEDUTPTKE7RANCNFSM4HJRE75Q>
.
AriPoy commented
it looks like that BluetoothGatt: readRssi() debug line is not produced by Nordic ID libraries..
challgren commented
Is it smart pair maybe? I'll see if I can track the source. I assumed it was nurapi