The Android logcat is overloaded with V/Cursor: Filling cursor window with start position:0 required position:0, so much so that the logs are being throttled with logs like I/chatty: uid=10182(app.package.name) DefaultDispatch identical 8 lines.
When performing many queries, this can result in chatty throttling thousands of lines in a matter of seconds. Even with this throttling, there are still dozens of these repetitive lines in the logs.
... 16:46:36.575 ... V/Cursor: Filling cursor window with start position:0 required position:0
... 16:46:56.483 ... I/chatty: uid=10183(app.package.name) SyncAdapterThre identical 1012 lines
... 16:46:56.570 ... V/Cursor: Filling cursor window with start position:0 required position:0
... 16:46:58.047 ... V/Cursor: Filling cursor window with start position:0 required position:0
... 16:46:58.639 ... I/chatty: uid=10183(app.package.name) SyncAdapterThre identical 998 lines
... 16:46:58.639 ... V/Cursor: Filling cursor window with start position:0 required position:0
... 16:46:59.358 ... V/Cursor: Filling cursor window with start position:0 required position:0
... 16:47:06.419 ... I/chatty: uid=10183(app.package.name) SyncAdapterThre identical 4079 lines
... 16:47:06.419 ... V/Cursor: Filling cursor window with start position:0 required position:0
Performing this many log operations is sure to have a performance hit, with the string formatting and I/O involved. I see that this commit added support for gating logging to only DEBUG builds. This would be a much welcomed change. Is there a planned release date for an update to the Android SQLCipher library that would include this change?