Caught the Camera Auto‑Launching via Intercept

Cal

Hi,
Disclaimer i am using ia for translation as the rules said.
Over the past few months I’ve had an issue that occurs occasionally and seems odd to me—could you comment on it?
I changed the default camera app on my phone to the interception service provided by the “App Manager” app from F-Droid.
Well, I’ve noticed that every now and then—about once every 1 to 3 weeks—the camera app opens by itself. At first I thought it was my mistake, but since it kept happening I finally opened the process with the interceptor and got the following message:

"URI intent:#Intent;actionandroid.media.action.STILL_IMAGE_CAMERA;launchFlags0x17000000;extendedLaunchFlags0x4;i.com.android.systemui.camera_launch_source%201;end

VERSION 1
ACTION android.media.action.STILL_IMAGE_CAMERA
FLAGS 0x17000000
EXTRA com.android.systemui.camera_launch_source 5 1

MATCHING ACTIVITIES 2
0 LABEL Camera
NAME app.grapheneos.camera.ui.activities.CameraLauncher
PACKAGE app.grapheneos.camera
1 LABEL Interceptador
NAME io.github.muntashirakon.AppManager.intercept.ActivityInterceptor
PACKAGE io.github.muntashirakon.AppManager

ACTIVITY RESULT 0"

I’ve tested it, and it isn’t triggered by double‑pressing the power button—the only gesture that is officially documented to launch this app- as far as I know.
What do you think, is this normal or should I be concerned?

Novalissoide

Cal default camera app

GrapheneOS have a selectable default camera app?
How did you shift from the stock to AM-interceptor?

Novalissoide

Cal
launch sources 201 and 51, seems like the things differing from a couple of normal launch cases.

A launch by right lockscreen shortcut gives

intent:#Intent;action=android.media.action.STILL_IMAGE_CAMERA_SECURE;launchFlags=0x17400000;extendedLaunchFlags=0x4;i.com.android.systemui.camera_launch_source=3;end

And a launch by double power from unlocked gives

intent:#Intent;action=android.media.action.STILL_IMAGE_CAMERA;launchFlags=0x17400000;extendedLaunchFlags=0x4;i.com.android.systemui.camera_launch_source=1;end

So, when is 201, or 51 the launch sources?

Cal

Cal I’ve tested it, and it isn’t triggered by double‑pressing the power button—the only gesture that is officially documented to launch this app- as far as I know

I would like to clarify that I didn’t mean to say it isn’t triggered; in fact, it is, but it’s not the same log I had when I didn’t do it intentionally.

Byku

CameraLauncher is an intent that can be called by other apps not only by double pressing the power button. The question is what is making that call on your device. Do you have any automation apps?

Cal

Byku

Not i know of

Cal

Novalissoide

I dont remember how i did it, sorry

Cal

Novalissoide

Hi, thanks for trying to reproduce this case.

First, I should clarify that I’m not very technical, so sorry if I can’t answer as thoroughly as I’d like.

My log consists of a single entry, which is the expanded information you get when after looking at what you’re seeing, tap the copy icon at the top‑right.

Therefore, launches 201 and 51 came from the same notification.

Seeing that the launch number varies depending on how you do it, I’m trying all possible options to see if any of them will give me 201 (or 51) again, but I can only get launch 1, even with the locked screen.

I’ll pay closer attention next time to see if I can provide more details, hoping i can clarify things further, since I suppose there isn’t much else that can be verified right now, right?

Thanks!

(Helped by a ia to traslation)

Novalissoide

Cal your communication is spotless! 🫡

I've got source '3' at most, but will look for some list where hopefully descriptions of these 'launch codes' is available.