Jump to content

Recommended Posts

Posted

Hello. Just yesterday I bought a 2023 Silverado 1500. I paired my iPhone to it and saved some Sirius and FM radio stations. But every time I shut the truck off and open the door, the settings are gone and I must re-sync my phone. I thought something was up because it happened at the dealership with the phone sync but I didn’t realize it would happen every time. 
 

I found a YouTube video on making sure the truck isn’t in transport mode. I don’t think it was but I went through the process to be sure. This didn’t fix the issue.  Can anyone tell me what I must do to get the infotainment system to remember my phone and settings?  Thank you.

Posted

I took delivery yesterday of a 2023 Denali Ultimate 1500 and am having the same issues.  Anyone?

Posted

Tailwind- I reset the infotainment system and went through the various screens. I didn’t really understand everything I was answering but after the process I synced my phone and set some radio stations up. Shut off the truck and opened the door. When I started again the radio was on the station I had left it and at the same volume. And my phone synced up by itself.

 

To start the reset, press down the phone hangup button on the steering wheel for ten seconds. See if this helps you.

Posted

Hummm, that's weird......I'd drive back to the dealer and let them fix it. 

 

I have a 2023 High Country and it works fine......sure are a lot of settings to F-with, but it's nice to have it customizable. 

Only wish I could change manual turn signal to 5-flashes instead of 3, which is not available except when towing. 

 

Good luck getting this fixed on your truck....

Posted

Thanks Mick. I was able to resolve this by resetting the infotainment system and starting over. Everything seems fine now.

  • Like 1
Posted

If anyone is having issues with the guest profile and saving phone pairings and settings you need to go into settings and select reset and select enter safe mode.  It will clear the guest profile and allow you to log in with your my GMC account.  Solved my issue.

  • Like 1
Posted (edited)

Not sure if it's the same for the refresh trucks...

https://gm-techlink.com/?p=15391

Resetting a Mobile Device for Connectivity Issues

September 30, 2021

Concerns about mobile device connections – Apple and Android –on a vehicle equipped with an Infotainment 3 system (RPO IOR, IOS, IOT, IOU, IOV) can be difficult to reproduce and diagnose due to a number of varying factors with the device, ranging from recently released updates to the operating system to the use of different versions of popular apps. (Fig. 6)

 

F06-Radio-Apple-CarPlay.jpgFig. 6

 

However, in some instances, device connectivity issues may be resolved by rebooting the device. Performing the reboot procedure may help avoid spending additional time diagnosing a device that doesn’t always connect with the vehicle.

Mobile devices require being rebooted– powered off and then on again, especially after software updates – on a regular basis. When a device is not rebooted often, it could lead to device connectivity issues with the infotainment system, such as concerns with access to phone contacts, phone connections, wireless and wired projection for Apple CarPlay or Android Auto, and other issues.

TIP: Android phones can be set to “Auto Restart” at a set schedule by going to the phone’s Settings menu. Look for the Reset option. Many customers may not know about this feature on their phone. Apple phones do not offer an “Auto Restart” feature.

It’s recommended that a phone should be rebooted after every operating system (OS) update. Depending on the phone, the reboot may or may not occur automatically.

 

Resetting the Device and the Infotainment System

If the customer concern cannot be reproduced, attempt to reset the device as well as the infotainment system:

  1. Unpair or delete the device by removing the device from all infotainment system connections (Bluetooth, Wi-Fi and projection). Also remove or “forget” the vehicle from all settings on the device.
  2. Restart the device.
  3. Cycle off the vehicle ignition long enough for the radio sleep cycle to occur.
  4. Reset the radio by selecting Erase Infotainment Data under the Settings > System tab. The Erase Infotainment Data option is under the Reset Options menu. (Fig. 7)
  5. Pair and connect the device to the vehicle again.

 

F07-Radio-reset-R.jpgFig. 7

 

The infotainment system should not be reset on a regular basis if device connection issues occur. The system should only be reset once for a condition. If the same or similar conditions appear in the vehicle, additional diagnosis should be performed unless there is a proven device issue.

 

Factory Reset a Device

In some extremely rare cases, it may be necessary to ask customers to perform a “factory reset” to their device.

For example, if a condition only occurs with one specific device, where similar devices don’t exhibit the condition, it may be that the condition follows the affected device to identical vehicles, which will require resetting the customer’s device. A factory reset should only be done after the customer has performed all necessary backups of all of data on the device.

Once a factory reset is performed, data should not be immediately restored because an app or contact on the backup data may be the source of the customer’s concern. Restore data by systematically/logically reinstalling contacts, apps, and other data (photos and media, etc.) to see if the concern returns. This process will help identify the app or data that is causing the issue.

 

Edited by redwngr
  • Like 1

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