Alarms not going off reliably on recent touch images

[Dave Morley]

Alarms are not reliable on recent images on touch.

Even on not deep sleep mode, (wakelock with powerd-cli active), the alarm doesn't ring everytime when the screen is blanked. The first alarm worked, not the others.

Popey: See's the alarm notification but not hears no sound.
davmor2: I see and hear the alarm and notification if the device is awake if the screen is blank though I sometimes get an alarm 2 minutes Plus after the alarm was meant to go off other times I neither see nor hear the alarm.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.13.3-0ubuntu1
Architecture: armhf
Date: Thu Mar 20 13:12:36 2014
InstallationDate: Installed on 2014-03-20 (0 days ago)
InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

[Alan Pope 🍺🐧🐱 🦄 (popey)]

https://www.youtube.com/watch?v=MOQCAemwgeY

[Didier Roche-Tolomelli (didrocks)]

set as critical as a promotion blocker

[Ricardo Salveti (rsalveti)]

Can you guys try to reproduce this issue after running 'powerd-cli active' (as root) on another terminal?

Just to understand if this is related with the device going into deep suspend or not, as it's expected to be broken in case the device is fully suspended (no support for hw alarms yet).

[Alan Pope 🍺🐧🐱 🦄 (popey)]

I ran powerd-cli active in another terminal.
Set alarm for 1 min's time.
Tapped power button to blank screen.
Wait...
Nothing happens.
Tap power button once time for alarm has passed and the alarm appears and sounds.

[Charles Kerr (charlesk)]

I think this report is over a pair of known issues that are currently queued for fixing, but can't be fixed solely in indicator-datetime:

(1) There's currently no way to wake up the phone when it's asleep and needs to show an alarm. tvoss is working on adding hardware alarm support to platform-api <https://code.launchpad.net/~thomas-voss/platform-api/hw-alarms-api> so that indicator-datetime can use that API to wake up the phone.

(2) There's currently no way to turn on the display when an alarm goes off. This is similar to the need to show the display when receiving an incoming call. I summarized the state of this at <https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1283225/comments/2>, but the short summary is this is a powerd issue, it also needs to watch the hw-alarms-api and wake up the display.

[Didier Roche-Tolomelli (didrocks)]

ok, so the theory is busted.

In adb shell:
$ powerd-cli active
screen turned off
-> The alarm doesn't ring. The notification is there though when we light the alarm.

Not that this didn't happen 100% of the time (the first alarm worked)

[Charles Kerr (charlesk)]

So, after further discussion in #ubuntu-touch, it looks like the seen-but-not-heard issue that popey's encountering, and the showing-up-late issue that davmor2 is seeing, are not related to phone nor screen wakeup issues.

Dave fleshed out the showing-up-late issue at bug #1295237

I've expanded on the seen-but-not-heard issue at bug #1295271

Are there any other pending issues that need to be addressed?

[taiebot65 (dedreuil)]

I am also seeing this on 237

[Charles Kerr (charlesk)]

So there are the two separate issues mentioned above in the previous comment, which have been fixed in their own tickets.

There's also the Qt 5.2 event loop issue that stopped unity-notifications from responding, which has been addressed outside of this ticket.

I don't believe there are any pending issues here that weren't addressed elsewhere, so I'm marking this ticket as invalid to close it off. If I'm wrong about this, please reopen the ticket and provide more information. Thanks!