Hands Free Phone

WARNING:

To avoid serious or fatal injury on vehicles equipped with airbags, disable the Supplemental Restraint System (SRS) before attempting any steering wheel, steering column, airbags, airbag curtains, knee blocker, seat belt tensioner, impact sensor or instrument panel component diagnosis or service. Disconnect the Intelligent Battery Sensor (IBS)/negative battery cable assembly from the negative battery post, then wait two minutes for the system capacitor to discharge before performing further diagnosis or service. This is the only sure way to disable the SRS. Failure to take the proper precautions could result in accidental airbag deployment.

The hardwired circuits between components related to the Radio Receiver Module (RRM) and the Uconnect® Hands Free Phone system may be diagnosed using conventional diagnostic tools and procedures. Refer to the appropriate wiring information. The wiring information includes wiring diagrams, details of wire harness routing and retention, connector pin-out information and location views for the various wire harness connectors, splices and grounds. For proper wire repair, and connector repair procedures. Refer to STANDARD PROCEDURE . and. Refer to REMOVAL . Refer to INSTALLATION .

However, conventional diagnostic methods will not prove conclusive in the diagnosis of the RRM or the electronic controls and communication between modules and other devices that provide some features of the Uconnect® Hands Free Phone system. The most reliable, efficient and accurate means to diagnose the RRM or the electronic controls and communication related to Uconnect® Hands Free Phone system operation requires the use of a diagnostic scan tool. Refer to the appropriate diagnostic information.

NOTE:

Validation and diagnosis of many of the conditions listed below will require access to both the paired Bluetooth® device and the Personal Identification Number (PIN) required for that device.

HANDS FREE PHONE DIAGNOSIS
CONDITION	POSSIBLE CAUSES	CORRECTION
PHONE NOT AVAILABLE	1. Bluetooth® phone not paired to the RRM.	1. Be certain that the phone is Bluetooth® compatible and is paired to the RRM.
	2. Bluetooth® phone not present or turned OFF.	2. Be certain that the paired phone is present, turned ON and that the Bluetooth® option is enabled in the phone.
	3. Bluetooth® phone has low battery.	3. At low battery levels, some phones will turn OFF Bluetooth® functionality. Be certain that the phone battery is charged to an adequate level.
	4. The boot procedure for the RRM, the phone or both did not complete successfully.	4. Cycle both the RRM and the phone OFF, then ON again in an attempt to complete a successful boot procedure.
	5. A phone freeze has occurred.	5. Power cycle the phone. Refer to the operator's manual for the phone.
PHONE PAIRING FAILED	1. The phone is not Bluetooth® enabled.	1. The Bluetooth® transceiver requires that the cellular phone be Bluetooth® enabled. The phone must be upgraded to one that is Bluetooth® enabled. A list of suggested phones is available at: https://www.driveuconnect.com/
	2. The phone does not support the Bluetooth® Hands Free Profile.	2. The Bluetooth® transceiver requires that the cellular phone support the Hands Free Profile. The phone must be upgraded to one that supports the Hands Free Profile. A list of suggested phones is available at: https://www.driveuconnect.com/
	3. Incorrect discovered Bluetooth® device selected in phone.	3. Be certain to select Uconnect® in the discovered Bluetooth® devices in the phone for pairing.
	4. The PIN of the phone is not the same as the PIN assigned by the RRM during pairing.	4. The PIN assigned by the RRM during pairing must match the PIN of the phone.
	5. Phone pairing is locked (password protected).	5. To unlock phone pairing in the phone, be certain that password protection is turned OFF.
	6. The RRM has reached the maximum number of allowed devices paired.	6. Remove one of the previously paired devices from the paired list of the RRM.
	7. The phone has reached the maximum number of allowed devices paired.	7. Remove one of the previously paired devices from the paired list of the phone, or delete the pairing history from the phone. Refer to the operator's manual for the phone.
	8. The boot procedure for the RRM, the phone or both did not complete successfully.	8. Cycle both the RRM and the phone OFF, then ON again in an attempt to complete a successful boot procedure.
	9. A phone freeze has occurred.	9. Perform a hard reset (power cycle) to the phone. Refer to the operator's manual for the phone.
PHONE WILL NOT RECONNECT AFTER PAIRING	1. Bluetooth® settings in phone are incorrect.	1. Bluetooth® settings in phone should be set to auto-connect or select Uconnect® as a trusted device in phone.
	2. Phone pairing is locked (password protected).	2. To unlock phone pairing in the phone, be certain that password protection is turned OFF.
	3. The boot procedure for the RRM, the phone or both did not complete successfully.	3. Cycle both the RRM and the phone OFF, then ON again in an attempt to complete a successful boot procedure.
	4. A phone freeze has occurred.	4. Perform a hard reset (power cycle) to the phone. Refer to the operator's manual for the phone.
POOR VOICE RECOGNITION	1. User is not waiting for the beep tone acknowledgment before issuing voice commands.	1. Be certain the user knows to wait for the acknowledgment beep tone prior to issuing voice commands.
	2. User is not issuing voice commands in a smooth and consistent speaking voice.	2. Be certain the user is issuing voice commands in a normal, smooth and consistent speaking voice. The Advanced Speech Recognition (ASR) engine is designed to recognize normal speech patterns and at a normal tone. Some users tend to speak to a computer loud and slow, which results in reduced performance.
	3. User is not using proper Voice Recognition syntax.	3. User must speak using proper Voice Recognition syntax.
	4. High noise levels within the passenger compartment.	4. ASR engine performance is increased when noise conditions in the passenger compartment are lowered. Ideal conditions include having the windows closed and the blower fan set to LOW or OFF.
	5. Passengers are talking while the user is attempting to issue a voice command.	5. Although designed to focus on sounds from the driver seated position, the directional microphone will pick up sounds from any seating position in the vehicle. ASR engine performance is increased in low noise environments.
	6. Foreign objects interfering with microphone input.	6. Verify that there are no foreign objects obstructing the microphones in the headliner that could be interfering with microphone reception.
	7. The microphone is not properly attached to the headliner.	7. The microphones must be firmly mounted to the headliner. Be certain the microphone is properly installed.
	8. The incorrect Uconnect® switch button is being pressed.	8. Phone features are accessed using the Uconnect® Phone button on the steering wheel or the Phone soft key in the RRM display. Other Uconnect® Voice Recognition features are accessed using the Uconnect® VR button or soft key.
	9. Microphone failure.	9. Use a diagnostic scan tool and the appropriate diagnostic procedures for additional diagnosis of the microphone.
PHONE BOOK DOES NOT DOWNLOAD	1. Phone does not support the Phone Book Access Profile (PBAP).	1. The Uconnect® system requires that the cellular phone support the PBAP profile. To enable the Uconnect® phone book download feature, the phone must be upgraded to one that is PBAP enabled. A list of suggested phones is available at: https://www.driveuconnect.com/
	2. Phone book transfer not enabled in phone during pairing.	2. Be certain that phone book transfer is accepted or enabled in the phone during pairing to enable the Uconnect® phone book download feature.
	3. Missing contacts from downloaded phone book.	3. Only contacts with a phone number are downloaded from phone and the number of contacts downloaded is limited to 1000.
PHONE BOOK NAMES NOT RECOGNIZED CONSISTENTLY	1. User is not waiting for the beep tone acknowledgment before issuing voice commands.	1. Be certain the user knows to wait for the acknowledgment beep tone prior to issuing voice commands.
	2. User is not issuing voice commands in a smooth and consistent speaking voice.	2. Be certain the user is issuing voice commands in a normal, smooth and consistent speaking voice. The Advanced Speech Recognition (ASR) engine is designed to recognize normal speech patterns and at a normal tone. Some users tend to speak to a computer loud and slow, which results in reduced performance.
	3. User is not using proper Voice Recognition syntax.	3. User must speak using proper Voice Recognition syntax for example: say Call - then name, or say Dial - then number).
	4. Phone book names too short.	4. For increased performance, it is recommended to use both first and last names for phone book entries. Example: Daniel Johnson as opposed to Dan .
	5. Name not spoken by user as it appears in the phone book.	5. Speak the full contact name as it appears in the phone book. Do not use nicknames.
	6. Multiple similar sounding names in the phone book.	6. For increased performance it is recommended that the user do not enter similar sounding names in the phone book.
	7. Phone book download not yet completed.	7. Depending upon the size of the contact list on the phone, the download may not have had time to complete. If the Phone Book button on the RRM phone screen appears greyed out, the contact list download is still in progress. Wait until download completes.
	8. High noise levels within the passenger compartment.	8. ASR engine performance is increased when noise conditions in the passenger compartment are lowered. Ideal conditions include having the windows closed and the blower fan set to LOW or OFF.
	9. Passengers are talking while the user is attempting to issue a voice command.	9. Although designed to focus on sounds from the driver seated position, the directional microphone will pick up sounds from any seating position in the vehicle. ASR engine performance is increased in low noise environments.
	10. Foreign objects interfering with microphone input.	10. Verify that there are no foreign objects obstructing the microphones in the headliner that could be interfering with microphone reception.
	11. The microphone is not properly attached to the headliner.	11. The microphones must be firmly mounted to the headliner. Be certain the microphone is properly installed.
	12. The incorrect Uconnect® switch button is being pressed.	12. Phone features are accessed using the Uconnect® Phone button on the steering wheel or the Phone soft key in the RRM display. Other Uconnect® Voice Recognition features are accessed using the Uconnect® VR button or soft key.
	13. Microphone failure.	13. Use a diagnostic scan tool and the appropriate diagnostic procedures for additional diagnosis of the microphone.
POOR PHONE AUDIO QUALITY	1. High noise levels within the passenger compartment.	1. ASR engine performance is increased when noise conditions in the passenger compartment are lowered. Ideal conditions include having the windows closed and the blower fan set to Low or Off.
	2. Passengers are talking while the user is attempting to issue a voice command.	2. Although designed to focus on sounds from the driver's seated position, the directional microphone will pick up sounds from any seating position in the vehicle. ASR engine performance is increased in low noise environments.
	3. Foreign objects interfering with microphone input.	3. Verify that there are no foreign objects obstructing the microphones in the headliner that could be interfering with microphone reception.
	4. The microphone is not properly attached to the headliner.	4. The microphones must be firmly mounted to the headliner. Be certain the microphone is properly installed.
	5. Microphone failure.	5. Use a diagnostic scan tool and the appropriate diagnostic procedures for additional diagnosis of the microphone.
NO PHONE AUDIO	1. The settings in the phone cause the phone audio to be routed to a handset.	1. Route the phone audio to the hands free device.
CALL LOG INOPERATIVE OR INACCURATE	1. Call log not supported by phone.	1. The Uconnect® system requires that the cellular phone support the call log feature. To enable the Uconnect® call log feature, the phone must be upgraded to one that is call log enabled. A list of suggested phones is available at: https://www.driveuconnect.com/
CALL LOG INOPERATIVE OR INACCURATE	2. The phone is not providing accurate call log data.	2. Refer to the operator's manual for the phone.
AUDIO OUTPUT TOO LOW	1. Volume setting on the Bluetooth® device set too low.	1. Set the volume of the phone or other Bluetooth® device to about three quarters (3/4) of full or maximum volume.
AUDIO OUTPUT TOO LOW	2. Volume setting on the RRM set too low.	2. Set the volume of the RRM to the desired level during an active Uconnect® Hands Free Phone call session.