Will leave this open since alf provided a ppa with a possibly more
complete fix per comment #42
** Changed in: canonical-devices-system-image
Status: Fix Released => In Progress
** Changed in: canonical-devices-system-image
Milestone: 14 => backlog
** Changed in: ubuntu-clock-app
@Pat, in which release has this bug-id been fixed ? I have just tested OTA-14
and the issue is still there.
At the same time tell me where can I find information when a bug id is supposed
to be fixed how to test it on my own phone ?
--
You received this bug notification because you are a member
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
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/1588526
Title:
[mako]
I have prepared a PPA containing a new repowerd with a potential fix for
the issue here:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2276
IMPORTANT CAVEAT: The changes are experimental. Only try the PPA
packages on a development device, not one you care about keeping stable.
You m
** Also affects: repowerd
Importance: Undecided
Status: New
** Changed in: repowerd
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: repowerd
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch s
Expexperiancing this often. on nexus -4 OTA-13
--
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/1588526
Title:
[mako] Alarm doesn't ring when screen locked
Statu
Gents,
I'm currently in Rc-proposed, so my phone should have received by now
the fix, however the phone still experiencing this bug.
Regards
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
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/1588526
Title:
[mako] A
This bug was fixed in the package indicator-datetime -
15.10+17.04.20161104-0ubuntu1
---
indicator-datetime (15.10+17.04.20161104-0ubuntu1) zesty; urgency=medium
[ Charles Kerr ]
* Remember the system bus instead of fetching it asynchronously (LP:
#1588526)
-- charles.k...@c
Hi,
i have the same problem. But i often notice that sometime when i unlock the
phone it takes a few seconds for my nexus4 to refresh the time. It use to show
me the time i block it before..
could this be related to this bug?
thanks for your care!
--
You received this bug notification becaus
Did this land?
** Changed in: canonical-devices-system-image
Status: Incomplete => In Progress
** Changed in: canonical-devices-system-image
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Thanks for the info. Much appreciated!
--
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/1588526
Title:
[mako] Alarm doesn't ring when screen locked
Status in Can
FWIW updating the Clock app will not affect this bug. The Clock app just
saves an alarm using Alarm API and the rest is done by the system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://
Problem persists (alarm not waking phone) after updating to latest clock
app. Typically the problem occurs 1 or 2 days after a reset and always
comes back. My device has a bare minimum of apps installed and I don't
use any scopes, aside from the main home screen. Bluetooth and GPS
permanently off.
Yes, I can confirm the alarm does sound but only when you pick the phone
up and turn on the screen.
However, this is after (10 minutes in my case) it should have sounded
From: boun...@canonical.com on behalf of Michal
Predotka
Sent: 14 October 2016 23:05
To: m
Comment #13 describes a problem with a different alarm sound played then
expected. I believe that could be the same situation as in bug #1596924
(sound change need to be confirmed)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The suggestion of no longer supporting the Nexus 4 (comment #24) is worrying,
as there are no current OEM devices for sale and few enough supported models.
This deprecation isn't mentioned anywhere else (that I could find) and flies in
the face of these current pages:
https://developer.ubuntu.co
** Changed in: canonical-devices-system-image
Milestone: backlog => 14
--
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/1588526
Title:
[mako] Alarm doesn't ri
I see mentioned here only Nexus 4. I never experienced such a behaviour
on bq E4.5. The only thing that happened was a second alarm clock that
didn't ring. However it happened only once and I can not reproduce it.
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Not 100% sure if it's related to this bug or not, but the end result is the
same.
I have had occurrences where I set a new alarm and it does not go off at all.
So I have an alarm set to wake me up on weekdays, which hasn't given me issues.
But not too long ago, I added a new 'once off' alarm to w
I never saw a message that the Nexus 4 is no longer a supported device!
It would be nice to be able to actually buy something that I like, was
waiting on the MX 6 but that seems to have been canceled. A lot of
people use the Nexus 4, so why would you stop supporting it?
--
You received this bug
After looking through the code, Pat's thoughts in comment 14 seem right
to me.
For indicator-datetime's part, it can pass the system bus into the
object constructor instead of making an asynchronous call to fetch it.
This narrows the dangerous interval in datetime between wakeup and
calling reques
** Branch linked: lp:~charlesk/indicator-datetime/lp-1588526-remember-
system-bus
--
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/1588526
Title:
[mako] Alarm doe
Since when the N4 is not anymore supported, last month in OTA 13 the was
a bug specifically solved for Mako.
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360
Moreover, there is high likelihood the future fix for this bug
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1516696
Is Nexus4 a no longer supported device? :O This is the only phone what a
new user can buy. I don't think it's a good decision.
--
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.launchpa
These seems specific to the Nexus 4, moving to backlog as it is no
longer actively supported
** Summary changed:
- Alarm doesn't ring when screen locked
+ [mako] Alarm doesn't ring when screen locked
** Changed in: canonical-devices-system-image
Milestone: 14 => backlog
--
You received thi
26 matches
Mail list logo
