Related
Hi all,
I wonder why no one is asking or investigating the AVRCP issues on ROM's without Sense? It looks like something is missing in those roms that can be found inside Sense ones.
The bt call function is working as designed but play/pause/next/prev doesn't.
Any ideas?
The issue is that HTC have used their own bluetooth stack in their Sense based roms.
This stack supports the features that you are talking about.
Unfortunately, stock roms use a different stack which do not have the same features as the Sense stack.
This isn't an issue only on the HD2.
Can we get that stack and put it to nonSense roms?
AVRCP has been working on every CM6 build I've tried until recently. Just over the last week or so since I've updated to more recent nightlies I've found its stopped working. I'm currently using ginger_hd2 and it doesn't work. Also the mdj aosp gingerbread doesn't work and mdj streak ram v0.5. All the builds I've tried today!
I was using passion nightly 270 (or bravo, can't remember) and that worked fine.
Sent from my HTC HD2 using XDA App
Never worked for me since I tried HyperDroid and other roms.
I'm going to revert back to my old build later today to see if it still works. I thought it might be a problem with my headset as I dropped it the other day but I tested it last night with Windows Media Player on my PC and it worked OK, switching tracks, play, pause, etc.
Will let you know how it goes.
Sent from my HTC HD2 using XDA App
OK - It definitely works with my previous build.
This build is based on the Passion nightly CM6.1 v270
As I say, I've had it working on pretty much every build since the beginning of Android on the HD2 - it's only stopped working on the Gingerbread-type builds.
ie. It doesn't work on MDJs actual 2.3, or the Ginger_HD2 based on 2.2.1 with Gingerbread-style notifications, etc.
I can't work out if it's coincided with me using builds which have the newer initrd.gz...
Let's hope someone who knows about this stuff reads this thread!
What is this build with CM 6.1? Can you link it?
http://www.multiupload.com/FQCU3UV070
Try this... this one's based on 293 nightly.
Mine was a hybrid I kinda created myself using michyprima's nightly build v4, then incorporating the passion 270 files. If you look at this thread:
http://forum.xda-developers.com/showthread.php?t=824601
It'll explain how to do it...
OK, well I did some trying to fix it using MDJs Gingerbread v0.8 but no joy.
I tried replacing the three bluetooth libraries (libbluedroid.so, libbluetooth.so and libbluetoothd.so) with the working ones from my build but that didn't work.
I also tried replacing the AudioBTID.csv file as it had some slight changes and whilst it didn't fix the issue, it doesn't seem to have broken anything.
I'm currently looking at the bluetooth conf files in /system/etc/bluetooth to see if there's any differences there... think we need some dev help on this one though - I'm pretty much at the limit of what I can do....
Nope, no difference in the conf files. Also changed over the two .so files in /system/etc/lib/bluez-plugin
Again, this didn't work but didn't seem to break stuff!
That's bad. Even Sense roms has problems with media controls profile such as connecting automatically to Phone Audio only.
I feel like 1 from 1000 use it, so nobody cares
Just in case anyone finds this thread again...
MDJs NAND CM7 builds now have AVRCP working again. If you want a build without sense but with this working I suggest you try them! I'm a happy camper again!
Sent from my HTC HD2 using XDA App
Any updates on AVRCP on our devices? I am on CM7 (BoyPPC HoneyComB v31), and AVRCP does not work Do the GB sense ROMs have AVRCP capability?
I tested a few SD ROMS and AVRCP works with:
RAFDROID_HD_SD_4_2 (Sense)
AmeriCanAndroid (Gb)
JaguarMIUI-V11 (Gb)
Hey all,
Recently got my n4 and am currently running cm10 nightlies on it, but today I picked up our new car (Hyundai i30 premium) which has bluetooth built into the audio system and I can't get my n4 to sync with it properly. My partners Desire HD syncs no problems and all her contacts phone book everything shows up fine. My n4 wouldn't even sync originally then I just kept retrying and eventually it synced but nothing really works, music won't play through the speakers (the audio system just sits there waiting for music and nothing happens) my phonebook etc don't show up (after me allowing them permission) I can't even make calls.
I have heard that the n4 has some bluetooth problems but nothing this bad, anyone have any suggestions that I can try? Happy to go to another ROM if that will help??
Thanks,
Hosh
this build has serious BT issues. i can't even find a mouse that works. wait and see what the 4.2.2 update brings.
I own a Hyundai Elantra GT which is the US version of the i30 - I didn't seem to experience any issues when I paired it this morning, but I"ll double check when I get out of work this afternoon that the contact sync is working. I am, however, on the stock rom.
I own a 4 day old Dodge Journey and it pairs with no issue to Uconnect.
Try a different rom?
If thats not it, then its your hardware.
The new bluetooth stack in Android 4.2 is causing a lot of issues. Personally, I don't have any problems connecting to UConnect (Jeep Grand Cherokee) or my SmartMini (bluetooth music streaming).
I am waiting on delivery for my MetaWatch, there have been complaints that 4.2 isn't connecting well with it but I guess we'll see. CM10.1 users don't seem to have as many problems. I'm running Xylon w/ Franco r53.
I had the same problem with Chevrolet captiva until I have installed custom ROM and is working perfect now.I have tried every custom ROM and is OK with all.
I have this problem but there is a way around it (for me anyway).
Download Bluetooth file transfer from the market.
Delete the connections with your car. Both on the phone and your car.
Open Bluetooth file transfer. Select the Bluetooth screen.
Make a connection. The default android Bluetooth will ask for a password. Don't enter it. Instead go to your recent apps and select Bluetooth file transfer. Put the password in the request screen the app supplies.
Bluetooth file transfer should pair the devices and make a connection.
Once done. Kill Bluetooth file transfer as you won't be able to exit.
You can then uninstall Bluetooth file transfer if you want (although I tend to keep it for when I change ROMs or have to do a factory reset etc).
Hope this works for you
Sent from my Nexus 4 using xda premium
Hey all,
Sorry for the late reply, been away for the weekend. Thanks for all the advice, tried them all and no luck. Will try out a mates n4 tomorrow and see if he has any luck syncing with the car, if he does might just flash roms again.
after flashing a new rom, I had problems pairing w/bluetooth and connecting w/wi-fi. I fixed the problem by restoring my system settings w/titanium backup thanks to someone's suggestion.
Seems the only thing that worked for me is when it asks to sync my phonebook I have to say no, if I say yes it seems to freeze the whole thing. Makes me think if I click yes I might just need to give it 10-15 mins to sync, might try that tomorrow. But for the moment at least it's half working!
Hi I have searched for answers but am stumped now.
I am using Google Play Edition 06-08-2014 by Danvdh and I love the rom but when using the phone in my 2011 Mercedes Benz the phone was randomly rebooting on the 4.4.2 rom.
After updating to 4.4.3 rom the bluetooth connection drops out sometimes when trying to make or receive a call, it eventually reconnects but it is very frustrating. I am even considering moving back to my iphone if I can't sort this one out.
Any advice would be greatly appreciated.
Cheers
The first paragraph of the rom you are using:
This is the latest build for the I9505-G Google Edition S4 official from Google/Samsung, I have made quite a few optimizations to the ROM and added the tools necessary to give it the features (100% working features that is) of an AOSP ROM, Google edition does not use open source proprietary which mean's Bluetooth, and most importantly the camera will work way better out of the box since Samsung builds this ROM (Full HDR support, 1080p video recording, no green lines on the front cam).
I don't think there is much you can do. Maybe a different kernel would work, but I doubt it.
If you want working bluetooth you should flash an TW based rom.
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Blazing angel said:
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Click to expand...
Click to collapse
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
BassBlaster said:
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Click to expand...
Click to collapse
It is a rev_11
paul c said:
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
Click to expand...
Click to collapse
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Mine is also a rev11, 303k. I guess that rules out hardware issue
Blazing angel said:
It is a rev_11
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
I'm experiencing exactly the same problems than Blazing angel.
Bluetooth is unusable in my car, "Unfortunately, the process com.android.bluetooth has stopped" being displayed repetitively.
I suspect it's not hardware related as I do not have problem using the stock or paranoid ROMs. Unfortunately, my favorite ROMs (AOKP, CN or Carbon) are causing problems.
Do you think it's possible to pickeup some files in the paranoid files and inject them to Carbon to solve the problem ?
Thanks in advance for your help !
paul c said:
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
Click to expand...
Click to collapse
Great ! I was able to bypass my bluetooth problem using this Android 4.4.4 rom, without loosing great features of Carbon or Pac-ROM ! :victory:
Thanks for sharing this ROM Paul ! :good:
Hi!
I have been running CM for years now. For the first time the nightlies aren't working good for me. The cm-11-20140804-NIGHTLY is working great, but as soon as I installed any of the newer my bluetooth starts disconnecting. For instance, the cm-11-20140817-NIGHTLY caused the phone to restart several times a day. It also caused the bluetooth to disconnect and the wifi acted very strange.
The latest rom I tried was cm-11-20140831-NIGHTLY. The bluetooth disconnected almost immediately and I went back to 0804.
Any ideas?
Thanks in advance!
// Anders
str3der said:
Hi!
I have been running CM for years now. For the first time the nightlies aren't working good for me. The cm-11-20140804-NIGHTLY is working great, but as soon as I installed any of the newer my bluetooth starts disconnecting. For instance, the cm-11-20140817-NIGHTLY caused the phone to restart several times a day. It also caused the bluetooth to disconnect and the wifi acted very strange.
The latest rom I tried was cm-11-20140831-NIGHTLY. The bluetooth disconnected almost immediately and I went back to 0804.
Any ideas?
Thanks in advance!
// Anders
Click to expand...
Click to collapse
Hi,
I've made similar discoveries regarding only bluetooth connections. :crying:
I'm using nigthlies for a long time.
With cm-11-20140724-NIGHTLY-jflte S4 GT-I9505 and my car (BMW E61, 2006) connects perfectly. Later nightly roms aren't working with my car.
Any hints?
rainer777 said:
Hi,
I've made similar discoveries regarding only bluetooth connections. :crying:
I'm using nigthlies for a long time.
With cm-11-20140724-NIGHTLY-jflte S4 GT-I9505 and my car (BMW E61, 2006) connects perfectly. Later nightly roms aren't working with my car.
Any hints?
Click to expand...
Click to collapse
I have the same problem, but can't find cm-11-20140724-NIGHTLY-jflte, can you share it.
Tks
viincrt said:
I have the same problem, but can't find cm-11-20140724-NIGHTLY-jflte, can you share it.
Tks
Click to expand...
Click to collapse
You can use the latest Snapshot: cm-11-20140804-SNAPSHOT-M9-jflte.zip
In this one bluetooth is working correctly.
You can download at cyanogenmod.org
Regards,
Rainer
Same thing on SPH-L720
I noticed that the same thing happened with my Sprint Galaxy S4 (SPH-L720), on Cyanogenmod and Paranoid Android. I didn't even think to flash an older version of the ROM. Guess I'll do that since I miss having Bluetooth connectivity in my car.
Does anyone know why this started happening in recent builds, though? I haven't seen anything about it.
rainer777 said:
You can use the latest Snapshot: cm-11-20140804-SNAPSHOT-M9-jflte.zip
In this one bluetooth is working correctly.
You can download at cyanogenmod.org
Regards,
Rainer
Click to expand...
Click to collapse
Latest snapshot is cm-11-20141009-SNAPSHOT-M11-jflte and still has the problem. Connects but disconnects after a couple of minutes. Both in my car and my wife's car. Very annoying.
rainer777 said:
You can use the latest Snapshot: cm-11-20140804-SNAPSHOT-M9-jflte.zip
In this one bluetooth is working correctly.
You can download at cyanogenmod.org
Regards,
Rainer
Click to expand...
Click to collapse
hi
i have installed the dirty unicorn rom, and it works good, but the problem is the batery life, only one day.
now i have tested the cm-11-20140804-SNAPSHOT-M9-jflte.zip, and it works with problems, sometimes it dont disconect from the car and on the nest time it does not connect. normaly when it works, only can do on call the second only work after disable and enable the bluetooh.
tks
viincrt said:
hi
i have installed the dirty unicorn rom, and it works good, but the problem is the batery life, only one day.
now i have tested the cm-11-20140804-SNAPSHOT-M9-jflte.zip, and it works with problems, sometimes it dont disconect from the car and on the nest time it does not connect. normaly when it works, only can do on call the second only work after disable and enable the bluetooh.
tks
Click to expand...
Click to collapse
Has anyone tried the newest M12 snapshot to see if resolved their issue? I have the same issue on multiple M11 snapshots.
I have the last mahdi rom and use a bluetooth speaker for my bath. I don't have this problem. I don't know maybe they have another bluetooth driver or something
smurof1 said:
Has anyone tried the newest M12 snapshot to see if resolved their issue? I have the same issue on multiple M11 snapshots.
Click to expand...
Click to collapse
I just updated to the M12 Snapshot and managed to reconnected to my car about 15 times without any issues. I'll post back if I see other issues with this update.
CM11 M12 Bluetooth/WiFi Issue - Fix?
Apologies for the hijack, as this may not be entirely similar to the OP, but the solution could help.
I was experiencing wifi disconnects when I would toggle on bluetooth, when using CM11 M10 or higher.
With a clean install of Cm11 M12 (reset/new user + formatted /system), I finally worked up the courage (and kinda' understand what it is I have done) and updated the bootloader (not sure if necessary) and the GSM/LTE modems to the latest - XXUGNK4 - from here http://goo.gl/RziHz1
I was previously on XXUFNC6 (from the stock ROM), went to XXUGNI2 (closest to my country based on this thread http://goo.gl/TQi3gz) but that did not work either. So I went straight for the jugular, and installed first the bootloader, then the dual modem pack for XXUGNK4.
So far testing has yielded positive results.
Streaming audio (320mbps) via BT plus downloading some ISOs from MS (speed between 550KB/s to 1.01MB/s), and so far no issues.
Not saying this is going to work for anyone else, or solve the OP's exact issue, but it seems to for me.
-P