Jump to content

Recommended Posts

Posted
6 hours ago, Jason Gonzales said:

So my 2018 Chevy Silverado LTZ radio is basically bouncing and I have already tried to remove the blue cable and still does it. And ofcourse I am now 2000 miles out of warranty. This sucks my first new truck is messing up already! 

IMG_8354.MOV

Welcome to the site.

 

Take it to your dealer and see if they will help you with the warranty issue.

 

You might have a HMI module failing. 

  • 1 year later...
  • 9 months later...
Posted

My husband has a 2018 Silverado 1500 high country and his infotainment radio is doing the same. It bounces between screens, stations, disconnects Bluetooth, etc. it also causes the screen in front of the steering wheel to change too. His truck is way out of warranty (104,600 miles) so I’ve considered changing the head unit out for an aftermarket compatible one but I’m worried it’s a wiring issue as opposed to the radio unit itself. Your thoughts? 

Posted
3 hours ago, AprilJoy said:

My husband has a 2018 Silverado 1500 high country and his infotainment radio is doing the same. It bounces between screens, stations, disconnects Bluetooth, etc. it also causes the screen in front of the steering wheel to change too. His truck is way out of warranty (104,600 miles) so I’ve considered changing the head unit out for an aftermarket compatible one but I’m worried it’s a wiring issue as opposed to the radio unit itself. Your thoughts? 

This is certainly not what we like to hear, AprilJoy.  Please know, customer satisfaction is extremely important to us. Our team would be more than happy to take a closer look into the concerns with your husband's truck. To do so, please send an email to [email protected] with ATTN: AprilJoy/GM Trucks in the subject line.

Please include your contact information, VIN, a brief description of your concern, and the name of your preferred dealership. We look forward to hearing from you. To learn more about GM’s Privacy Policy, please visit https://www.gm.com/privacy-statement.html. The information you provide may be monitored and recorded and is subject to the GM Privacy Statement.
 
Privacy Statement | General Motors
Your privacy is important to General Motors. This Privacy Statement addresses the personal information GM collects and how GM handles that personal information.
www.gm.com
 

Posted

@GMCustomerService can you kindly explain how this post provides any kind of resolution so others can know how to fix their problem? The point of this forum is to provide help with solutions to fix problems. I have yet to see any of your posts do that

  • Haha 1
  • 1 year later...
Posted

Replying back to basically no one, start with the simple things like really giving the screen a good cleaning, this actually worked for me. The build of "grease" from your fingerprints will cause "ghost touches" after a period of time. 

  • Like 1
  • 9 months later...
Posted

I bought a 2018 Chevy 1500 Silverado High Country 4wd crew cab, in 1/24 96k miles, within 3 months it developed this issue your describing. I bought 3 GM products in the last  half a dozen years, all 3 have issue 2 major issues! I retired in 2012 from a 30 year career as a professional Automotive Technician. I've always been a GM fan have a brother who worked for GM and retired. It's looking like this is my last GM!!!

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...