1035107 - (mls-flame) MLS for Flame

Status: RESOLVED WORKSFORME

(Core :: DOM: Geolocation, defect)

Description

[Hanno Schlichting]

Tracking bug for MLS for Flame.

We are getting user reports about bugs in the MLS / Flame integration. So far this combination isn't actually an officially supported combination. To my knowledge the Flame devices ship with a replaced geo stack from our partner that doesn't use MLS.

But if users choose to install a nightly build provided by Mozilla, that replaced geo stack isn't there and users will use MLS instead.

Things to figure out, from what I can think of:

1. Is that statement about different geo stacks indeed true?
2. Which of the currently active bugs have been merged and are fixed for master?
3. It sounds like the Flame is a GSM/UMTS multi-SIM device, so needs the same bugs fixed as Dolphin
4. Generate a proper MLS API key and get it into the nightly build system (currently users seem to be using the build system fallback of "no-mozilla-api-key"). If the partner provided builds also use MLS, get them an API key as well.
5. Figure out GPS / MLS interaction on Flame, does this work? How does this work with partner geo stack vs. our geo stack?

These sorts of issues might apply more broadly to anyone using FxOS master for development, and not just the Flame device.

Comment 1

[Hanno Schlichting]

The issues I mentioned are actually all done and working.

For the API key, the build system default is actually ok here, as we want MLS to work for developers doing their own builds and flashing their devices.