[Droid Ultra Android Development] GeneralSchnook:
Bluetooth Calls on 2015 Jeep Grand Cherokee Uconnect

TL;DR

Bluetooth calls on Jeep GC 2015 causes Lineage with GAPPs to soft reboot phone. No audio goes through bluetooth.

Wow, glad I found this thread. A little bit of background:

I got my xt1080m Droid Maxx a few years ago when they were still new, and immediately wished I had an unlocked bootloader. At the time, was locked down and didn't have root or anything. Oh well, phone worked good enough. Froze some bloat apps and installed a custom launcher and all was well.

I'm addicted to root, and couldn't resist it. Started following some of the happenings with JCase and Sunshine, plus a few blackhat/defcon talks about the particular exploit being used to bypass the locked down bootloader. Sounded promising. When the OTAs came, I disabled the update app and was determined to sit on my unpatched phone until Sunshine would work (basically just needed a root 'sploit).

My impatience led me to seek out and pay some sketch Chinese dude for an unlock code. Didn't work and now the Chinese have my IMEI. At least I got a refund...

After a few months of waiting on my old version, my patience payed off!! Rooted the phone, ran sunshine. BAM. Bootloader unlocked. At this point life got busy, and I had a working phone so no further action for a good chunk of time (couple of years at least). Keep in mind I was sitting on the unpatched version of the phone the whole time, and at one point I ran out of space from d/l'ing too many things, so just last week I was sitting on 64+ un-updated android apps too. Not a very good security practice...

Enter October 2017. I finally decided to get my act together with this phone. Figured enough time has passed that there would be a few decent ROMs for this thing. Kind of surprised there aren't more, but I guess with the amount of work it took to unlock the bootloader, not terribly surprising. Glad to see this has been worked on relatively recently.

Alright, here's what I have done so far:

Factory wiped my old, un-updated phone from 2013 or however long ago it was. Just used stock recovery for this...

Took all OTAs to make sure all the modems and such were up-to-date. To put in perspective how terribly out-of-date my phone was, I think it took 7 OTAs before I was on SU6-7.7, lol

Wiped in stock recovery one more time, just for good measure

fastboot installed TWRP 2.8.4.0

wiped via TWRP (it failed, probably because whatever the stock recovery does to wipe confused it or something)

let phone boot to "initialize" the modem or whatever (I am kind of a n00b on how android firmware and modem stuff actually work together)

wiped in TWRP (it worked this time)

let SU6-7.7 boot one more time. Checked the modem version to make sure everything was good (real reason I wiped was because I forgot to do it the first time, lol). I noticed that even though I had applied 7 OTAs and wiped twice, the root stuff still was there from when I sunshined way back years before this (so I guess I was working with a dirty install at this point).

uploaded 8Oct Lineage from this thread to internal storage along with GAPPS stock.

wiped system,cache,dalvik,data. Applied lineage zip. Wiped Cache/Dalvik. Applied GAPPS. Wiped Cache/Dalvik. Booted

noticed right away GPS did not work. Wiped modemst1 and modemst2. Gps works now.

paired bluetooth to my car. Used GAPPs dialer to make a call. No sound through car. Car suddenly is disconnected from phone. Try to end phone call (Red phone hang-up icon). Phone becomes unresponsive. Soft Reboots. Crap, everything else works perfectly. BUT IT IS A PHONE AND IF IT CAN'T MAKE CALLS, DEFEATS THE PURPOSE :laugh:

clean install lineage again but with GAPPS pico (maybe it's GAPPs dialer's fault?). Same thing.

Okay, so now that I am here, I decided to RSDLite the thing to the stock CFC SU6-7.7 zip file thingy (btw, where do these zips come from, and how do we know that there isn't a little extra something-something added to, idk say the system.img for nefarious purposes?). Running fully updated stock again. Bluetooth works with my car just fine.

My next step is to repeat the whole process from a clean install (probably going to stick with pico for now, or maybe even try without GAPPs to see what happens). I have already looked at a logcat, but it wasn't terribly helpful (at least to me, but maybe I don't know what I am looking for). If it happens again I will probably post the relevant logcat stuff here.

But for now, any ideas?? If I can't figure this out, probably gonna upgrade. Any recommendations for good, Verizon, root/bootloader unlocked friendly phones?