Efenstor
Efenstor
@unfa Interesting idea, but as far as I know Noise Repellent in its current form won't help much here because it provides only broadband noise reduction, while what you suggest...
@FrnchFrgg Yeah, that should work. But the microphones should ideally be identical. Besides, some pure signal will still be heard by the second mike and it will be quite different...
@unfa I think smartphones and noise-cancelling headphones do it with hardware, thus with zero latency: they simply take the signal from the rear mic, invert its phase and mix it...
@unfa Well, I think there's no need for us to invent the wheel, dear fellow ))) Just read some patents: https://patents.google.com/?q=active+noise+cancellation
> To be honest though I would prefer to do a noise-repellent2 using dpf or juce and once I have a good framework going for spectral processing that would be...
> I have not seen a single one. And I've been looking. Me neither.
> I added _the minimum time between incoming calls (from the same number)_ in repeated check. Do not understand what you mean by > > > So if the protection...
Having exactly the same problem on Android 12.1 / Lineage 19.1. Recently upgraded the OS and now all unknown numbers are simply rejected. With this flaw the app cannot work...
I have checked the previous versions down to v1.11.4 and the problem is present there as well, so it has nothing to do with the burst protection.
If I set the repeated count to 1 then it allows incoming calls (but makes the function useless of course). May be that helps a bit to pinpoint the problem....