[Bug 1470886] [NEW] dialer allows no name search, inefficient route to contact search
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 magnifier-type name) In reality it's faster to start the contacts app first if you want to call someone. To me that's illogical. This is quite a central feature, I think, that most other phone OSes offer. It would be nice if someone could try to pick this up. ** Affects: ubuntu Importance: Undecided Status: New -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1470886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470886] Re: dialer allows no name search, inefficient route to contact search
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1470886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470336] Re: Network manager problem
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470336 Title: Network manager problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1470336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470336] Re: Network manager problem
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 Title: Network manager problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1470336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466029] Re: Ubuntu Phone (Touch) won't turn off automatically after upgrade to OS 23
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466029 Title: Ubuntu Phone (Touch) won't turn off automatically after upgrade to OS 23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1466029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471597] Re: MX4 ubuntu version screen won't auto-lock
** 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, 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: all passed except the first: Test: checkForDbusName(test_dbusname, 0, requests, TRUE) - result: FAILED + result: FAILED - The following is syslog if I turn on the screen from locked state to - active, wait for >2 minutes (lock time is 1 min), and then turn off - again. - - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: handle_requestSysState from :1.13 (com.canonical.Unity.Screen) - ACTIVE (1) - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: name_watch_add: looking for :1.13 - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: watching :1.13 to see when it disappears on dbus - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: libsuspend: acquire_wake_lock: powerd_power_request - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: handle_requestSysState - SUCCESS - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: Enqueue state change to ACTIVE - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: exiting suspend - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: libsuspend: calling exit_suspend - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: libsuspend: exit_suspend succeeded - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: Emitting signal for transition to state ACTIVE (1) - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: Transition to ACTIVE complete - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: libsuspend: release_wake_lock: powerd_power_request - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: light_dev: setting brightness to 78 - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: we get signal from :1.14: DisplayPowerStateChange - Jul 5 22:12:08 ubuntu-phablet powerd[3893]: Received DisplayPowerStateChange: state=1 flags=2 - Jul 5 22:12:12 ubuntu-phablet powerd[3893]: handle_requestSysState from :1.22 (usensord) - ACTIVE (1) - Jul 5 22:12:12 ubuntu-phablet powerd[3893]: name_watch_add: looking for :1.22 - Jul 5 22:12:12 ubuntu-phablet powerd[3893]: watching :1.22 to see when it disappears on dbus - Jul 5 22:12:12 ubuntu-phablet powerd[3893]: libsuspend: acquire_wake_lock: powerd_power_request - Jul 5 22:12:12 ubuntu-phablet powerd[3893]: handle_requestSysState - SUCCESS - Jul 5 22:12:12 ubuntu-phablet powerd[3893]: Enqueue state change to ACTIVE - Jul 5 22:12:12 ubuntu-phablet powerd[3893]: queue empty && state == current, discarding - Jul 5 22:12:12 ubuntu-phablet powerd[3893]: libsuspend: release_wake_lock: powerd_power_request - Jul 5 22:12:15 ubuntu-phablet powerd[3893]: handle_clearSysState from :1.22, cookie: 8096ad4e-6c90-4852-97e2-dac9866d21e0 - Jul 5 22:12:15 ubuntu-phablet powerd[3893]: clear_sys_request: usensord - :1.22 - Jul 5 22:12:15 ubuntu-phablet powerd[3893]: name_watch_remove: looking for :1.22 - Jul 5 22:12:15 ubuntu-phablet powerd[3893]: name_watch: ref_count for :1.22 is now 0 - Jul 5 22:12:15 ubuntu-phablet powerd[3893]: no longer watching :1.22, there are no more requests - Jul 5 22:12:15 ubuntu-phablet powerd[3893]: libsuspend: acquire_wake_lock: powerd_power_request - Jul 5 22:12:15 ubuntu-phablet powerd[3893]: Enqueue state change to ACTIVE - Jul 5 22:12:15 ubuntu-phablet powerd[3893]: queue empty && state == current, discarding - Jul 5 22:12:15 ubuntu-phablet powerd[3893]: libsuspend: release_wake_lock: powerd_power_request - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: light_dev: setting brightness to 0 - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: we get signal from :1.14: DisplayPowerStateChange - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: Received DisplayPowerStateChange: state=0 flags=2 - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: handle_clearSysState from :1.13, cookie: 28dfac1e-72a2-4e07-81c2-eb50380d620d - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: clear_sys_request: com.canonical.Unity.Screen - :1.13 - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: name_watch_remove: looking for :1.13 - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: name_watch: ref_count for :1.13 is now 0 - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: no longer watching :1.13, there are no more requests - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: libsuspend: acquire_wake_lock: powerd_power_request - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: Enqueue state change to SUSPEND - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: libsuspend: prepare_suspend. - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: Emitting signal for transition to state SUSPEND (0) - Jul 5 22:14:27 ubuntu-phablet powerd[3893]: entering suspend - Jul 5 22:14:27 ubuntu-p
[Bug 1471597] [NEW] MX4 ubuntu version screen won't auto-lock
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: all passed except the first: Test: checkForDbusName(test_dbusname, 0, requests, TRUE) result: FAILED Attached is the full output and the syslog entries for a period where I turn on the screen, wait for 2 minutes, and turn it off again. (lock time is 1 minute. Also doesn't turn off after 1hr) What does it mean that testdbus_name is failing? What should happen when screen autolocks? ** Affects: powerd (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-desktop3 (Ubuntu) => powerd (Ubuntu) -- 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 screen won't auto-lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1471597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471597] Re: MX4 ubuntu version screen won't auto-lock
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. https://bugs.launchpad.net/bugs/1471597 Title: MX4 ubuntu version screen won't auto-lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1471597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440111] Re: [calendar] Reminder notifications are not integrated into system notifications
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 very cool 'feature'. Also I still didn't know what the reminder was for. MX4 15.04 r3 cal0.4.688.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440111 Title: [calendar] Reminder notifications are not integrated into system notifications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1440111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1472166] [NEW] Battery statistics are incorrect for MX4
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 100%, where it stayed for 4 hours. So far, so good. I played a game for a while, (<1hr) and suddenly I was warned at(below?) 10% battery. Rather fast drain, but shit happens. So I close game and quickly connect charger. Battery statistics say 0% at this point. I wait for a while, (5 minutes) and notice 1%. Because I want to take a screenshot, I unplug from charger to plug into usb connection, but phone dies instantly when I pull the plug. Boots normally, and says 75% battery. WTF? Battery stats graph in settings menu seems to be lagging behind on reality, but the real issue is I don't know if the battery is unstable or the statistics package is giving false readings. If readings were false, why did phone power off? It was no normal shutdown, rather hard power off. How can I supply more data? ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472166 Title: Battery statistics are incorrect for MX4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1472166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1472166] Re: Battery statistics are incorrect for MX4
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 still a software issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472166 Title: Battery statistics are incorrect for MX4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1472166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1472166] Re: Battery statistics are incorrect for MX4
*** 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 Ubuntu. https://bugs.launchpad.net/bugs/1472166 Title: Battery statistics are incorrect for MX4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1472166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1456626] Re: [Dialer] ubuntu touch bad dialer/contacts integration
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 that matches with number or name? It doesn't have to be difficult! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1456626 Title: [Dialer] ubuntu touch bad dialer/contacts integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471597] Re: MX4 ubuntu version screen won't auto-lock
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 screen won't auto-lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1471597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471597] Re: MX4 ubuntu version screen won't auto-lock
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471597 Title: MX4 ubuntu version screen won't auto-lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1471597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
