mcastillof
mcastillof
I was trying in DuckDuckGo browser (also in F-droid), and I see the same problem. I realized that the steps to reproduce the problem could be shortened. * Clear cache...
Ok I understand, but in that case there is a leak in the sandbox, because even if I start a new sandbox they can still do tracking. I would expect...
Problem persist when changing the display size.
Ok, I have rebuilt WebApps using the following User Agent taken from User-Agent Switcher plugin for Firefox/Chrome: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.9 Safari/537.36 The problem...
The UserAgent could be spoofed just as you pointed out. But I'm thinking that the problem is within WebView. WebView is adding 'X-Requested-With' header, which shows which app is doing...
I see some bugs that are dated as '46 years ago', but they don't have any report inside. I think that '46 years ago' is related to Unix Epoch (1/1/1970).
Hello AndiLeni, based on the tests that I have done in my device, taping the stop button should stop fake locations. If this is not the case, remove Fake Traveler...
@AndiLeni The Apply button becomes Stop button (text changed) only if the refresh setting is greater than 1. If the refresh setting is 1, then the location is set only...
just to be sure, did you increase the refresh time in the settings?
Hello @dzamizain, thanks you for taking the time to write those enhancement requests. 1.- Fake in satellite: This could be easy to implement. We only need to get satellite tiles...