I don't have access to this device, so it is a bit difficult to tell what is going on. The following would be helpful in debugging the problem:
1. could you attach the log file (~/.cache/upstart/mediascanner-2.0.log).
2. If you run "restart mediascanner-2.0" from the terminal or an "adb shell" session, does anything show up? If so, it might be an issue of detecting when new volumes are mounted at runtime, as opposed to volumes already mounted when the service starts.
I don't have access to this device, so it is a bit difficult to tell what is going on. The following would be helpful in debugging the problem:
1. could you attach the log file (~/.cache/ upstart/ mediascanner- 2.0.log) .
2. If you run "restart mediascanner-2.0" from the terminal or an "adb shell" session, does anything show up? If so, it might be an issue of detecting when new volumes are mounted at runtime, as opposed to volumes already mounted when the service starts.