Jump to content

Recommended Posts

Posted

I have a 2015 Silverado LT. For the passed few months I have been battling the radio, and the cluster screen. It will switch screens on its own, swipe up and down, change the song, go to NAV without me telling it to, etc. I wanted to see if anyone has had the same problem, and what steps it takes to fix it. Please keep in mind that I am not touching any buttons except when I switch the screen back to where it started. These videos have been taking over the course of several weeks, not all in one day. So the problem remains.

 

IMG_4240.MOV

 

IMG_4239 2.MOV

 

ips-8177546C-7DC6-49FE-BC42-E9607B49A977 3.mp4

 

 

Posted

I am having a similar issue with my 2016. I have taken it to two different dealerships and they have not resolved the issue. The first one did a software update, didn't fix the problem. The next two visits I was told they couldn't do anything because they couldn't replicate the issue. I hope you have more luck then I did.

Posted

Make sure you try and get a video as proof its doing it... Thats the easiest way for them to say that there isnt a problem. 

Posted

I had issues with mine to. It was picking it's own radio stations and cranking the volume up. When I took into the dealer it was blasting Girls just want to have fun and there wasn't a darn thing I could do about it. Uh Boy! :shakehead: It then got to the point it wasn't working at all as I waited for the parts to come in.

 

Anyway the ended up replacing the entire unit.

  • 2 months later...
  • 1 year later...
Posted

My 2016 Tahoe , is  changing stations on its own , screen is changing to tune station , going from AM- FM to MEDIA , 

Its driving me crazy any update or way to reset 

Posted
On 8/21/2020 at 5:57 AM, Lia said:

My 2016 Tahoe , is  changing stations on its own , screen is changing to tune station , going from AM- FM to MEDIA , 

Its driving me crazy any update or way to reset 

Welcome to the site.

 

Sounds like your HMI module might be failing. Only replaceable, not fixable.

  • 1 year later...
Posted

@RACERX7775

 

I am having the same problem with my 17 Silverado 1500 Radio.  You asked if there was any issues with stabili-trac or steering. When parked and idling for a period of time my stabili-trac and ABS light comes on. They go off within seconds of me driving. From what I’ve gathered, it’s do to a small vacuum leak. GM know about the issue as there was a recall where they reprogrammed the hydraulic system to take over at low parking speeds. I never had a problem with any of it until I took my truck in to have the transmission replaced ( under warranty) and they did the recall and reprogramming. My radio problem started about 6-8 months after I got my truck back. It has been getting worse slowly over time. When it starts I go to settings then return to factory settings and restore the radio. Sometimes I need to do this 2 times but it usually stops it for a day or so. Do you think the stabili-track has anything to do with the radio? 

Posted
1 hour ago, sguidry78 said:

@RACERX7775

 

I am having the same problem with my 17 Silverado 1500 Radio.  You asked if there was any issues with stabili-trac or steering. When parked and idling for a period of time my stabili-trac and ABS light comes on. They go off within seconds of me driving. From what I’ve gathered, it’s do to a small vacuum leak. GM know about the issue as there was a recall where they reprogrammed the hydraulic system to take over at low parking speeds. I never had a problem with any of it until I took my truck in to have the transmission replaced ( under warranty) and they did the recall and reprogramming. My radio problem started about 6-8 months after I got my truck back. It has been getting worse slowly over time. When it starts I go to settings then return to factory settings and restore the radio. Sometimes I need to do this 2 times but it usually stops it for a day or so. Do you think the stabili-track has anything to do with the radio? 

I thought the low speed vacuum reprogram was for the vacuum pump for the brakes. I know that I had the flash done on mine and later the vacuum pump failed. I never had any stabilitrack or ABS issues  only extreme hard brake pedal at slower speeds.

Posted

It reprograms the hydronic system to add more pressure and make up the difference at low speeds. Never had an issue with my brakes until they got ahold of it. How long after the flash did your pump go out? Do you think there’s any connection between the 2? 

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

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...