Don't work backup in Android 13 about musify

[gokadzev]

no, only in the backup, that's why I can understand why it is repeated several times in the backup in favorites and in search history , more if I make the backup after delete all search history.

If it's only in backup file content and it doesn't affect data when you restore in the app, then there's nothing to worry about

[marcossmtp]

well I have a backup of 15 songs in favourites and it grow from 20kb to 600kb, why as much information about.
Its not possible use json or yaml instead of hive format to store backups?
It would more clear and really less space of storage

[marcossmtp]

ok thanks

[marcossmtp]

very nice to heard that
thank you very much

[marcossmtp]

same for me with android 13

[gokadzev]

It works, you just need to choose "Documents" folder, otherwise it won't work because of Android 13 restrictions.

[gokadzev]

In other thing when I make the backup in android 8 it works but the file have too much information. I deleted search history, cache and all, and it repeats the same line several times. https://pastebin.com/y1AZ2yAL This is the backup with 5 song marked favourite and after clean cache and search history

About that, don't edit backup content. it's not cache, the app doesn't backup cache, all these info are user and settings info.

[marcossmtp]

yes, but in other apps I have in android 13 when they need to store something it ask for permission to write in the folder and it writte without problem in any folder of the phone.
In other case I think @calatorius is refering that deleting history search and only having 5 songs is a lot of information repeated, I see the same template in my case. Why if history search is deleted appears repeated many times the same entry?

[calatorius]

Yes, I was refering at the amount of the same data repeated when I deleted the search history.
And like it said by @marcossmtp perhaps if the app get the permission of storage and not media it allows to choose the folder to download songs and backups.

[gokadzev]

About repeating data I need more information, because I really didn't understand the problem. About access on other folders too, I prefer to follow Android restrictions and give app control on folders according to the android rules, we already had some permission and download connected issues and I don't want to mess up things again.

[calatorius]

About repeating data I need more information, because I really didn't understand the problem. About access on other folders too, I prefer to follow Android restrictions and give app control on folders according to the android rules, we already had some permission and download connected issues and I don't want to mess up things again.

This two screenshots are after clear history search and the song destiny is all I have onlv added one time to favorites.

[gokadzev]

About repeating data I need more information, because I really didn't understand the problem. About access on other folders too, I prefer to follow Android restrictions and give app control on folders according to the android rules, we already had some permission and download connected issues and I don't want to mess up things again.

This two screenshots are after clear history search and the song destiny is all I have onlv added one time to favorites.

Does it show this song several time in the app after restoring this backup file too?

[marcossmtp]

no, only in the backup, that's why I can understand why it is repeated several times in the backup in favorites and in search history , more if I make the backup after delete all search history.

[calatorius]

yes its my case too

[calatorius]

ok, it was only curiosity about the reason of that.
Thanks

[calatorius]

i use mixplorer to edit the file, and the file is 21.3kb that matchs with the text that shows, and it would be too much for no history search and only 5 songs in favorites.
But I'm with you that if not affected at the app only all is ok.

[calatorius]

yes, I'm in the same oppinion.

[gokadzev]

I will definitely review the backup implementation and everything to check if I missed anything. If I find nothing, then I will think about a new solution.

[gokadzev]

Backed up 2 liked songs (+2 recently played songs), and the backup file is 1.39KB. It's possible that JSON or YAML files will be bigger than that due to additional symbols and other factors.

[gokadzev]

That's it, all necessary changes are made. Backup file size will be less than half of current file size in the next release.

[marcossmtp]

Backed up 2 liked songs (+2 recently played songs), and the backup file is 1.39KB. It's possible that JSON or YAML files will be bigger than that due to additional symbols and other factors.

json and yaml has the advantage of clear format to read it and can access your data more easier than with hiven database format, but probably it fill more space about symbols.
yaml is really a very human readable format.
But it was only a idea if database app continues with problems with the backup. Happy to heard that all is ok.
Thanks one more time

[gokadzev]

Backed up 2 liked songs (+2 recently played songs), and the backup file is 1.39KB. It's possible that JSON or YAML files will be bigger than that due to additional symbols and other factors.

json and yaml has the advantage of clear format to read it and can access your data more easier than with hiven database format, but probably it fill more space about symbols. yaml is really a very human readable format. But it was only a idea if database app continues with problems with the backup. Happy to heard that all is ok. Thanks one more time

I'm sure it will lead to lots of problems, including instability and I/O issues. Otherwise, I would definitely consider this feedback and implement it. Since the whole app is working with this implementation without any major problems, it's better if we leave it as it is.

[marcossmtp]

Backed up 2 liked songs (+2 recently played songs), and the backup file is 1.39KB. It's possible that JSON or YAML files will be bigger than that due to additional symbols and other factors.

json and yaml has the advantage of clear format to read it and can access your data more easier than with hiven database format, but probably it fill more space about symbols. yaml is really a very human readable format. But it was only a idea if database app continues with problems with the backup. Happy to heard that all is ok. Thanks one more time

I'm sure it will lead to lots of problems, including instability and I/O issues. Otherwise, I would definitely consider this feedback and implement it. Since the whole app is working with this implementation without any major problems, it's better if we leave it as it is.

ok
the important thing is that things works not the method used to work.
So, It's nice that the backup now works correctly now.