Let me ask you this: What happens if you compute the wrong size for that overlay? If you're making the overlay, even if you're not drawing on it, it may still be intercepting screen touches.

You pretended you know the "internal" but you actually know nothing. What you said is full of hostile guesses. I have told you again and again "if you disabled the button the app will not display it." If you enabled the button the app just asks Android to display the button, when you click the button Android will notify the app "the button is clicked", then the app start recording. It's super simple. Compute the wrong size? No, nothing need to compute.

You are not telling the truth. From your screenshots I saw you also revoked the Contacts permission, this is the reason why the app complains.

Interesting. I do not recall ever removing (or denying) that permission. And when running the app it doesn't present me with a request to enable the permission. Why does it even want access to contacts? To make the log pretty? Going into the manager and permitting contacts does seem to have removed the complaint pop-up.

boldbeast wrote:

The official API suggested by Android works great so far, no other user met the problem you said.

I'm sure the API is fine... It's not the API. But it may be how you're using it.

Samsung often uses advanced features in it's launcher and notification handler. The Note 8 uses features beyond what most devices do, including app-in-a-window, split/screen, special notification drop downs, etc. The phone app in particular has a setting allowing it to only appear as a small notification area drop window if you're in another app. I suspect that's playing a role here. If the phone app is in a special mode, it's window size is likely a number that's smaller than device size (or maybe even negative, given Samsung has done that in the past). I believe the math you do to figure out overlay offset and size may be messing up in those edge cases.

boldbeast wrote:

Further more, if you disabled the button the app will not display it. It's impossible to make the problem.

The complaint I have is that the screen does not register taps when the call is on-going, and Boldbeast is installed and recording. The same API that lets you draw on the screen also allows you to intercept screen taps in the same overlay area. This is how you can detect screen hits when you're not in the foreground, to know when your "button" has been tapped, or held for moving.

Let me ask you this: What happens if you compute the wrong size for that overlay? If you're making the overlay, even if you're not drawing on it, it may still be intercepting screen touches. It may be passing touches to the phone app, which works fine for most devices. What happens if the phone app isn't in the foreground at the time? Are you even checking for that, or are you assuming it is? It's not a huge leap of logic I'm making here that an errant overdraw/overlay could be causing a touch lockup.

ANYWAY

I have a work around. I really don't care if you fix your buggy app. Sorry I even bothered to come here, make an account, and alert you to the fact you have an issue. (Won't make that mistake again...) Had I not already purchased it, I would have simply gone and found another app on the store, or written my own. Other Note 8 users will likely hit this, then uninstall and pick another app, or they already have (which may be why you're not getting reports of it).

I'm done wasting my time trying to help you improve your product. You think it's not your app... fine. Think that. If you're wrong, the only person hurt is you, when you start seeing a flood of complaints or a sharp drop in people buying your app as windowed apps become more prevalent.

Good luck. With customer support like this, you're going to need it.

]]>Wed, 16 Jan 2019 21:28:58 +0000https://www.boldbeast.com/forum/post7016.html#p7016https://www.boldbeast.com/forum/post7011.html#p7011
1. The only changes I've made was to the single permission for Boldbeast to disallow drawing on the phone app.=> You are not telling the truth. From your screenshots I saw you also revoked the Contacts permission, this is the reason why the app complains.

2. The app is not able to make the problem you said. Why? Because- The app only uses standard Android API to display the button, nothing special. The official API suggested by Android works great so far, no other user met the problem you said.- Further more, if you disabled the button the app will not display it. It's impossible to make the problem.

If you disabled the in-call button and disabled the "draw over other apps" permission, the app doesn't complain. Please check again. If it complains you must disabled other permissions.

I can assure you, I've changed no other permissions. And I've disabled the in-call button. I've taken screen shots, but you seem to have no way to upload them. You also appear to block any URL using the commercial domain (.còm), making linking hard. Is there another area one needs to disable this in?

No, the app doesn't do so. If you disabled the in-call button the app will no longer display it, so there is no need to do things you described.

And yet, it is in fact doing it. I've taken over 50 calls with this one permission changed, and haven't had a single screen lock issue. No other software has been updated (I prevent auto-updates). The only changes I've made was to the single permission for Boldbeast to disallow drawing on the phone app.

That you're being this stubborn, when there's clearly an issue here, speaks volumes as to why you have the reputation you do. Just wish I'd read the reviews a little closer before buying...

]]>Mon, 14 Jan 2019 19:11:36 +0000https://www.boldbeast.com/forum/post7008.html#p7008https://www.boldbeast.com/forum/post7004.html#p7004
1. Cannot get necessary permissions to work correctlyIf you disabled the in-call button and disabled the "draw over other apps" permission, the app doesn't complain. Please check again. If it complains you must disabled other permissions.

2. Even when the button setting is off in your app, you're still calling in to measure the app size, computing the overlay box=> No, the app doesn't do so. If you disabled the in-call button the app will no longer display it, so there is no need to do things you described.

]]>Sat, 12 Jan 2019 22:08:07 +0000https://www.boldbeast.com/forum/post7004.html#p7004https://www.boldbeast.com/forum/post7001.html#p7001
FYI, there is one more bit of info: The recording works fine with this setting off, but after (nearly?) every call now, the Boldbeast notification icon turns red, noting: "Cannot get necessary permissions to work correctly. Please check built-in settings, do not revoke permissions needed by the app."

But the only permission I've removed was the "draw over other apps" permission noted earlier. And I have the manual record button turned off in the app settings. So what's it trying to use that permission for, to discover it can't use it?

Here's my bet:

Even when the button setting is off in your app, you're still calling in to measure the app size, computing the overlay box, and making your headview. Normally this is harmless. In this cases though (where "Show call in pop-up" is enabled), the measure you're getting is either 0 or negative. (See question 20586525 on stackoverflow, you've disable URLs or I would link it.) Then your math to compute the overlay size/location causes your overlay size to be bogus, and the overlay takes the whole screen (or way more), including the notification bar area. Likely the button being drawn is drawn off screen.

I didn't test this out, but does hitting anywhere in the square of the overlay for the button cause toggle? Is so, I bet if I re-enable the button and app permissions and get into a lockup situation again, each screen tap would cause the recording status to toggle. I should be able to see that via the notification icon changing, even if the button is being drawn off the screen edge.

]]>Fri, 11 Jan 2019 17:16:56 +0000https://www.boldbeast.com/forum/post7001.html#p7001https://www.boldbeast.com/forum/post6998.html#p6998
I know there are many Note 8 users using this app.Can anyone else confirm this problem said by woody14619?]]>Thu, 10 Jan 2019 02:43:01 +0000https://www.boldbeast.com/forum/post6998.html#p6998https://www.boldbeast.com/forum/post6996.html#p6996
Resetting to factory isn't an viable option. It baffles me how every page on how to fix a phone issue has step three as "try reset to factory". As if it doesn't take hours of work to backup, reset, re-install apps, and bring a device back to a functional level.

I can tell you without a doubt that this problem IS being caused by Boldbeast. In fact, I can tell you that it's linked to exactly the feature I asked for a toggle on. Curious how? A few hours after my top post I was talking to a friend and was reminded that one can retroactively remove permissions in Oreo. I disabled just this permission and have yet to have a call lock up! I even re-enabled the partial pop-up options this afternoon, again, no calls locked up. I re-enabled the permission and made a test call; instant lock-up. Disabled again and it works fine. All while the setting to show the button overlay is off. Pretty solid proof to me that this is an issue with your app.

Take this as you will; I'm no longer asking. I'm telling you that your app provably causes a problem on recently updated Note 8 devices. What you do with that info is your prerogative at this point.

I will say that this whole experience has put me off though. Given the attitude, I'll be avoiding anything else you develop, and won't be suggesting this app to others. In fact, I may look for alternatives, since I'd rather not have to deal with "support" of this type long term, despite already having purchased the pro version.

You said even if you disable the in-call button the problem is still there. The fact is if you disable the button the app will stop displaying it, so the problem is completely not related to Boldbeast.

It's obvious another app in your phone made the problem. Please check other apps. If you don't know what's that app, I suggest you reset the phone to factory settings to remove all apps, then reinstall Boldbeast, the problem will surely disappear at once.

]]>Tue, 08 Jan 2019 16:52:04 +0000https://www.boldbeast.com/forum/post6991.html#p6991https://www.boldbeast.com/forum/post6989.html#p6989
While using my Note 8 during calls I sometimes find that the screen becomes unresponsive if Bolbbeast is installed. I removed it for a short time and had no lockups, but really prefer to have it installed and on, since I like having my calls recorded for later reference.

Note that only the touch screen becomes unresponsive. Hardware buttons work fine, and the screen properly displays, changes orientation, etc. Shortcuts for snapping screen captures, shake-toggling the flashlight, taking pictures from off mode, all work. But the touch screen is unresponsive from the point the call is answered to upwards of 30 seconds after the other side has hung up. (The Note 8 phone app also has an option to force call hangup using the power button, which I've enabled short term to get around not being able to end a call due to this issue.)

I suspect this may have to do with the overlay used to make the manual record button appear in the app. It mainly seems to happen when the phone app is either in the background, or has started as a partial drop-down app (something likely unique to the Note series). I've disabled both of those features for now, and have seen a much reduced occurrence of the problem, but it still happens at times, usually on longer calls.

Would it be possible to add an option to completely disable the overlay code? (eg. Prevent the code for making the overlay from ever being called?)

I've tried turning the manual button off (so no button is visible), but I suspect that the app is still trying to create the overlay when a call is active even if the manual button is not being displayed. I use the auto-record function (registered) to record all calls, so I have no need of a touch button to toggle record states.

Before suggesting other resolutions, note that I've already tried most other things from this site and others. I've checked that it's not the proximity sensor, nor does it appear to be any other app causing it, since removing Boldbeast fixed the problem. I've tried uninstalling and re-installing Boldbeast, cleared the system cache, and app caches for all instances of Boldbeast, the phone app, and the contact app. The only time I've seen it never have this bug is when Boldebeast is uninstalled, which I'd really rather not do.

This started happening shortly after the last Oreo update. It took me some time to trace down exactly what was happening.