leo Orphee

I didn't do any particular setup - just installed it on my owner profile (with Google Play Services) and I see the Multipoint option from within the Pixel Buds app.

I first tried to install it into my Work profile via Shelter, but the app refused to open. I suppose it has to be installed in the main/owner profile.

    Orphee

    That's strange. Here is a screenshot of the landing page that shows the Multipoint menu within the Pixel Buds app:

    link

    Here's the screenshot of the me within the Multipoint menu:

    link

    Here's the App details for the Pixel Buds app:

    link

    I'm using the Pixel 8 (Japanese model), with GOS build number 2024040900.

    11 days later

    So for some reason, I tried to play a bit with permissions...

    And while running :
    System > Application > Sandboxed Google Play > Google Settings > devices and share > devices

    I can see my Pixel buds pro ready to pair.
    But when I try, it fails and request a manual pair from bluetooth menu (wich works, but with limited functions)

    Looking at logs from gms app :
    I catched this :
    https://i.imgur.com/51ZCTs5.png

    FastPair fails because of missing permission android.permission.BLUETOOTH_PRIVILEGED

    Looking in package settings :

    shiba:/ $ dumpsys package com.google.android.gms | grep permission |grep -i bluetooth                                                                                                                       
          android.permission.BLUETOOTH_CONNECT
          android.permission.BLUETOOTH
          android.permission.BLUETOOTH_ADMIN
          android.permission.BLUETOOTH_PRIVILEGED
          android.permission.BLUETOOTH_ADVERTISE
          android.permission.BLUETOOTH_SCAN
          android.permission.BLUETOOTH: granted=true
          android.permission.BLUETOOTH_ADMIN: granted=true
          android.permission.BLUETOOTH_PRIVILEGED: granted=false
          android.permission.BLUETOOTH: granted=true
          android.permission.BLUETOOTH_ADMIN: granted=true
          android.permission.BLUETOOTH_PRIVILEGED: granted=false
            android.permission.BLUETOOTH_CONNECT: granted=false, flags=[ USER_SET|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]
            android.permission.BLUETOOTH_ADVERTISE: granted=false, flags=[ USER_SET|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]
            android.permission.BLUETOOTH_SCAN: granted=false, flags=[ USER_SET|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]

    and this permission can't be enabled from adb

    shiba:/ $ pm grant com.google.android.gms android.permission.BLUETOOTH_PRIVILEGED                                                                                                                           
    
    Exception occurred while executing 'grant':
    java.lang.SecurityException: Permission android.permission.BLUETOOTH_PRIVILEGED requested by com.google.android.gms is not a changeable permission type
            at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermissionInternal(PermissionManagerServiceImpl.java:1402)
            at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermission(PermissionManagerServiceImpl.java:1321)
            at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:583)
            at android.permission.PermissionManager.grantRuntimePermission(PermissionManager.java:634)
            at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2899)
            at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:313)
            at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
            at android.os.ShellCommand.exec(ShellCommand.java:38)
            at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6459)
            at android.os.Binder.shellCommand(Binder.java:1238)
            at android.os.Binder.onTransact(Binder.java:1051)
            at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4742)
            at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6443)
            at android.os.Binder.execTransactInternal(Binder.java:1530)
            at android.os.Binder.execTransact(Binder.java:1464)

    Is there anything I miss ?

    How can we give BLUETOOTH_PRIVILEGED permission to Play Service App ?

    Thanks

      Orphee That's a privileged permission. Sandboxed Google Play's approach is treating the Play Services apps as regular sandboxed apps. Making them privileged and giving them privileged permissions would be against that approach, so I don't think there's a way to do this.

      @matchboxbananasynergy I don't understand how @Vagabond8630 made it work...

      As long as I configure bluetooth with "standard" pairing approach, I don't have Multipoint option, and I can't see Pixel buds Pro pictures in the app... I have blank icons...

        9 days later

        Orphee I have one possible explanation of why it's working for me but not for you, but no idea if it's correct.

        Before I installed GOS, I had a brief 1-month period when I was on stock and I had first set up my Pixel buds on stock OS. After I switched to GOS, I then re-set up the buds on GOS (for the first time from GOS's POV, but for the second time from the Bud's POV) through the Pixel Buds app. Then everything worked without me doing any special settings adjustments on GOS or the Pixel Buds app.

        This is pure conjecture, but maybe there is some sort of software locking mechanism of the multi-point feature that only works on Buds that have an internal settings flag that gets enabled after initial setup on stock OS.

        12 days later

        Was anyone able to solve this? I'm having the opposite problem. Multi point is stuck on and i hate it. It's a trasb feature that doesn't work but i can't find anyway to turn it off.

        My buds were originally setup on a stock oneplus 7 pro, the feature was visible in the pixel buds app on there, but isn't on mu pixel 7a with graphene.

          GrouchyGrape i haven't tried but i believe multi point is on by default. Think the only way will be to connect to the old phone

          Steadying5496

          Interesting, due to your comment, I revisited the Pixel Buds app and found out that the Multipoint menu that was previously available was no longer available. The only explanation I can give is that I had recently changed my Google account on GOS from my personal account to an anonymous account that I had created to download apps from the Play Store without tying my GOS device to my personal account.

          After this, I noticed several changes:

          • The buds don't connect to my GOS phone automatically as it did before
          • The Multipoint menu is no longer available
          • The three icons at the top showing left/right earbuds and the case show a blank circle instead of a picture of the earbuds/case

          It seems that to fully use all functions of the buds, the following conditions all need to be met:

          1. First set up the buds with a Google account on stock
          2. On GOS, sign in to the same Google account used to set up the buds on stock
          3. Keep GOS signed in to the same Google account

          I reset my Pixel Buds Pro to factory settings following the official instructions, and further found that I was no longer able to pair the buds to my phone from the Pixel Buds screen & notifications, and I had to activate pairing mode, then add it in the Bluetooth menu of the phone settings. I'm quite certain this was possible when I had signed in to my personal Google account on GOS when pairing with my buds that had been first set up on stock.

          Of note, when previously setting it up on GOS, the {NAME}'s Pixel Buds Pro name I had given the buds while on stock was remembered, but now it gets set up as simply Pixel Buds Pro.

          The blank icons are a bit of an eyesore when on the Pixel Buds app, but the battery percentages seem to update fine, and besides the multipoint function not working anymore, the buds seem to function fine.

          In conclusion,

          i can't find anyway to turn it off.

          Factory reset the buds following the instructions linked above, and re-link it with the BT settings. That should remove the Multipoint setting from the app, and I assume it would also disable the setting toggle itself.

            6 days later

            Vagabond8630 Factory reset the buds following the instructions linked above, and re-link it with the BT settings. That should remove the Multipoint setting from the app, and I assume it would also disable the setting toggle itsel

            I didn't get around to trying this but I don't believe it will work as I'm pretty sure multi-point is on by default.

            I managed to turn it off by pairing the buds to my work Samsung device running stock. This did have the settings for multi-point and auto switch, both of which I've now turned off.

            I'm now having the wonderful issue of the buds only want to connect to a device that's been told not to automatically connect. Phone in range and ready available to connect? Let's show a prompt on the laptop instead. In the middle of a call on your phone? No worries buddy we're just gonna disconnect and try and connect to the laptop real quick.

            Anyway rant about bluetooth aside, I've resolved the issue but it's only brought on further bugs.

            I really hope we see either major improvements or an outright replacement to bluetooth in coming years.