Somewhere worse, I just got a huge similar problem.
First: I'm using subsonic server on my raspberry, Version 4.9-KANG – January 29, 2014, with dyndns. So there might at some points be connection problems.
My Android APP is the Standard Subsonic App, set to "Use offline".
In about half an hour this morning it transferred 160Mb data in the background (according to android) using the mobile network without me even using the app. My server log is somewhere similar to the following.
- Code: Select all
...
[5/20/14 8:31:21 AM CEST] DEBUG InputStreamReaderThread (/var/subsonic/transcode/ffmpeg) size= 161kB time=20.61 bitrate= 64.1kbits/s
[5/20/14 8:31:21 AM CEST] DEBUG InputStreamReaderThread (/var/subsonic/transcode/ffmpeg) size= 160kB time=20.38 bitrate= 64.1kbits/s
[5/20/14 8:31:21 AM CEST] DEBUG InputStreamReaderThread (/var/subsonic/transcode/ffmpeg) size= 80kB time=10.19 bitrate= 64.3kbits/s
[5/20/14 8:31:22 AM CEST] DEBUG InputStreamReaderThread (/var/subsonic/transcode/ffmpeg) size= 123kB time=15.67 bitrate= 64.2kbits/s
[5/20/14 8:31:22 AM CEST] DEBUG InputStreamReaderThread (/var/subsonic/transcode/ffmpeg) size= 163kB time=20.87 bitrate= 64.1kbits/s
[5/20/14 8:31:22 AM CEST] DEBUG InputStreamReaderThread (/var/subsonic/transcode/ffmpeg) size= 161kB time=20.61 bitrate= 64.1kbits/s
[5/20/14 8:31:22 AM CEST] DEBUG InputStreamReaderThread (/var/subsonic/transcode/ffmpeg) size= 82kB time=10.42 bitrate= 64.3kbits/s
[5/20/14 8:31:22 AM CEST] DEBUG InputStreamReaderThread (/var/subsonic/transcode/ffmpeg) size= 125kB time=15.91 bitrate= 64.2kbits/s
...
Now 160Mb isn't too much, but considering it wasn't even supposed to load anything, and my mobile limit being quite low, I kinda ran out of mobile data transfer, which is the more annyoing part. Furthermore, I have the impression that subsonic already did this a few days ago, when my mobile didn't want to stop transferring data (i watched the web data icon), the phone got unusual warm and my battery was drained like being sucked by a vampire. Had to restart the complete phone to get things back to normal then.
I suppose there must be a bug somewhere. Is there any way I can find/produce a log of the android app?