false flagging of WhosCall on Android has come back = see original case xxxxxx

Aspirant

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx

My impression is that there is no way to be sure if the 'false-detect' goes away.

 

If 24 hours pass with no detections and then a detection occurrs, I assume it had gone away for a while.

 

If 10 minutes pass and then a detection occurrs, I assume it had NOT gone away.

 

But I don't know exactly where to draw the line between 10 minutes and 24 hours.

Superuser

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx

With my experience - I usually "run" F-Secure Scan (by F-Secure SAFE UI) as kind of "check" - if there any detections for files or not (since - also with my experience - Whoscall was detected by manual scan; maybe additionally to real-time potential detections);

 

So - if detection did not comes with one of scan-runs (but than comes back after some minutes) - there is something wrong with scanning-design;

Because.. I think that usually there should not be situations when "detections added/dropped/added/dropped" with small timeframe between changes.. too much often;


Later added: with my experience there dropped detection for Whoscall (on current time), which was there some days before. still not sure - if situation will be repeated later.

Aspirant

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx

The problem has been back for WEEKS now. The 'problem detected' has become an almost PERMANENT display.

 

The really irritating thing is that I am given exactly ONE option: let f-secure delete my whoscall app.

 

I have 15 f-secure SAFE licenses and, if this doesn't get fixed soon, I will switch to another A-V product.

 

I've invested a LOT of time and money into f-secure along with my work as a beta tester.

 

This is just absurd!

Superuser

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx

Hello,

 

Sorry for my reply. I also decided to re-check with my device and indeed F-Secure do detect PUA-items with latest (?!) WhosCall (and generic-detection name as previously).

 

You should not to do this .... but did you transfer such information to F-Secure SAS and then there is stuck for weeks?!

I able to feel that 'detection' comes more about 'advertisement-module' (StartApp) than about WhosCall (even it about 'one'-view). And this is indeed can be 'potentially unwanted'. But I still not sure about handling such "PUA" with Android-platform. Because it can be more 'friendly' to ignore such notification (or re-rate/exclude) certain application.

 

Thanks!

Aspirant

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx

On my phone, at least, there is NO option to 'exclude.' The ONLY choice I get is to 'remove all.'

 

I did another 'remove and reinstall' yesterday and, for the first time noticed that, F-Secure SAFE Andorid, has added a 'call block' feature.

 

Is it possible that the F-Secure company has decided they want to pressure users to delete any other call-blockers?

 

That might possibly be illegal behavior. For sure it would be unethical.

 

I wonder if the Technology section of the New York Times might be interested in looking at this and, maybe even, asking some public questions about this!

 

NOTE: I prefer to keep using WhosCall because it provides a shared database of known SPAM callers which is far more effective than me having to create my own personal list for everything. Individual users can automatically contribut to that database.

 

But, then, SPAM calling is legal in Taiwan; partly because the recipient doesn't pay anything for inbound calls.

 

Why Americans have been persuaded to pay for inbound calls is another question entirely.

Superuser

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx

Yes,

 

Sorry for my worst explanation. I also do mean that "there is NO visible option to exclude or ignore detected PUA-item" (and this is "not friendly"). ?! but maybe required clarification from official F-Secure Teams about designed steps when PUA-item can be ignored/excluded (if not possible to use F-Secure SAS or required to do it too often).

 

About another part:

 

--> F-Secure SAFE for Android already long time with "Call blocker" module/feature. At least... years (?!).

And this feature does not cover some of specific situations. So another 'specific' applications time to time can be reasonable under device.

As my own feelings - can not be any meanings as 'pressure' (or actions against any other call-blockers) by cyber security/privacy F-Secure company . This is maybe common things for US-based (or some other locations) companies, but with my own opinion -> Finland-based (officially) companies do not use such things (usually). They do able to promote their 'technologies' with much more good way (if required).

 

--> And... F-Secure do mark WhosCall by generic PUA-detection based on their ADs-module (?!). Startapp (as noted/discussed under this topic);

MAYBE possible to re-check/re-rate such module.. if F-Secure wrongly mark it as PUA;

They created certain 'policy' for PUA-detections:

https://www.f-secure.com/en/web/labs_global/potentially-unwanted-applications

 

If such policy do not cover (or not possible to apply) StartApp.... so F-Secure able to remove such detection at all (since break their policy); I able to think that not only "WhosCall" do use StartApp-module and generic detection for StartApp-advertisement-module can be for another Android applications too.

 

Potential fix-steps:

- re-rate it (by transfer information to F-Secure Labs; or when found it by their own steps).

But... with "WhosCall" required to do it with ?! each update (fresh build for WhosCall);

 

- re-classify it.

 

- 'visible' option to ignore/exclude certain PUA-iteam.

 

Thanks!

Community Manager

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx

Hi Joschka2,

 

I have now escalated this post to our labs so that they can have a look at your issue in detail. One of our lab analysts will get in touch with you via email for further communication.

Has somebody helped you? Say thanks by giving likes. Has your issue been solved? Mark the post using "Accept As Solution" button to let others know.
Superuser

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx


@Laksh wrote:

Hi Joschka2,

 

I have now escalated this post to our labs so that they can have a look at your issue in detail. One of our lab analysts will get in touch with you via email for further communication.


Hello,

 

Sorry for my reply. I just 'randomly' noticed that WhosCall was updated after the latest topic's replies and decided to re-check if F-Secure will detect it (else one time) or not.

 

With my experience -> detection is back :) (or maybe does not re-rated).

So... does it was useful to talk with Lab analysts? And does it was drop status for WhosCall detection?

You did not back with fresh reply about fresh detection (back status) - because did not update WhosCall to latest build.. or situation is fixed locally? // I did transfer URL to F-Secure Labs by F-Secure SAS... about current detection-time. and with 'brief feelings' - except notifcation under FS Protection UI, taskbar(?) and during scaning -> Whoscall still available as application probably (possible to use it). And close notification about detection (as 'cancel' or 'back-back-back').

 

Thanks!

Aspirant

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx

It was not only NOT USEFUL, I was rather outraged by the response which directed ME to contact Whoscall and persuade THEM to contact F-Secure to arrange for Whoscall to do things according to F-Secure preferences.

 

It's been DECADES since I got an arrogant answer like that! (I've been in the software industry since 1968.)

 

As a consequence, despite a good number of years as an F-Secure customer and beta-tester, and despite having almost one full year left on my 15-license purchase, I have switched to Bitdefender.

 

I think F-Secure really should study the features that Bitdefender offers, there is much room for F-Secure to improve.

View solution in original post

Superuser

Re: false flagging of WhosCall on Android has come back = see original case xxxxxx

Hello,

 

I see.

 

I think that maybe such response was with meanings like: current detection for advertisement-module can be 'reasonable' (based on policies about PUA). But not sure... I will try to re-ask after receiving response about my current transfer URL.

 

And about switch to another solution -> did you mean for all of platforms? Or under Android only?

If for Windows too -> does it possible to note what kind of nice features available with another solution (because I'm not able to try it with my devices based on something it always works wrong with this solution; but it can be interesting and good to know for me). Just as sidenote about Support-responses... with your noted solution (previously) I got much more 'strange' response than wtih F-Secure (later). But I did read quite many public responses from different companies - where time to time can be too much strange suggestions. :)

 

Thanks!