Jump to content

Recommended Posts

Posted

I believe I have mentioned this before about my audiophile habit. Been into this a long time. I have 3 stereo systems, living room for TV, music, basement for TV, music and garage for music. Living room picture.

 

20220830_102345.jpg

  • Like 2
Posted
1 hour ago, diyer2 said:

I believe I have mentioned this before about my audiophile habit. Been into this a long time. I have 3 stereo systems, living room for TV, music, basement for TV, music and garage for music. Living room picture.

 

20220830_102345.jpg

Yea, I’m with you. I went from a speaker in every corner in my living room to just a sound bar for my tv. Instead of listening to my hundreds of albums and CDs. I listen to pandora via my iPhone on a portable Bluetooth speaker from Walmart. My old speakers are in the garage. I may get ambitious and modernized again. 

  • Like 1
Posted

Was on a solo run the other day and the Bose bass was enough to vibrate the HID display on the windshield. 

Good enough for me. I still like halfway decent sound in my golden years. 

Posted
On 9/2/2023 at 1:24 PM, Mshawn said:

Will do. I’ll do a write up on it. I just ordered the metra 72-4573 speaker harness to see if they will work because I know some have said it would although they are listed to only be compatible with up to 22 year. I ordered them today of Amazon for $7.50 plus free shipping will be here on the 15th and then I’ll install it then post my results.

Changing dash speakers is pretty easy.  There is already a write up with pictures in another thread on the main forum.  I went with the Kenwood speakers recommended  by Crutchfield.  You will lose your turn signal click due to frequency range, but I think there is a filter you can add to get it back.  I replaced everything but the 4" sub under the center console.  It needs an amp to really round it out, which will happen later this fall.

  • Like 1
Posted
6 hours ago, SPASierra said:

Changing dash speakers is pretty easy.  There is already a write up with pictures in another thread on the main forum.  I went with the Kenwood speakers recommended  by Crutchfield.  You will lose your turn signal click due to frequency range, but I think there is a filter you can add to get it back.  I replaced everything but the 4" sub under the center console.  It needs an amp to really round it out, which will happen later this fall.

Ditto. I'm going to wait until someone posts the install instructions and what speakers they use and then I'll go for it.

Posted
8 hours ago, SPASierra said:

Changing dash speakers is pretty easy.  There is already a write up with pictures in another thread on the main forum.  I went with the Kenwood speakers recommended  by Crutchfield.  You will lose your turn signal click due to frequency range, but I think there is a filter you can add to get it back.  I replaced everything but the 4" sub under the center console.  It needs an amp to really round it out, which will happen later this fall.

Where is that write up for changing the dash speakers? I've looked but can't find it.

Posted
20 hours ago, SPASierra said:

Changing dash speakers is pretty easy.  There is already a write up with pictures in another thread on the main forum.  I went with the Kenwood speakers recommended  by Crutchfield.  You will lose your turn signal click due to frequency range, but I think there is a filter you can add to get it back.  I replaced everything but the 4" sub under the center console.  It needs an amp to really round it out, which will happen later this fall.

I didn’t realize there was a write up about it already. I’m doing this a step at a time to hear the changes as I go. I ordered to pioneers ( front dash corners)from crutchfield. I’m going to keep watch the forum here for advice on what works best with theses bose systems a slowly build it 

  • Like 1
Posted
6 hours ago, Mshawn said:

I didn’t realize there was a write up about it already. I’m doing this a step at a time to hear the changes as I go. I ordered to pioneers ( front dash corners)from crutchfield. I’m going to keep watch the forum here for advice on what works best with theses bose systems a slowly build it 

Its of good info in this post:

 

  • 1 year later...
Posted
On 8/29/2023 at 12:57 PM, madweazl said:

Our '24 AT4 "Bose Premium" sound system is the worst sounding system of any car I've had the past 15 years or so (our '05 Evo was terrible lol). Going from the Alpine branded system in our '16 Ram to this was beyond disappointing. Weak highs, no lows, and lots of muttled mid range; unbelievably poor sound quality for any vehicle much less something approaching 6 figures. 

 

SAME issue with my 2024 High Country. My 2020 RST was BUMPIN with the Bose system... 2024 High Country bass totally sucks. 

 

Dealership has been useless with 5 trips. "Yes we know it sounds weaker than the truck on the lot... But we don't know what to do." -- replaced the amplifier & the subwoofer. It might sound a little better... But not much better. 

 

They even reflashed the system a few times... Now there's popping when I'm on phone calls. Worse than before...! 😫 So frustrated...

  • 5 months later...
Posted

Just bought a 2025 Silverado 1500 High Country with the Bose Premium Sound System. My daughter's 2021 Nissan Altima has a better sounding system than this thing does. My Harley Road Glide has a better sounding system. My 2023 GMC 2500 SLT has  abtter sounding system. This thing is flat and lifeless.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   3 Members, 0 Anonymous, 1,554 Guests (See full list)

  • Latest Articles

  • Posts

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