Bluetooth different in Stock vs Custom Roms (Juicy, MightyMike, etc)?

[nbaj2k]

So far for any of the custom roms I've tried (such as Juicy or MightyMike), I have had issues when using my Parrot 3200 car kit. Calls will end right after they are connected or a few seconds in. They ring once and then the call just ends. I went to reflash my phone back to stock and bring it to the store to be looked at, when I realized the for some reason the stock rom does not have this issue at all!

This is really weird to me as I didn't think there was a difference in bluetooth between the stock rom and the custom roms. If anything I thought it should work better! I love all of the stock roms, especially those with the Sense UI interface. Does anyone know why this would happen? The weird part is it seems that only my car kit is having this issue, as I've tried other regular bluetooth headsets and they seem to work fine. I thought it might be an issue with the Parrot 3200, but it works flawlessly with a stock rom.

Could there possibly be a tweak in the custom rom that I could try to change back in order to try to get this to work? Maybe a change in the registry or trying to load a cab or something?

I had thought this might be related to the bluetooth problems others were having, but since it is working fine in the stock rom and the issues seem a little different, it doesn't look like it.

Thanks,

~J

[WisdomWolfX]

The newer custom ROMS use updated drivers from the USC Core. It's odd that you are having issues with the updated driver as it is the only thing that has fixed BT for most of us.

[nbaj2k]

Is there a way someone can post the old drivers so that I could try those with the ROM to see if they work any better and if that fixes the problem?

[WisdomWolfX]

IIRC, drivers have to be cooked in. You can try one of the older MM or Juicy builds and see if that helps though. They only recently (last week) switched to USC core.