Hello everyone
Currently, I'm facing a very annoying issue and I have no idea how to solve this.
I'm running Lollipop 5.0.1 on my device. As soon as the system runs fstrim in the background, my entire Google Play Music cache (12GB) disappears and everything needs to be re-downloaded.
I allowed my Google Play Music app to download even on mobile data because I thought adding ~10 songs per week doesn't strip my entire mobile data volume. I didn't reckon that it would download 2000 songs while being outside, so it ate my entire data volume.
I can reproduce this issue by downloading the whole music library and afterwards run fstrim manually via terminal: fstrim -v /data.
Then I see that it trims 12GB data. If I open my Google Play Music app again, it starts re-downloading everything... :(
Does anyone have an idea how to solve this? Is there a way to exclude a directory from fstrim?
Side note: I've always been using Google Play Music. I also use Lollipop since its release. I never experienced this issue before, it somehow started recently, but I have no idea why or when it started. :crying:
Currently, I'm facing a very annoying issue and I have no idea how to solve this.
I'm running Lollipop 5.0.1 on my device. As soon as the system runs fstrim in the background, my entire Google Play Music cache (12GB) disappears and everything needs to be re-downloaded.
I allowed my Google Play Music app to download even on mobile data because I thought adding ~10 songs per week doesn't strip my entire mobile data volume. I didn't reckon that it would download 2000 songs while being outside, so it ate my entire data volume.
I can reproduce this issue by downloading the whole music library and afterwards run fstrim manually via terminal: fstrim -v /data.
Then I see that it trims 12GB data. If I open my Google Play Music app again, it starts re-downloading everything... :(
Does anyone have an idea how to solve this? Is there a way to exclude a directory from fstrim?
Side note: I've always been using Google Play Music. I also use Lollipop since its release. I never experienced this issue before, it somehow started recently, but I have no idea why or when it started. :crying:
No comments:
Post a Comment