Home > Pixel Series

Pixel 7 Pro Bluetooth name changing to random strings! [Fix]

In this guide, we will be discussing a workaround that might help you fix the issue of Bluetooth name changing automatically to random strings on Pixel 7/Pro. Ever since the thirteenth iteration of the OS was rolled out, there has been a slew of reports related to Bluetooth. As per the latest development, many users are unable to connect their Pixel to their car’s Bluetooth. While that issue is yet to be addressed, a new one has already made its way.

Pixel 7 Pro Bluetooth name changing

As of now, numerous users have voiced their concern that the Bluetooth name on their Pixel 7 Pro is changing automatically to a long random string of alphanumeric characters. If you are also in the same boat, then this guide will make you aware of a nifty workaround that should help you resolve this issue. So without further ado, let’s check it out.

Fix Pixel 7 Pro Bluetooth name changing to random strings

Pixel 7 Pro Bluetooth name changing

The culprit behind this issue might be a third-party app that is using the location access in the background, So we will have to disable all the apps from having access to the device’s location and enable them one at a time unit we are able to catch the culprit. Follow along.

  1. Head over to Settings > Security & Privacy > Privacy > Permission Manager.
  2. Then go to Location, select a third-party app from the list, and set Don’t Allow. Do so for all the other third-party apps. Pixel 7 Pro Bluetooth name changing
  3. Now re-enable their permission but one app at a time and then check out the results.
  4. Once the Bluetooth name changes, refer to the last app whose location you just enabled.
  5. That app is your culprit and you should keep its location access disabled, at least for now.

That’s it. These were the steps to fix the issue of Bluetooth name changing automatically to random strings on Pixel 7/Pro. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workaround is your best bet.


Share: