PR 2/3: Experimental Native Call - headless

[BillCarsonFr]

Content

This PR allows to accept incoming audio call without any UI (via the notifcation to accept then hangup).

In a nutshell, there is an ElementCallStack that needs to be created (it is done lazilly see getOrBuild and per account -for multi account-), this setups the wireing needed for the rust core to talk and listen to the matrix client. I exists when there is no call.

From the stack object, you can now access the ElementCallController, this is the thing that will actually start/join a call and maintain an active call.

The flow is the following:

• There is a push notification for a rtc.notification
• Goes to the IncomingCallActivity that forwards to the ElementCallEntryPoint
• The ElementCallEntryPoint reads the lab flag and forwards to the NativeCallEntryPoint
• The NativeCallEntryPoint use the ElementCallController to start the call

Motivation and context

Screenshots / GIFs

Tests

• Step 1
• Step 2
• Step ...

Tested devices

• Physical
• Emulator
• OS version(s):

Checklist

• I am aware of the etiquette.
• This PR was made with the help of AI:
  • Yes. In this case, please request a review by Copilot.
  • No.
• Changes have been tested on an Android device or Android emulator with API 24
• UI change has been tested on both light and dark themes
• Accessibility has been taken into account. See https://github.com/element-hq/element-x-android/blob/develop/CONTRIBUTING.md#accessibility
• Pull request is based on the develop branch
• Pull request title will be used in the release note, it clearly defines what will change for the user
• Pull request includes screenshots or videos if containing UI changes
• You've made a self review of your PR

[github-actions]

📱 Scan the QR code below to install the build (arm64 only) for this PR.

If you can't scan the QR code you can install the build via this link: https://i.diawi.com/etmhFT

[codecov]

Codecov Report

❌ Patch coverage is 31.40496% with 83 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.99%. Comparing base (c32d1d5) to head (5de162e).

Files with missing lines	Patch %	Lines
...features/callnative/impl/ElementCallControllers.kt	0.00%	49 Missing ⚠️
...res/callnative/impl/ElementXRoomContextProvider.kt	0.00%	20 Missing ⚠️
...roid/features/call/impl/ui/IncomingCallActivity.kt	0.00%	10 Missing ⚠️
...trix/impl/di/DefaultElementCallTransportFactory.kt	0.00%	4 Missing ⚠️

Additional details and impacted files

@@                            Coverage Diff                             @@
##           feature/valere/native_call_entry_point    #7745      +/-   ##
==========================================================================
- Coverage                                   81.05%   80.99%   -0.07%     
==========================================================================
  Files                                        2794     2798       +4     
  Lines                                       82690    82804     +114     
  Branches                                    11384    11398      +14     
==========================================================================
+ Hits                                        67027    67063      +36     
- Misses                                      11277    11355      +78     
  Partials                                     4386     4386              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[BillCarsonFr]

@jmartinesp I modified the PR and forced push it. Your previous comment is on code that has been removed.
I marking as ready to review.

There is a point about the dependency that I am not sure about, right now the native call component and the matrix-rust-rtc core publish as GitHub release asset. Is this is a blocker? Should I publish on maven?

Other than that I updated the PR description to say more about the content.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jmartinesp]

The code in the PR seems ok, and I tested the feature and it worked well overall.

There is a point about the dependency that I am not sure about, right now the native call component and the matrix-rust-rtc core publish as GitHub release asset. Is this is a blocker? Should I publish on maven?

I think this is ok, but ideally we'd publish the libraries to maven central in the future.

Other than that, a few things I noticed which I'm not sure if are part of the integration or the EC native project:

• When you are in a call for a DM and the other user hangs up, the call doesn't end for you AFAICT. I always have to hang up manually in the notification.
• Clicking on 'mute microphone' doesn't modify the notification, so it always displays 'mute microphone' (also, the text is cut-off).
• At least once, I started a call from EW, replied on EXA an although I could see the call happening on both devices, none received sound AFAICT. Muting and unmuting did nothing. I haven't found a way to reproduce this though, it seemed quite random.

[BillCarsonFr]

Other than that, a few things I noticed which I'm not sure if are part of the integration or the EC native project

I haven't tested that PR stand-alone a lot. Do you have these issue with the 3/3 top of the stack?

[jmartinesp]

I haven't tested that PR stand-alone a lot. Do you have these issue with the 3/3 top of the stack?

I haven't tested that one yet, but I can take a look.

[jmartinesp]

Yes, it still has both DM and mute microphone issues + a few new ones with PiP. I guess the PiP change triggered within the EC native UI is different than the one we trigger when leaving the screen in EXA?