[rohitsasi720]

On the web, a one-to-one Remote can make a call from its phone button. This brings calls to the app, and they work with the web in both directions: phone to browser, browser to phone, and phone to phone.

It needs the call endpoints on the signed API from dev-null-sh/dev-null.sh#1312.

What you can do

• A one-to-one thread you can write in gets a phone button next to its menu. It opens a call screen that rings them for 45 seconds.
• A call ringing for you opens the same screen with Accept and Decline, and buzzes unless their thread is muted. This works from the Log, Notifications, Remotes, your profile or any thread, while the app is open.
• Once connected, the screen shows the timer and the web's fp code, made from both ends' keys, with mute, speaker and Hang up. It says how a call ended ("Call ended.", "No answer.", "Missed call from @…", "Couldn't connect the call.") for 4 seconds, as the web does. Android's back button hangs up.
• Threads now log calls in the web's words ("you started a call", "missed call from @ada"). Before, these showed as a bare "* someone".

How it works

packages/calls is a new local NativePHP plugin around Google's WebRTC (io.getstream:stream-webrtc-android, stasel/WebRTC). It sets the call up exactly as the browser does (resources/js/lib/call.ts on the web):

• the microphone, an empty video slot, and a call data channel whose closing means the other end hung up
• the offer or answer sent only once candidate gathering is done
• relay-only when devnull says so

The PHP side of the call lives in Call. The fp code is worked out in PHP from both descriptions, and a test checks it against the web's own function.

Limits for now

• Audio only. A partner on the web can turn their camera on, but this end doesn't show it.
• Calls only ring while the app is open, and Android may cut the microphone if the app goes to the background mid-call.
• One-to-one only, since org calls aren't on the API yet.

Testing

• tests/Feature/Screens/CallTest.php passes: 22 tests, 202 assertions. The thread, inbox and composer tests pass too.
• In the full suite, LogTest › "shows the following log in tab chrome" fails on my machine. It stalls for 90 seconds and the clock moves on. It fails the same way without this change.
• Tried on a Pixel 9 (Android 16) against a local instance of the API branch, with Chrome on macOS:
  • phone to web and web to phone, with audio both ways and the same fp code on both ends
  • decline, ring-out and missed call, hang up from either end
  • mute and speaker
• iOS isn't built or tested. The Swift side is written, but I don't have Xcode on this machine.

Screenshots

Android only, because of the iOS limitation above. The call screen is new, so it has no before shots.

conversation

	Android light	Android dark
Before
After

call-ringing

	Android light	Android dark
After

Recordings of an incoming call sliding up: Android light, Android dark

call-connected

	Android light	Android dark
After

• No visible change