Jump to content

Recommended Posts

Posted
1 hour ago, kickass audio said:

is it actually cold enough for the defrosters to kick on? My wheel and seats have been kicking on but never my mirrors or back window yet, it must be lower than 40 degrees or something like that to get it to automatically kick on.

Not sure,it was 40 or 41. I hope that's the case. Supposed to be low of 37 Thursday night.  I'll try then. Yes my wheel and seats do come on.

  • Like 1
Posted
Just now, 15 Z71 said:

Not sure,it was 40 or 41. I hope that's the case. Supposed to be low of 37 Thursday night.  I'll try then. Yes my wheel and seats do come on.

Freezing is 32 degrees and I know it was right around that point where my mirrors would kick on. Lately it's been warm and cool to make a good amount of dew on the outside but if I start the truck my vents are in their default defrost state and the heated seats and wheel are automatically on but the mirrors and rear glass never kick on until I get in and turn them on.

 

If you wanted to try it, you can put a ice cube on the little bubble under your passenger mirror which is supposed to be the exterior temperature sensor and see if you can get it cold enough then try to remote start the truck and see if the defrosters will kick the circuit on for you.

  • Thanks 1
Posted
12 hours ago, kickass audio said:

is it actually cold enough for the defrosters to kick on? My wheel and seats have been kicking on but never my mirrors or back window yet, it must be lower than 40 degrees or something like that to get it to automatically kick on.

It might depend on location as to whether the temps are low enough for all features to activate with remote start or on vehicle start-up. My seat and wheel turned on yesterday when i started the truck, but the AUTO setting for the climate control did not engage the defrost function and the rear defrost also didn't turn on. It was in the mid-50's at the time.

Posted

I supposedly got mine done this morning. (2 hours at dealer)   Reading above posts, it seems I should be on android 12.  I’m still on android 10.

not happy, unless I’m missing something 

 

2024 Chevy zr2 2500

Posted
47 minutes ago, panicfishwater said:

I supposedly got mine done this morning. (2 hours at dealer)   Reading above posts, it seems I should be on android 12.  I’m still on android 10.

not happy, unless I’m missing something 

 

2024 Chevy zr2 2500

 

 

"not happy"  

 

Can't go by the Android version.  

 

You need to look at another page in the radio.  Settings, System, then touch where it shows the Android version.  Once you are in the build menu, scroll down until you see a line of build that has the "Y" version on there.  If the radio was updated, you should see a Y172.5.  If it is NOT Y172, the dealer only did half of your recall.  

Posted
19 minutes ago, newdude said:

 

 

"not happy"  

 

Can't go by the Android version.  

 

You need to look at another page in the radio.  Settings, System, then touch where it shows the Android version.  Once you are in the build menu, scroll down until you see a line of build that has the "Y" version on there.  If the radio was updated, you should see a Y172.5.  If it is NOT Y172, the dealer only did half of your recall.  

Had mine updated last Tuesday,now android 12 and version 175.5 all seems well

20241011_140313.jpg

Posted
2 hours ago, newdude said:

 

 

"not happy"  

 

Can't go by the Android version.  

 

You need to look at another page in the radio.  Settings, System, then touch where it shows the Android version.  Once you are in the build menu, scroll down until you see a line of build that has the "Y" version on there.  If the radio was updated, you should see a Y172.5.  If it is NOT Y172, the dealer only did half of your recall.  

Isnt the newest version that they are supposed to be installing, Android 12? Seems like every post I have seen on this has this one installed vs 10.

Posted

Beware of update...it causes popping and cracking to your phone calls and the radio speakers still go out!  They are working on yet another fix for this...more to come...

Posted
1 hour ago, panicfishwater said:

Yep.  They didn’t finish.  
Y169.3.2

 

 

Take it back then.  The serial data gateway recall includes reprogramming the radio if it is not up to date.  

Posted
4 hours ago, NW-Shadow21 said:

Had mine updated last Tuesday,now android 12 and version 175.5 all seems well

20241011_140313.jpg

 

 

I'm wondering if Y175 takes care of some of the issues popping up with Y171 and Y172.  

Posted
1 hour ago, Byrds8 said:

Isnt the newest version that they are supposed to be installing, Android 12? Seems like every post I have seen on this has this one installed vs 10.

 

 

The build number is what GM/dealers go by.  Customers seem to be attached to the "android version" but in update land its the build number that's important.  The software update TSBs have details of the updates via that build number.  Y172 was the latest, apparently there is a new Y175 that must have just arrived.  

  • Like 1
Posted
11 hours ago, newdude said:

 

 

The build number is what GM/dealers go by.  Customers seem to be attached to the "android version" but in update land its the build number that's important.  The software update TSBs have details of the updates via that build number.  Y172 was the latest, apparently there is a new Y175 that must have just arrived.  

I understand build numbers are important in updates. But, generally speaking, the building number for a different version of an OS will still be higher than an older version. Android 12 will be, to some degree, different than Android 10 regardless of build number.

Posted
On 10/8/2024 at 8:40 PM, kickass audio said:

is it actually cold enough for the defrosters to kick on? My wheel and seats have been kicking on but never my mirrors or back window yet, it must be lower than 40 degrees or something like that to get it to automatically kick on.

You were right,finally got under 40 degrees and it worked.  Defrost and rear Defrost came on. I guess it was not cold enough.  I guess I felt like my 15 came on at a higher temp. I'm just happy it all works OK. Was worried that update they did messed up something. 

  • Like 1

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...