[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
** Changed in: telephony-service (Ubuntu)
Assignee: Michael Terry (mterry) => (unassigned)
** Changed in: powerd (Ubuntu)
Assignee: Michael Terry (mterry) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1482317
Title:
Unify code that turns screen on when a notification happens
Status in powerd package in Ubuntu:
In Progress
Status in telephony-service package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
Fix Released
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
See also bug #1562923
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1482317
Title:
Unify code that turns screen on when a notification happens
Status in powerd package in Ubuntu:
In Progress
Status in telephony-service package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
Fix Released
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
** Also affects: powerd (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:~mterry/powerd/no-screen-on
** Changed in: unity8 (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: telephony-service (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:~mterry/telephony-service/no-screen-on
** Changed in: telephony-service (Ubuntu)
Status: New => In Progress
** Changed in: telephony-service (Ubuntu)
Assignee: (unassigned) => Michael Terry (mterry)
** Changed in: powerd (Ubuntu)
Status: New => In Progress
** Changed in: powerd (Ubuntu)
Assignee: (unassigned) => Michael Terry (mterry)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1482317
Title:
Unify code that turns screen on when a notification happens
Status in powerd package in Ubuntu:
In Progress
Status in telephony-service package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
Fix Released
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1482317
Title:
Unify code that turns screen on when a notification happens
Status in unity8 package in Ubuntu:
Confirmed
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
Humph... Unity8 is not running when the device is suspended, is it?
That might put a damper on this plan.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1482317
Title:
Unify code that turns screen on when a notification happens
Status in unity8 package in Ubuntu:
New
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
Nevermind, I was confused by ubuntu-push not actually emitting a
displayable notification (one with popup=true on its card) when the
greeter is up. Which obscured my testing. It's an odd decision (to
me), but is a separate issue.
An MR is coming for this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1482317
Title:
Unify code that turns screen on when a notification happens
Status in unity8 package in Ubuntu:
New
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens
** Branch linked: lp:~mterry/unity8/turn-on-screen-when-notifying
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1482317
Title:
Unify code that turns screen on when a notification happens
Status in unity8 package in Ubuntu:
New
Bug description:
Right now, there are several places we ask USC to turn the screen on
when a notification happens:
- powerd for SMS, USSD, and incoming calls
- telephony-service for MMS and telephony messages
And we don't seem to be turning them on for ubuntu-push notifications,
but we should, right? Following the pattern above, we'd have ubuntu-
push itself turn the screen on, for a third location.
We don't turn the screen on at all for notifications that don't come
via those sources. For example, the following command line doesn't
turn the screen on, but I think it should:
gdbus call --session --dest org.freedesktop.Notifications --object-
path /org/freedesktop/Notifications --method
org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
0
It feels weird to have telephony-service turning the screen on.
Logically, it is just emitting a notification. The presentation of
that notification is up to a higher layer (maybe we're on a raspberry
pi2 and we present notifications as LED morse code or whatever). It
just makes sense that unity8, which is drawing the notification, is
the one that knows that the screen needs to be on. It also knows what
form factor we are in (I assume we only want to turn screen on for
phones/tablets, not desktops).
So I'm proposing that we unify all those places into one code path in
unity8 that can turn the screen on when a notification is received.
(This is a breakout bug from bug 1426115.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482317/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
