Jump to content

Rear Seat Headrest Rattle

RSTPilot86
 Share

Recommended Posts

Wheelguy Enthusiast

Wheelguy

Posted
Posted
22 hours ago, McCoy7 said:

 How did you remove them? 

There are 2 release buttons on the sides of the plastic grommets into which the headrest bars go into. Press them in at the same time and the headrest will pull up and eventually come out. You will probably have to fold the headrest down to get it out.

  • Replies 50
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Wheelguy
Wheelguy

Took my Denali into the dealer for same issue & they pulled the headrest out & gently pulled the bars further apart. No issues since & something that can be done yourself. Figured it might

Wheelguy
Wheelguy

Not a problem. That’s one of the reasons we’re on the forums - to share knowledge & experiences. Thanks goes to the service tech that was nice enough to allow me in the shop area & actually sh

Robwcormack
Robwcormack

Took mine in early last week.  It's the actual grommets/guides that hold the headrest into the seat.  They are replacing them on Tuesday, so hopefully that'll fix it.  Another member on here had the s

TBL569 Enthusiast

TBL569

Posted
Posted
On 7/13/2019 at 11:37 PM, McCoy7 said:

I have had mine 2 weeks and kept hearing a rattle over certain bumps been saying I am going to take it back to service.  I figured out today this is what it is.  How did you remove them? 

Just push the button on one side of the base and wiggle the head rest out, it's a little tight.  I pulled the bars apart a bit when I switched then around and all was good when I put them back in.

McCoy7 Enthusiast

McCoy7

Posted
Posted

I pulled my headrests out and stretched out the bars a little bit and reinstalled and boom problem solved.  Thanks guys!!!!!!

 

I hated to have to do that myself on a brand new truck but sure beats taking time to go to dealer.  

  • Thanks 1
Zach-91 Enthusiast

Zach-91

Posted
Posted
On 7/16/2019 at 8:05 AM, McCoy7 said:

I pulled my headrests out and stretched out the bars a little bit and reinstalled and boom problem solved.  Thanks guys!!!!!!

 

I hated to have to do that myself on a brand new truck but sure beats taking time to go to dealer.  

Just went out and did this to mine as well and so far so good. went for a short drive and all was quiet. Thank you all!

Wheelguy Enthusiast

Wheelguy

Posted
Posted

It’s been a few days shy of 3 weeks since the dealer did a slight pull apart on mine and it hasn’t come back yet.

  • 1 month later...
Renovator New Member

Renovator

Posted
Posted

We recently bought our 2019 Sierra 1500, we have maybe 300miles on it, and the same issue with the rattle in the headrest. Did what Wheelguy suggested and took care of it. Thx Wheelguy.

Wheelguy Enthusiast

Wheelguy

Posted
Posted
6 hours ago, Renovator said:

We recently bought our 2019 Sierra 1500, we have maybe 300miles on it, and the same issue with the rattle in the headrest. Did what Wheelguy suggested and took care of it. Thx Wheelguy.

Not a problem. That’s one of the reasons we’re on the forums - to share knowledge & experiences. Thanks goes to the service tech that was nice enough to allow me in the shop area & actually show me what he was doing and make sure I was OK with it.

  • Like 2
  • 1 month later...
jefferoonie Enthusiast

jefferoonie

Posted
Posted

Thanks, I will have to spread the posts a little bit, and see if that helps.

 

Coming from a 2002 Siverado with over 200k miles that had no rattles, I found it quite annoying.

Chevy's interior quality going down the shitter?

 

Jeff

Openmind Enthusiast

Openmind

Posted
Posted

Great advice on widening the headrest stems.  For those of you that would rather not address this yourself and let dealership take care of it, a temporary solution is to simply fold up a small towel and stuff it between the rear window and back of headrest.

SRBOSST1 Enthusiast

SRBOSST1

Posted
Posted

Yes I have heard this same issue. My temporary solution was... if you press the button as if you were to raise the head rest up, you can instead push them down slightly. They are not locked into place but it does solve the rattle until you can properly have them fixed. I hope my explanation makes sense and I hope it works for you guys too. 

AbsoluteNole New Member

AbsoluteNole

Posted
Posted

I am also having a terrible rattle coming from the rear cabin on the driver's side. The sound is not coming from the headrest like others have suggested but actually from the back seat itself shaking. The only temporary solution I have found is to fold up the rear seat, which keeps the backrest from shaking. I can easily recreate this sound by opening the small compartment in the seat back and shaking the seat.   

geddylee2112 Enthusiast

geddylee2112

Posted
Posted

I am new to the forum.  I picked up a 2019 GMC Sierra SLT a couple weeks ago and had this rattle almost immediately.  I tried spreading the posts apart but it didn't seem to work.  If I take them completely out, the rattle stops.  I have an appointment at the dealer over lunch today.  I can't wait to hear what they have to say.  

geddylee2112 Enthusiast

geddylee2112

Posted
Posted

Just got back from the dealer.  That took almost 2 hours and I even told them where the rattle was coming from.  They were able to replicate the rattle, so that was a win.  Then they took 2 headrests from a truck on the showroom floor and put those in mine.  Apparently, the rattle disappeared.  They ordered me 2 new headrests.  So, now I wait.  

 

Just thought that I would followup in case it helps anyone else.  

 

Brian

  • Thanks 1
crimsontidefan Enthusiast

crimsontidefan

Posted
Posted

Took mine (2019 RST) to the dealer today. Was doing very same thing and was constant. The service manager had fixed one truck before so they told me what to do and it works. 
Lower both headrest down low as they will go. That’s it and it will go away. The posts rattle the inserts if they are up. 

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

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • 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?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...