Jump to content

Truck automatically turns down AC fan when I get a phone call.

No F-bdy Bs
 Share

Recommended Posts

No F-bdy Bs Enthusiast

No F-bdy Bs

Posted
Posted

25' Custom trim. This damn thing have adaptive Hvac or some ******? 

Everytime I answer a call through the truck, it turns the AC fan level down to what seems to be the lowest setting. 

I'm in Louisiana. I don't need the truck trying to be courteous,and quiet. 

I dug into all the settings, but couldn't find anything. 

 

Z45 Senior Enthusiast

Z45

Posted
Posted

Mine does it too.  Can't please everyone, what bothers you, pleases others. 

newdude Senior Enthusiast

newdude

Posted
Posted
2 hours ago, No F-bdy Bs said:

25' Custom trim. This damn thing have adaptive Hvac or some ******? 

Everytime I answer a call through the truck, it turns the AC fan level down to what seems to be the lowest setting. 

I'm in Louisiana. I don't need the truck trying to be courteous,and quiet. 

I dug into all the settings, but couldn't find anything. 

 

 

 

Normal and working as intended.  Fan speed lowers to quell cabin noise being picked up by the microphone.  

  • Like 1
Pryme Senior Enthusiast

Pryme

Posted
Posted
7 hours ago, No F-bdy Bs said:

I know WHY it does it. 

I want it to NOT do it. 

More and more “features” that are just annoying. Nothing like that on my poverty edition w/t. Just a simple dial that I myself decide when and how much I want to turn it. 

  • Haha 1
newdude Senior Enthusiast

newdude

Posted
Posted
7 minutes ago, Pryme said:

More and more “features” that are just annoying. Nothing like that on my poverty edition w/t. Just a simple dial that I myself decide when and how much I want to turn it. 

 

 

OP has a poverty spec too.  Custom trim which is a WT with a couple extra bits.  Both have the same climate setup, semi-auto "manual" HVAC.  You have control over fan, temp and direction but it can handle some things on its own like for instance lowering fan speed for using phone and voice commands.  

  • Like 2
Pryme Senior Enthusiast

Pryme

Posted
Posted
1 hour ago, newdude said:

 

 

OP has a poverty spec too.  Custom trim which is a WT with a couple extra bits.  Both have the same climate setup, semi-auto "manual" HVAC.  You have control over fan, temp and direction but it can handle some things on its own like for instance lowering fan speed for using phone and voice commands.  

Mine is the limited edition extreme poverty edition though. I’ve never noticed the fan lowering when I get a call. I never plug my phone in though either so maybe that’s needed? It does connect to my truck when I am in it tough. 

newdude Senior Enthusiast

newdude

Posted
Posted (edited)
14 hours ago, Pryme said:

Mine is the limited edition extreme poverty edition though. I’ve never noticed the fan lowering when I get a call. I never plug my phone in though either so maybe that’s needed? It does connect to my truck when I am in it tough. 

 

 

It would be when using bluetooth or apple carplay/anrdoid auto.  It lowers once the call is picked up, not when its ringing.  Or if you trigger voice commands for bluetooth or carplay/AA it lowers. 

Edited by newdude
  • Thanks 1
Epsilon Plus Enthusiast

Epsilon Plus

Posted
Posted

You can override it on my LT with auto by manually upping the fan speed. 

 

Your wife will love the "WHOOOOOOOOSH" coming over the microphone when you talk to her. Women absolutely love loud background noise/sound on phone calls. Ask any blue collar guy who gets a phone call at work on an ear bud.

  • Like 1
  • Haha 1
Pryme Senior Enthusiast

Pryme

Posted
Posted
2 hours ago, newdude said:

 

 

It would be when using bluetooth or apple carplay/anrdoid auto.  It lowers once the call is picked up, not when its ringing.  Or if you trigger voice commands for bluetooth or carplay/AA it lowers. 

I’ve never tried to use voice commands didn’t know I had that feature. This w/t is too feature rich for me I guess lol. Is there a T trim level under w/t? Just “truck”

EXSlider400 Senior Enthusiast

EXSlider400

Posted
Posted

But this is the only vehicle I have driven that the fan speed does not return to the higher speed after the call ends. Gets annoying to keep turning it back up after every call or text. 

EXSlider400 Senior Enthusiast

EXSlider400

Posted
Posted (edited)

When I go to car shows, you would be surprised how many young kids ask how to roll down the windows because there are no buttons…and I still love my side vent windows. BTW… Cruisin the Coast is right around the corner!!! 

Edited by EXSlider400

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

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...