Jump to content

Speech Services by Google Notification / AC blower motor pauses thinking microphone has been activated

Gaimcock
 Share

Recommended Posts

Gaimcock Enthusiast

Gaimcock

Posted
Posted (edited)

2022 Sierra 1500 AT4 with Technology package. 

 

Installed the 2nd OTA update a couple weeks ago.  I got 2 OTAs in about a week time.    This one is GM N23-240353.

 

Two issues that weren't previously issues.  Now, upon startup of truck, I have to x out of this notification

 

image.png.f882508df94777715f32c793741a925c.png

 

Second issue:  about 5 seconds after truck is cranked, AC "pauses" as if the microphone has been activated on Android Auto.  It doesn't blow normal until I either mute the radio or toggle the microphone button - then it normally starts blowing normal.

 


Both super annoying.  Anyone else seeing this and anyone have any ideas?


I've totally disabled the Speech Services by Google app, didn't help.  It did eliminate the pop up, but AC issue still prevalent.  

 

 

Edited by Ryan Foster
Correction
jaxcam02 Enthusiast

jaxcam02

Posted
Posted

Yes, I have that exact issue after some updates as well. It is at the dealer now for the third time among a number of other issues caused by updates.

Gaimcock Enthusiast

Gaimcock

Posted
  • Author
Posted

I really want to just roll back the update.  Is that possible?  Can't find out how.  I'd also be willing to factory reset the software if that deletes out the software updates.

White LTZ Enthusiast

White LTZ

Posted
Posted

Same issue here with the annoying notification and the fan speed.  I hope GM has a fix for this in the very near future.

I've had the truck for 11 days and it did get an update right after I got it home.  I'm not sure if this problem was present before the update but it sounds like the update may have caused this.

 

  

  • Gaimcock changed the title to Speech Services by Google Notification / AC blower motor pauses thinking microphone has been activated
jaxcam02 Enthusiast

jaxcam02

Posted
Posted

Update, GM has a service bulletin for it but there is no fix for it yet. As far as rolling back updates. Not possible.

White LTZ Enthusiast

White LTZ

Posted
Posted

My truck did an update last night, but I still have the same issue.  Also, I noticed that my push to talk button doesn't work.  A short press will activate the Google service, but a long press is supposed to activate Siri.  A long press does nothing.

 

  

jaxcam02 Enthusiast

jaxcam02

Posted
Posted
1 hour ago, Ryan Foster said:

Good deal, thx.  Do you know service bulletin #?

So I just looked at my paperwork. Apparently it is no yet a bulletin but just a GM Doc # 6378631.

Ricks Munn Enthusiast

Ricks Munn

Posted
Posted

It looks like their website is down or something. What did it say?

Gaimcock Enthusiast

Gaimcock

Posted
  • Author
Posted
1 hour ago, Ricks Munn said:

It looks like their website is down or something. What did it say?

Just that it's a known issue.

Sammy64 Enthusiast

Sammy64

Posted
Posted

Same issue here, 22 Refresh 1500 LT Z71 W/O-DFM... I had another issue with my Trk, The rear camera was replaced and the firmware was updated during that visit, all was good and everything worked.
Fast forward 2 weeks later and the first of 2 OTA came through, Then the 2nd one about 5 days later, and that's when it all went to the dogs. 
same issue as above, running the fan, AC or not, it doesn't matter, the Radio burps and the fan speed drops just like I was on the phone, During this time I have noticed the steering wheel controls (volume and switch radio stations buttons on the back of the steering wheel) stop working. 
The radio will burp the 2nd time and then it seems like everything is back to normal with the controls, but the fan speed is still very low. I have to use the mute button on the steering wheel to mute whatever it is, and the fan speed goes back up automatically to where it should be. 

The update was GM QIHM22B-00708  

20230902_125735.jpg

Gaimcock Enthusiast

Gaimcock

Posted
  • Author
Posted

Update, Services by Google notification is now not every start up, I would say about 75% of the time, so intermittent.  

 

Blower speed change also now intermittent, and at times seems to fix itself without me toggling mute on off. 

  • 4 weeks later...

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

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

      By Grumpy Bear · Posted

      I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • revmanii
      Looking at ordering a '26 WT because I want a std cab, std bed

      By revmanii · Posted

      Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...