Hi, every so often the Android App is flooding the logs with messages like
03-31 14:50:20.749 7555 7555 V ApiRequest: Performing request to https://127.0.0.1:8384/rest/system/connections
03-31 14:50:20.760 7555 7555 I chatty : uid=10198(u0_a198) com.nutomic.syncthingandroid identical 12 lines
03-31 14:50:30.770 7555 7555 V ApiRequest: Performing request to https://127.0.0.1:8384/rest/system/connections
03-31 14:50:30.771 7555 7555 I chatty : uid=10198(u0_a198) com.nutomic.syncthingandroid identical 2 lines
and you see that Android isn’t happy about this (actually, the https request messages came in bursts of 60 or so, but I didn’t want to flood this post with them), and it also makes it difficult finding other things in the logs.
So, is there a way to tune this down a bit?
How much devices have you got in the devices tab of your app?
Right now, I’ve got two of them.
Ok so theoretically there should be two connections queries logged every three seconds as the app queries status for every device you have. Was your screen off for some time while capturing the lines?
You mean, like the device was sleeping and catching up? In fact I was looking for something else in the logs and the device was almost permanently awake, I activated some apps and closed them again, although with being set to go asleep after 60s of inactivity, it went to sleep once or twice in about 15 minutes…
Yes, I first thought of some queued queries with a catch up to current. I know already that the eventprocessor that uses the same library class (apirequest) issues long running http requests to the web ui to save battery. If nothing happens on the event api, the request is just sitting there in state “pending”. I wonder if this also can happen to the connections query… Especially when thinking of how different Android’s can be regarding os power management.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.