maemo.org Bugzilla – Bug 9493
Profile-specified audible alerts sometimes do not go back to normal after headphones are unplugged
Last modified: 2011-01-18 15:37:02 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: (Settings > General > About product) Maemo 5, Version 3.2010.02-8.002 EXACT STEPS LEADING TO PROBLEM: (Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message Connection Failed appears)) 1. Starting from a freshly booted n900, set profile to 'General', which specifies full audible alert tones for email/sms/phone calls/etc. 2. Plug in headphones and listen to music on media player. This will cause alerts for email/sms to be routed to the headphones, and to only play a simple 'beep' instead of a full alert tone. 3. Unplug the headphones, and the device will not revert to playing full 'alert tones' - it still plays the quiet beeps that it would play if the headphones were still plugged in. Changing profiles to silent and back to general does not resolve this - a reboot is required. EXPECTED OUTCOME: Upon unplugging the headphones, the device should revert to the selected profile, and play the alert tones as described in the profile. ACTUAL OUTCOME: The device will not revert to playing full 'alert tones' after headphones are unplugged - it still plays the quiet beeps that it would play if the headphones were still plugged in. REPRODUCIBILITY: 8/10 EXTRA SOFTWARE INSTALLED: The Headphone Daemon (that pauses the music applet when headphones are unplugged). I can extract a full list on request - but I can't see anything else that seems related to this. OTHER COMMENTS: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6
(In reply to comment #0) > 2. Plug in headphones and listen to music on media player. This will cause > alerts for email/sms to be routed to the headphones, and to only play a simple > 'beep' instead of a full alert tone. This is not the case for me when I tried to reproduce this on a clean PR1.1.1 It blasts out music to earphone and loudspeaker when there's an incoming call with earphone plugged in. Not a 'beep' like you mentioned.
(In reply to comment #1) > (In reply to comment #0) > > > 2. Plug in headphones and listen to music on media player. This will cause > > alerts for email/sms to be routed to the headphones, and to only play a simple > > 'beep' instead of a full alert tone. > > This is not the case for me when I tried to reproduce this on a clean PR1.1.1 > It blasts out music to earphone and loudspeaker when there's an incoming call > with earphone plugged in. Not a 'beep' like you mentioned. > Well, it's different with phone calls - that always plays my full 'ring tone' whether I have my headphones plugged in or not. However, for email&sms alerts, plugging the headphones in changes the tone to a 'beep'. The problem I have is unplugging the headphones doesn't change the email&sms tones back to the full tone, often it just goes to vibrate for some reason. This isn't a duplicate of that other bug for that reason (although they are both related to profile/audio problems).
Unable to reproduce bug here.
I think I managed to get "silent mail" when I stopped the media player only after unplugging the headphones, but I could not reliably reproduce it.
This is happening to me too. PR1.2, headphone daemon and last.fm scrobbler installed, but nothing else related to audio. After listening to music through headphones for a while, I unplug the headphones. Music stops, but when I get an SMS or IM, the N900 plays the short beep you would hear through the headphones upon getting an message, but through the loudspeaker. A workaround I'm using at the moment is to going into the settings to edit the General profile, and then back out.
I want to confirm that this still happens to me after the upgrade to PR1.2, although now sometimes instead of the 'headphones plugged in' beep-only-alert after unplugging the headphones, I sometimes get no alert tone at all (despite being on the GENERAL profile). I cannot always replicate this, but the overall problem itself is definitely repeatable, and like Ian I can only fix it by either rebooting the phone or editing my profile.
*** Bug 9597 has been marked as a duplicate of this bug. ***