Jump to content

Driver display screen will not switch back after phone call


Recommended Posts

Posted

I was wondering if there is a way to fix this or is everyone experiencing this. When I make a call the touch screen goes from radio to phone screen and after the call it will not go back to the radio screen unless I push the radio button. The thing that bothers me the most is the driver info screen. When I receive a call the driver info screen shows who is calling which is normal but after the call it will not go back to the screen it was in before the call. Example if I have the screen set to the digital speed read out and someone calls it goes to the incoming call screen but when I end the call it stays in the incoming call screen then I have to back and select the digital speed screen again. Is this normal or is there a setting I don't know about. My wife's Buick has the same drivers screen and it does not do this when she ends the call it goes back to the previous screen.

Posted

Yep mine does this too. Very annoying. I agree I don't know how they missed this problem during testing but then again, its a software/computer problem and GM builds cars and trucks. This is why Apple and Samsung need to enter the automobile technology market and start selling products to manufacturers to use in their vehicles and let the vehicle manufacturers stick to engineering vehicles.

Posted

I asked my dealer about this...this is what I was told. The screen stays on that because it was the last function you have used. The only way I have worked around it is access your phone though the drivers screen on the dash, this way the 8" screen goes back to the radio once you have completed the phone call, but your smaller screed will stay on the phone setting, at least I can just change it with the steering wheel controls compared to the 8" screen. I agree that I wish you could somehow have a default screen that is your home screen and when you are done doing whatever you want it would go back to your home/default screen.

Posted

I agree that I wish you could somehow have a default screen that is your home screen and when you are done doing whatever you want it would go back to your home/default screen.

 

I'd prefer it just go back to whatever screen was up before I received or dialed any calls.

Posted

I too think this is annoying and that GM should fix it.

 

I'm sure they will at some point with a software update. GM is a little backed up with recalls at the moment.................

Posted

That's the least of your worries. The infotainment is fuggy as buck.

 

I had the VOLUME knob advancing songs on my iphone the other day. No joke. No, I wasn't mistaken, had witnesses. Steering wheel volume didn't do anyhing.

Archived

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

  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...