1

I don’t know what you guys are doing with the beta but its going from bad to worse. Call blocking, App locking: switches don’t work. Screens stay darkened can’t view app permissions. Dozens of features missing from the non-beta, you name it…

2

I agree the beta is a load of fart! I can’t view my mobile account in avast account because it simply is not there. What excellent protection if my phone is stolen. I would say they need to go back to the drawing board and come up with something even half decent.

3

the AV is for if your phone gets stolen. That’s anti-theft, not mobile security. Or in this case, lack of security. Though anti-theft root never got updated for lollipop support (advanced users only they say, load of bullcrap) but i’m not holding much hope for Marshmallow either

4

Regarding the switches, are you using something like CF.Lumen, F.Lux, Twighlight or a similar app, that makes a transparent yellow/red colored overlay at night?

5

Hi Patrice58, please be patient - we fixed my.avast.com connection issues in latest beta. You should see your device connected. Could you please confirm?

6

Yes the account is there.

7

@Ondrej Cermak: yes but i double checked it during the day around 2PM when its not active. Still wouldn’t work. As such its not a CF.Lumen cause problem.

8

Depends if “not active” means “no overlay” or “invisible overlay”. Just try to Force stop the application and try it in AMS again. We’re intentionally blocking disabling the switch if there’s an overlay, because of possible click-jacking attack - a malicious app, that could look like a game, could play you into disabling app-locking. Not saying that the attack vector is particularly big, but we chose to stay on the safe side :).

9

Well force closing did it but not having cf.lumen active is not an option. I was able to bypass this by disabling cf, enabling the switches and enable cf again. I know of the malware and don’t use any of the apps it fakes. Chainfire is a well known developer on xda and creator of SuperSU. AVAST in this case is being a bit TOO sensitive.

Case and point: superSU itself. Also has clickjacking protection but things still work fine in it with cf.lumen enabled.

10

I’m not sure if it’s possible to somehow detect who’s overlay is displayed, so we could let the click go through. But we can for sure investigate that, because it seems like SuperSU must do it somehow :slight_smile: