Bluetooth connectivity 2018 GMC Terrain Headunit [369945538]

Assigned

Bug

Status Update

No update yet.

Description

rs...@gmail.com

created issue #1

Sep 27, 2024 03:39PM

I have two support cases
Case ID 0-5316000036780
Case ID 6-3540000037029

Vehicle - 2018 GMC Terrain Head Unit has most recent software update PS22.11 Sept 23, 2024 updated by dealership
this update did not solve the issue.

Since the purchase of two Pixel 8 Pros (my phone and my wife's phone) back in Oct of 2023 I have been plagued with a very specific BT pairing / connectivity issue. Since day one the phones have had BT connectivity issues with vehicle and prior to this I have had Pixel 6 Pro (running current version of Android 14 Sept Update) and a Pixel 5a connect successfully to the vehicle with full functionality.

These Pixel 8 Pro phones do not have any BT connectivity issues with our other devices, watches, ear bugs, other radios, including a 2018 GMC Sierra head unit.

I have patiently waited for several months doing update every month hope the issue will get resolved. I have the latest software update for Android 14 and still issue persists.

I have dealer ship telling me I need to get a different phone manufacturer and I have Google Support telling me that it is an issue with my car and I need to get a new car. Neither one of these are expectable.

it does not matter if the phones are plugged in via USB cable for Android Auto functionality or just normal paring, the BT connection never stabilizes. It just keeps doing an looping connecting, then disconnects, connecting, disconnects over and over.. Every once in a blue moon, I mean maybe 1 in a 100 connection attempts it will connect for about 10 sec and then disconnect and start the looping all over again.

Steps.
1. Factory reset phone
2. Factory reset head unit in car
3. Updated phone
4. Updated car
5. Used Dealership 2019 GMC Terrain (same head unit differ build on software V507 aug 2018) phones connect just fine
6. Put Pixel 8 Pro in Developer mode and tried the various BT setting All the different version of AVRCP and MAP nothing works
7. forgetting device, restarting phone after each setting option.
8. changed BT device name to something very short thinking maybe it was a name resolution issue..
9. turned on BT HCI snooping on both Pixel 6 Pro and Pixel 8 Pro done did fresh BT paring and connection attempts..
10. Pulled bug report out of both phones using ADB analyzed BT traffic using Wireshark can clearly see Pixel 8 Pro at a point in the provisioning process times out (cannot pinpoint on what the timeout is) it is some point around getting vendor dependences and then just connects and dissconnects

Finally broken down purchased a brand new out of the box Pixel 9 Pro XL EID 89033023553429009100037556223968 it is doing exactly the something.

here is all the supporting information attached

See attachedment

screen-20240911-171850.mp4 -

https://drive.google.com/open?id=11dRr0qnZFJbCyLi8bX96D3dg8hQeh7YB

Pixel3BTlogs.zip -

https://drive.google.com/open?id=1KYjtKx42tyZ9WlbKn1IlnCQk9Spa5TPf

Pixel6BTlogs.zip -

https://drive.google.com/open?id=1WPp5YUZdUJHWHQDqKdVAjOy6vDsTC0x6

Pixel8BTlogs.zip -

https://drive.google.com/open?id=16jCH3O48E0s6mqOMEYL5NWfUHcgMtUJz

Pixel82BTlogs.zip -

https://drive.google.com/open?id=1ASNBjF7On5zUQXUOzWAdPFvyk5DyW92N

Pixel6Pro_ws.pcapng

182 KB

Download

Pixel8Pro_ws.pcapng

261 KB

Download

Comments

rs...@gmail.com <rs...@gmail.com> #2Oct 7, 2024 05:03PM

Forgot to note the environment.
This crash occurs on only API 21.

rs...@gmail.com <rs...@gmail.com> #3Oct 16, 2024 01:25PM

This crash occurs on API 22 and 23 when the user doesn't have Google Play installed. Related discussions:

https://stackoverflow.com/q/41025200/842697

vi...@gmail.com <vi...@gmail.com> #4Nov 6, 2024 06:42PM

This crash doesn't reproduce on 1.1.0-rc0. Found that this commit in 1.1.0 with applyOverrideConfiguration

https://android.googlesource.com/platform/frameworks/support/+/26079d87c79a64829f036236353fac1dae4e0613%5E%21/#F2 causes crashes.

ta...@gmail.com <ta...@gmail.com> #5Dec 9, 2024 09:39PM

For me this still persisted in 1.1.0-rc01 as well as 1.1.0-alpha01.

Only downgrading all my androidx version to the previously working state helped.

From:

implementation 'androidx.appcompat:appcompat:1.1.0'
implementation 'androidx.cardview:cardview:1.0.0'
implementation 'com.google.android.material:material:1.1.0-alpha10'
implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
implementation 'androidx.recyclerview:recyclerview:1.1.0-beta04'
implementation 'androidx.viewpager2:viewpager2:1.0.0-beta04'
implementation 'androidx.legacy:legacy-support-v4:1.0.0'
implementation 'androidx.vectordrawable:vectordrawable:1.1.0'
implementation 'androidx.preference:preference:1.1.0'
implementation 'androidx.core:core:1.2.0-alpha04'

back to:

implementation 'androidx.appcompat:appcompat:1.1.0-rc01'
implementation 'androidx.cardview:cardview:1.0.0'
implementation 'com.google.android.material:material:1.1.0-alpha09'
implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
implementation 'androidx.recyclerview:recyclerview:1.1.0-beta03'
implementation 'androidx.viewpager2:viewpager2:1.0.0-beta03'
implementation 'androidx.legacy:legacy-support-v4:1.0.0'
implementation 'androidx.vectordrawable:vectordrawable:1.1.0-rc01'
implementation 'androidx.preference:preference:1.1.0-rc01'
implementation 'androidx.core:core:1.2.0-alpha03'

ta...@gmail.com <ta...@gmail.com> #6Dec 9, 2024 09:42PM

If you want to use 1.1.0 , override applyOverrideConfiguration in your activity as follows. However, this might need app restart for API 21 to 25, while switching Dark Theme to Light Theme and vice versa.

override fun applyOverrideConfiguration(overrideConfiguration: Configuration?) {
if (Build.VERSION.SDK_INT in 21..25 && (resources.configuration.uiMode == AppConstants.appContext.resources.configuration.uiMode)) {
return
}
super.applyOverrideConfiguration(overrideConfiguration)
}

rs...@gmail.com <rs...@gmail.com> #7Dec 28, 2024 05:56PM

Any update? Issue reproduces with androidx.appcompat:appcompat:1.1.0...

rs...@gmail.com <rs...@gmail.com> #8Feb 5, 2025 01:13AM

Thank you guys for letting me know workarounds, I really appreciate that.
But here is not stack overflow.
I just want the bug of appcompat to be fixed.

There is some reasons like below why I point that it's bug of appcompat.

- androidx.appcompat supports api 21
- As far as I know, apparently there are no api 21 emulator supporting play store.

I hope developer experience to improve as much as possible.

Thanks

rs...@gmail.com <rs...@gmail.com> #9Feb 5, 2025 01:14AM

I also encounter this issue on androidx.appcompat:appcompat:1.1.0 on lollipop

rs...@gmail.com <rs...@gmail.com> #10Mar 1, 2025 12:17AM

The workaround from

https://stackoverflow.com/a/49024931/2360984 works for me