Skipping to next time several times causes Scrobbledroid to crash

[GoogleCodeExporter]

When using the android music player in Party Shuffle mode and you listen to
a couple of seconds of song, then hit the next track button several times,
this causes scrobbledroid to crash. Then Android asks if you want to force
it to close because it is not responding. 

Original issue reported on code.google.com by jtempl...@gmail.com on 30 Mar 2009 at 6:45

[GoogleCodeExporter]

Hi there. Thanks for the report.

I can't seem to duplicate this. Does it happen every time for you? Do you have 
to
press the next track button rapidly, or do you let each track play for a few 
seconds?

Original comment by jjc1...@gmail.com on 30 Mar 2009 at 9:27

• Added labels: Type-Bug
• Removed labels: Type-Defect

[GoogleCodeExporter]

It seems to happen randomly, not every time. I usually let the song play for 
about a
second, then I skip. Usually after 7-8 skips is when I get that error. Having it
scrobble after every track usually makes it happen/increases the chance. It's 
as follows:

Sorry!
The application Scrobble Droid (process net.jjc1138.android.scrobbler) has 
stopped
unexpectedly. Please try again.

Thank you! Your works is very much appreciated!

Jason

Original comment by jtempl...@gmail.com on 30 Mar 2009 at 10:20

[GoogleCodeExporter]

Thanks for the extra details. Do you have any WMA format songs on your phone? 
It's
been reported that that makes Scrobble Droid crash.

If you'd like, you can get the log file from the phone, which should help me 
track
down the problem. The process is a big laborious, though:

1) On the phone go to Settings / Applications / Development and switch on the 
option
"USB debugging".
2) On your PC download this file:
http://jjc1138.net/AndroidLogFetcher.zip
and unzip it to a directory somewhere.
3) Connect your G1 to the PC. The "Found New Hardware Wizard" should appear.
4) Select "No, not this time" / Next / "Install from a list or specific location
(Advanced)" / Next
5) Select "Search for the best driver in these locations" and "Include this 
location
in the search:" and then "Browse" and find wherever you unzipped the file above.
6) Click "Finish" and wait for the driver to install.
7) Use the music player until you see the "Scrobble Droid (process
net.jjc1138.android.scrobbler) has stopped unexpectedly" error.
8) On your PC run the file "Fetch Log.cmd".
9) In a second or two that should generate a new file "Log.txt". Please e-mail 
me
that file (bugs at scrobbledroid.com).

Original comment by jjc1...@gmail.com on 31 Mar 2009 at 11:58

[GoogleCodeExporter]

Actually I experience the same crash from time to time.  Usually when I lose 
signal
or just a random track.  I'll pay more attention the next time it happens.

Original comment by LiLJ...@gmail.com on 2 Apr 2009 at 6:12

[GoogleCodeExporter]

I've only just noticed this (don't ask me how I missed it), but this is the
force-close bug I addressed in my patch (issue 20). Although the patch contains 
all
the extra functionality I added, the only stuff it changes in 
MusicStatusFetcher was
to fix this, since it happened to me. Had I noticed that I would have submitted 
it as
a separate patch - sorry. Anyway, you can check what I changed in there, 
starting at
line 1044.

It happened occasionally when I skipped (mp3, not wma) tracks rapidly, because
MusicStatusFetcher attempted to bind while it was already bound from the 
previous
call. I just made MusicStatusFetcher not bind again if it was still bound from 
last
time. Maybe it should queue up and bind when the other one unbinds - not sure 
about
that. My possibly naive fix worked well enough for me so I just went with that.

If you absolutely can't get it to happen I could always unfix it, reproduce it, 
and
supply you with the stack trace. I checked it in DDMS when it happened to me, 
but
didn't bother saving the log. Let me know if you want me to.

Original comment by themightyjon on 30 Apr 2009 at 8:55

[GoogleCodeExporter]

I don't think a stack trace will be necessary; I'll take your word for it. :-) 
Thanks
again.

Original comment by jjc1...@gmail.com on 30 Apr 2009 at 9:02