Re: Issues with 430N (RHB) Media Center & iPhone 4
Ok, so Apple has provided a new set of updates:
4.2.10 for Verizon Iphone and
4.3.5 for ATT IPhone (3&4) as well as iPods.
With the Iphone there is a chance that you may experience 1 of 2 issues when plugging into the docking cable:
1) you may get an "error occurred" message,
2) you may get a long "reading" time frame that seems not to go away,
If you get these messages, you will also notice that on the phone will be another message "accessory device not supported by phone"
I have performed several different tests on the phones and found that this case seems to happen if you plug the cable into the phone when it is turned completely off.
So the “real world” case that this would happen is:
1)If a person has a phone that is paired to Uconnect, turns BT off to preserve the battery level,
2)Leaves the vehicle and does some activity where he / she will play the iPod during this activity,
3)Drains the battery down and the phone shuts off or they power off the phone to save some battery charge for calls before getting back to the car,
4)When they get back to the vehicle and plug the phone into the docking cable without having powered it up,
5)After the phone powers up a the “accessory not supported by Iphone” will pop up on the display,
6)If they immediately press the MEDIA button , select Aux Uconnect will show “Reading”, then “Error Occurred”, when the error box goes away the Aux screen shows 00:00 on the timer and the < > & ll buttons are light blue (inactive),
Steps to get past the “Error Occurred” message
1)Unplug the docking cable, power up the phone after the phone is powered up, plug in the docking cable, press the Media button, select “Aux”, Uconnect will Read then start playing,
2)If not done as described in step #1, I have had to unplug up to 4 times before “Reading” was done and play started,
WELL HERE WE GO AGAIN:::::::: if you have an ipod or iphone,
please do not do the 4.3.5 update till i can test it. I have just been told by a person that I have helped with the Uconnect update that there is a new problem with this update. I will be testing it and let you know more soon.