Jump to content

Recommended Posts

Posted (edited)

Absolutely no audio on start up however the screen was working. Tried shutting truck down and restart still nothing. Even the turn signals had no clicking sound. After a few hours of being parked it was all back to normal again. Anyone else?

Edited by ILSilverado
Posted

I get that with xm, but regular FM works as does aux.

Sent from my SM-G960U using Tapatalk

Posted

Take advantage of your warranty and have it repaired.  Even if they can't find the problem, there will be a record of your complaint.   Don't accept this as a little idiosyncrasy with your truck. It is not normal and should be fixed.

Posted
Absolutely no audio on start up however the screen was working. Tried shutting truck down and restart still nothing. Even the turn signals had no clicking sound. After a few hours of being parked it was all back to normal again. Anyone else?
This has happened to me a few times, usually it fixes as soon as I restart the truck, but a couple times I have had to wait. I took it to the dealer, but one time had started working prior to arriving and second time worked as soon as they turned the truck came back on. Was told not anything they could do about it.

Sent from my SM-N960U using Tapatalk

Posted
This has happened to me a few times, usually it fixes as soon as I restart the truck, but a couple times I have had to wait. I took it to the dealer, but one time had started working prior to arriving and second time worked as soon as they turned the truck came back on. Was told not anything they could do about it.

Sent from my SM-N960U using Tapatalk


Same here. Just glitches in the software. Until GM moves to a rolling release for updates there will be issues. I think they started this in the new trucks so maybe see if you have an update available.. you will probably have to connect to WiFi.
Posted

I've looked for updates and havent seen any. I'm not holding my breath for a fix at this point and I've had my truck into the dealer I think 9 times now since I got it at the end of november, pretty much just tired of dealing with the issues.

Sent from my SM-N960U using Tapatalk

Posted
9 hours ago, tmo said:


Same here. Just glitches in the software. Until GM moves to a rolling release for updates there will be issues. I think they started this in the new trucks so maybe see if you have an update available.. you will probably have to connect to WiFi.

This has been going on since 2014 keep waiting.  

  • Haha 1
Posted
This has been going on since 2014 keep waiting.  

I’m not. Has only happened once in my 2018. I’m not worried about it.
Posted
16 hours ago, Pinnacle said:

This has been going on since 2014 keep waiting.  

Was going to say, well the infotainment system in my 2014 is pretty much what the 2021 models have in it haha. I have had this glitch but it has been few and far between in my 7 years of owning this truck now.

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...