Jump to content

new radio update recall N242435631

kickass audio
 Share

Recommended Posts

kickass audio Enthusiast

kickass audio

Posted
  • Author
Posted
9 hours ago, rrmccabe said:

My update has been decent.  To comment on above post my 2024 LTZ has Play and Ignore when I get a text message.  Clicking play is hit or miss and does not always work. Not sure if one of the steering wheel buttons will activate play or not.

 

So several of you have talked about radio cutting out..  I have an issue which sounds like lack of signal where the speakers will mute for probably less than a second. But it does it on FM stations and also data streams like YouTube Music. Is this what you guys experiencing?  Except for KellyB which is obviously worse. Kelly have you tried doing a reset starting with he less invasive one of pressing and holding the end call button?  If that does not work try the full reset which will cause you to add your accounts, etc again.

My audio had issues pre and post update where it mutes everything for a second and comes back on regardless of the source. The only thing I could see is whenever an app from google updates it will make the amp cut out and back on but i haven't had any apps update since the new radio update was installed. I also noticed it in the past when the offline map built into the radio restarts itself and isn't running on just data. I just take it for what it is as it's not too long of the cut out period.

  • Replies 243
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

ember1205
ember1205

A) The slated time allotted for this update appears to be two hours based on the conversation I had with the Service Writer when I made my appointment. B) The length of time indicated is apparent

newdude
newdude

We've done a bunch of these.  Its 1.5-2.5 hours depending on internet connection, GM servers and how busy they are, etc.     Big thing is the order the steps are done in.  Radio update is ty

kickass audio
kickass audio

I will keep everyone posted. I'm going in tomorrow for a oil change (doing that while still under warranty then will do them myself at home) and to have the recall work performed.

Posted Images

Byrds8 Enthusiast

Byrds8

Posted
Posted

Others on the ZR2 specific forums have said they have had issues with the new update. Glad I waited on getting it. 

DubVBenz Enthusiast

DubVBenz

Posted
Posted

I'd like to get the update to see if it resolves my Android Auto issues, which have seemed to worsen over the recent months. I'll get in the truck, it'll connect and display my google maps for about 30-60 seconds, then disconnect. Cycling bluetooth on my phone and choosing myGMC as soon as it comes back on fixes it.. until the next drive cycle. 

 

Other issues that have popped up: Sometimes I cannot get AA to connect at all, until I do a hard reset of the head unit. With increasing frequency, my cameras will not come on automatically or when pressing the button, and they will also not stop showing when I hit 10-20mph as they're supposed to. The overlays, for actions like adjusting the HVAC, are also inconsistently displayed. 

 

I don't use my bluetooth phone much, but I don't want to introduce the crackling problem. Others have mentioned it's seemed to resolve itself over time, can anyone else share those experiences? In the IT world it's very unlikely for things to "fix" themselves unless something is changed. 

tbare54 Enthusiast

tbare54

Posted
Posted

Prior to receiving the update my radio would read my text messages to me, that I receive on my iPhone , then ask if I want to reply. It no longer asks if I want to reply, anyone figure out how to enable that??

rrmccabe Enthusiast

rrmccabe

Posted
Posted
On 10/25/2024 at 5:54 PM, sjgris said:

  Pretty sure the turbo not related to this update!

You underestimate  the GM infotainment teams ability to screw things up.

Today my infotainment system was stuck on "retrieving content" or something to that effect and I finally held down the end call button and reset it and it came back.

Yesterday the Next/Prev buttons on the left back of steering wheel would not work but eventually came back.
 

I like the refresh trucks dash/radio setup but no question its the buggiest system I have ever messed with.  I am a Microsoft network engineer and play around with amateur radio equipment as a hobby and GM takes the cake on this one. Very unreliable!

  • Like 2
DubVBenz Enthusiast

DubVBenz

Posted
Posted

So ****ing sick of GM. Brought the truck in for this recall update. Went to pick it up... Android version 10 (supposed to be 12). Kernel last updated Aug 2023, Security patch last updated Feb 2023. So no, they didn't actually update the head unit. What did I need to do as soon as I got in this piece of ****** truck? another hard reset to get my phone to connect. What a garbage company and garbage vehicle. 

DubVBenz Enthusiast

DubVBenz

Posted
Posted

Can anyone provide a screenshot/image of your Android version, kernel version and security patch version post-update showing Android version 12? I want to provide evidence of where this HU needs to be post-update. Another day wasted on a piece of garbage. 

NW-Shadow21 Enthusiast

NW-Shadow21

Posted
Posted
56 minutes ago, DubVBenz said:

Can anyone provide a screenshot/image of your Android version, kernel version and security patch version post-update showing Android version 12? I want to provide evidence of where this HU needs to be post-update. Another day wasted on a piece of garbage. 

20241029_171753.thumb.jpg.eb094ca7b5e2e47388bc3892a231ca82.jpg

DubVBenz Enthusiast

DubVBenz

Posted
Posted

Thank you so much @NW-Shadow21 . Can you confirm that's a 1500 model? I know mine is the GMC variant, but they're basically the same. Was yours updated with the  N242435631 recall, or something else? This is great information. 

NW-Shadow21 Enthusiast

NW-Shadow21

Posted
Posted
2 minutes ago, DubVBenz said:

Thank you so much @NW-Shadow21 . Can you confirm that's a 1500 model? I know mine is the GMC variant, but they're basically the same. Was yours updated with the  N242435631 recall, or something else? This is great information. 

Yep 1500 RST it was updated October 8th for the recall N242435631

 

  • Like 1
ember1205 Senior Enthusiast

ember1205

Posted
Posted
1 hour ago, NW-Shadow21 said:

Yep 1500 RST it was updated October 8th for the recall N242435631

 

Mine is a 2024 RST, but the build is 172 (not 175) and the Security Patch update date is something like Feb 2024. They do not all update to the exact same build for some reason, but it absolutely SHOULD be Android 12.

  • Like 1
DubVBenz Enthusiast

DubVBenz

Posted
Posted

There have been 3 additional revisions to this bulletin, with the most recent that I could find posted here: https://static.nhtsa.gov/odi/tsbs/2024/MC-11007681-0001.pdf . I am printing this off and including it when I drop the truck off next (later today...). Not sure if competitor forum links are allowed to be shared,but there's a thread over on the ZR2 forums discussing this revision: https://www.chevyzr2.com/threads/recall-n242435631-03.2586/  

J69759623 Enthusiast

J69759623

Posted
Posted (edited)

 

Quote

 

REVISION: N242435631-05

This bulletin is being revised to remove the radio programming and to update the Warranty Information table. Please discard all previous copies of N242435631.

 

 

Edited by J69759623
  • Like 1
DubVBenz Enthusiast

DubVBenz

Posted
Posted
10 minutes ago, J69759623 said:

It appears with the latest revision -05 radio programming is no longer a part of the recall. 

 

Thank you. I found the -04 revision, and it looks like it drops the radio update as well: https://static.nhtsa.gov/odi/tsbs/2024/MC-11008247-0001.pdf 

 

Do you have a link to the -05 version? 

 

If I'm reading this correctly, it looks like there may have been complaints after the radio updates in earlier revisions regarding bluetooth phone calls. Perhaps they've dropped the radio/android updates in the later revisions while they attempt to get that sorted out. I'd would rather sacrifice bluetooth call quality to have a functional HU. 

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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