[One (M7) Android Development] jrandallpierce:
Help with car bluetooth calls

First, thanks to santod040 for this gift.

I've been pulling ROMS from XDA for years and never been moved to register and comment. But this is by far the most stable ROM I've seen so close on the heals of a major release of Android. Kudos.

I really, really want this to be my daily driver. I have had 2 minor apps consistently FC on me, but the main thing that forced me back to KitKat was the behavior of the dialer when connected to my Ford Sync system via Bluetooth. It looks like many people are having similar issues, but some appear to be having success. I'd like to copy their success. Can someone who is able to place and receive calls over a car bluetooth help me figure out where I've gone wrong?

I'm unlocked, rooted, S-OFF running 6.09.401.5 firmware (darkboot), and thus HBOOT 1.54. I've flashed using TWRP 2.7.1.0a.

The first flash I made of this ROM was the 11-18b version. Since I'm S-OFF, I didn't independently flash the kernel. I did do a full wipe before flashing the ROM and GAPPS as they were at that time. With that build, I noticed that volume down+power did take a screen shot. I've since lost that ability, but the main thing was that I never could make a phone call while connected to my car's bluetooth. After entering a phone number, when I click the 'dial' circle at the bottom, my phone does make the call. But the dialer itself disappears (I cannot see the various buttons to mute myself, or the keypad to enter more digits such as joining a conference call, or the sound toggle to go from handset to speaker phone to bluetooth, or even the 'hang up' button). The other person can answer the call, and I can carry a conversation with them through the phone, but I have no way to hang up and the sound isn't through the car's bluetooth speakers and microphone. Also, when I actually paired the phone, the car asked if I wanted to download call history. Normally when I say 'yes', the phone then asks me if I want to allow the car to download that history. With 11-18b, the phone never asked me if I wanted to allow the car to access that history. So I'm not 100% certain the pairing was 'as successful' as with other ROMS using older versions of Android.

I tried build 11-21, with a complete wipe/flash. For good measure, I independently flashed the kernel as well, along with the SuperSU alpha and pie fix. Same result. No ability to make a phone call while connected to the car's bluetooth. This is also the first build where power + volume down didn't take a screen shot for me.

I tried again with build 11-22. Full wipe, flash ROM, kernel, SuperSU (without the pie fix), and even the Lollipop boot animation. Same result with both phone and screen shot button combo.

Just in case it helps track things down, the two apps that consistently FC on me are the Sothwest Airlines app when I click to view my rapid rewards details, and the Trainyard logic puzzle game by Noodlecake. LogCat tells me Southwest is FC due to a drawing issue. Since I had developer options on and Trickster installed (free version) I randomly played around with various graphing settings (force GPU, etc). Nothing allowed me to use either of these two apps. I have no idea if these could be in any way related to the main thing forcing me back to KitKat (the phone). I'm just passing them along in case it triggers someone's memory of a change that enabled the phone.

Can anyone spot something in my setup and install process that would explain why I'm not able to use the phone while connected to the car's bluetooth? Everything else about the ROM has been outstanding for me.

Many thanks,

RP