Also there is no way to stop the snoozing feature. Every 5 minutes it
will ring, there is no way to stop it. For me it also rings on events
with no notifications set, which are imported from google calendar, and
i've sometimes woken up from repeating reminders in the middle of the
night. Not a
I did a factory reset to resove this issue. That worked. I'll report
back if I manage to reproduce, but I'm not shooting for that right now.
As noone else is affected, that's not so productive, and I actually
prefer an autolocking phone.
--
You received this bug notification because you are a
Actually this is also a security issue, if someone forgets to manually
lock his phone, the phone will stay unlocked!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471597
Title:
MX4 ubuntu version
I find calling people is rather central in the whole 'phone' business.
It should be as easy as with other phones, or seeing as it's Ubuntu
actually the aim should be even higher. The dialer is a numeric one that
looks for a match in the 'phone number' field, why not change that to an
alphanumeric
Public bug reported:
MX4 Ubuntu version:
(I can't take a screenshot due to other issues, but:)
Battery statistic is not working (I hope). I'll describe the graph, and
at which points I verified this. While charging tonight, the battery
went gradually up from 20-55%, then instantly jumped to
Battery statistics are jumpy/jittery at times, with sharp drops/jumps in
battery remaining %. Reboot sometimes corrects this. I believe an uneven
battery may be the underlying cause, since it gradually got better.
Others (Armin Eder) are still affected, and if it returns with me it is
probably
*** This bug is a duplicate of bug 1471913 ***
https://bugs.launchpad.net/bugs/1471913
** This bug has been marked a duplicate of bug 1471913
[MX4] Battery statistics are incorrect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ah, also the weird thing is the phone does wake up for notifications and
such, so I think the monitor is still working, just neglects to turn off
after stay awake time runs out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm experiencing the same in MX4. Glad I'm not the only one - but that
doesn't help either of us. How can we supply information? Which service
should keep the screen awake / turn if off after x minutes? Where can I
find its logs?
--
You received this bug notification because you are a member of
** Attachment added: This is the output from powerd-cli test and the log
entries as described in the bug
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1471597/+attachment/4424660/+files/powerd-cli_test_Output_and_powerd_log
** Description changed:
I'm running 15.04 r2. Initially,
Public bug reported:
I'm running 15.04 r2. Initially, the screen locked nicely, but I turned
that off for a while (for USB access etc). Now it's turned back on
again, and it seems not to lock automatically anymore. Due to battery
consumption this is a pretty annoying bug.
I ran powerd-cli test:
Public bug reported:
Currently, the main way to make a call with dialer-app is to dial the
number. Most calls are made to contact entries, for which the number is
not memorised by the user, but rather the name. This creates unnecessary
steps in my opinion. (open dialer-tap contact icon-tap
stop/start network-manager allows me to reconnect. I use an MX4 by the
way, but now that I think about it I think I experienced the same with
E4.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470336
** Package changed: ubuntu = dialer-app (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470886
Title:
dialer allows no name search, inefficient route to contact search
To manage
I think I see the same thing. I think when I disable wifi and reboot it
turns back on, but if wifi has been on, it doesn't bother to connect.
And of course this is inconsistent, and sometimes difficult to
reproduce. Flight mode on/off doesn't seem to solve the problem
--
You received this bug
15 matches
Mail list logo
