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
@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
@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:
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
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 "conne
@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 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
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
@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
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
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: marco 1976 F pulseaudio
/dev/snd/controlC0: marco 1976 F pulseaudio
/dev/snd/controlC1: marco 1976 F pulseaudio
/dev/snd/controlC2: marco
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650660/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1407505
Ti
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650659/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/14
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650661/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650663/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1407505
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650666/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650667/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650665/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650671/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650669/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650662/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650668/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650664/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1407505
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1407505/+attachment/4650670/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1407505
I'm was running: "apport-collect 1407505", all of my comments up there are
autogenerated by apport-collect, I'm sorry for the quantities.
I have updated from Ubuntu 15.10 to Ubuntu 16.04 LTS and now I'm affected from
this bug.
The kernel version is: 4.4.0-21-generic
Running: dmesg | egrep 'drm|
It's necessary to open a new bug report?
Because this report it's for Ubuntu Utopic (no longer supported) and
Ubuntu Vivid (that it's supported yet).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
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
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
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
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
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
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
>
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
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
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
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
** Attachment removed: "AlsaInfo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650659/+files/AlsaInfo.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650660/+files/CRDA.txt
** Attachment remov
I followed your instructions, and now it works.
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1214348
Title:
package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to
ins
In a forum where I partecipate we solved the problem.
We found that the problem is caused about a file called "blacklist-bcm43.conf"
that put all the broadcom driver in blacklist after the installation (that no
happened during live cd session).
This is the cause of the issue.
You have to move
I have the same problem on Ubuntu 13.04 (amd64). But when i try to
uninstall broadcom-sta-common and bcmwl the terminal answer me:
***
paola@paola-Inspiron-1520:~$ sudo apt-get remove broadcom-sta-common
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura infor
Public bug reported:
I get this error every time I turn on the computer.
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architectu
40 matches
Mail list logo