Jump to content

Recommended Posts

Posted

New member, first post, sorry if this has been discussed before.  I have a 3 month old 2020 GMC SLT and twice now in the last couple weeks the radio just

cuts out completely and won't play any sound on any station, XM or FM, etc, till the truck is powered down and re-started.  I have figured out there is a mute

function on the on/off button and it is not that.  I have tried powering the radio off/on while driving and that doesn't do it either.  The radio is still under power

and everything looks functional, just no sound at all at any volume.  Anyone have this happen to them.  I have also noticed this new radio struggles with finding

and keeping an XM connection,  Never had any of these issues on my 2015 GMC Sierra.  Any thoughts?  Anyone have this happen to them?

Posted

Yes, this has happen to me as well.  I have a 2020 LTZ, radio is on, but no sound.  Usually if I turn the truck off and restart it works again.  I have a few issues with my radio doing crazy things, stuff my 2014 never did.  The strangest one is when I get a call, its shows the wrong contact info.  My phone shows the right person calling, but my truck shows a completely different name, if it decides to show a nameat all, most of the time its just the number of the person calling even though I have that contact in my phone.

Posted

My 'just acquired 20 AT4 after 3k miles just did that... No radio/GPS lady sound after sub freezing temps Saturday morning. Just started out long drive back south. Disappointed, but.....

 

Then after a while sound returned. Very strange. At first I thought maybe a built in delay due to low temperature but not sensible to engineer that in vehicles that reside in cold climates. It must be a hw or sw fault, albeit intermittent.

 

Then after another stop and restart, the HUD disappeared. Later after another shut down and restart, HUD display reappeared.

 

Drove 1500 miles more and neither the radio/GPS lady sound or the HUD malfunctioned. All ok.

 

Appt will be setup at dealer to see if they can get any failure codes or if a TSB exists. Need 1st oil change after 4k miles in 3 weeks anyway. Oil life around 25% but I want it done now. Truck was awesome for the trip. Sadly for family illness needs, but all ok now.

 

I'll follow up with info.

 

Rich

 

 

1003201854.jpg

  • 2 weeks later...
Posted (edited)

Update...

 

Wednesday I setup an appointment for 1st oil/rotate and to address and record the radio sound issue I had, and the HUD display loss, both of which were only once.

 

A new oddity had been occurring too when XM would just cut out on engine start. It would display "acquiring signal" but never would in known good signal areas.

 

The XM "acquiring signal" fault had continued intermittently over the last week. Continued "resets" by power off/on or engine off/on would not correct. Typically after a few hours of rest and restarts, XM would return.

 

Ironically GM-Trucks.com sent me a email Weds night and included this.....

GM Releases Significant Over The Air Update For 2020 Silverado/Sierra & Other Vehicles

 

When I arrived yesterday morning for the service I told the Service Manager about the update. He said he hadn't received it yet and even mentioned...."We often find out last..." I gave him the Update Ref#, 20-NA-199.

 

The update includes s/w corrections to both the radio/display and the XM "acquiring signal" issue. The Service tech applied this 20-NA-199 update to mine. Everything fine so far and will update if any issues.

 

Rich

Edited by richmz
Posted

I've had my 2020 LTZ for 3 weeks now and This happened to me today. Turned my truck off and on and the radio came back but my steering wheel controls aren't working, has anyone seen this? 

 

Posted
10 hours ago, RRonin said:

I've had my 2020 LTZ for 3 weeks now and This happened to me today. Turned my truck off and on and the radio came back but my steering wheel controls aren't working, has anyone seen this? 

Haven't..... but doesn't mean it hasn't to others.

Did you try repeated on-offs and wait to retries?

 

Regardless, you need that update to correct related radio issues so it may be best to have your dealer do it so there's a record of the fault. They can also diagnose the wheel button functions as well, if it persists. Please let us know what happens.

 

Rich

10 hours ago, RRonin said:

 

 

  • 3 years later...
Posted

My 2023 Sierra was doing this. Dealer says its the first they've heard, so putting up with it for now. I started experimenting with turning things off one by one to see if it stopped; turning these off had no effect: wi-fi hot spot & Android auto. I left them off, and still had issues. Then I realized it usually happened within the first minute of starting, and coincided with the Google Assistant on screen notification "Play the news?". Went to Home, Settings, Google Assistant, and UN-checked:

  • Say "Hey Google"
  • Allow suggestions from Assistant
  • Get notifications from your Assistant

Audio has been stable for 2+ weeks now.

 

Posted

Thanks Grizz, I too have a 2023 Sierra and the same symptom, will be implementing these setting changes as well.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,891 Guests (See full list)

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • 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.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...