1112494 - [FFOS7715 v2.1][FMD]The location is not correct on the website "find.firefox.com".

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: FindMyDevice, defect)

Description

[Chaochao Huang]

Attachment: a picture about the location

STR：
1. Enable find my device in Settings APP
2. Login in the website "find.firefox.com"

OBSERVED:
3. The location is Taipei, but my device is at Tianjin city China.

EXPECTED:
4. The location should be at Tianjin city China.

Comment 1

[Chaochao Huang]

Hi Guilherme

self._watchPositionId = navigator.geolocation.watchPosition(
      function(position) {
        DUMP('received location (' +
          position.coords.latitude + ', ' +
          position.coords.longitude + ')'
        );
Why are the position.coords.latitude and position.coords.longitude  always 25.0392, 121.525.? 
Thanks.

Comment 2

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi ChaoChao -

Just to clarify it is not a network relevant issue, is it possible you can share with me the firefox account you use to test Find My Device? Maybe i can help to login the website to see if i get the correct location at my end

Also I assuming you already login your firefox account on your device, right?

Thanks

Vance

Comment 3

[Chaochao Huang]

(In reply to Vance Chen [:vchen][[e-mail]] from comment #2)
> Hi ChaoChao -
> 
> Just to clarify it is not a network relevant issue, is it possible you can
> share with me the firefox account you use to test Find My Device? Maybe i
> can help to login the website to see if i get the correct location at my end
> 
> Also I assuming you already login your firefox account on your device, right?
> 


OK, the testing account is "[e-mail]" and the secret is "hcc19881114"
Thanks.
> Vance

Comment 4

[Chaochao Huang]

I don't think it's a network relevant issue. The position.coords.latitude and position.coords.longitude  are always 25.0392, 121.525, where is Taipei. So it maybe a geolocation relevant issue.

Comment 5

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Chaochao -

i just ring your device via "Find My Device" page, did you hear the bip?

Also could you help to bring the device to the out door environment? Want to make sure indeed it can find the GPS Satellite

Thanks

Vance

Comment 6

[Chaochao Huang]

(In reply to Vance Chen [:vchen][[e-mail]] from comment #5)

> i just ring your device via "Find My Device" page, did you hear the bip?

So sorry. I didn't hear.

> Also could you help to bring the device to the out door environment? Want to
> make sure indeed it can find the GPS Satellite

OK, I have been outside. Plz test again. Thanks.

Comment 7

[Chaochao Huang]

I have heard the bip. Is the location at Tianjin city?

Comment 8

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

No...it is still in Taipei. Guess we can only wait for Guilherme's feedback...

Thanks

Vance

Comment 9

[Chaochao Huang]

(In reply to Vance Chen [:vchen][[e-mail]] from comment #8)
> No...it is still in Taipei. Guess we can only wait for Guilherme's
> feedback...

OK. Thank you for your help :)

Comment 10

[Guilherme Gonçalves [:ggp]]

(In reply to Chaochao Huang from comment #1)
> Why are the position.coords.latitude and position.coords.longitude  always
> 25.0392, 121.525.? 

This sounds like a geolocation issue. As far as FMD is concerned, the geolocation API is working -- it's just not giving out very good positions :) Garvan, can you help them diagnose this perhaps?

Comment 11

[:garvan]

If you have access to an Android device, please install Mozilla Stumbler, turn on 'Show MLS locations'.
Then stumble a bit in the location you are in (just get 2-3 observations), you can walk in a 100m circle for this. The MLS locations will show up as red dots. Those are what the MLS service is reporting for your location. 

Unfortunately, you will need the GPS to be active on the Android device for Mozilla Stumbler to activate, so if you are in a building, go to a window, you should be able to get >3 satellite fixes at a window of a building.

In summary, if the MLS location is approx 25.0392, 121.525, then the bug is not FMD. It is an MLS accuracy problem, which I can explain further if needed.

Comment 12

[Chaochao Huang]

(In reply to Garvan Keeley [:garvank] from comment #11)
> In summary, if the MLS location is approx 25.0392, 121.525, then the bug is
> not FMD. It is an MLS accuracy problem, which I can explain further if
> needed.

If it is an MLS accuracy problem, the result is so different from the actual situation. And that the result is always 25.0392, 121.525 also isn't normal.

Comment 13

[:garvan]

What device and build is this?
Sorry, I assumed because I was cc'd it was related to MLS, and could be checked against Mozilla Stumbler. If the device is not a Spreadtrum chipset (or something similar that uses our Geo stack), then it isn't using MLS, so ignore my Mozilla Stumbler suggestion. 

In which case, just check on the device what Here maps, or any maps website what the current location on the device is reported as. That would eliminate FMD as the problem.

Comment 14

[Chaochao Huang]

(In reply to Garvan Keeley [:garvank] from comment #13)
> What device and build is this?
The device is a Spreadtrum chipset.
Gaia      4ccc94e470a29cae83c7b4b28e01131ecb3004da
Gecko     c037d04af15649fa3d997eab4dd98a52084529ab
BuildID   20141207141721
Version   34.0
ro.build.version.incremental=55

It's still in Taipei in zMAPs, which is downloaded from marketplace APP.

Comment 15

[:garvan]

Not an FMD bug, is an MLS bug, so please file a bug for Product: Mozilla Services, Component: Location, 
include the IP address of the device.

Comment 16

[Chaochao Huang]

(In reply to Garvan Keeley [:garvank] from comment #15)
> Not an FMD bug, is an MLS bug, so please file a bug for Product: Mozilla
> Services, Component: Location, 
> include the IP address of the device.

I also think it's an MLS bug. Thank you for your reply:)

Comment 17

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Chaochao -

I just tried again find my device and this time it can locate my device successfully. Could you help to try again as well?

Thanks

Vance

Comment 18

[Chaochao Huang]

Vance,

I have tried again, but it is still in Taipei.

Comment 19

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

(In reply to Chaochao Huang from comment #18)
> Vance,
> 
> I have tried again, but it is still in Taipei.

That is so strange...I use the SPRD build with 7715 device and everything works fine:

Gaia      73be51f998031f06db0cd660c0e388fa621c9f4c
Gecko     https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/ea426e47bfc4
BuildID   20141229161203
Version   34.0
ro.build.version.incremental=65
ro.build.date=Mon Dec 15 18:51:29 CST 2014

And it can locate my device in TPE office....

Make me wonder maybe there is something wrong with the GPS chipset of your device? Could you find a new device, flash the same software build as mentioned above and try again?

Thanks for your help

Vance

Comment 20

[:garvan]

In the dev. settings, if you enable Geolocation output in ADB, and 
adb logcat | grep -i geo

You'll see output that will confirm that network geolocation is being used.

I doubt the GPS is getting a location.

Comment 21

[Chaochao Huang]

Gaia      73be51f998031f06db0cd660c0e388fa621c9f4c
Gecko     d9ff7b40310421ce33fe21b1ec6ebd4e1841e9be
BuildID   20141230134755
Version   34.0
ro.build.version.incremental=eng.chaochaohuang.20141210.180828
ro.build.date=Wed Dec 10 18:09:21 CST 2014

I use a new device to test, The location is still in Taipei.


adb logcat | grep -i geo as below:

E/GeckoConsole(  106): *** WIFI GEO: startup called.
I/Gecko   (  106): *** WIFI GEO: startup called.
E/GeckoConsole(  106): *** WIFI GEO: getMobileInfo called
I/Gecko   (  106): *** WIFI GEO: getMobileInfo called
E/GeckoConsole(  106): *** WIFI GEO: Looking for SIM in slot:0 of 2
I/Gecko   (  106): *** WIFI GEO: Looking for SIM in slot:0 of 2
E/GeckoConsole(  106): *** WIFI GEO: Looking for SIM in slot:1 of 2
I/Gecko   (  106): *** WIFI GEO: Looking for SIM in slot:1 of 2
E/GeckoConsole(  106): *** WIFI GEO: Use request cache:false reason:No cached data
I/Gecko   (  106): *** WIFI GEO: Use request cache:false reason:No cached data
E/GeckoConsole(  106): *** WIFI GEO: Sending request
I/Gecko   (  106): *** WIFI GEO: Sending request
E/GeckoConsole(  106): *** WIFI GEO: sending {"wifiAccessPoints":[{"macAddress":"7c-95-f3-07-f1-81","signalStrength":-29},{"macAddress":"90-94-e4-a9-65-0e","signalStrength":-35},{"macAddress":"40-16-7e-31-aa-88","signalStrength":-47},{"macAddress":"bc-ee-7b-6f-7c-78","signalStrength":-52},{"macAddress":"40-16-7e-a3-3e-f8","signalStrength":-53},{"macAddress":"0c-72-2c-26-19-70","signalStrength":-54},{"macAddress":"9c-21-6a-fa-9e-e3","signalStrength":-69},{"macAddress":"ac-9e-17-7b-05-a8","signalStrength":-71},{"macAddress":"38-83-45-3a-d5-94","signalStrength":-71},{"macAddress":"7a-da-6e-e6-da-67","signalStrength":-71},{"macAddress":"7c-95-f3-30-73-91","signalStrength":-72},{"macAddress":"78-da-6e-e6-da-66","signalStrength":-72},{"macAddress":"7a-da-6e-e6-da-68","signalStrength":-72},{"macAddress":"7a-da-6e-e6-da-69","signalStrength":-73},{"macAddress":"0c-72-2c-fa-e0-5e","signalStrength":-74}]}
I/Gecko   (  106): *** WIFI GEO: sending {"wifiAccessPoints":[{"macAddress":"7c-95-f3-07-f1-81","signalStrength":-29},{"macAddress":"90-94-e4-a9-65-0e","signalStrength":-35},{"macAddress":"40-16-7e-31-aa-88","signalStrength":-47},{"macAddress":"bc-ee-7b-6f-7c-78","signalStrength":-52},{"macAddress":"40-16-7e-a3-3e-f8","signalStrength":-53},{"macAddress":"0c-72-2c-26-19-70","signalStrength":-54},{"macAddress":"9c-21-6a-fa-9e-e3","signalStrength":-69},{"macAddress":"ac-9e-17-7b-05-a8","signalStrength":-71},{"macAddress":"38-83-45-3a-d5-94","signalStrength":-71},{"macAddress":"7a-da-6e-e6-da-67","signalStrength":-71},{"macAddress":"7c-95-f3-30-73-91","signalStrength":-72},{"macAddress":"78-da-6e-e6-da-66","signalStrength":-72},{"macAddress":"7a-da-6e-e6-da-68","signalStrength":-72},{"macAddress":"7a-da-6e-e6-da-69","signalStrength":-73},{"macAddress":"0c-72-2c-fa-e0-5e","signalStrength":-74}]}
E/GeckoConsole(  106): *** WIFI GEO: gls returned status: 200 --> {"location":{"lat":25.0392,"lng":121.525},"accuracy":50000}
I/Gecko   (  106): *** WIFI GEO: gls returned status: 200 --> {"location":{"lat":25.0392,"lng":121.525},"accuracy":50000}
E/GeckoConsole(  106): geo: Using MLS, GPS age:1419922645.856000s, MLS Delta:0.000000m
E/GeckoConsole(  106): *** WIFI GEO: getMobileInfo called
I/Gecko   (  106): *** WIFI GEO: getMobileInfo called
E/GeckoConsole(  106): *** WIFI GEO: Looking for SIM in slot:0 of 2
I/Gecko   (  106): *** WIFI GEO: Looking for SIM in slot:0 of 2
E/GeckoConsole(  106): *** WIFI GEO: Looking for SIM in slot:1 of 2
I/Gecko   (  106): *** WIFI GEO: Looking for SIM in slot:1 of 2
E/GeckoConsole(  106): *** WIFI GEO: Use request cache:true reason:New req. is GeoIP.
I/Gecko   (  106): *** WIFI GEO: Use request cache:true reason:New req. is GeoIP.
E/GeckoConsole(  106): geo: Using MLS, GPS age:1419922648.651000s, MLS Delta:0.000000m
E/GeckoConsole(  106): *** WIFI GEO: getMobileInfo called
I/Gecko   (  106): *** WIFI GEO: getMobileInfo called
E/GeckoConsole(  106): *** WIFI GEO: Looking for SIM in slot:0 of 2
I/Gecko   (  106): *** WIFI GEO: Looking for SIM in slot:0 of 2
E/GeckoConsole(  106): *** WIFI GEO: Looking for SIM in slot:1 of 2
I/Gecko   (  106): *** WIFI GEO: Looking for SIM in slot:1 of 2
E/GeckoConsole(  106): *** WIFI GEO: Use request cache:true reason:EqualCells:false EqualWifis:true, Wifi only.
I/Gecko   (  106): *** WIFI GEO: Use request cache:true reason:EqualCells:false EqualWifis:true, Wifi only.
E/GeckoConsole(  106): geo: Using MLS, GPS age:1419922648.958000s, MLS Delta:0.000000m
E/GeckoConsole(  106): *** WIFI GEO: getMobileInfo called
I/Gecko   (  106): *** WIFI GEO: getMobileInfo called
E/GeckoConsole(  106): *** WIFI GEO: Looking for SIM in slot:0 of 2
I/Gecko   (  106): *** WIFI GEO: Looking for SIM in slot:0 of 2
E/GeckoConsole(  106): *** WIFI GEO: Looking for SIM in slot:1 of 2
I/Gecko   (  106): *** WIFI GEO: Looking for SIM in slot:1 of 2
E/GeckoConsole(  106): *** WIFI GEO: Use request cache:true reason:EqualCells:false EqualWifis:true, Wifi only.
I/Gecko   (  106): *** WIFI GEO: Use request cache:true reason:EqualCells:false EqualWifis:true, Wifi only.
E/GeckoConsole(  106): geo: Using MLS, GPS age:1419922653.853000s, MLS Delta:0.000000m

Comment 22

[:garvan]

Thanks for log, makes everything much clearer!

> E/GeckoConsole(  106): *** WIFI GEO: gls returned status: 200 -->
> {"location":{"lat":25.0392,"lng":121.525},"accuracy":50000}
> I/Gecko   (  106): *** WIFI GEO: gls returned status: 200 -->
> {"location":{"lat":25.0392,"lng":121.525},"accuracy":50000}
> E/GeckoConsole(  106): geo: Using MLS, GPS age:1419922645.856000s, MLS
> Delta:0.000000m

Using MLS, so not using the GPS. 
The 50km accuracy level indicates GeoIP is being used.

Comment 23

[Chaochao Huang]

(In reply to Garvan Keeley [:garvank] from comment #22)

What's difference between MLS and GPS? And what is GeoIP? Could you explain more? Thanks a lot.

Comment 24

[:garvan]

MLS => Mozilla Location Service https://location.services.mozilla.com
By scanning cell towers and Wi-Fi access points, the device can ask the service for geolocation. Compared to GPS, is faster + coarser + low power. Ideally, this is <5km accuracy. 

GeoIP => Uses the IP of the device to geolocate. Low accuracy, estimated as 50km. 

Both methods require an Internet connection.

Because these methods are database lookups, any bad data in the db, will result in bad geolocation like you are seeing.

Comment 25

[Chaochao Huang]

(In reply to Garvan Keeley [:garvank] from comment #24)

> 
> Both methods require an Internet connection.
> 
> Because these methods are database lookups, any bad data in the db, will
> result in bad geolocation like you are seeing.

Thanks for your reply. :)

Comment 26

[BMO Automation]

Firefox OS is not being worked on