[Touch-packages] [Bug 1368811] Re: [SDK] Bottom edge behaviour needs refining
** Changed in: ubuntu-ux Status: In Progress => Fix Committed ** Description changed: - Move the bottom edge hint into the SDK so it's behavour is consistent across apps, and make the hiding of the bottom edge hint less aggressive. - When the user grabs the bottom edge, leave the tab visible until the user releases - Find a way to make it possible to pull down screens accessed via the bottom edge to make the gesture reversible. + + -- UX comment -- + + The spec for the bottom edge was updated into the UI toolkit documentation. + https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit?pli=1#heading=h.y7e1o2x66nvr -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1368811 Title: [SDK] Bottom edge behaviour needs refining Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: - Move the bottom edge hint into the SDK so it's behavour is consistent across apps, and make the hiding of the bottom edge hint less aggressive. - When the user grabs the bottom edge, leave the tab visible until the user releases - Find a way to make it possible to pull down screens accessed via the bottom edge to make the gesture reversible. -- UX comment -- The spec for the bottom edge was updated into the UI toolkit documentation. https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit?pli=1#heading=h.y7e1o2x66nvr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368811/+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 1367412] Re: [address book] no landscape support
** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1367412 Title: [address book] no landscape support Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Long contact name handling seems to behave somewhat erratically but normally ends in "...". The expectation is that turning the screen sideways would allow the full contact name to be shown but the app doesn't seem to support this yet. -- UX comment-- The desired solution is that the address book app will be able to rotate into landscape. There is a new header design for landscape on mobile and it will be part of the UI toolkit. Once the header lands, then the address book can use it. As for the long name issue: Once the AB rotates into landscape, long names should have more space to be displayed. The new header design for mobile landscape can be found here: https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#heading=h.a8gwztgmbhpq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1367412/+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 1513079] Re: Sections are aligned to the left
Marking as "Invalid" as it is intended design and behaviour, not a bug. ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: New => Opinion ** Description changed: I just noticed that head.sections are aligned to the left when using Ubuntu.Components 1.3. In my opinion it looks unbalanced and "wrong". In the previous version of the framework(1.2) they were centered. Screenshot attached + + + --- UX comment -- + + The behaviour and visual design is intended and went through various + review cycles. There won't be any change to that component in near + future. ** Changed in: ubuntu-ux Status: Opinion => Invalid ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1513079 Title: Sections are aligned to the left Status in Ubuntu UX: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: I just noticed that head.sections are aligned to the left when using Ubuntu.Components 1.3. In my opinion it looks unbalanced and "wrong". In the previous version of the framework(1.2) they were centered. Screenshot attached --- UX comment -- The behaviour and visual design is intended and went through various review cycles. There won't be any change to that component in near future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1513079/+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 1500483] Re: [sdk] animate header component when app comes back to the foreground
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1500483 Title: [sdk] animate header component when app comes back to the foreground Status in Ubuntu UX: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: When the header is hidden by scrolling it out of the view in an app, and the user switches between apps, when an app comes back to the foreground, the header instantly appears again. This means when going back to a previous app, the app is not in exactly the same state as where the user left it. Example: - Open gallery-app - Scroll down to hide the header (you need to have enough photos in the gallery to scroll down). - Long left/right edge swipe to hide send the gallery-app to the background - Re-open the gallery app Result: The gallery-app re-opens with the header visible. This can be confusing for the user. Two possible solutions: 1. Show the header when re-opening the app, but animate it so the user knows what is happening 2. Don't do anything. Header stays hidden and the user can show it as they normally would. After discussing with Olga, we decided to go for solution 1. The header will show, but it must animate. -- UX comment - As described above: The header should animate once user navigates back to the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1500483/+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 1443869] Re: [Edge Education] New wizard in Vivid doesn't excercise indicator gesture
** Changed in: ubuntu-ux Assignee: Andreea Pirvu (andreea-pirvu) => Paty Davila (dizzypaty) -- 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/1443869 Title: [Edge Education] New wizard in Vivid doesn't excercise indicator gesture Status in Ubuntu UX: In Progress Status in unity8 package in Ubuntu: Incomplete Bug description: Test case. - Flash the device with a recent Vivid image. - Complete the wizard. - Go through edges demo. Expected result. - Edges demo exercises the indicator gesture. Actual result. - Indicators aren't opened. current build number: 184 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1443869/+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 1484383] Re: [Edge education] Tutorial doesn't teach you about the long swipe from left
** Changed in: ubuntu-ux Assignee: Andreea Pirvu (andreea-pirvu) => Paty Davila (dizzypaty) -- 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/1484383 Title: [Edge education] Tutorial doesn't teach you about the long swipe from left Status in Ubuntu UX: In Progress Status in unity8 package in Ubuntu: Incomplete Bug description: I've only just discovered the long swipe from the left to get to the apps scope. I feel like an idiot but it turns out it's quite hard to find out about or discover accidentally. Even the Unity8 tutorial fails to show this feature to the user. You can (in fact, must) get through the tutorial using only a short swipe from the left to show the launcher. The long swipe remains a somewhat hidden feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1484383/+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 1456612] Re: [coachmarks] The discoverability of 'recent call' tab was poor
** Changed in: ubuntu-ux Assignee: Andreea Pirvu (andreea-pirvu) => Paty Davila (dizzypaty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1456612 Title: [coachmarks] The discoverability of 'recent call' tab was poor Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: The testers would like a stronger visual hint or to be introduced to the bottom tab function in the first time tutorial - UX comment This is not a dialer issue but more of how the bottom edge hint behaves across all apps. An empty screen state could solve the problem but potentially the SDK component will have to be updated with additional visual design. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456612/+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 1382621] Re: [sim pin] prompt on boot but after greeter
** Changed in: ubuntu-ux Assignee: Andreea Pirvu (andreea-pirvu) => Paty Davila (dizzypaty) -- 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/1382621 Title: [sim pin] prompt on boot but after greeter Status in Ubuntu UX: In Progress Status in indicator-network package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: Per this bug 1382604 it was discussed that the sim pin prompt is occuring before the greeter on boot, and doesn't seem to match the spec per this bug 1333121 -UX comment Desired resolution: As mentioned in comment #5 and this bug https://bugs.launchpad.net/ubuntu-ux/+bug/1397963 we need to redesign the authentication dialog and let it show after the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1382621/+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 1407930] Re: [coachmarks] Need to educate users about drag-for-action gestures
** Changed in: ubuntu-ux Assignee: Andreea Pirvu (andreea-pirvu) => Paty Davila (dizzypaty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1407930 Title: [coachmarks] Need to educate users about drag-for-action gestures Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: The drag-left/right gestures to remove items or get a context menu on them are not obvious, we need to find a place to educate users about those, seeing as those get more and more usage across the phone. This might be something for the initial shell demo, or maybe the SDK should have a "learning" mode the first few times a draggable item is displayed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 12:19:41 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1407930/+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 1486872] Re: Can skip wizard steps after you tap on notification"Storage device detected"
** Changed in: ubuntu-ux Assignee: Andreea Pirvu (andreea-pirvu) => Paty Davila (dizzypaty) -- 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/1486872 Title: Can skip wizard steps after you tap on notification"Storage device detected" Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: $ system-image-cli -i current build number: 104 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-08-20 03:24:50 version version: 104 version ubuntu: 20150819 version device: 20150817-3879cb2 version custom: 20150814-887-30-30-vivid Reproduce steps: 1,Boot the phone with SD card inserted 2,Wait a while on wizard page > notification ¨Storage device deteced¨ pops up for SD card 3.Tap on the notification > external storage opens 4.Exit external storage Actual=> it backs to today scope Expect=>Can't skip wizard steps To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1486872/+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 1435877] Re: [edge education] tutorial not adapted to desktop mode
** Changed in: ubuntu-ux Assignee: Andreea Pirvu (andreea-pirvu) => Paty Davila (dizzypaty) -- 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/1435877 Title: [edge education] tutorial not adapted to desktop mode Status in Ubuntu UX: In Progress Status in unity8 package in Ubuntu: Incomplete Bug description: The first unity8 run shows you a tutorial explaining how the edges gestures work, that's also the case on the desktop-next iso, but some details don't fit well there - the switcher previews are not nicely scaled - the "there are your software" suggest that the dash is taking the screen, which is not the case - it might make sense to not restrict the explanations to be touch specific? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1435877/+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 1397963] Re: [sim pin] SIM PIN + passcode screens too similar
** Changed in: ubuntu-ux Assignee: Andreea Pirvu (andreea-pirvu) => Paty Davila (dizzypaty) -- 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/1397963 Title: [sim pin] SIM PIN + passcode screens too similar Status in Ubuntu UX: In Progress Status in unity8 package in Ubuntu: Incomplete Bug description: unity8 8.01+15.04.20141125.2-0ubuntu1, Ubuntu 15.04 The SIM PIN and lock-screen dialogs for passcode are too similar to one another, I repeatedly end up putting my passcode as SIM PIN, this could lead to locking your SIM card. Fixing this might also fix bug 1387207. UX comment-- Desired resolution: please see comment #2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1397963/+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 1456641] Re: [Dialer] Phone was locked during the phone call and can't hang up without having to unlock first
** Description changed: Phone was locked during the phone call and can't hang up without having to unlock first + + - UX comment --- + + The behaviour for a phone call should follow this specification: + + https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0/edit + + Please refer to the use cases in this document. ** Changed in: ubuntu-ux Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1456641 Title: [Dialer] Phone was locked during the phone call and can't hang up without having to unlock first Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: New Bug description: Phone was locked during the phone call and can't hang up without having to unlock first - UX comment --- The behaviour for a phone call should follow this specification: https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0/edit Please refer to the use cases in this document. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456641/+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 1512430] Re: Shouldn't be able to swipe away incoming call notification
** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: New => Triaged ** Changed in: ubuntu-ux Importance: Undecided => High ** Summary changed: - Shouldn't be able to swipe away incoming call notification + [phone] Shouldn't be able to swipe away incoming call notification -- 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/1512430 Title: [phone] Shouldn't be able to swipe away incoming call notification Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: latest rc-proposed on krillin Steps to reproduce: 1) lock phone 2) call phone 3) press volume down button to lower the volume, this causes sound notification to be shown and incoming call notification to be reduced in height 4) while incoming call notification reduced in height, swipe it from left to right Expected results: incoming call notification should not be dismissed, so you can still answer the phone Actual results: incoming call notification is dismissed and you now have no way to answer the incoming call To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512430/+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 1513642] Re: Change "Back button" to simple right-swipe from the center of the screen.
Marking as INVALID, please see UX comment in bug description. ** Description changed: Back button is located in left-upper corner. Stretching the thumb to that corner is not easy (regardless left- or right-hand usage). More natural will be using horisontal swipe from the middle of the screen, the same way as it's done for shuffling scopes back. I think it will work almost everywhere, making interface experience more streamlined. + + UX comment --- + + While swiping left and right in the center of the screen for navigational purposes works for scopes, it would lead to issues in many other places. + As stated below, list items have the ability being swiped to the left and to the right, which would interfere with the navigation. An other example is the camera app, where user access their camera roll/last picture shot. + + This is why the proposed interaction is not suitable navigating between + applications. ** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Status: New => Invalid ** Changed in: ubuntu-ux Importance: Undecided => Wishlist ** Summary changed: - Change "Back button" to simple right-swipe from the center of the screen. + [sdk] Change "Back button" to simple right-swipe from the center of the screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1513642 Title: [sdk] Change "Back button" to simple right-swipe from the center of the screen. Status in Ubuntu UX: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Back button is located in left-upper corner. Stretching the thumb to that corner is not easy (regardless left- or right-hand usage). More natural will be using horisontal swipe from the middle of the screen, the same way as it's done for shuffling scopes back. I think it will work almost everywhere, making interface experience more streamlined. UX comment --- While swiping left and right in the center of the screen for navigational purposes works for scopes, it would lead to issues in many other places. As stated below, list items have the ability being swiped to the left and to the right, which would interfere with the navigation. An other example is the camera app, where user access their camera roll/last picture shot. This is why the proposed interaction is not suitable navigating between applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1513642/+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 1512327] Re: [dialer-app] Can't hang up phone calls
** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1512327 Title: [dialer-app] Can't hang up phone calls Status in Ubuntu UX: New Status in dialer-app package in Ubuntu: New Bug description: Recently I had a problem with hanging up. I don't think it was just with incoming calls but in that case I was able to reproduce it. I have all the recent updates installed and I think the problem only occurred after the update to OTA-7. - Somebody calls me - Name appears in the dialog and I take off - The dialer app opens but doesn't show the name nor number nor the calling time but the call works - It is not possible to hang up the call by pressing the red button - I close the dialer app, the green bar at the top appears - I reopen it, at this point I might be able to hang up the call otherwise I have to redo the closing I couldn't find the combination which led to this issue. Could be related to bug #1377996. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1512327/+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 1512327] Re: [dialer-app] Can't hang up phone calls
** Description changed: Recently I had a problem with hanging up. I don't think it was just with incoming calls but in that case I was able to reproduce it. I have all the recent updates installed and I think the problem only occurred after the update to OTA-7. - Somebody calls me - Name appears in the dialog and I take off - The dialer app opens but doesn't show the name nor number nor the calling time but the call works - It is not possible to hang up the call by pressing the red button - I close the dialer app, the green bar at the top appears - I reopen it, at this point I might be able to hang up the call otherwise I have to redo the closing I couldn't find the combination which led to this issue. Could be related to bug #1377996. + + + - UX comment --- + + The dialer should always show the contact who is calling. Also, it + should always be possible to hang up the call. ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: New => Fix Committed ** Changed in: ubuntu-ux Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1512327 Title: [dialer-app] Can't hang up phone calls Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: New Bug description: Recently I had a problem with hanging up. I don't think it was just with incoming calls but in that case I was able to reproduce it. I have all the recent updates installed and I think the problem only occurred after the update to OTA-7. - Somebody calls me - Name appears in the dialog and I take off - The dialer app opens but doesn't show the name nor number nor the calling time but the call works - It is not possible to hang up the call by pressing the red button - I close the dialer app, the green bar at the top appears - I reopen it, at this point I might be able to hang up the call otherwise I have to redo the closing I couldn't find the combination which led to this issue. Could be related to bug #1377996. - UX comment --- The dialer should always show the contact who is calling. Also, it should always be possible to hang up the call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1512327/+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 1502205] Re: [notification] [messaging app] message notification does not link to correct message thread
** Summary changed: - message notification does not link to correct message thread + [notification] [messaging app] message notification does not link to correct message thread ** Description changed: When a device is in pin locked (or password locked) state, a notification is displayed when a message is received. However, when the user requests to be redirected to the message thread (and enters pin or password) he is not redirected to the correct thread. Instead, he gets redirected to the most recently active screen/thread in the messaging app, which usually is some other message thread. He then has to exit this thread and open the one he wished to see. + + --- UX comment + + The desired behaviour is: + 1. user taps on notification + 2. enter PIN/PASSWORD on corresponding screen + 3. messaging app should open, presenting user with the correct message thread ** Also affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1502205 Title: [notification] [messaging app] message notification does not link to correct message thread Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: New Bug description: When a device is in pin locked (or password locked) state, a notification is displayed when a message is received. However, when the user requests to be redirected to the message thread (and enters pin or password) he is not redirected to the correct thread. Instead, he gets redirected to the most recently active screen/thread in the messaging app, which usually is some other message thread. He then has to exit this thread and open the one he wished to see. --- UX comment The desired behaviour is: 1. user taps on notification 2. enter PIN/PASSWORD on corresponding screen 3. messaging app should open, presenting user with the correct message thread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1502205/+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 1510659] Re: Enable T9 for names search with dialer
** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Importance: Undecided => Wishlist ** Changed in: ubuntu-ux Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1510659 Title: Enable T9 for names search with dialer Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: New Bug description: In the dialer app of the OS with the green robot it is possible to search for telephone numbers by inputting the names via T9. Example: A "Dave" and his phone number could be found by typing 3, 2, 8 and 3, as these are the T9 keys for the D, A, V and E. I don't like green robots, but this function is snappy. Thank you + best regards! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1510659/+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 1368811] Re: [SDK] Bottom edge behaviour needs refining
** Changed in: ubuntu-ux Importance: Medium => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1368811 Title: [SDK] Bottom edge behaviour needs refining Status in Canonical System Image: In Progress Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: - Move the bottom edge hint into the SDK so it's behavour is consistent across apps, and make the hiding of the bottom edge hint less aggressive. - When the user grabs the bottom edge, leave the tab visible until the user releases - Find a way to make it possible to pull down screens accessed via the bottom edge to make the gesture reversible. -- UX comment -- The spec for the bottom edge was updated into the UI toolkit documentation. https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit?pli=1#heading=h.y7e1o2x66nvr To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368811/+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 1506535] Re: Add export to .vcf or/and vcard to sharing menu
** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Importance: Undecided => Medium ** Changed in: ubuntu-ux Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1506535 Title: [address-book] Add export to .vcf or/and vcard to sharing menu Status in Ubuntu UX: Triaged Status in address-book-app package in Ubuntu: New Bug description: Sharing contacts is a key feature IMHO and at the moment only sharing trough SMS is available in address-book-app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1506535/+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 1323837] Re: [phone] Sim toolkit is not available on UT
** Summary changed: - Sim toolkit is not available on UT + [phone] Sim toolkit is not available on UT -- 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/1323837 Title: [phone] Sim toolkit is not available on UT Status in Canonical System Image: Incomplete Status in Ubuntu UX: Triaged Status in ofono package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ /SIM-Toolkit While a lot of those addons are completely crap and useless, the SIm toolkit is sometimes used by some phone provider to set your sim card to roaming mode when you are abroad which makes it a must have. For the moment i need to borrow a second phone put my sim card in it, go to the Sim-toolkit, enable my sim card for roaming and put the sim card back in my UT to get my phone working while i am abroad. I need to do the same when i go back home. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1323837/+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 1511471] Re: [address book] Adding a online account should not change the default address book.
** Description changed: The current version of Contacts APP uses the last added account as default account when creating contacts. This cause confusion with the user because this happen without the user notice and the Address book selector is most of the time obscured by the virtual keyboard. + + + UX comment + + When a new account is added and contacts are synced with the AB, the + added account should NOT become a default. + + If users want to change the default account, they always have to do it + manually for now. This option should be available through AB app + settings. ** Changed in: ubuntu-ux Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1511471 Title: [address book] Adding a online account should not change the default address book. Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: New Bug description: The current version of Contacts APP uses the last added account as default account when creating contacts. This cause confusion with the user because this happen without the user notice and the Address book selector is most of the time obscured by the virtual keyboard. UX comment When a new account is added and contacts are synced with the AB, the added account should NOT become a default. If users want to change the default account, they always have to do it manually for now. This option should be available through AB app settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1511471/+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 1506535] Re: [address-book] Add export to .vcf or/and vcard to sharing menu
** Summary changed: - Add export to .vcf or/and vcard to sharing menu + [address-book] Add export to .vcf or/and vcard to sharing menu ** Changed in: ubuntu-ux Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1506535 Title: [address-book] Add export to .vcf or/and vcard to sharing menu Status in Ubuntu UX: Triaged Status in address-book-app package in Ubuntu: New Bug description: Sharing contacts is a key feature IMHO and at the moment only sharing trough SMS is available in address-book-app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1506535/+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 1482551] Re: Phone app -> Settings -> Back doesn't return to Phone app
This is a design issue because design needs to provide the right way of navigation. Added ubuntu-ux back to the bug. ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Status: New => Triaged ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1482551 Title: Phone app -> Settings -> Back doesn't return to Phone app Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: Triaged Bug description: From settings in telephony suite, when tap return button, it goes back to system settings instead of phone/one of the telephony suite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1482551/+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 1487528] Re: [notifications] + [messaging] SMS notifications should should show which SIM received message
** Summary changed: - SMS notifications should should show which SIM received message + [notifications] + [messaging] SMS notifications should should show which SIM received message -- 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/1487528 Title: [notifications] + [messaging] SMS notifications should should show which SIM received message Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in telephony-service package in Ubuntu: Confirmed Bug description: User does not see onto which SIM card the SMS was received on the lock screen (if this option is enabled by device privacy settings). It is great that used has option to reply immediately, without unlocking the device, but it is not possible to know, which SIM card to use to reply back. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487528/+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 1487528] Re: [notifications] + [messaging] SMS notifications should should show which SIM received message
Wireframe for SIM card stamp. ** Description changed: User does not see onto which SIM card the SMS was received on the lock screen (if this option is enabled by device privacy settings). It is great that used has option to reply immediately, without unlocking the device, but it is not possible to know, which SIM card to use to reply back. + + + UX comment --- + + Please find attached to this bug a design solution which will allow + users to see which SIM card is used on the notification bubble. + + The label of the SIM card should always represent the label users set, + even if they renamed the sim cards. ** Attachment added: "112015 incoming notification SMS MMS SIM stamp.jpg" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487528/+attachment/4522705/+files/112015%20incoming%20notification%20SMS%20MMS%20SIM%20stamp.jpg ** Changed in: ubuntu-ux Status: Triaged => Fix Committed -- 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/1487528 Title: [notifications] + [messaging] SMS notifications should should show which SIM received message Status in Canonical System Image: Confirmed Status in Ubuntu UX: Fix Committed Status in telephony-service package in Ubuntu: Confirmed Bug description: User does not see onto which SIM card the SMS was received on the lock screen (if this option is enabled by device privacy settings). It is great that used has option to reply immediately, without unlocking the device, but it is not possible to know, which SIM card to use to reply back. UX comment --- Please find attached to this bug a design solution which will allow users to see which SIM card is used on the notification bubble. The label of the SIM card should always represent the label users set, even if they renamed the sim cards. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487528/+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 1487528] Re: [notifications] + [messaging] SMS notifications should should show which SIM received message
** Description changed: User does not see onto which SIM card the SMS was received on the lock screen (if this option is enabled by device privacy settings). It is great that used has option to reply immediately, without unlocking the device, but it is not possible to know, which SIM card to use to reply back. - UX comment --- Please find attached to this bug a design solution which will allow - users to see which SIM card is used on the notification bubble. + users to see which SIM card is used on the notification bubble. There is + a SIM stamp on the right hand side, centered with the name. The label of the SIM card should always represent the label users set, even if they renamed the sim cards. -- 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/1487528 Title: [notifications] + [messaging] SMS notifications should should show which SIM received message Status in Canonical System Image: Confirmed Status in Ubuntu UX: Fix Committed Status in telephony-service package in Ubuntu: Confirmed Bug description: User does not see onto which SIM card the SMS was received on the lock screen (if this option is enabled by device privacy settings). It is great that used has option to reply immediately, without unlocking the device, but it is not possible to know, which SIM card to use to reply back. UX comment --- Please find attached to this bug a design solution which will allow users to see which SIM card is used on the notification bubble. There is a SIM stamp on the right hand side, centered with the name. The label of the SIM card should always represent the label users set, even if they renamed the sim cards. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487528/+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 1460301] Re: [Dialer] Incoming call - no info which SIM card was called (dual SIM)
Please find desired solution in attachment. The SIM indication should be inline with the "Incoming call" text. Marking as Fix Commited. ** Changed in: ubuntu-ux Status: Triaged => Fix Committed ** Description changed: Ubuntu 14.10 (r22) (Don't know how to find a package version :/, but I checked for updates on 29-05-2015 and all apps are up to date) - I have two SIM cards inserted into BQ Aquaris 4.5 On incoming call I expect to see information if SIM1 or SIM2 was dialled by caller alongside caller ID. I see only caller ID. It may be useful if one of the SIM cards is in roaming, or when one of the SIMs is a company number while other is a private number. + + UX comment --- + + The SIM card indication should be next to the text stating "Incoming + call". Please see attached wireframe for the exact solution. ** Attachment added: "112015Incoming call snap with SIM indication.jpg" https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1460301/+attachment/4522719/+files/112015Incoming%20call%20snap%20with%20SIM%20indication.jpg -- 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/1460301 Title: [Dialer] Incoming call - no info which SIM card was called (dual SIM) Status in Canonical System Image: Confirmed Status in Ubuntu UX: Fix Committed Status in telephony-service package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 (r22) (Don't know how to find a package version :/, but I checked for updates on 29-05-2015 and all apps are up to date) I have two SIM cards inserted into BQ Aquaris 4.5 On incoming call I expect to see information if SIM1 or SIM2 was dialled by caller alongside caller ID. I see only caller ID. It may be useful if one of the SIM cards is in roaming, or when one of the SIMs is a company number while other is a private number. UX comment --- The SIM card indication should be next to the text stating "Incoming call". Please see attached wireframe for the exact solution. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1460301/+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 1387207] Re: [greeter] strange persistent "Enter SIM1 PIN" dialog on Greeter
I'm really sorry but it still does happen on krillin: tested it on 15.04 (r140) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1387207 Title: [greeter] strange persistent "Enter SIM1 PIN" dialog on Greeter Status in Ubuntu UX: Fix Committed Status in indicator-network package in Ubuntu: Fix Released Status in unity-notifications package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: Invalid Bug description: Build r133 Krillin I'm not entirely sure how to reproduce this bug but I try to sum up the conditions and how the phone was set up before. 1. Make sure both SIM cards are inserted 2. SIM1 is locked 3. reboot device 4 skip SIM PIN entry When skipping the SIM PIN entry screen, you can see a small glitch on the top of the screen. It looks like a dialog/snap but it disappears very quickly. Now, I had my device locked for a while and when I unlocked it via the hard key button a snap decision appeared on top of the greeter saying "Enter SIM PIN1". It is possible to swipe away the greeter screen but then this is it. You are basically stuck. I managed as well to pull down the notifications menu but the snap stayed on top of that. It looks like there is there passcode screen in the background and if you want to return back to the greeter you have to lock/unlock the device with the hard key button. Maybe anyone can reproduce this bug or knows what causes it. Please see attached screenshots for more visual info. Update: 14.04 r269 krillin The glitch of briefly appearing dialog still persists. Every time the device is rebooted and user has to enter the SIM PIN. UX comment- The desired resolution is that users are presented with the actual SIM PIN screen without the appearing glitch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1387207/+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 1375513] Re: [phone-app] bypass lock on shell possible
Marking as Fix Released: tested on krillin 15.04 (r140) ** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1375513 Title: [phone-app] bypass lock on shell possible Status in dialer-app: Fix Released Status in Ubuntu UX: Fix Released Status in dialer-app package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: from a private bug 1374773 With the "Recent" option in the dialer in emergency call mode it's possible to get to the task switcher, app scope Steps to reproduce 1. Set a passcode 2. Swipe away welcome screen 3. Tap 'emergency call' - phone opens 4. Swipe "Recent" bottom edge up 5. Swipe a contact left, choose message (screen locks, wait for osk) 6. Swipe away osk 7. Tap 'emergency call' - phone opens again to 'recent' 8. Swipe left a person, tap person icon (screen locks) 9. Tap 'emergency call' 10. Swipe in from right of screen, observe muliple apps, and you can pick any of them. This bypasses screen lock. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1375513/+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 1490754] Re: [dialler] No vibration during a call
** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1490754 Title: [dialler] No vibration during a call Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: New Bug description: It happend to me a few times, that I was on the phone, explaining something and suddenly my phone started buzzing right next to my ear. The reason was an incomming message. It would be nice to have a more discreet information about an incomming message when you are on a call. My Nokia phone just did a little beep, which was not distracting but noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1490754/+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 1490754] Re: [dialler] No vibration during a call
** Description changed: It happend to me a few times, that I was on the phone, explaining something and suddenly my phone started buzzing right next to my ear. - The reason was an incomming message. It would be nice to have a more - discreet information about an incomming message when you are on a call. + The reason was an incoming message. It would be nice to have a more + discreet information about an incoming message when you are on a call. My Nokia phone just did a little beep, which was not distracting but noticeable. + + --- UX comment --- + + I understand that the buzzing is not ideal. The desired solution is: + If a message comes in while user is on a call, the vibration is disabled. a beeping tone in the phone speaker should signal user about the message, even if the phone is taking place via headphones. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1490754 Title: [dialler] No vibration during a call Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: New Bug description: It happend to me a few times, that I was on the phone, explaining something and suddenly my phone started buzzing right next to my ear. The reason was an incoming message. It would be nice to have a more discreet information about an incoming message when you are on a call. My Nokia phone just did a little beep, which was not distracting but noticeable. --- UX comment --- I understand that the buzzing is not ideal. The desired solution is: If a message comes in while user is on a call, the vibration is disabled. a beeping tone in the phone speaker should signal user about the message, even if the phone is taking place via headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1490754/+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 1490754] Re: [dialler] No vibration during a call
** Also affects: unity-notifications (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1490754 Title: [dialler] No vibration during a call Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: New Status in unity-notifications package in Ubuntu: New Bug description: It happend to me a few times, that I was on the phone, explaining something and suddenly my phone started buzzing right next to my ear. The reason was an incoming message. It would be nice to have a more discreet information about an incoming message when you are on a call. My Nokia phone just did a little beep, which was not distracting but noticeable. --- UX comment --- I understand that the buzzing is not ideal. The desired solution is: If a message comes in while user is on a call, the vibration is disabled. a beeping tone in the phone speaker should signal user about the message, even if the phone is taking place via headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1490754/+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 1124071] Re: [tabs] Cannot add Tabs programmatically
** Changed in: ubuntu-ux Assignee: Giorgio Venturi (giorgio-venturi) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: Won't Fix => Fix Committed ** Summary changed: - [tabs] Cannot add Tabs programmatically + [tabs] + [header sections] Cannot add Tabs programmatically -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1124071 Title: [tabs] + [header sections] Cannot add Tabs programmatically Status in Ubuntu Shorts App: Confirmed Status in Ubuntu UI Toolkit: Fix Released Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Trusty: Confirmed Status in ubuntu-ui-toolkit source package in Vivid: New Bug description: There seems to be no easy way to add a Tab to Tabs programmatically. I would be nice to be able add, remove and edit Tabs dynamically. So far I haven't found a way to do this. I have made an Android style ViewPager based on ListView. It is quite easy to update the pages with ListModel methods. UX Comment --- Tabs component is not deprecated from UITK point of view. Design uses slightly different naming than UITK for components they design, we call "Tabs" now "Header Sections". This is a bar which sits below the main header. An other option to add "tabs" to your UI, allowing user to navigate through different sections of the app, is a navigation drawer on the left hand side of the header. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1124071/+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 1124071] Re: [tabs] + [header sections] Cannot add Tabs programmatically
** Description changed: There seems to be no easy way to add a Tab to Tabs programmatically. I would be nice to be able add, remove and edit Tabs dynamically. So far I haven't found a way to do this. I have made an Android style ViewPager based on ListView. It is quite easy to update the pages with ListModel methods. - UX Comments - Tabs are deprecated, use the new header instead, or headers sections + + UX Comment --- + + Tabs component is not deprecated from UITK point of view. Design uses slightly different naming than UITK for components they design, we call "Tabs" now "Header Sections". This is a bar which sits below the main header. + An other option to add "tabs" to your UI, allowing user to navigate through different sections of the app, is a navigation drawer on the left hand side of the header. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1124071 Title: [tabs] + [header sections] Cannot add Tabs programmatically Status in Ubuntu Shorts App: Confirmed Status in Ubuntu UI Toolkit: Fix Released Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit source package in Trusty: Confirmed Status in ubuntu-ui-toolkit source package in Vivid: New Bug description: There seems to be no easy way to add a Tab to Tabs programmatically. I would be nice to be able add, remove and edit Tabs dynamically. So far I haven't found a way to do this. I have made an Android style ViewPager based on ListView. It is quite easy to update the pages with ListModel methods. UX Comment --- Tabs component is not deprecated from UITK point of view. Design uses slightly different naming than UITK for components they design, we call "Tabs" now "Header Sections". This is a bar which sits below the main header. An other option to add "tabs" to your UI, allowing user to navigate through different sections of the app, is a navigation drawer on the left hand side of the header. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1124071/+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 1306078] Re: [system settings] per app data transfer over 3G should be configurable by the user
** Changed in: ubuntu-ux Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1306078 Title: [system settings] per app data transfer over 3G should be configurable by the user Status in sync-monitor: Confirmed Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: New Status in sync-monitor package in Ubuntu: Confirmed Status in ubuntu-calendar-app package in Ubuntu: New Bug description: by default we should not perform a sync when not connected to wifi. in the future this should be a setting. -UX comment-- desired resolution: In general Sync/background updates per up should be allowed in System Settings. However, switching off this functionality should be done per app basis, therefor should sit in App Settings. To manage notifications about this bug go to: https://bugs.launchpad.net/sync-monitor/+bug/1306078/+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 1388115] Re: [sdk] More actions visible in header with selection mode
** Changed in: ubuntu-ux Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1388115 Title: [sdk] More actions visible in header with selection mode Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The header has space for two (when there is a back/tabs button) or three actions on the right side. In selection mode, where the title text is hidden, there is more space available, so the header looks a bit empty. How many actions can go in the header in selection mode? --- UX Solution --- * For the phone, 4 slots can be accommodated in selection mode * For future work (tablet/desktop), we will need to provide some automatic/responsive layout rules for headers (e.g. actions at the top of an action menu will surface to the header) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1388115/+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 1439041] Re: Address-Book lists contacts from second google account without permission
** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: New => Triaged ** Changed in: ubuntu-ux Importance: Undecided => High ** Summary changed: - Address-Book lists contacts from second google account without permission + [Address-Book] lists contacts from second google account without permission -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1439041 Title: [Address-Book] lists contacts from second google account without permission Status in Ubuntu UX: Triaged Status in address-book-app package in Ubuntu: Confirmed Bug description: Hello, I am using the BQ phone. I have two google accounts registered in my online-accounts. The first account has access to all applications listed in online accounts. The second account is supposed to deliver only the calendar events of my wife. Hence I enabled for the second account only access to "calendar" and "com.ubuntu.developer...". However my address-book lists all contacts of my wife even though no access is granted in online accounts. The behavior not only affects the usability but is also a security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1439041/+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 1368811] Re: [SDK] Bottom edge behaviour needs refining
** Changed in: ubuntu-ux Assignee: Jouni Helminen (jounihelminen) => (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1368811 Title: [SDK] Bottom edge behaviour needs refining Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: - Move the bottom edge hint into the SDK so it's behavour is consistent across apps, and make the hiding of the bottom edge hint less aggressive. - When the user grabs the bottom edge, leave the tab visible until the user releases - Find a way to make it possible to pull down screens accessed via the bottom edge to make the gesture reversible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368811/+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 1504170] Re: [Indicators] Some icons in messaging-menu disappear when list items are selected
** Also affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1504170 Title: [Indicators] Some icons in messaging-menu disappear when list items are selected Status in Canonical System Image: New Status in Ubuntu UX: Triaged Status in indicator-messages package in Ubuntu: New Status in messaging-app package in Ubuntu: New Bug description: Steps to reproduce: 1) receive a message from a MMS group 2) open messaging-menu 3) verify the group icon is displayed 4) tap the message to reply 5) verify the icon disappears because it has the same color as the selection. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1504170/+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 1414740] Re: [phone-app] Multiple calls text delegate overlapping
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1414740 Title: [phone-app] Multiple calls text delegate overlapping Status in Dialer app for Ubuntu Touch: Fix Released Status in Ubuntu UX bugs: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu RTM: New Bug description: In the multiple calls screen, depending on the language and on the contact name labels are overlapping. Check the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1414740/+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 1389861] Re: [dialer-app] can't unlock phone during an incoming call
** Tags added: usability -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1389861 Title: [dialer-app] can't unlock phone during an incoming call Status in Ubuntu UX bugs: Triaged Status in dialer-app package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: While testing krillin rtm image 142, I noticed that the phone remains locked during an incoming call if the screen was off when the call came in. There is no way to unlock the phone to access other functions until after the call is done. It seems like a common use case to be able to do other things on the phone during a call, looking up someone's number or checking a map or whatever, but this currently is only possible during outgoing calls. During an incoming call I can't even access the indicators to change brightness or check today's date or even see what time it is, so it actually ends up being more "locked" than the lock screen. Could we add the ability to unlock the phone during a call received while locked? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1389861/+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 1389861] Re: [dialer-app] can't unlock phone during an incoming call
I would agree with mterry, we should have two different modes for the dialer when the device is locked. I can imagine that it would be then easier to make changes/fixes according to the specific use case. As for the initial bug, it looks like it was fixed. I tested it on vivid r207. The fact that indicators are not shown during the active call, if it was accepted while device is locked, seems to me a separate issue. ** Changed in: ubuntu-ux Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1389861 Title: [dialer-app] can't unlock phone during an incoming call Status in Ubuntu UX bugs: Fix Released Status in dialer-app package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: While testing krillin rtm image 142, I noticed that the phone remains locked during an incoming call if the screen was off when the call came in. There is no way to unlock the phone to access other functions until after the call is done. It seems like a common use case to be able to do other things on the phone during a call, looking up someone's number or checking a map or whatever, but this currently is only possible during outgoing calls. During an incoming call I can't even access the indicators to change brightness or check today's date or even see what time it is, so it actually ends up being more "locked" than the lock screen. Could we add the ability to unlock the phone during a call received while locked? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1389861/+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 1453217] [NEW] [indicators] tap to return to call shouldn't expand indicators
Public bug reported: Vivid r 207 steps to reproduce: 1. call device 2. accept call 3. navigate away, e.g. dash, different app... 4. the indicator panel should be now green and say "tap to return to call" 5. tap the panel actual result: The panel expands 1/3 of the screen and then navigates back to the active call screen. ---UX comment/expected result- The panel should not expand at all during the duration of the call and just navigate back to the calling screen. ** Affects: ubuntu-ux Importance: Medium Status: Triaged ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: usability ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453217 Title: [indicators] tap to return to call shouldn't expand indicators Status in Ubuntu UX bugs: Triaged Status in dialer-app package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Vivid r 207 steps to reproduce: 1. call device 2. accept call 3. navigate away, e.g. dash, different app... 4. the indicator panel should be now green and say "tap to return to call" 5. tap the panel actual result: The panel expands 1/3 of the screen and then navigates back to the active call screen. ---UX comment/expected result- The panel should not expand at all during the duration of the call and just navigate back to the calling screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1453217/+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 1453217] Re: [indicators] tap to return to call shouldn't expand indicators
** Changed in: ubuntu-ux Status: New => Triaged ** Changed in: ubuntu-ux Importance: Undecided => Medium ** Changed in: ubuntu-ux Assignee: (unassigned) => Paty Davila (dizzypaty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1453217 Title: [indicators] tap to return to call shouldn't expand indicators Status in Ubuntu UX bugs: Triaged Status in dialer-app package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Vivid r 207 steps to reproduce: 1. call device 2. accept call 3. navigate away, e.g. dash, different app... 4. the indicator panel should be now green and say "tap to return to call" 5. tap the panel actual result: The panel expands 1/3 of the screen and then navigates back to the active call screen. ---UX comment/expected result- The panel should not expand at all during the duration of the call and just navigate back to the calling screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1453217/+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 1417353] Re: [messaging-app] Make it easier to resend messages that can't be sent
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1417353 Title: [messaging-app] Make it easier to resend messages that can't be sent Status in the base for Ubuntu mobile products: New Status in Messaging App: Fix Released Status in Ubuntu UX bugs: Fix Released Status in history-service package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu RTM: New Bug description: From usability testing: Testers expected the phone to provide a resent option or to automatically resend the message when the singal is back if a message is not sent successfully Testers received a 'no network' pop up, and the full text message stayed in the compose bar. As a result, they had to constantly check if the network is back, and then resend the message again. Phone is often used on the move, and network issue can be a common issue when such as on the train or around places where full of high buildings. It is important to design for these retrictions. Proposed solution: Until we have "Save as draft" support, I'd propose the following: - If we detect No Network or No SIM Card and the user presses Send, directly add the message to the message thread, but mark it as failed (with the resend icon visible) - Then pop up the dialog as we do today This way, the message is part of the history and the user can resend whenever is convenient without losing their message. Also, eventually when we have auto resend these messages will be in the queue. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417353/+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 1447995] Re: [SDK] Re-enable swipe gestures of list items
** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags added: usability -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1447995 Title: [SDK] Re-enable swipe gestures of list items Status in Document Viewer application for Ubuntu devices: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: STEP TO REPRODUCE THIS ISSUE: 1. Open Document Viewer. The list of documents in $HOME/Documents will be shown. 2. Delete an entry in the list (N.B. not the grid), by swiping to right the corrisponding list item. WHAT HAPPENS: The list item can not be swipped WHAT SHOULD HAPPENS: The list item can be swipped to right, and a red-coloured action is shown. Currently, to delete an item we need to switch to the multi-selection mode. BLOCKERS: We need to find an equivalent UI pattern for this user case, when the grid view is used instead of the list view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1447995/+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 1200371] Re: [SDK] auto-scroll input fields when OSK visibility changes
** Changed in: ubuntu-ux Assignee: Giorgio Venturi (giorgio-venturi) => Olga Kemmet (olga-kemmet) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1200371 Title: [SDK] auto-scroll input fields when OSK visibility changes Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Currently when you select in an input field, it causes the osk to be displayed. If the field is located beneath the osk it is obscured. Currently many of the apps have to write special code to handle the osk visiblilty and handle scrolling of the field. This should be done automatically by the sdk if the app opt's in somehow. Here is a pointer to code in lp:phone-app that makes the input filed for sending text messages scroll based on osk visibility. Same is repeated in webbrowser-app: http://bazaar.launchpad.net/~phablet-team/phone-app/trunk/view/head:/src/qml/Widgets/KeyboardRectangle.qml http://bazaar.launchpad.net/~phablet-team/phone-app/trunk/view/head:/src/qml/DetailViewCommunication/CommunicationView.qml#L235 You basically anchor the KeyboardRectangle item to the bottom of your view, and then the contents you want to scroll you anchor to the top of the KeyboardRectangle. This KeyboardRectangle is a normal item that has the size of the virtual keyboard. When the keyboard is visible it has the height of the keyboard, when the keyboard is hidden, it has a height of 0 UX Solution The solution identified by Florian above is 100% correct To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1200371/+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 1290201] Re: haptic feedback / vibration audible during calls
** Tags added: usability -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1290201 Title: haptic feedback / vibration audible during calls Status in Ubuntu UX bugs: Fix Committed Status in dialer-app package in Ubuntu: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: If I press any of the call control buttons during a call, the phone vibrates. This vibration is audible to the person on the other end of the call. This means people can hear when I toggle mute/pause/speaker, which can be considered rude or at least distracting. The dialer app seems to ignore audio for a while after each button press, but the mic starts working again before the vibration stops. Could we make the vibration shorter? This was on a nexus 4 (mako), image 228 (observed on older images too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1290201/+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 1447995] Re: [SDK] Re-enable swipe gestures of list items
According to the description is seems to be an implementation issue on the app, and not SDK related...? The current toolkit list items do accommodate a delete if swiped to the right. ** Changed in: ubuntu-ux Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1447995 Title: [SDK] Re-enable swipe gestures of list items Status in Document Viewer application for Ubuntu devices: New Status in Ubuntu UX bugs: Incomplete Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: STEP TO REPRODUCE THIS ISSUE: 1. Open Document Viewer. The list of documents in $HOME/Documents will be shown. 2. Delete an entry in the list (N.B. not the grid), by swiping to right the corrisponding list item. WHAT HAPPENS: The list item can not be swipped WHAT SHOULD HAPPENS: The list item can be swipped to right, and a red-coloured action is shown. Currently, to delete an item we need to switch to the multi-selection mode. BLOCKERS: We need to find an equivalent UI pattern for this user case, when the grid view is used instead of the list view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1447995/+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 1269005] Re: [dialer-app] shows wrong contact is being dialed when two contacts have the same number
** Description changed: There are circumstances when contacts will legitimately have the same phone number. Eg, family members who have different mobile numbers but live at the same residence, business contacts who have the same number but a different extension, etc. Sometimes the dialer-app will show the wrong contact is being dialed when dialing the number. Steps to reproduce: 1. Open the contacts app 2. add a contact, 'Foo' with mobile number and shared home number 3. add a contact, 'Bar' with different mobile number, but same home number as '2' 4. open 'Foo' in the contacts app, then press the phone icon next to the shared home number, and the dialer-app opens At this point, 'Foo' should be shown as being dialed, but instead, 'Bar' is shown as being dialed. + + -UX comment--- + + I am not sure if this is a UX issue, but rather a technical/implementation issue. + At all times users should be presented with the correct contact they dialed, regardless if the number is matching with an other contact. ** Changed in: ubuntu-ux Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1269005 Title: [dialer-app] shows wrong contact is being dialed when two contacts have the same number Status in Ubuntu UX bugs: Fix Committed Status in dialer-app package in Ubuntu: Confirmed Bug description: There are circumstances when contacts will legitimately have the same phone number. Eg, family members who have different mobile numbers but live at the same residence, business contacts who have the same number but a different extension, etc. Sometimes the dialer-app will show the wrong contact is being dialed when dialing the number. Steps to reproduce: 1. Open the contacts app 2. add a contact, 'Foo' with mobile number and shared home number 3. add a contact, 'Bar' with different mobile number, but same home number as '2' 4. open 'Foo' in the contacts app, then press the phone icon next to the shared home number, and the dialer-app opens At this point, 'Foo' should be shown as being dialed, but instead, 'Bar' is shown as being dialed. -UX comment--- I am not sure if this is a UX issue, but rather a technical/implementation issue. At all times users should be presented with the correct contact they dialed, regardless if the number is matching with an other contact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1269005/+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 1442851] Re: [browser] Setting labels ellipsized on phone screen in portrait orientation
** Summary changed: - Setting labels ellipsized on phone screen in portrait orientation + [browser] Setting labels ellipsized on phone screen in portrait orientation ** Changed in: ubuntu-ux Assignee: Olga Kemmet (olga-kemmet) => (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) => James Mulholland (jamesjosephmulholland) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1442851 Title: [browser] Setting labels ellipsized on phone screen in portrait orientation Status in Ubuntu UX bugs: Triaged Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: Confirmed Status in webbrowser-app source package in Vivid: New Bug description: As shown on the attached screenshot, the rows #2 and #3 of the settings screen have a text that doesn't fit on the screen. The only way to see what these options mean is to switch the phone to landscape orientation. A different UI component should be used for these two options, one that allows the user to see the full text of what he's enabling or disabling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1442851/+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 1328915] Re: [address-book]Go back to contact app when SMS is created from Contact
** Changed in: ubuntu-ux Status: Triaged => Fix Committed ** Description changed: Mako build 77 TEST CASE: 1. Open the addressbook app 2. Tap a contact with a mobile phone to open the details page 3. Tap the 'message' icon at the end of the 'phone' line - > Verify that the compose window opens + > Verify that the compose window opens 4. Hide OSK,and reveal the menu from the bottom edge 5. Press the back button - > Verify that the addressbook app is active + > Verify that the addressbook app is active ACTUAL RESULT Messaging app is active and on the list of messages EXPECTED RESULT User goes back to the address book app. + + -UX comment- + + Please follow the EXPECTED RESULT recommendation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1328915 Title: [address-book]Go back to contact app when SMS is created from Contact Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: New Status in messaging-app package in Ubuntu: Confirmed Status in address-book-app source package in Vivid: New Status in messaging-app source package in Vivid: New Bug description: Mako build 77 TEST CASE: 1. Open the addressbook app 2. Tap a contact with a mobile phone to open the details page 3. Tap the 'message' icon at the end of the 'phone' line > Verify that the compose window opens 4. Hide OSK,and reveal the menu from the bottom edge 5. Press the back button > Verify that the addressbook app is active ACTUAL RESULT Messaging app is active and on the list of messages EXPECTED RESULT User goes back to the address book app. -UX comment- Please follow the EXPECTED RESULT recommendation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1328915/+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 1242089] Re: [sdk] Swipe delete of a list item does not display "Delete" text or icon if confirmRemoval option is not set
** Changed in: ubuntu-ux Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1242089 Title: [sdk] Swipe delete of a list item does not display "Delete" text or icon if confirmRemoval option is not set Status in Ubuntu UX bugs: Won't Fix Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: List items provide the properties confirmRemoval and removable to allow deleting a list item by swiping either to the left or right. If you have a list item which is removable by setting the property removable: true, on swiping to the left or right, no text is displayed. This leads to the user not being aware which action is performed on swiping. However if the confirmRemoval property is set true, then the delete icon and text is shown. I think that the delete icon and text should be shown if either property removable or confirmRemoval is set to true. This can be seen in the UITK gallery. Open gallery, navigate to List Items -> Removable. When you swipe to delete a list item, no text or icon is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1242089/+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 1371202] Re: [SDK] Double tap should display the contextual menu
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1371202 Title: [SDK] Double tap should display the contextual menu Status in Ubuntu UX bugs: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: Current behaviour - Focus text field with text - Double tap on a word - Contextual menu does not appear Desired behaviour - Double tap should bring up the contextual menu, same as long press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1371202/+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 1439669] Re: [dialer-app] Can not record phone call
** Changed in: ubuntu-ux Status: Invalid => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1439669 Title: [dialer-app] Can not record phone call Status in Ubuntu UX bugs: Opinion Status in dialer-app package in Ubuntu: New Bug description: When calling companies that you are a customer of, it is sometimes helpful to record the phone calls, so they don's scam you. Right now this feature seems not implemented in ubuntu touch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1439669/+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 1456626] Re: [Dialer] ubuntu touch bad dialer/contacts integration
** Tags added: usability -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1456626 Title: [Dialer] ubuntu touch bad dialer/contacts integration Status in Ubuntu UX bugs: Opinion Status in dialer-app package in Ubuntu: New Bug description: I' using my ubuntu phone as a telephone mostly! I find it somewhat annoying, how much steps have to be taken to select a contact from contacts. These are the steps: 1) Hit Contacts 2) Hit the magnifying glass 3) Enter filter string 4) Select contact 5) Select number 6) Hit the green Button. This is 6 Buttons - as much as a telephone number has (in Austria) I'd like to have a filter field in the dialer app, with contacts popping up as I enter the filter string. Contacts should be shown in a tree view with the numbers visible. If I hit a number, it will be dialed immediately. A bit the same, when using the 'recent' view of the dialer or favourites. If you select a call, it won't be dialed immediately. The number is transferred to the dialer field and you have to hit the green button. PS: I'd like to contrubute to the touch project. I'm a software developer (mostly doing C/C++/Qt). If someone would guide me, I'd do some work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456626/+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 1456626] Re: [Dialer] ubuntu touch bad dialer/contacts integration
Thanks for filing this bug. Unfortunately this is more of a feature request/usability issue than a bug. As much as I do understand the reported problem here, the behaviour is not "broken". Design will have to address this issue at a later stage in the project. ** Changed in: ubuntu-ux Importance: High => Wishlist ** Changed in: ubuntu-ux Status: Triaged => Opinion ** Changed in: ubuntu-ux Importance: Wishlist => Low ** Changed in: ubuntu-ux Importance: Low => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1456626 Title: [Dialer] ubuntu touch bad dialer/contacts integration Status in Ubuntu UX bugs: Opinion Status in dialer-app package in Ubuntu: New Bug description: I' using my ubuntu phone as a telephone mostly! I find it somewhat annoying, how much steps have to be taken to select a contact from contacts. These are the steps: 1) Hit Contacts 2) Hit the magnifying glass 3) Enter filter string 4) Select contact 5) Select number 6) Hit the green Button. This is 6 Buttons - as much as a telephone number has (in Austria) I'd like to have a filter field in the dialer app, with contacts popping up as I enter the filter string. Contacts should be shown in a tree view with the numbers visible. If I hit a number, it will be dialed immediately. A bit the same, when using the 'recent' view of the dialer or favourites. If you select a call, it won't be dialed immediately. The number is transferred to the dialer field and you have to hit the green button. PS: I'd like to contrubute to the touch project. I'm a software developer (mostly doing C/C++/Qt). If someone would guide me, I'd do some work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456626/+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 1456610] Re: [messaging app] Expected to be able to select picture in a full screen preview mode before sending it
This is addressed as part of the media framework design. Once it is implemented, it should resolve issues in the apps mentioned above. ** Changed in: ubuntu-ux Assignee: Olga Kemmet (olga-kemmet) => (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) => James Mulholland (jamesjosephmulholland) ** Tags added: uability ** Tags removed: uability ** Tags added: usability ** Changed in: ubuntu-ux Importance: High => Medium ** Summary changed: - [messaging app] Expected to be able to select picture in a full screen preview mode before sending it + [media-framework] Expected to be able to select picture in a full screen preview mode before sending it ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1456610 Title: [media-framework] Expected to be able to select picture in a full screen preview mode before sending it Status in Ubuntu UX bugs: Triaged Status in unity package in Ubuntu: New Bug description: When testers tried to send picture via Gallery (event view) or Telegram or Messaging app, it was difficult for them to select the one they wanted to sent (especially when the pictures were similar). This is because the pictures were not displayed in full sizes, and there was no preview mode for them to check before committing to send. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456610/+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 1197058] Re: [SDK ListItems] should allow controls on the left
** Changed in: ubuntu-ux
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1197058
Title:
[SDK ListItems] should allow controls on the left
Status in Ubuntu UX bugs:
Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Bug description:
Looking to this system settings design:
https://wiki.ubuntu.com/Sound?action=AttachFile&do=get&target=phone-settings-sound.png
The list have list entries with that format
| [check] |
I've used a custom item for those doing that:
'ListItem.Base {
property string textEntry: "";
property bool checkStatus: false;
Row {
anchors.top: parent.top
anchors.bottom: parent.bottom
spacing: units.gu(2)
CheckBox {
anchors.verticalCenter: parent.verticalCenter
checked: checkStatus
}
Label {
anchors.verticalCenter: parent.verticalCenter
text: textEntry
}
}
}"
But:
- that's not standard
- clicking on the label doesn't tweak the checkbox as it does for other
controls (I can hack that easily if needed though)
- the UI might not be consistent with what is used in other place
This bug might also be a place to discuss if those items are fine to
use or non coherent with our use of the toolkit in other places...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1197058/+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 1276797] Re: [sdk] Add keyboard navigation support to widgets
** Changed in: ubuntu-ux Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1276797 Title: [sdk] Add keyboard navigation support to widgets Status in Ubuntu UX bugs: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: This concerns TAB/Shift+TAB navigation between components. We need UX on how/when to highlight the focus component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1276797/+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 1396615] Re: [phone-app] The word "Keypad" still shows in header
It is still an issue and it would be great to change it. We normally have the name of the app in the header. Putting "Keypad" there is a weird thing to do and feels misleading. ** Changed in: ubuntu-ux Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1396615 Title: [phone-app] The word "Keypad" still shows in header Status in Ubuntu UX bugs: Fix Committed Status in dialer-app package in Ubuntu: New Bug description: Krillin, build r169 Steps to reproduce: 1. make sure you have to sim cards inserted 2. launch the phone app for the first time 2. dismiss the popup dialog by tapping LATER asking you to set up a default SIM 3. The header should now say "Keypad" Expected behaviour: The header should state PHONE instead of KEYPAD in case no default SIM was selected yet. This issue was partially resolved in this bug: https://bugs.launchpad.net/ubuntu-ux/+bug/1353959 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1396615/+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 1450213] Re: [SDK] cursor handle should not be visible if field is empty
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1450213 Title: [SDK] cursor handle should not be visible if field is empty Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu UX bugs: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: Fix Released Bug description: On arale ui-tookit version 1.2.1485+15.04.20150429-0ubuntu1 The big blue cursor handle should not be visible if the text field is empty, as dragging does nothing. It should only be displayed if the field has text (or spaces) in it where dragging would make sense. Steps to reproduce: 1) reboot phone 2) launch messaging-app 3) swipe up from bottom to create new messaage Expected results: - cursor should be blinking in field - no text handle should be visible Actual results: - cursor is blinking in field - big blue cursor handle is visible NOTE, you can repeat this same thing by pressing the Search icon in the dash. The blue cursor appears even when nothing in paste buffer. SOLUTION: Don't show handler when tapping on an empty textfield. Long press textfield in order to access copy/paste To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450213/+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 1455470] Re: The NOTE field sould be synced and displayed
** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Importance: Undecided => Medium ** Changed in: ubuntu-ux Status: New => Confirmed ** Summary changed: - The NOTE field sould be synced and displayed + [address-book-app] The NOTE field sould be synced and displayed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1455470 Title: [address-book-app] The NOTE field sould be synced and displayed Status in Ubuntu UX bugs: Confirmed Status in address-book-app package in Ubuntu: New Bug description: On my bq, r22, the contacts does not show the NOTE field, nor it allows to create a contact and to add a such field. This field is useful to store contact information like opening hours, GPS coordinates... It should be added in the list of fields managed (and synchronized) by the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1455470/+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 1443861] Re: [Phone call] When accepting a call, call panel takes at least 10s to appear
*** This bug is a duplicate of bug 1454790 *** https://bugs.launchpad.net/bugs/1454790 ** This bug is no longer a duplicate of bug 1440889 Dialer app launches to slow ** This bug has been marked a duplicate of bug 1454790 [Dialer] Dialer app launches too slow -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1443861 Title: [Phone call] When accepting a call, call panel takes at least 10s to appear Status in dialer-app package in Ubuntu: New Bug description: I have a BQ phone with the devel-proposed channel. When someone calls you and you accept the call, there is 10s where nothing happens. Call panel is loading and no sounds comes. Should be great to reduce this time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1443861/+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 1454790] Re: [Dialer] Dialer app launches too slow
I marked the other bug as a duplicate for the reasons that more projects are assigned to this one. ** No longer affects: ubuntu-ux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1454790 Title: [Dialer] Dialer app launches too slow Status in dialer-app package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: In my opinion the dialer app on the Ubuntu Phone is much too slow. On my BQ Aquarius E4.5 (Ubuntu 14.10 (r22)) it takes 3 seconds to launch the dialer app. This is a phone! Since I was born there was no phone that had such a delay to get ready. My previouse phone a Nokia 3720c launches the "dialer app" in less than a second. Also Android phones are much faster. Wouldn't it be possible to keep the dialer app in the RAM to force an instant launch? (Also the messaging app should get that boost but it's less important than the dialer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1454790/+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 1440889] Re: Dialer app launches to slow
*** This bug is a duplicate of bug 1454790 *** https://bugs.launchpad.net/bugs/1454790 ** This bug has been marked a duplicate of bug 1454790 [Dialer] Dialer app launches too slow -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1440889 Title: Dialer app launches to slow Status in dialer-app package in Ubuntu: Confirmed Bug description: The dialer app on the BQ Aquarius 4.5 takes too long to launch. It takes 2-5 seconds to open the dialer. After that more time is required for dialing. I thing for a device that should at first still be a phone, this is much too long. Here a solution is absolutly neccessary. Could keeping the dialer app in the RAM be an option? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1440889/+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 1257307] Re: [sdk] The pagestacks should allow to pop more than one page at the time
** Changed in: ubuntu-ux Status: Triaged => Fix Committed ** Description changed: In some cases you have several level of pages stacked, it would be useful to let be able to pop more than once a the time e.g you have a start page, push a list, push a confirmation/option dialog, then you want to go back to the start screen ... right now you have to pop one level and then have some logic to pop down another level when getting there. It would be nice to be able to pop(n), maybe with 0=bottom of the stack + + ---UX comment- + + The solution as per comment #3 seems plausible. I do agree with comment + #4 + #4. A sudden change in the general logic and page stack navigation + is going to cause confusion to the user. The described use case + (example?) seems to be an edge case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1257307 Title: [sdk] The pagestacks should allow to pop more than one page at the time Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: In some cases you have several level of pages stacked, it would be useful to let be able to pop more than once a the time e.g you have a start page, push a list, push a confirmation/option dialog, then you want to go back to the start screen ... right now you have to pop one level and then have some logic to pop down another level when getting there. It would be nice to be able to pop(n), maybe with 0=bottom of the stack ---UX comment- The solution as per comment #3 seems plausible. I do agree with comment #4 + #4. A sudden change in the general logic and page stack navigation is going to cause confusion to the user. The described use case (example?) seems to be an edge case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1257307/+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 1452676] Re: [SDK] Right-click menu instead of leading/ trailing actions
** Changed in: ubuntu-ux Status: Triaged => In Progress ** Description changed: On desktops/ laptops the leading and trailing actions of list items should be available as context menus. In practise we probably want to enable the menu if a mouse is being used and only enable the actions if s touchscreen is available. + + ---UX comment- + Solution was discussed and agreed during UITK/SDK sprint in London, 1st week of June 2015. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1452676 Title: [SDK] Right-click menu instead of leading/ trailing actions Status in Ubuntu UX bugs: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: On desktops/ laptops the leading and trailing actions of list items should be available as context menus. In practise we probably want to enable the menu if a mouse is being used and only enable the actions if s touchscreen is available. ---UX comment- Solution was discussed and agreed during UITK/SDK sprint in London, 1st week of June 2015. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1452676/+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 1375844] Re: [SDK] Insert/Select text mode should not bar users from using other elements on screen
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1375844 Title: [SDK] Insert/Select text mode should not bar users from using other elements on screen Status in Ubuntu UX bugs: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: REPRO 1. Tap on a text field 2. Long press on a word 3. Contextual Pop-over will appear 4. Tap on an action or button outside the text field 5. Popover disappears 6. You need to tap again to activate the function DESIRED BEHAVIOUR 5. The action/button is working (user does not need to tap twice) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1375844/+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 1450988] Re: Duplicate metrics for no calls made today
** Changed in: ubuntu-ux
Assignee: Olga Kemmet (olga-kemmet) => (unassigned)
** Changed in: ubuntu-ux
Assignee: (unassigned) => Andreea Pirvu (andreea-pirvu)
** Summary changed:
- Duplicate metrics for no calls made today
+ [Greeter] Duplicate metrics for no calls made today
--
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/1450988
Title:
[Greeter] Duplicate metrics for no calls made today
Status in Ubuntu UX bugs:
Triaged
Status in telephony-service package in Ubuntu:
New
Bug description:
I noticed that when tapping on the welcome screen, the metrics for "No
calls made today"" were shown twice. That is:
1. Tap on the circle until you see "No calls made today""
2. Double tap again
Actual:
- The same "No calls made today"" text is shown, but with a different diagram
Expected:
- "No time spent on calls today" (or similar) is shown
I think it just needs a one-liner change on this code in
indicator/metrics.cpp [1]. I would suggest "No time spent on calls
today" on the second instance.
This will also need a .pot file update to expose the new string to
translators.
mMetrics[OutgoingCalls] =
mMetricManager->add(MetricParameters(DIALER_OUTGOING_STATISTICS_ID).formatString(GettextMarkExtraction("%1
calls made today"))
.emptyDataString(GettextMarkExtraction("No calls made
today")).textDomain(APP_ID).minimum(0.0));
mMetrics[CallDurations] =
mMetricManager->add(MetricParameters(DIALER_CALL_DURATION_STATISTICS_ID).formatString(GettextMarkExtraction("Spent
%1 minutes in calls today"))
.emptyDataString(GettextMarkExtraction("No calls made
today")).textDomain(APP_ID).minimum(0.0));
[1] http://bazaar.launchpad.net/~phablet-team/telephony-
service/trunk/view/head:/indicator/metrics.cpp#L48
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1450988/+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 1395056] Re: [Dialler] Can't see indiviual log events in the dialer log
Not sure what the bug is from the description above. This info is available as per UX comment in the bug description. Hence marking as INVALID. ** Changed in: ubuntu-ux Status: Triaged => Invalid ** Description changed: When looking at logged incomming and outgoing calls to the same recipient and day, you only see the count, not when and how long (or missed) the call was. + + UX comment + + Additional information for a contact in the recent view can be + reviewed/obtained by swiping the list item towards the left + tapping + the INFO icon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1395056 Title: [Dialler] Can't see indiviual log events in the dialer log Status in Ubuntu UX bugs: Invalid Status in dialer-app package in Ubuntu: New Bug description: When looking at logged incomming and outgoing calls to the same recipient and day, you only see the count, not when and how long (or missed) the call was. UX comment Additional information for a contact in the recent view can be reviewed/obtained by swiping the list item towards the left + tapping the INFO icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1395056/+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 1456782] Re: [Dialer and Messaging] should be able to edit a contact without switching to address book
** Changed in: ubuntu-ux Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1456782 Title: [Dialer and Messaging] should be able to edit a contact without switching to address book Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: Confirmed Status in dialer-app source package in Vivid: Confirmed Status in messaging-app source package in Vivid: Confirmed Bug description: per design, users of dialer and messaging-app should be able to open a contact directly from within those apps and edit it. Currently it launches address book app and then the user's context is switched. Desired behavior: Dialer app: - from dialer screen click the contacts icon on header - contact list should be shown in the dialer app - click on contact to open it - should be able to edit contact from that screen and interact without switching to address book app Messaging app: - create new message - click contacts icon on header - contact list should be shown in the messaaging app - can edit or interact without switching to address book app To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1456782/+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 1447995] Re: [Document-Viewer] Re-enable swipe gestures of list items
** Summary changed: - [SDK] Re-enable swipe gestures of list items + [Document-Viewer] Re-enable swipe gestures of list items -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1447995 Title: [Document-Viewer] Re-enable swipe gestures of list items Status in Document Viewer application for Ubuntu devices: New Status in Ubuntu UX bugs: Incomplete Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: STEP TO REPRODUCE THIS ISSUE: 1. Open Document Viewer. The list of documents in $HOME/Documents will be shown. 2. Delete an entry in the list (N.B. not the grid), by swiping to right the corrisponding list item. WHAT HAPPENS: The list item can not be swipped WHAT SHOULD HAPPENS: The list item can be swipped to right, and a red-coloured action is shown. Currently, to delete an item we need to switch to the multi-selection mode. BLOCKERS: We need to find an equivalent UI pattern for this user case, when the grid view is used instead of the list view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1447995/+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 1440065] Re: [Address book] Contacts with accent on first letter are not ordered properly
** Tags added: usability ** Description changed: My contact list is a bit strange when it comes to the "E" letter. I have six different categories, three "E"s and three "É"s. Also, when I search for a contact, "E" and "É" are not the same, which is inconvenient. My contacts come from two Google accounts but it does not seem to be the problem, since contacts from both accounts may appear under one "E" occurrence. This is on the retail bq phone, r20, French locale. + + UX comment-- + + My recommendation is not to create new sections for the accent letters but accommodate them under their parent letter. This would mean: + - "É," is in the "E" section, "Ç" is under the "C", "Å" is under the "A" section and so on. ** Changed in: ubuntu-ux Status: Triaged => Fix Committed ** Changed in: ubuntu-ux Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1440065 Title: [Address book] Contacts with accent on first letter are not ordered properly Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: New Bug description: My contact list is a bit strange when it comes to the "E" letter. I have six different categories, three "E"s and three "É"s. Also, when I search for a contact, "E" and "É" are not the same, which is inconvenient. My contacts come from two Google accounts but it does not seem to be the problem, since contacts from both accounts may appear under one "E" occurrence. This is on the retail bq phone, r20, French locale. UX comment-- My recommendation is not to create new sections for the accent letters but accommodate them under their parent letter. This would mean: - "É," is in the "E" section, "Ç" is under the "C", "Å" is under the "A" section and so on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1440065/+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 1447995] Re: [Document-Viewer] Re-enable swipe gestures of list items
Hi Stefano Thank you for the detailed explanation, I understand the issue now better. Indeed, we do not have any pattern for this particular use case at the moment. I would recommend you to do something similar as per your Android example: - A: You include on the tile on the top right an overflow menu where you could put any additional actions or - B: you include a text link saying "more..." in the bottom right of the tile which triggers a popover. The popover can be a list view with any additional actions for that tile. I included a sketched wireframe to illustrate what I mean. Hope it helps. ** Attachment added: "IMG_2015-06-12 15:05:17.jpg" https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1447995/+attachment/4413942/+files/IMG_2015-06-12%2015%3A05%3A17.jpg ** Changed in: ubuntu-ux Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1447995 Title: [Document-Viewer] Re-enable swipe gestures of list items Status in Document Viewer application for Ubuntu devices: New Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: STEP TO REPRODUCE THIS ISSUE: 1. Open Document Viewer. The list of documents in $HOME/Documents will be shown. 2. Delete an entry in the list (N.B. not the grid), by swiping to right the corrisponding list item. WHAT HAPPENS: The list item can not be swipped WHAT SHOULD HAPPENS: The list item can be swipped to right, and a red-coloured action is shown. Currently, to delete an item we need to switch to the multi-selection mode. BLOCKERS: We need to find an equivalent UI pattern for this user case, when the grid view is used instead of the list view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1447995/+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 1338970] Re: No voicemail number defined ==> No feedback when attempting to dial
Do you guys need UX for that? ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Importance: Undecided => Low ** Changed in: ubuntu-ux Status: New => Triaged ** Summary changed: - No voicemail number defined ==> No feedback when attempting to dial + [dialer] No voicemail number defined ==> No feedback when attempting to dial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1338970 Title: [dialer] No voicemail number defined ==> No feedback when attempting to dial Status in Ubuntu UX bugs: Triaged Status in dialer-app package in Ubuntu: Confirmed Bug description: I have some SIM cards with no voicemail number predefined (although the voicemail service actually works with the subscription). Testing with a SIM card that has a pre-defined voicemail number (Saunalahti, Finland): - Open dialer - Long press number 1 (with the "tape reels" icon) Actual result: Voicemail is dialled correctly Testing with a SIM card that does *not* have a pre-defined voicemail number (Sonera, Finland): - Open dialer - Long press number 1 (with the "tape reels" icon) Actual result: Nothing happens Expected result: - Either something like "No voicemail number defined, enter now? " and a corresponding settings page, - or maybe show the voicemail icon only conditionally, if property org.ofono.MessageWaiting.VoicemailMailboxNumber is not empty Tested on mako HW, image 118. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1338970/+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 1320788] Re: USSD code result shows useless Cancel button
@Tiago: Can you use a dialog for this instance? ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Importance: Undecided => Medium ** Changed in: ubuntu-ux Status: New => Triaged ** Summary changed: - USSD code result shows useless Cancel button + [dialer] USSD code result shows useless Cancel button -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1320788 Title: [dialer] USSD code result shows useless Cancel button Status in Ubuntu UX bugs: Triaged Status in dialer-app package in Ubuntu: Confirmed Bug description: Hi there, This is on T-Mobile with devel build #28. When running USSD code #225# to get the account balance, I get a nice popup with the resulting text from T-Mobile, but it has both Ok and Cancel buttons which do the same thing. The Cancel button should be removed. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1320788/+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 1458914] Re: [messaging app] should be able to send direct message to group member from menu
** Description changed: Steps to reproduce: - receive a group message (MMS chat needs to be enabled) - open the message - on the header, click on the Contacts avatar - a list of recipients is displayed with the recipients of the message - click on one of the recipients in the list Expected Results - should open a new message to the selected recipient Actual results: - click on the recipient causes no action + + --UX comment--- + + As per new design (please refer to the latest UX spec) the GROUP icon is + replaced with a INFO icon where you can review the list with group + members. Tapping on a list item from this view should allow user to + start a new conversation with the selected contact. ** Changed in: ubuntu-ux Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1458914 Title: [messaging app] should be able to send direct message to group member from menu Status in Ubuntu UX bugs: Fix Committed Status in messaging-app package in Ubuntu: New Bug description: Steps to reproduce: - receive a group message (MMS chat needs to be enabled) - open the message - on the header, click on the Contacts avatar - a list of recipients is displayed with the recipients of the message - click on one of the recipients in the list Expected Results - should open a new message to the selected recipient Actual results: - click on the recipient causes no action --UX comment--- As per new design (please refer to the latest UX spec) the GROUP icon is replaced with a INFO icon where you can review the list with group members. Tapping on a list item from this view should allow user to start a new conversation with the selected contact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1458914/+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 1415076] Re: {Dialler] Can't send a text message to a number typed in the dialer
This is not a bug but a feature request. The dialer doesn't need to
support messaging on the main page. Marking as OPINION.
** Changed in: ubuntu-ux
Status: Triaged => Opinion
** Changed in: ubuntu-ux
Importance: Medium => Undecided
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1415076
Title:
{Dialler] Can't send a text message to a number typed in the dialer
Status in Ubuntu UX bugs:
Opinion
Status in dialer-app package in Ubuntu:
Confirmed
Bug description:
Steps:
* type a number in the dialer
Expected
* I can use the number to send a message to it
Current
* no way to "transfer" the number to the messaging app
ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: dialer-app 0.1+15.04.20150122~rtm-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Tue Jan 27 15:51:26 2015
InstallationDate: Installed on 2015-01-27 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf
(20150127-030205)
SourcePackage: dialer-app
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1415076/+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 1352817] Re: [messaging-app] group message is missing actions for recipients
*** This bug is a duplicate of bug 1458914 *** https://bugs.launchpad.net/bugs/1458914 ** This bug has been marked a duplicate of bug 1458914 [messaging app] should be able to send direct message to group member from menu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1352817 Title: [messaging-app] group message is missing actions for recipients Status in Ubuntu UX bugs: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: To reproduce: 1. Open messaging app 2. Go to tan existing group threat or create a new one 3. Tap on the group icon in the top right corner of the header 4. A drop down menu shows all recipients in the message -> missing: actions for the recipients in the drop down menu --- Desired solution: The drop down should have following actions a) for existing contacts: CALL & VIEW PROFILE (in address book) b) for new contacts (number): CALL & CREATE NEW CONTACT (address book) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1352817/+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 1291455] Re: [greeter] Screen and input should be disabled with proximity sensor when on greeter
** Changed in: ubuntu-ux Assignee: Olga Kemmet (olga-kemmet) => Andreea Pirvu (andreea-pirvu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1291455 Title: [greeter] Screen and input should be disabled with proximity sensor when on greeter Status in the base for Ubuntu mobile products: Incomplete Status in Ubuntu UX bugs: Triaged Status in Unity System Compositor: New Status in powerd package in Ubuntu: Incomplete Status in telepathy-ofono package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Incomplete Bug description: Steps to reproduce: * suspend your device * cover the proximity sensor (top left on mako) * call the phone Expecte result: * screen does not light up until you uncover the proximity sensor Current result: * screen lights up and you can answer the call This results in butt/pocket calls... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.84+14.04.20140306-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Wed Mar 12 13:14:37 2014 InstallationDate: Installed on 2014-03-12 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140312) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1291455/+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 1257307] Re: [sdk] The pagestacks should allow to pop more than one page at the time
** Changed in: ubuntu-ux Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1257307 Title: [sdk] The pagestacks should allow to pop more than one page at the time Status in Ubuntu UX: Won't Fix Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: In some cases you have several level of pages stacked, it would be useful to let be able to pop more than once a the time e.g you have a start page, push a list, push a confirmation/option dialog, then you want to go back to the start screen ... right now you have to pop one level and then have some logic to pop down another level when getting there. It would be nice to be able to pop(n), maybe with 0=bottom of the stack ---UX comment- The solution as per comment #3 seems plausible. I do agree with comment #4 + #4. A sudden change in the general logic and page stack navigation is going to cause confusion to the user. The described use case (example?) seems to be an edge case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1257307/+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 1497095] Re: Two identical grey window buttons for minimize and maximize
** Changed in: ubuntu-ux Assignee: (unassigned) => Jamie Young (jamiedawsonyoung) ** Changed in: ubuntu-ux Status: New => Triaged ** Summary changed: - Two identical grey window buttons for minimize and maximize + [sdk] [buttons] Two identical grey window buttons for minimize and maximize -- 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/1497095 Title: [sdk] [buttons] Two identical grey window buttons for minimize and maximize Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: Two identical grey window buttons for minimize and maximize. Which is which? Click them and find out :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1497095/+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 1497155] Re: apostrophe in scopes bq aquaris e4.5 ubuntu touch
I don't think this is a dialer app issue. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New -- 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/1497155 Title: apostrophe in scopes bq aquaris e4.5 ubuntu touch Status in dialer-app: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: I noticed that the apostrophe is not displayed in the notice scope sometimes. it is translated with "&8226;" or same code. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1497155/+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 1474940] Re: phone call ends after 2 hours
** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New ** Summary changed: - phone call ends after 2 hours + [dialer] phone call ends after 2 hours ** Changed in: ubuntu-ux Importance: Undecided => Medium ** Description changed: My calls will be finished after exactly 2:00:00 hours. Device: nexus 4 mako System: All up to date (stable) + + - UX comment -- + + The obvious solution is that a call can go on as long as the user wants + it, considering sufficient funds in case of a top-up SIM, constant + reception & enough battery life. ** Changed in: ubuntu-ux Status: New => Fix Committed -- 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/1474940 Title: [dialer] phone call ends after 2 hours Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: New Status in telephony-service package in Ubuntu: New Bug description: My calls will be finished after exactly 2:00:00 hours. Device: nexus 4 mako System: All up to date (stable) - UX comment -- The obvious solution is that a call can go on as long as the user wants it, considering sufficient funds in case of a top-up SIM, constant reception & enough battery life. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1474940/+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 1408159] Re: [messaging] Too easy to delete whole conversation history with a contact
@saviq: The way phone calls and messages are clustered is different. Whilst call history clusters calls per contact per day the messaging only does it per contact so that you wont create duplicates in the inbox. You have a chronological conversation history in the messaging thread. The recent calls view can have e.g. on a Monday a clustered entry with 1 number if you received a call and made a call to this number. However if you call that person on a Tuesday it becomes a new data entry. The most important thing users want to know in recent calls is WHEN certain calls were made and who to. If you tap on a list item in recent calls, you will be always calling that entry. Whilst for messaging you are drilling down into a conversation. In messaging apps users mostly want to know WHO they chatted with, content of the last message not necessarily when. Also showing multiple entries creates unneeded duplicates which bring other issues. E.g. multiple saved threads to a person will have either be kept up to date with the last message sent/received. Otherwise a user might tap on a thread with a person and will only see the last message from that day. This can lead to confusion. Finally, as a security measure we could introduce a dialog asking users if they really want to delete the whole conversation. Maybe that would prevent accidental removal of the whole thread. ** Changed in: ubuntu-ux Status: Won't Fix => Fix Committed ** Description changed: Steps: * open messaging app * drag one of the items on the list to the right * tap on the trash icon Expected: * only today's messages are removed or at least there's a confirmation dialog Current: * whole history of messaging with a contact is removed The fact that conversations are separated by days suggests as if a single item was a conversation within that day. But in fact they're complete conversations just ordered by date (which is actually different than the phone log, which *is* split by date, and removing an item there only affects a day's events). I wonder if it would be better to indeed show multiple entries for a single contact, in each day a message was sent either way, this being a shortcut to a certain message when opening. It feels like this would be better in the long run (imagine many years of messaging history). That might deserve another bug though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: messaging-app 0.1+15.04.20141210-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Wed Jan 7 00:06:35 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: messaging-app UpgradeStatus: No upgrade log present (probably fresh install) --- UX comment & resolution - There is an active action of + There is an active action of 1. dragging the list item in the conversation overview to the right 2. tapping the delete icon This means that there is already a two step interaction in place before - the message is deleted, hence no additional confirmation dialog is - needed. This would place an unnecessary 3rd step in place. - - It wouldn't make much sense to delete just today's messages, because you - are removing the whole conversation. The behaviour of removing the whole - message with a contact is intended. + the message is deleted. As an additionally security measure we could + introduce an additional confirmation dialog. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1408159 Title: [messaging] Too easy to delete whole conversation history with a contact Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: New Bug description: Steps: * open messaging app * drag one of the items on the list to the right * tap on the trash icon Expected: * only today's messages are removed or at least there's a confirmation dialog Current: * whole history of messaging with a contact is removed The fact that conversations are separated by days suggests as if a single item was a conversation within that day. But in fact they're complete conversations just ordered by date (which is actually different than the phone log, which *is* split by date, and removing an item there only affects a day's events). I wonder if it would be better to indeed show multiple entries for a single contact, in each day a message was sent either way, this being a shortcut to a certain message when opening. It feels like this would be better in the long run (imagine many years of messaging history). That might deserve another bug though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: messaging-app 0.1+15.04.20141210-0ubuntu1
[Touch-packages] [Bug 1487539] Re: Small light grey text difficult to read on of white background
** Also affects: ubuntu-ux Importance: Undecided Status: New -- 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/1487539 Title: [SDK] Small light grey text difficult to read on of white background Status in Ubuntu UX: Triaged Bug description: I am using the Meizu MX4 with the latest updates(15.04 r3), I also have the BQ E4.5 that has the same issue. Light grey text is very difficult to read even on a white background. In some apps such as the Dekko for instance you cant read the text in the emails, such as bug reports sent from Ubuntu. In settings > accounts , you cant read the email address below each company such as Ubuntu one or Google. As Ubuntu Touch is content based I would have though text contrast would be high on the list but this is not the case. Please see Dekko example attached (taken from MX4) Also, If in the future users wish to change the white background to a picture (or another colour) this will be a big problem . I have manually changed the scope backgrounds to a light blue, lake / mountain picture and the phone looks much more interesting, but text is very dim for general reading. To be honest I think the end user should have some control over text size, colour, contrast, font etc as they do in the Unity desktop software. Please can you consider my request. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1487539/+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 1489395] Re: [scopes] Single star means "this number is the rating", but looks like app has a low rating
** Summary changed: - Single star means "this number is the rating", but looks like app has a low rating + [scopes] Single star means "this number is the rating", but looks like app has a low rating -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1489395 Title: [scopes] Single star means "this number is the rating", but looks like app has a low rating Status in Ubuntu UX: Triaged Status in unity-scope-click package in Ubuntu: Triaged Bug description: App ratings are displayed as ☆ 4.5. Every time I glance at an app's rating my first thought is that it's been rated low, because it's only got one star. Then I read the number and realise that the app is rated highly and that star means "here is the rating", not "it's got a one- star rating". As far as I can tell everywhere a star rating is displayed it's on a line on its own, so there ought to be room to write ☆ 4.5 (nine characters) -- there is room to fit the developer name horizontally, or the app name -- and this would avoid the confusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1489395/+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 1498609] Re: No notification about incomming calls on bluetooth headset
@themeles Does the device detect the headset and is it somehow surfaced in the device UI? Do you have any screenshots what is happening on the UI during that instance? ** Also affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Also affects: dialer-app Importance: Undecided Status: New ** Also affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1498609 Title: No notification about incomming calls on bluetooth headset Status in dialer-app: New Status in Ubuntu UX: Incomplete Status in indicator-bluetooth package in Ubuntu: New Status in indicator-messages package in Ubuntu: New Bug description: When I get incomming calls there is no notice on my bluetooth headset, about these. This happened when the phone was silenced and also when it was not. When the phone was not silenced, it at least did a little crack. There should be a notification in both cases. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1498609/+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 1415480] Re: [indicators]/OSD provide no visual clue that they modify bluetooth device volumes
** Also affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** No longer affects: indicator-messages (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1415480 Title: [indicators]/OSD provide no visual clue that they modify bluetooth device volumes Status in Canonical System Image: Confirmed Status in Ubuntu UX: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Connect a bluetooth audio device (headset, speakers) to the ubuntu phone. Play music/enter into a call, so that you have active audio to the device. Adjust the volume, using the UI or keys on the ubuntu phone. The volume of the bluetooth headset changes (good) but the ui contains no clue that this is what the phone is doing (less good). The standard volume indicator is shown. This can lead to user confusion if they are not currently using the paired bluetooth accessory, and have forgotten it is paired. On other devices the volume indicator changes to provide visual feedback that the bluetooth device volume is being set. -- Desired resolution: Please use this icon to replace the volume icon. The icon is bluetooth volume which we had design already. https://www.dropbox.com/s/a5r3ro1h0917p0a/audio-speakers-bluetooth- symbolic.svg?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415480/+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 1493427] Re: dialer app movement on screen in window mode
@kevin: I had a chat with Matthew who is working on the MIR spec. One of the suggestions I had was to reposition the windows after a reboot. The ideal case would be to show the full window to the user, positioned as close as possible to its previous "off-screen" position. Many people, myself included, close and re-open apps because a window was moved too far out of view. In most cases this window is displayed fully on screen, close to the previous position. That might solve part of the problem, at least after a reboot of the device. The indicator issue is part of an other bug, as mentioned above. ** Summary changed: - dialer app movement on screen in window mode + [dialer app] + [window management] movement on screen in window mode ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** No longer affects: mir (Ubuntu) ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1493427 Title: [dialer app] + [window management] movement on screen in window mode Status in canonical-pocket-desktop: New Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: New Bug description: somewhat related to bug 1488852 so the dialer app is currently treated like any other window in terms of movement, you can move the dialer app to the point where the dialer application window is not seen "hanging of the screen" so only the title bar of the application is visible. Also, if the device reboots, this will be the remembered location of the window. Concern was that the user might move offscreen and struggle to find it quickly for "ending call" or entering numbers at a prompt or changing from loudspeaker to earpiece or wanting to hit mute. It was discussed whether or not the dialer application should become a "special" application/surface to disallow having any portion of the window being moved offscreen ? Or is this completely ok - e.g. the user wanted to do it and should be allowed to. Or should the green banner of the dialer app in the shell be used to bring the dialer app back on screen ? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1493427/+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 1493427] Re: [dialer app] + [window management] movement on screen in window mode
@kevin: I think this is a very reasonable approach, we just need to figure out how to deal with the indicators. There seem to be an issue in therms of click & touch interactions. Just to clarify: the dialer will come back into view every time user clicks or taps on the indicators. I would say ideally in full screen mode, or the minimum mode one needs to interact with all controls. Would it be possible to always centre the dialer window? -- 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/1493427 Title: [dialer app] + [window management] movement on screen in window mode Status in canonical-pocket-desktop: New Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: New Bug description: somewhat related to bug 1488852 so the dialer app is currently treated like any other window in terms of movement, you can move the dialer app to the point where the dialer application window is not seen "hanging of the screen" so only the title bar of the application is visible. Also, if the device reboots, this will be the remembered location of the window. Concern was that the user might move offscreen and struggle to find it quickly for "ending call" or entering numbers at a prompt or changing from loudspeaker to earpiece or wanting to hit mute. It was discussed whether or not the dialer application should become a "special" application/surface to disallow having any portion of the window being moved offscreen ? Or is this completely ok - e.g. the user wanted to do it and should be allowed to. Or should the green banner of the dialer app in the shell be used to bring the dialer app back on screen ? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1493427/+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 1500483] Re: [sdk] animate header component when app comes back to the foreground
** Summary changed: - Do not instantly show the header when app comes back to the foreground + [sdk] animate header component when app comes back to the foreground -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1500483 Title: [sdk] animate header component when app comes back to the foreground Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: When the header is hidden by scrolling it out of the view in an app, and the user switches between apps, when an app comes back to the foreground, the header instantly appears again. This means when going back to a previous app, the app is not in exactly the same state as where the user left it. Example: - Open gallery-app - Scroll down to hide the header (you need to have enough photos in the gallery to scroll down). - Long left/right edge swipe to hide send the gallery-app to the background - Re-open the gallery app Result: The gallery-app re-opens with the header visible. This can be confusing for the user. Two possible solutions: 1. Show the header when re-opening the app, but animate it so the user knows what is happening 2. Don't do anything. Header stays hidden and the user can show it as they normally would. After discussing with Olga, we decided to go for solution 1. The header will show, but it must animate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1500483/+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 1500483] Re: [sdk] animate header component when app comes back to the foreground
** Description changed: When the header is hidden by scrolling it out of the view in an app, and the user switches between apps, when an app comes back to the foreground, the header instantly appears again. This means when going back to a previous app, the app is not in exactly the same state as where the user left it. Example: - Open gallery-app - Scroll down to hide the header (you need to have enough photos in the gallery to scroll down). - Long left/right edge swipe to hide send the gallery-app to the background - Re-open the gallery app Result: The gallery-app re-opens with the header visible. - This can be confusing for the user. Two possible solutions: 1. Show the header when re-opening the app, but animate it so the user knows what is happening 2. Don't do anything. Header stays hidden and the user can show it as they normally would. After discussing with Olga, we decided to go for solution 1. The header will show, but it must animate. + + + -- UX comment - + + As described above: + The header should animate once user navigates back to the app. ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Importance: Undecided => Medium ** Changed in: ubuntu-ux Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1500483 Title: [sdk] animate header component when app comes back to the foreground Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: When the header is hidden by scrolling it out of the view in an app, and the user switches between apps, when an app comes back to the foreground, the header instantly appears again. This means when going back to a previous app, the app is not in exactly the same state as where the user left it. Example: - Open gallery-app - Scroll down to hide the header (you need to have enough photos in the gallery to scroll down). - Long left/right edge swipe to hide send the gallery-app to the background - Re-open the gallery app Result: The gallery-app re-opens with the header visible. This can be confusing for the user. Two possible solutions: 1. Show the header when re-opening the app, but animate it so the user knows what is happening 2. Don't do anything. Header stays hidden and the user can show it as they normally would. After discussing with Olga, we decided to go for solution 1. The header will show, but it must animate. -- UX comment - As described above: The header should animate once user navigates back to the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1500483/+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 1456612] Re: [Dialler] The discoverability of 'recent call' tab was poor
** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Importance: High => Medium ** Description changed: The testers would like a stronger visual hint or to be introduced to the bottom tab function in the first time tutorial + + - UX comment + + This is not a dialer issue but more of how the bottom edge hint behaves + across all apps. An empty screen state could solve the problem but + potentially the SDK component will have to be updated with additional + visual design. ** Summary changed: - [Dialler] The discoverability of 'recent call' tab was poor + [SDK] The discoverability of 'recent call' tab was poor ** Changed in: ubuntu-ux Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1456612 Title: [SDK] The discoverability of 'recent call' tab was poor Status in Ubuntu UX bugs: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The testers would like a stronger visual hint or to be introduced to the bottom tab function in the first time tutorial - UX comment This is not a dialer issue but more of how the bottom edge hint behaves across all apps. An empty screen state could solve the problem but potentially the SDK component will have to be updated with additional visual design. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456612/+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 1463874] Re: [messaging app] change icon and allow other attachment types when sending MMS
** Changed in: ubuntu-ux Importance: Undecided => Medium ** Description changed: Per bug in barajas: https://bugs.launchpad.net/barajas/+bug/1372270 I believe two things need to happen here: 1) change the attachment icon from a camera to a paper clip 2) change the types we are requesting from pictures to Pictures, Contacts, Text (and in future Videos when we we support that) + + + --UX comment + + The paperclip icon is already in the wireframes and can be obtained from + the SURU icon theme. ** Changed in: ubuntu-ux Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1463874 Title: [messaging app] change icon and allow other attachment types when sending MMS Status in Ubuntu UX bugs: Fix Committed Status in messaging-app package in Ubuntu: New Bug description: Per bug in barajas: https://bugs.launchpad.net/barajas/+bug/1372270 I believe two things need to happen here: 1) change the attachment icon from a camera to a paper clip 2) change the types we are requesting from pictures to Pictures, Contacts, Text (and in future Videos when we we support that) --UX comment The paperclip icon is already in the wireframes and can be obtained from the SURU icon theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1463874/+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 1466336] Re: [messaging-app] Failed to send MMS to more than two contacts
This is not a UX but rather an implementation issue, marking as invalid. ** Summary changed: - Failed to send MMS to more than two contacts + [messaging-app] Failed to send MMS to more than two contacts ** Also affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1466336 Title: [messaging-app] Failed to send MMS to more than two contacts Status in Ubuntu UX bugs: Invalid Status in messaging-app package in Ubuntu: New Bug description: Arale, OTA4+ image #2, channel: ubuntu-touch/rc/meizu.en Steps to reproduce 1. Open messaging app 2. Select multiple contacts (more than 2) and send MMS 3. Ensure MMS sent correctly Expected results: Both MMS send and receive are ok Actual results: MMS send failed, and no contents is displayed in Messaging app, please refer to screenshot for details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1466336/+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 1468695] Re: Can't finish the message guide task when the phone is in the landscape mode
** Changed in: ubuntu-ux Importance: High => Low ** Summary changed: - Can't finish the message guide task when the phone is in the landscape mode + [messaging-app] Can't finish the message guide task when the phone is in the landscape mode -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1468695 Title: [messaging-app] Can't finish the message guide task when the phone is in the landscape mode Status in Ubuntu UX bugs: Triaged Status in messaging-app package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 30 device name: arale channel: ubuntu-touch/devel-proposed/meizu.en last update: 2015-06-23 02:58:10 version version: 30 version ubuntu: 20150622 version device: 20150608-6e66f3c version custom: 20150602-731-5-32 Reproduce steps: 1,First use message app 2,Got a message from another device 3,Enter a message to view content 4,Display guide for "how to delete the message" 5,Rotation the device to landscape mode 6,Check if the content of guide complete Expect Result: The "got it "button can display in the landscape mode normally Actual Result: The "got it "button can't display in the landscape mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1468695/+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
