You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a Samsung Galaxy Tab A7 (SM-T505) running Android 12 (Patch Level September 1, 2022, Google Play system update July 1, 2022) with Samsung's One UI Core 4.1 that is NOT jailbroken, I've installed EasyNoise v0.10 (9/13/22), the latest available and recommended through F-Droid.
Every time I receive an incoming call, if EasyNoise is playing sound or running but paused, I get a crash notice from Android and have to launch the app again afterward. This happens while it is ringing, before it has been answered or dismissed. I assume it's receiving a signal to allow the app to pause playback the way most media apps do when you get an incoming call. A cursory glance shows there is code for handling the event but nothing jumps out at me as being the cause of a crash. I'm not well versed in the Android API and my java knowledge is about 20 years out of date so that's not saying much.
The text was updated successfully, but these errors were encountered:
On a Samsung Galaxy Tab A7 (SM-T505) running Android 12 (Patch Level September 1, 2022, Google Play system update July 1, 2022) with Samsung's One UI Core 4.1 that is NOT jailbroken, I've installed EasyNoise v0.10 (9/13/22), the latest available and recommended through F-Droid.
Every time I receive an incoming call, if EasyNoise is
playing sound orrunning but paused, I get a crash notice from Android and have to launch the app again afterward. This happens while it is ringing, before it has been answered or dismissed. I assume it's receiving a signal to allow the app to pause playback the way most media apps do when you get an incoming call. A cursory glance shows there is code for handling the event but nothing jumps out at me as being the cause of a crash. I'm not well versed in the Android API and my java knowledge is about 20 years out of date so that's not saying much.The text was updated successfully, but these errors were encountered: