by sordup » Sat Feb 11, 2023 3:18 pm
I have a new (to me) phone (Pixel 4a 5g) with a lot of space on it, for a phone, and have been in the process of syncing some music to it from MMW5 (I have MM for Android on the phone as well). It was going along swimmingly transferring about 20 gigs already in a couple of sync sessions yesterday and today, and now suddenly when trying to sync some more (there is 45gb left on the device), I continue to get, first the "media transfer process frozen" error message, and then this...
and then this...
I have rebooted, both Windows and Android several times, tried different USB cables, disabled then re-enabled USB file transfer on phone, opened MM with the phone already plugged in and alternately plugged the phone in after starting MM, all to no avail. What yesterday (and this morning) worked so well now is dead in the water. There were no changes to the system on either machine in the interim.
I am using MMW5 version 5.0.4.2690 on a updated Windows 10 machine.
What could be going on?
I have a new (to me) phone (Pixel 4a 5g) with a lot of space on it, for a phone, and have been in the process of syncing some music to it from MMW5 (I have MM for Android on the phone as well). It was going along swimmingly transferring about 20 gigs already in a couple of sync sessions yesterday and today, and now suddenly when trying to sync some more (there is 45gb left on the device), I continue to get, first the "media transfer process frozen" error message, and then this...
[img]https://i.imgur.com/6A4d38D.png[/img]
and then this...
[img]https://i.imgur.com/VDKny6v.png[/img]
I have rebooted, both Windows and Android several times, tried different USB cables, disabled then re-enabled USB file transfer on phone, opened MM with the phone already plugged in and alternately plugged the phone in after starting MM, all to no avail. What yesterday (and this morning) worked so well now is dead in the water. There were no changes to the system on either machine in the interim.
I am using MMW5 version 5.0.4.2690 on a updated Windows 10 machine.
What could be going on?