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

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

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