Unfortunately I'm sure because when I disable Adguard the issue is gone. It could be somehow related to filtering of applications that I have enabled.
I'm not sure, I will have to check it later today as I don't have my tablet with me. OK, let's suppose that the problem is in this option but it doesn't answer question why it happens in browsers.
Trying to understand which level of filtering causing the issue. It could be either TCP-level (if the issue is here with disabled "filter apps traffic") or HTTP-level.
I was trying to reproduce it all day, but still no luck. Could you please send us a message from the app next time you face this issue? Maybe I'll notice something in your log.
@avatar Have noticed that v1.0.523 is recorded on Google Play but on your website is only 1.0.493. Does it mean that you won't keep the latest builds on your site? It would be odd because you said that the build on your site includes also applications filtering. Can you clarify because now I don't know which the update channel I should follow. Thanks
New version is published but we have not yet added information to our website. It's hard to understand when it is really published to Google Play so there is also a small gap after GP release.
Thanks. I have been prompted to update my installation via GUI. It downloaded the new installer to my tablet and running this file brought the latest version including applications filtering. So it is independent on Google Play and I will keep this update channel.
This filter contains rules specific for mobile devices: mobile ad networks mostly. There is no need in these rules on the desktop because these ad networks aren't used on common websites.
Thanks for the clarification. Btw, I updated (from your website) from .523 to .532 yesterday and I had open (in the background) Opera browser. After update I noticed that Opera isn't filtered by Adguard. I had to shut down Opera and restart it to let Adguard filter Opera again. So, my conclusion is that during update all browsers should be down and if not they need to be restarted. I'm not complaining, just giving the facts.
My guess is that some connections were made by Opera before new version was installed. These connections remained unfiltered after update. All new connections should have been filtered. New version is out: http://adguard.com/en/adguard-android/release-notes.html#android-1.0.564
When today updating filters manually in extension for Chrome I'm getting intermittently "Failed to update". Any problems with Adguard servers? EDIT: It seems ok now. Perhaps it was a hiccup.
Ok updated and filtering of Opera is still buggy. After update it didn't filter Opera, so closed Opera, shut down Adguard, restarted Adguard, starting Opera but filtering didn't work. So last attempt was to clear cache on my tablet. Only after that Adguard started to filter Opera.
Well, 564 is the worst build. Surfing is incredibly lazy, it takes ages to load websites, when trying to shut down Adguard it is stopping it's protection a couple of minutes. Sorry but have no other chance than to uninstall it. Edit: I installed it again. Only default options and free version, i.e. no applications filtering and no browser protection but it proved to be indeed unusable build. Really disaster. Uninstalled it. It's pity.
Argh, sorry for the delay, I don't receive notifications about your posts from this forum. Please try the latest version (1.0.589). Have you tried restoring purchases on the license screen?
Tried both .589, from Play and apk but to no avail. Webpages load very very slowly what has also negative impact on battery consumption. You had to something change in build .564 and up because since this build it is unusable (in my case). No, tried it in the free mode to see if it makes any difference and then I simply put my key and activated the premium version what unfortunately made no difference as far as my issues are concerned.
This is sooo weird, you are the only person who complaints on slow page load in new builds. Normally this new build is much faster than previous, it's very interesting why it is so slow in your case. What filtering mode do you use? Proxy or VPN? Have you tried switching filtering mode? Could you please collect logs for us? To do this: 1. Switch logging level to "Record everything" in Adguard's extended settings 2. Open any webpage (or several webpages) 3. Get the log file from: /sdcard/data/com.adguard.android/cache/logs 4. Send it to devteam@adguard.com
Ok will check later and revert. Btw, how to write an exception for embedded video on a site? Event Type in the log is Injected CSS/JS. Can you write me a sample of this exception?