\nWhat does this Phone Hub change do to make things more efficient?
\nThe big change that appears to be in the cards revolves around how Phone Hub works, to begin with. But not necessarily in the method used. As noted in the commit in the Chromium Gerrit, it allows the nearby connections client to request specific keep alive and timeout. Nearby Share will keep the default values. So that feature will still work as always, now that it\u2019s been added to Chrome OS officially.
\nThe change, summarily dubbed \u201c[PhoneHub] Set keep alive and timeout longer for battery life,\u201d does exactly what is implied. Namely, it lengthens the time between Phone Hub pings between the Chromebook and smartphone to make things more battery efficient. Specifically, it lengthens the ping from 5 seconds to 15 seconds. And it stops that polling at 60 seconds if there\u2019s been no response.
\nThat will make the phone connection more efficient on the battery side because it will stop the phone from having to maintain that connection as often. By lowering the timing to a third as often, it could, theoretically, by as much as three times, in fact. Although, it remains to be seen exactly how impactful a change this will be.
\nThis is a Chromebook change but it\u2019s coming to Android
\nNow, the change in question, oddly enough, doesn\u2019t appear to require a Chromebook update. Instead, it\u2019s thought to be arriving on the Android side of the equation. That doesn\u2019t necessarily mean it\u2019s coming soon. But it will be arriving, if reports are accurate, via a Google Play Services update. So, given how often that updates, it could arrive sooner than later.
\nThe post Chromebook Phone Hub Will Soon Be More Efficient For Your Phone appeared first on Android Headlines.
\n
![](\"https:\/\/plus.maciejpiasecki.info\/wp-content\/uploads\/2021\/07\/how-to-phone-hub-chromebook-DG-ah-2021.jpg\")
\nSource: ndroidheadlines.com <\/p>\n","protected":false},"excerpt":{"rendered":"