Jump to content

iPhone not connecting with GMC IntelliLink, please help

zfromvan
 Share

Recommended Posts

zfromvan Enthusiast

zfromvan

Posted
Posted

When I try to pair my iphone to my truck, my phone says:

 

"Connection Unsuccessful, make sure GMC IntelliLink is turned on and in range."

 

As far as I can tell, it's turned on and I'm sitting in the truck when I try and pair my phone so range should not be an issue. Bluetooth is turned on on my phone, so I'm lost on what to do.

I've also read that there is a way to display the text messages you get on the main gauge display, how would I do that?

 

Any help would be greatly appreciated!

Robert.jean1 Enthusiast

Robert.jean1

Posted
Posted

My iPhone does that sometimes as well. It isn't the truck it's the prone. Cause when that happens I do a quick reset on the phone and it connects right away.

Timothy Brown Enthusiast

Timothy Brown

Posted
Posted

My iPhone does that sometimes as well. It isn't the truck it's the prone. Cause when that happens I do a quick reset on the phone and it connects right away.

 

This is correct. If it has been paired before, try deleting the phone from the truck and repair it. If that doesn't work then you may want to take your phone to an Apple store and have them reset your iOS.

GulfTango Enthusiast

GulfTango

Posted
Posted

I would first, delete the phone from the truck, then turn the phone off, turn it back on again...then re-pair the two.

 

The old, turn it off, turn it back on again...

 

 

Sent from my iPad using Tapatalk

zfromvan Enthusiast

zfromvan

Posted
  • Author
Posted

Thanks guys, I've tried deleting the phone from the truck and then trying to re connect, but that's a no go. I'll try turning the phone off and then back on and see what it does.

ember1205 Senior Enthusiast

ember1205

Posted
Posted

Here's a more detailed process to follow:

 

- Turn on truck, delete phone, turn off truck, open driver's door

- On the iPhone, delete the truck

- On the iPhone, hold the home button and the lock button until the phone resets itself. This will clear all of your Wi-Fi connections as well, so be aware that you'll have to set them back up.

- Once the phone powers back on, re-pair it with the truck

ember1205 Senior Enthusiast

ember1205

Posted
Posted

As far as displaying messages - you'll need Notifications turned on on the phone, turned on in the truck, and the option enabled on the Bluetooth profile in the phone (you can enable this AFTER pairing it to the truck and disconnecting it). You will also need to have Notifications turned on on the lock screen for the phone. It's all in the details.

zfromvan Enthusiast

zfromvan

Posted
  • Author
Posted

As far as displaying messages - you'll need Notifications turned on on the phone, turned on in the truck, and the option enabled on the Bluetooth profile in the phone (you can enable this AFTER pairing it to the truck and disconnecting it). You will also need to have Notifications turned on on the lock screen for the phone. It's all in the details.

 

Thank you so much!

 

I ended up having to go to Apple and they found some sort of error in the bluetooth. Regardless, it works great now.

Thanks again for the help guys.

ember1205 Senior Enthusiast

ember1205

Posted
Posted

If you plug the phone in to a power source and have all of the Siri stuff enabled, you can just yell out "Hey, Siri!" and ask her to read you new incoming messages and also dictate messages outbound that way.

bmf4069 Enthusiast

bmf4069

Posted
Posted (edited)

Or you could buy an android. I haven't had any problems.

Edited by bmf4069
ember1205 Senior Enthusiast

ember1205

Posted
Posted

That's because you haven't gotten the text message of death yet. None are perfect.

 

There are things I like about both platforms. Android can be tweaked to do EXACTLY what I want. But, it's a pain in the a$$ to have to spend that much time customizing a phone and then losing EVERYTHING when I change to a new one. The iPhone has a lot of things you just can't make the work that you feel they should, but it's reasonably stable and iTunes is actually a quality backup program (as is the iCloud if you have enough space). Plus, it syncs up with my Mac and I can share my full suite of text messages across all iOS and Mac devices.

  • Like 1
Timothy Brown Enthusiast

Timothy Brown

Posted
Posted

I've gotten the text of death. It sucks having to either suffer through the phone reading this code or turn the truck off, and open the door at the next stop haha

 

to each their own right. I love android phones but have a mac. as long as you know what you're doing, you can make anything fit exactly what you need it to do.

  • 2 weeks later...
Farmers Enthusiast

Farmers

Posted
Posted

I have a 2015 Sierra w/ Intellilink and an iPhone 6. I'm able to pare, make and receive calls, and receive text messages. However the Intellilink says "Error" when I try and reply to a message. Is this the iPhone or the Intellilink?

Prdtrgttr Enthusiast

Prdtrgttr

Posted
Posted

No text of death here. I have paired my BlackBerry to 2 Silverados and 2 Sierras flawlessly. Kudos to the Canadian phone company, BlackBerry! Lol

 

Bvonscott Enthusiast

Bvonscott

Posted
Posted

I have a 2015 Sierra w/ Intellilink and an iPhone 6. I'm able to pare, make and receive calls, and receive text messages. However the Intellilink says "Error" when I try and reply to a message. Is this the iPhone or the Intellilink?

 

Due to programming on the iPhone you cannot reply to txts from the truck's display. You can however hold down the voice command button on the steering wheel until SIRI comes on and ask her to reply to the txt

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...