Is internal audio recording not allowed by Android now?
Android has long provided apps the ability to record audio if users granted the required permissions. However, recent versions of Android have put new restrictions in place limiting apps’ access to microphone and internal audio recording capabilities. This was done in response to privacy concerns around apps potentially recording users without consent.
In Android 10, released in 2019, Google blocked apps from accessing the device’s microphone or recording internal audio by default. Users now have to explicitly grant permission through a runtime prompt for each app that wants to access the microphone. Additionally, recording internal audio from other apps is restricted to only a few authorized system apps.
Android’s Historical Audio Recording Permissions
In the past, Android apps were able to freely record audio as long as they requested the RECORD_AUDIO permission and the user granted access. The RECORD_AUDIO permission allowed apps to use the device’s microphone to record audio at any time without limitation.
Users could revoke the RECORD_AUDIO permission for individual apps through the system settings, but audio recording was enabled by default if the app requested the permission. There were no major restrictions on when or how long apps could record audio in the background if the user granted permission.
This meant that apps could potentially record private conversations without the user’s knowledge. However, developers had to justify why the app needed the permission, and users had to proactively grant the access for recording to occur.
New Restrictions Added in Android 10
Android 10 introduced major changes to the way background audio recording is handled, with the goal of protecting user privacy. The two most significant changes are:
Background recording without notification disallowed – Prior to Android 10, apps could record audio in the background without needing to display a notification. This allowed potentially malicious apps to secretly record users without their knowledge. Android 10 now requires a notification to be displayed while recording in the background, alerting the user that recording is taking place.
Recording threshold changed from 3 mins to 10 secs – In previous Android versions, an app could record up to 3 minutes of background audio before needing to prompt the user. This threshold has now been shortened significantly to just 10 seconds in Android 10. After 10 seconds, users must explicitly grant permission again for recording to continue.
As noted in the Android developer documentation, these changes provide “greater transparency and control over apps that want to access audio in the background.” Requiring prominent notification makes it impossible for apps to secretly record users.
Rationale for the Changes
Android 10 introduced new restrictions on apps’ ability to record audio from other apps and system sources. This was done primarily to improve user privacy and transparency around audio recording, as well as prevent potential abuse by malicious apps.
In previous versions of Android, apps could record audio from other apps and system sources without any restrictions. This meant an app could potentially record conversations and other audio without the user’s knowledge. The new restrictions in Android 10 aimed to curb this behavior and give users more control.
Now, in order for an app to record internal audio, it must declare the “RECORD_AUDIO” permission and be foreground and visible while recording. Alternatively, apps can use MediaProjection APIs which require user consent each time recording starts. These changes force apps to be upfront about recording and prevent secret background recording.
Additionally, apps are restricted from capturing audio from other apps and system sources like phone calls. Only apps designated as assistant or accessibility services can do this. This prevents malicious apps from spying on users.
Overall, these new restrictions empower users to control their privacy and prevent misuse of features that could facilitate illegal wiretapping or spying. Google wanted to curb exploitative behavior while providing developers the necessary tools for legitimate use cases under proper user consent.Source
Developer Reaction
Many app developers expressed concerns over the restricted audio recording permissions in Android 10, particularly regarding the impact on utility apps.
Certain apps like voice recorders, note taking apps, and accessibility apps require audio recording capabilities to function properly. The new limitations make it difficult for developers to include features that were previously commonplace, like automatically transcribing meetings or recording phone calls.[1]
Some developers argue that the changes reduce functionality without meaningfully improving privacy or security. They claim that bad actors could still find loopholes while benign apps lose capabilities. However, other developers acknowledge that increased scrutiny of sensitive permissions provides protections that users desire.[2]
User Response
Users have had mixed reactions to the new audio recording restrictions introduced in Android 10. On one hand, there is increased awareness around app permissions and privacy. Many users appreciate Android limiting background audio recording without consent (MediaRecorder overview | Android media). The new runtime permission dialog also makes users more conscious of which apps are accessing the microphone.
However, some users find the notification behavior when apps access the microphone to be confusing or frustrating. Since background audio recording is restricted, apps now display a persistent notification when recording audio in the foreground. Some users complain this notification clutter is disruptive. There is also uncertainty around why some apps require users to keep the app open during audio recording.
Workarounds for Developers
To comply with Android’s new audio recording restrictions while still enabling some call recording functionality, developers have come up with various workarounds like:
1. Adjusting recording duration and frequency: Rather than capturing full call recordings continuously like in the past, many call recorder apps now limit recordings to short snippets that are only captured intermittently (1). For example, a call may be recorded for 30 seconds every 5 minutes rather than the full duration.
2. Thoroughly informing users on permission needs: Developers should clearly communicate to users that additional permissions like accessibility services are required for call recording functions to work properly after Android 10. Transparency around permission requirements helps set proper user expectations (2).
Tips for Users
When it comes to managing app permissions on Android, there are a couple tips users should keep in mind:
First, pay close attention to permission requests when installing or updating apps. Android will notify you of the permissions an app is requesting access to. Consider whether you are comfortable granting that access before proceeding with the install. For example, think twice before allowing an app access to sensitive permissions like microphone or camera if it does not seem necessary for the app’s functionality (Change app permissions on your Android phone).
Second, periodically review and disable unused app permissions. Open your phone’s settings, go to Apps, select the app, and tap Permissions to see which permissions are enabled. Disable any permissions the app does not need. This helps protect your privacy and data.
The Future of Audio Recording on Android
Google will likely continue tweaking its approach to find the right balance between privacy, security, and functionality. More granular control over permissions seems inevitable, allowing users to approve microphone access only for specific apps and use cases instead of all-or-nothing.
As mentioned in this Android Developers article, future versions of Android may require declaring specific foreground service types that clearly describe the associated functionality. For audio recording apps, this could mean designating a “Voice Recorder” service type rather than the generic “foreground service” currently used.
Tighter permission controls and more transparency around how apps access the microphone may frustrate some developers. However, enhancing user trust and reassurance will likely drive increased engagement over the long term. The onus will be on developers to clearly communicate how and why their apps use the microphone, rather than taking audio access for granted.
Conclusion
In summary, Android 10 introduced tighter restrictions around apps’ ability to record audio in the background. This change was made to better protect user privacy and prevent abuse. Reactions have been mixed – while some developers have struggled to adjust, many users see benefit in Google limiting background recording without explicit consent.
As the Android platform continues to evolve, it’s clear Google wants to enable innovation while also ensuring control stays in users’ hands. The exact future standards around microphone access remain to be seen, but changes will likely balance both developer and user needs.
By restricting background audio recording, Android is forcing developers to be more transparent with users about how apps utilize the microphone. And users can feel more confident installing apps knowing Google is tightening privacy protections.