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

kimt1688

  • Jr. Member
  • **
  • Posts: 109
I think the conversion can be implemented in a few days and can be beta released (open tested), but if indeed the cause is as expected, I cannot predict how the file names will be converted. Especially the EMOJI issue.
If the Wifi App has converted them, then the next Wired Sync may have other problems.
Thanks, I can test it. Is joining the beta on play store enough or will the apk be posted here or on your site?

The beta version will be available on the Play Store, so please register as a beta tester.

kimt1688

  • Jr. Member
  • **
  • Posts: 109
I think the conversion can be implemented in a few days and can be beta released (open tested), but if indeed the cause is as expected, I cannot predict how the file names will be converted. Especially the EMOJI issue.
If the Wifi App has converted them, then the next Wired Sync may have other problems.
Thanks, I can test it. Is joining the beta on play store enough or will the apk be posted here or on your site?

The beta version will be available on the Play Store, so please register as a beta tester.

I am trying to fix and debug a large playlist process, but the MusicBee side is time out.
It seems like it is taking a long time to convert from mbp (MusicBee native format playlist) to m3u (the playlist format used on the device side) and during that time it is time out.
The Wifi App is not receiving anything, it is receiving an EOF before the playlist itself comes in and the process is terminated.
I will continue to debug this a bit more, but it may be difficult to fix the Wifi App by itself!

kimt1688

  • Jr. Member
  • **
  • Posts: 109
I think the conversion can be implemented in a few days and can be beta released (open tested), but if indeed the cause is as expected, I cannot predict how the file names will be converted. Especially the EMOJI issue.
If the Wifi App has converted them, then the next Wired Sync may have other problems.
Thanks, I can test it. Is joining the beta on play store enough or will the apk be posted here or on your site?

The beta version will be available on the Play Store, so please register as a beta tester.

I am trying to fix and debug a large playlist process, but the MusicBee side is time out.
It seems like it is taking a long time to convert from mbp (MusicBee native format playlist) to m3u (the playlist format used on the device side) and during that time it is time out.
The Wifi App is not receiving anything, it is receiving an EOT before the playlist itself comes in and the process is terminated.
I will continue to debug this a bit more, but it may be difficult to fix the Wifi App by itself!

I show the debug log.
5.2kB 547tracks
Code
Music/Playlists/BOOWY.m3u
2025-02-14 03:52:37.876 30415-30486 Update ContentUri:      kim.tkland.musicbeewifisync          D  content://media/6534-6335/audio/playlists/1000209020
2025-02-14 03:52:37.968 30415-30415 Compatibil...geReporter kim.tkland.musicbeewifisync          D  Compat change id reported: 78294732; UID 10675; state: ENABLED
2025-02-14 03:52:56.615 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): bytesRead == 1448
2025-02-14 03:52:56.615 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): remainingBytes == 33097
2025-02-14 03:52:56.616 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): bytesRead == 10136
2025-02-14 03:52:56.617 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): remainingBytes == 22961
2025-02-14 03:52:56.618 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): bytesRead == 2896
2025-02-14 03:52:56.619 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): remainingBytes == 20065
2025-02-14 03:52:56.625 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): bytesRead == 5792
2025-02-14 03:52:56.625 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): remainingBytes == 14273
2025-02-14 03:52:56.626 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): bytesRead == 14273
2025-02-14 03:52:56.626 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): remainingBytes == 0
2025-02-14 03:52:56.629 30415-30524 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): break at bytesRead <= 0

36.3kB 3107tracks
Code
 Receive: Music/Playlists/iPod Playlist.m3u
2025-02-14 03:52:57.082 30415-30486 Update ContentUri       kim.tkland.musicbeewifisync          D  Music/Playlists/iPod Playlist.m3u
2025-02-14 03:52:57.082 30415-30486 Update ContentUri:      kim.tkland.musicbeewifisync          D  content://media/6534-6335/audio/playlists/1000226743
2025-02-14 03:55:00.875 30415-30584 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): bytesRead == 7
2025-02-14 03:55:00.875 30415-30584 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): remainingBytes == 255273
2025-02-14 03:55:00.908 30415-30584 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): bytesRead == -1
2025-02-14 03:55:00.909 30415-30584 WifiSync                kim.tkland.musicbeewifisync          I  ReceiveTextFileReceiveLoop(): break at bytesRead <= 0
2025-02-14 03:55:00.913 30415-30486 WifiSync                kim.tkland.musicbeewifisync          E  receiveFile: java.net.SocketException: Error reading file: file=Music/Playlists/iPod Playlist.m3u
2025-02-14 03:55:00.916 30415-30486 WifiSync                kim.tkland.musicbeewifisync          I  

The first is an example of success.
The second is an example of one that fails.
I have been adjusting various things such as timeouts and buffer sizes, and now I get this error.
Note that under some circumstances, this “iPod Playlist.m3u” playlist may succeed, and in that case, I can reproduce it with a playlist, 439.5kB, 38449 tracks, which contains all of my library.
MusicBee's error log records a timeout.
The Wifi App timeout value is set to Zero, which is a no timeout situation on the app side.

ADD Writing

Converting the contents of the log to a String after "ReceiveTextFileReceiveLoop(): bytesRead == 7", it looks like this

Code
readArray(): ??Exit
readArray(): 0004457869741B
Last Edit: February 14, 2025, 12:52:42 PM by kimt1688

c0sb0rne

  • Jr. Member
  • **
  • Posts: 37
@kimt1688 i found an older post related to a system out of memory exception specifically for the windows application: https://getmusicbee.com/forum/index.php?topic=42284.0
Could this be related in any way?

kimt1688

  • Jr. Member
  • **
  • Posts: 109
As for updating the playlist, we can now do it even with a large playlist (tested with 38k tracks).
As for new copies, please give me a little more time.
I will be able to speed up the process with this fix as well.


kimt1688

  • Jr. Member
  • **
  • Posts: 109
I think the conversion can be implemented in a few days and can be beta released (open tested), but if indeed the cause is as expected, I cannot predict how the file names will be converted. Especially the EMOJI issue.
If the Wifi App has converted them, then the next Wired Sync may have other problems.
Thanks, I can test it. Is joining the beta on play store enough or will the apk be posted here or on your site?

The beta version will be available on the Play Store, so please register as a beta tester.

I am trying to fix and debug a large playlist process, but the MusicBee side is time out.
It seems like it is taking a long time to convert from mbp (MusicBee native format playlist) to m3u (the playlist format used on the device side) and during that time it is time out.
The Wifi App is not receiving anything, it is receiving an EOF before the playlist itself comes in and the process is terminated.
I will continue to debug this a bit more, but it may be difficult to fix the Wifi App by itself!

The beta version has been released to the store, although there are still some instabilities in new copies.
It will take some time before it can be released and used.
Playlist update speed has been increased regardless of size.
In testing, I have also successfully copied all of my library, a 38k track playlist (2.9MB M3U file).

c0sb0rne

  • Jr. Member
  • **
  • Posts: 37
Nice! I'll test out the Beta version once it's available on my device with Steven's latest 3.6 patched update.
Thanks again @kimt1688 for all your efforts!
Last Edit: February 16, 2025, 03:30:42 PM by c0sb0rne

ACardAttack

  • Jr. Member
  • **
  • Posts: 33
Emojis were my issue, removed the files with them, which is weird as it was never an issue before Android 15

c0sb0rne

  • Jr. Member
  • **
  • Posts: 37
I think the conversion can be implemented in a few days and can be beta released (open tested), but if indeed the cause is as expected, I cannot predict how the file names will be converted. Especially the EMOJI issue.
If the Wifi App has converted them, then the next Wired Sync may have other problems.
Thanks, I can test it. Is joining the beta on play store enough or will the apk be posted here or on your site?

The beta version will be available on the Play Store, so please register as a beta tester.

I am trying to fix and debug a large playlist process, but the MusicBee side is time out.
It seems like it is taking a long time to convert from mbp (MusicBee native format playlist) to m3u (the playlist format used on the device side) and during that time it is time out.
The Wifi App is not receiving anything, it is receiving an EOF before the playlist itself comes in and the process is terminated.
I will continue to debug this a bit more, but it may be difficult to fix the Wifi App by itself!

The beta version has been released to the store, although there are still some instabilities in new copies.
It will take some time before it can be released and used.
Playlist update speed has been increased regardless of size.
In testing, I have also successfully copied all of my library, a 38k track playlist (2.9MB M3U file).

@kimt1688 The beta became available for my device today. I successfully synced all 5 playlists without timeouts or errors (39k tracks), and the reverse playcounts updated Musicbee as expected.
This latest version appears to be much faster compared to the previous wifi sync app. Great work as always!

kimt1688

  • Jr. Member
  • **
  • Posts: 109
Emojis were my issue, removed the files with them, which is weird as it was never an issue before Android 15

https://i.imgur.com/yolK4Pn.png

EMOJI It is taking a long time to work on the file name.
I am able to get to the preview, but it takes a bit of time until the screen comes up.
Please wait a little longer for file sync and processing time tuning.
I think I can solve the UTFDataFormatException at the same time.
Please give me some time to get a version ready for public release and I will put it out to a closed test environment.

kimt1688

  • Jr. Member
  • **
  • Posts: 109
Emojis were my issue, removed the files with them, which is weird as it was never an issue before Android 15

https://i.imgur.com/yolK4Pn.png

EMOJI It is taking a long time to work on the file name.
I am able to get to the preview, but it takes a bit of time until the screen comes up.
Please wait a little longer for file sync and processing time tuning.
I think I can solve the UTFDataFormatException at the same time.
Please give me some time to get a version ready for public release and I will put it out to a closed test environment.

Version 2.7.13 has been released for closed test environment.
I was working on EMOJI filename support, but could not complete the support and decided to release a version that can avoid UTFDataFormatException in the process.
I don't think there is an error about EMOJI filenames, but there is still a phenomenon where the file goes to be copied many times even though it has already been copied to the device.
I have confirmed that the EMOJI filename looks fine in the filer and that it can be played back in GoneMAD.
Since I don't want to stop the public release of the recent beta release (2.7.11) and I don't know how many people will need it, I decided to release it to a closed test environment.
You should be able to use this version by going to your Google group site and searching for “MusicBee Wifi Sync Test” and joining.
As with the previous beta version (2.7.11), please make sure you have the latest patched version of MusicBee.

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

kimt1688

  • Jr. Member
  • **
  • Posts: 109
Version 2.7.14 has been uploaded to the closed test environment. It will be available in a few days.
All problems with emoji filenames have been resolved in this version.
No more copying every time, no more trying to delete files with corrupted names, no more inability to reverse sync.
Please use RC2 or newer patched version of MusicBee when testing.

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10266
@kimt1688...

Does the latest non-beta version from the Play Store still need MiXplorer to work? The WiFi app I'm currently using was a compiled APK that you or someone else made available late 2023. It works  well and I don't need play counts nor reverse syncing - just music and playlists from the PC to the Android.

I'm assuming the latest version doesn't need MiXplorer as I've seen no mention of it lately and I'd like to get it off my phone if no longer needed for the WiFi Sync app to work.

How stable is the latest beta vs the current release?

Thanks for keep this alive.
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
MixPlore is no longer needed.
I officially started development and registered it with Google in May 2024, so an apk from 2023 is not mine if it was installed via the store.
If the latest beta does not install, you may go to the play store, delete cache and storage to see the latest.

As for stability between the beta and the official version, I think the beta has the advantage including speed.
However, I have not made the official version because it requires MusicBee RC2.
Last Edit: March 02, 2025, 03:58:05 AM by kimt1688