Author Topic: Wifi android device synching  (Read 428473 times)

trtlcake

  • Newbie
  • *
  • Posts: 4
I have tried to join the google groups but I cannot find it when I search. Can you confirm that it is available? It may be I am searching incorrectly.

kimt1688

  • Jr. Member
  • **
  • Posts: 109
I made a mistake in the settings.
I had left the people who could see the group as the default members only.
After it was pointed out to us, we changed it so that all people can see the group.

Neo_Violence

  • Newbie
  • *
  • Posts: 2
For anyone else who wants to participate: Go to Google Groups, select "All groups and messages " at the top and search for "MusicBee Wifi Sync Test". Then you can join the group.

kimt1688

  • Jr. Member
  • **
  • Posts: 109
Currently, 13 people, not including myself, have joined the Google Group for closed testing.
We need 7 more people to join, as we need 20 people to join and 14 more days of closed testing in order to proceed to the next open test.
If you don't have time to participate in the test, you don't have to test strictly. However, I want you to join the group and have the closed test version of the app installed on your device. Otherwise, you will not be counted as a participant.
It is not yet complete, and the one dropped from my site may be better for practical use.
However, I think I can implement it without MANAGE_EXTERNAL_STORAGE up to reverse sync with GoneMAD.
There are still some improvements to be made in the behavior on devices without SD cards, but I am working on it every day, hoping to have a more decent test version out in the next week or so.


*** Translated with www.DeepL.com/Translator (free version) ***


kimt1688

  • Jr. Member
  • **
  • Posts: 109
I believe I have completed the functional implementation with yesterday's release to the test environment.
I believe that it will work almost without problems, although there are still some bugs due to inadequate testing by me personally.
We need more testers for closed testing to take the next step. We currently have 12 people participating; we need 20.
I do not intend to stop publishing the application on my personal website, but I also do not intend to update it in the future.
I want to do future updates on the Play Store.
Please participate in the test.

Please join the Google Group called "MusicBee Wifi Sync Test".
Once you join,

https://play.google.com/store/apps/details?id=kim.tkland.musicbeewifisync

You can install the test app from the Play Store using the URL


*** Translated with www.DeepL.com/Translator (free version) ***


phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10267
You can install the test app from the Play Store using the URL
Thanks for this.

The good news is that it installed easily on my Samsung tablet and has no issues demanding I use the root directory. 

The bad news is that when syncing (from MB to the device) for every file that is to be deleted from the device, there is a pop-up asking if I will allow MB WiFi Sync to delete the file. I can choose "Deny" or "Allow." It's been quite some time since I performed a sync on this device and there are  17,285 files to be deleted. No one should have to click "Allow" 17,285 times. Especially after it's initial scan, it asked me if I wanted to delete 17,285 files. That one-time ask should be enough.

I can see behind the Deny/Allow window that some syncing is taking place. I can see that it is deleting files and I can see under that line the beginning of the name of the file that is being deleted. So it's working. But the pop-up really interferes with my ability to monitor the sync.

The screen timeout on the device is set for five minutes. But the WiFi app closes after about a minute. Apparently it's still running, but my screen goes black and returns to the home screen. I then have to tap the WiFi Sync app icon to get back to watching the pop-ups.

In addition, at about 5% complete, the app closed and had to be restarted. I could only do that by restarting the tablet.

This most recent time that the app closed and the screen went black and returned to the home screen I did not try to open the app. It appears to be running as MB's status bar is showing progress. In this state, I'm (obviously) not tapping "Allow" as the app isn't on the screen. Yet the sync proceeds. So the continuous asking for permission (other than the first time) is not necessary. But it really should not keep popping-up.

Again, thanks for doing this and I hope you can work out the things I've mentioned. Let me know if there's other information I can provide to get things stabilized.
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10267
The sync has now failed four times and I'm giving up. The most recent sync failed at 80%. But each time I start it again, it asks if I want to delete 17,285 files. So what is it doing during that 80%? It's not deleting files even though it says it is. And and if it's waiting for me to tap "allow," that's not going to happen 17,285 times.
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

BoringName

  • Sr. Member
  • ****
  • Posts: 916
I think those issues will be due to the file permission changes for scoped storage. You can give permission for the app to access an individual file which is what it seems to be doing with the popup. It's asking individual permission for each file to delete it. I have a gallery app that does a similar thing, but that one gives you the choice of giving permission to the individual photo or the whole folder.

Changing it to just prompt for permission of the main music folder should be possible.

kimt1688

  • Jr. Member
  • **
  • Posts: 109
Even files copied via wired Sync with MusicBee are treated as files created and managed by a different app under Scoped Storage, so you are surely changing access rights when deleting or overwriting.
However, I'm trying not to pop up and in fact I don't in my environment.
I am sure that the Scoped Storage process is not optimal and is affecting performance, causing it to terminate abnormally in the middle of the process, but the fact that the popups are on every file is a completely different issue.


*** Translated with www.DeepL.com/Translator (free version) ***


phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10267
Thanks for the feedback.

I have checked the permissions on the tablet and all permissions were/are allowed. I have just started another sync and the pop-ups still occur as does the closing of the app even though the syncing appears to be taking place per MB's status bar.
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10267
Per MB's status bar, the sync reached 99% and stayed there for about five minutes before failing. And no files appear to have been transferred as the music folder and playlists folder are empty.
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

kimt1688

  • Jr. Member
  • **
  • Posts: 109
The closed test on the Google Group "MusicBee Wifi Sync Test" is still ongoing.
The reason for this is that there are still bugs and the number of people has not been met.
And today I released a new version to the test environment.
That app will only support Android 14, per Google's request.
Google says that an OS that has been released for a year is no longer supported.
I will keep up with the new environment as long as I can.
Your cooperation in testing is appreciated.

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10267
Your cooperation in testing is appreciated.
You're welcome. Let's hope we (you) can get this working in the not too distant future. I will download the latest version to my tablet tomorrow and report back.
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

BoringName

  • Sr. Member
  • ****
  • Posts: 916
That app will only support Android 14, per Google's request.
Google says that an OS that has been released for a year is no longer supported.

I don't think this is accurate. I have plenty of apps installed from the play store that support 6.0 and up.

When you update an app, there is a minimum android API level it needs to support to be accepted in the play store. As of 31/08/24 this needs to be API level 34 (Android 14). I think this might be where you are getting confused. I don't think there is a limit on what older versions you can support. It's just more work adding code to support older versions. My SMS app supports 5.0 and up.

kimt1688

  • Jr. Member
  • **
  • Posts: 109
That app will only support Android 14, per Google's request.
Google says that an OS that has been released for a year is no longer supported.

I don't think this is accurate. I have plenty of apps installed from the play store that support 6.0 and up.

When you update an app, there is a minimum android API level it needs to support to be accepted in the play store. As of 31/08/24 this needs to be API level 34 (Android 14). I think this might be where you are getting confused. I don't think there is a limit on what older versions you can support. It's just more work adding code to support older versions. My SMS app supports 5.0 and up.

I believe this is not a misunderstanding or my confusion, but a condition imposed because I am a new app developer who created an account for MusicBee Wifi Sync.

Shortly after I started this project, I targeted Android 13 and 14, but I submitted a release request to Google for Android 12+ with the understanding that with a few improvements it would be compatible with Android 12.

Google then immediately rejected the request, saying that Android 12 was an old OS and could not be accepted.

I believe the situation is similar for this Android 13 and below OS.

So I chose to release the app as an application that is compatible only with Android 14.