Any way to release android microfone when mute

[EugeneGxUA]

Is there is any wayt to release micro of device when mute your self ?

Now if we want to release micro we need unpublishAudioTrack but this create history overflow at server side, when all users publish and unpublish tracks.

Maybe somehow we can setMicroEnabled(FALSE) and release device micro ?

Thanks

[vhimanshu07]

We are also trying it, we need to release microphone when we are in background, how can we do it?
Is there a way to do it?
Right now to release the microphone, we are using this -
val audioManager = activity.getSystemService(Context.AUDIO_SERVICE) as AudioManager audioManager.isMicrophoneMute = !unMute

But with this, when I do room.disconnect() and if I try to connect again, the app crashes. Getting this error -

java.lang.AssertionError: Expected condition to be true at livekit.org.webrtc.audio.WebRtcAudioRecord.assertTrue(WebRtcAudioRecord.java:739) at livekit.org.webrtc.audio.WebRtcAudioRecord.startRecordingImpl(WebRtcAudioRecord.java:582) at livekit.org.webrtc.audio.WebRtcAudioRecord.prewarmRecordingIfNeeded(WebRtcAudioRecord.java:535) at livekit.org.webrtc.audio.JavaAudioDeviceModule.prewarmRecording(JavaAudioDeviceModule.java:462) at io.livekit.android.audio.JavaAudioRecordPrewarmer.prewarm(AudioRecordPrewarmer.kt:47) at io.livekit.android.room.track.LocalAudioTrack.prewarm(LocalAudioTrack.kt:91) at io.livekit.android.room.participant.LocalParticipant.setTrackEnabled(LocalParticipant.kt:370) at io.livekit.android.room.participant.LocalParticipant.setTrackEnabled$default(LocalParticipant.kt:336) at io.livekit.android.room.participant.LocalParticipant.setMicrophoneEnabled(LocalParticipant.kt:307)

[adrian-niculescu]

There are two ways to do this today and neither is quite right.

1. Unpublish and republish the audio track. Releases the mic, but leaks native memory on the audio path: 50 mic toggles on a two-party call retained about 11.7 MB of native heap, roughly 0.23 MB per cycle, with no decay afterwards. The video path got a fix for the same shape of leak in #971, and audio has no counterpart to it. And as the original post says, publish/unpublish is not free on the server either.

2. Mute the publication. LocalTrackPublication.muted only sets mediaTrack.enabled = false. It never touches the ADM, so AudioRecord stays open and the OS microphone-in-use indicator stays lit. An indicator burning next to a muted mic reads as a bug at best and a privacy invasion at worst.

The web SDK handles this with stopMicTrackOnMute, which stops the underlying MediaStreamTrack so the browser releases the device. That has no direct port to Android, since capture is owned by the ADM shared across the PeerConnectionFactory rather than by the track. PeerConnection.setAudioRecording(false) is the equivalent lever: it stops the ADM and releases AudioRecord with no renegotiation and no change to the publication.

#987 adds that as LocalAudioTrackOptions.stopMicrophoneOnMute.

@vhimanshu07 AudioManager.isMicrophoneMute only zeroes the samples, it does not release the device. The assertion you hit is in the prewarm path that setMicrophoneEnabled drives on every toggle, which is the same churn option 1 causes.