Jeep Patriot Forums banner
1 - 5 of 5 Posts

Nightflight

· Registered
Joined
·
98 Posts
Discussion starter · #1 ·
I've had my Patriot for about a week now, and the biggest quirk I've found is that I'm unable to make calls through Uconnect. I can receive them just fine, but the problem is that when I tell it to dial someone, it rings through the stereo twice, then it says "call completed," hangs up, and goes back to the radio. However, the actual phone keeps ringing, so I have to grab my phone, turn off the Bluetooth, and talk regularly. It also doesn't go through the vehicle when I make a call directly from my phone, but receiving them works just fine. I know the phone doesn't have a problem with connecting to Bluetooth-equipped vehicles because it worked flawlessly on my Focus, on my father's Ford Escape, F-250, and my mother's Cadillac ATS. I'm not really sure what to do, either, because I looked on the Uconnect website to check for a software update, and it said my VIN was invalid when I typed in the last 8 digits.

Any ideas on how I can fix this?

Phone: Samsung Galaxy S5
Carrier: Verizon
Stereo: RBZ (I believe that's what it is... it slipped my mind)
 
STAR Case
This document does not authorize warranty repairs. This communication documents a record of past experiences. STAR Center
Online does not provide any conclusions about what is wrong with the vehicle. Rather, it captures all previous cases known that appear
to be similar or related to the vehicle symptom / condition. You are the expert, and you are responsible for deciding on the appropriate
course of action.
Chrysler Group LLC Contact the STAR Center for assistance if no solution is found Version 5/23/13
Case Number: S1408000081
Release Date: 02/28/2014
Symptom/Vehicle Issue:
Uconnect Ends Call, Message “Call Completed”
Discussion:
NOTE: Uconnect disconnects phone with message “Call Completed”. Do not replace the uconnect module for this concern.
There is an issue with Samsung phones with the Android 4.3 SW version. This issue is only on the CDMA networks (Sprint & Verizon) This issue is on newly purchased phones with the version already on them or older phones that have been updated from a lower Android SW version to the 4.3 version. Older phones had been working correctly and after the customers have updated the phone, this new issue began.
When an outgoing call is made, the call will begin to be placed and sometimes the call is actually made. Within a few seconds the call is ended and Uconnect replies with “call completed” and returns to the radio mode; call can still active on the phone itself. This is not an issue with Uconnect, it is between the network and the phone. This same issue has been found on BlackBerry phones (Q10 & Z10) where they also have had a new SW update done or a newly purchased phone with the software concern
 
Discussion starter · #4 · (Edited)
Long story short, you are **** out of luck until samsung updates the phone.
Well, seeing as though Verizon has their own thing where they don't immediately release software updates and, instead, do their own testing before letting it out to the public, it looks like it's going to be a while until that happens. :(

Thanks for the info! Much appreciated.

Also, kind of unrelated, but a couple of the songs I imported to the car's hard drive play very slowly... Like, slow enough so it sounds demonic. Any ideas how I can fix that? I'll upload a video to YouTube that I took to show an example.
 
Discussion starter · #5 ·
Here is the issue I was talking about with the song slowing down to a demonic level:

">
" type="application/x-shockwave-flash" width="425" height="350">


Edit: I don't really know what happened with the formatting, but I don't know how to fix it, either.
 
1 - 5 of 5 Posts