I have looked for information on my problem. But haven't found any anywhere else.
I'm using a Nexus 5, running the new version 6.0. I bought a jawbone UP Move fitness tracker. And I can't seem to get it to connect through bluetooth. I know bluetooth is working on my device, because I was able to connect my bluetooth headphones to my Nexus 5. The Up Move shows up on my Nexus 5, but pairing is rejected.
I was able to successfully pair the UP Move to my wifes Sony Xperia t2 ultra running Lollipop. So I know it is neither my Nexus 5, or the device.
The only thing I cant think of, is either the app or device is unsupported, or something in the new version of Android.
Is there any known issues with bluetooth in android 6.0 that anyone knows of? Or has anyone came across this issue with the jawbone UP Move and figured it out?
Related
So I got my Nexus 5 today and have spent most of the afternoon tinkering with it. When I came to drive home, I paired it with my car (2012 Holden Cruze) and just like my Nexus 4 before it, it tells me there is no phonebook available, so I can't call anyone from the car. Also the car's call / disconnect buttons don't work.
I had exactly the same scenario with the Nexus 4 and ended up running CM10 on it, as bluetooth worked fine in that ROM. Clearly, CM has some different bluetooth code ..... my question is, does anybody know how to make this work? Can we somehow extract the bluetooth code from a CM10.2 / 11 ROM and install it into stock? I would really like to stay on stock.
I am interested in finding this out too, I have tried all sorts on my Nexus 4 but with no success. I don't seem to get the request from the car to access the phonebook on stock 4.2, 4.3 or 4.4 but get it straight away with CM10.1 :crying:
I wrote an Android application that control an RC car. The phone and the car communicates by bluetooth. I have tested the application with several Android based phones. The Os version was 5.0 and lower. I had problem with only one phone. That was a Nexus 5 with the newer version of Android. After the new update arrived to my phone, i just updated my phone. I changed 4.4.2 to 5.0, I have an LG G3. Unfortunatly after the update the problem occured on my phone too. The problem is that after the phone connected to the car the data send is getting laggy and slowing down and the car cannot be controlled, sometimes it work fine for few seconds. On every other phone I have tested the application it worked fine.
Anybody knows anything about that problem?
Thank
Hi
anyone else fancing problems with a Jawbone Device and Marshmallow?
I cant get my UP2 connected to my Nexus 5 with Marshmallow. I reflashed Lollipot Image - it worked. Other devices like my car or bluetooth speaker worked flawlessly.
I already contacted the Jawbone support, but no response.
Michael
What is the source of the ROM you installed? The ROM distributed by google works without any problem.
Jawbone has acknowledged this as a problem and is doing nothing to fix it. They're blaming Google because this issue exists with many types of devices, including fitbit, car audio systems, etc., and Google has yet to release a fix.
You won't get any help from jawbone other than hearing them tell you to turn on location services or to "use a supported device".
Hi,
I use 3 bluetooth devices at home. With my previous build (rooted and tweaked Kit Kat) everything worked just fine.
I flash the new Marshmallow, root it and tweak it a bit (nothing major) like I did before but now my Bluetooth can only see one device out of my 3.
Doing a Google search I see some problems but nothing recent and no possible fixes.
Anyone else have this problem and get it fixed? Anyone have any thoughts?
It's lonely being the only one.
You're not the only one - since upgrading to STOCK Marshmallow and now 6.0.1, if my phone is more than 6 INCHES from my headset, any of 5 of them, the phone will connect / disconnect every 20 to 70 seconds. If the phone is in my left pocket with the headset in my right ear, I can't connect the headset AT ALL! I'm gettin' my HATE on for Marshmallow in a big way!
Hello,
I've got a new Dasiata PX5 with Android 8.0 and 4GB of RAM in my Honda CRV-2012.
Everything is OK exect the Bluetooth is not working. It can not recognize any device. Also no device can see the radio (tried Galaxy S8 and iphone 6).
I tried changing the bluetooth adapter in Factory menu then reboot, but no one worked.
Since bluetooth is 100% essential for me, any help would be appreciated.
No device found:
https://forum.xda-developers.com/picture.php?albumid=14759&pictureid=57065
All types BT tried:
https://forum.xda-developers.com/picture.php?albumid=14759&pictureid=57066
Config:
https://forum.xda-developers.com/picture.php?albumid=14759&pictureid=57067
https://forum.xda-developers.com/picture.php?albumid=14759&pictureid=57069
I had the same issue when upgrading from Android 6.0 to 8. Have you contacted Dasiata about the issue?
If unable to resolve, consider downgrading to Android 6, at least to test your bluetooth. You can always go back to 8.
marchnz said:
I had the same issue when upgrading from Android 6.0 to 8. Have you contacted Dasiata about the issue?
If unable to resolve, consider downgrading to Android 6, at least to test your bluetooth. You can always go back to 8.
Click to expand...
Click to collapse
Thx for you help. Can i downgrade juste like a regular update? put on sdcard and use factory update?
Has this issue been resolve? I bought Anroid 8.0 Radio from Dasaita too and Bluetooth is not working well.
Hello, no solution yet
Let me know if you find one!
Bluetooth noise
I have recently installed an HA2102-V840-8 "10.2" HD Touch Screen Octa Core Android 8.0 car GPS player 4G RAM + 32G autoradio" in my Lancer. It's an awesome unit, looks great and has great features.
The only problem is digital/electronic noise whenever there is audio playing. The noise is only present when my phone (or any phone) is paired with bluetooth and some/any audio source is active. It happens with usb audio, radio and phone. It stops as soon as the phone is unpaired/bluetooth turned off or music is paused. It also stops briefly between music tracks. Has anyone else encountered this?