Call terminated onProximitySensorToggleScreen

[iddq]

https://github.com/meshenger-app/meshenger-android/blob/70258593af4b4e2f726cc5fa0e7cbc96626fdfd2/app/src/main/kotlin/d/d/meshenger/CallActivity.kt#L1050

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]

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]

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

[iddq]

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.

[iddq]

#160

[mwarning]

Should be fixed in 4.4.8