ipod not longer goes into disk mode when usb charging

[crescentfresh]

I plugged my usb cable into my 60 gig ipod photo while it was playing a few minutes ago.  It started charging, but did not go into disk mode, which was great.  However, I then wanted to dump some files on it, and my computer wasn't recognizing it as a hard drive.  I unplugged the player, stopped playing my music, then plugged in the usb cable again.  Even when music was no longer playing, it started charging without going into disk mode.  I then shut the ipod completely down, plugged in the usb cable, and it booted up into the regular menu again, not disk mode.  Is there something I need to do to have the player go into disk mode by default again when plugging the usb cable in?  I know how to manually get into disk mode, but just found this behavior strange, so I thought I'd post here for others thoughts.

I've check the manual, as well as poked around the forums via search, and did not find anything, so it would be appreciated if we just skipped over the typical "Try reading the manual or searching forums" remarks.

[AlexP]

I don't know the answer to your problem, but

I've check the manual, as well as poked around the forums via search, and did not find anything, so it would be appreciated if we just skipped over the typical "Try reading the manual or searching forums" remarks.

are only given when that is what the poster needs to do.

[Chronon]

Is it possible that your cable went bad?  Does it connect properly if you manually enter Disk Mode (or boot the Apple firmware)?  If so, then it sounds like a bug.

[crescentfresh]

No, the cable's not bad.  It recognizes when I plug it in, and puts the little charging icon in the top left corner.  I just went manually into disk mode and plugged the cable in as well, and it's charging this way now too.

[v497]

Hi, everyone.

I actually seem to have the same problem(?) on my 5G (60 gig) iPod Video.

Haven't used it for a few days, wanted to update to the latest build, but it didn't boot into disk mode anymore.. whenever I plug in the cable, it boots into the Rockbox menu and stays there, charging.

Manually booting into disk mode works. The player was running r19824, I have updated it to the latest build now, but it still doesn't automatically go into disk mode on plugging the cable in. Is this intended behavior?

[saratoga]

You don't charge over the data lines, so just because its charging doesn't mean the cable is good.   Worth checking, but it seems a little unlikely.

[crescentfresh]

You don't charge over the data lines, so just because its charging doesn't mean the cable is good.   Worth checking, but it seems a little unlikely.

When I manually put it into disk mode (the only way I can get my computer to recognize it as an external hard drive), I just successfully pulled files off and added new files to the ipod, so the cable appears to be fine.

Anything else I can do to help diagnose the issue?

[elitenoobboy]

It's an actual bug, not a cable problem. I had the reverse of it (http://forums.rockbox.org/index.php?topic=20242.msg143118) until one of the releases a few days ago switched it around.

[Zardoz]

Hi. I'm having the same problem. The most recent build I installed (r19865 for ipod 5.5 80GB.) does not boot to disk mode automatically. I entered disk mode manually and reinstalled r19822 which froze after i ok'd 'to disconnect.' Restarted but no change and after manually entering disk mode again installed r19752 which was the last revision I remember specifically downloading. and in spite of freezing on disconnect, as above, it did enter disk mode automatically when reconnected a minute or so later. I haven't tried any builds in between. Does this relate to work on the USB stack? Incidentally Rockbox itself was fine on those more recent builds and in fact seemed more responsive if anything, with button presses and menu navigation and the like.  Z

[Chronon]

Then someone should file a bug report.  If you can figure out which build introduced this behavior that would be ideal.

[Zardoz]

OK will try. If a problem was reported and it was deemed irrelevant or unconsidered, then my reports will mean nothing to you. Should I still report them? I'll personally try each build since and feedback on each. You seem to consider my opinions 'criticism'. Sorry for wasting your time...

[AlexP]

OK will try. If a problem was reported and it was deemed irrelevant or unconsidered, then my reports will mean nothing to you. Should I still report them? I'll personally try each build since and feedback on each. You seem to consider my opinions 'criticism'. Sorry for wasting your time...

Where on earth has anyone said any of that?  Don't be rediculous.  Of course we want bugs reported, we just try to eliminate other possible factors such as bad cables or user error first, as quite a lot of "bugs" turn out to be one of those.

Here, we have eliminated the cable and user errors as the reason, so it looks like there is indeed a bug.  Chronon has asked one of the people suffering from it to report it on Flyspray (the bug tracker) as it is usually a good idea that the one with the problem reports it so that they presumably can describe it.  In addition, it would be brilliant if one of the people suffering from this could try and find out in what build the problem started - if developers do not suffer from this then they can't find it themselves, and without some clue on when it started it is like looking for a needle in a haystack.

[crescentfresh]

The first daily build this appears on is 1-23-09, Rev. 19822.  I've never used flyspray before, but will type something up for this and submit it.

[Chronon]

Thank you.   

[crescentfresh]

Actually, would you say this is the same bug as reported in FS#9831?  Would it make more sense for me to add a comment to that bug to say it's happening on the 4G ipod color/photo rather than opening a new one?