Jump to content

Radio volume way to low (2014 Silverado)

Ryan Los

Recommended Posts

Ryan Los New Member

Ryan Los

Posted
Posted

Recently got a 2014 silverado and I love the truck everything is great but the radio volume. Even with the radio turned ALL the way up it's not very loud, I can have a conversation on full volume. Ive noticed when my iPhone is hooked up its slightly quieter than if I just had FM radio on, it's hardly a difference. Curious why this truck is so ****in' quiet I mean my old car (1998 malibu) with all stock was WAY louder. Im a metal head and you cant listen to the music low, curious if thers anything I can do and beleive me ive already checked the settings lol

SouthernSilveradoGuy85 Senior Enthusiast

SouthernSilveradoGuy85

Posted
Posted

I don't have Bose and I've never had to put mine at 1/2 or higher. That's also going down the interstate with all windows down going 75 mph. That's also with a Flowmaster Super 44 exhaust which could wake up the dead on a cold start.

 

I know you've already checked the settings. But, maybe you should also check the balance of front to rear and side to side. If everything is fine then something could just be wrong with the head unit.

Ryan Los New Member

Ryan Los

Posted
  • Author
Posted

Thanks for advice I took into the dealership since im still under warranty and the guy didnt seem to want to do anything about. It should be louder!!

camcamaro1991 Enthusiast

camcamaro1991

Posted
Posted

Sounds like someone had done some work to the system, possibly an aftermarket was in there and now removed. You're phone directly connected (NOT Bluetooth) should be a noticeable difference in volume and SQ (depending on phone of course) I know my iPhone sounds far better than even HD radio and is louder at the same volume level.

Crstfr Enthusiast

Crstfr

Posted
Posted

is it set to turn down when you drive at certain speeds.. i think there's an option for adaptive sound or i thought i saw one in there...... . just fishing... .. .adaptive sound might not be there wright word for it.. sorry..

Cosmic Charlie Enthusiast

Cosmic Charlie

Posted
Posted

Had my Door Chime LOWERED - Radio reprogram to lower the loudness of the ding warning (TIS2Web) (40 minute download) so maybe they can UP yours whereas someone may have had it in the shop and messed it up ...

2016 Sierra Owner Senior Enthusiast

2016 Sierra Owner

Posted
Posted

I noticed this just today. My 14 did not have Bose and some songs I like to crank up the volume. It would have to be (by the level indicator bar) all the way up to get loud. Today though in my 16 with the Bose system I had the radio cranked up or so I thought but when I looked at the volume level bar it was only 1/2 way up.

Archived

This topic is now archived and is closed to further replies.

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...