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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair wi
Reduced priority for Ubuntu Touch bugs.
** Changed in: bluez (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair with in-
Ok, so it turns out I'm still having some issues with this after OTA-14.
I can still pair the phone with the Hands Free System (HFS), but...
I can only do this if I make the phone search for the HFS. If I try the pairing
by having the HFS search for the phone, I get an error - the PIN (hardcoded t
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 Kernel
Packages
I only paired with very old OTA's. It was when started the E4.5
--
You received this bug notification because you are a member of Kernel
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 upd
@Marco and @Cesar:
Were you able to pair the phone with the car's HFS before OTA9?
If that is not the case, you may wish to track bug #1435040 (if you are not
tracking it already).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
I forgot to say my phone is BQ E4.5
--
You received this bug notification because you are a member of Kernel
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 Sys
With OTA-13 I can't pair to Citroen C4 either.
Cheers
--
You received this bug notification because you are a member of Kernel
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
Statu
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 notifica
YES! Confirming that OTA13 has solved the pairing issue. I can now pair
my BQ Aquaris E4.5 with the HFS without any problems.
Furthermore - once pairing is done, I get the "volume" notification with the
title: "Bluetooth speakers" and I can play music via the car's speakers (albeit
I can't contr
Thank you Konrad!
Eagerly waiting for OTA13.
--
You received this bug notification because you are a member of Kernel
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 Cano
For you to know that silo has landed and will be a part of OTA13
--
You received this bug notification because you are a member of Kernel
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 up
Hey,
Silo 46 is next in queue to land just needs a little bit of tweaking
after the recent landings of Ubuntu System Settings. I expect it to be
the part of OTA13.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://b
Hi Konrad,
OTA13 freeze is tomorrow. Is the fix from silo 46 landing there? The latest
upstream Bluez is mentioned in the landings email, but I didn't see any
references to this issue (but I could have missed it in a previous email).
Thanks.
--
You received this bug notification because you ar
Hey,
We might have fix for issues where the pairing is initiated by the car.
It is currently in silo 46 and we are working towards including it in
the next OTA update.
Best,
Konrad
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
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 2
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,
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
wrote:
> Hi Konrad,
>
> I tried to remove the "Nissan Connect" device, but i got this error: "*Fa
What is your phone?
--
You received this bug notification because you are a member of Kernel
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
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@u
Hellow Konrad:
I enable the developer mode, connect the phone to the computer and write adb
shell in a terminal.
It shows this:
c@C:~$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
c@C:~$
I don't know how to continue.
Chee
My Meizu MX4 is paired with my car (Renault with Carminat TomTom), but
the connection breaks within 2 sec. after connecting.
The sad thing is that it did work a bit before OTA 9.
Will this be fixed by the new silo?
--
You received this bug notification because you are a member of Kernel
Package
Hey,
the procedure is not very difficult and once all the tools are installed it
is straightforward however if you do not feel confident, given that it is
not certain that it will help for issues with cars, I would recommend
waiting till OTA-13.
Best,
Konrad
On Thu, Jul 28, 2016 at 1:05 PM, Marc
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 tr
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
I have an E4.5 and with OTA-12 I can't pair to C4 Citroen.
Time ago I did some tests. When the phone detect a car tried to match it. Now
their names still appear. This is very strange.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
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://bug
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair with in-car hands-
@Stunts: yes, it is the same issue. I can pair the phone, but no audio
--
You received this bug notification because you are a member of Kernel
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 OT
FWIW I still can't pair with my hands-free system.
--
You received this bug notification because you are a member of Kernel
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 i
@higuita:
These are being tracked in these bugs:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578176
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578178
Is it the same issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Hi
After updating to OTA-11, i still can pair with the car, but on incoming
or outoing calls i have no audio. This in a Toyota Prius and before
OTA-9 it worked fine
it looks like this fix did solved the pairing problem, but there is
still something failing in using the audio in the cars
--
You
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair with in-car hands-f
This bug was fixed in the package ubuntu-system-settings -
0.4+16.10.20160609-0ubuntu1
---
ubuntu-system-settings (0.4+16.10.20160609-0ubuntu1) yakkety; urgency=medium
* Fix pin code request is rejected because device is not valid (LP:
#1539158)
-- Konrad Zapałowicz Thu, 09
Yes, you can try it
--
You received this bug notification because you are a member of Kernel
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
Ok, I can confirm that I am unable to pair the phone with that car's bluetooth
system if I have the car's system try to find and pair with the phone.
However, if I let the phone try to find the car's system, pairing works without
issue.
I will retest using 'bluetoothctl' just to make sure I didn'
Interesting, please try.
--
You received this bug notification because you are a member of Kernel
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:
I didn't get to try the silo.
After your comment, I found this very strange and took a better look:
Before, I used to wait for the car to find the phone, and after being
found the car requested me to enter in the phone for pairing (which
failed immediately).
What is occurring now, is that th
@Stunts, no it did not. Have you used the silo for testing or just
OTA11?
--
You received this bug notification because you are a member of Kernel
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
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair with
Did this fix land in OTA11?
Because I can now pair the car's bluetooth system with the phone without any
issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to
Ok, so I think I'm ready to test that silo.
Are these instructions up-to-date, (especially the recovery process)?
https://wiki.ubuntu.com/LandingTeam/SiloTestingGuidelines
Or should I get them from somewhere else?
--
You received this bug notification because you are a member of Kernel
Packages,
Sorry about the delay. I'll try this ASAP, which is likely before the weekend.
I'll report back with results soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to
@Stunts
Have you had time to verify the silo 00?
--
You received this bug notification because you are a member of Kernel
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
** Changed in: canonical-devices-system-image
Milestone: 11 => 12
--
You received this bug notification because you are a member of Kernel
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
I absolutely understand and good luck with finishing all of the updates.
Sounds like you had a lot of fun hacking :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable
Sorry about the lag.
I had a bit of an emergency this weekend, since the HDD on my home
server (which is also my router) failed. I had to find a replacement,
restore from backups, and reinstall the OS.
It was still running Ubuntu 10.04, and migrating to 16.04 is taking
longer than I anticipate
@Stunts
I wonder if you had time and chance to test the possible fix. Let me
know because if it works then we could include it in the upcoming OTA
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.laun
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: Ken VanDine (ken-vandine) => Konrad Zapałowicz (kzapalowicz)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
U
I cannot seem to find the log you requested anywhere.
I found similar files under ~/.cache, but they seemed to be specific logs (for
system updates, for example), not a generic one like the mentioned ones. Wiki
pages also refer the file location you mentioned, but it does not seem to exist
anymo
@Stunts
I have made an improvement and I wonder if it will have any positive
effect on your side. Could you install silo 00 on your device and try if
that fixes the problem for you?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
** Branch linked: lp:~kzapalowicz/ubuntu-system-settings/fix-1539158
--
You received this bug notification because you are a member of Kernel
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-
It seems that I know what is happening and why the pairing is denied. I
think that it is because the device when added to the internal data
structures is not yet fully initialized as the properties are gathered
asynchronously. In the same time the pin request is executed that tries
to use the yet
You are welcome. Let me know if you need me to test something else.
I have also opened 2 new tickets for the 2 "downstream" reported issues:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578176
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578178
--
You received this bug notifica
This is awesome, thank you for performing the test case. Now I know that
the flaw is still somewhere in the Ubuntu System Settings and it is most
probably a race.
As for the other issues that you have observed I would prefer to first
solve the pairing bug and the other you mention will be waiting
@Konrad
Great idea.
Ok, so I went here[1] to get info on running "bluetoothctl" and pairing a
device via this interface.
Here's the result:
Pairing works via "bluetoothctl". I did not have to enter a PIN code as before
and as mentioned in the car's instructions.
After pairing was working, I was a
@Stunts:
There is one thing, however, that you could try on your phone. In order
to make sure that the flaw is still in the Ubuntu System Settings you
could try to pair and connect with the car using the bluetoothctl
commandline interface w/o even opening the Bluetooth settings scope.
In order to
Hey, the Bluetooth bugs with cars are our top priority at the moment and
we are putting the effort into fixing them as soon as we can.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Sorry about the noise, but is there any further info I can provide, or patches
I can try?
This is a critical functionality for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
T
** Changed in: canonical-devices-system-image
Assignee: Bill Filler (bfiller) => John McAleely (john.mcaleely)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable t
** Changed in: canonical-devices-system-image
Status: Fix Released => Confirmed
** Changed in: canonical-devices-system-image
Milestone: 10 => 11
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: bluez (Ubuntu)
Status: Invali
I am attaching the log with OTA10.1.
As far as I can tell, the error is still the same. But all the experience I
have with debugging bluetooth errors is what you see in this bug report.
** Attachment added: "Syslog with verbose bluetooth after OTA10.1"
https://bugs.launchpad.net/canonical-dev
I can confirm that it is not working for me either.
However, there is a small difference from the previous tries:
Now the car system asks for the pin code, and it takes 4-5 seconds before
failing, whereas previously it instantly failed.
I will report back later with the debug log.
--
You receive
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
That's great news!
I'll try it again tomorrow morning and report back.
--
You received this bug notification because you are a member of Kernel
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 OT
It hopefully works in the latest update, v10+
--
You received this bug notification because you are a member of Kernel
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 Can
Fix Released - Is there some silo I can try to test this?
Thanks.
--
You received this bug notification because you are a member of Kernel
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
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair with in-car hands-
This is related to
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair with in-car hands-free system
Attaching a stripped syslog, using the same procedure as done in comment #14.
I hope it contains the required information.
Upon a quick uninformed look, the error seems to be the same as before, but I
may well be missing something.
** Attachment added: "Syslog with verbose bluetooth"
https://
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 it
Problem persists after updating to OTA10.
The symptoms appear to be the same.
I will enable verbose logging again and report back.
This time I will most certainly try any silos you may provide as I have already
learned a bit more abut the system.
--
You received this bug notification because you
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair with in-car hands-f
This bug was fixed in the package ubuntu-system-settings -
0.3+16.04.20160318-0ubuntu1
---
ubuntu-system-settings (0.3+16.04.20160318-0ubuntu1) xenial; urgency=medium
* Process pairing attempts for unknown devices correctly (LP:
#1539158)
-- Simon Fels Fri, 18 Mar 2016 17:56
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: Simon Fels (morphis) => Ken VanDine (ken-vandine)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pa
@Marco
Sorry, I cannot reproduce that. In both my desktop and my phone, pressing
"Enter" on the save dialog will result in saving the file...
You may wish to try "Ctrl+X" instead of "Ctrl+O", to try to work around the
problem, but I'm not sure it will achieve anything...
--
You received this b
@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:
@Marco:
Just "press" "Enter" and the file should be saved. Don't worry about that
message. Nano always asks that question before saving a file.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bu
@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 fo
Humm... I guess I'll have to read a bit on how to do the reflashes.
Worst case scenario I'll have to wait until OTA10, which should be released
somewhere in April IIRC.
I will report back if I make some progress on this front (hopefully with enough
time before OTA10 lands for any further tweaking
@Stunts: Do the following on your HOST system:
$ sudo add-apt-repository ppa:phablet-team/ubuntu/tools
$ sudo apt-get install phablet-tools-citrain
Now connect the phone over adb (make sure developer mode is enabled):
Still from the HOST system:
$ citrain device-upgrade
PLEASE KEEP IN MIND:
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
@kenvandine I guess you need to take this bug to land with some other
fixes?
** Changed in: canonical-devices-system-image
Assignee: John McAleely (john.mcaleely) => Bill Filler (bfiller)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@Simon
Thanks!
Just to make sure: in order to try this, all I have to do is add the PPA to
sources.list and install it using apt-get?
Or is there more to this, such as re-flashing the device with some daily build
image?
If procedures other than adding the PPA are required, would you please point
MP with a possible fix is linked now.
@Stunts: I've put the MP into silo 67 (https://requests.ci-
train.ubuntu.com/#/ticket/1102). Can you install that one on your device
and try if that fixes the problem for you?
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-system-settings (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-system-settings (Ubuntu)
Importance: High => Critical
** Changed in: ubuntu-system-settings (Ubuntu)
Analyzed the latest log files and came to following conclusion about
that is going on here:
The key point here is that the car initiates the pairing with the phone
which then leads to a timing problem in ubuntu-system-settings. But step
by step:
Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]:
sr
** Tags removed: bluetooth
** Tags added: bluetooth-ota10bluetooth
** Tags removed: bluetooth-ota10bluetooth
** Tags added: bluetooth bluetooth-ota10
** Tags added: bluez-touch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubu
Ok, I think I stripped any sensitive information from that log.
I hope it contains what you need.
Let me know if you require anything else (including potential solutions for
testing).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
Sorry about the spam. I forgot the attachment.
** Attachment added: "Syslog with verbose bluetooth"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4579464/+files/syslog_stripped.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages
Nice that you managed to get the log, well done. As for the personal
info I suppose that it is better you remove it however if that is too
complicated just let us know and we will figure something out. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, whic
Ok, I have generated a verbose bluetooth log.
However, this log contains some personal information, that I would prefer not
to make public (email address, partial wifi credentials, etc). How can I make
it avaialable to devs in a more private way?
Here is what I did:
Make "/" rw
Edit /etc/init/b
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 "bluetoothh
@Marco
Woha, I actually asked the askubuntu referenced question. Talk about full
circle.
Anyway, I have gotten my system on rw mode, using "sudo mount -o remount,rw /".
I did this to insert a new ringtone on my phone (which can now be done via the
GUI without changing the image to rw mode).
In
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-wr
@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 me
@Marco Graziotti:
The syslog is nothing special. You can find it in "/var/log/syslog".
There is also this:
https://wiki.ubuntu.com/DebuggingBluetooth
I recently found that documentation, and I am planning on getting that info out
here. But sofar I haven't had the chance to try it.
It will probab
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pa
Attached is the syslog from my Krillin device from a few minutes before
attempting the pairing until failure.
I hope this may help speed things up.
I'm willing to test new stuff to help fix this issue.
** Attachment added: "syslog (trimmed to the last few minutes before pairing)"
https://bugs
1 - 100 of 108 matches
Mail list logo