The server is test.supl.svc.ovi.com:7276. Kan-Ru can you test this server? I haven't been able to make SUPL connections through my provider :(. We should ensure that this configuration isn't used for production builds; there should be an explicit flag set to enable this configuration.

Comment on attachment 710036 [details] Pull request Are we actually ok to ship the pref file? If so, this patch is ok. If not, we should just use custom-prefs.js

I don't think I understand fabrice's question. We can't ship this file with production devices. But we can and do want to distribute it in development builds.

Does dogfood count as production devices or development builds?

Development.

Comment on attachment 710036 [details] Pull request Ask for review again given comment 6

Comment on attachment 710036 [details] Pull request [Approval Request Comment] Dogfood only

v1-train: f8f45aca2d5565dc0a5005356695aed46dec0f32

Batch edit: bugs fixed on b2g18 since 1/25 branch of v1.0 are fixed on v1.0.1

Hi, I think we should reconsider how the fix was done here. I can see 2 possibilities : * Fabrice's proposition in comment 3: Releng would add a local build/custom-prefs.js file in their build environment, and we backout what was commited here. This adds more work to the releng team though. * We change the property to add this to (for example) SUPL_PREFS=1. I'd like to decorrelate DOGFOOD=1 with this, because DOGFOOD=1 is supposed to do much more. We could still make DOGFOOD=1 trigger SUPL_PREFS=1, but it would make it possible to add the prefs for the supl server in dev builds. Fabrice, I'd love to know your opinion on this. I'd say the second way could be easier for everyone. If this is the way to do it, I'll go on with filing another bug and fixing this.

I'm not against adding something like SUPL_PREFS, even if I'm not a big fan. But I really think we should not make any env var trigger another one. Let's do everything explicitly, and not hidden behind some magic dependency.

I just found that the GPS prefs were recently moved to all builds in Bug 850112. So there is no need to do anything else here.