Jump to content

Recommended Posts

Posted (edited)

Same issue called the dealer and they said that was strange ha.  They need to have the truck to diagnose but I'm not hopeful. The infotainment system on these trucks are getting worse not better. 15, 18 and now 20 Sierra Denali all have had problems with phone and syncing!  15 was the best but last 2 are terrible and my truck is my office so I need it to work...

Edited by Col. Brown
  • 2 weeks later...
Posted

Each time I start my 2019 Silverado, many of the contacts do not load. It varies each time to which contacts load and the ones that don’t load 

Posted

2019 ltz here.  Mine wont load any contacts at all unless on android auto and then it has to relearn every time. 

  • 2 weeks later...
Posted

I was having this problem until today. Seems the newest IOS 13.4 update fixed mine.


Sent from my iPhone using Tapatalk

  • Like 1
Posted

Thanks hotrods37 I'm going to give it a try.  I typically wait until the kinks are out of iOS updates but this is encouraging...

Posted

I have IOS 13.4 on my iPhone XR and still having contact sync issues.  Picked up 3500HD AT4 on March 20 and have issue since driving away from dealer.  Been on the phone with Onstar and apple with no fix.  Truck is in at dealer now as they are getting GM on the phone to help.  Reading the previous posts, I'm not holding out a lot of hope that this can be a simple fix other than replace the radio.  Will advise later what the dealer comes back with.

Posted

Yep, no change with 13.4 getting a little perturbed. Very inconsistent when I get in the truck sometimes it sync's up other it doesn't recognize the phone. What can we expect for 70,000 dollars!!

Posted

Brought into local GMC dealer in Twin Cities.  They spent hours on the phone with GM tech adviser.  Final resolve was this from GM:  "Advised GM is aware of this issue with the iPhone contacts on the 2020 IOT radios.  We have been seeing that this issue may be something engineering has to investigate.  NO REPAIR IS AVAILABLE AT THIS TIME.  AS ADVISED BY OUR STAFF, CUSTOMER TO USE APPLE CAR PLAY AS WAY OF CIRCUMVENTING RADIO ISSUES UNTIL GM RESOLVES THE PROGRAMMING SITUATION.

 

Service manager at dealer said that it could be months or longer for GM engineers to fix being there is no official recall's or notices at this time.  While I am still able to drive the truck fine, and for that matter love everything else about it, I do find it frustrating that one has to have a work around to circumvent an issue that GM knows about, and admits to knowing about, but doesn't seem to have any urgency in finding a fix.

Posted

Thanks Hog, and I hate to say this but I think its time for me to look at other makes the next truck around.  Getting tired of paying big bucks for lackluster performance.  Thanks for your insight...

Posted
On 4/18/2020 at 8:06 AM, Col. Brown said:

Thanks Hog, and I hate to say this but I think its time for me to look at other makes the next truck around.  Getting tired of paying big bucks for lackluster performance.  Thanks for your insight...

Have you had it in to the dealer yet?

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

  • Latest Articles

  • Posts

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...