Alarm sounds fail after few days of uptime

[ExTechOp]

REPRODUCIBILITY:
OS VERSION: 4.5.0.16 (and earlier)
HARDWARE: Sony Xperia 10III (also earlier seen on 10II)
UI LANGUAGE: English
REGRESSION:

DESCRIPTION:

After a few days of uptime, the phone sounds (ringing, SMS, alarms, timers) stop working, and only vibration remains.

PRECONDITIONS:

Extended uptime seems to be required, in the range of a few days.

EXPECTED RESULT:

Sounds work normally.

ACTUAL RESULT:

No sounds, only vibration (if you’ve set that)

MODIFICATIONS:

F-Droid, Chum, Storeman, Aurora Store

ADDITIONAL INFORMATION:

This same bug has also been discussed in the following threads, it seems plausible this bug has been around for quite some time now:

[4.1.0.23][4.0.1.48][4.4.0.64][4.5.0.16] No notification sounds (ringing, SMS, alarm)

REPRODUCIBILITY (% or how often): second time so far BUILD ID = OS VERSION (Settings > About product): 4.0.1.48 HARDWARE (XA2, Xperia 10…): Xperia 10 UI LANGUAGE: Slovenian REGRESSION: (compared to previous public release: Yes, No, ?): Yes (compared to v3) DESCRIPTION: Twice so far (first time was with 4.0.1.45) notification sounds stopped working - no alarm, no ringing, no SMS alert tone), in addition if I go to Settings → Sounds and try to change the volume there, the Settings app freeze…

Situations no longer turns sound on?

I’ve used Situations for a very simple sounds/silent switching so that I don’t get email blings in the middle of the night. However, after upgrading my Xperia 10 III to SFOS to 4.4.0.72 (Vanha Rauma) it seems Situations has issues restoring sounds in the morning. When this happens, the only solution seems to be to restart the phone, running the Situations app thinks it has switched the sounds on but nothing changes. Has anyone else experienced issues like this?

[direc85]

Yes, this is a duplicate of the first bug you linked. Why did you open a one more duplicate bug report of a known issue?

[vlagged]

So, does vibration still work on 10 mark III if you systemctl --user stop ngfd ? If yes, it’s probably the same bug. If not, it is another one.

(asking because on my device, vibrations are also tied to ngfd.)

[ExTechOp]

It can indeed be a duplicate, I was asked to open a bug report at the Jolla users irc meet so that it could be determined if it really is one.

[ExTechOp]

So, does vibration still work on 10 mark III if you systemctl --user stop ngfd ? If yes, it’s probably the same bug. If not, it is another one.

I was hit by this again today on my Sony Xperia 10III: sounds are gone but the vibration alarm is still there.

After doing systemctl --user stop ngfd vibrations still work at least with timers (which is the most convenient test to do). If you are correct, this is the same issue as in the other thread.

I’ll mark your message as a “solution” so this apparent duplicate doesn’t clog up bug tracking. Please move all discussion to the 1st of the above bugs.

[vlagged]

Thanks for confirming.
I will not be able to move the discussion, and I think it’s fine like this - separate bugs with similar but not evidently the same symptoms are OK in my opinion.
Maybe @pherjung can help tracking this as a duplicate.

Since this may also be caused by a ngfd hang, there’s a daemon I hacked together to restart ngfd when I detect one (by a heuristic, not much scientific method). See if installing / running that “ngfd-watch” helps you (it will send a notification when it “helped”;- )