telegram pauses whatever is playing the second you hold its mic button, and that turns out to not be a telegram feature at all, it's an android convention. telegram grabs a temporary audio focus lock the moment recording starts and returns it the moment you let go, and android turns lock taken into pause for whatever is playing and lock given back into resume. that's the entire trick, straight from the source.
so the plan was to send the identical request from my own app's hold to record button and get the same pause and resume behavior. tested the full cycle on the emulator and it worked, background audio stopped within milliseconds of the hold and came back after the release. but on the real phone nothing happened, youtube just kept playing, and the version check said the app was the old build.
the fix wasn't the code at all, it was the delivery. every build had been shipped under the same file name, so the phone kept installing an old cached copy instead of the new one, and the version field still read the old build label, which is the tell. new unique file name, new version stamp, and check the installed version before testing anything. the audio focus code was right all along, the artifact on the phone was the bug.
the lesson is boring and it applies everywhere. if a fix doesn't work, verify the thing the user actually runs, not the thing you built. one file name serving two builds is a trap you will step in again, and a version stamp is the only way to tell which copy is real.