View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020415 | MMW 5 | Sync | public | 2023-11-22 19:56 | 2023-12-05 10:20 |
| Reporter | peke | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | duplicate | ||
| Target Version | 5.2 | ||||
| Summary | 0020415: MM5 stalls on sending data causing MMA WiFi sync fail with timeouts | ||||
| Description | MMA WiFi sync fail with timeouts when MM5 stalls on sending data and completely stops responding to MMA calls. MMA and MM5 Logs from 0020412 should reveal exact point where MMA <-> MM5 stopped communicating sync status and why. Possible point is MM5 showed dialog not enough space to convert all tracks. Expected behavior would be that MMA throw MM5 error on Sync fail. This is especially important in case MM5 is installed and started as Service where user interaction on MM5 is not possible. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
| duplicate of | 0020412 | resolved | Ludek | MMW 5 | Sync Fail on Pixel 8 Pro Using Surface Tablet from 2017 |
| related to | 0012440 | closed | Ludek | MMW v4 | No feedback to user that temp drive has insufficient free space |
| related to | 0020416 | resolved | martin | MMA | MMA WiFi sync fail with timeouts when MM5 stalls on sending data |
|
|
Sounds like dup of 0020412 -- so let's solve it in 0020412 |
|
|
It is not duplicate of 0020412 but closely related to 0020416 Where MM5 shows Dialog no space to convert files and MMA timeouts sync. Point of 0020415 and 0020416 that MMA fail with verbose error letting user know why things fail. As pointed MM5 started as Service will not show any dialogs, but will lock MM5 and user will not know why MMA sync fail. |
|
|
Moving to 5.2 and decreasing priority as the combination of having MM5 running as service and not having enough space to convert a single file is not common.. |
|
|
The idea (to not break compatibility with older MMA) described in 0020416, so moving there... |
