I really like the idea behind Mozilla Location Services. I’m thinking of a way to help that initiative. Are there some major problems with the database that could be solved in a crowd-sourced manner?
What I’m interested in particular is:
Is the amount of data in the database satisfactory?
Are there any regions that need more data badly?
Is Mozilla Stumbler the only source of data for the services?
@hannosch , do you know, what is the current status of MLS? I have recently noticed the change in Mozilla Stumbler, that the measurements are attributed based on Firefox Account login. And the option to turn measurement on in Firefox for Android is still there. But as Daniele mentioned, no promotion for a long time…
MLS is alive and well, but it is partly a victim of its own success.
At this point there aren’t any major features missing from MLS and the client applications. While there is always room for improvements, by and large MLS has achieved what it set out to do and is working well.
It’s also true that after work on Firefox OS stopped, MLS is no longer an important strategic service for Mozilla, so the available staff working on it got reduced. I continue to work on it as a part time project, but that is focused on the service side, operations and general project management. There hasn’t been anyone working on the standalone Mozilla Stumbler app or the leaderboard service for a couple months now.
We also get most of our data from users using Firefox for Android and opt-ing into the contribution option in the mobile browser. The number of contributors from this are at least a hundred times more than the number of contributors using the standalone Mozilla Stumbler app. So the Mozilla Stumbler app and its leaderboard where always more of a hobby project.
Looking forward I think MLS will continue to exist and be maintained. There are enough people in upper management at Mozilla who like MLS and the general idea of it. But whether or not it will get more attention and focus again is anyone’s guess.
We’re gathering data a hundred times fast, but do we still use data from it anymore? MLS is started to help Firefox OS and is it targeted to set as location service for Firefox in future with any timetable?
Data gathering in Firefox for Android is optimized to have little battery cost and no mobile data plan usage. It sit and waits until other applications on the phone obtain GPS-based location information, for example Google Maps. The battery impact of using the GPS sensor is so large, that anything else you do at the same time is basically not noticeable. When some other application get a GPS based position, our data gathering code gets activated as well and initiates a scan for nearby cell and WiFi networks. Often enough the other application will have also caused those, as part of getting a location fix, so there’s almost no additional battery cost that can be attributed to our code.
Finally with the GPS position and the cell and WiFi networks in hand, our code stores those locally on the phone. There are also a variety of rate limits in place, so we don’t collect too often and not more than a certain amount per day.
Once the phone connects to a WiFi network, the locally stored data is uploaded to our service, avoiding mobile data plan costs.
The phone won’t collect more data, when it already has reached its total quota and wasn’t able to send data to us, so it won’t spam the local disk.
Currently there are no configuration options to change any of those default settings, as that would defeat the simple “opt-in and don’t worry” model we choose. If one wants more control, the dedicated Mozilla Stumbler app is there for you.
For Firefox specifically, MLS is used by default for Firefox Aurora/Nightly users and Firefox users on all channels for some Linux distribution provided packages (Fedora, ArchLinux, etc.).
The situation with Firefox Desktop release and beta channels is complicated, as it touches business contracts and isn’t merely decided based on technical merit. As a single user, everyone can switch from the default geolocation provider to MLS by adjusting the “geo.wifi.uri” preference in about config and changing it to “https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%”.
Yes, though there is no user id or token being sent to the service or any other identifying information. So on its own it’s hard to impossible to correlate multiple queries and assign them to the same user or connect that information to anything else about the user.
Firefox Desktop as shipped and distributed by Mozilla has used Google’s location service since the geolocation feature was introduced into the browser. I believe the same is true for Firefox distributed by Canonical (Ubuntu). This is stated fairly clearly in the privacy policy (Firefox Privacy Notice — Mozilla - second “learn more” link, in the Location services section). Firefox for Android uses the Android Open Source API on the phone to get the users location. If and what service is called there depends on the device, but it’s safe to assume that this is also frequently Google. Firefox for iOS uses Apple’s location service.
Great to know that there are some services still using MLS. Because we had a pretty bad reputation on closing services that with less usage, so it’s also a challenge for local communities to keep promoting it.
Hi everyone,
I’d like to use MLS add my default location service on my Android phone. Unfortunately I can’t install a custom ROM or root it to use Xposed and the UnifiedNlp mods. Is there any other way to use MLS by default?
Thanks