This problem started after the ota 14 update
--
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/1429887
Title:
Sometimes need 3 power button presses to turn on screen
Status
Update:
I have tested this some more now and it seems like the delay from
pressing the power button until the screen comes on gets longer the
longer the time lapse since the phone was last booted.
Yesterday, I had the following experience:
* With the phone on and screen off, I pressed the
Hi Michael,
I just tested, but so far only three times.
1st time: Screen came on after 17s showing the "turn off / restart /
cancel" dialogue box. This, incidentally, is something I often get when
switching on the screen.
2nd time: Screen came on normally after 15s.
3rd time: Screen came on
Thanks Ari, so that confirms that this is a delayed-screen-on bug, not a
screen-never-comes-on bug.
You mentioned the shutdown dialog appearing. That's bug 1508563, with a
fix incoming.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thanks, Ari. I also happened to catch this several times this weekend
on my phone, which is running rc-proposed (so OTA7+).
Here's an interesting tidbit though: I tried waiting after the first
power button press. So rather than thinking "oh, I must not have hit it
right" and pressing it again
Sorry for the late reply. I unfortunately overlooked your post.
Yes, I am on OTA-7 and I am getting it constantly, although not every
single time I want to turn on the screen.
Ari
Den 22. okt. 2015 20:20, skrev Michael Terry:
> I'm beginning to doubt that this is particularly associated with
I'm beginning to doubt that this is particularly associated with system
load (there was speculation that this is related to the scenario of wifi
APs causing NetworkManager and dbus-daemon to go crazy, slowing down the
system, which is a separate bug).
I've used the following script in
I did some more testing, trying to reproduce this. I did my usual "get
dbus-daemon to go crazy because I'm running through a bunch of wifi
networks" test in my neighborhood.
After getting my phone to be a bit overloaded, I still couldn't trigger
this bug even once.
But I did notice one oddity
On my handset I get the bug whether there are incoming notifications or
not. I have reproduced it three times out of four attempts while writing
a few emails on my laptop just now. No notifications.
Regards,
Ari
Den 21. okt. 2015 20:08, skrev Robie Basak:
> I think this might be related to the
I think this might be related to the phone powering on the screen after
a notification. That is: I believe the occurrence is higher after the
phone has woken the screen (and perhaps then timed out), compared to
when there was no notification since I last used it. This is because it
seems to affect
The last comment here is from July and I have been experiencing this
issue practically every single day since first asking about it on the
Ubuntu Phone mailing list in April, so I thought I'd take the time to
say that it is still an issue, and an extremely annoying one. If there
is anything I can
I experience this behavior everytime i leave a wifi network which my bq
4.5 was connected to. For ~10 minutes it reacts very slow. Even making a
phone call is not really possible.
This behavior goes away when i disable wifi on my phone.
--
You received this bug notification because you are a
incomplete until we can get a good reproduction scenario
** Changed in: canonical-devices-system-image
Status: Confirmed = Incomplete
** Changed in: canonical-devices-system-image
Milestone: ww21-2015 = None
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: powerd (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
I am seeing this again this week while traveling, only similarity was a lot of
APs listed which seems unrelated
Pressing 3 times quickly wakes it up without delay so it doesn't seem there
are events being processed at the time
** Changed in: canonical-devices-system-image
Importance:
15 matches
Mail list logo
