Crash when playing sound.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set an alarm with internal tone. One other than 'default.
(ex pixie dust, terminated...)
2. Wait
3. Alarm does not sound but will vibrate if set. 
Get an error saying that the process crashed.
Alarm will fail to play sound 3/4 times.

What is the expected output? What do you see instead?

Crash message:
"The process com.angrydoughnuts.android.alarmclock for program alarm klock .... 
"

What version of the product are you using? On what operating system?

Latest from market on Android 2.1 on a Sony Ericsson X8.

Please provide any additional information below.

This appears to happen with internal sounds more often than otherwise
but that could just be my imagination.
Sometimes the music will start to play but then abruply stop other times it 
will not begin to play at all. 
This problem just started 2 days ago. It has worked perfectly before.
I have tried to do a reboot to no avail.
I will make a few tests by removing recently installed apps.

Original issue reported on code.google.com by Kent.Wen...@gmail.com on 20 Apr 2011 at 5:28

[GoogleCodeExporter]

There's a bug in the app that gets triggered by the more aggressive garbage 
collecting in gingerbread.  It's fixed in the test version, but I haven't had a 
chance to release it yet.  You can try it out by installing
http://kraigsandroid.googlecode.com/files/Alarm%20Klock.apk

Let me know if that fixes the problem for you.

Original comment by kraigs.a...@gmail.com on 20 Apr 2011 at 5:37

[GoogleCodeExporter]

Just saw that you had released a new APK here. I'll see if that one works 
better.

Also should have mentioned in my report that you have my thanks for a great app.
Best regards.

Original comment by Kent.Wen...@gmail.com on 20 Apr 2011 at 5:38

[GoogleCodeExporter]

Update: Have run a bunch of different alarms now. They all appear to function 
great.

You should probably put the new app up on market ASAP. Not everyone will be 
able 
to figure out how to get here and find this.

Thanks and best regards.

Original comment by Kent.Wen...@gmail.com on 20 Apr 2011 at 6:16

[GoogleCodeExporter]

Thanks for the update!  Releasing a new version through the market is a pretty 
involved process.  In this case, the first release is probably going to break 
more people than it fixes.  There are always a million new bugs that pop up 
because of unexpected interactions with the newer API versions (I think the 
current release version is still build against version 1.6 of the API, so this 
will be a fairly significant version change), so I've been holding off until I 
have a solid week free to firefight all of the new problems that are going to 
show up... I'll get to it soon, though!

Thanks again for confirming the fix,
Craig

Original comment by kraigs.a...@gmail.com on 20 Apr 2011 at 6:24

• Changed state: Fixed