|
|
Reminder sent to: jiri, marek, rusty
As talked on IM with Marek.
This is standing known bug for some time as discussed with Marek and Ludek. It interfere with sync time considerably, even it crashed MMA/Sync in earlier builds (fixed with some other sync fixes)
Rusty, Jiri
Opening this bug for immediate fix. Can you please triage.
|
|
|
Ludek
2012-11-24 12:45
developer
~0033352
Last edited: 2012-11-24 12:46
|
I don't think that disabling the profile remotelly in MMA is needed.
I think that only that needs to be fixed is that disabling the profile in MMW should deny WiFi access, i.e. it should behave same as disabling the [ ] Grant remote access... checkbox.
Rusty, Jiri, do you agree?
If yes, then please change the project from MMA->MMW and assign to me for fix.
|
|
|
|
Peke, can you please clarify what the bug is (I don't have a device that can replicate this scenario). i.e. what does MMA/MMW currently do when attempting to sync with a device profile that is disabled? Is the bug that it recreates a new one?
Ludek's proposal seems to make sense, but I don't really understand the bug... |
|
|
|
As many users requested that a must feature from Android app is that they are able to disable sync to internal storage and use only external storage, I have tested with disabled Internal storage of my phone (it can be tested with any device that report two different available sync storage and MMW creates two profiles) shot00063.jpg
In earlier builds when trying to sync MMA crashed with timeout (Marek fixed that with my debugging) and it was left to Ludek (according to Marek talk with him) to implement MMW part where MMA will know to skip storage disabled in MMW.
My proposal is to implement same thing in MMA that way Sync should be faster as MMA will not wait for reply from Sync Server and profiles set on MMW but will not even initiate Sync on disabled storage no matter what MMW settings are and is profile enabled/disabled.
Test Results with 64 and 1607: Although MMA do not crash it ignores MMW disabled state and still sync with error. Additionally analyze part takes 10 Minutes even previous setting for internal storage (while it was enabled) only sync 5 tracks.
Re Ludek Proposal: I would rather say it is workaround rather than actual fix/feature, but it will do the job as MMW disable Remote access rights for that profile, but what If User wants to keep Remote access enabled but just temporarily disable plugin for current sync? |
|
|
|
If I understand correctly repro steps/bugs are:
1 Attempt to wirelessly sync device with internal memory + external card
--> Multiple device profiles are created 'internal' + 'external'
2 User configures device profile for external card and initiates wifi sync via MMA
--> Both profiles attempt to sync even though one of them hasn't been configured at all (i.e. nothing is in the sync list for the 'internal' profile), and as a consequence performance is very slow!!
3 User goes to MMA and tries to disable/delete the internal profile
--> There is no means to do so!!
4 So... user disables the profile in MMW
5 User initiates sync in MMA
-->Both profiles still try to sync despite one being disabled!!
Is that right? Are the bugs described at steps 2/3/5 represent what you're trying to describe?
Also, are the problems specific to wifi sync, or are you saying that they also occur with a direct usb connection? |
|
|
|
2. If there's really nothing configured to be synced and also bi-di sync isn't enabled, we really should try to skip sync to this storage quickly.
3. We probably could add a checkbox, either to each storage on the main page, or next to 'Auto sync to this device' on each storage config page.
5. Would be fixed by 3. |
|
|
|
2. Even user initially setup Storage and later decide to disable, logically it should be skipped/ignored no matter of Bi-di sync or majebe just properties/play counts are sync back.
6. Additionally it could be also valuable to make MMA ignore tracks on Disabled storage in fix 3. eg. I put Ringtones on internal and all media on SD card which implies that I do not like to hear SMS, Ringtones in random playback of whole library (it happened to me today and I got several 3 sec tracks annoying me in now playing) |
|
|
rusty
2012-11-26 22:49
administrator
~0033392
Last edited: 2012-11-27 20:47
|
Per discussion with Jiri, in order to completely avoid Wifi Sync for the internal device, it would have to be explicitly disabled. So, re. item:
2. We should maximize performance for this case
3. We need to add checkboxes for the different storage locations. e.g.
<Nexus 7 Internal Storage>
Sync to this location [ ]
You can configure basic settings....
Auto-sync to the server [ ]
....
Auto-sync to this device
....
....
....
Presumably, the first checkbox would be enabled by default and/or for any pre-existing sync profiles, except in the case when multiple storage locations appear for a device, and they haven't been preconfigured, in which case only the external location will be enabled?
|
|
|
rusty
2012-11-27 06:00
administrator
~0033399
Last edited: 2012-11-27 20:54
|
Upon further discussion with Marek, it was decided that the only possible solution is to allow the user to manually choose the location to which files should be synced.
To effect that:
1) Dialog will appear after a new Server is found, in cases where > 1 sync location exists:
Choose where to sync your media files:
( ) loc1
( ) loc2
[OK] [Cancel]
[OK] --> Sync Settings dialog for <locx>
[Cancel] --> Options dialog
2) Options dialog will have a minor modifications to better support multiple sync locations:
i Change 'Sync Settings' --> 'Sync Location/Settings'
|
|
|
martin
2012-11-28 14:35
developer
~0033450
Last edited: 2012-11-28 14:35
|
Fixed in build 66.
|
|
|
|
Just partially fixed |
|
|
|
Fixed in build 67 |
|
|
|
MMW doesn't process that storage was enabled/disabled in MMA. I.e. when settings are sent to MMW with Visible element set to 0, it remains enabled in MMW and when I refresh MMA settings, I get Visible set to 1 from MMW |
|
|
|
Fixed a tweak on MMW side in build 1609, but there was a bug on MMA side too, assigning to Marek to fix... |
|
|
|
Fixed in build 67 |
|
|
|
Verified 74 |
|
