Search the Community
Showing results for tags 'google policy'.
Found 2 results
The AchieVer posted a topic in Mobile NewsNew Google Policy Means Trouble for Microsoft on Android A new policy implemented by Google for Android apps brings tighter controls for SMS and call logs, technically enforcing a new limitation of the use of services like digital assistants on the platform. According to Google itself, access for call logs and SMS should only be required when it’s absolutely necessary for the app’s core functionality, which Google defines as explained below: “Core functionality is defined as the main purpose of the app. It's the feature most prominently documented and promoted in the app’s description; no other feature is more central to the app’s functionality. If this feature isn't provided, the app is “broken” or rendered unusable (i.e., app is deprived of its primary functionality and will not perform as a user would expect).” These changes mean applications like Microsoft Launcher can now receive your permission to access calls and texts, but at the same time, to also enable Cortana to read this data.New update for Microsoft LauncherAs a result, Microsoft has recently updated Microsoft Launcher with a prompt that seeks your permission to update the device assistant, as you can no longer run Google Assistant and Cortana side by side without setting up these controls. “Due to a new policy from the Google Play Store, Microsoft Launcher needs to be set as your device assistant if you want to do things like let Cortana keep you updated on calls and texts in your feed. Once that’s done, you’ll be good for this update,” the notification reads. The message started appearing after the latest update for Microsoft Launcher, and unless you tap the option that reads “Set it up now,” it comes back occasionally to seek your permission. Obviously, Microsoft Launcher isn’t the only application that needs to comply with this new policy, so expect similar prompts from other apps on Android these days. Source
vissha posted a topic in Mobile NewsAndroid User Locked Out Of Google After Moving Cities Image Courtesy: Techworm An Android user has been locked out of his Google account apparently because he moved cities, according to a post on Reddit. The explanation offered by Google support staff was that since his address details differed, billing information with Google wasn't current and hence the user's purchases could look fraudulent. The user in question does not know for sure that this is the reason; during his interactions with Google support to find out why he had been locked out, he was told that When asked what he could do, he was initially directed by Google staff to a site where he had to scan his driver's licence and credit card and told that he would have to wait 24 hours to get his account unlocked. But after this time passed, he was told that the account would not be unlocked and Google would not tell him why. He was advised to abandon his old account and start a fresh one. However, this meant he could not use the credit card that he had used on the old account and would have to obtain a new one to continue using Google's services. All his previous purchases would not be transferred to the new account, he was told. An email he sent to Google support resulted in the following reply: Source