{"id":13507,"date":"2022-02-15T15:19:07","date_gmt":"2022-02-15T15:19:07","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/15\/google-might-bring-fast-pair-to-more-manufacturers-in-android-13\/"},"modified":"2022-02-15T15:19:07","modified_gmt":"2022-02-15T15:19:07","slug":"google-might-bring-fast-pair-to-more-manufacturers-in-android-13","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/15\/google-might-bring-fast-pair-to-more-manufacturers-in-android-13\/","title":{"rendered":"Google might bring Fast Pair to more manufacturers in Android 13"},"content":{"rendered":"

<\/a>\n
<\/p>\n

\n

It looks like Google will expand the Fast Pair feature to more Android phones with the upcoming Android 13<\/a> update.<\/p>\n

Fast Pair, which Google introduced in 2017, makes it easier for Android users to connect Bluetooth devices by surfacing an Apple AirPods-like pop-up when Android detects a nearby supported Fast Pair device. Moreover, Fast Pair requires Bluetooth device makers to register products before they can start using the feature to prevent unauthorized use, and Fast Pair is built into Google\u2019s \u2018Google Mobile Services (GMS) suite.<\/p>\n

That means that Android devices that ship without GMS can\u2019t access Fast Pair in its current state. That likely won\u2019t impact most Canadians since the majority of phones sold in Canada have GMS.<\/p>\n

However, new code changes spotted in the Android Open Source Project (AOSP) Gerrit<\/a> \u2014 an online collaborative tool for working on and reviewing code \u2014 suggests Google will split Fast Pair from GMS in Android 13.<\/p>\n

Spotted by Esper<\/a> (via Android Police<\/em><\/a>), the code change would move Fast Pair into the \u2018Mainline\u2019 module. Specifically, Fast Pair would become part of the newly introduced \u2018NearbyManager\u2019 API \u2014 a change that\u2019s already part of the first Android 13 developer preview.<\/p>\n

Further, comments on the code change say that the plan is to let manufacturers set up their own server to \u201csync and serve certified Fast Pair devices\u2019 metadata\u201d and support Fast Pair by connecting already-paired Fast Pair devices to manufacturer accounts.<\/p>\n

As Android Police <\/em>points out, the change should tie in well with Google\u2019s plan to bring Fast Pair to Chromebooks, Windows, Android TVs, and other smart home devices<\/a>. However, it\u2019s also worth noting that Google hasn\u2019t officially announced the change. Android Police <\/em>also reports that Google doesn\u2019t appear to be using the Mainline module in the Android 13 developer preview, although it could arrive in future releases.<\/p>\n

Source: AOSP Gerrit<\/a> Via: Android Police<\/a>, Esper<\/a><\/p>\n<\/p><\/div>\n