View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0013278 | MMA | Synchronization | public | 2016-05-13 05:57 | 2019-11-10 23:25 |
Reporter | rusty | Assigned To | |||
Priority | high | Severity | major | Reproducibility | always |
Status | assigned | Resolution | open | ||
Target Version | 2.1.0 | ||||
Summary | 0013278: Sync failures on huawei device triggered by track deletion | ||||
Description | So I've figured out how to fix the problem on the Huawei device, and how to replicate it: a) To fix the problem, reboot the device and attempt a usb sync that deletes all tracks from the device without first running MMA (log: line 2700, MMA Log CSNGMP4TUH). Then do multiple USB syncs (adding/removing playlists/tracks) and they will work correctly (verified by running MMA after each sync operation). Sample sync at log line at aprox 5900 line of 'Test list 2' and 'Test list 6 random'. MMA log after successful sync SAHW362HY5. Sample sync that deletes 'Test list 2' at log line 10541. MMA log after successful deletion and sync K12YN7F9WU. b) To trigger the problem, after a USB sync has been done successfully, run MMA, and from within MMA, delete all of the tracks and all of the playlists from the device (MMA log DI288PT67H), then exit MMA (optional) and initiate a USB sync (using the same settings as the previously successful USB sync--i.e. sync the tracks that had just been deleted by the user) (MMW log line 0004677:0014000). --> failed sync (it gets stuck on a track exactly as per the log provided earlier today). Disconnecting the device (which is the only way to terminate the stuck process) sometimes triggers an AV and otherwise indicates that there was a problem synchronizing several audio files and jpgs. Note that once this issue occurs, all subsequent syncs fail and the only way to get synch to work is via Step C (partially fix) or Step A (complete fix). c) At this point, rebooting the device will allow a USB sync to proceed (log line 18217), however, unless the steps described at step a) are performed, the sync operation will often, but not always generate errors in MMW, indicating that some tracks/jpg files could not be copied (the error may not occur at step c) if they've occurred at step b). Proceeding with step a) solves this completely. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in build | |||||
|
This may be related to 0012961, however, I think that something else is going on as well: When I delete tracks from within MMA (CM12 device or huawei device), then the subsequent sync operation will fail _every_time_. On the other hand, if I configure MMW to delete the same playlist/tracks by removing the playlist from the auto-sync list, the operation will usually succeed (tested cm12 device). If this bug is the same as the MTP deletion bug, then why would deletion from within MMA cause more problems than deletion over MTP? Furthermore, if I delete the tracks from the device using ES explorer (tested on CM12), then run MMA and close it, and then do the USB sync operation, it proceeds successfully! It seems to me that MMA is doing something different than ES Explorer in terms of deletion, that results in the MTP instability. |
|
As described over IM: I tested it and ES file explorer behaves the same way. When I delete one file, it is immediately visible over MTP. Folders are problematic and the deletion is not visible over MTP. But it is the same for both ES file and MMA app. I tried to workaround it without success. This is impossible to fix. Each device behaves slightly differently. |
|
Required tests: Whether files/folders are visible over MTP via Windows explorer for: 1) File deletion via ES Explorer 2) File and folder deletion via ES Explorer 3) Deletion via USB sync |
|
Test Note: I tried to replicate this issue on Huawei P20 Lite (Pie) without success. For Test I used latest ES File Explorer Pro from https://www.cyanogenmods.org/es-file-explorer-pro-apk-download/ and https://forum.xda-developers.com/showthread.php?t=2210417 |