[spb1122]

I went to my dealer today.
I brought a copy of the TSB and the screen shots from this forum.
The service writer was receptive to my request, and the update was performed as requested, without any resistance.
No charge to me, all part of my 3 year/36K mile bumper-to-bumper warranty.
No questions asked.
I have to say it was one of the best experiences I've had with a dealership Service Department in my 45+ years of driving. They simply did the right thing without any hassle.

Of note is that the version they updated to was V810, not V809 as I've seen so far. I Googled V810 (quickly), and couldn't find anything on it.
On one hand I suppose I got the most recent release.
On the other hand I hope that V810 continues to resolve the issues as well as V809 has per reports on this forum.

I hope V810 doesn't introduce any new bugs.

FWIW, on the ride home, I stopped once, used my phone to make a call, used my Motorola MA1 for Android Auto and Google Maps, switched audio sources, and scrolled through settings and options.
No hiccups at all, everything worked as it should. Could be my imagination, but everything did seem a bit snappier, cleaner, and quicker.

I'll update if anything changes.

My "About" screens DO show the update. I mention that because I've read about others here that have had a dealer claim to have done the update, but their radio does not show the update. I suspect that those updates were not performed properly by the dealer in one way or another. Of course, egos and pride get in the way sometimes. As just one example, the doors must all remain closed for the entire process while the radio is updating. Opening a door during the update will FUBAR the update. There are some other specific nuances as well (lights, battery charge level, the dealers connections and network, etc.), but at the end of the day, I believe your radio SHOULD show the update. If it still reads V807, I don't believe you were successfully updated.

 

[gherbert]

Glad you were able to get it updated without any issues from the dealership
Might be the latest update since the TSB was released

 

[Hikesmtns]

Update, radio has rebooted 2 times since the second “update”. About to choke the people at the dealership. Been updated 2 times so far and still says version 808. Idiots have no clue what they’re doing. I’m bringing it back and they told me they’ll replace the radio if the problem persists. Wonder if the new radio will have the correct software in it. So done. Love the truck otherwise

 

[spb1122]

Update, radio has rebooted 2 times since the second “update”. About to choke the people at the dealership. Been updated 2 times so far and still says version 808. Idiots have no clue what they’re doing. I’m bringing it back and they told me they’ll replace the radio if the problem persists. Wonder if the new radio will have the correct software in it. So done. Love the truck otherwise

Maybe you could try a different dealership? Or, show your current dealer the screen shots posted in this thread that prove the updated version should show on your radio if the update is installed correctly? Maybe your dealer and/or their tech could call my dealer/tech for tips, instructions, pitfalls?

 

[gherbert]

Update, radio has rebooted 2 times since the second “update”. About to choke the people at the dealership. Been updated 2 times so far and still says version 808. Idiots have no clue what they’re doing. I’m bringing it back and they told me they’ll replace the radio if the problem persists. Wonder if the new radio will have the correct software in it. So done. Love the truck otherwise

It also could be that the radio is not taking the update.
Yes, the Dealership could be messing up.
But, Sounds like it might be the next step for a radio that will not update

 

[spb1122]

Update 6/20/23:

My infotainment center has NOT had the black screen/reboot/splash screen episode happen once since I received the update, so that is good.

However, I have had two instances where Android Auto did not connect properly on start up. Now, there are many factors that could be issues in this regard. I have an older phone, and I use the Motorola MA-1 to achieve wireless Android Auto. Most of the time it all starts up just fine, only twice since the update has it not hooked up properly. That is also a HUGE improvement over pre-update, so I suppose I'll take it.

Historically, when Android Auto did not connect, I had to shut down the truck, wait the few minutes for everything to shut down completely (power to the USB ports, and for the anti-theft to turn on), then restart the truck. Android Auto has always hooked up on the first restart. I've tried restarting my phone, pulling the MA-1 plug to reboot it, both, etc. Only restarting the truck has worked.

Till yesterday.
The second time Android Auto did not fire up properly.
I discovered something new, which might be a major clue/solution to the issue. I have not read about this anywhere else (and I've read A LOT on this issue), so I figured I'd post it up here, and see what shakes out.

My wife happened to be driving, so as a passenger, I was able to tinker a bit deeper with the set up.
I tried the usual, pulled the MA-1, restarted it, restarted the phone, looked at settings on the head unit, looked at settings on the phone, did the "power off" for the head unit (which doesn't really power it off). Same non-result. Android Auto would not hook up.
I thought I'd try switching the MA-1 to the other USB port. That other USB port hold a flash drive containing music. I changed the source on the radio to USB, and ...WTF?... the screen reads "no device detected". Though that was odd, because while I don't use the USB music very often (it's only a back up for when FM radio and/or Spotify don't work), I've never seen that "no device detected" message before.

Sidenotes: There is power to both USB ports. Light on MA-1 is blinking green, and the flash drive light is blinking. I have changed this dual USB port once before because there was no power to one of the two ports, and no data transfer from either port. Best guess is something on the circuit board(s) in the ports fried. The new port resolved all that, and continues to function now.

Anyway, before I swap the MA-1 and the flash drive, I pull the flash drive and reinsert it into the same port. The head unit immediately recognizes the flash drive and starts to play music..

AND...

Android Auto hooks up without me touching the MA-1, my phone, or the head unit.
It's like the flash drive was "blocking" the data road.

So I pulled the flash drive, and will be leaving it out for now. If Android Auto fails to hook up on start up again? Oh well, I'll just have to make the best of it I suppose. If it never happens again while the flash drive is out? I'm no electronics expert, but I'm going to really suspect that the dual USB port itself, and the circuitry inside that hub, may have something to do with the Android Auto issues, and/or the infotainment issues.

 

[Hikesmtns]

Mine has rebooted without CarPlay on. Nothing plugged into the usb. It’s amazing how we have research this problem ourselves for a $45.000 truck. GM knows exactly with the problem is but won’t admit it because it’s not a safety issue. It’ll cost them money if they do.

 

[gherbert]

Thanks for updating us
Glad to hear that things got better
Hopefully the other bugs will sort themselves out

 

[Ngel]

Went to the dealer and found out the whole radio was covered under my extended warranty and they even replaced my battery as well. They installed a brand new unit. Took 4 hours because the update did not work the first 2 times but finally worked on 3rd time. Mine is showing version 810 now.

I have not had a chance to check and see if it reboots while using CarPlay and the phone. I will update my results. So far so good, and probably one of the best experiences I have had at a dealer with service yet. Guess it pays to have the extended warranty. They said the warranty cover $1600 worth of service between the battery and the head unit.