Jump to content

Recommended Posts

Posted

Hey y’all,

 

so I bought the refreshed Silverado last week and everything seemed to be working great. A couple days after, I went out to start the truck and the digital cluster wouldn’t come on which is kinda inconvenient if you need to drive lol. After a few minutes I came back to it and the dash came on like normal. The following day the speakers had a ton of static. Left it alone for a few minutes and everything worked as it should. Was told by the dealership that it could be Gm sending updates? Anyone know what could be going on? I’ll attach a pic of the cluster 

73FBB956-1B1D-474C-9377-DD43136DE1E5.jpeg

Posted (edited)

Well that’s lame and I think whoever gave you that answer at the dealer is clueless.

 

I’d push them for action and not just a bullshit cop out like they gave you. That’s obviously a serious issue and you could make a big deal out of it in the name of safety.


I doubt anyone will have much information for you on this forum since this is all still pretty new. 

Edited by Dirk13
  • 2 weeks later...
Posted

So, I also bought a new 2022 Silverado at about the same time. The new screens look awesome and sold me on the roughly $2,500 price increase over the LTD model. I have noticed a few similar glitches. The first weekend after I bought the truck I took it on about a 500 mile round trip and the way there the stereo could not be turned above 30% volume without really bad static and cutting out. I actually called the dealership and left a voicemail about it that was never responded to. The way back it was fine and I haven’t experienced that exact issue since. I have noticed a weird issue with the backup camera cutting out though. While reversing I have had the camera go black a few times. Definitely not ideal. I wonder how much is just the early adopter tax and what will come of these issues. Chevy has been long overdue for a refresh and to think they couldn’t launch something reliable after so long is disheartening. Maybe when they install the microchips for the heated seats and steering wheel they will fix these other issues. Otherwise it is still a really nice truck for the money. 

Posted

Bump for this thread. I’ve noticed similar issues. Lately have a weird static that comes and goes. I posted a thread about it. Keep us posted if anyone figure sit out 

  • 2 weeks later...
Posted

I had this screen setup on my AT4 for about an hour the other night.  Wouldn't go away despite numerous restart attempts.  Finally corrected itself after about an hour.

 

The new dash is pretty sweet looking but its definitely laggy.  The Google Maps function through the vehicle sometimes takes over a minute to generate driving directions.  

 

I do love the Apple Carplay connectivity - it's wireless (bluetooth) as well and very snappy, quick.  

image_50381569.JPG

Posted

I've been having an intermittent issue with flickering lines in the radio display not to mention how laggy the software is.....I just bought this truck 2 weeks ago and regret it, I should've got the dam RAM rebel....it's about time Chevy refreshed their dash but they should've studied RAMs Uconnect a little more, this new dash PALES in comparison. Mary Barra needs to be fired as CEO and someone young and open minded be brought in to replace her

20220528_204252.jpg

  • Haha 2
  • 2 weeks later...
Posted

Having the same issue, 3 days worth now, hard reset everything and my speakers still sound terrible with static. Truck has 645 miles on it…. Any answers? 

Posted

I'm having similar issues in my new Sierra had it for about a month and once (5 days in) the speedo side went out and yesterday I went to the local waste transfer to toss some recycle stuff, shutoff the truck when I dumped the barrels got back in, and no maps, no carplay, and no ability to change radio volume via steering wheel controls. When the speedo went out I lost steering wheel controls on the right side also.

Posted

I have the 22 refresh elevation. Having the same issue with the speakers cutting out. I just pull over and disconnect the battery for 10 seconds and reconnect. Not ideal but unfortunately until GM figures out this issue this is the only way I have found to fix it immediately. Also are you guys having issues with the parking Brake automatically applying when hitting the park button. And I'm pretty sure it's sticking cuz my rear brakes are already sounding like metal on metal with 3k miles on it. Smdh. 

Posted

I have just purchased the refreshed RST.   I am not experiencing static.   The Bose audio sounds clean all the way up to max volume.

 

What I have experienced is the audio / speakers cutting out for a few seconds randomly.   Definitely annoying. 

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

    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...