No alarm sound after 1.5 upgrade

[GoogleCodeExporter]

There have been several reports of the alarm sound not playing after the 1.5 
upgrade.  I have not yet been able to reproduce this problem.  Please add 
additional information to this bug report so that I can try to track down the 
problem.  Hopefully a pattern will fall out given the information below.

Useful information:
- Type of hardware that you are using (eg, Nexus one, G1, etc)
- Version of the android operating system Menu->Settings->About Phone->Build 
number (eg FRF91)
- Alarm settings (repeats, tone type (mp3, built in, ringer, midi, etc), 
snooze, vibrate, volume fade)
- Application settings (display notification icon, lock screen text, etc)
- How reproducible is this?  (every time, sometimes, 1 in 5, etc)

Even more useful information:
If you are comfortable debugging, getting the system log for the phone when the 
problem occurs would be extremely useful.  Instructions can be found in the 
logcat section 
here:http://developer.android.com/guide/developing/tools/adb.html#logcat

Original issue reported on code.google.com by kraigs.a...@gmail.com on 13 Jul 2010 at 1:54

[GoogleCodeExporter]

I have the same problems on:
- HTC Desire
- 2.1 - ver. 1.15.405.4
- Alarm settings - on weekdays, mp3 on SD card, volume fading on
- Display notification icon on
- 1st time it's OK, 2nd it plays the system default ringtone, 3rd isn't playing 
at all anything, but the alarm screen is on, but I cannot switch it off, 4th 
the same as the 3rd

Original comment by nemeth.d...@gmail.com on 13 Jul 2010 at 2:16

[GoogleCodeExporter]

Similar issues after latest Alarm Klock upgrade. Alarm seems to work fine 
except that it starts at the loudest setting.  Turned off phone (HTC 
Incredible) and removed battery.  Next time alarm was triggered it seemed to 
work fine.  However, then next time it went back to loud (no incremental sound.)
HTC Incredible
Firmware: 2.1-update1
Software #: 1.22.605.2

Original comment by Guitarra...@gmail.com on 13 Jul 2010 at 3:11

[GoogleCodeExporter]

I had a really strange behavior:
- after update to 1.5 I had the problem too
- then I switched back to 1.4 to solve the problem
- now I updated again to 1.5 and tried the alarm set with version 1.4 (which 
staid afer update, I only changed the time): it worked!
- I deleted the alarm and created a new one (with unchanged default settings 
from 1.4: my mp3 from sd card): I got the standard ringtone
- I deleted the alarm and changed the default settings: selected the same mp3 
on sd card again
- I created a new alaram: no Sound, only vibration! But I can switch the alarm 
screen off with the dismiss slider...

other settings:
- Display notification icon [x]
- Lock screen text: Countdown
- Alarm time out: 10
- Debug Mode: On
- fading: 0 to 100 in 20sec
- snooze: 5 sec
- vibrate: enabled

some Infos about my device:
- HTC Desire (rooted)
- MoDaco Custom ROM r3.1 based on 2.1-update1 BuildNr 1.21.MCR2

I attached a aLogcat output from changing the time, alarm (with no sound) and 
dismiss.
seems to loog "good": W/System.err( 5168):  at 
com.angrydoughnuts.android.alarmclock.NotificationService.soundAlarm(Notificatio
nService.java:286)

Just ask if you need more information

Original comment by hallo...@graffiti.net on 13 Jul 2010 at 3:22

Attachments:

• alogcat.2010-07-13-17-18-30+0200.txt

[GoogleCodeExporter]

Wow thanks, there are lots of not-good looking things in this log.  I think the 
most likely issue is
W/PVPlayer(  152): Exceeds maximum number of OpenCore instances

The media player objects are pretty heavy weight and this would imply that they 
are not being recycled properly.  However, only one should be created at any 
given time.  You wouldn't happen to be running a task killer, would you?  It 
looks like the notification service restarted (ungracefully) several times in 
this log.  This service did not exist in the previous version of the 
application.

One other question, is there anything special about the tone that you are 
using?  Is it a built in sound? an MP3 (DRMed or not), a midi file maybe?

Original comment by kraigs.a...@gmail.com on 13 Jul 2010 at 4:11

[GoogleCodeExporter]

i have a desire (t-mobile germany branded) with 2.1.
it is independent from the ring tone i chose, but i remember that the very 
first time it worked, but i had two sounds at one time. afterwards nothing 
happened.
but i encountered, that the vibration is working, that means, that you are 
going into the right direction.

good luck.

Original comment by AndreGro...@gmail.com on 13 Jul 2010 at 7:31

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

After rebooting the device I had a sound (my mp3). Then I tried it the second 
time and got only the default sound. The third time I got no sound again...

I made logs of each try again and attached the ringtone. I don't know the 
coypright rules, I think its the best if you delete it after downloading...

Original comment by hallo...@graffiti.net on 13 Jul 2010 at 7:37

Attachments:

• alogcat1.txt
• alogcat2.txt
• alogcat3.txt

[GoogleCodeExporter]

HTC Legend:
- After upgraded, original sound settings didn't work. I restarted the program 
and set up all sounds again.
- No ringing sound while my mp3 player was on (MixZing. The ringing worked 
before upgrade).
- This morning my 1st alarm setting at 6:30 worked well (mp3 sound, no repeat, 
vibration disabled). Then I miss the 2nd at 7:00 (a 3-minute mp3, repeat and 
vibration enabled). When I came back at 7:10, the snoozing was on with no sound 
but only vibration.

Original comment by prelude0...@gmail.com on 14 Jul 2010 at 12:58

[GoogleCodeExporter]

Type of hardware - HTC Desire
Version of the android operating system 2.1 - update 1 Build 1.21.405.2 
CL174215 release-keys
Alarm settings - repeats Mon to Fri, tone type is mp3 from SD card, snooze 5 
minutes, vibrate off, volume fade from 0% to 100% over 60 seconds
Application settings - display notification icon off, lock screen text is 
countdown
How reproducible is this - after a phone reboot it works fine but then no sound 
for alarm after the first one so in other words if I reboot phone each night 
the first alarm will work but if I hit snooze then the next alarm has no sound. 
alarm kicks in and notification on screen shows but no sound. I have debug mode 
turned on but don't know how to get the files for you. It all worked fine 
before the recent update I applied via the market

P.S.
Great App - just hope you can get it working again

Original comment by tui0...@gmail.com on 14 Jul 2010 at 7:36

[GoogleCodeExporter]

I've got a theory about the media player recycling issue.  If that is the 
problem, I think I have a fix for it.  Could someone experiencing this problem 
please install and test out this?  You may have to reboot after installing in 
order to reset the media player.
http://kraigsandroid.googlecode.com/files/Alarm%20Klock-sound-fix-test.apk

I also added a bunch of extra debugging log statements to that apk, so logcat 
files will be more useful if the problem was not fixed.

Original comment by kraigs.a...@gmail.com on 14 Jul 2010 at 3:42

[GoogleCodeExporter]

Just tried your bugfix version on a HTC Legend (Android 2.1) and works with mp3 
sound from the SD card as well with sound files from the phone itself.

Original comment by s.penten...@gmail.com on 14 Jul 2010 at 4:03

[GoogleCodeExporter]

worked for me too (three times in a row). Do you still need a logcat output?

Original comment by hallo...@graffiti.net on 14 Jul 2010 at 4:10

[GoogleCodeExporter]

Running Android 2.1 on HTC Incredible. After the upgrade I can no longer use 
mp3's from the SD card. Alarms function, but only vibration and no sound.

Original comment by Hubri...@gmail.com on 14 Jul 2010 at 4:20

[GoogleCodeExporter]

Awesome, thanks for the report back on the patched apk.  I've you've got the 
log files, I'd be happy to look at them to make sure what I expected to happen 
actually happened...

Assuming those are correct, and no other bugs pop up, I'll push the fix 
tomorrow.

Thanks everyone!
Craig

Original comment by kraigs.a...@gmail.com on 14 Jul 2010 at 4:25

[GoogleCodeExporter]

Useful information:
- HTC Incredible
- 2.1 Update 1 - 1.22.605.2 CL161494
- Repeat every day, Tone=Curve, Snooze=10 min, vibrate disabled, alarm volume 
fade 0 to 10% over 60 seconds
- Display notification icon checked, lock screen text = countdown, alarm 
timeout = 10, debug mode = default
- Happens every time.  Alarm comes on, but no sound.

Original comment by kevinpre...@gmail.com on 14 Jul 2010 at 4:37

[GoogleCodeExporter]

Here are 3 logs again, but I forgot to enable debugging mode.... Should I make 
new ones?

Original comment by hallo...@graffiti.net on 14 Jul 2010 at 4:43

Attachments:

• alogcat1.txt
• alogcat2.txt
• alogcat3.txt

[GoogleCodeExporter]

Fix works for me too. Have tried it 5 times now and its playing mp3 from SD no 
problem. Thanks. If you want log files let me know and I will figure out how to 
do them and send them on

Original comment by tui0...@gmail.com on 14 Jul 2010 at 7:08

[GoogleCodeExporter]

These logs are sufficient.  The media player is properly being recycled now.  
I'm mostly convinced that this fixes the problem and doesn't introduce any new 
ones.  Please let me know if anyone experiences a problem with the test apk 
above.  I'll push the fix to the market tomorrow otherwise.

Thanks all!
Craig

Original comment by kraigs.a...@gmail.com on 14 Jul 2010 at 8:50

[GoogleCodeExporter]

test didnt work for me,

sorry no time for details, 

desire 2.1 stock rom
normal settings like everyone

still no sound, please give me the previouos version i miss my alarm klock! 
almost lost my job :(

greetz

Original comment by ewi...@gmail.com on 15 Jul 2010 at 3:40

[GoogleCodeExporter]

fix worked for me, thanks!
great job.

Original comment by AndreGro...@gmail.com on 15 Jul 2010 at 6:14

[GoogleCodeExporter]

The fix worked on my incredible.  Thank you and will the program still be able 
to update through the market?

Original comment by jessekos...@gmail.com on 15 Jul 2010 at 1:45

[GoogleCodeExporter]

Just pushed the 1.6 update to the market including this fix.  Please reopen if 
the bug comes up again.

Original comment by kraigs.a...@gmail.com on 15 Jul 2010 at 3:25

• Changed state: Fixed