Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call terminated onProximitySensorToggleScreen #163

Open
iddq opened this issue Sep 3, 2024 · 3 comments
Open

Call terminated onProximitySensorToggleScreen #163

iddq opened this issue Sep 3, 2024 · 3 comments

Comments

@iddq
Copy link

iddq commented Sep 3, 2024

Let me ask, why is the release necessary here, and could it cause any issues that might interrupt the program execution?

09-03 20:46:28.592 1269 1882 D SGM:PkgDataHelper: getGamePkgData(). d.d.meshenger 09-03 20:46:41.250 1269 3378 V AudioService.RecordingActivityMonitor: updateSoundAppPolicy packageName = d.d.meshenger 09-03 20:46:41.339 1269 3373 D PowerManagerService: [api] release WakeLock SCREEN_BRIGHT_WAKE_LOCK 'meshenger:tag' ACQUIRE_CAUSES_WAKEUP DISABLED (uid=10243 pid=1826 displayId=-1 lock=730a7a3)

@iddq
Copy link
Author

iddq commented Sep 3, 2024

Although it is becoming increasingly likely that the issue I am investigating is unrelated. The issue is as follows: the called device is in a locked state when the incoming call is automatically accepted. The call is then disconnected after a few seconds. If I had to guess, the problem is that the CallActivity cannot come to the foreground. I think the network and call handling should be managed from a Service, independently of any activity.

09-03 21:37:56.234 1269 3888 W NotificationService: Toast already killed. pkg=d.d.meshenger token=android.os.BinderProxy@d6f0d60

@mwarning
Copy link
Member

mwarning commented Sep 3, 2024

Hi, thank you for highlighting this. I will take a look over the weekend.

@iddq
Copy link
Author

iddq commented Sep 3, 2024

the error occurred even when the screen was on and finally disappeared only when the called application was restarted after a force stop. This makes it difficult to find out what causes the error. Certain events should be logged to find out why the call is dropped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants