[Ubuntu-phonedations-bugs] [Bug 1539338] Re: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory
Found the cause. It was this update: android-headers (23-0ubuntu1) xenial; urgency=medium * New upstream release which now includes multiple sets of header files divided by the Android API levels we care about. * All header sets are now installed in their corresponding debian package android-headers-. The former android-headers package is now a transitional one depending on android-headers-19 and installing proper symlinks to allow all current users to still build without any changes. * Install proper pkgconfig configuration files for all header sets so that users can now select which of those to use a build time. -- Simon Fels Mon, 11 Jan 2016 08:50:59 +0100 ** Also affects: mir/0.18 Importance: Undecided Status: New ** Changed in: mir/0.18 Importance: Undecided => Critical ** Changed in: mir/0.19 Importance: Undecided => Critical ** Changed in: mir/0.18 Milestone: None => 0.18.2 ** Changed in: mir/0.19 Milestone: None => 0.19.0 ** Tags removed: ftmfs ** Tags added: ftbfs ** Also affects: android-headers (Ubuntu) Importance: Undecided Status: New ** Changed in: android-headers (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to android-headers in Ubuntu. https://bugs.launchpad.net/bugs/1539338 Title: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory Status in Mir: New Status in Mir 0.18 series: New Status in Mir 0.19 series: New Status in android-headers package in Ubuntu: New Bug description: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1539338] Re: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory
Unfortunately because the offending change is a package change in xenial, we can't immediately fix this without also losing support for building on wily or vivid. So we'll either need a flexible creative workaround in Mir, or a fix in android-headers itself. -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to android-headers in Ubuntu. https://bugs.launchpad.net/bugs/1539338 Title: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory Status in Mir: New Status in Mir 0.18 series: New Status in Mir 0.19 series: New Status in android-headers package in Ubuntu: New Bug description: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1539338] Re: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory
Hmm, my /usr/include/android/ is empty. This suggests the aforementioned "symlinks to allow all current users to still build without any changes" are missing. -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to android-headers in Ubuntu. https://bugs.launchpad.net/bugs/1539338 Title: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory Status in Mir: New Status in Mir 0.18 series: New Status in Mir 0.19 series: New Status in android-headers package in Ubuntu: New Bug description: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1539338] Re: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory
** Branch linked: lp:~vanvugt/mir/fix-1539338 -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to android-headers in Ubuntu. https://bugs.launchpad.net/bugs/1539338 Title: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory Status in Mir: New Status in Mir 0.18 series: New Status in Mir 0.19 series: New Status in android-headers package in Ubuntu: New Bug description: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1539338] Re: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory
** Changed in: mir Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to android-headers in Ubuntu. https://bugs.launchpad.net/bugs/1539338 Title: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory Status in Mir: In Progress Status in Mir 0.18 series: New Status in Mir 0.19 series: New Status in android-headers package in Ubuntu: New Bug description: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1539338] Re: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory
Fix Released? I can't see it; https://launchpad.net/ubuntu/+source /android-headers ** Description changed: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. + + WORKAROUND: + Just avoid building Mir with Android support: + cmake .. -DMIR_PLATFORM=mesa-kms -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to android-headers in Ubuntu. https://bugs.launchpad.net/bugs/1539338 Title: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory Status in Mir: In Progress Status in Mir 0.18 series: New Status in Mir 0.19 series: New Status in android-headers package in Ubuntu: Fix Released Bug description: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. WORKAROUND: Just avoid building Mir with Android support: cmake .. -DMIR_PLATFORM=mesa-kms To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1539338] Re: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory
** Changed in: mir/0.18 Milestone: 0.18.2 => None ** Changed in: mir/0.19 Milestone: 0.19.0 => None -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to android-headers in Ubuntu. https://bugs.launchpad.net/bugs/1539338 Title: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory Status in Mir: Fix Committed Status in Mir 0.18 series: New Status in Mir 0.19 series: New Status in android-headers package in Ubuntu: Fix Released Bug description: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. WORKAROUND: Just avoid building Mir with Android support: cmake .. -DMIR_PLATFORM=mesa-kms To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1539338] Re: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory
Chris' fix to android-headers means we don't need to rush fixes into Mir maintenance branches any more. ** Changed in: mir/0.18 Importance: Critical => Medium ** Changed in: mir/0.19 Importance: Critical => Medium ** Changed in: mir/0.18 Status: New => Won't Fix ** Changed in: mir/0.19 Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to android-headers in Ubuntu. https://bugs.launchpad.net/bugs/1539338 Title: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory Status in Mir: Fix Committed Status in Mir 0.18 series: Won't Fix Status in Mir 0.19 series: Won't Fix Status in android-headers package in Ubuntu: Fix Released Bug description: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. WORKAROUND: Just avoid building Mir with Android support: cmake .. -DMIR_PLATFORM=mesa-kms To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1539338] Re: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory
** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Triaged ** Changed in: mir (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to android-headers in Ubuntu. https://bugs.launchpad.net/bugs/1539338 Title: Mir fails to build on xenial today: android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory Status in Mir: Fix Committed Status in Mir 0.18 series: Won't Fix Status in Mir 0.19 series: Won't Fix Status in android-headers package in Ubuntu: Fix Released Status in mir package in Ubuntu: Triaged Bug description: After updating my xenial build machine today, lp:mir no longer builds: In file included from /home/dan/bzr/mir/trunk/src/platforms/android/server/platform.cpp:22:0: /home/dan/bzr/mir/trunk/src/platforms/android/server/android_graphic_buffer_allocator.h:23:31: fatal error: hardware/hardware.h: No such file or directory compilation terminated. The file in question exists in /usr/include/android-19/ but I suspect it might have moved there only recently. WORKAROUND: Just avoid building Mir with Android support: cmake .. -DMIR_PLATFORM=mesa-kms To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1607079] Re: Cellular Option immediately crashes [OTA-12]
Would the fix for this bug also resolve bug 1598010? -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1607079 Title: Cellular Option immediately crashes [OTA-12] Status in Canonical System Image: In Progress Status in indicator-network package in Ubuntu: In Progress Status in ofono package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: After upgrading to OTA-12 today, everything seemed to work perfectly. But after rebooting the first time, I was not asked for a SIM PIN number. I had to deactivate/activate the SIM card so I could use the phone again. Due to the fact that the indicator-network is empty, I tried to activate the 3G connection by using the cellular option in the system settings. The cellular data option immediately crashes when selecting it. Edit: After rebooting a few times and deactivate/activate the SIM card again I could use this option. But I cannot activate/deactivate the cellular data option. My carrier is shown correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607079/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Tags added: ubuntu-touch -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Status in ofono package in Ubuntu: Confirmed Status in ofono package in Ubuntu RTM: Confirmed Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Status in ofono package in Ubuntu: Confirmed Status in ofono package in Ubuntu RTM: Confirmed Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
** Tags added: bluez-touch -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1524939] Re: Using telephony in car with bluetooth not possible after second connection
** Tags added: bluez-touch -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1524939 Title: Using telephony in car with bluetooth not possible after second connection Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Bug description: I've a problem using telephony with bluetooth in my car I explain : I can connect in bluetooth with my car At the first connection everything works fine (I can do a call, play music normally in car speakers) At the second automatic connection (ie. I leave the car and go away, lost the bluetooth connection, and come back in the car --> the phone reconnect automatically to the car bluetooth) At this second connection, I loose the possibility to do a call with audio in car speakers. Telephony app detect the bluetooth well (bluetooth icon in app), but this doesn’t cut the sound already playing in car speaker and phone call is not redirected to car speakers. When I hangout the sound playing in car speaker is cut (for 2sec) but if do an other call this still not working. So to solve the problem, I have to manually disconnect from car bluetooth and reconnect again (in settings). If I just turn off bluetooth then turn it back on, the problem is not solved. Does someone have the same issue or am I not clear ? I could try to add a syslog if it could help. Device : mako rc-proposed; Bluetooth car module : XCARLink Smart BT in 207 Peugeot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1524939/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1519325] Re: Car kit reports "No network" when two SIMs are present but just one is online
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete ** Changed in: ofono (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1519325 Title: Car kit reports "No network" when two SIMs are present but just one is online Status in bluez package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: I've a second SIM that won't register because it has no roaming enabled. The car kit says "No network" even though I can make and receive calls. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 5.35+15.04.20151023-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Nov 24 13:03:40 2015 InstallationDate: Installed on 2015-11-24 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20151124-020303) Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 fixrtc lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=459 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=459 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � ProcModules: SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0:Type: BR/EDR Bus: UART BD Address: B8:64:91:48:2B:21 ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:774 acl:0 sco:0 events:53 errors:0 TX bytes:3722 acl:0 sco:0 commands:53 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519325/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1603150] Re: bluetooth HFP static noise
** Tags added: bluez-touch -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1603150 Title: bluetooth HFP static noise Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I have a headset connected and a phone call starts, all I hear is static noise. Seems like the wrong codec is selected. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603150/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Status in ofono package in Ubuntu: Confirmed Status in ofono package in Ubuntu RTM: Confirmed Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1494225] Re: Call audio is not routed to headset with HFP
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: Critical => Medium ** Changed in: pulseaudio (Ubuntu) Importance: Critical => Medium -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Invalid Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed: * pair and connect a headset over HFP * Establish an outgoing call or accept an incoming one * Once the call is established the call audio isn't routed through the handsfree device To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1394105] Re: Sometimes significant lag between snap dialog and ringtone start
** Tags added: pulse-touch ** Changed in: pulseaudio (Ubuntu) Assignee: Selene Scriven (toykeeper) => (unassigned) ** Changed in: canonical-devices-system-image Status: Incomplete => Won't Fix ** Changed in: canonical-devices-system-image Assignee: Jean-Baptiste Lallement (jibel) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1394105 Title: Sometimes significant lag between snap dialog and ringtone start Status in Canonical System Image: Won't Fix Status in indicator-messages package in Ubuntu: Invalid Status in ofono package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Incomplete Bug description: Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin When testing a large number of phone calls it could be seen that on certain calls there would be a significant delay between the snap decision dialog being displayed and the ringtone beginning to play. In extreme circumstances this could cause calls to be missed as there would not be enough time to answer. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394105/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1494225] Re: Call audio is not routed to headset with HFP
** Tags added: pulse-touch -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Invalid Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed: * pair and connect a headset over HFP * Establish an outgoing call or accept an incoming one * Once the call is established the call audio isn't routed through the handsfree device To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
** Tags added: bluez-touch pulse-touch -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1519809 Title: No sound is routed to bluetooth headset after a call Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Fix Committed Bug description: After the latest update to bluez5 no sound is routed to the connected bluetooth headset after a call is ended. Steps to reproduce: 1) connect a bluetooth headset 2) Receive a call 3) End the call 4) Try to play music Expected behavior: Music is routed to the connected headset Current behavior: No sound is routed, although music player behaves as it was playing normally. Additional info. If you receive a second call, the audio is again routed normally to the headset after it's finished. Just tried with old images with bluez4 and it works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1519809/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1603150] Re: bluetooth HFP static noise
** Tags added: pulse-touch -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1603150 Title: bluetooth HFP static noise Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I have a headset connected and a phone call starts, all I hear is static noise. Seems like the wrong codec is selected. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603150/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly
** Tags added: pulse-touch -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
Ubuntu Touch is no longer supported. ** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1519809 Title: No sound is routed to bluetooth headset after a call Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Won't Fix Bug description: After the latest update to bluez5 no sound is routed to the connected bluetooth headset after a call is ended. Steps to reproduce: 1) connect a bluetooth headset 2) Receive a call 3) End the call 4) Try to play music Expected behavior: Music is routed to the connected headset Current behavior: No sound is routed, although music player behaves as it was playing normally. Additional info. If you receive a second call, the audio is again routed normally to the headset after it's finished. Just tried with old images with bluez4 and it works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1519809/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1524939] Re: Using telephony in car with bluetooth not possible after second connection
Ubuntu Touch is no longer supported. ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1524939 Title: Using telephony in car with bluetooth not possible after second connection Status in bluez package in Ubuntu: Won't Fix Status in ofono package in Ubuntu: Confirmed Bug description: I've a problem using telephony with bluetooth in my car I explain : I can connect in bluetooth with my car At the first connection everything works fine (I can do a call, play music normally in car speakers) At the second automatic connection (ie. I leave the car and go away, lost the bluetooth connection, and come back in the car --> the phone reconnect automatically to the car bluetooth) At this second connection, I loose the possibility to do a call with audio in car speakers. Telephony app detect the bluetooth well (bluetooth icon in app), but this doesn’t cut the sound already playing in car speaker and phone call is not redirected to car speakers. When I hangout the sound playing in car speaker is cut (for 2sec) but if do an other call this still not working. So to solve the problem, I have to manually disconnect from car bluetooth and reconnect again (in settings). If I just turn off bluetooth then turn it back on, the problem is not solved. Does someone have the same issue or am I not clear ? I could try to add a syslog if it could help. Device : mako rc-proposed; Bluetooth car module : XCARLink Smart BT in 207 Peugeot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1524939/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly
Ubuntu Touch is no longer supported. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1494225] Re: Call audio is not routed to headset with HFP
Ubuntu Touch is no longer supported. -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: Won't Fix Status in bluez package in Ubuntu: Won't Fix Status in media-hub package in Ubuntu: Invalid Status in ofono package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed: * pair and connect a headset over HFP * Establish an outgoing call or accept an incoming one * Once the call is established the call audio isn't routed through the handsfree device To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1603150] Re: bluetooth HFP static noise
Ubuntu Touch is no longer supported. ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1603150 Title: bluetooth HFP static noise Status in Canonical System Image: New Status in bluez package in Ubuntu: Won't Fix Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Won't Fix Bug description: When I have a headset connected and a phone call starts, all I hear is static noise. Seems like the wrong codec is selected. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603150/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Ubuntu Touch is no longer supported. ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Won't Fix Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
Ubuntu Touch is no longer supported. -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Won't Fix Status in bluez package in Ubuntu: Won't Fix Status in ofono package in Ubuntu: Won't Fix Status in ofono package in Ubuntu RTM: Won't Fix Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1394105] Re: Sometimes significant lag between snap dialog and ringtone start
Ubuntu Touch is no longer supported. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1394105 Title: Sometimes significant lag between snap dialog and ringtone start Status in Canonical System Image: Won't Fix Status in indicator-messages package in Ubuntu: Invalid Status in ofono package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin When testing a large number of phone calls it could be seen that on certain calls there would be a significant delay between the snap decision dialog being displayed and the ringtone beginning to play. In extreme circumstances this could cause calls to be missed as there would not be enough time to answer. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394105/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
Ubuntu Touch is no longer a supported. ** Changed in: bluez (Ubuntu) Status: In Progress => Won't Fix ** Changed in: canonical-devices-system-image Status: Confirmed => Won't Fix ** Changed in: ofono (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: ofono (Ubuntu RTM) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Won't Fix Status in bluez package in Ubuntu: Won't Fix Status in ofono package in Ubuntu: Won't Fix Status in ofono package in Ubuntu RTM: Won't Fix Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-phonedations-bugs] [Bug 1494225] Re: Call audio is not routed to headset with HFP
Ubuntu Touch is no longer supported. ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: canonical-devices-system-image Status: Confirmed => Won't Fix ** Changed in: ofono (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: Won't Fix Status in bluez package in Ubuntu: Won't Fix Status in media-hub package in Ubuntu: Invalid Status in ofono package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed: * pair and connect a headset over HFP * Establish an outgoing call or accept an incoming one * Once the call is established the call audio isn't routed through the handsfree device To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
