Unfortunately this bug remains. The code in question is below and essentially kills the call if PiP is not available:

talk-android/app/src/main/java/com/nextcloud/talk/activities/CallBaseActivity.java

Lines 121 to 130 in 49991d7

    
           if (isPipModePossible()) { 
        
               Rational pipRatio = new Rational(300, 500); 
        
               mPictureInPictureParamsBuilder.setAspectRatio(pipRatio); 
        
               enterPictureInPictureMode(mPictureInPictureParamsBuilder.build()); 
        
           } else { 
        
               // we don't support other solutions than PIP to have a call in the background. 
        
               // If PIP is not available the call is ended when user presses the home button. 
        
               Log.d(TAG, "Activity was finished because PIP is not available."); 
        
               finish(); 
        
           }

I've been investigation how to fix this, as it is the last remaining piece needed along with Issue #869 and #5467 to bring Talk to equivalence with other talk apps on Android.

In essence, a few things have to happen here:

Call lifecycle
- Prevent CallActivity from tearing down the ongoing call when it is backgrounded. Calls must continue without forcing a hangup, and the foreground notification should stay active.
- Ensure WebRTC renderers (self view and PiP) are only initialized once and are safely reused when the UI is restored.
- Avoid triggering onCreate when the user re-enters the call while it is already running. Resume the existing activity instance instead of launching a new one.
Bring existing call to the front
- Add a helper (e.g., CallActivity.show(...)) that first searches for an existing CallActivity and moves it to the front.
- Update all in-app entry points (ChatActivity, foreground service notification actions, incoming call notification taps, etc.) to use the helper so they reuse the running activity.
- Make sure notification actions continue to support the "Leave meeting" broadcast flow.
Call UI work and notification
- Guard CallActivity's teardown logic with a flag so lifecycle-driven onDestroy calls do not hang up active calls. Only dispose local streams during an explicit hangup.
- When returning from PiP, restore the existing renderers without reinitializing them or rejoining the room.
- Create notification to allow return to call

	if (isPipModePossible()) {
	Rational pipRatio = new Rational(300, 500);
	mPictureInPictureParamsBuilder.setAspectRatio(pipRatio);
	enterPictureInPictureMode(mPictureInPictureParamsBuilder.build());
	} else {
	// we don't support other solutions than PIP to have a call in the background.
	// If PIP is not available the call is ended when user presses the home button.
	Log.d(TAG, "Activity was finished because PIP is not available.");
	finish();
	}

Uh oh!

continue call when minimizing app and PIP is not available/enabled #1688

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions