Jump to content

Recommended Posts

Posted

The FM reception on my GMC Sierra SLE sucks! My previous ride, 2011 Mazda 3 was awesome. I just run my iPod instead mosta the time!

Posted

Gotta love it a 51K truck and they cant put in a decent radio. I live 20 miles north of Philly and I can not listen to my three favorite stations. I will under no circumstances use XM even on the free trial . My wife got me an IPOD nano put about 600 songs on it. That will keep me busy for many an hour. A pox on the designer that designed this POS

  • Like 2
Posted

Same problem here....I thought it was just me. My reception is marginal at best, CONSTANTLY going in and out of HD. My wife's 2013 Acadia with HD radio doesn't have a problem picking up the HD stations in my area. Im about 25 miles outside of Philly in SJ. I pretty much only listen to XM now. Is there a way to disable the HD radio altogether or a possible fix?

Posted

i also leave north of Philly, the radio sation with the strongest signal doesn't come in clear. i agree 50k for a truck and the radio is the worst.

Posted

I just drove an Arcadia last night and the FM reception was just as bad as my Silverado. Although, when the stations were not in HD it did sound a bit better but it kept flopping back in forth. One other thing I cannot understand is why the Arcadia got album art and station art and my truck only gets generic FM and XM logos you would figure it is the same software.

 

Henry

Posted

2014 Chevy Silverado DC, Z71:

 

Worst FM reception of any car/truck I have ever owned. Took it back to dealer and they checked other new Silverado's with mine and they were all the same. Service Tech agreed that the FM reception is not very good. He said he has seen GM come out with a TSB before on radio reception and documented my issue so I would be contacted if GM has a fix for this issue at a later date.

Posted

FM reception is not as good as 2011 silverado or other vehicles I have driven. I have the stock audio system and I had the speakers replaced with Kenwood speakers. The radio sounds terrible in non HD mode and switches back to non HD alot. This is the worst audio system that I have had in any vehicle since the 1980's. Remindes me of the radio in my car in the 1980's when they tried puting the antenna in the windshield.

Posted

Drove my Sierra and a 2013 4 runner over the same route the Sierra's fm reception started to break up twenty miles before the Toyota. Is GM going to address this concern? The radio reception is fine at the dealers location but drive a few miles out of town it is terrible. Can an aftermarket tuner be installed?

Posted

My Mazda Miata had great radio reception, almost never lost a station and it only had a 6" rubber antenna on the rear deck. way to go GMC

Posted

I will keep taking this truck back to dealer for the FM radio reception issue. This is an issue that should not happen with today's technology.

  • Like 2
Posted

I had a signal booster in my truck back in the 70's. Unplugged wire from antenna plugged into box, plugged wire from box into radio, hooked up power wire to fuse box,never ever lost a signal on my supertuner. Was about the size of a pack of smokes. Seems like we have taken a giant leap backwards,welcome to the 20th century Marty McFly

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

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...