Jump to content

GM leather seats

Byron Sparrow
 Share

Recommended Posts

Byron Sparrow New Member

Byron Sparrow

Posted
Posted

Hello, I’m new to this but I would like to see who else is having issues with the leather seats on their 2018 GMC  Sierra pickups . The driver side has cracks in the bottom cushion and the back of the seat along the edges is also showing lots of wear. (By the way I only weigh 162#) when I was finally able to get in to the dealer for an oil change (39172 miles) I  questioned  the dealer and they said GM would not Waranty any seat wear. My wife has a 2012 Honda Pilot with over a 100k and the seats look brand new.  

dplarson Enthusiast

dplarson

Posted
Posted

Not sure about the 2018 as I have cloth in my truck.

My 2006 Suburban with leather did the same thing you describe.

I took the Suburban to a local upholstery shop and they said yep, they all do that.
They were able to replace the bottom side of the driver's seat for not a lot of $.
I didn't mess with the sides of the back, they weren't so bad on mine until years later.

Good luck getting it covered under warranty!

In years past I've seen Volvo warranty seat and door upholstery but never GM :(

Sent from the demons in my head

  • Like 1
Donstar Senior Enthusiast

Donstar

Posted
Posted

Welcome to this forum!  I suggest taking your truck to an upholstery shop and have it repaired like dplarson.  Once this is done, practice and get in the habit of not sliding on the edge of your seat when entering and exiting.  If you don't have step bars then get some to ease getting in and out.  I wore the edge of the driver's seat out in my last truck and made the conscious decision not to do it on my current truck.  I've had this truck since Nov. '15 (leather) and the seats are like new.  I'm heavier than you and in and out of my truck several times per day.

  • 1 month later...
Chadw90 Enthusiast

Chadw90

Posted
Posted
On 7/14/2020 at 9:52 AM, Byron Sparrow said:

Hello, I’m new to this but I would like to see who else is having issues with the leather seats on their 2018 GMC  Sierra pickups . The driver side has cracks in the bottom cushion and the back of the seat along the edges is also showing lots of wear. (By the way I only weigh 162#) when I was finally able to get in to the dealer for an oil change (39172 miles) I  questioned  the dealer and they said GM would not Waranty any seat wear. My wife has a 2012 Honda Pilot with over a 100k and the seats look brand new.  

I have a 2018 with 28,000miles. Same thing. At the back corners on a 45 degree angle to the center, its wrinkled and cracking. Dealer changed the seat at 10,000miles due to this and it was loose/rocking forward and backwards. 
the rocking didnt go away. And its all cracking again. Seats get AC Delco leather conditioner applied Every 3500miles. 
 

junk leather. Nothing compared to a ford or ram now. GM use to be the cadillac of trucks for interiors, now they at the bottom of the barrel. 

  • 2 months later...
Cosmic Charlie Enthusiast

Cosmic Charlie

Posted
Posted

My 2015 HD 25 SLT has the same crack on the Drivers bottom seat SIDE toward the rear - it showed up at about 70,000 miles and grows a bit more each year - is about 2" long now with 125,000 miles - I'm the only driver and weigh 170 lbs - obvious defeat by GM

 

I've tried High Performance Kevlar Tape but it eventually unsticks

 

I have some glue made to FUSE plastic tarps permanently together, I may try that if I find some Black Seat Plastic or something in my travels +-

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

    • Chuck FB
      summer road trips in the 2026 2500HD

      By Chuck FB · Posted

      I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...