The device node in the Media Tree has gone awol several times ... ie. the open that is created when attaching the device by usb.
When it goes missing it is hard to get back.
These *didn't* work today:
* plug and unplug the usb cable
* swap to a different usb port
* close & restart MMW
This did work:
* reboot the tablet.
Any idea what triggers this? Has happened to me today & yesterday.
Any easier way of getting it back, other than rebooting the device?
MMW 4.1.0.1662
MMA: 1.0.4.0.0168
Device node can go awol
Moderator: Gurus
Device node can go awol
Want a dark skin for MM5? This is the one that works best for me .. elegant, compact & clear.
Re: Device node can go awol
You should capture this in a debug log (step 4b) and send it to support: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: Device node can go awol
OK, I will look at doing that soon.
Am not sure how to trigger the issue. I think that it may be caused by taking the MM "Synch Device" autoplay option on the dbox that Windows throws up when you plug the device into the usb port.
The option doesn't seem to accomplish anything, and it seems to cause the effect I described.
Am not sure how to trigger the issue. I think that it may be caused by taking the MM "Synch Device" autoplay option on the dbox that Windows throws up when you plug the device into the usb port.
The option doesn't seem to accomplish anything, and it seems to cause the effect I described.
Want a dark skin for MM5? This is the one that works best for me .. elegant, compact & clear.
Re: Device node can go awol
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: Device node can go awol
That's a big thread. Which part were you meaning?Lowlander wrote:Could it be: http://www.mediamonkey.com/forum/viewto ... 03#p375103
I don't have a SD card (it is Nexus 7 tablet).
And I don't have have any the script that the thread seems to be focused upon.
Want a dark skin for MM5? This is the one that works best for me .. elegant, compact & clear.
Re: Device node can go awol
If only tablet reboot helps then I am afraid that it is something on the PC connection (WMDM) layer and is not fixable within MediaMonkey.
If the device disappears, is it still accessible via Windows Explorer? I guess that it is not?
If the device disappears, is it still accessible via Windows Explorer? I guess that it is not?
Re: Device node can go awol
Sorry my error.
Looks like the tablet, unlike two pc's on a lan, can't be in screen saver mode, or whatever it is called in Android. ... ie I need to unlock the tablet 1st?
And it has to be unlocked *before* plugging in to the usb port. ... ie. unlock after plugging in doesn't seem to work for MM, although it is ok for Explorer.
If this is the case, it seems to working ok for me now.
Looks like the tablet, unlike two pc's on a lan, can't be in screen saver mode, or whatever it is called in Android. ... ie I need to unlock the tablet 1st?
And it has to be unlocked *before* plugging in to the usb port. ... ie. unlock after plugging in doesn't seem to work for MM, although it is ok for Explorer.
If this is the case, it seems to working ok for me now.

Want a dark skin for MM5? This is the one that works best for me .. elegant, compact & clear.
Re: Device node can go awol
The post I directly linked to. Advanced Duplicate Find & Fix and the latest beta of MediaMonkey 4.1 can cause errors/crash when accessing a portable device.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)