Jump to content

Recommended Posts

Posted
On 5/30/2023 at 10:42 AM, Klutch said:

Curious if this has happened to anyone without the BOSE audio.

Happened to me once, no bose. Never happened again, as of yet.

Posted
3 hours ago, GOMD said:

Happened to me once, no bose. Never happened again, as of yet.

Well that suck but hey, misery loves company.  Good news is, the more affected the better chance we have of getting a fix.

  • 1 month later...
Posted

22 LT 3500 with infotainment screen .Glad to see im not the only one. This happend to me on a few days ago on a hot  day i believe it was around 100 degress. Lasted for about an hour. I stopped and restarted the truck, restarted the infotainment screen and nothing. Until I reached my destination I let the truck sit a few hours and it worked again. 

  • 1 month later...
Posted

This has happened to me probably 3-4 times on my 2022 with the new refreshed interior and 21000 miles or so.  I'm always listening to my phone so I just hit pause on the phone and give it a minute.  The only solution seems to be turning down on the steering wheel controls continuously until it begins to go down.

 

It would be nice to find a fix one day but I agree it probably wont happen.

  • 3 weeks later...
Posted (edited)

This happened to me today for the first time where the volume went to max. Before now it's happened about 3-4 times where it went to 0, which is no big deal. I cannot keep this truck if it can't be fixed soon since I carry my small daughter around with me. This would be traumatizing for her. Thankfully she wasn't with me today.

The TSB that's out there 20-NA-097 states the volume can be turned down when it happens. So this technically isn't the same problem address in that TSB since the volume can't be turned down at least for a period of time in this case.

I also submitted a NHTSA complaint as bullcitysierra recommended.  My case number is 11546400. 


Link to report via NHTSA:

https://www.nhtsa.gov/report-a-safety-problem#index


Edit: I have the 2022 refresh version with Bose

Edited by Bamaguy514
  • 3 months later...
Posted

This has happened to me in my 2022 Silverado TB.  It’s happened like 5-6 times in the past year.  Took it in twice for it and just get told it’s an update. I find that hard to believe and should not have to constantly take it in or worry about it.  Definitely a safety issue and could cause a wreck or if you have newborn baby in the vehicle and volume goes to max. Mute or power button does nothing. I had to scramble to grab my phone and switch over to Apple Music and start and pause a song. 

Posted

The past couple of times this has happened to me, the volume goes all the way DOWN.  Figured they couldn't fix it but made it go down instead of up.  

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   5 Members, 0 Anonymous, 2,189 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...