Jump to content

Recommended Posts

Posted

Got a 21 AT4 a few Months ago and the apple car play constantly skips like a scratched CD while listening to music. I’ve tried everything I can think of. Anyone experience this and figure it out?

Posted

Mine does the same thing. It's also been in the dealer for 3 weeks now after they blew out the master cylinder installing the Brembo Front Brake Upgrade. There seems to be a problem on GM's end with the programming. Anyway, I've been in 2 different rentals, a Buick Encore and GMC Acadia and both skip like crazy either while streaming music or while on a call. 

Posted
13 hours ago, RedRumAT4 said:

Mine does the same thing. It's also been in the dealer for 3 weeks now after they blew out the master cylinder installing the Brembo Front Brake Upgrade. There seems to be a problem on GM's end with the programming. Anyway, I've been in 2 different rentals, a Buick Encore and GMC Acadia and both skip like crazy either while streaming music or while on a call. 

That’s real handy. I’ve tried even plugging the phone in and still can’t get it resolved. I just want to listen to music!

Posted

I have a 2019 Silverado and I use Apple Car Play quite a lot on long drives.  I have noticed that after about playing for 2-3 hours it will produce static that is corrected by unplugging the phone and re-plugging it in.  I have never figured it out.  I use the original apple cord and it has happened on both the USB and the USB-C ports, same phone and different phone.

 

  • Like 1
  • 2 weeks later...
Posted

Just picked up my 2021 AT4 and I have the same issue.  I am also having another issue with the infotainment system that apparently is fixed in TSB #20-NA-221 maybe it will address this issue along with the issue of the APPS application not working.

Posted
2 hours ago, Jeff Brandt said:

Just picked up my 2021 AT4 and I have the same issue.  I am also having another issue with the infotainment system that apparently is fixed in TSB #20-NA-221 maybe it will address this issue along with the issue of the APPS application not working.

What’s the other issue you’re having? The skipping is killing me. I dread bringing it to the dealer as I know it’s gonna be a headache. 

Posted

I am having the exact issue that is explained in TSB# 20-NA-2231, you can find it in this forum.  The problem with these new vehicles is there is some much technology I feel that mechanics just can't keep up or understand everything that goes on, and especially when everything is software managed.  This is by no means any disrespect for the mechanics out there, it is just that software developers sit in their own world, a perfect world, and when the software gets rolled out things change.  I just wish there was a way to contact the manufactures directly to share these issues with so that they can get the issues directly from the users.  Enough ranting I hope that this TSB fixes the current issue fo the apps not loading but I hope there is more in the fix that corrects this skipping issue as well.

  • Like 1
Posted

So on my 16 AT my android phone was flawless for years with Bluetooth,  switched to apple and BAM! Random Skipping/cutting out on Bluetooth and car play.  Just got a 21 RST, have done some of the car play and 0 issues

Posted

Just got mine updated with TSB #20-NA-221 and life is good.  Skipping is gone, apps are working.  GM Tech told me that there were a number of things this fixed, even some issue with touch screen calibration.

Posted (edited)

V153 which was prematurely announced but as of last night is still not available should fix this. The update above is just calibrations to fix the back end connection; V153 should be available shortly. 

Edited by GTPprix
  • Like 2
Posted

I was getting this in my 21 SLT. Then read on a forum that having an Apple Watch or some other sort of smart watch could be the cause. I disconnected the Bluetooth on my Garmin smart watch and it hasn’t happened again. So I’m guessing that it’s somehow related to the phone/bluetooth 

Posted

Just picked up a 21 Trailboss and wouldnt you know.. skipping after connecting phone.. Thx for the tread

  • Like 1
Posted
23 hours ago, edktm said:

Just picked up a 21 Trailboss and wouldnt you know.. skipping after connecting phone.. Thx for the tread

Hoping to find a sure fix on this at some point so I don’t have to goto the dealer 100 times.

Posted
On 1/26/2021 at 3:43 PM, GTPprix said:

V153 which was prematurely announced but as of last night is still not available should fix this. The update above is just calibrations to fix the back end connection; V153 should be available shortly. 

Is this something that Downloads somehow or does the dealer have to do it ?

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, 2,189 Guests (See full list)


  • Latest Articles

  • Posts

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

  • Popular Contributors

×
×
  • Create New...