[Touch-packages] [Bug 1630243] [NEW] WebWhatsapp App (v. 1.02) - Problem when trying to record a message, issue with webview
Public bug reported: I'm trying to use your WebWhatsapp App (v. 1.02) and it works well on Meizu MX4. Starting from OTA 12 Ubuntu Touch web browser support the WebRTC Api, that permits to send audio message. But I have a problem to doing this. Here what I'm doing: 1. Open WebWhatsapp, and in a chat press the "microphone" icon; 2. I need to accept the microphone access permission every single time that I open the App, after that I need to click again on the microphone icon; 3. Then the recording starts; 4. After the end of the recording, if you try to record another audio message, you can't, the template open and close the keyboard and the recording doesn't start. 5. You need to close and reopen the App and starting again from point 1. Probably there's a problem with CSS and webview template. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm trying to use your WebWhatsapp App (v. 1.02) and it works well on Meizu MX4. Starting from OTA 12 Ubuntu Touch web browser support the WebRTC Api, that permits to send audio message. But I have a problem to doing this. Here what I'm doing: 1. Open WebWhatsapp, and in a chat press the "microphone" icon; - 2. I need to accept the microphone access permission every single time that I open the App and I click on the microphone icon; + 2. I need to accept the microphone access permission every single time that I open the App, after that I need to click again on the microphone icon; 3. Then the recording starts; 4. After the end of the recording, if you try to record another audio message, you can't, the template open and close the keyboard and the recording doesn't start. 5. You need to close and reopen the App and starting again from point 1. Probably there's a problem with CSS and webview template. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1630243 Title: WebWhatsapp App (v. 1.02) - Problem when trying to record a message, issue with webview Status in webbrowser-app package in Ubuntu: New Bug description: I'm trying to use your WebWhatsapp App (v. 1.02) and it works well on Meizu MX4. Starting from OTA 12 Ubuntu Touch web browser support the WebRTC Api, that permits to send audio message. But I have a problem to doing this. Here what I'm doing: 1. Open WebWhatsapp, and in a chat press the "microphone" icon; 2. I need to accept the microphone access permission every single time that I open the App, after that I need to click again on the microphone icon; 3. Then the recording starts; 4. After the end of the recording, if you try to record another audio message, you can't, the template open and close the keyboard and the recording doesn't start. 5. You need to close and reopen the App and starting again from point 1. Probably there's a problem with CSS and webview template. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540942] Re: Showing the remaining power percentage
Something new? it's possible to add a button to showing or hiding battery percentage? Thank you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1540942 Title: Showing the remaining power percentage Status in Ubuntu UX: Confirmed Status in indicator-power package in Ubuntu: Incomplete Bug description: It's very useful add an option for showing the remaining power percentage, near the power indicator. Watch the pic attached below, this is what happen in android devices. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1540942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
I bought MX4 when it was released in Europe and Italy (more then 1 year ago), I don't remember what number of version it was. Maybe OTA-10? I'm never been able to pair MX4 with Nissan Connect system. What can I do? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
In my own case the problem remain the same. No difference between OTA-12 and 13 on Meizu MX4, pairing process always fail. Also I can't remove "Nissan Connect" device, to remove it I needed to use the terminal again. How can I provide more details? Thank you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, I tryed to pair again the phone with my car, but it don't work. The car say "Pairing failed". After this, to remove the device, I needed to use the terminal again. To resolve, I need to wait for OTA-13, or I need instruction for installing the new bluez silo. Thank you, Marco Il 29/07/2016 12:43, Konrad Zapałowicz ha scritto: > Marco, > > this is super strange, I will think of possible solutions however in > the meantime what is the output from > > info 60:38:0E:59:32:39 > > Thanks, > K > > On Fri, Jul 29, 2016 at 12:40 PM, Marco Graziotti > <graziottima...@gmail.com <mailto:graziottima...@gmail.com>> wrote: > > Hi Konrad, > > I tried to remove the "Nissan Connect" device, but i got this > error: "*Failed to remove device: org.bluez.Error.NotReady*". > Here you can read what I'm doing: > > *user@user-laptop:~$ adb shell* > * daemon not running. starting it now on port 5037 * > * daemon started successfully * > > phablet@ubuntu-phablet:~$ $ bluetoothctl > bash: $: command not found > > *phablet@ubuntu-phablet:~$ bluetoothctl* > [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] > [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# devices* > Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# remove 60:38:0E:59:32:39** > **Failed to remove device: org.bluez.Error.NotReady* > > What can I do? > > Thank you > > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: >> Hey, >> >> I'll try to help a bit here. >> >> First as for the unknown or unwanted entries on the paired devices lists >> [and such] you can try to remove them from the bluetoothctl level. >> >> ) enable developers mode & connect it via usb cable >> ) login with adb shell to the deivce >> ) type $ bluetoothctl >> ) then type: devices - to list the known devices >> ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address >> of the device [not it's name] >> >> Second we are in the of releasing the newest bluez 5.41 which is now in >> silo 37. If you are familiar with installing silos on your device you >> can try it out and check if it improves anything. It includes fixes for >> link management and pairing therefore there is a chance [although not >> certain] that there might be joy. >> >> If unsure please ask. >> >> Best, >> Konrad >> > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, the problem was that my bluetooth is turned off :D :D Now I'm able to remove the NISSAN CONNECT device [bluetooth]# remove 60:38:0E:59:32:39 [DEL] Device 60:38:0E:59:32:39 NISSAN CONNECT Device has been removed Now I will try to pair it again. Thank you, Marco Il 29/07/2016 12:43, Konrad Zapałowicz ha scritto: > Marco, > > this is super strange, I will think of possible solutions however in > the meantime what is the output from > > info 60:38:0E:59:32:39 > > Thanks, > K > > On Fri, Jul 29, 2016 at 12:40 PM, Marco Graziotti > <graziottima...@gmail.com <mailto:graziottima...@gmail.com>> wrote: > > Hi Konrad, > > I tried to remove the "Nissan Connect" device, but i got this > error: "*Failed to remove device: org.bluez.Error.NotReady*". > Here you can read what I'm doing: > > *user@user-laptop:~$ adb shell* > * daemon not running. starting it now on port 5037 * > * daemon started successfully * > > phablet@ubuntu-phablet:~$ $ bluetoothctl > bash: $: command not found > > *phablet@ubuntu-phablet:~$ bluetoothctl* > [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] > [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# devices* > Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# remove 60:38:0E:59:32:39** > **Failed to remove device: org.bluez.Error.NotReady* > > What can I do? > > Thank you > > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: >> Hey, >> >> I'll try to help a bit here. >> >> First as for the unknown or unwanted entries on the paired devices lists >> [and such] you can try to remove them from the bluetoothctl level. >> >> ) enable developers mode & connect it via usb cable >> ) login with adb shell to the deivce >> ) type $ bluetoothctl >> ) then type: devices - to list the known devices >> ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address >> of the device [not it's name] >> >> Second we are in the of releasing the newest bluez 5.41 which is now in >> silo 37. If you are familiar with installing silos on your device you >> can try it out and check if it improves anything. It includes fixes for >> link management and pairing therefore there is a chance [although not >> certain] that there might be joy. >> >> If unsure please ask. >> >> Best, >> Konrad >> > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, I tried to remove the "Nissan Connect" device, but i got this error: "*Failed to remove device: org.bluez.Error.NotReady*". Here you can read what I'm doing: *user@user-laptop:~$ adb shell* * daemon not running. starting it now on port 5037 * * daemon started successfully * phablet@ubuntu-phablet:~$ $ bluetoothctl bash: $: command not found *phablet@ubuntu-phablet:~$ bluetoothctl* [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT *[bluetooth]# devices* Device 90:F1:AA:7B:80:0F [Samsung] Soundbar Device 60:38:0E:59:32:39 NISSAN CONNECT *[bluetooth]# remove 60:38:0E:59:32:39** **Failed to remove device: org.bluez.Error.NotReady* What can I do? Thank you Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, thank you for your answer, I will try to apply the procedure that you have described during this weekend. I never installed a silos, so maybe it's better to wait the OTA-13 that incude bluez 5.41. Thank you, Marco Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
After the OTA-12 update, my MX4 still not working. Also I cant remove the "Nissan Connect" as paired device (see the image attached). I never been able to pair MX4 with Nissan Connect, so I don't know why it results as paired. ** Attachment added: "screenshot20160727_225309929.png" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4708302/+files/screenshot20160727_225309929.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580908] Re: Sim lock screen doesn't appear after restarting the device
Same problem for me on Meizu MX4 starting from OTA-11 update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1580908 Title: Sim lock screen doesn't appear after restarting the device Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in ofono package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: From https://bugs.launchpad.net/zhongshan/+bug/1572886 current build number: 4 device name: turbo channel: ubuntu-touch/rc/meizu.en last update: 2016-04-19 10:38:50 version version: 4 version ubuntu: 20160418 version device: 20160412-d272a77 version custom: 20160324-945-18-69 Steps: 1.turn on sim pin lock 2.reboot the device 3.swipe to dismiss the greeter Actual result: phone lock screen is displayed Expected result: sim lock screen should appear before the phone lock screen It also happens sometimes on arale without any pattern to reproduce, just random on reboot. = After debugging it seems that this is caused by ofono removing the modems in the middle of the unlock process. You can see the difference for Turbo and Krillin below. Log for Turbo: http://paste.ubuntu.com/1147/ Log for Krillin: http://paste.ubuntu.com/16675431/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
In my own case the bug persists with OTA 11 (Meizu MX4). @Stunts for this bug the milestone it's OTA12. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
In my own case it don't work. It's impossible to pair the MX4 (OTA-10.1) to "Nissan Connect" bluetooth. Also, it's now impossible to forget the "Nissan Connect" paired before. The "forget" button isn't cliccable (see pictures attached). You can find my bluetooth log file (with OTA-9) attached at the message number 22 ( https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/comments/22 ). If needed, I can prepare a new log file. ** Attachment added: "MX4_bluetooth_car_pair_problem.zip" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4635443/+files/MX4_bluetooth_car_pair_problem.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Problem persist for me too after updating to OTA-10. I'm using Meizu MX4 with "Nissan Connect" (first version, 2011 edition, see pic: https://launchpadlibrarian.net/236039500/Nissan-Connect-First-Version.jpg ). The phone finds "Nissan Connect", but when the pair procedure starts, it stops by itself before than asks me to enter the pin code "1234" to pair the device. After this stops the Nissan Connect display says "connection failed". "Nissan Connect" can connect phones with bluetooth 4, for example, I have also a Samsung S3 mini, and it works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
@Stunts: No way. When I'm trying to save the file pressing "enter", nothing happen. Editor ask me for a format (M-D DOS format; M-M Mac format; M-A Append; ecc), see the picture attached at message #25 This is the procedure that I have applied: - connect MX4 via terminal adb - insert command: sudo mount -o remount,rw / - edit file with: sudo nano /etc/init/bluetooth.conf - remove -d option from: exec /usr/sbin/bluetoothd -d - press CTRL + O for saving - trying to press enter for apply changes, but nothing happen What can I do? Thank you Marco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
@Stunts: I have followed the instruction that you shared here: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/comments/14 now I'm trying to remove "-d" option from "/etc/init/bluetooth.conf" but when I'm saving the file, nano's editor ask me if I wanna save the file as: - M-D DOS format - M-M Mac format - M-A Append - M-P Prepend - M-B Backup file (see picture attached) How did you save the file? *** @Simon Fels: Can the log file I attached in message 22 be useful? ** Attachment added: "problema_rimozione_opzione_-d.png" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4597999/+files/problema_rimozione_opzione_-d.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Thanks to the instruction provided by "Stunt" ( https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/comments/14 ), I have generated a bluetooth log file that you can find attached at this message. My own hands free system it's a NISSAN CONNECT, I'm using a Meizu MX4 with OTA 9.1. I hope that this log file contains what you need and let me know if you require anything else. Thank you. P.S.: I think I have removed any sensitive information from that log. ** Attachment added: "syslog_bluetooth pair_MX4.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4596895/+files/syslog_bluetooth%20pair_MX4.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi, today I've tried to make a log file about the bluetooth pair problem. I followed this istruction: https://wiki.ubuntu.com/DebuggingBluetooth for generating log files with debugging information. After this, I tried to pair my phone with car bluettoth system, and I have copied the "bluetoothhd" file from my phone (/usr/sbin/) to my desktop. I have opened this file but only a little part it's readable, part of this file contain unreadable characters; so I attach at this message only the readable parts. Please, let me know if this procedure is correct. This file attached it's useful for debugging? Thank you ** Attachment added: "bluetoothd.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4576690/+files/bluetoothd.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360582] Re: Can't manually install clicks "Signature verification error" since #205
I solved adding option "--allow-untrusted": pkcon --allow-untrusted install-local provissima.username_0.1_all.click -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1360582 Title: Can't manually install clicks "Signature verification error" since #205 Status in PackageKit: Confirmed Status in click package in Ubuntu: Fix Released Status in phablet-tools package in Ubuntu: Fix Released Status in qtcreator-plugin-ubuntu package in Ubuntu: Fix Released Bug description: See mailing list thread at https://lists.launchpad.net/ubuntu- phone/msg09607.html Since image #205 I can't install click packages using click-buddy & pkcon install-local. Changed click-buddy to use "adb $ADBOPTS shell click install --user=$DEVICE_USER --allow-unauthenticated /tmp/$click" which worked for me, but dunno if that's the "right" thing to do. alan@deep-thought:~/phablet/code/coreapps⟫ adb push com.ubuntu.music_1.3.597_all.click /tmp 2560 KB/s (401406 bytes in 0.153s) alan@deep-thought:~/phablet/code/coreapps⟫ phablet-shell start: Job is already running: ssh /home/alan/.ssh/known_hosts updated. Original contents retained as /home/alan/.ssh/known_hosts.old 9 KB/s (399 bytes in 0.040s) Warning: Permanently added '[localhost]:' (RSA) to the list of known hosts. Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako armv7l) * Documentation: https://help.ubuntu.com/ Last login: Fri Aug 22 23:53:19 2014 from localhost.localdomain phablet@ubuntu-phablet:~$ pkcon install-local /tmp/com.ubuntu.music_1.3.597_all.click Installing files [=] Finished [=] Installing files [=] Waiting for authentication[=] Starting [=] Finished [=] Fatal error: /tmp/com.ubuntu.music_1.3.597_all.click failed to install. Cannot install /tmp/com.ubuntu.music_1.3.597_all.click: Signature verification error: debsig: Origin Signature check failed. This deb might not be signed. To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1360582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360582] Re: Can't manually install clicks "Signature verification error" since #205
Same problem for me: phablet@ubuntu-phablet:~/Downloads$ pkcon install-local provissima.username_0.1_all.click Installing files [=] Finished [=] Installing files [=] Waiting for authentication[=] Starting [=] Finished [=] Fatal error: /home/phablet/Downloads/provissima.username_0.1_all.click failed to install. Cannot install /home/phablet/Downloads/provissima.username_0.1_all.click: Signature verification error: debsig: Origin Signature check failed. This deb might not be signed. There's a fix for this bug? Thank you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1360582 Title: Can't manually install clicks "Signature verification error" since #205 Status in PackageKit: Confirmed Status in click package in Ubuntu: Fix Released Status in phablet-tools package in Ubuntu: Fix Released Status in qtcreator-plugin-ubuntu package in Ubuntu: Fix Released Bug description: See mailing list thread at https://lists.launchpad.net/ubuntu- phone/msg09607.html Since image #205 I can't install click packages using click-buddy & pkcon install-local. Changed click-buddy to use "adb $ADBOPTS shell click install --user=$DEVICE_USER --allow-unauthenticated /tmp/$click" which worked for me, but dunno if that's the "right" thing to do. alan@deep-thought:~/phablet/code/coreapps⟫ adb push com.ubuntu.music_1.3.597_all.click /tmp 2560 KB/s (401406 bytes in 0.153s) alan@deep-thought:~/phablet/code/coreapps⟫ phablet-shell start: Job is already running: ssh /home/alan/.ssh/known_hosts updated. Original contents retained as /home/alan/.ssh/known_hosts.old 9 KB/s (399 bytes in 0.040s) Warning: Permanently added '[localhost]:' (RSA) to the list of known hosts. Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako armv7l) * Documentation: https://help.ubuntu.com/ Last login: Fri Aug 22 23:53:19 2014 from localhost.localdomain phablet@ubuntu-phablet:~$ pkcon install-local /tmp/com.ubuntu.music_1.3.597_all.click Installing files [=] Finished [=] Installing files [=] Waiting for authentication[=] Starting [=] Finished [=] Fatal error: /tmp/com.ubuntu.music_1.3.597_all.click failed to install. Cannot install /tmp/com.ubuntu.music_1.3.597_all.click: Signature verification error: debsig: Origin Signature check failed. This deb might not be signed. To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1360582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
I asked this because I read that it's dangerous switch in RW mode. At this url: http://askubuntu.com/questions/600065/consequences-of-using-apt-get-in-ubuntu-touch I read this: http://askubuntu.com/a/600313 ['evergreen' answer] "By default the system is read-only. You can switch to read-write mode, although this disables Ubuntu system upgrades.The main purpose for this is developing the Ubuntu system directly. This is not required for developing apps or using the system normally. Recovering from read-write mode is possible but requires reinstalling the system from scratch. Warning: Switching a device to read-write mode (and/or recovering from it) is an advanced feature and may result in complete data loss. Warning: Switching a device to read-write mode disables automatic over-the-air delta updates. Accepting a full over-the-air update after making a device writable may undo changes you have made." -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
@Stunts Thank you for your reply. For generating bluetooth log files with debugging information it's necessary to switch in read and write mode ( sudo mount -o remount,rw / ), after this, how can I restore the read only mode? Thank you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Where I can find the bluetooth syslog file? I wanna attach my own log to helping the fix procedure. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
I can't pair the device to the system. I'm using MX4 with OTA9. I have a Nissan, with "Nissan Connect" (first version, 2011 edition, see pic attached). The car finds the phone "Meizu MX4 Ubuntu Edition", and then asks me to enter the code "1234" to pair the device, but after this it says "connection failed". This system can connect phones with bluetooth 4; for example, I have also a Samsung S3, and it works. ** Attachment added: "Nissan-Connect-First-Version.jpg" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4562226/+files/Nissan-Connect-First-Version.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540942] [NEW] Showing the remaining power percentage
Public bug reported: It's very useful add an option for showing the remaining power percentage, near the power indicator. Watch the pic attached below, this is what happen in android devices. Thank you ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Attachment added: "samsung.jpg" https://bugs.launchpad.net/bugs/1540942/+attachment/4562192/+files/samsung.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1540942 Title: Showing the remaining power percentage Status in indicator-power package in Ubuntu: New Bug description: It's very useful add an option for showing the remaining power percentage, near the power indicator. Watch the pic attached below, this is what happen in android devices. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1540942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
@Stunts: No. I'm never been able to pair them. It never work in my own case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] [NEW] Impossible to export contacts in sim card, and it's impossible to choose where saving a new contact
Public bug reported: 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. ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20160128_092517218.png" https://bugs.launchpad.net/bugs/1538951/+attachment/4558196/+files/screenshot20160128_092517218.png -- 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 address-book-app package in Ubuntu: New 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/+source/address-book-app/+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 1473668] Re: [MX4] Photos are blurry and underexposed in low light conditions
Same problem for me. Blurry photos and bad synchronization when using flash (I got always a black photo - underexposed). I saw that the photos are also blurry if you shoot it during the day. Sometimes the AF isn't able to focusing object at short or long distances, maybe it's a problem with aperture values. See the shooting values of attached picture: f/2,2, 1/17 sec, 179 ISO; They are wrong values for this kind of photo, it's better: f/3,5, 1/60, 400 ISO. I have a second MX4 with Flyme 4.0.4.I, and it make wonderful photos. So I think this is a software problem. What do you think about? Thank you. ** Attachment added: "image20151224_201623129.jpg" https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1473668/+attachment/4546227/+files/image20151224_201623129.jpg -- 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/1473668 Title: [MX4] Photos are blurry and underexposed in low light conditions Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Triaged Bug description: Hello, photos taken by MX4 are blurry and underexposed. First one is really annoying, I can't take even one good sharp photo and I don't know why. Second one is maybe because of bad synchronization time of flashing and taking shot; I think that because, when I record video with lamp, everything is great, problem is only for photos. I know that smartphones are not great for night photos, but I've used before worse and cheaper low-end phones with no-name lens and photos was significantly better. Please tell me, if you need more information. I will try to provide them. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473668] Re: [MX4] Photos are blurry and underexposed in low light conditions
I'm checking all the pics that I have taken with MX4 Ubuntu Edition, and it seems that the aperture values is always set to f/2,2. Also the time values isn't always set for a correct exposure. This happen at any condition of light (day or night), only the ISO values change radically, sometimes the time values changing too. See the picture attached. Thank you. ** Attachment added: "image20160103_114116921.jpg" https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1473668/+attachment/4546240/+files/image20160103_114116921.jpg -- 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/1473668 Title: [MX4] Photos are blurry and underexposed in low light conditions Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Triaged Bug description: Hello, photos taken by MX4 are blurry and underexposed. First one is really annoying, I can't take even one good sharp photo and I don't know why. Second one is maybe because of bad synchronization time of flashing and taking shot; I think that because, when I record video with lamp, everything is great, problem is only for photos. I know that smartphones are not great for night photos, but I've used before worse and cheaper low-end phones with no-name lens and photos was significantly better. Please tell me, if you need more information. I will try to provide them. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1477838] Re: [MX4] Crackling sound after playing audio and suspended
Same problem for me, on my Meizu MX4 (OTA-8), when I receive a notification, after the ring tone, I can hear a little sound from the speaker (like a continuous "tic", it seems a current discharge, or something similar). It stops when I resume the phone from the standby mode. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1477838 Title: [MX4] Crackling sound after playing audio and suspended Status in Canonical System Image: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: The Meizu MX4 is doing a weird "tic tic tic..." after receive a notification (from telegram, mail...) and it's suspended. -- When I press the screen lock button on the MX4 shortly after playing music or ending a phone call I hear a radio/fuzzy distorted noise coming from the phone. To make it stop I need to unlock and lock the screen again but this is not ideal. - When the screen is locked and the playing song is finished and waiting for a stopped signal, MX4 will do a weird lower sound. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1477838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1512100] Re: Meizu MX4 (Arale r6) - Blinking screen during the call if you remove the phone from your ear
Hi Ramin, if you are affected too on your bq, subscribe the bug at this url: https://bugs.launchpad.net/bugs/1512100 and add a comment with a detailed event. Cheers, Marco Il 01/nov/2015 19:50, "Ramin" <1512...@bugs.launchpad.net> ha scritto: > hi there. > > I had this problem occur regularly on krillin stable on my bq aquaris > 4.5 > > this was present right up until the latest stable release. it was so > often it caused me to install android on the phone as making calls was > becoming impossible. most of the time after the call during the flashing > the only thing I could do was to hold down power to restart the os. > > sonetimes I would call someone and if they didn't answer I would end up > leaving messages on their answerphone because I could not hang up due to > the flashing. > > I'm now back on Ubuntu but the Rc-proposed channel and I don't think > I've expereinced it, but certainly had on the current stable. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1512100 > > Title: > Meizu MX4 (Arale r6) - Blinking screen during the call if you remove > the phone from your ear > > Status in dialer-app package in Ubuntu: > Confirmed > > Bug description: > I have a problem with my Meizu MX4 (Arale r6). > During a call if you remove the phone from your ear, sometimes (not > always) the screen remains turned off. When you try to push the power > button to wake up the screen, that starts blinking and it's not possible to > hang up. The screen remains in that condition even after the end of the > call. > When it keeps blinking I try to hold the button down and in few seconds > the screen turns black and the phone starts working again. Sometimes, > instead, it starts working again by itself. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1512100/+subscriptions > -- 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/1512100 Title: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1512100] Re: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear
Yes Ramin. I made a mistake. I'm sorry. Cheers, Marco Il lunedì 2 novembre 2015, Ramin <1512...@bugs.launchpad.net> ha scritto: > hi macro, isn't that URL this URL ? I'm sorry I'm a little confused > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1512100 > > Title: > Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you > remove the phone from your ear > > Status in Canonical System Image: > Confirmed > Status in powerd package in Ubuntu: > New > Status in unity-system-compositor package in Ubuntu: > New > > Bug description: > I have a problem with my Meizu MX4 (Arale r6). > During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. > When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+subscriptions > -- 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/1512100 Title: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512100] [NEW] Meizu MX4 (Arale r6) - Blinking screen during the call if you remove the phone from your ear
Public bug reported: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: Confirmed -- 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/1512100 Title: Meizu MX4 (Arale r6) - Blinking screen during the call if you remove the phone from your ear Status in dialer-app package in Ubuntu: Confirmed Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1512100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491125] [NEW] [Arale r4] Can't login with facebook in "flipboard"
Public bug reported: * I'm using * > Arale r4, on Meizu MX4 Ubuntu Edition > webbrowser-app 0.23+15.04.20150817-0ubuntu1 (checked via terminal, because in > Software Center the version is not showed) * Problem * When you try to sign in with facebook in "Flipboard" it's impossible to fill the textbox with your facebook email and password, the textbox it isn't cliccable. I don't know if the same things happen with another website that permits to login with facebook. I attach the screenshot in this message. Tell me if you need more information. Thank you. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot login with facebook" https://bugs.launchpad.net/bugs/1491125/+attachment/4455830/+files/screenshot20150901_220051092.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1491125 Title: [Arale r4] Can't login with facebook in "flipboard" Status in webbrowser-app package in Ubuntu: New Bug description: * I'm using * > Arale r4, on Meizu MX4 Ubuntu Edition > webbrowser-app 0.23+15.04.20150817-0ubuntu1 (checked via terminal, because in Software Center the version is not showed) * Problem * When you try to sign in with facebook in "Flipboard" it's impossible to fill the textbox with your facebook email and password, the textbox it isn't cliccable. I don't know if the same things happen with another website that permits to login with facebook. I attach the screenshot in this message. Tell me if you need more information. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1491125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339792] Re: Panel network icon - too much latency when network type changes
I have the same problem on Meizu MX4 - Arale r.4 -. When I'm connected to wi-fi, then I'm going out of the wi-fi range, the system don't switch to carrier connection. Tell me if you need more details. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1339792 Title: Panel network icon - too much latency when network type changes Status in indicator-network package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in indicator-network source package in Utopic: Confirmed Status in ofono source package in Utopic: Confirmed Status in indicator-network source package in Vivid: Confirmed Status in ofono source package in Vivid: Confirmed Status in indicator-network package in Ubuntu RTM: Confirmed Bug description: Testing image #u122 this morning, I ran into two separate scenarios where the panel network icon didn't always accurately reflect the current network technology due to some kind of latency detecting network changes ( ie. WiFi -> 3G -> WiFi ). Both scenarios were reproduced on mako. Scenario 1: 3G: online WiFi: enabled; connected to AP 1 - display network menu - tap another secure network - tap cancel when Password dialog is displayed At this point the indicator shows '3G' whereas the network menu still shows the original AP 1 as connected. After some period of time ( 10s - 1m ), the icon will change back to show that WiFi is connected. Scenario 2: 3G: online WiFi: connected to AP 1 - go to System Settings::WiFi - click "Previous Networks" - select the currently connected AP/network - click Forget Network - go back to WiFi settings The WiFi settings correctly shows the AP is no longer connected, however again the network icon takes some time ( 10s - 1m ) to reflect the change back to "3G". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1339792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
