View Issue Details

IDProjectCategoryView StatusLast Update
0011826MMASynchronizationpublic2014-09-28 01:23
Reporterlowlander Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status closedResolutionfixed 
Product Version1.0.4 
Target Version1.0.4Fixed in Version1.0.7 
Summary0011826: Wifi Sync fails on BLU DASH
DescriptionI did a successful sync, then did a second sync that included more items and it failed and MMA jumped to home screen. Debug log (capturing both syncs) on FTP.

MMA log 4RST732FQ (several others have been submitted from this device over the past week).
TagsNo tags attached.
Fixed in build304

Relationships

related to 0011825 newLudek MMW v4 USB connect creates new Device Profiles 

Activities

lowlander

2014-02-02 18:52

developer   ~0039482

It seems that the Audiobooks Playlist is causing problems. I disabled it for sync and added another Playlist and sync worked. Any clues in log as to why Audiobooks fails to sync?

marek

2014-02-06 16:38

developer   ~0039524

It seems to be related to really long list of tracks for autoconversion. And it looks like it occurs when you turn off the phone (or maybe the screen times out). There is an issue that is most probably in implementation of sqlite database.

But could you please try to generate new log. I want to verify my assumption. Thanks.

lowlander

2014-02-06 16:50

developer   ~0039525

Should I only sync the Audiobook Playlist (it seems to be the one failing) or do the full sync for the log?

It seems that although MMW is auto-converting files that MMA is stuck on the downloading... screen which is the screen prior to the screen showing the actual files being downloaded.

marek

2014-02-07 10:15

developer   ~0039530

Well yes, that is the phase when it fails.

I need a second log, but it might be with the same synclist. I think that in your case it is related to number of autoconversions. So you can try it with the audiobooks only. But I don't know whether it occurs. It doesn't matter what you will sync. I just need another log from failed sync.

lowlander

2014-02-09 03:48

developer   ~0039541

Last edited: 2014-02-09 03:50

It is syncing right now, which means it has gotten further than normally (with Audiobooks enabled).

In this case I kept the screen alive and it spend several minutes on the Downloading, preparing download... screen. Much longer than my Samsung phone (which has several complex AutoPlaylists to prepare). However it's set to sync more files (0000323:0002500 vs. 0000198:0001000 on the Samsung).

So your hunch of screen time out during Downloading, preparing download... screen as the source of the failure may be correct.

lowlander

2014-02-09 22:01

developer   ~0039542

Sync seems to have run fine (device was off due to low battery when I returned). Do you need me to try to let sync fail by letting screen time out? If so should I let screen timeout during Downloading state?

marek

2014-02-10 09:43

developer   ~0039544

Yes, that would be great.. I have no idea why it might be related to screen timeout but it looks like it is. We have to inspect the code. But new log that confirms it will be very helpful.

lowlander

2014-02-11 05:30

developer   ~0039555

Ran a new test where I kept screen alive till delete confirmation. Sync was successful (most files including Audiobooks were already on device).

marek

2014-09-25 05:13

developer   ~0040564

Fixed in build 304

It was already fixed and there were changes in SQLite database that helped to fix it too.

peke

2014-09-28 01:23

developer   ~0040612

Verified 303