Android 4.3 issues with Uconnect
#31
06-12-2014, 09:38 AM
Rookie
mmark27,
No, it will be fixed and is currently being worked on. The issue that I have found out is that there are several issues that Samsung is having with Android versions 4.3 & 4.4.2. There are issues with other vehicle lines also and some of the other vehicle mfg's won't even pair up to the phone and there's some ear buds having issues. So this is where the timing is becoming a problem, if our issue was the only one then it would be easy. What I'm being told is that they plan on a maintenance update late this month - early July.
No, it will be fixed and is currently being worked on. The issue that I have found out is that there are several issues that Samsung is having with Android versions 4.3 & 4.4.2. There are issues with other vehicle lines also and some of the other vehicle mfg's won't even pair up to the phone and there's some ear buds having issues. So this is where the timing is becoming a problem, if our issue was the only one then it would be easy. What I'm being told is that they plan on a maintenance update late this month - early July.
#32
06-12-2014, 09:50 AM
Registered User
Join Date: Mar 2014
Location: Minnetonka MN
Posts: 5
Likes: 0
Received 0 Likes
on
0 Posts
FIXED! Kind of, sort of.
FIXED! Kind of sort of. I have found a work around that works on a sometimes basis. First, you place the call from the handset. I wish I could voice dial, but this doesn't work as well when you do that. Here is the procedure that you follow:
1) Get the number to be dialed on the screen, either looking up the contact or by the keypad, then push the the dial key, aka, the green phone.
2) As soon as the screen changes to the call in progress screen look for the "headset key" on the lower right to turn green.
3) Push the headset key, to turn the Bluetooth connection to the car off. (It sounds dumb, but do it)
4) The car will reconnect and turn the headset back on, and your connection will work.
There is some timing involved, but once you get used to doing this procedure you can expect close to 90% success on not having the call dropped.
1) Get the number to be dialed on the screen, either looking up the contact or by the keypad, then push the the dial key, aka, the green phone.
2) As soon as the screen changes to the call in progress screen look for the "headset key" on the lower right to turn green.
3) Push the headset key, to turn the Bluetooth connection to the car off. (It sounds dumb, but do it)
4) The car will reconnect and turn the headset back on, and your connection will work.
There is some timing involved, but once you get used to doing this procedure you can expect close to 90% success on not having the call dropped.
#33
06-12-2014, 09:58 AM
Rookie
FIXED! Kind of sort of. I have found a work around that works on a sometimes basis. First, you place the call from the handset. I wish I could voice dial, but this doesn't work as well when you do that. Here is the procedure that you follow:
1) Get the number to be dialed on the screen, either looking up the contact or by the keypad, then push the the dial key, aka, the green phone.
2) As soon as the screen changes to the call in progress screen look for the "headset key" on the lower right to turn green.
3) Push the headset key, to turn the Bluetooth connection to the car off. (It sounds dumb, but do it)
4) The car will reconnect and turn the headset back on, and your connection will work.
There is some timing involved, but once you get used to doing this procedure you can expect close to 90% success on not having the call dropped.
1) Get the number to be dialed on the screen, either looking up the contact or by the keypad, then push the the dial key, aka, the green phone.
2) As soon as the screen changes to the call in progress screen look for the "headset key" on the lower right to turn green.
3) Push the headset key, to turn the Bluetooth connection to the car off. (It sounds dumb, but do it)
4) The car will reconnect and turn the headset back on, and your connection will work.
There is some timing involved, but once you get used to doing this procedure you can expect close to 90% success on not having the call dropped.
I found another bug in the Uconnect that's a real Uconnect bug and not attributed to Samsung. Since the text message announcement is very annoying, long and uninformative, I've disabled the announcement when text is received in the settings menu of Uconnect. This works if you are listening to the radio or your HDD. However, if you are streaming music from your phone (or using phone navigation, etc.) the incoming text message announcement still comes through despite the setting turned off.
#34
06-13-2014, 09:08 AM
On the incoming SMS announcement, is this the same Uconnect voice prompt or is it only a sound?
I stumbled upon this accidentally once as I didn't want the call on the speakers, yet it connected to them to my surprise, and it did seem to work for me a few times, but it is very, very timing based. The issue I have with this is that when I dial on my phone it is rarely even picked up by my Uconnect that I'm dialing out. So my music keeps playing and nothing ever happens. BUT if I use the Uconnect to find the name (43% chance of that working), this toggle method does work.
I found another bug in the Uconnect that's a real Uconnect bug and not attributed to Samsung. Since the text message announcement is very annoying, long and uninformative, I've disabled the announcement when text is received in the settings menu of Uconnect. This works if you are listening to the radio or your HDD. However, if you are streaming music from your phone (or using phone navigation, etc.) the incoming text message announcement still comes through despite the setting turned off.
I found another bug in the Uconnect that's a real Uconnect bug and not attributed to Samsung. Since the text message announcement is very annoying, long and uninformative, I've disabled the announcement when text is received in the settings menu of Uconnect. This works if you are listening to the radio or your HDD. However, if you are streaming music from your phone (or using phone navigation, etc.) the incoming text message announcement still comes through despite the setting turned off.
#35
06-13-2014, 09:11 AM
Rookie
#36
06-13-2014, 09:22 AM
I have mentioned initiating the call from the handset in prior replies.
The reason why it works by turning the phones BT off and then back on is because Uconnect doesn't query the phone about the calls if the call isn't placed thru Uconnect.
The reason why it works by turning the phones BT off and then back on is because Uconnect doesn't query the phone about the calls if the call isn't placed thru Uconnect.
FIXED! Kind of sort of. I have found a work around that works on a sometimes basis. First, you place the call from the handset. I wish I could voice dial, but this doesn't work as well when you do that. Here is the procedure that you follow:
1) Get the number to be dialed on the screen, either looking up the contact or by the keypad, then push the the dial key, aka, the green phone.
2) As soon as the screen changes to the call in progress screen look for the "headset key" on the lower right to turn green.
3) Push the headset key, to turn the Bluetooth connection to the car off. (It sounds dumb, but do it)
4) The car will reconnect and turn the headset back on, and your connection will work.
There is some timing involved, but once you get used to doing this procedure you can expect close to 90% success on not having the call dropped.
1) Get the number to be dialed on the screen, either looking up the contact or by the keypad, then push the the dial key, aka, the green phone.
2) As soon as the screen changes to the call in progress screen look for the "headset key" on the lower right to turn green.
3) Push the headset key, to turn the Bluetooth connection to the car off. (It sounds dumb, but do it)
4) The car will reconnect and turn the headset back on, and your connection will work.
There is some timing involved, but once you get used to doing this procedure you can expect close to 90% success on not having the call dropped.
#37
06-14-2014, 07:40 AM
Registered User
Join Date: Mar 2014
Location: Minnetonka MN
Posts: 5
Likes: 0
Received 0 Likes
on
0 Posts
#38
06-16-2014, 07:23 AM
It's ok, You didn't step on my toes.
As I did also mention, Samsung is working on this issue along with others that they're having with Android 4.3 & 4.4. There are plans to have the SW update released the end of this month - early next month.
As I did also mention, Samsung is working on this issue along with others that they're having with Android 4.3 & 4.4. There are plans to have the SW update released the end of this month - early next month.
#39
06-16-2014, 07:25 AM
Sounds like the phone isn't responding to the BT message from Uconnect to turn it off. Can you try a rebooting of the phone? Remove the battery for a few minutes then reinsert it and try it again.
#40
07-08-2014, 10:28 AM
