New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clutterreport: /storage/emulated/0/linkmessages (new) #1141

feistyone68 opened this Issue Sep 19, 2017 · 3 comments


2 participants

feistyone68 commented Sep 19, 2017


Target: /storage/emulated/0/linkmessages
Prefix-free: linkmessages
Path-prefix: /storage/emulated/0/
Location: SDCARD
Current keeper state: false
Suggested keeper state: true

Suggested owners

Appname: Messenger
Version: 1.7.9 (179)

Current owners


SD Maid

Version: 4.7.6 (40706)


Fingerprint: samsung/j3xlteuc/j3xlteatt:6.0.1/MMB29K/J320AUCS3AQG1:user/release-keys

@d4rken d4rken added this to the v4.8.0 milestone Sep 19, 2017


This comment has been minimized.


d4rken commented Sep 19, 2017

What kind of data does this contain? Backups?


This comment has been minimized.

feistyone68 commented Sep 19, 2017

Partially. I'm new to this so I could be wrong.

Contains 2 folders. One named files that has 0 items and one named gif that has 359 items and both folders have drw permissions.

It also contains 4 PNG images I use for custom backgrounds. The last 2 items are JPG images that I shared from Facebook. The 6 image files have rw permissions.

The only files I was concerned about losing were my custom backgrounds.

Not sure how important the other are.


This comment has been minimized.


d4rken commented Sep 19, 2017

You did everything correctly, if this contains things such as the custom backgrounds, that you want to keep even after removing the app, then it is correct to mark it as keeper.

The clutter report itself just teaches SD Maid about the connection, the "keeper" flag tells SD Maid whether the files are to be kept even without the app that created them.

@d4rken d4rken closed this Sep 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment