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!
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:
Struggling with 3 different wired head set mics (inc MDR-NC31E) not working after update to 5.1.1 also really low bluetooth volume (mic) when in the car with hands free. Speakers all work fine wired and Bluetooth
UK sim free, encrypted for work reasons - everything else vanilla
any help gratefully recieved
update - I've now had 2 incidents where when I dialed out the handset mic didn't work, the work around was to tap the output button to turn the phone into a speaker phone for a moment and then back again.
Comment
Having same issue over here, its working with most apss excpet for skype which is a software that I use everyday. Finding no solution yet :c
Googling led me to:
- Downloading Soundabout
- Clearing data of Speed Connect
- Installing older versions of skype
All with no avail :C
please help ;-;
I have the same isssue and it happened right after the update, the workaround did work for a bit but it's getting worse to the point where I have to reboot the phone to get it to work again.
Now I noticed that this only happens after I use SoundCloud to listen to music.
I didn't use it for few days and I didn't have the issue,so maybe some apps trigger this.
Sent from my D6603
It's fixed in the latest update 23.4.A.1.200
Ever since I upgraded to the new ViperOneM8 4.3.0 ROM I have been experiencing bluetooth issues every now and again. For example, I typically have my Moto360 watch and my Plantronics earpiece connected. In the middle of a call it will do weird things like spudder some crazy noises really fast for about 10 seconds then disconnect, or just plan disconnect. When it does disconnect, my phone still thinks the earpiece is connected and does NOT switch back to phone headset (like it used to). Then if I wait another 10-30 seconds it will reconnect and pick up the call on my earpiece again.
Anyone else having bluetooth issues on this ROM? It's a brand new install with nothing other than the basic google apps (and a few remote apps like LogMeIn, TeamViewer, and RD Client).
arvo.bowen said:
Ever since I upgraded to the new ViperOneM8 4.3.0 ROM I have been experiencing bluetooth issues every now and again. For example, I typically have my Moto360 watch and my Plantronics earpiece connected. In the middle of a call it will do weird things like spudder some crazy noises really fast for about 10 seconds then disconnect, or just plan disconnect. When it does disconnect, my phone still thinks the earpiece is connected and does NOT switch back to phone headset (like it used to). Then if I wait another 10-30 seconds it will reconnect and pick up the call on my earpiece again.
Anyone else having bluetooth issues on this ROM? It's a brand new install with nothing other than the basic google apps (and a few remote apps like LogMeIn, TeamViewer, and RD Client).
Click to expand...
Click to collapse
Mods should probably move this to the Q&A forum.
In general, I had weird bluetooth issues with audio. After flashing HK BS switcher INCLUDING the ADSP, all my issues went away. You need to be S-OFF, if you're not, don't even bother.
You want version 4.3.1 of this mod, considering you're running Lollipop.
Choose the Verizon install, not the ViperOne or anything else (even though you have Viper rom)
It's your choice what sound system you want. HK or Boomsound. I chose HK but that's just me.
I'd make a nandroid and give it a shot. Not sure if it's going to work, but can't hurt, especially if you make a nandroid.
http://forum.xda-developers.com/htc-one-m8/development/mod-audio-hk-bs-aroma-switcher-4-1-0-t3035354
Hi all,
Recently upgraded to Cyanogen 13 (marshmallow) on one plus one and since update Bluetooth connection to car head unit is not stable. I can receive calls fine but if I try to make calls the phone reboots. Happens less if original one plus flip cover is open (sensor not blocked), didn't happen in 12.1 (Lollipop).
Have done the forget and re-pair on both car head unit and one plus, clear cash/data and have done factory reset, nothing works.
Seems to be worse when playing podcasts via BT, not an App problem as all was fine before update.
Have looked through previous posts on a lot of forums, looks like this is not restricted to just oneplus and may be a marshmallow issue. Anyone else experience this and come up with a fix?
Cheers.
I have connection issue too in car, connects for 2 seconds then drops, cannot hold the connection. It worked before I upgraded to COS13. Only thing I've seen is report the bug to developers and hope they come out with a fix..
jira.cyanogenmod.org/browse/BACON-4733
Same for me. Buetooth connection in CM13 is very bad. Phone reboots... Worked fine in CM12.x.
jlkahn said:
Same for me. Buetooth connection in CM13 is very bad. Phone reboots... Worked fine in CM12.x.
Click to expand...
Click to collapse
Same for me, the phone reboots if any call is made through Bluetooth & Car when the flip cover is closed. Looks like a bug is reported in jira, but closed with description as invalid.
Anyone knows workaround?
There is a small magnet about 45mm up and 10 mm in from the bottom left corner of the case, (looked at when the case is open) this interacts with a hall effect device. What I did was tape a piece of mu metal 10mm x 40mm over the magnet in the cover so that the phone doesn't turn the screen off or on when the cover is opened. It needed a bit of experimenting as the first time I tried it, enough magnetism leaked after 30 mins to activate the sensor.
[email protected] said:
Same for me, the phone reboots if any call is made through Bluetooth & Car when the flip cover is closed. Looks like a bug is reported in jira, but closed with description as invalid.
Anyone knows workaround?
Click to expand...
Click to collapse
Ran into this on my Samsung S3 running CM13. (Seems to be a core CM13 issue....) Only a problem on my phone when connecting to headphones and speakerphones that have BOTH media AND phone profiles.
The workaround (not great, but better than a rebooting phone) is to disable one of the two profiles in the device-specific Bluetooth settings. Then it only accepts/makes calls -or- plays music/audio.
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?