[Touch-packages] [Bug 1634544] Re: Missing many calls/messages
I have exactly the same issue on my BQ E4.5 ** Also affects: system-image (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1634544 Title: Missing many calls/messages Status in ofono package in Ubuntu: Confirmed Status in system-image package in Ubuntu: New Bug description: I repeatedly miss calls and text messages. I simply find some time in the future when I look at my phone I have missed calls or messages waiting for me. I've always assumed that the phone is not making any noise or vibrating, otherwise I would have noticed, but today I caught it in the act for the first time. The phone was sitting on the table right next to me, when I looked at it, there was a notification for an incoming call, there was no sound, there was no vibration. The phone was not in silent mode, it was set to medium volume in a quiet environment. This does not happen to every call, but to a significant number that it is very annoying, as a vague idea, somewhere in the range of 10-60%. This has been happening for months atleast. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1634544/+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 1508363] Re: Coordinated migration to UITK 1.3
** Changed in: ubuntu-calculator-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1508363 Title: Coordinated migration to UITK 1.3 Status in Canonical System Image: Fix Released Status in Ubuntu Music App: Fix Released Status in Ubuntu Notes app: Fix Committed Status in Tagger: Fix Released Status in task-app: In Progress Status in Ubuntu Calculator App: Fix Released Status in Ubuntu Calendar App: Fix Released Status in Ubuntu Clock App: Fix Released Status in Ubuntu Document Viewer App: Fix Released Status in Ubuntu Shorts App: Fix Committed Status in Ubuntu Weather App: Fix Released Status in Weather: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in calendar-app package in Ubuntu: Confirmed Status in camera-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Committed Status in gallery-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Committed Status in music-app package in Ubuntu: Confirmed Status in reminders-app package in Ubuntu: Fix Committed Status in ubuntu-clock-app package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Status in ubuntu-weather-app package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: The migration to 1.3 needs to happen in a coordinated way, so that shell and all apps we care of migrate within the same OTA window to reduce visual inconsistencies to a minimum. This bug is a means to collect all the projects affected and keep tabs on what's happening. NOTES: - The toolkit has the following modules: Ubuntu.Components 1.3 Ubuntu.Components.ListItems 1.3 Ubuntu.Components.Pickers 1.3 Ubuntu.Components.Popups 1.3 Ubuntu.Components.Styles 1.3 Ubuntu.Components.Themes 1.3 Ubuntu.Components.Themes.Ambiance 1.3 Ubuntu.Components.Themes.SuruDark 1.3 - The following modules were not altered recently: Ubuntu.Layouts 1.0 Ubuntu.PerformanceMetrics 1.0 - Theme is now theme (lowercase) - PageHeadStyle now has a "config" property In manifest.json file use: "framework": "ubuntu-sdk-15.04.1-qml" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+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 1582262] Re: calculator problems with Qt 5.6
Do you have any console output while you typing numbers? -- 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/1582262 Title: calculator problems with Qt 5.6 Status in Ubuntu Calculator App: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I suspect this might be UITK problem so filing there too. On xenial (ubuntu-touch/staging/ubuntu) + Qt 5.6 (https://wiki.ubuntu.com/Touch/QtTesting) I'm not seeing any numbers in calculator when typing them. There seem to be other problems too. It seems to work better with Qt 5.5 (stock xenial). Qt 5.6 would be targeted to be used when the switch to xenial is made at some point in the future. More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1582262/+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 1333522] Re: add README file
** Changed in: messaging-app (Ubuntu) Status: In Progress => Confirmed ** Changed in: messaging-app (Ubuntu) Assignee: Bartosz Kosiorek (gang65) => (unassigned) -- 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/1333522 Title: add README file Status in messaging-app package in Ubuntu: Confirmed Bug description: The project needs a README with at least: - what the project is - how to build it - how to test it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1333522/+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 1413611] Re: [dialer] Speaker button with "x" is confusing
** Changed in: dialer-app (Ubuntu) Status: In Progress => Confirmed ** Changed in: dialer-app (Ubuntu) Assignee: Bartosz Kosiorek (gang65) => (unassigned) -- 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/1413611 Title: [dialer] Speaker button with "x" is confusing Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: Confirmed Bug description: on active call screen, the icon used to enable the phone speaker is a speaker icon with a "x", that give me the false idea that I will make the call mute if I click on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1413611/+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 1350687] Re: Add content to the README file
** Changed in: ubuntu-system-settings (Ubuntu) Status: In Progress => Confirmed ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: Bartosz Kosiorek (gang65) => (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/1350687 Title: Add content to the README file Status in ubuntu-keyboard: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: The readme file should include at least instructions to: - build the project - run the project - run the tests The current README file is almost empty, which makes it hard for new people to collaborate with this project. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1350687/+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 1492637] Re: Reduce file size of the background image, to improve performance
** Changed in: dialer-app (Ubuntu) Status: In Progress => Invalid -- 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/1492637 Title: Reduce file size of the background image, to improve performance Status in dialer-app package in Ubuntu: Invalid Bug description: Current file size of the background image is huge (about 800kB). It is located in: src/qml/assets/dialer_background_f...@27.png Big size of background image is impacting performance,. I think dialer app should run as fast as possible. That's why I would like to propose reduce image size by using tools like: https://tinypng.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1492637/+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: dialer-app Status: In Progress => Confirmed ** Changed in: dialer-app Assignee: Bartosz Kosiorek (gang65) => (unassigned) ** Changed in: messaging-app Status: In Progress => Confirmed ** Changed in: messaging-app Assignee: Bartosz Kosiorek (gang65) => (unassigned) -- 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 dialer-app: Confirmed Status in messaging-app: Confirmed Status in scope-aggregator: New 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: Fix Released Status in dialer-app package in Ubuntu: Confirmed Status in messaging-app package in Ubuntu: Fix Released Status in ubuntu-clock-app package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released 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 1468799] Re: Too many keys in Polish keyboard
** Changed in: ubuntu-keyboard (Ubuntu) Status: In Progress => Confirmed ** Changed in: ubuntu-keyboard (Ubuntu) Assignee: Bartosz Kosiorek (gang65) => (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/1468799 Title: Too many keys in Polish keyboard Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: For Polish keyboard, to standard QWERTY keyboard the new column with Polish letters was added. It is not optimal because: 1. Adding additional key column, takes space, and for small devices (BQ E4.5) it is hard to use 2. For Polish language there are 9 diactric signs, (ą, ć, ę, ł, ń, ó, ś, ź, ż) but only 3 is available as separate keys 3. In Poland most common used is "Polish Programmer" keyboard (it is also used on Android phone). The diactric sign are available with SHIFT modifier (Example: SHIFT+a = ą, SHIFT+c = ć etc.) Proposal: To improve UX of Polish keyboard, I would like propose to remove Polish keys and use "Polish Programmer" style (with SHIFT modifier). With that solution it will be much easier typying on Polish keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1468799/+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 1475223] Re: Crash during Clock application start on Desktop
@Marcus Please create separate bug report for that crash, and attach logs. Here you have instruction how to gather logs: http://askubuntu.com/questions/548504/ubuntu-sdk-how-can-i-see-error-logs-for-my-ubuntu-touch-app -- 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/1475223 Title: Crash during Clock application start on Desktop Status in Ubuntu Clock App: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Statistically once per 8 Clock runs, the application is crashing with following BackTrace: #0 0x754539fc in g_type_check_instance (type_instance=type_instance@entry=0xf1a0b0) at /build/buildd/glib2.0-2.44.1/./gobject/gtype.c:4136 #1 0x754496fe in g_signal_emit_valist (instance=0xf1a0b0, signal_id=289, detail=0, var_args=var_args@entry=0x7fffd250) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3090 #2 0x7544a8ff in g_signal_emit (instance=, signal_id=, detail=) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361 #3 0x7fffbe19e271 in () at /usr/lib/x86_64-linux-gnu/libgeoclue.so.0 #4 0x7fffdfb0ef3c in marshal_dbus_message_to_g_marshaller (closure=0x1520db0, return_value=0x0, n_param_values=, param_values=, invocation_hint=0x7fffd530, marshal_data=0x0) at dbus-gproxy.c:1736 #8 0x7544a8ff in (instance=instance@entry=0xf0f780, signal_id=, detail=) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361 #5 0x754302d5 in g_closure_invoke (closure=0x1520db0, return_value=0x0, n_param_values=3, param_values=0x7fffd590, invocation_hint=0x7fffd530) at /build/buildd/glib2.0-2.44.1/./gobject/gclosure.c:768 #6 0x7544203c in signal_emit_unlocked_R (node=node@entry=0x151e740, detail=detail@entry=1533, instance=instance@entry=0xf0f780, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd590) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3549 #7 0x7544a698 in g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fffd740) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3305 #9 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (message=0x5307c0, proxy=0xf0f780 [DBusGProxy]) at dbus-gproxy.c:1789 #10 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (connection=, message=0x5307c0, user_data=0xf1f540) at dbus-gproxy.c:1356 #11 0x7fffec3e21d1 in dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #12 0x7fffdfb095d5 in message_queue_dispatch (source=, callback=, user_data=) at dbus-gmain.c:90 #13 0x7515ac3d in g_main_context_dispatch (context=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3122 #14 0x7515ac3d in g_main_context_dispatch (context=context@entry=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #15 0x7515af20 in g_main_context_iterate (context=context@entry=0x7fffe40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808 ---Type to continue, or q to quit--- #16 0x7515afcc in g_main_context_iteration (context=0x7fffe40016f0, may_block=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #17 0x767bcc57 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x767613e2 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7676902c in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00404098 in () #21 0x75ac1a40 in __libc_start_main (main= 0x4037d0, argc=4, argv=0x7fffdf38, init=, fini=, rtld_fini=, stack_end=0x7fffdf28) at libc-start.c:289 #22 0x004058b9 in () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+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 1590501] Re: [bq E] [OTA11] Snoozed alarm keeps ringing after being deleted
** Description changed: So, this is what happenes: 1) Set an alarm 2) When it goes on, press snooze 3) Delete the alarm 4) after the 10 minutes from the original time, it rings again + + + It looks also strange that even if alarm is Snoozed then it looks like to be turned off. ** Changed in: ubuntu-clock-app Importance: Undecided => Medium ** Changed in: ubuntu-clock-app Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1590501 Title: [bq E] [OTA11] Snoozed alarm keeps ringing after being deleted Status in Ubuntu Clock App: Triaged Status in indicator-datetime package in Ubuntu: New Bug description: So, this is what happenes: 1) Set an alarm 2) When it goes on, press snooze 3) Delete the alarm 4) after the 10 minutes from the original time, it rings again It looks also strange that even if alarm is Snoozed then it looks like to be turned off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1590501/+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 1489784] Re: No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10
** Changed in: canonical-devices-system-image Status: In Progress => Confirmed ** Changed in: canonical-devices-system-image Assignee: Sturm Flut (sturmflut) => (unassigned) ** Description changed: - Device Aquaris BQ45 as a buitin hardware FM tuner. + Device Aquaris BQ e45, e5, m10 as a buitin hardware FM tuner. On "factory" mode this device works. The device does not seem known by the kernel and there is no API to develop an FM radio application. The C code for the FM chip: https://github.com/Sturmflut/mtkfmcli Still missing Audio part. - Some more details from mailing list: We discussed this topic lengthily on the list some time ago :) It's not like we don't want to support FM radio, but the lack of a common Android HAL for FM radio access would force us to maintain an FM radio abstraction ourselves (more on that below). In addition, most of the device-specific radio apps require elevated privileges to run as they directly access the FM radio HW (not multiplexed by a system service). > For some reason Android doesn't have an FM radio API and leaves it up to > the manufacturers to come up with something. I've looked at several > devices, among them the bq Aquaris E4.5, and every SoC manufacturer > seems to have a different opinion on how to do it. > > Some ship no FM radio at all. > > Some seem to ship drivers for the Linux V4L subsystem. > > MediaTek (Aquaris E4.5 and E5) decided to implement custom kernel > drivers with a custom character device (/dev/fm) and custom ioctl > commands. There seem to be userspace libraries (libfm*) including a JNI > wrapper in /system/lib of the Android container on our Ubuntu phones. > > Because there is no standard API, there are no generic FM radio apps for > Android, and pretty much every manufacturer ships a custom app for his > own SoC(s) and/or device(s). > > > I'll try to come up with a piece of C code for the command line that can > at least initialize and tune the FM radio on the Aquaris E4.5 and E5. > The long-term goal could be to turn this into plugins for an extended > media-hub. > If you are interested in helping to enable the functionality, the correct chain for integrating the feature would be: [1.] Add a (potentially limited) API to lp:platform-api, that exposes a simple common C interface to the Ubuntu side. [2.] Provide an implementation of the API in platform-api/android (see http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/files/head:/android/) [2.1] Provide a dummy fallback implementation for devices that do not support FM radio of any kind. [3.] Expose the respective hardware functionality to media-hub. Multiple ways are possible, but we would need to significantly adjust the interfaces to support fm radio semantics (switching stations, rds, automatic scans etc.) [4.] Adjust Qt's radio abstraction and come up with a Ubuntu Touch specific backend implementation, that either: [4.1] Leverages the API in [1.] directly (would require any app to have special privileges in accessing the system). [4.2] Leverages the API in [3.] (which is the clean way of integration FM radio support). For starters, [1.], [2.], [2.1] and [4.1] should be good enough to get started. Cheers, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1489784 Title: No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10 Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in qtmultimedia package in Ubuntu: Confirmed Bug description: Device Aquaris BQ e45, e5, m10 as a buitin hardware FM tuner. On "factory" mode this device works. The device does not seem known by the kernel and there is no API to develop an FM radio application. The C code for the FM chip: https://github.com/Sturmflut/mtkfmcli Still missing Audio part. Some more details from mailing list: We discussed this topic lengthily on the list some time ago :) It's not like we don't want to support FM radio, but the lack of a common Android HAL for FM radio access would force us to maintain an FM radio abstraction ourselves (more on that below). In addition, most of the device-specific radio apps require elevated privileges to run as they directly access the FM radio HW (not multiplexed by a system service). > For some reason Android doesn't have an FM radio API and leaves it up to > the manufacturers to come up with something. I've looked at several > devices, among them the bq Aquaris E4.5, and every SoC manufacturer > seems to have a different opinion on how to do it. > > Some ship no FM radio at all. > > Some seem to ship drivers for the Linux V4L
[Touch-packages] [Bug 1489784] Re: No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10
** Summary changed: - No access to the FM tuner/radio on Meizu MX4, Aquaris Bq e4.5, e5 and m10 + No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1489784 Title: No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10 Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in qtmultimedia package in Ubuntu: Confirmed Bug description: Device Aquaris BQ45 as a buitin hardware FM tuner. On "factory" mode this device works. The device does not seem known by the kernel and there is no API to develop an FM radio application. The C code for the FM chip: https://github.com/Sturmflut/mtkfmcli Still missing Audio part. Some more details from mailing list: We discussed this topic lengthily on the list some time ago :) It's not like we don't want to support FM radio, but the lack of a common Android HAL for FM radio access would force us to maintain an FM radio abstraction ourselves (more on that below). In addition, most of the device-specific radio apps require elevated privileges to run as they directly access the FM radio HW (not multiplexed by a system service). > For some reason Android doesn't have an FM radio API and leaves it up to > the manufacturers to come up with something. I've looked at several > devices, among them the bq Aquaris E4.5, and every SoC manufacturer > seems to have a different opinion on how to do it. > > Some ship no FM radio at all. > > Some seem to ship drivers for the Linux V4L subsystem. > > MediaTek (Aquaris E4.5 and E5) decided to implement custom kernel > drivers with a custom character device (/dev/fm) and custom ioctl > commands. There seem to be userspace libraries (libfm*) including a JNI > wrapper in /system/lib of the Android container on our Ubuntu phones. > > Because there is no standard API, there are no generic FM radio apps for > Android, and pretty much every manufacturer ships a custom app for his > own SoC(s) and/or device(s). > > > I'll try to come up with a piece of C code for the command line that can > at least initialize and tune the FM radio on the Aquaris E4.5 and E5. > The long-term goal could be to turn this into plugins for an extended > media-hub. > If you are interested in helping to enable the functionality, the correct chain for integrating the feature would be: [1.] Add a (potentially limited) API to lp:platform-api, that exposes a simple common C interface to the Ubuntu side. [2.] Provide an implementation of the API in platform-api/android (see http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/files/head:/android/) [2.1] Provide a dummy fallback implementation for devices that do not support FM radio of any kind. [3.] Expose the respective hardware functionality to media-hub. Multiple ways are possible, but we would need to significantly adjust the interfaces to support fm radio semantics (switching stations, rds, automatic scans etc.) [4.] Adjust Qt's radio abstraction and come up with a Ubuntu Touch specific backend implementation, that either: [4.1] Leverages the API in [1.] directly (would require any app to have special privileges in accessing the system). [4.2] Leverages the API in [3.] (which is the clean way of integration FM radio support). For starters, [1.], [2.], [2.1] and [4.1] should be good enough to get started. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489784/+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 1581480] Re: [SRU] New stable release 2.48.2
It is working perfectly for me after install glib-networking from proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1581480 Title: [SRU] New stable release 2.48.2 Status in glib-networking package in Ubuntu: Fix Released Status in glib-networking source package in Xenial: Fix Committed Bug description: [ Description ] Upstream have released a new bugfix release. [ Changes ] From NEWS: * gnutls: Fixed an infinite loop if a server sent two identical copies of its CA certificate [#765317, Carlos Garcia Campos] [ QA, testing, regression potential ] Under the GNOME MRE, you can believe all bugs upstream says are fixed are really fixed. Just test the system and make sure there are no regressions (e.g. look at errors.ubuntu.com). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1581480/+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 1581439] Re: [SRU] New stable release 2.48.1
It is working perfectly for me after install glib2.0 from proposed. I tested it for several days. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1581439 Title: [SRU] New stable release 2.48.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: Fix Committed Bug description: [ Description ] Upstream have released a new bugfix release. [ Changes ] From NEWS: Bugs fixed: 731988 glocalfile: Avoid a potential NULL pointer dereference 747107 GVariant varargs documentation: g_variant_get() example 747478 g_system_thread_set_name() is not implemented for gthread-win32 748474 g_get_language_names() is not thread-safe 748530 gthread: W32 implementation of g_get_num_processors() has lame fallback 748806 GVariant: Better introduction to the concepts and its uses 749606 tests: always remove app.desktop 758174 Fix documentation typos 758738 Usage of GType properties causes crashes due to gulong/gpointer mismatch 762994 Race condition in GIO/AppFileChooser crashes Firefox/Gtk3 763379 codegen: Add support for g_autoptr to gdbus-codegen–generated objects 763821 build: Also dist Systemtap files always for gobject/ 764092 gstrfuncs: Document the behaviour of g_strjoinv() 764574 build: Fix all statfs() tests failing 764575 tests: Fix compilation errors due to Y2K format problems 764685 GApplication documentation about handling command-line options is confusing 764754 '-' in application id: unbreak bus activation and notifications 765959 socket: set fd field to -1 after closing socket 765990 Visual Studio: Define inline only when necessary Translations updated: Basque language Catalan Vietnamese zh_CN [ QA, testing, regression potential ] Under the GNOME MRE, you can believe all bugs upstream says are fixed are really fixed. Just test the system and make sure there are no regressions (e.g. look at errors.ubuntu.com). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1581439/+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 1581480] Re: [SRU] New stable release 2.48.2
** Changed in: glib-networking (Ubuntu Xenial) Assignee: (unassigned) => Bartosz Kosiorek (gang65) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1581480 Title: [SRU] New stable release 2.48.2 Status in glib-networking package in Ubuntu: Fix Released Status in glib-networking source package in Xenial: Fix Committed Bug description: [ Description ] Upstream have released a new bugfix release. [ Changes ] From NEWS: * gnutls: Fixed an infinite loop if a server sent two identical copies of its CA certificate [#765317, Carlos Garcia Campos] [ QA, testing, regression potential ] Under the GNOME MRE, you can believe all bugs upstream says are fixed are really fixed. Just test the system and make sure there are no regressions (e.g. look at errors.ubuntu.com). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1581480/+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 1407921] Re: Indicator should give feedback when location-service is in use by apps
** Changed in: ubuntu-themes Status: In Progress => Confirmed ** Changed in: ubuntu-themes Assignee: Bartosz Kosiorek (gang65) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1407921 Title: Indicator should give feedback when location-service is in use by apps Status in Canonical System Image: In Progress Status in Indicator Location: New Status in Ubuntu theme: Confirmed Status in Ubuntu UX: Triaged Status in indicator-location package in Ubuntu: In Progress Bug description: The only information the location indicator icon conveys currently is whether location detection is enabled at all, when more data could be interesting. Especially acquiring a GPS lock is often interesting, as this greatly impacts the location accuracy. Maybe the location icon should be dimmed when nothing is using it and blink when GPS lock is being acquired, bright when the lock is fine? The current spec is @ https://wiki.ubuntu.com/Location == Bug revision by charlesk 2016-01-24: The Location spec has been revised in this regard. The new text reads: > The indicator should appear in the status bar > whenever an app has accessed your location in > the past five minutes. It should list all apps > that have accessed your location in the past > five minutes, most recent first. Choosing any > app should switch to that app, so that you may > control whichever functions in that app are > accessing location. “Location Settings…” should > navigate to the “Location” screen of System > Settings. This bug is about the first part of that spec -- making the indicator visible when it's active -- and is (currently) blocked on location- service bug #1536774. The recent apps list component of the spec is covered in sibling bug #1235300. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407921/+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 1575109] Re: Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation
** Bug watch added: Debian Bug tracker #808181 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808181 ** Also affects: ubuntu-release-upgrader (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808181 Importance: Unknown Status: Unknown ** Also affects: libc6-i386 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808181 Importance: Unknown Status: Unknown ** No longer affects: ubuntu-release-upgrader (Debian) ** Summary changed: - Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation + Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation (0x2a) in section `.init' ** Also affects: binutils Importance: Undecided Status: New ** No longer affects: libc6-i386 (Debian) ** Also affects: binutils (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808181 Importance: Unknown Status: Unknown ** Also affects: binutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1575109 Title: Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation (0x2a) in section `.init' Status in binutils: New Status in binutils package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Status in binutils package in Debian: Unknown Bug description: Running sa-compile (may take a long time) /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o: unrecognized relocation (0x2a) in section `.init' /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status make: *** [blib/arch/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so] Error 1 command 'make >>/tmp/.spamassassin6654c6JaRRtmp/log' failed: exit 2 dpkg: error processing package sa-compile (--configure): subprocess installed post-installation script returned error exit status 25 Errors were encountered while processing: libgmp-dev:amd64 systemd sa-compile ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:15.10.14.4 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Apr 26 11:38:01 2016 InstallationDate: Installed on 2012-02-04 (1542 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-26 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1575109/+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 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" Status in accountsservice: Confirmed Status in accountsservice package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Invalid Status in policykit-1-gnome package in Ubuntu: Invalid Status in accountsservice source package in Xenial: Fix Committed Bug description: * Impact Sometimes useless "Authentication is required to change your own user data" prompts are displayed * Test case $ ssh -X localhost $ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 & $ dbus-send --system --print-reply=literal --dest=org.freedesktop.Accounts /org/freedesktop/Accounts/User1001 org.freedesktop.Accounts.User.SetXHasMessages boolean:true that shouldn't trigger a prompt * Regression potential it allows the change to be done without prompting in more cases, shouldn't have an impact on cases which were already working -- Every few days a dialog pops up saying "Authentication is required to change your own user data" with an entry field for a password. If I type my user's password the dialog will reappear with an empty entry field. If I click on the cross to close the window many times it will be gone, but reappear a few days later. I don't know what this window is for and it makes no difference whether I close it or leave it. I don't use the gnome keyring. This started with Ubuntu 15.04 or maybe with an earlier release, and is still there in Ubuntu 15.10, also on machines I did a fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1512002/+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 1576726] Re: [SRU]network-manager
After install network-manager on Ubuntu 16.04 everything is working correctly for me: $ apt-cache policy network-manager network-manager: Zainstalowana: 1.2.0-0ubuntu0.16.04.1 Kandydująca: 1.2.0-0ubuntu0.16.04.1 Tabela wersji: *** 1.2.0-0ubuntu0.16.04.1 100 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://pl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576726 Title: [SRU]network-manager Status in network-manager package in Ubuntu: Fix Committed Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager-applet source package in Xenial: Fix Committed Status in network-manager-openconnect source package in Xenial: Confirmed Bug description: [Impact] Xenial was released with upstream beta2 version of network-manager to keep in time for the release schedule, and upstream stable release has been made so it's time to update to it. [Testcase] After upgrading the package, user should still be able to connect to networks like Ethernet, Wi-Fi and VPNs. [Regression Potential] Potential of causing regression is relatively small because there is not big changes made during beta2 -> stable process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+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 1327412] Re: Delay during PXE Boot, IP-Config gives up
** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Committed Status in klibc source package in Wily: Fix Committed Status in klibc source package in Xenial: Fix Committed Status in klibc package in Debian: New Bug description: [Impact] PXE booting users with live images or other minimal setups using klibc-utils. [Test case] Attempt to PXE boot using Ubuntu live images; see below for details. [Regression potential] This forces the yiaddr (client requested/current IP) to be set to 0 when sending DHCP messages; currently the messages are DHCPREQUEST and DHCPDISCOVER, which should typically only happen when there is no IP set on the device and it is otherwise unable to receive unicast (on account of not being configured). Should there be a need to send other messages which would require setting the yiaddr value to the current configured IP address, a naive change would break. The yiaddr variable would need to be adjusted to pull value from a new location, or initialized directly by the callers to dhcp_send() where the business logic would reside. --- Attempting to PXE boot both the 12.04.3 and 14.04 Live images. PXE boot works normally (PXE Menu, select desired image, image begins loading), then the boot process hangs while IP-Config attempts to get an IP address: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 2 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 3 secs - giving up These lines appear very quickly (5 seconds has NOT elapsed), after about a minute, we get this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 4 secs - giving up Some time later, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 6 secs - giving up Until finally, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 9 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.25.11.31 IP-Config: eth0 complete (dhcp from 172.25.10.20): (snip) While watching the DHCP server logs, Ubuntu is either not sending a DHCP Discover at times, or is not replying back with a DHCPRequest during these sessions, presumably ignoring an response from the DHCP server. From the initial booting of the system via PXE, to when Ubuntu finally shows the desktop, almost 12 minutes will have elapsed. I am seeing this same behavior on both 12.04.3 and 14.04. After finding a number of similar erros via Google and no real resolution, I have opened this bug. The system experiencing this issue has multiple ethernet interfaces (actual HW, not a VM), some Google found solutions suggest hard coding DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't acceptable as a system attempting to PXE boot may be using an alternate port for the network. I have found what looks to be a very similar bug filed for Debian, #584583, which also contains a patch for this issue (under Debian). I have no problems in PXE booting to various Windows, RedHat, Centos, or Fedora OSs. Ubuntu is the only Live OS that I'm attempting to boot at present. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Jun 6 20:22:09 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1543484] Re: date/time picker should rescale for a larger display
** Changed in: ubuntu-clock-app Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1543484 Title: date/time picker should rescale for a larger display Status in Ubuntu Clock App: Incomplete Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Picker is too small on large displays (such as tablets) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1543484/+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 1459809] Re: [greeter infographic] Remove entries with zero count
** Changed in: libusermetrics (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1459809 Title: [greeter infographic] Remove entries with zero count Status in Ubuntu UX: Won't Fix Status in libusermetrics package in Ubuntu: Invalid Bug description: I would like to have a setting so the phone only displays entries with at least one occurrence. I know that having "0" is information too, but I don’t need my phone to tell my I haven’t gotten any sms/taken no photos/played no songs today. - Design comment - 04/08/2015 It can't be fixed as a single bug. The desired resolution and specs will be updated as soon as they are available. https://canonical.leankit.com/Boards/View/109386535/113890502 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1459809/+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 1390469] Re: [messaging-app] can't receive vcards via SMS
** Changed in: messaging-app (Ubuntu) Status: Confirmed => Incomplete -- 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/1390469 Title: [messaging-app] can't receive vcards via SMS Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Incomplete Bug description: I tried to send a vcard via SMS from another phone to the Ubuntu Phone. It seems to get lost. No indication or anything shows up. --UX comment Sending and receiving v-cards should be possible through all available channels, e.g. IM, SMS/MMS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1390469/+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 1520551] Re: Profiling from Ubuntu SDK IDE is working only if "networking", policy group is enabled in apparmor
Should I take /var/log/syslog logs from PC or a phone ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1520551 Title: Profiling from Ubuntu SDK IDE is working only if "networking", policy group is enabled in apparmor Status in Ubuntu SDK IDE: New Status in apparmor-easyprof-ubuntu package in Ubuntu: Incomplete Bug description: Profiling from Ubuntu SDK IDE is working only if "networking", policy group is enabled in apparmor. It could be reproduced with project: https://code.launchpad.net/ubuntu-calculator-app Only after apply following patch, it is possible to run profiler: http://pastebin.ubuntu.com/13525452/ "policy_groups": [ "networking" ], To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-sdk-ide/+bug/1520551/+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 1489784] Re: No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10
** Summary changed: - No access to the FM tuner/radio on Aquaris Bq e4.5 + No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1489784 Title: No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10 Status in Canonical System Image: In Progress Status in media-hub package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in qtmultimedia package in Ubuntu: New Bug description: Device Aquaris BQ45 as a buitin hardware FM tuner. On "factory" mode this device works. The device does not seem known by the kernel and there is no API to develop an FM radio application. Some more details from mailing list: We discussed this topic lengthily on the list some time ago :) It's not like we don't want to support FM radio, but the lack of a common Android HAL for FM radio access would force us to maintain an FM radio abstraction ourselves (more on that below). In addition, most of the device-specific radio apps require elevated privileges to run as they directly access the FM radio HW (not multiplexed by a system service). > For some reason Android doesn't have an FM radio API and leaves it up to > the manufacturers to come up with something. I've looked at several > devices, among them the bq Aquaris E4.5, and every SoC manufacturer > seems to have a different opinion on how to do it. > > Some ship no FM radio at all. > > Some seem to ship drivers for the Linux V4L subsystem. > > MediaTek (Aquaris E4.5 and E5) decided to implement custom kernel > drivers with a custom character device (/dev/fm) and custom ioctl > commands. There seem to be userspace libraries (libfm*) including a JNI > wrapper in /system/lib of the Android container on our Ubuntu phones. > > Because there is no standard API, there are no generic FM radio apps for > Android, and pretty much every manufacturer ships a custom app for his > own SoC(s) and/or device(s). > > > I'll try to come up with a piece of C code for the command line that can > at least initialize and tune the FM radio on the Aquaris E4.5 and E5. > The long-term goal could be to turn this into plugins for an extended > media-hub. > If you are interested in helping to enable the functionality, the correct chain for integrating the feature would be: [1.] Add a (potentially limited) API to lp:platform-api, that exposes a simple common C interface to the Ubuntu side. [2.] Provide an implementation of the API in platform-api/android (see http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/files/head:/android/) [2.1] Provide a dummy fallback implementation for devices that do not support FM radio of any kind. [3.] Expose the respective hardware functionality to media-hub. Multiple ways are possible, but we would need to significantly adjust the interfaces to support fm radio semantics (switching stations, rds, automatic scans etc.) [4.] Adjust Qt's radio abstraction and come up with a Ubuntu Touch specific backend implementation, that either: [4.1] Leverages the API in [1.] directly (would require any app to have special privileges in accessing the system). [4.2] Leverages the API in [3.] (which is the clean way of integration FM radio support). For starters, [1.], [2.], [2.1] and [4.1] should be good enough to get started. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489784/+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 1489784] Re: No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10
** Description changed: Device Aquaris BQ45 as a buitin hardware FM tuner. On "factory" mode this device works. The device does not seem known by the kernel and there is no API to develop an FM radio application. + + The C code for the FM chip: + https://github.com/Sturmflut/mtkfmcli + Still missing Audio part. + Some more details from mailing list: We discussed this topic lengthily on the list some time ago :) It's not like we don't want to support FM radio, but the lack of a common Android HAL for FM radio access would force us to maintain an FM radio abstraction ourselves (more on that below). In addition, most of the device-specific radio apps require elevated privileges to run as they directly access the FM radio HW (not multiplexed by a system service). > For some reason Android doesn't have an FM radio API and leaves it up to > the manufacturers to come up with something. I've looked at several > devices, among them the bq Aquaris E4.5, and every SoC manufacturer > seems to have a different opinion on how to do it. > > Some ship no FM radio at all. > > Some seem to ship drivers for the Linux V4L subsystem. > > MediaTek (Aquaris E4.5 and E5) decided to implement custom kernel > drivers with a custom character device (/dev/fm) and custom ioctl > commands. There seem to be userspace libraries (libfm*) including a JNI > wrapper in /system/lib of the Android container on our Ubuntu phones. > > Because there is no standard API, there are no generic FM radio apps for > Android, and pretty much every manufacturer ships a custom app for his > own SoC(s) and/or device(s). > > > I'll try to come up with a piece of C code for the command line that can > at least initialize and tune the FM radio on the Aquaris E4.5 and E5. > The long-term goal could be to turn this into plugins for an extended > media-hub. > If you are interested in helping to enable the functionality, the correct chain for integrating the feature would be: [1.] Add a (potentially limited) API to lp:platform-api, that exposes a simple common C interface to the Ubuntu side. [2.] Provide an implementation of the API in platform-api/android (see http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/files/head:/android/) [2.1] Provide a dummy fallback implementation for devices that do not support FM radio of any kind. [3.] Expose the respective hardware functionality to media-hub. Multiple ways are possible, but we would need to significantly adjust the interfaces to support fm radio semantics (switching stations, rds, automatic scans etc.) [4.] Adjust Qt's radio abstraction and come up with a Ubuntu Touch specific backend implementation, that either: [4.1] Leverages the API in [1.] directly (would require any app to have special privileges in accessing the system). [4.2] Leverages the API in [3.] (which is the clean way of integration FM radio support). For starters, [1.], [2.], [2.1] and [4.1] should be good enough to get started. Cheers, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1489784 Title: No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10 Status in Canonical System Image: In Progress Status in media-hub package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in qtmultimedia package in Ubuntu: New Bug description: Device Aquaris BQ45 as a buitin hardware FM tuner. On "factory" mode this device works. The device does not seem known by the kernel and there is no API to develop an FM radio application. The C code for the FM chip: https://github.com/Sturmflut/mtkfmcli Still missing Audio part. Some more details from mailing list: We discussed this topic lengthily on the list some time ago :) It's not like we don't want to support FM radio, but the lack of a common Android HAL for FM radio access would force us to maintain an FM radio abstraction ourselves (more on that below). In addition, most of the device-specific radio apps require elevated privileges to run as they directly access the FM radio HW (not multiplexed by a system service). > For some reason Android doesn't have an FM radio API and leaves it up to > the manufacturers to come up with something. I've looked at several > devices, among them the bq Aquaris E4.5, and every SoC manufacturer > seems to have a different opinion on how to do it. > > Some ship no FM radio at all. > > Some seem to ship drivers for the Linux V4L subsystem. > > MediaTek (Aquaris E4.5 and E5) decided to implement custom kernel > drivers with a custom character device (/dev/fm) and custom ioctl > commands. There seem to be userspace libraries (libfm*) including a JNI > wrapper in /system/lib of the
[Touch-packages] [Bug 1532895] Re: Messages with a trailing CR are not displayed properly in the main list
** Changed in: messaging-app (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1532895 Title: Messages with a trailing CR are not displayed properly in the main list Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: Normally a long message is truncated and "..." is shown to indicate its longer than the box. When the message ends with a CR it is not truncated and the text extends to the end f the screen, and is shown underneath the new message count. Not reproducible on krillin, only arale To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532895/+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 1518344] Re: "Swipe to reveal actions" label needs more space.
** Changed in: messaging-app (Ubuntu) Status: Confirmed => In Progress -- 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/1518344 Title: "Swipe to reveal actions" label needs more space. Status in Canonical System Image: Triaged Status in messaging-app package in Ubuntu: In Progress Bug description: Hi! I translated the following string to Hungarian: "Swipe to reveal actions" But it needs more space (see attached screenshot). Additional info: In the Phone app the same translation looks okay. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518344/+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 1492637] Re: Reduce file size of the background image, to improve performance
** Changed in: dialer-app (Ubuntu) Status: Confirmed => In Progress ** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) => Bartosz Kosiorek (gang65) -- 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/1492637 Title: Reduce file size of the background image, to improve performance Status in dialer-app package in Ubuntu: In Progress Bug description: Current file size of the background image is huge (about 800kB). It is located in: src/qml/assets/dialer_background_f...@27.png Big size of background image is impacting performance,. I think dialer app should run as fast as possible. That's why I would like to propose reduce image size by using tools like: https://tinypng.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1492637/+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
** Description changed: From settings in telephony suite, when tap return button, it goes back to system settings instead of phone/one of the telephony suite + + This is general problem also with: + ubuntu_clock + messaging-indicator + datetime-indicator + location-indicator + messaging-app + + Proposal: + When the ubuntu-system-settings application is executed from external application (listed above), then instead of "Back" button, System-settings should display "Close" button. ** Also affects: ubuntu-system-settings Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-clock-app Importance: Undecided Status: New ** Also affects: indicator-datetime Importance: Undecided Status: New ** Summary changed: - Phone app -> Settings -> Back doesn't return to Phone app + "External" app -> System Settings -> Back doesn't return to "External" app ** Summary changed: - "External" app -> System Settings -> Back doesn't return to "External" app + "External" app setting -> System Settings -> Back doesn't return to "External" app ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Description changed: From settings in telephony suite, when tap return button, it goes back to system settings instead of phone/one of the telephony suite - This is general problem also with: - ubuntu_clock - messaging-indicator - datetime-indicator - location-indicator - messaging-app + Steps to reproduce: + 1. Open Ubuntu Clock Application + 2. Click Gear button on top right corner + 3. Click "Change time and date" + 4. "Time & Date" System settings is revealed + + Current + 4. On top left corner, the "Back" button is displayed. Pressing it return to General System settings. + + Expected: + 4. On top left corner, the "Close" button is displayed. Pressing it close system-settings application and return to Ubuntu-Clock-Application. + Proposal: When the ubuntu-system-settings application is executed from external application (listed above), then instead of "Back" button, System-settings should display "Close" button. ** Description changed: From settings in telephony suite, when tap return button, it goes back to system settings instead of phone/one of the telephony suite Steps to reproduce: 1. Open Ubuntu Clock Application 2. Click Gear button on top right corner 3. Click "Change time and date" 4. "Time & Date" System settings is revealed Current 4. On top left corner, the "Back" button is displayed. Pressing it return to General System settings. Expected: 4. On top left corner, the "Close" button is displayed. Pressing it close system-settings application and return to Ubuntu-Clock-Application. - Proposal: - When the ubuntu-system-settings application is executed from external application (listed above), then instead of "Back" button, System-settings should display "Close" button. + When the ubuntu-system-settings application is executed from external application, then instead of "Back" button, System-settings should display "Close" button. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1482551 Title: "External" app setting -> System Settings -> Back doesn't return to "External" app Status in Indicator Date and Time: New Status in Ubuntu Clock App: New Status in ubuntu-system-settings: New Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: Triaged Status in indicator-messages package in Ubuntu: New Status in indicator-network package in Ubuntu: New Status in indicator-power package in Ubuntu: New Status in indicator-sound package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New 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 Steps to reproduce: 1. Open Ubuntu Clock Application 2. Click Gear button on top right corner 3. Click "Change time and date" 4. "Time & Date" System settings is revealed Current 4. On top left corner, the "Back" button is displayed. Pressing it return to General System settings. Expected: 4. On top left corner, the "Close" button is displayed. Pressing it close system-settings application and return to Ubuntu-Clock-Application. Proposal: When the ubuntu-system-settings application is executed from external application, then instead of "Back" button, System-settings should display "Close"
[Touch-packages] [Bug 1407921] Re: Indicator should give feedback when location-service is in use by apps
Hi Charles. I think still this icon make sense to comply resolving bug: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1536774 GPS Disabled: No icon displayed GPS Enabled, GPS active: Display https://launchpadlibrarian.net/210299143/gps-enabled-connected.svg GPS Enabled, GPS inactive: Display https://launchpadlibrarian.net/210299156/gps-enabled-not-connected.svg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1407921 Title: Indicator should give feedback when location-service is in use by apps Status in Indicator Location: New Status in Ubuntu theme: In Progress Status in Ubuntu UX: Triaged Status in indicator-location package in Ubuntu: In Progress Bug description: The only information the location indicator icon conveys currently is whether location detection is enabled at all, when more data could be interesting. Especially acquiring a GPS lock is often interesting, as this greatly impacts the location accuracy. Maybe the location icon should be dimmed when nothing is using it and blink when GPS lock is being acquired, bright when the lock is fine? The current spec is @ https://wiki.ubuntu.com/Location == Bug revision by charlesk 2016-01-24: The Location spec has been revised in this regard. The new text reads: > The indicator should appear in the status bar > whenever an app has accessed your location in > the past five minutes. It should list all apps > that have accessed your location in the past > five minutes, most recent first. Choosing any > app should switch to that app, so that you may > control whichever functions in that app are > accessing location. “Location Settings…” should > navigate to the “Location” screen of System > Settings. This bug is about the first part of that spec -- making the indicator visible when it's active -- and is (currently) blocked on location- service bug #1536774. The recent apps list component of the spec is covered in sibling bug #1235300. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1407921/+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 1536774] Re: Service state should distinguish between enabled/disabled and active/inactive
** Description changed: Service state should distinguish between enabled/disabled and active/inactive + + To resolve that issue I would like to propose new icons which are added in bug report: + https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1407921 + + + GPS Disabled: No icon displayed + GPS Enabled, GPS active: Display https://launchpadlibrarian.net/210299143/gps-enabled-connected.svg + GPS Enabled, GPS inactive: Display https://launchpadlibrarian.net/210299156/gps-enabled-not-connected.svg ** Description changed: Service state should distinguish between enabled/disabled and active/inactive - To resolve that issue I would like to propose new icons which are added in bug report: + To make usage of that solution I would like to propose new icons which are added in bug report: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1407921 - GPS Disabled: No icon displayed GPS Enabled, GPS active: Display https://launchpadlibrarian.net/210299143/gps-enabled-connected.svg GPS Enabled, GPS inactive: Display https://launchpadlibrarian.net/210299156/gps-enabled-not-connected.svg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1536774 Title: Service state should distinguish between enabled/disabled and active/inactive Status in location-service package in Ubuntu: Confirmed Bug description: Service state should distinguish between enabled/disabled and active/inactive To make usage of that solution I would like to propose new icons which are added in bug report: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1407921 GPS Disabled: No icon displayed GPS Enabled, GPS active: Display https://launchpadlibrarian.net/210299143/gps-enabled-connected.svg GPS Enabled, GPS inactive: Display https://launchpadlibrarian.net/210299156/gps-enabled-not-connected.svg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1536774/+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 1489784] Re: No access to the FM tuner on Aquaris BQ45
Here are some details taken from mailing list:
Good morning dear list,
it's time for the "good news, bad news" part again.
The good news: I managed to attach gdb to the Factory Mode [1] binary,
and with some debugging-symbol-building and gdb-command-writing it's now
starting to get possible to catch every ioctl and semi-automatically
dump the parameters. Those of you who know a bit about debugging may see
the value in a gdb output like this one:
Breakpoint 1, 0xb6f41298 in ioctl () from /system/lib/libc.so
lrwx-- root root 2015-12-16 21:44 25 -> /dev/fm
FM_IOCTL_POWERUP
$5 = {err = 0 '\000', band = 1 '\001', space = 1 '\001', hilo = 0
'\000', freq = 880}
Turns out you only need three ioctl()s to power on and tune the whole FM
chip: FM_IOCTL_POWERUP, FM_IOCTL_MUTE and FM_IOCTL_ANA_SWITCH.
The bad news: We also catched all the ioctls necessary to tell the audio
chip to forward the FM signal to the headphones, and it's 90 (!) calls.
So our problem isn't the FM radio, it actually seems to be the audio
subsystem.
cheers,
Simon
[1]
http://sturmflut.github.io/ubuntu/bq/2015/05/04/hacking-the-bq-part-2-factory-mode/
** Description changed:
Device Aquaris BQ45 as a buitin hardware FM tuner.
On "factory" mode this device works.
The device does not seem known by the kernel and there is no API to
develop an FM radio application.
+
+
+ Some more details:
+
+ > I've been looking at the necessary pieces for FM radio support, and I
+ > hope somebody can correct me, but it looks more complicated than I expected.
+ >
+
+ We discussed this topic lengthily on the list some time ago :) It's
+ not like we don't want to
+ support FM radio, but the lack of a common Android HAL for FM radio
+ access would force us to
+ maintain an FM radio abstraction ourselves (more on that below). In
+ addition, most of the device-specific
+ radio apps require elevated privileges to run as they directly access
+ the FM radio HW (not multiplexed by a system service).
+
+ > For some reason Android doesn't have an FM radio API and leaves it up to
+ > the manufacturers to come up with something. I've looked at several
+ > devices, among them the bq Aquaris E4.5, and every SoC manufacturer
+ > seems to have a different opinion on how to do it.
+ >
+ > Some ship no FM radio at all.
+ >
+ > Some seem to ship drivers for the Linux V4L subsystem.
+ >
+ > MediaTek (Aquaris E4.5 and E5) decided to implement custom kernel
+ > drivers with a custom character device (/dev/fm) and custom ioctl
+ > commands. There seem to be userspace libraries (libfm*) including a JNI
+ > wrapper in /system/lib of the Android container on our Ubuntu phones.
+ >
+ > Because there is no standard API, there are no generic FM radio apps for
+ > Android, and pretty much every manufacturer ships a custom app for his
+ > own SoC(s) and/or device(s).
+ >
+ >
+ > I'll try to come up with a piece of C code for the command line that can
+ > at least initialize and tune the FM radio on the Aquaris E4.5 and E5.
+ > The long-term goal could be to turn this into plugins for an extended
+ > media-hub.
+ >
+
+ If you are interested in helping to enable the functionality, the
+ correct chain for integrating the feature would be:
+
+ [1.] Add a (potentially limited) API to lp:platform-api, that exposes
+ a simple common C interface to the Ubuntu side.
+ [2.] Provide an implementation of the API in platform-api/android (see
+
http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/files/head:/android/)
+ [2.1] Provide a dummy fallback implementation for devices that do not
+ support FM radio of any kind.
+ [3.] Expose the respective hardware functionality to media-hub.
+ Multiple ways are possible, but we would need to significantly adjust
+ the interfaces
+ to support fm radio semantics (switching stations, rds, automatic scans etc.)
+ [4.] Adjust Qt's radio abstraction and come up with a Ubuntu Touch
+ specific backend implementation, that either:
+ [4.1] Leverages the API in [1.] directly (would require any app to
+ have special privileges in accessing the system).
+ [4.2] Leverages the API in [3.] (which is the clean way of
+ integration FM radio support).
+
+ For starters, [1.], [2.], [2.1] and [4.1] should be good enough to get
+ started.
+
+ Cheers,
** Also affects: platform-api (Ubuntu)
Importance: Undecided
Status: New
** Also affects: media-hub (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Device Aquaris BQ45 as a buitin hardware FM tuner.
On "factory" mode this device works.
The device does not seem known by the kernel and there is no API to
develop an FM radio application.
-
- Some more details:
-
- > I've been looking at the necessary pieces for FM radio support, and I
- > hope somebody can correct me, but it looks more complicated than I expected.
- >
+ Some more details from mailing list:
We discussed this topic lengthily on the list some time ago :)
[Touch-packages] [Bug 1420896] Re: FM radio doesn't work
*** This bug is a duplicate of bug 1489784 ***
https://bugs.launchpad.net/bugs/1489784
** This bug has been marked a duplicate of bug 1489784
No access to the FM tuner on Aquaris BQ45
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtmultimedia-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1420896
Title:
FM radio doesn't work
Status in qtmultimedia-opensource-src package in Ubuntu:
Confirmed
Bug description:
We have an API, but, at least, on officially supported BQ Aquaris it
simply doesn't work. Attribute "availability" in Radio {} returns
Radio.Unavailable, but phone has FM module.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmultimedia-opensource-src/+bug/1420896/+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 1489784] Re: No access to the FM tuner on Aquaris BQ45
** Also affects: qtmultimedia (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No access to the FM tuner on Aquaris BQ45 + No access to the FM tuner/radio on Aquaris BQ45 ** Summary changed: - No access to the FM tuner/radio on Aquaris BQ45 + No access to the FM tuner/radio on Aquaris Bq e4.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1489784 Title: No access to the FM tuner/radio on Aquaris Bq e4.5 Status in Canonical System Image: In Progress Status in media-hub package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in qtmultimedia package in Ubuntu: New Bug description: Device Aquaris BQ45 as a buitin hardware FM tuner. On "factory" mode this device works. The device does not seem known by the kernel and there is no API to develop an FM radio application. Some more details from mailing list: We discussed this topic lengthily on the list some time ago :) It's not like we don't want to support FM radio, but the lack of a common Android HAL for FM radio access would force us to maintain an FM radio abstraction ourselves (more on that below). In addition, most of the device-specific radio apps require elevated privileges to run as they directly access the FM radio HW (not multiplexed by a system service). > For some reason Android doesn't have an FM radio API and leaves it up to > the manufacturers to come up with something. I've looked at several > devices, among them the bq Aquaris E4.5, and every SoC manufacturer > seems to have a different opinion on how to do it. > > Some ship no FM radio at all. > > Some seem to ship drivers for the Linux V4L subsystem. > > MediaTek (Aquaris E4.5 and E5) decided to implement custom kernel > drivers with a custom character device (/dev/fm) and custom ioctl > commands. There seem to be userspace libraries (libfm*) including a JNI > wrapper in /system/lib of the Android container on our Ubuntu phones. > > Because there is no standard API, there are no generic FM radio apps for > Android, and pretty much every manufacturer ships a custom app for his > own SoC(s) and/or device(s). > > > I'll try to come up with a piece of C code for the command line that can > at least initialize and tune the FM radio on the Aquaris E4.5 and E5. > The long-term goal could be to turn this into plugins for an extended > media-hub. > If you are interested in helping to enable the functionality, the correct chain for integrating the feature would be: [1.] Add a (potentially limited) API to lp:platform-api, that exposes a simple common C interface to the Ubuntu side. [2.] Provide an implementation of the API in platform-api/android (see http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/files/head:/android/) [2.1] Provide a dummy fallback implementation for devices that do not support FM radio of any kind. [3.] Expose the respective hardware functionality to media-hub. Multiple ways are possible, but we would need to significantly adjust the interfaces to support fm radio semantics (switching stations, rds, automatic scans etc.) [4.] Adjust Qt's radio abstraction and come up with a Ubuntu Touch specific backend implementation, that either: [4.1] Leverages the API in [1.] directly (would require any app to have special privileges in accessing the system). [4.2] Leverages the API in [3.] (which is the clean way of integration FM radio support). For starters, [1.], [2.], [2.1] and [4.1] should be good enough to get started. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489784/+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
** Branch linked: lp:~gang65/messaging-app/messaging-app-chevron-down -- 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 messaging-app: In Progress 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: Fix Released Status in dialer-app package in Ubuntu: Confirmed Status in messaging-app package in Ubuntu: Fix Released 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 1485334] Re: No content to display on send a SMS to yourself.
I'm unable to reproduce this issue on my bq e4.5 device. ** Changed in: messaging-app (Ubuntu) Status: New => Incomplete -- 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/1485334 Title: No content to display on send a SMS to yourself. Status in messaging-app package in Ubuntu: Incomplete Bug description: Test Environment: $ system-image-cli -i current build number: 98 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-08-16 09:38:54 version version: 98 version ubuntu: 20150814 version device: 20150804-7bba081 version custom: 20150814-887-30-30-vivid Reproduce steps: 1.Open the messaging application 2.Send a SMS to yourself Actual result: After step 2: Got this SMS but no content to display and this message that display on information bar can't delete Expected result: Content to display on send a SMS to yourself. Other info:This is not issue for arale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1485334/+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 1413611] Re: [dialer] Speaker button with "x" is confusing
** Changed in: dialer-app (Ubuntu) Status: Confirmed => In Progress ** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) => Bartosz Kosiorek (gang65) -- 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/1413611 Title: [dialer] Speaker button with "x" is confusing Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: In Progress Bug description: on active call screen, the icon used to enable the phone speaker is a speaker icon with a "x", that give me the false idea that I will make the call mute if I click on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1413611/+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 1479076] Re: Does not process %0A line feed symbol
How to reproduce this bug? ** Changed in: messaging-app (Ubuntu) Status: New => Incomplete -- 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/1479076 Title: Does not process %0A line feed symbol Status in messaging-app package in Ubuntu: Incomplete Bug description: Follow up on: https://bugs.launchpad.net/messaging-app/+bug/1382623 The app does not process line feed (%0A) symbol when passed in URL (see bug above for reference). phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 24 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en last update: 2015-07-22 14:36:08 version version: 24 version ubuntu: 20150713 version device: 20150529-8e13c5f version custom: 20150709-814-29-21-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1479076/+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
** Also affects: scope-aggregator 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/1432696 Title: [SDK] Bottom edge header improvement Status in Dekko: Fix Released Status in messaging-app: In Progress Status in scope-aggregator: New 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: Fix Released Status in dialer-app package in Ubuntu: Confirmed Status in messaging-app package in Ubuntu: Fix Released 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 1432696] Re: [SDK] Bottom edge header improvement
** Also affects: dialer-app Importance: Undecided Status: New ** Changed in: dialer-app Status: New => In Progress ** Changed in: dialer-app Assignee: (unassigned) => Bartosz Kosiorek (gang65) -- 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 dialer-app: In Progress Status in messaging-app: In Progress Status in scope-aggregator: New 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: Fix Released Status in dialer-app package in Ubuntu: Confirmed Status in messaging-app package in Ubuntu: Fix Released 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 1471680] Re: there is no copy and paste options when long pressing the number in dialer
** 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 dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1471680 Title: there is no copy and paste options when long pressing the number in dialer Status in Ubuntu UX: New Status in dialer-app package in Ubuntu: Confirmed Bug description: current build number: 47 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-06 05:43:41 version version: 47 version ubuntu: 20150706 version device: 20150701-cdd791c version custom: 20150602-731-5-32 Steps: 1.open the dialer app 2.input some numbers 3.long press the numbers Expectations: After step3#,the numbers should be chosen and there will be two options: copy,select Actual result: after step3#, there is nothing appears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1471680/+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 1433131] Re: [dialer app] pressing power button a 2nd time switches off screen
I could confirm that this issue was not resolved yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1433131 Title: [dialer app] pressing power button a 2nd time switches off screen Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: New Status in telephony-service package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: This bug is related to this one: https://bugs.launchpad.net/ubuntu- ux/+bug/1376240 While pressing the power button does silence the call but this interaction switches off the screen too. It can look strange for users because it is not clear if the call was just silenced or completely dismissed. UX desired solution: - 1st press of power button silences the call - 2nd press shuts off device screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1433131/+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 1309727] Re: headphone button does not answer or hangup phone call.
** Changed in: dialer-app (Ubuntu) Status: Incomplete => Fix Released ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => 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/1309727 Title: headphone button does not answer or hangup phone call. Status in dialer-app package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: Summary: headphone button does not answer or hangup phone call. Steps: 1. plug in headphones with a call/hangup button in headphone jack 2. call the phone with the headphones plugged in with step 1 3. press headphone answer/hangup button expected results: call is answered actual results nothing happens. Additional info, this should also play/pause music when no call is in session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1309727/+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 1413611] Re: [dialer] Speaker button with "x" is confusing
** Branch linked: lp:~gang65/dialer-app/dialer-app-speaker-icon-fix -- 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/1413611 Title: [dialer] Speaker button with "x" is confusing Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: In Progress Bug description: on active call screen, the icon used to enable the phone speaker is a speaker icon with a "x", that give me the false idea that I will make the call mute if I click on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1413611/+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 1309727] Re: headphone button does not answer or hangup phone call.
Headphone's button is working perfectly for me on my BQ e4.5 device. ** Changed in: dialer-app (Ubuntu) Status: Triaged => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1309727 Title: headphone button does not answer or hangup phone call. Status in dialer-app package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Summary: headphone button does not answer or hangup phone call. Steps: 1. plug in headphones with a call/hangup button in headphone jack 2. call the phone with the headphones plugged in with step 1 3. press headphone answer/hangup button expected results: call is answered actual results nothing happens. Additional info, this should also play/pause music when no call is in session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1309727/+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 1267594] Re: Separate volume for ringer
This bug was already resolved. Please reopen it if I miss something. ** Changed in: dialer-app (Ubuntu) Status: Confirmed => 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/1267594 Title: Separate volume for ringer Status in dialer-app package in Ubuntu: Fix Released Bug description: There should be a separate volume setting for the ringer, so I can turn down or mute the volume of apps, but still be able to hear the ringer when I have an incoming call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1267594/+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 1431436] Re: Crash during a call
** Changed in: dialer-app (Ubuntu) Status: New => Incomplete -- 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/1431436 Title: Crash during a call Status in dialer-app package in Ubuntu: Incomplete Bug description: Was on a conference line about to enter the conf code Tried to turn on speaker mode and the keypad and the UI became unresponsive the call continued but I couldn't interact with it Resulting crash file attached mako running 213 rtm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1431436/+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 1361722] Re: [lock screen] Number pad is inconsistent between dialer and lock screen
Does this bug is still applicable? The lock screen implementation was changed. ** Changed in: dialer-app (Ubuntu) Status: Confirmed => Incomplete ** Changed in: unity8 (Ubuntu) Status: Confirmed => Incomplete -- 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/1361722 Title: [lock screen] Number pad is inconsistent between dialer and lock screen Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 14.10 r203 1. Set the phone to have a PIN code, if it does not have one already. 2. Navigate to the keypad screen of the phone app. 3. Lock the phone and then reveal the unlock screen. What you see: The number pads have different colors, shapes, sizes, spacing, font sizes, and even font weights. It's as if they've been designed by two different people. What you should see: The two screens use different colors, and the phone buttons have letters and * + # symbols, but the number pads are otherwise consistent. Fixing this bug would be one way of fixing bug 1362136. --Ux comment Desired solution: Please align lock screen visuals as per dialer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1361722/+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 1421399] Re: [dialer] increase touch area for in call controls
** Changed in: dialer-app (Ubuntu RTM) Status: New => Invalid -- 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/1421399 Title: [dialer] increase touch area for in call controls Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: Confirmed Status in dialer-app package in Ubuntu RTM: Invalid Bug description: from usability tests: Buttons (eg. mute icon, hang up button) are a bit small therefore demanded high gesture precision. Guidance from design is Make invisible touch targets larger ---UX comment- Please increase the touch target area and follow the latest Visual design spec: https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.ga167dd8c0_0_8 touch areas outlined on page 9 of the spec https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit?pli=1#slide=id.g34608d763_0187 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1421399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1338970] Re: [dialer] No voicemail number defined ==> No feedback when attempting to dial
** Changed in: dialer-app (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1338970 Title: [dialer] No voicemail number defined ==> No feedback when attempting to dial Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: Incomplete Bug description: I have some SIM cards with no voicemail number predefined (although the voicemail service actually works with the subscription). Testing with a SIM card that has a pre-defined voicemail number (Saunalahti, Finland): - Open dialer - Long press number 1 (with the "tape reels" icon) Actual result: Voicemail is dialled correctly Testing with a SIM card that does *not* have a pre-defined voicemail number (Sonera, Finland): - Open dialer - Long press number 1 (with the "tape reels" icon) Actual result: Nothing happens Expected result: - Either something like "No voicemail number defined, enter now? " and a corresponding settings page, - or maybe show the voicemail icon only conditionally, if property org.ofono.MessageWaiting.VoicemailMailboxNumber is not empty Tested on mako HW, image 118. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1338970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440835] Re: [dialer] In call selection does not function
It is working perfectly for me. ** Changed in: dialer-app (Ubuntu) Status: New => 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/1440835 Title: [dialer] In call selection does not function Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: Fix Released Bug description: When in a call and asked to "press 1 for blahblah" the number 1 registers on the screen when the keypad is pressed but it does not select the menu option at the call destination. In my case, I cannot check my pay as you go balance that way ! [Aquaris, build 20]. --UX COMMENT--- In call keyboard has always to function during an active call in case users want to click through additional options or add extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1440835/+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 1449691] Re: [Dialer] Auto-completion when dialing a number
** Changed in: dialer-app (Ubuntu) Status: Confirmed => Incomplete -- 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/1449691 Title: [Dialer] Auto-completion when dialing a number Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: Incomplete Bug description: I would suggest auto-completion when I dial a number which is stored in my contacts. The app should show results e.g. Tux's number is 12345678 after typing the first numbers his number there should be suggestions. There should also be the possibility to deactivate this function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1449691/+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 1346837] Re: [phone-app]*#06# does not report IMEI when no SIM present
** Changed in: dialer-app (Ubuntu) Status: Confirmed => 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/1346837 Title: [phone-app]*#06# does not report IMEI when no SIM present Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: Fix Released Bug description: 1. Boot the phone with no SIM present. (No SIMs present for dual-sim) 2. Open the dialer. (2a. Select one of the SIM slots) 3. Dial *#06# Expected result: Dialog presented with the IMEI for the corresponding SIM slot. Current result: Dialog is shown but the IMEI field is empty This works when a SIM is present, but should not be dependent on this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1346837/+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 1476317] Re: Header is partially transperent in landscape mode
This issue was resolved with latest release with OTA-9 ** Changed in: messaging-app (Ubuntu) Status: Confirmed => 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/1476317 Title: Header is partially transperent in landscape mode Status in messaging-app package in Ubuntu: Fix Released Bug description: Writing a long message in landscape mode causes transparency issues. bq aquaris 4.5; Ubuntu 15.04 (r24) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1476317/+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 1420896] Re: FM radio doesn't work
Good morning dear list,
it's time for the "good news, bad news" part again.
The good news: I managed to attach gdb to the Factory Mode [1] binary,
and with some debugging-symbol-building and gdb-command-writing it's now
starting to get possible to catch every ioctl and semi-automatically
dump the parameters. Those of you who know a bit about debugging may see
the value in a gdb output like this one:
Breakpoint 1, 0xb6f41298 in ioctl () from /system/lib/libc.so
lrwx-- root root 2015-12-16 21:44 25 -> /dev/fm
FM_IOCTL_POWERUP
$5 = {err = 0 '\000', band = 1 '\001', space = 1 '\001', hilo = 0
'\000', freq = 880}
Turns out you only need three ioctl()s to power on and tune the whole FM
chip: FM_IOCTL_POWERUP, FM_IOCTL_MUTE and FM_IOCTL_ANA_SWITCH.
The bad news: We also catched all the ioctls necessary to tell the audio
chip to forward the FM signal to the headphones, and it's 90 (!) calls.
So our problem isn't the FM radio, it actually seems to be the audio
subsystem.
cheers,
Simon
[1]
http://sturmflut.github.io/ubuntu/bq/2015/05/04/hacking-the-bq-part-2-factory-mode/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtmultimedia-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1420896
Title:
FM radio doesn't work
Status in qtmultimedia-opensource-src package in Ubuntu:
Confirmed
Bug description:
We have an API, but, at least, on officially supported BQ Aquaris it
simply doesn't work. Attribute "availability" in Radio {} returns
Radio.Unavailable, but phone has FM module.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmultimedia-opensource-src/+bug/1420896/+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 1420896] Re: FM radio doesn't work
Soem FM Radio support was already started by Sturm FLut:
https://lists.launchpad.net/ubuntu-phone/msg17340.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtmultimedia-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1420896
Title:
FM radio doesn't work
Status in qtmultimedia-opensource-src package in Ubuntu:
Confirmed
Bug description:
We have an API, but, at least, on officially supported BQ Aquaris it
simply doesn't work. Attribute "availability" in Radio {} returns
Radio.Unavailable, but phone has FM module.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmultimedia-opensource-src/+bug/1420896/+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 1489579] Re: At launch the design is different then quickly changes (see image)
There is no longer such issue with new SDK 1.3 ** Changed in: messaging-app (Ubuntu) Status: Confirmed => 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/1489579 Title: At launch the design is different then quickly changes (see image) Status in messaging-app package in Ubuntu: Fix Released Bug description: After OTA-6 when you launch the application it very briefly shows the entire app with a white background and then changes. I managed to take a screenshot of the application before it changed. Before- RightAfter-Left http://i.imgur.com/DMk0inN.png This happens every time when starting the application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1489579/+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 1413170] Re: Not able to select contact while composing a SMS
This issue was already resolved. ** Changed in: messaging-app (Ubuntu) Status: New => 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/1413170 Title: Not able to select contact while composing a SMS Status in messaging-app package in Ubuntu: Fix Released Bug description: I'm using Nexus 5. I have installed Ubuntu using MultiROM I can reply to the SMS that i have received but following is not working. 1. Open SMS app 2. Select 'Compose' from bottom bar 3. Click the Add Contact icon 4. Choose the contact from the list 5. It shows as added 6. Type message 7. Click Send 8. Returns Failed error Message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1413170/+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 1488985] Re: App doesn't show the sms lenght
*** This bug is a duplicate of bug 1278790 *** https://bugs.launchpad.net/bugs/1278790 ** This bug has been marked a duplicate of bug 1278790 [Messaging] Show number of characters used and number of messages to send -- 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/1488985 Title: App doesn't show the sms lenght Status in messaging-app package in Ubuntu: Confirmed Bug description: Some people can consider it as not important but I find it a bug because of the costs especially in roaming mode. The problem of the Ubuntu phone (unlike any other device starting from the ancient very first Nokia or Motorola phones) is that we don't see the length of the message that we write. Some people can say: "hey there are only a few cents difference nowadays! What's the difference between sending one sms message or two of them?". The answer to that question is very simple: try to take Your phone abroad. For example fly from Your home country as Poland, Germany, France etc. to RPA, Macedonia or such kind of countries where one single space between two words can save You a few dollars/euro for every single message. Let's say You have now badly send many of them? It makes a difference! If a message is to be send as a sms it does make a difference! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1488985/+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 1491752] Re: Cant sent picture attached to text from Gallery
** Summary changed: - Cant sent picture attached to text from Galory + Cant sent picture attached to text from Gallery -- 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/1491752 Title: Cant sent picture attached to text from Gallery Status in messaging-app package in Ubuntu: New Bug description: Hi, I am using the ubuntu MX4 with version 15.04 (r4) update. When I attached a picture using the galory app or file manager the text message fails to send (red text is shown "Failed"). I have tried pictures taken from the phone camera and other pictures but the same result. I called my provider Tesco and confirmed that I have picture messaging is enabled (it is). Can you please investigate. Note, it would also be useful to attached documents etc. General comment. I also find the default gray text very dim and difficult to read, once you navigate to the website (such as the BBC) the text is far better. This is not so good for a phone that's designed to be content based. When the Ubuntu phone goes main stream in 2016 and the user wishes to add a background picture this will become a real problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1491752/+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 1247216] Re: Support for XMPP
** Changed in: messaging-app (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1247216 Title: Support for XMPP Status in messaging-app package in Ubuntu: Confirmed Status in ubuntu-system-settings-online-accounts package in Ubuntu: Triaged Bug description: Hi All, basically there are three things that block me to move to Ubuntu Touch. A missing spotify app (already in developement :) ), a missing mail app (planned for 14.04 :) ) and finally a missing IM app -- especially for XMPP. Thusly, I propose adding support for XMPP to the messaging-app. It already uses telepathy so we should be able to add this functionality. I would also be willing to work on this if somebody points me out where to start. I guess we would have to break this down into several work packages: setting up accounts, online/offline handling of friends, choosing protocols when composing a message etc. But first I would like to get some feedback if you would be okay with such a feature. Maybe it is already planned? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1247216/+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 1457424] Re: Please update icon (May 2015)
** Changed in: mediaplayer-app Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1457424 Title: Please update icon (May 2015) Status in address-book-app: Fix Released Status in camera-app: Fix Released Status in Canonical System Image: Fix Released Status in Dekko: Fix Released Status in gallery-app: Fix Released Status in mediaplayer-app: Fix Released Status in messaging-app: In Progress Status in Ubuntu Music App: Fix Released Status in Ubuntu Notes app: Fix Released Status in Ubuntu Calculator App: Fix Released Status in Ubuntu Calendar App: Fix Released Status in Ubuntu Clock App: Fix Released Status in Ubuntu Shorts App: Fix Released Status in Ubuntu theme: Fix Released Status in Ubuntu Weather App: Fix Released Status in webbrowser-app: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in mediaplayer-app package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in qtcreator-plugin-ubuntu package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Status in ubuntu-system-settings source package in Vivid: New Bug description: New icons are available. Please update app to new icon. Note the icon inside the app will need updating as well as the icon in the store (when uploaded). 256x256 and 512x512 Icons attached in zip file. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1457424/+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 1207772] Re: [Addres book] Date of birth field is missing
** Description changed: There is no Date of birth field on the contact view/edit page, as per visual design - To implement that, first bug: + The SDK bug which was stopper for resolving that issue was already resolved: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1226329 - needs to be resolved + @Renato Could you please propose you branch for merge? --- UX comment -- We provided UX and updated the visual design for guidance. Please see the visual design spec, pages 31 & 32 : https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g9971256b2_0_9 -- 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/1207772 Title: [Addres book] Date of birth field is missing Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: In Progress Bug description: There is no Date of birth field on the contact view/edit page, as per visual design The SDK bug which was stopper for resolving that issue was already resolved: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1226329 @Renato Could you please propose you branch for merge? --- UX comment -- We provided UX and updated the visual design for guidance. Please see the visual design spec, pages 31 & 32 : https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g9971256b2_0_9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1207772/+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 1478673] Re: Add birthday to the contact details (and sync from google contacts)
*** This bug is a duplicate of bug 1207772 *** https://bugs.launchpad.net/bugs/1207772 ** This bug has been marked a duplicate of bug 1207772 [Addres book] Date of birth field is missing -- 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/1478673 Title: Add birthday to the contact details (and sync from google contacts) Status in Canonical System Image: Confirmed Status in address-book-app package in Ubuntu: Triaged Bug description: After importing contacts from Google, birthdays are not shown. Adding birthdays to contacts is not possible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478673/+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 1492161] Re: Messaging app sluggish after OTA-6
*** This bug is a duplicate of bug 1488988 *** https://bugs.launchpad.net/bugs/1488988 ** This bug has been marked a duplicate of bug 1488988 slow to load a thread -- 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/1492161 Title: Messaging app sluggish after OTA-6 Status in messaging-app package in Ubuntu: Incomplete Bug description: Since OTA-6 on Bq Aquaris 4.5, the new messaging app is just unbearably slow. The app is very unresponsive and everything seems to take very long. Opening the app takes about 5 seconds, displaying contact names instead of numbers another 5 secs, opening a chat >=5 secs, sending message after pressing button some 3 seconds etc. Sometimes the app sort of pauses while typing, then after a few seconds showing the characters that have been entered. Unfortunately, the latency in the app is so bad it is almost unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1492161/+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 1401136] Re: [messaging-app] selection toggle doesn't unselect items in main view
** Changed in: messaging-app (Ubuntu) Status: New => Confirmed -- 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/1401136 Title: [messaging-app] selection toggle doesn't unselect items in main view Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: steps to reproduce build r172 1. launch messaging app, make sure your landing view has several conversations stored 2. long press on any list item 3. check boxes appear next to the list items and you should be able to select them individually (try it out) 4. now tap the "box + tick" icon in the header to select all items at the same time 5. tap it again Actual result: The 2nd tap on the "box + tick" icon in the header does not unselect all list items as though. Ideally the icon in the header should toggle: a) square with tick = select all b) empty square = unselect all UX comment--- Expected result: As you were able to select all items with one tap on the "box + tick" icon, a second tap should unselect them Currently it works correctly in the Address Book and Phone app, apart from changing icon in the header. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1401136/+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 1333522] Re: add README file
** Branch linked: lp:~gang65/messaging-app/messaging-app-readme -- 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/1333522 Title: add README file Status in messaging-app package in Ubuntu: In Progress Bug description: The project needs a README with at least: - what the project is - how to build it - how to test it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1333522/+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 1424625] Re: Cannot send SMS message when there is no network.
*** This bug is a duplicate of bug 1229950 *** https://bugs.launchpad.net/bugs/1229950 We should store such SMS as a Draft. Sending it after network is available is very risky, as there could be Roaming enabled after getting network. ** This bug has been marked a duplicate of bug 1229950 [messaging-app]"draft" messages aren't saved -- 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/1424625 Title: Cannot send SMS message when there is no network. Status in messaging-app package in Ubuntu: Confirmed Bug description: I am unable to send a SMS message when there is no network (no coverage). I think that the System should save the message and automatically send the SMS when the telephone will find the coverage. It's very frustrating because to send a SMS in poorly coveraged area I have to wait a few minutes and try sending the message. Device: MAKO, OS build number: 15, Ubuntu Image part: 20150129, Device Image part: 20150116 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1424625/+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 1442582] Re: Wait for reception to send texts, don't fail straight away!
*** This bug is a duplicate of bug 1229950 *** https://bugs.launchpad.net/bugs/1229950 ** This bug is no longer a duplicate of bug 1424625 Cannot send SMS message when there is no network. ** This bug has been marked a duplicate of bug 1229950 [messaging-app]"draft" messages aren't saved -- 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/1442582 Title: Wait for reception to send texts, don't fail straight away! Status in messaging-app package in Ubuntu: New Bug description: when I send a text and I don't have reception at the time, I don't want to wait around for reception before I manually resend it, I want the message to send automatically when I get reception. Id like to prepare a text and send it and let the phone manage that, this is a requisite of a smart-phone my phone knows I'm trying to send a text and should try and send the text when it can. Having to manually resend the text is not very "smart" Thanks, I'm reporting this bug on my BQ Aquarius! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1442582/+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 1426553] Re: [messaging-app] Can't get rid of unread indicator
Hi Michael. Do you have still such issue with OTA-9 ? ** Changed in: messaging-app (Ubuntu) Status: New => Incomplete -- 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/1426553 Title: [messaging-app] Can't get rid of unread indicator Status in messaging-app package in Ubuntu: Incomplete Bug description: This is on my dogfood phone, a mako running ubuntu-touch/stable. I was having a text conversation with someone, and I don't know how this happened, but now I see a permanent unread indicator of 1. Entering the chat view with them does not clear it. What logs would be useful? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1426553/+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 1495726] Re: Contacts sorted by first name instead of last name
*** This bug is a duplicate of bug 1439140 *** https://bugs.launchpad.net/bugs/1439140 ** This bug has been marked a duplicate of bug 1439140 [Address Book] Display familly name first in the addressbook -- 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/1495726 Title: Contacts sorted by first name instead of last name Status in address-book-app package in Ubuntu: New Bug description: Tested on r25 Contacts are sorted by first name instead of the usual last name. Plus, there's not even an option to try to sort them differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1495726/+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 1509957] Re: inadeqaute fields to populate in contact details
*** This bug is a duplicate of bug 1207772 *** https://bugs.launchpad.net/bugs/1207772 ** This bug is no longer a duplicate of bug 1478673 Add birthday to the contact details (and sync from google contacts) ** This bug has been marked a duplicate of bug 1207772 [Addres book] Date of birth field is missing -- 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/1509957 Title: inadeqaute fields to populate in contact details Status in address-book-app package in Ubuntu: New Bug description: If I add any new entry with name, number, email, there is no provision to enter the person's birthday & make it reflect in calendar. If there is provision that contact app can talk to calendar, it will be easy to set reminder for anniversary, birthday etc. Also I cannot choose any photograph for conatcts added newly or existing. Also I tried sending contact via Bluetooth from Asus Zenfone 5 to BQ Auaris E5 Ubuntu phone. But I cannot find where the contact went on my ubuntu phone! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1509957/+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 1226329] Re: [TextField] The placeholderText does not apper when inputMask is setted
I checked it and it seems that TextField with placeholderText is working
correctly when inputMask is set.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1226329
Title:
[TextField] The placeholderText does not apper when inputMask is
setted
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Bug description:
The inputMask makes the placehorlderText invisible even when the text
property is empty.
Example:
TextInputDetail {
height: units.gu(4)
// this will never appears
placeholderText: i18n.tr("Date of birth")
inputMask: "09/09/"
}
WORKAROUND:
TextInputDetail {
height: units.gu(4)
// this will never appears
placeholderText: i18n.tr("Date of birth")
inputMask: activeFocus ? "09/09/" : ""
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1226329/+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 1492161] Re: Messaging app sluggish after OTA-6
Hi Tomas. Do you have the same issue with OTA-9. In OTA-9 the SDK was improved, so there should be improvement. ** Changed in: messaging-app (Ubuntu) Status: Confirmed => Incomplete -- 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/1492161 Title: Messaging app sluggish after OTA-6 Status in messaging-app package in Ubuntu: Incomplete Bug description: Since OTA-6 on Bq Aquaris 4.5, the new messaging app is just unbearably slow. The app is very unresponsive and everything seems to take very long. Opening the app takes about 5 seconds, displaying contact names instead of numbers another 5 secs, opening a chat >=5 secs, sending message after pressing button some 3 seconds etc. Sometimes the app sort of pauses while typing, then after a few seconds showing the characters that have been entered. Unfortunately, the latency in the app is so bad it is almost unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1492161/+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 1207772] Re: [Addres book] Date of birth field is missing
** Description changed: There is no Date of birth field on the contact view/edit page, as per visual design + + To implement that, first bug: + https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1226329 + needs to be resolved --- UX comment -- We provided UX and updated the visual design for guidance. Please see the visual design spec, pages 31 & 32 : https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g9971256b2_0_9 -- 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/1207772 Title: [Addres book] Date of birth field is missing Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: In Progress Bug description: There is no Date of birth field on the contact view/edit page, as per visual design To implement that, first bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1226329 needs to be resolved --- UX comment -- We provided UX and updated the visual design for guidance. Please see the visual design spec, pages 31 & 32 : https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g9971256b2_0_9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1207772/+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: messaging-app (Ubuntu) Status: New => Incomplete -- 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: Incomplete 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 1463874] Re: [messaging app] change icon and allow other attachment types when sending MMS
** Changed in: messaging-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1463874 Title: [messaging app] change icon and allow other attachment types when sending MMS Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: Per bug in barajas: https://bugs.launchpad.net/barajas/+bug/1372270 I believe two things need to happen here: 1) change the attachment icon from a camera to a paper clip 2) change the types we are requesting from pictures to Pictures, Contacts, Text (and in future Videos when we we support that) --UX comment The paperclip icon is already in the wireframes and can be obtained from the SURU icon theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1463874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436979] Re: BQ-Ubuntuphone: can not copy Text from SMS
** Changed in: messaging-app (Ubuntu) Status: Confirmed => 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/1436979 Title: BQ-Ubuntuphone: can not copy Text from SMS Status in messaging-app package in Ubuntu: Fix Released Bug description: ist all said in the Summary. I got a SMS containing a Telephone-number and I really like to be able to copy that Number, but its not possible. G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1436979/+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 1487530] Re: [messaging app] Confirmation missing for "SMS Received by Recipient(s)"
** Changed in: messaging-app (Ubuntu) Status: Confirmed => Incomplete -- 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/1487530 Title: [messaging app] Confirmation missing for "SMS Received by Recipient(s)" Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in messaging-app package in Ubuntu: Incomplete Bug description: Confirmation missing for "SMS Received by Recipient(s)" Not possible to set this rule anywhere? (Aquaris E5 OTA-5) Ofono supports requesting a delivery report with a third option on the SendMessage method. When the report is received an IncomingStatusReport signal is provided. A setting in messaging app could be added to enable this. It seems not all carriers support this feature. UX resolution -- This is planned to be a part of the app settings in the messaging app. the wireframes are work in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487530/+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 1265236] Re: [messaging-app] Sync logs
** Changed in: messaging-app (Ubuntu) Status: Triaged => Incomplete -- 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/1265236 Title: [messaging-app] Sync logs Status in Ubuntu UX: Triaged Status in messaging-app package in Ubuntu: Incomplete Bug description: Hi, it would be nice if the chatlogs could be synced/backed-up somehow (e.g. via Ubuntu One). This is currently not a big problem as only SMS is supported, but if other chat protocols kick in this would be a killer feature. Of course, this would create some privacy issues, but this could be solved e.g. by adding PGP encryption to the logs. Would generally be nice if UOA or some other service would expose the users PGP key so it can be used to encrypt sensitive data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1265236/+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 1229950] Re: [messaging-app]"draft" messages aren't saved
** Changed in: messaging-app (Ubuntu) Status: Confirmed => Incomplete -- 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/1229950 Title: [messaging-app]"draft" messages aren't saved Status in Ubuntu UX: In Progress Status in messaging-app package in Ubuntu: Incomplete Bug description: Drafting an sms message and then pressing back to go back to the main messaging screen causes we to lose my unsent message 1. open messaging and select a contact 2. draft a new message to them 3. open toolbar and select back to go back to primary screen 4. Tap the contact again Expected Results draft version of message is retained in the text box actual result blank text box, without the draft message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1229950/+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 1442216] Re: Cannot call numbers received in SMS
** Changed in: messaging-app (Ubuntu) Status: Confirmed => 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/1442216 Title: Cannot call numbers received in SMS Status in messaging-app package in Ubuntu: Fix Released Bug description: Some SMS contain numbers of sufficient length that are obvious phone numbers (some even start from the + sign) but cannot be called from the application. They should be clickable, same way as URLs, which are recognized correctly. Or even better, Messaging app should search for possible owners of these numbers in Contacts app and give choice: open contact or call the number. There are two well known scenarios involving sending phone numbers through SMS: 1. A person sending a number to another person (a "mutual friend") 2. Carrier notification about a missed call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1442216/+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 1538951] Re: Impossible to export contacts in sim card, and it's impossible to choose where saving a new contact
** 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/1538951 Title: Impossible to export contacts in sim card, and it's impossible to choose where saving a new contact Status in Ubuntu UX: New Status in address-book-app package in Ubuntu: Confirmed Bug description: I'm using Meizu MX4 with OTA9. 1. There isn't an option to EXPORT contacts in SIM card. It's impossible to export contacts from address book app to a sim card. This is a good features when an user want to use the sim card in another cellphone. 2. Also, when you add a new contact in address book app it's impossible to choose where saving it: on SIM, or Phone memory. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1538951/+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: messaging-app (Ubuntu) Status: Confirmed => Fix Released ** Also affects: messaging-app Importance: Undecided Status: New ** Changed in: messaging-app Status: New => In Progress ** Changed in: messaging-app Assignee: (unassigned) => Bartosz Kosiorek (gang65) -- 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 messaging-app: In Progress 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: Fix Released Status in dialer-app package in Ubuntu: Confirmed Status in messaging-app package in Ubuntu: Fix Released 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 1278790] Re: [Messaging] Show number of characters used and numver of messages
** Summary changed: - [Messaging] Show number of characters used + [Messaging] Show number of characters used and numver of messages ** Summary changed: - [Messaging] Show number of characters used and numver of messages + [Messaging] Show number of characters used and number of messages ** Summary changed: - [Messaging] Show number of characters used and number of messages + [Messaging] Show number of characters used and number of messages to send -- 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 and number of messages to send Status in Ubuntu UX: Triaged Status in messaging-app package in Ubuntu: Incomplete 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 1474962] Re: Amount of SMS's used to send a message is not shown
*** This bug is a duplicate of bug 1278790 *** https://bugs.launchpad.net/bugs/1278790 ** This bug has been marked a duplicate of bug 1278790 [Messaging] Show number of characters used and number of messages -- 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/1474962 Title: Amount of SMS's used to send a message is not shown Status in messaging-app package in Ubuntu: New Bug description: For people who don't have an unlimited amount of SMS's or who pay per SMS, it is useful to know if they are about to send a message that needs more than one SMS, using Concatenated SMS. I would propose to show this information above the Send button, as in the attached mockup. As in the mockup, an info button could be provided. It would open an information screen informing the user that the message has to be sent using multiple SMS's, and that they probably will be charged multiple messages by the provider. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1474962/+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 1528673] Re: App doesn't have a qml-project file
*** This bug is a duplicate of bug 1333522 *** https://bugs.launchpad.net/bugs/1333522 You could import project via CMakeLists.txt. The README file should be upgraded to handle this. ** This bug has been marked a duplicate of bug 1333522 add README file -- 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/1528673 Title: App doesn't have a qml-project file Status in messaging-app package in Ubuntu: New Bug description: There is no way to open this up as a project in Qt Creator because there isn't a .qml-project file that can be opened by Qt Creator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1528673/+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 1393683] Re: notification indicator shows new messages as being from yesterday
This issue was already solved. ** Changed in: messaging-app (Ubuntu) Status: New => 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/1393683 Title: notification indicator shows new messages as being from yesterday Status in messaging-app package in Ubuntu: Fix Released Bug description: If I receive SMS messages, they appear in the notification indicator as having happened "yesterday", immediately after being received. I suspect this is an issue with calculating times in UTC instead of local time. I noticed it less than 7 hours before midnight, and I'm in UTC-7, so in UTC it's technically already tomorrow, and my local "today" is technically yesterday. The actual time of day displayed in the indicator is correct, but the day itself is wrong. I noticed this on rtm krillin image 162. It probably isn't an issue in places near UTC, but it definitely shows up in the west hemisphere. I wouldn't be surprised if eastern time zones have the opposite symptom, showing "tomorrow" sometimes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1393683/+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 1287709] Re: [Messaging app] shows wrong icon when adding a contact during Compose
In current implementation two icons are shown: One to send SMS and second to Call. ** Changed in: messaging-app (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1287709 Title: [Messaging app] shows wrong icon when adding a contact during Compose Status in Ubuntu UX: Fix Released Status in messaging-app package in Ubuntu: Fix Released Bug description: If I open the messaging app, then swipe up the toolbar and select Compose, I am presented with the compose window (good). If I then click the add Contact icon, then select a contact, a list is displayed that shows the number and "View contact's profile". This is fine, but the list shows a telephone icon rather than a message icon. If I select the telephone icon, the contact is added to the message and all is fine. This isn't a major issue, but can be confusing and is inconsistent with the dialer app's call log, where if you click an item in the call log, a list is displayed that shows a telephone icon with 'Call now' and a message icon with 'Send text message'. I would expect that the message icon always be used when dealing with messages and the telephone icon when dealing with calls. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1287709/+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 1356369] Re: [shell] Please disable screen rotation till unity8 supports it as well
** Changed in: messaging-app (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1356369 Title: [shell] Please disable screen rotation till unity8 supports it as well Status in Ubuntu UX: Fix Released Status in messaging-app package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Screen rotation conflicts with on screen notifications. 1. In landscape mode try to write an SMS 2. Ensure an incoming message while you are typing What happens: Notification appears over keyboard and you end up tapping on the notification losing your written text. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: messaging-app 0.1+14.10.20140806-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Wed Aug 13 18:21:57 2014 InstallationDate: Installed on 2014-08-13 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140813-020204) SourcePackage: messaging-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1356369/+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 1379421] Re: [messaing-app] shouldn't rotate into landscape mode as causes issues with compose and main view
The overlay issue was already fixed in OTA-9. Also rotation is working well ** Changed in: messaging-app (Ubuntu) Status: Confirmed => 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/1379421 Title: [messaing-app] shouldn't rotate into landscape mode as causes issues with compose and main view Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Fix Released Bug description: Build r93 The messaging app rotates to make it easier to type and read messaging threads. However, this causes issues in the compose and main views. If you rotate the app into landscape mode on the landing view, there is no way to carry out a bottom edge swipe to compose a new message. In the compose view, the landscape mode doesn't show the header. This one is needed, to add ppl to the recipient list. Recommendation: The ideal case is that we would have a custom header for landscape views because the current one in portrait mode is too large for certain devices. This needs further investigation from design and probably SDK. Plus there is still the issue of the bottom edge swipe in landscape, which needs to be addressed by Unity. Therefor it would be best to remove this feature for the RTM release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1379421/+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 1417759] Re: allready written message lost after restart
*** This bug is a duplicate of bug 1229950 *** https://bugs.launchpad.net/bugs/1229950 ** This bug has been marked a duplicate of bug 1229950 [messaging-app]"draft" messages aren't saved -- 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/1417759 Title: allready written message lost after restart Status in messaging-app package in Ubuntu: Confirmed Bug description: writte a message without sending it restart phone and message is lost Ubuntu development branch Build 186 (20150203-030204) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1417759/+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 1392619] Re: Should show up in 'Communication' department
*** This bug is a duplicate of bug 1379348 *** https://bugs.launchpad.net/bugs/1379348 ** This bug has been marked a duplicate of bug 1379348 App should be in department Communications -- 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/1392619 Title: Should show up in 'Communication' department Status in messaging-app package in Ubuntu: Confirmed Bug description: I think messaging (and dialer) app's should show up in 'Communication' department, rather than utilities. They're not utilities, like things like Calculator, Clock or System Settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1392619/+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 1461873] Re: [messaging] Ability to forward SMS without copy 'n past approach
** Changed in: ubuntu-ux Status: Confirmed => In Progress -- 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/1461873 Title: [messaging] Ability to forward SMS without copy 'n past approach Status in Ubuntu UX: In Progress Status in messaging-app package in Ubuntu: Confirmed Bug description: It would be nice if the SMS app swipe left context had the ability to forward the SMS to other receivers. The existing approah where one can swipe left and copy the content and then paste into a new SMS seems less intuitive. ** This feature is in the new designs but has yet to be implemented. https://docs.google.com/presentation/d/1hkrF2g- ad7fhJ0UVLKmu_5ZXSFK1EkcWS129JxmAAI4/edit#slide=id.p97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1461873/+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 1333522] Re: add README file
Hello. Could you please provide some short instruction how to build and run messaging-app application? ** Changed in: messaging-app (Ubuntu) Assignee: (unassigned) => Bartosz Kosiorek (gang65) ** Changed in: messaging-app (Ubuntu) Status: Confirmed => In Progress -- 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/1333522 Title: add README file Status in messaging-app package in Ubuntu: In Progress Bug description: The project needs a README with at least: - what the project is - how to build it - how to test it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1333522/+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 1439958] Re: Always receive duplicated SMS ans MMS
** Changed in: messaging-app (Ubuntu) Status: Confirmed => Incomplete -- 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/1439958 Title: Always receive duplicated SMS ans MMS Status in messaging-app package in Ubuntu: Incomplete Bug description: When someone send me a SMS or MMS, I always receive it twice and sometimes for the MMS is 10 times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1439958/+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 1473761] Re: SMS from A appear as to have been sent from B
** Changed in: messaging-app (Ubuntu) Status: Confirmed => 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/1473761 Title: SMS from A appear as to have been sent from B Status in Canonical System Image: Fix Released Status in messaging-app package in Ubuntu: Fix Released Bug description: Has been happening a lot since one week ago. Mako @ rc-proposed latest Reproduce: 1. Receive sms message from person A What happens: The message appears in the message history of person B, C, …, n. What should happen: Clearly, it's crucial that a message from person A needs to appear in person A's message history To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473761/+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 1476317] Re: Header is partially transperent in landscape mode
I could confirm that I could reproduce that issue on my BQ e4.5 device OTA-9 -- 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/1476317 Title: Header is partially transperent in landscape mode Status in messaging-app package in Ubuntu: Confirmed Bug description: Writing a long message in landscape mode causes transparency issues. bq aquaris 4.5; Ubuntu 15.04 (r24) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1476317/+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
