and targeted SDK version 33 used to allow user to continue talking (via audio) when the phone is turned off (i.e., screen locked, via power button).
However, retargeting the same to SDK version 34 (as demanded by Google PlayStore policy), when the phone is turned off (screen locked), audio from the Jitsi App is no longer heard by the remote counterpart (i.e., as if it is muted). When the phone is turned back on (i.e., screen unlocked), it is audible again.
Meanwhile, audio from the remote counterpart can always be heard before and after phone is turn off (screen lock).
Expected behaviour: the Jitsi App continue to allow two-way audio talks between phone and remote participants even when the Android phone is screen locked after targeting to :
Jitsi Android App compiled using
implementation ('org.jitsi.react:jitsi-meet-sdk:9.2.2') { transitive = true }
and targeted SDK version 33 used to allow user to continue talking (via audio) when the phone is turned off (i.e., screen locked, via power button).
However, retargeting the same to SDK version 34 (as demanded by Google PlayStore policy), when the phone is turned off (screen locked), audio from the Jitsi App is no longer heard by the remote counterpart (i.e., as if it is muted). When the phone is turned back on (i.e., screen unlocked), it is audible again.
Meanwhile, audio from the remote counterpart can always be heard before and after phone is turn off (screen lock).
Expected behaviour: the Jitsi App continue to allow two-way audio talks between phone and remote participants even when the Android phone is screen locked after targeting to :