[Touch-packages] [Bug 1542047] Re: visual cleanup for convergence
** Changed in: ubuntu-ux Assignee: (unassigned) => Benjamin Keyser (bjkeyser) ** Changed in: ubuntu-ux Importance: Undecided => High ** 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/1542047 Title: visual cleanup for convergence Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in address-book-app package in Ubuntu: In Progress Bug description: Information from design: 1) App should set preferred size to something that is good for desktop, i.e. that shows 2 columns width 2) in windowed mode - window decoration quickly switches between Contacts & Address Book in the naming on start of app 3) clean up empty state text, leave right hand column blank, no text at all accoding to Ben 4) google logo in 1st panel, empty list: import contacts is disappearing when you open the bottom edge briefly - should stay there until bottom edge is committed 5) when bottom edge is triggered and the background darkens, a white line is visible seemingly dividing the header and header sections; the white line seems to float on top of the bottom edge view. Should get rid of this 6) Contacts > new contact: “Add Field” should be “Add field” in the New contact view 7) Contacts > New contact - Font size for name and surname appears too large, make smaller 8) selected state in contact list view is super orange…and the names are purple -> massive no go; list item text should be aligned with new sdk guidelines as well as list item selection - use the selection rectangles instead of highlighting that olivier is using from the sdk presentation: https://docs.google.com/presentation/d/1YUJgWpH7nNFshhNsHhvVnYOjSx_sRE7mPrtupB3-F7s/edit?ts=56aa1cdf#slide=id.gb5ac35bf4_0_0 - Settings: 9) default “Addressbook” should be “Address book” from one word to two words 10) wrong icon in the default address book, seem not to use the SURU icon theme, are icons in the selector needed at all? ‘Option Selector’ used to select address book (‘default address book, etc’) - Miss-aligned assets (icon, label, chevron). usage of wrong component in address book settings for selecting a local address book, it should be a list item and then a 2nd screen listing available accounts. Check with Ben on this. At miminum fix the alignment issues he is talking about. Lower priority: 11) Settings panel in two column mode is wrong: contacts are still visible in left panel, should be list of settings in left hand panel with details in right panel To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542047/+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 1542047] Re: visual cleanup for convergence
** Description changed: Information from design: 1) App should set preferred size to something that is good for desktop, i.e. that shows 2 columns width - 2) in windowed mode - window decoration quickly switches between Contacts & Address Book in the naming on start of app + 2) in windowed mode - window decoration quickly switches between Contacts & Address Book in the naming on start of app 3) clean up empty state text, leave right hand column blank, no text at all accoding to Ben 4) google logo in 1st panel, empty list: import contacts is disappearing when you open the bottom edge briefly - should stay there until bottom edge is committed 5) when bottom edge is triggered and the background darkens, a white line is visible seemingly dividing the header and header sections; the white line seems to float on top of the bottom edge view. Should get rid of this 6) Contacts > new contact: “Add Field” should be “Add field” in the New contact view 7) Contacts > New contact - Font size for name and surname appears too large, make smaller 8) selected state in contact list view is super orange…and the names are purple -> massive no go; list item text should be aligned with new sdk guidelines as well as list item selection - use the selection rectangles instead of highlighting that olivier is using from the sdk presentation: https://docs.google.com/presentation/d/1YUJgWpH7nNFshhNsHhvVnYOjSx_sRE7mPrtupB3-F7s/edit?ts=56aa1cdf#slide=id.gb5ac35bf4_0_0 - - Settings: + - Settings: 9) default “Addressbook” should be “Address book” from one word to two words 10) wrong icon in the default address book, seem not to use the SURU icon theme, are icons in the selector needed at all? ‘Option Selector’ used to select address book (‘default address book, etc’) - Miss-aligned assets (icon, label, chevron). usage of wrong component in address book settings for selecting a local address book, it should be a list item and then a 2nd screen listing available accounts. Check with Ben on this. At miminum fix the alignment issues he is talking about. - Lower priority: - 11)Contacts > new contact: tags “home > work > other” should change to “private/personal>work>other” and Enter an email address’ & ‘home/work/other’ should read ‘Email address’ & ‘Personal/Work/other’. Is this hard? Will it cause incompatibilities? - 12) Settings panel in two column mode is wrong: contacts are still visible in left panel, should be list of settings in left hand panel with details in right panel + 11) Settings panel in two column mode is wrong: contacts are still visible in left panel, should be list of settings in left hand panel with details in right panel -- 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/1542047 Title: visual cleanup for convergence Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in address-book-app package in Ubuntu: Confirmed Bug description: Information from design: 1) App should set preferred size to something that is good for desktop, i.e. that shows 2 columns width 2) in windowed mode - window decoration quickly switches between Contacts & Address Book in the naming on start of app 3) clean up empty state text, leave right hand column blank, no text at all accoding to Ben 4) google logo in 1st panel, empty list: import contacts is disappearing when you open the bottom edge briefly - should stay there until bottom edge is committed 5) when bottom edge is triggered and the background darkens, a white line is visible seemingly dividing the header and header sections; the white line seems to float on top of the bottom edge view. Should get rid of this 6) Contacts > new contact: “Add Field” should be “Add field” in the New contact view 7) Contacts > New contact - Font size for name and surname appears too large, make smaller 8) selected state in contact list view is super orange…and the names are purple -> massive no go; list item text should be aligned with new sdk guidelines as well as list item selection - use the selection rectangles instead of highlighting that olivier is using from the sdk presentation: https://docs.google.com/presentation/d/1YUJgWpH7nNFshhNsHhvVnYOjSx_sRE7mPrtupB3-F7s/edit?ts=56aa1cdf#slide=id.gb5ac35bf4_0_0 - Settings: 9) default “Addressbook” should be “Address book” from one word to two words 10) wrong icon in the default address book, seem not to use the SURU icon theme, are icons in the selector needed at all? ‘Option Selector’ used to select address book (‘default address book, etc’) - Miss-aligned assets (icon, label, chevron). usage of wrong component in address book settings for selecting a local address book, it should be a list item and then a 2nd screen listing available accounts. Check with Ben on this. At miminum fix the
[Touch-packages] [Bug 1542047] Re: visual cleanup for convergence
** 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 address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1542047 Title: visual cleanup for convergence Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in address-book-app package in Ubuntu: Confirmed Bug description: Information from design: 1) App should set preferred size to something that is good for desktop, i.e. that shows 2 columns width 2) in windowed mode - window decoration quickly switches between Contacts & Address Book in the naming on start of app 3) clean up empty state text, leave right hand column blank, no text at all accoding to Ben 4) google logo in 1st panel, empty list: import contacts is disappearing when you open the bottom edge briefly - should stay there until bottom edge is committed 5) when bottom edge is triggered and the background darkens, a white line is visible seemingly dividing the header and header sections; the white line seems to float on top of the bottom edge view. Should get rid of this 6) Contacts > new contact: “Add Field” should be “Add field” in the New contact view 7) Contacts > New contact - Font size for name and surname appears too large, make smaller 8) selected state in contact list view is super orange…and the names are purple -> massive no go; list item text should be aligned with new sdk guidelines as well as list item selection - use the selection rectangles instead of highlighting that olivier is using from the sdk presentation: https://docs.google.com/presentation/d/1YUJgWpH7nNFshhNsHhvVnYOjSx_sRE7mPrtupB3-F7s/edit?ts=56aa1cdf#slide=id.gb5ac35bf4_0_0 - Settings: 9) default “Addressbook” should be “Address book” from one word to two words 10) wrong icon in the default address book, seem not to use the SURU icon theme, are icons in the selector needed at all? ‘Option Selector’ used to select address book (‘default address book, etc’) - Miss-aligned assets (icon, label, chevron). usage of wrong component in address book settings for selecting a local address book, it should be a list item and then a 2nd screen listing available accounts. Check with Ben on this. At miminum fix the alignment issues he is talking about. Lower priority: 11)Contacts > new contact: tags “home > work > other” should change to “private/personal>work>other” and Enter an email address’ & ‘home/work/other’ should read ‘Email address’ & ‘Personal/Work/other’. Is this hard? Will it cause incompatibilities? 12) Settings panel in two column mode is wrong: contacts are still visible in left panel, should be list of settings in left hand panel with details in right panel To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542047/+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 1537142] Re: Preview text should be user copyable
** Changed in: ubuntu-ux Assignee: (unassigned) => Paty Davila (dizzypaty) ** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1537142 Title: Preview text should be user copyable Status in The Savilerow project: New Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: New Bug description: There are many cases where a use may want to copy text from a scope preview, but they are now not able to. For example, in my dropbox photos scope, in a preview, the user can click a button to make a shared link to the photo. This shared link is simply a URL text string. The user would want to copy this to, for example, put it in email to a friend. Currently the only way the user can get this string is by opening the shared link (from a preview button) in the browser, tapping the browser address bar to display the full text of the url, then copying it. So either specified preview text or perhaps (preferably) all preview text should be user copyable. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1537142/+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 1540240] Re: Automatic Header height adjustment should be optional
** Changed in: ubuntu-ux Status: New => Triaged ** 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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1540240 Title: Automatic Header height adjustment should be optional Status in Ubuntu UX: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: I am currently developing a convergence capable CAD App and i recently switched the UI to use AdaptivePageLayout and the new headers. I have noticed that the header automatically resizes across columns to match the column with the greatest header height. This doesn't suit my particular application as I would like to maintain maximum screen space for the drawing canvas. I have attached some screenshots (early development - dont judge me!!) of what I am seeing. It would be super cool if you could include a flag or option to disable the header adjustment for any particular page or column. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1540240/+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 1456644] Re: [messaging] Resend issues
@Johannes - the correct designs are provided, I guess it is just not implemented yet. As for the translation, sometimes it makes sense not to translate english phrasings directly into other languages. This seems to be a good example. How about using "erneut" "nochmal", etc? E.g. "Erneut senden" could go into two lines in this case. -- 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/1456644 Title: [messaging] Resend issues Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: If a message is not sent successfully, testers expected the phone to provide a resent option or to automatically resend the message when the signal is back "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 on the train or around places where full of high buildings. It is important to design for these restrictions. " The swipe to reveal a resent option for a text message was not discovered - UX comment We already provide an option to resend from the in message view if a message fails to send. The message changes to red and previously there was a "Failed!" text below the resent icon. Since that was not very well understood, the text should be changed to "Resend" below the resend icon. Please amend this and for visuals see this spec: https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g18adf9eae_5116 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456644/+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 1428757] Re: [SDK] Header should be responsive for Tablet and Desktop form factors
** 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/1428757 Title: [SDK] Header should be responsive for Tablet and Desktop form factors Status in Ubuntu UI Toolkit: Fix Committed Status in Ubuntu UX: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: As part of our convergence path to Tablet and Desktop form factors, we will have more screen real estate and less constrained. Therefore, we have more space to provide additional affordances. - Optional subheader, with increased flexibility - Max 4 slots on the right - Capability of adding input field expanded or dropdown (not both) - Capability of adding tabs - Capability of having responsive labels display - once breakpoint is reached, labels are displayed UX spec here: https://www.dropbox.com/s/j47sua4ilof0zud/050315_Convergence%20-%20Header_gv.pdf?dl=0 VD link TBC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428757/+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 1431564] Re: Can't use mouse to access bottom edge
** Changed in: ubuntu-ux Status: In Progress => Fix Committed -- 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/1431564 Title: Can't use mouse to access bottom edge Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: If I connect my BT mouse to my Nexus 4 running devel-proposed with silo 0 (the MWC demo), I can neither open the app spread nor the manage scopes overview. Using the touch screen, both actions work fine, even when the mouse is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1431564/+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 1336793] Re: [sdk] Smaller header in landscape orientation
** Changed in: ubuntu-ux Status: In Progress => Fix Released ** Changed in: ubuntu-ux Assignee: Jouni Helminen (jounihelminen) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: Fix Released => Fix Committed ** Changed in: ubuntu-ux Importance: Low => High -- 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/1336793 Title: [sdk] Smaller header in landscape orientation Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: Make the header less high when in landscape orientation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1336793/+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 1431564] Re: Can't use mouse to access bottom edge
Tested on tablet, customized image part 20150929-vivid and it is working fine. Marking as Fix Released ** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1431564 Title: Can't use mouse to access bottom edge Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: If I connect my BT mouse to my Nexus 4 running devel-proposed with silo 0 (the MWC demo), I can neither open the app spread nor the manage scopes overview. Using the touch screen, both actions work fine, even when the mouse is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1431564/+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 1531270] Re: Shell always switches to Windowed mode when mouse is connected
** No longer affects: ubuntu-ux -- 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/1531270 Title: Shell always switches to Windowed mode when mouse is connected Status in Client Developer Experience: New Status in Canonical System Image: Confirmed Status in android package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: When the emulator starts it presents the login screen for the phablet user, presumably because it detects a mouse. I expect it to emulate the phone and provide the passcode screen as approproate (see also bug #1531268) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-developer-experience/+bug/1531270/+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 1530371] Re: Number of unread messages within icon
** Changed in: ubuntu-ux Assignee: (unassigned) => Paty Davila (dizzypaty) ** Changed in: ubuntu-ux Status: New => Triaged ** 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 messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1530371 Title: Number of unread messages within icon Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in messaging-app package in Ubuntu: New Bug description: It would be nice to display the total number of unread messages within the icon (like the telegram app does). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1530371/+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 1489330] Re: [address book] Empty state for Favorites view not correct
** Description changed: The empty state for the Favorites view of the contacts is confusing and should be improved. Currently if you have populated contacts but not favorites, it will show: "Create a new contact by swiping up from the bottom of the screen". If you do swipe up and create a contact it is not even made a favorite. I'd propose changing the message to something like: - "You have no favorites. Open a contact and select star button to favorite" or something along those lines - It's fine to leave the "+" on bottom edge but the Star should be automatically selected if you create the new contact from the Favorites view - UX comment --- As per comment #1: remove the favourites section from the header until user starts favouriting contacts. This way we can avoid maintenance on empty states and only surface the right sections if they are in use. + + Addition: + Regardless what section the user is in, triggering the bottom edge would only create a new contact. This means that even if the contact is seemingly created e.g. in the Favourites section, the contact is not automatically stored there. -- 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/1489330 Title: [address book] Empty state for Favorites view not correct Status in Canonical System Image: In Progress Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: In Progress Bug description: The empty state for the Favorites view of the contacts is confusing and should be improved. Currently if you have populated contacts but not favorites, it will show: "Create a new contact by swiping up from the bottom of the screen". If you do swipe up and create a contact it is not even made a favorite. I'd propose changing the message to something like: - "You have no favorites. Open a contact and select star button to favorite" or something along those lines - It's fine to leave the "+" on bottom edge but the Star should be automatically selected if you create the new contact from the Favorites view UX comment --- As per comment #1: remove the favourites section from the header until user starts favouriting contacts. This way we can avoid maintenance on empty states and only surface the right sections if they are in use. Addition: Regardless what section the user is in, triggering the bottom edge would only create a new contact. This means that even if the contact is seemingly created e.g. in the Favourites section, the contact is not automatically stored there. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489330/+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 1522058] Re: Add search capability to picker mode
** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: New => Confirmed ** Summary changed: - Add search capability to picker mode + [address book] Add search capability to picker mode -- 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/1522058 Title: [address book] Add search capability to picker mode Status in Ubuntu UX: Confirmed Status in address-book-app package in Ubuntu: New Bug description: While in multi selection contacts would be nice to be able to search for individual contacts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1522058/+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 1521948] [NEW] [indicators] + [mobile] hide indicator bar when mobile devices rotate into landscape
Public bug reported: Issue: In the current build the landscape mode is showing indicators in apps which are using it. Displaying the indicator bar takes away some screen estate, especially when the OSK is visible as well. Design and SDK are working on reducing the header hight when mobile devices are rotated into landscape but hiding indicators needs to be done system wide. UX comment | desired resolution -- Please ensure that if a mobile devices rotates into landscape mode the indicator bar is hidden automatically. Indicators should be still available by swiping from the top edge. For visual/UX reference please refer to this spec: https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit?pli=1#heading=h.sdqqbpcpmqmd Also, please refer to attachement ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: ubuntu-ux Importance: High Assignee: Olga Kemmet (olga-kemmet) Status: Fix Committed ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: ota9 ** Attachment added: "122015_header_transition_mobile_portrait_landscape.png" https://bugs.launchpad.net/bugs/1521948/+attachment/4528525/+files/122015_header_transition_mobile_portrait_landscape.png ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: New => Fix Committed ** Changed in: ubuntu-ux Importance: Undecided => Medium ** Changed in: ubuntu-ux Importance: Medium => High -- 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/1521948 Title: [indicators] + [mobile] hide indicator bar when mobile devices rotate into landscape Status in Canonical System Image: New Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: New Bug description: Issue: In the current build the landscape mode is showing indicators in apps which are using it. Displaying the indicator bar takes away some screen estate, especially when the OSK is visible as well. Design and SDK are working on reducing the header hight when mobile devices are rotated into landscape but hiding indicators needs to be done system wide. UX comment | desired resolution -- Please ensure that if a mobile devices rotates into landscape mode the indicator bar is hidden automatically. Indicators should be still available by swiping from the top edge. For visual/UX reference please refer to this spec: https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit?pli=1#heading=h.sdqqbpcpmqmd Also, please refer to attachement To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521948/+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 1521948] Re: [indicators] + [mobile] hide indicator bar when mobile devices rotate into landscape
We had a little bit of a discussion with Gerry, Ben and myself. The rule we came up with is as follows: Every single time the OSK pops up in landscape mode, indicators are hidden. This applies only for phones and tablets. -- 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/1521948 Title: [indicators] + [mobile] hide indicator bar when mobile devices rotate into landscape Status in Canonical System Image: New Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: Incomplete Bug description: Issue: In the current build the landscape mode is showing indicators in apps which are using it. Displaying the indicator bar takes away some screen estate, especially when the OSK is visible as well. Design and SDK are working on reducing the header hight when mobile devices are rotated into landscape but hiding indicators needs to be done system wide. UX comment | desired resolution -- Please ensure that if a mobile devices rotates into landscape mode the indicator bar is hidden automatically. Indicators should be still available by swiping from the top edge. For visual/UX reference please refer to this spec: https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit?pli=1#heading=h.sdqqbpcpmqmd Also, please refer to attachement To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521948/+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)
@tiagosh: Yes, I am aware of that. :) One other solution I thought about was to remove "Incoming call" and simply replace it with "SIM1" or whatever label user is choosing. This would only apply to dual SIM devices though. For a single SIM device the initial "Incoming call" text should remain on the incoming call snap. -- 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 replace the "Incoming call" text. This applies only for dual SIM devices. On a single SIM device the "Incoming call" labe remains. 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 1460301] Re: [Dialer] Incoming call - no info which SIM card was called (dual SIM)
** 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. + The SIM card indication should replace the "Incoming call" text. This + applies only for dual SIM devices. On a single SIM device the "Incoming + call" labe remains. Please see attached wireframe for the exact + solution. ** Attachment removed: "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 ** Attachment added: "Incoming call snap with SIM indication wireframe.jpg" https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1460301/+attachment/4524033/+files/Incoming%20call%20snap%20with%20SIM%20indication%20wireframe.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 replace the "Incoming call" text. This applies only for dual SIM devices. On a single SIM device the "Incoming call" labe remains. 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 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. There is - a SIM stamp on the right hand side, centered with the name. + Please find attached to this bug a design solution which shows two solutions for the here described issue. + A. Places the [SIM name] in the place of a time stamp (recommended). + B. Adds [SIM name] after the header of the notification. + + Solution B may be applied if solution A can not be implemented for the + time being. 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 shows two solutions for the here described issue. A. Places the [SIM name] in the place of a time stamp (recommended). B. Adds [SIM name] after the header of the notification. Solution B may be applied if solution A can not be implemented for the time being. 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
@tiago: There is a notifications spec but I don't think anyone implemented the designs just yet. Here is the link: https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1# A good example of the messaging bubble is on page 29. A. This spec allows stamps on the right hand side in the bubble. Originally this place was reserved for a time stamp but this info is not needed on the lock screen/normal usage. This means that the time stamp space can be used for indicating which SIM the message was sent to. B. If this implementation causes issues we can fall back on doing the following: Add the SIM tag next to the NAME in the notification bubble. Please see for both solution the new attachment. Notification Centre: Paty and I reviewed the current implementation and it looks ok for now. There is going to be a redesign of the notification centre but it is not clear when this happens. Ergo, displaying "1 Voicemail - [name of SIM]" is correct for the time being. ** Attachment removed: "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 -- 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 shows two solutions for the here described issue. A. Places the [SIM name] in the place of a time stamp (recommended). B. Adds [SIM name] after the header of the notification. Solution B may be applied if solution A can not be implemented for the time being. 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
** Attachment added: "MMS - two options.png" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487528/+attachment/4524072/+files/MMS%20-%20two%20options.png -- 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 shows two solutions for the here described issue. A. Places the [SIM name] in the place of a time stamp (recommended). B. Adds [SIM name] after the header of the notification. Solution B may be applied if solution A can not be implemented for the time being. 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 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 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 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 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 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 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
** 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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] + [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 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 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 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 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 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 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 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 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 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 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 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 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
[Touch-packages] [Bug 1489330] Re: [address book] Empty state for Favorites view not correct
** Description changed: The empty state for the Favorites view of the contacts is confusing and should be improved. Currently if you have populated contacts but not favorites, it will show: "Create a new contact by swiping up from the bottom of the screen". If you do swipe up and create a contact it is not even made a favorite. I'd propose changing the message to something like: - "You have no favorites. Open a contact and select star button to favorite" or something along those lines - It's fine to leave the "+" on bottom edge but the Star should be automatically selected if you create the new contact from the Favorites view + + + UX comment --- + + As per comment #1: remove the favourites section from the header until + user starts favouriting contacts. This way we can avoid maintenance on + empty states and only surface the right sections if they are in use. ** 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/1489330 Title: [address book] Empty state for Favorites view not correct Status in Canonical System Image: Confirmed Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: Confirmed Bug description: The empty state for the Favorites view of the contacts is confusing and should be improved. Currently if you have populated contacts but not favorites, it will show: "Create a new contact by swiping up from the bottom of the screen". If you do swipe up and create a contact it is not even made a favorite. I'd propose changing the message to something like: - "You have no favorites. Open a contact and select star button to favorite" or something along those lines - It's fine to leave the "+" on bottom edge but the Star should be automatically selected if you create the new contact from the Favorites view UX comment --- As per comment #1: remove the favourites section from the header until user starts favouriting contacts. This way we can avoid maintenance on empty states and only surface the right sections if they are in use. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489330/+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 1489330] Re: Empty state for Favorites view not correct
** 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/1489330 Title: Empty state for Favorites view not correct Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in address-book-app package in Ubuntu: Confirmed Bug description: The empty state for the Favorites view of the contacts is confusing and should be improved. Currently if you have populated contacts but not favorites, it will show: "Create a new contact by swiping up from the bottom of the screen". If you do swipe up and create a contact it is not even made a favorite. I'd propose changing the message to something like: - "You have no favorites. Open a contact and select star button to favorite" or something along those lines - It's fine to leave the "+" on bottom edge but the Star should be automatically selected if you create the new contact from the Favorites view To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489330/+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 1489330] Re: [address book] Empty state for Favorites view not correct
** Summary changed: - Empty state for Favorites view not correct + [address book] Empty state for Favorites view not correct -- 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/1489330 Title: [address book] Empty state for Favorites view not correct Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in address-book-app package in Ubuntu: Confirmed Bug description: The empty state for the Favorites view of the contacts is confusing and should be improved. Currently if you have populated contacts but not favorites, it will show: "Create a new contact by swiping up from the bottom of the screen". If you do swipe up and create a contact it is not even made a favorite. I'd propose changing the message to something like: - "You have no favorites. Open a contact and select star button to favorite" or something along those lines - It's fine to leave the "+" on bottom edge but the Star should be automatically selected if you create the new contact from the Favorites view To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489330/+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 1489330] Re: [address book] Empty state for Favorites view not correct
I am not sure if it is the best idea to change the copy for the empty state. This would mean that we have to change the copy every single time if a new group is created and a new section appears in the header. How about reassessing the need of a favourites section in the first place when no contact was made a favourite yet? As the plan is to move frequently called entries into the recent call screen, this section might always be empty because some users simply never favourite any contacts (me for example). This means that the section will be always present, even if unused. My suggestion is to only surface the favourites tab in the header sections if users really use it, this way we remove any need of additional empty states. -- 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/1489330 Title: [address book] Empty state for Favorites view not correct Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in address-book-app package in Ubuntu: Confirmed Bug description: The empty state for the Favorites view of the contacts is confusing and should be improved. Currently if you have populated contacts but not favorites, it will show: "Create a new contact by swiping up from the bottom of the screen". If you do swipe up and create a contact it is not even made a favorite. I'd propose changing the message to something like: - "You have no favorites. Open a contact and select star button to favorite" or something along those lines - It's fine to leave the "+" on bottom edge but the Star should be automatically selected if you create the new contact from the Favorites view To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489330/+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 1456644] Re: [messaging] Resend issues
@Johannes: We opted not to resend automatically because in many cases users like to have control over the messages they send and any potential cost involved sending an SMS/MMS. -- 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/1456644 Title: [messaging] Resend issues Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: If a message is not sent successfully, testers expected the phone to provide a resent option or to automatically resend the message when the signal is back "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 on the train or around places where full of high buildings. It is important to design for these restrictions. " The swipe to reveal a resent option for a text message was not discovered - UX comment We already provide an option to resend from the in message view if a message fails to send. The message changes to red and previously there was a "Failed!" text below the resent icon. Since that was not very well understood, the text should be changed to "Resend" below the resend icon. Please amend this and for visuals see this spec: https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g18adf9eae_5116 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456644/+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 1278790] Re: [Messaging] Show number of characters used
** Changed in: ubuntu-ux Status: Fix Committed => Triaged -- 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/1278790 Title: [Messaging] Show number of characters used Status in Ubuntu UX: Triaged Status in messaging-app package in Ubuntu: Confirmed Bug description: As many carriers charge per text message sent, it'd be nice to show how many characters were used for the message, so the sender knows how many sent text messages this boils down to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1278790/+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 1432696] Re: [SDK] Bottom edge header improvement
** 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 messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1432696 Title: [SDK] Bottom edge header improvement Status in Dekko: Fix Released Status in Ubuntu Calendar App: Invalid Status in Ubuntu Clock App: Fix Released Status in Ubuntu Document Viewer App: Fix Released Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: Confirmed Status in dialer-app package in Ubuntu: Confirmed Status in messaging-app package in Ubuntu: Confirmed Status in ubuntu-clock-app package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: When user does a bottom edge gesture to show a new view (Address Book, Dialer, Clock, etc) the new header should never have a chevron pointing left, as it seems to suggest the wrong direction for the movement. The header of the new View should always have a chevron pointing down. Also, it should allow people using a gesture and dismiss the new screen by dragging or swiping the [chevron & title area of the header] downward UX here: https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0 VD: https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1432696/+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 1492238] Re: back button hard to reach/use
** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Importance: Undecided => Medium ** Description changed: Open some sub page, e.g. updates. If you want to go back to the main screen one has to reach quite small < button on the top left corner. It would be easier if the whole updates field would act as a back button or even better, just swipe from left to right. + + + UX comment -- + + The plan is to make the whole area of title& BACK button tappable. + This is specified in the UI Toolkit documentation and will hopefully land whit the next SDK release. ** Changed in: ubuntu-ux Status: New => Fix Committed ** Summary changed: - back button hard to reach/use + [sdk] back button hard to reach/use ** Description changed: Open some sub page, e.g. updates. If you want to go back to the main screen one has to reach quite small < button on the top left corner. It would be easier if the whole updates field would act as a back button or even better, just swipe from left to right. - UX comment -- - The plan is to make the whole area of title& BACK button tappable. + The plan is to make the whole area of title & BACK button tappable. This is specified in the UI Toolkit documentation and will hopefully land whit the next SDK release. -- 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/1492238 Title: [sdk] back button hard to reach/use Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Open some sub page, e.g. updates. If you want to go back to the main screen one has to reach quite small < button on the top left corner. It would be easier if the whole updates field would act as a back button or even better, just swipe from left to right. UX comment -- The plan is to make the whole area of title & BACK button tappable. This is specified in the UI Toolkit documentation and will hopefully land whit the next SDK release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1492238/+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 1364638] Re: [address book] Edit > Fields (Address, Phone, Email) are poorly distinguished, and "Edit" page title is non-descriptive.
** Changed in: ubuntu-ux Status: Fix Released => Triaged ** Changed in: ubuntu-ux Assignee: Olga Kemmet (olga-kemmet) => (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) => Rae Shambrook (raecontreras) ** Changed in: ubuntu-ux Importance: Low => Medium -- 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/1364638 Title: [address book] Edit > Fields (Address, Phone, Email) are poorly distinguished, and "Edit" page title is non-descriptive. Status in address-book-app: Triaged Status in Ubuntu UX: Triaged Status in address-book-app package in Ubuntu: Triaged Bug description: Small Aesthetic opinion http://i.imgur.com/V5tanmc.png A. The titles almost look like they can be clicked. B. The seperators look like they encapsulate one item. For example in the screenshot, the item looks like this: --- Number Home Email --- C. Page Title: "Edit"? Edit Contacts, or Edit my contact info? I suppose considering that I can't connect to the server on qml scene, I am confused as whether this is my own personal details, or the hypothetical person I have in a list. UX comment & resolution There is a UX and UI change for the Address Book app. Edit always refers to the page you are editing and the way you normally land on this page is: 1. Open Address Book app 2. Tap on a contact 3. view contact card 4. tap edit in the top right of the header in the contact card 5. view switches and you are able to edit the contact. For the latest visual design please refer to the visual design spec: https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g18adf9eae_59 The different sections are now much better separated. Closing this bug as Fix Released because solution is provided. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1364638/+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 1368671] Re: [dialer-app]+[address-book]+[messaging] expansion should be removed from all contact list views
marking as Fix Released, tested on krillin 15.04 r117 ** 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 messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1368671 Title: [dialer-app]+[address-book]+[messaging] expansion should be removed from all contact list views Status in Canonical System Image: Fix Released Status in Ubuntu UX: 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: New Status in dialer-app source package in Vivid: New Status in messaging-app source package in Vivid: New Bug description: Steps to reproduce: 1. Open any of the following apps - > Address Book, Phone & Messaging app 2. Navigate to a contact list view/page 3. Tap on a contact list item 4. Current implementation: the list item expands and gives you a selection of numbers and an icon appears on the tapped list item, to access contact's profile UX comment - desired solution: Remove expansion pattern from all contact views/lists. A tap action a the contact list item should open the detail screen of the contact. ---UPDATE This is became a usability issue because people didn't understand the tap and the additional tap to view the full contact details. Comment #2 "User testing showed, that expansion is not working vey well or user can not navigate all the time to the actual contact card." To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368671/+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 1489517] Re: can't quit apps with touch in right-edge-spread when in windowed mode
** Changed in: ubuntu-ux Assignee: (unassigned) => Vesa Rautiainen (vesar) -- 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/1489517 Title: can't quit apps with touch in right-edge-spread when in windowed mode Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: vivid+o + silo0, easier on n7 steps 1. launch a few apps 2. connect to monitor, putting unity8 into window mode 3. right edge swipe to open spread 4. attempt to close by touching little red x out button on top left corner of app in spread expected: it would close result: it just selects seems to be just a diff between touch and cursor that might have been a design decision? or maybe just a bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1489517/+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 1347913] Re: [incoming call] Turn screen on when phone is moved during a call
** Changed in: ubuntu-ux Status: In Progress => 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/1347913 Title: [incoming call] Turn screen on when phone is moved during a call Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: New Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: This is a breakaway bug from bug 1347001. During a call, position the phone such that the proximity sensor is not enabled, i.e. put phone on table. Let the screen shut off after an idle timeout. The screen should turn on when the phone is moved or screen is touched. This is what Android and iOS do anyway, and probably what users expect. I'm assuming that powerd is the logical place to have that logic, but maybe I'm wrong. Please feel free to re-assign. - UX comment Design is collecting all bugs on any hardware related issues to kick off a bigger project. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1347913/+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: Fix Committed => Triaged -- 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: Triaged 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 1338138] Re: [sdk] Time Picker component does not respect user locale
** Changed in: ubuntu-ux
Assignee: Olga Kemmet (olga-kemmet) => Pierre Bertet (bpierre)
--
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/1338138
Title:
[sdk] Time Picker component does not respect user locale
Status in Ubuntu UX:
Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
In the new clock app we are using the Date Picker component to allow
the user to choose a time. Hence the mode used was "Hours|Minutes".
However the Date Picker seems to always display the time in 24 hour
instead of using the user's locale. So whereever 12-hour time format
is required, the time picker ignores that.
The code below shows the usage in the clock app.
DatePicker {
id: _timePicker
anchors {
left: parent.left
right: parent.right
margins: units.gu(-2)
}
clip: true
mode: "Hours|Minutes"
}
-- Design solution --
https://docs.google.com/a/canonical.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#heading=h.tuxva2dtgvpk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1338138/+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 1391839] Re: [sdk] Cannot change boundsBehaviour on Flickable in Expandable
** Changed in: ubuntu-ux Status: Fix Committed => Triaged ** Changed in: ubuntu-ux Assignee: Olga Kemmet (olga-kemmet) => Femma (femma) -- 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/1391839 Title: [sdk] Cannot change boundsBehaviour on Flickable in Expandable Status in Ubuntu UI Toolkit: Incomplete Status in Ubuntu UX: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Right now it's quite unfortunate that some Expandables can be dragged and overshot (Flickable.DragAndOvershootBounds). Could the Expandable expose the boundsBehaviour property or in some other way make this changeable? UX Solution: We should have a good default, then allow developers to change the property. For example, an app developer might not want to have overshoot at all and provide a different hint that the list/area boundaries have been reached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1391839/+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 1276066] Re: [sdk] Checkbox cannot be stopped from animating
** Changed in: ubuntu-ux
Assignee: Olga Kemmet (olga-kemmet) => Matthew Paul Thomas (mpt)
--
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/1276066
Title:
[sdk] Checkbox cannot be stopped from animating
Status in Ubuntu UI Toolkit:
Incomplete
Status in Ubuntu UX:
Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
Incomplete
Bug description:
The Checkbox component always animates its state transitions.
Sometimes, the "checked" property is set shortly after initialization,
which shows the animation when creating a page. For example, this
happens when using the GSettings object, which fills in its properties
in its componentCompleted:
GSettings {
id: settings
schema.id: "com.ubuntu.touch.system"
}
CheckBox {
checked: settings.autoBrightness
}
It would be nice if there was a property "animate" which could be used
to suppress animations while loading a page.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1276066/+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 1234886] Re: [physical keyboard] No way to auto-repeat
** Changed in: ubuntu-ux Assignee: Olga Kemmet (olga-kemmet) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1234886 Title: [physical keyboard] No way to auto-repeat Status in ubuntu-keyboard: Triaged Status in Ubuntu UX: Incomplete Status in ubuntu-keyboard package in Ubuntu: Triaged Bug description: Auto repeat doesn't seem to work. If it is a hidden gesture or feature, it is not easily discoverable. $ adb shell system-image-cli -i current build number: 78 device name: mako channel: stable last update: 2013-10-03 13:05:32 version version: 78 version ubuntu: 20131003 version device: 20131002.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1234886/+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 1464466] Re: [messaging-app] SIM preference ignored for MMS
** Description changed: I discovered today that the user's choice of SIM slot (configured in the messaging app) is only used for SMS. This setting gets ignored for MMS, and instead it uses whatever system settings / cellular has configured for cell data. This can cause failure to send MMS, if the other slot has no service, or can cause the message to be sent from the wrong number. I saw this in krillin ubuntu-touch/ubuntu-rtm/14.09-factory-proposed image 10, the OTA4 candidate. I'm not sure how feasible it is to configure this in the same manner as SMS uses, since the phone generally only connects to one cell data provider at a time, but it would be nice if it used the same policies as SMS. ---comment- - This bug depends is not a UX bug however, depends on this one here: + This bug is not a UX bug however, depends on this one here: https://bugs.launchpad.net/ubuntu-ux/+bug/1426278 Once the actual UX bug is solved this one can be patched too. Removing Ubuntu-UX -- 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/1464466 Title: [messaging-app] SIM preference ignored for MMS Status in messaging-app package in Ubuntu: New Status in nuntium package in Ubuntu: New Bug description: I discovered today that the user's choice of SIM slot (configured in the messaging app) is only used for SMS. This setting gets ignored for MMS, and instead it uses whatever system settings / cellular has configured for cell data. This can cause failure to send MMS, if the other slot has no service, or can cause the message to be sent from the wrong number. I saw this in krillin ubuntu-touch/ubuntu-rtm/14.09-factory-proposed image 10, the OTA4 candidate. I'm not sure how feasible it is to configure this in the same manner as SMS uses, since the phone generally only connects to one cell data provider at a time, but it would be nice if it used the same policies as SMS. ---comment- This bug is not a UX bug however, depends on this one here: https://bugs.launchpad.net/ubuntu-ux/+bug/1426278 Once the actual UX bug is solved this one can be patched too. Removing Ubuntu-UX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1464466/+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: ubuntu-ux Importance: Undecided Status: New ** 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 telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1474940 Title: phone call ends after 2 hours Status in Ubuntu UX: 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) 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 1470057] Re: [Navigation] Long left swipe inconsistent in apps/scopes
** Changed in: ubuntu-ux Assignee: John Lea (johnlea) => Vesa Rautiainen (vesar) ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: Vesa Rautiainen (vesar) => 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/1470057 Title: [Navigation] Long left swipe inconsistent in apps/scopes Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: New Bug description: Open an app Long swipe in from left -> Takes you to your default scope Swipe across to a different scope Long swipe in from left -> Does nothing Should they not both do the same thing? Return your back to the default scope? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1470057/+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 1486008] Re: [sdk] leading actions width is too small making it very difficult to press
** Summary changed:
- leading actions width is too small making it very difficult to press
+ [sdk] leading actions width is too small making it very difficult to press
--
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/1486008
Title:
[sdk] leading actions width is too small making it very difficult to
press
Status in Ubuntu UX:
Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
Since a recent update to the ListItem leading actions in
Ubuntu.Components 1.2, where the width of the action was clamped, the
width is too small to press comfortably on a phone resulting in it
missing 9 out of 10 tries. It affects the usability of the action and
may be become a release blocker for apps that have recently switched
over to the new list items.
Sample App
import QtQuick 2.4
import Ubuntu.Components 1.2
MainView {
applicationName: "testdelete.nik90"
width: units.gu(100)
height: units.gu(75)
Page {
title: "Swipe to Delete"
ListItem {
id: listItem
anchors.top: parent.top
Label {
text: "Swipe me right to delete this listitem"
wrapMode: Text.WordWrap
anchors { left: parent.left; leftMargin: units.gu(2); right:
parent.right; verticalCenter: parent.verticalCenter }
}
leadingActions: ListItemActions {
actions: [
Action {
iconName: "delete"
onTriggered: listItem.destroy()
}
]
}
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1486008/+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 1488865] Re: Jump to top of page functionality missing in web browser
** Also affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Assignee: (unassigned) => James Mulholland (jamesjosephmulholland) ** Changed in: ubuntu-ux Status: New => Triaged ** 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 webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1488865 Title: Jump to top of page functionality missing in web browser Status in Ubuntu UX: Triaged Status in webbrowser-app package in Ubuntu: New Bug description: I would like to propose that "jump to top of page" be considered for inclusion in the web browser. This is something I'm really missing from Ubuntu Touch on my bq E5. On iOS touching the top of the screen will jump to the top of the page. On PS Vita there's a button on the toolbar that does the same thing. Some web pages will have menus or search at the top of the page and I believe it would be a good idea to allow users to quickly get back to the top. The way iOS does this clearly seems unsuited to Ubuntu with its top menu bar. I would like to propose two ways to implement this: 1. A button next to the back/forward buttons, like so: <^ [address] or <>^ [address] or 2. A sufficiently vigorous swipe down would send the page directly to the top. I like the 2nd option more, since it won't clutter the top bar with an additional button and I believe users are bound to discover the functionality by themselves anyway. A fast, vigorous swipe down would be used by the user exactly in that situation - when trying to quickly get back to the top of the page. Right now a couple or more swings are necessary on long pages (e.g. www.gamingonlinux.com), plus having to wait for the page to scroll. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1488865/+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 1450846] Re: [SDK] Changing the font / font size...
** Changed in: ubuntu-ux Assignee: John Lea (johnlea) => Jamie Young (jamiedawsonyoung) -- 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/1450846 Title: [SDK] Changing the font / font size... Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It would be usefull if the font and the font size could be changed espacially for elderly users and for people with visual problems. So content could be read easily. Changing colors, features like home screen simplification, large icons... would be great, too. Should be found in system settings → background To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450846/+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
** No longer affects: ubuntu-ui-toolkit (Ubuntu) -- 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 Ubuntu Document Viewer App: Fix Released Status in Ubuntu UX: Fix Committed 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. DESIRED SOLUTION: See "Option A" in the comment #4. 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 1483888] Re: Ringtone cannot be heard when jack/headphones plugged
** Changed in: telephony-service (Ubuntu) Assignee: Olga Kemmet (olga-kemmet) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1483888 Title: Ringtone cannot be heard when jack/headphones plugged Status in Canonical System Image: New Status in telephony-service package in Ubuntu: Confirmed Bug description: Aquaris E5: Ringtone cannot be heard when jack/headphones are plugged. This I consider a bug, since user cannot depend on the such a device with hearing calls in the morning. Typical scenario: listening to music/watching movies during the night and falling asleep. It already happened several times to me that I did not get awakened by the phone in the morning, since headphones were plugged into the device and all the sounds could be heard only in headphones. (The equivalent for the alarm clock is bug 1364647.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1483888/+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
