[CLShifter]

I posted about this in an existing thread but figured I'd give it its own in case others run into the same problem.

My Latitude has the uConnect 5.0, and for the most part everything works great. However it's acting strangely with regard to text messaging on my phone (Motorola Droid Turbo, Android 5.1 Lollipop, Verizon)

When I initially paired the phone, the uConnect messaging function worked perfectly. It would read incoming texts, and I could use voice commands to reply using one of the canned responses. It worked really well. However, I found later that when I got in the Jeep and the phone connected, the messaging button on the screen was grayed out. When I pressed it, a message came up that said "Texting is not supported on this phone."

So I deleted the device and re-paired, and texting started working again, until the phone was disconnected and reconnected, and then went back to unsupported.

So obviously texting IS supported, if it works once there's no reason for it to quit working. I saw it work, I used it!

I had a chat session with Jeep Customer Help and here's what I got:

Delores: I am showing on the http://www.driveuconnect.com website that the only software that is 100% compatible with your Motorola Droid turbo phone is 4.4.4 you have a software version of 5.1.
Delores: If your phone is not 100% compatible with the 5.0 radio then some features will work and some will not.

Christopher Scott: Understood, but why would it work perfectly when the phone is first paired, then stop working when disconnected and reconnected. Obviously the feature has support if it works initially

Delores: because the software is not 100% compatible if you go to our website http://www.driveuconnect.com and view that site for pairing your phone when you click on your phone it will show the software that is compatible yours is not and so this is why it is doing what it is doing. Sometimes it will work and sometimes it won't if you had the droid turbo with the software 4.4.4 then it would not do thata.
Delores: You may keep checking that website for when they update the software to the 5.1 which you have on your phone. Then it would function at 100% capacity.

This makes no sense to me. The functionality is there. I could use it if I wanted to re-pair my phone every time I get in the car.

Has anyone else run into similar weirdness?

 

[Thorpeland]

Are they saying this feature is only supported by Android version 4.4.4?? A version most phone are no longer on? Good grief. I use Google Hangouts for all my texts. Which is data based, so the car doesn't see texts send/recieved through that. But i'll try to send a few using SMS and see if get the same results. My phone is running 5.1.1

 

[Sammydni]

Mine is running on 5.0.1 and I have had no issues.

 

[raz-0]

I posted about this in an existing thread but figured I'd give it its own in case others run into the same problem.

My Latitude has the uConnect 5.0, and for the most part everything works great. However it's acting strangely with regard to text messaging on my phone (Motorola Droid Turbo, Android 5.1 Lollipop, Verizon)

When I initially paired the phone, the uConnect messaging function worked perfectly. It would read incoming texts, and I could use voice commands to reply using one of the canned responses. It worked really well. However, I found later that when I got in the Jeep and the phone connected, the messaging button on the screen was grayed out. When I pressed it, a message came up that said "Texting is not supported on this phone."

So I deleted the device and re-paired, and texting started working again, until the phone was disconnected and reconnected, and then went back to unsupported.

So obviously texting IS supported, if it works once there's no reason for it to quit working. I saw it work, I used it!

I had a chat session with Jeep Customer Help and here's what I got:



This makes no sense to me. The functionality is there. I could use it if I wanted to re-pair my phone every time I get in the car.

Has anyone else run into similar weirdness?

No, but there explanation is possible. Google really kinda sucks at not changing the way their os works from version to version. The degree to which they have both fixed, broken, refixed various active sync, email, and calendaring bugs is maddening. And much like they are starting to screw over active sync because they are making their own standard for google apps, it wouldn't shock me if they do similar now that car play is coming.

Don't even bring up the gmail api. That thing seldom functions as published, and changes are seldom noted in docs before being put in production.

 

[plmorrell]

Are they saying this feature is only supported by Android version 4.4.4?? A version most phone are no longer on? Good grief. I use Google Hangouts for all my texts. Which is data based, so the car doesn't see texts send/recieved through that. But i'll try to send a few using SMS and see if get the same results. My phone is running 5.1.1

That's odd cause I use Hangouts for my SMS and the Renegade sees & reads them just fine. I have yet to have to respond to any though.

ETA: I'm on an LG G3 Android 5.0.1

 

[CLShifter]

After searching around the Android forums I found a similar problem with a proposed solution that seems to have worked. First, I deleted most of my message backlog. I then un-paired all devices, cleared the Bluetooth cache, and restarted the phone. I re-paired with uConnect, and texting is now working and seems to keep working after a reconnect.

We'll see what happens when I re-pair my BT earpiece and OBDII reader.

So i guess we've learned that we shouldn't be surprised if the Customer Care people are working with outdated information, and don't' have access to anything additional other than what's on the website for all to see. I suspect the 4.4.4 compatibility listing just hasn't been updated.

 

[Thorpeland]

That's odd cause I use Hangouts for my SMS and the Renegade sees & reads them just fine. I have yet to have to respond to any though.

ETA: I'm on an LG G3 Android 5.0.1

Reeeeeeaaaalllly!!? Hhmm... I hadn't seen any come through the Uconnect system. I figured since it was technically data and not normal text SMS, the system wasn't seeing it. I had just accepted that wasn't going to work. I'll try the steps mentioned below to see if I can get it to work now!

 

[toohappytocare]

Here's the thing. When they say it's not supported, doesn't mean it doesn't work. It means that they haven't fully tested it and certified that it works. Some features might, and some might not. Some might work intermittently.

When I get my Rennie, I'll dig into this more. I'm on Android 5 as well.

 

[roachgr]

I'm on android as well and everything works except my phonebook. uConnect will not download my phonebook..

 

[mojave_tx]

I have a Galaxy S6 and it's worked fine with my Renegade so far. Of course I've only had the Renegade for a week now, but I've been making calls and using text messaging with no issues.

 

[pavl]

I have a z3 that I'm running 5.1.1 on and it's working fine, no issues since the initial pairing two weeks ago, so lollipop is most definitely supported, I think it's something phone side maybe. Do you use anything like tasker or anything else that would affect bluetooth?

 

[CLShifter]

I have a z3 that I'm running 5.1.1 on and it's working fine, no issues since the initial pairing two weeks ago, so lollipop is most definitely supported, I think it's something phone side maybe. Do you use anything like tasker or anything else that would affect bluetooth?

No, it's a stock Verizon Motorola Droid Turbo, purchased in June. I'm using the standard Verizon Message+ app for text, and I removed all other paired devices.

After having the car for a month now, I've pretty much given up on the text integration working with any consistency for the time being.

 

[MetsFan]

I'm on android as well and everything works except my phonebook. uConnect will not download my phonebook..

My phonebook (contact list) shows all of my social media friends in addition to traditional phonebook contacts and took a long time to load when I initially paired it, but it eventually completed. And each time I reconnect, there's a delay in it recognizing the contact list (it will display the phone # and say something to the effect of contact name equals zero), but after a short time, it matches the names fine. Is your phonebook pretty big?


An issue I had this morning is that it kept re-reading the same text message as if it was new (and I had actually read that message manually before even leaving the house - so it wasn't new). And, it then started a count up of new messages (43 new messages, 44 .. 45 .. 46 .. 47) when there were no new ones. If I hit ignore, it would start over again. So, I turned off Bluetooth on my phone. I assume it somehow thought everything in my phone was new. After shutting off the car and getting back in later with Bluetooth on, it was no longer doing that (although I didn't get anymore texts either).

 

[logan5]

Just a reminder that you can change what is shared over Bluetooth by going to the settings for each individual Bluetooth connection. See attached.
For example, I don't want to play music over Bluetooth from my phone (I use a flash drive), so I disabled Media Audio.