wp-plugin-hostgator domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home4/scienrds/scienceandnerds/wp-includes/functions.php on line 6114ol-scrapes domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home4/scienrds/scienceandnerds/wp-includes/functions.php on line 6114Source: https:\/\/www.theverge.com\/2022\/4\/21\/23036078\/google-android-call-recording-apps-accessibility-loopholes-play-store-rules<\/a> Google is changing its Play Store policy to clamp down on a workaround that call recording apps were using, potentially closing the final loophole that allowed these apps to exist (via NLL-Apps on Reddit<\/a>). On May 11th, a rule clarifying<\/a> that \u201cthe Accessibility API is not designed and cannot be requested for remote call audio recording\u201d will go into effect, making it so that apps won\u2019t be able to record audio from a call.<\/p>\n As XDA<\/em> points out<\/a>, Google has been playing whack-a-mole with call recording methods after it removed the official API with Android 6. In an email to The Verge<\/em>, Google spokesperson Dan Jackson said the reason for the change is that call recording was an inappropriate use of the accessibility API. \u201cOnly services that are designed to help people with disabilities access their device or otherwise overcome challenges stemming from their disabilities are eligible to declare that they are accessibility tools. It should be obvious when reading the Google Play Store description of an accessibility tool who those users are and how the app helps them meet the challenges they face,\u201d he said.<\/p>\n Here are the new guidelines:<\/p>\n The Accessibility API is not designed and cannot be requested for remote call audio recording. <\/p>\n The use of the Accessibility API must be documented in the Google Play listing.<\/p>\n Guidelines for IsAccessibilityTool<\/strong><\/p>\n Apps with a core functionality intended to directly support people with disabilities are eligible to use the IsAccessibilityTool to appropriately publicly designate themselves as an accessibility app.<\/p>\n Apps not eligible for IsAccessibilityTool may not use the flag and must meet prominent disclosure and consent requirements as outlined in the User Data policy<\/a> as the accessibility related functionality is not obvious to the user. Please refer to the AccessibilityService API<\/a> help center article for more information.<\/p>\n Apps must use more narrowly scoped APIs and permissions<\/a> in lieu of the Accessibility API when possible to achieve the desired functionality. <\/p>\n<\/blockquote>\n While it\u2019s understandable that Google wouldn\u2019t want apps using accessibility features outside their intended purpose, it seems unlikely that this crackdown will help preserve privacy given that Google\u2019s own phone app lets you natively record calls<\/a>. (Other default phone apps, like Samsung\u2019s<\/a>, will be allowed to keep their call recording functionality, too, as they\u2019re not using the accessibility API to get the call\u2019s audio.) <\/p>\n
\n
<\/br><\/code><\/p>\n\n