Jump to content

Recommended Posts

Posted

Has anyone figured out the way to not have my phone volume lower all the way to its lowest setting when I turn the truck on and the phone connects to bluetooth? I messed with settings on my IphoneX, but nothing seemed to work.

 

Thank you!

  • 2 months later...
Posted
On 7/25/2019 at 4:16 PM, mattsvtcobra said:

Has anyone figured out the way to not have my phone volume lower all the way to its lowest setting when I turn the truck on and the phone connects to bluetooth? I messed with settings on my IphoneX, but nothing seemed to work.

 

Thank you!

THIS HAPPENS when an iPhone is connected through bluetooth, the iPhone defaults to the volume button on the phone, not on the radio.

In order to hear "line volume" either connect through USB cable/CarPlay OR turn the volume on your phone to its highest setting.

  • 2 weeks later...
Posted
On 10/17/2019 at 1:30 PM, rbrjr1 said:

THIS HAPPENS when an iPhone is connected through bluetooth, the iPhone defaults to the volume button on the phone, not on the radio.

In order to hear "line volume" either connect through USB cable/CarPlay OR turn the volume on your phone to its highest setting.

So you want me not to use bluetooth and plug my phone in every time? If you use bluetooth, it turns down your volume every single time, to the lowest setting. No matter what.

Posted
On 10/25/2019 at 4:32 PM, mattsvtcobra said:

So you want me not to use bluetooth and plug my phone in every time? If you use bluetooth, it turns down your volume every single time, to the lowest setting. No matter what.

Thats because you leave the volume on your phone down.

the bluetooth connection doesn't have the bandwidth or the speed that the lightning connector/USB has, which is why Carplay doesn't work unless you're plugged in. (too much data to transfer over bluetooth for a "real time" experience)

Posted
16 minutes ago, rbrjr1 said:

Thats because you leave the volume on your phone down.

the bluetooth connection doesn't have the bandwidth or the speed that the lightning connector/USB has, which is why Carplay doesn't work unless you're plugged in. (too much data to transfer over bluetooth for a "real time" experience)

Sorry, We are talking 2 different things I guess. When you get in and turn the truck on, it lowers the ringer volume all the way down. Many people are complaining about this and there is no fix. Doing the "change with buttons trick" doesn't seem to work for most people.

 

 But the bluetooth and Apple car play information you are stating is not correct. My wife's car does not need to be plugged in for Apple car play to function. 

  • Like 1
Posted
3 hours ago, mattsvtcobra said:

Sorry, We are talking 2 different things I guess. When you get in and turn the truck on, it lowers the ringer volume all the way down. Many people are complaining about this and there is no fix. Doing the "change with buttons trick" doesn't seem to work for most people.

 

 But the bluetooth and Apple car play information you are stating is not correct. My wife's car does not need to be plugged in for Apple car play to function. 

sorry.. good luck fixing the problem.

  • 1 month later...
Posted

Same issue.  I have disconnected Bluetooth until a solution has been found.  Otherwise, I forget to turn the phone volume back up and I miss texts & calls.

  • Like 1
Posted

I have only had this 19 a couple of days but I kept missing calls and finally figured out same as these other guy that every time I drove this truck and the phone connected to Bluetooth the phone ringer volume was turned to the lowest level.

I have a theory (tongue in cheek) maybe it is OnStar punishing me because I turned down their high pressure sales pitch when I picked the truck up......... Quote "Well if you don't give me a CC number you don't get your free month of OnStar"   This might be considered a quid pro quo?   

  • Haha 1
  • 3 weeks later...
Posted

I personally think it does this simply for safety reasons.  My Android phone does the same thing when connected via blue tooth, it turns on a "Do not disturb" mode which mutes the ringer and notifications on the phone.  Calls do go through hands free on the truck but I miss texts, and again I think it does this so that you are not having to handle the phone while driving.  If connected to Android Auto via USB cable I get notifications when I get texts via Android Auto and it also reads them aloud if I so choose and can also reply hands free. 

Posted

I recently switched from Android to Iphone due to everyone in my family having one. Because of this issue, I switched back to Android. The only time I had this issue was with the Iphone. Android works fine.

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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   5 Members, 0 Anonymous, 1,769 Guests (See full list)


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