[Touch-packages] [Bug 1434637] Re: Default alarm behavior can cause unnecessary battery drain

2015-04-02 Thread Launchpad Bug Tracker
This bug was fixed in the package indicator-datetime - 13.10.0+15.04.20150331-0ubuntu1 --- indicator-datetime (13.10.0+15.04.20150331-0ubuntu1) vivid; urgency=medium [ Charles Kerr ] * Reduce the forced screen-on time for alarms to reduce battery consumption. Also, lower the

[Touch-packages] [Bug 1434637] Re: Default alarm behavior can cause unnecessary battery drain

2015-03-30 Thread Matthew Paul Thomas
Specification updated. ** Description changed: As discussed in private bug #1430666, the default alarm ring duration of 30 minutes is really long compared to other phones. This got called out because it will cause unnecessary screen-on battery drain. IMO 30 minutes should not be the

[Touch-packages] [Bug 1434637] Re: Default alarm behavior can cause unnecessary battery drain

2015-03-25 Thread Charles Kerr
** Description changed: As discussed in private bug #1430666, the default alarm ring duration of 30 minutes is really long compared to other phones. This got called out because it will cause unnecessary screen-on battery drain. IMO 30 minutes should not be the default option -- if a

[Touch-packages] [Bug 1434637] Re: Default alarm behavior can cause unnecessary battery drain

2015-03-25 Thread Charles Kerr
** Branch linked: lp:~charlesk/indicator-datetime/lp-1434637-make- alarms-use-less-battery -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1434637 Title:

[Touch-packages] [Bug 1434637] Re: Default alarm behavior can cause unnecessary battery drain

2015-03-25 Thread Matthew Paul Thomas
Giorgio is no longer with us, and the clock spec is currently unmaintained. In the meantime: 1. I think you're on safe ground changing the alarm from 30 minutes to 10 minutes. I've requested access to the spec to update it accordingly. 2. I don't see any mention of a 'screen on' hold. What I do