View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012070 | MMA | Synchronization | public | 2014-05-28 00:31 | 2014-12-11 23:13 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0.6 | ||||
| Target Version | 1.1.0 | Fixed in Version | 1.1.0 | ||
| Summary | 0012070: Wi-Fi Sync: Sync fails silently and playlists fail to sync if insufficient space is available | ||||
| Description | Currently if using Wi-Fi Sync and sync list provided by MMW is larger than free space MMA just silently finishes sync when device gets full resulting that no playlists are added and User get false Successful sync info. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 353 | ||||
|
|
As reported at ticket TWI-316-76839 the problem is actually a bit worse: Wi-Fi Sync not only fails, it also ignores the setting re. reservation of space on the device! |
|
|
So this problem can be divided into a few components: 1) No valid error message appears--apparently it's been implemented but doesn't appear in the foreground. It should indicate something like: Sync incomplete. Not enough space available on (<storage location>). 2) Playlists fail to sync when storage is insufficient. This shouldn't occur--i.e. Playlists should sync with higher priority than actual media content. 3) Device space settings are ignored. This is tracked separately at 0012138. |
|
|
1) Fixed in build 338 |
|
|
4) Would it be a good idea to preserve a certain minimal amount of space on the drive for working space? e.g. a minimum of 50-100MB unused (I'm wondering if low space is related to other bugs). |
|
|
2) Fixed in build 351 3) Tracked separately 4) We already do this with 20 MB. I have increased it to 50 MB |
|
|
2) Verified 352 3) Build 352 showed that sync failed because only 17MB remained. Shouldn't MMA have reserved at least 50MB? |
|
|
3) Well we do in other way. We test the space before downloading. So I can change it to test it before and somehow include the size of downloaded track. But it won't delete any track, when there is less space, right ? |
|
|
As discussed, a simpler solution would be to bump up the reserved space to 100MB. |
|
|
Fixed in build 353 |
|
|
Verified 353. |
