We have moved to a new Sailfish OS Forum. Please start new discussions there.
9

alarm clock no sound 1.1.9.28 [major bug?]

asked 2015-09-17 08:53:58 +0300

FOMBE gravatar image

updated 2016-11-08 14:19:23 +0300

jiit gravatar image

so this morning I woke up 2.5 hours late since jolla had alarm sounds off. I tested it by setting alarm to next minute. alarm goes on screen nicely but there is no sound. system sounds are @ 80% , phone is not in silence mode or not in silenced theme.

speaker does work,tested with spotify.

battery was ~5% but even on charger it still doesnt give off the alarm.

after few times clock even went unresponsive, I closed it and started again and no progress.

apps open was whatsapp and messener. but those never conflicted this far with sounds.

Ill try to reboot next althought uptime is 1day 1 hour.

edit retag flag offensive close delete

Comments

there also is a jolla-alarm tune selected for alarm sound. and even by closing all apps there is no progress.

noticed only that every app went unresponsive when using pulley menu

rebooting solved alarm clock no sound problem.

FOMBE ( 2015-09-17 08:58:47 +0300 )edit
1

Same here. no alarm sound, only vibration.

njeiseck ( 2015-09-17 09:13:29 +0300 )edit

I my case it seems to have been a problem with the speaker. Compressing the lower part of the phone seems to have cured this (temporarily?) See https://together.jolla.com/question/39900/no-sound-through-speaker/

njeiseck ( 2015-09-17 10:59:49 +0300 )edit

2 Answers

Sort by » oldest newest most voted
1

answered 2015-10-22 11:14:22 +0300

evo3de gravatar image

I have recognized something a few weeks ago: Bug - Alarms not alarming

edit flag offensive delete publish link more

Comments

Isn't your question a duplicate of this one?

raketti ( 2015-10-22 12:31:30 +0300 )edit

Not realy, because it was not showen @ notification, did not run at all

evo3de ( 2015-10-22 12:58:38 +0300 )edit

@evo3de, if you have set an alarm and it will ring to the end and stop. Should it be shown in the Events view as a missed alarm?

I know calendar reminders do this, but does it apply to the alarm clock as well?

raketti ( 2015-10-22 13:38:26 +0300 )edit

@raketti normally yes, so i saw that it wasn´t running

evo3de ( 2015-10-22 14:00:25 +0300 )edit

@evo3de - thank, I've never noticed, or seen it in the Events screen.. So that would confirm that today my alarm didn't even go off.

raketti ( 2015-10-22 15:28:01 +0300 )edit
1

answered 2016-11-07 12:35:25 +0300

luen gravatar image

updated 2016-11-07 12:56:26 +0300

This morning my phone didn't wake me up, so I verified that there really hadn't been any sound by setting an alarm go off the next minute and observed it opening the alarm application and showing the alarm without making any sound. Since I'm on a Fairphone 2 without vibration, that didn't help either.

Other observations:

  • When pushing the volume rocker at the lock screen, the notification says "Volume" instead of "Ringtone volume"
  • It's not possible to play songs in the music player ("Media"). They just don't start and nothing about it is written to the log.
  • The only "unusual" thing that I have done recently on the phone is was to listen to some podcasts using gPodder.
  • Not even gPodder can play anything now.
  • Phone: Fairphone 2
  • SFOS version: 2.0.1.11

Is there anything else I should test while the phone is in this state, before I reboot?

Log from the first occasion when the alarm went off without sound (when I tested it again, there was nothing about it in the log):

Nov 07 08:00:00 dbus-daemon[1115]: Activating via systemd: service name='com.nokia.voland' unit='jolla-alarm-ui.service'
Nov 07 08:00:00 systemd[1039]: Starting Alarm ui...
Nov 07 08:00:00 DSME[10253]: IPHB: alarm state from timed: powerup=1, resume=1478622600
Nov 07 08:00:00 [18752]: [W] DeclarativeWindow::DeclarativeWindow:93 - No default allowed orientations defined. Check your device configuration! 
Nov 07 08:00:00 dbus-daemon[1115]: Successfully activated service 'com.nokia.voland'
Nov 07 08:00:00 systemd[1039]: Started Alarm ui.
Nov 07 08:00:00 invoker[1551]: WARNING: An inactive plugin is misbehaving - tried to show a window!
Nov 07 08:00:00 invoker[1551]: WARNING: requestActivate() called for  QQuickView(0x3852a8)  which has Qt::WindowDoesNotAcceptFocus set.
Nov 07 08:00:00 lipstick[1174]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Nov 07 08:00:00 statefs[637]: Display: "on" 
Nov 07 08:00:01 booster-silica-qt5[20683]: [D] QWaylandEglClientBufferIntegration::QWaylandEglClientBufferIntegration:62 - Using Wayland-EGL 
Nov 07 08:00:01 mapplauncherd[20683]: SilicaBooster: Initiate asynchronous preload.
Nov 07 08:00:04 [20683]: [W] DeclarativeWindow::DeclarativeWindow:93 - No default allowed orientations defined. Check your device configuration! 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:68 - Initializing plugin 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:93 - Reading setting for Press : 20 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:94 - Reading setting for Release : 18 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:95 - Reading setting for PressWeak : 10 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:96 - Reading setting for ReleaseWeak : 7 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:97 - Reading setting for PressStrong : 30 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:98 - Reading setting for ReleaseStrong : 25 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:99 - Reading setting for DragStart : 5 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:100 - Reading setting for DragDropInZone : 15 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:101 - Reading setting for DragDropOutOfZone : 0 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:102 - Reading setting for DragCrossBoundary : 10 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:103 - Reading setting for Appear : 0 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:104 - Reading setting for Disappear : 0 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::QFeedbackDroidVibrator:105 - Reading setting for Move : 0 
Nov 07 08:00:04 [20683]: [D] QFeedbackDroidVibrator::deviceProfileSettingsChanged:133 - Profile settings changed: enabled: true level: 1 
Nov 07 08:00:10 start-jolla-alarm-ui[20682]: invoker: Invoking execution: '/usr/bin/jolla-alarm-ui'
Nov 07 08:01:01 DSME[10253]: IPHB: alarm state from timed: powerup=1478502361, resume=1478622600
Nov 07 08:01:02 lipstick[1174]: [W] QQuickShaderEffectCommon::updateMaterial:428 - ShaderEffect: Property 'source' is not assigned a valid texture provider (QQuickItem*).
Nov 07 08:01:02 statefs[637]: Display: "off" 
Nov 07 08:01:02 lipstick[1174]: [D] HwComposerContext::sleepDisplay:177 - sleepDisplay
Nov 07 08:01:33 dbus-daemon[1115]: Activating via systemd: service name='org.nemo.transferengine' unit='transferengine.service'
edit flag offensive delete publish link more

Comments

1

imho you should start new topic for your fairphone port problem

coderus ( 2016-11-07 15:53:20 +0300 )edit

@coderus I don't think the alarm sound thing is FP2 related and didn't want to create a duplicate question.

luen ( 2016-11-07 15:55:26 +0300 )edit

everything related to ports should be solved separately and its 100% unrelated to jolla production.

coderus ( 2016-11-07 15:58:01 +0300 )edit

@coderus Of course things should be reported where they belong, and in this case I judged the problem to probably be unrelated to anything FP2 specific. I have reported other non-port related SFOS issues on TJC. Shouldn't I have done that just because I'm using a Fairphone? How can you be so sure that this problem is port related?

luen ( 2016-11-07 16:38:16 +0300 )edit

Happened again today. Haven't used gPodder lately this time, so I guess it had nothing to do with it. No idea what else that may have caused it.

luen ( 2017-02-19 15:07:29 +0300 )edit
Login/Signup to Answer

Question tools

Follow
5 followers

Stats

Asked: 2015-09-17 08:53:58 +0300

Seen: 640 times

Last updated: Nov 07 '16