965191 - Geolocation is broken in non release builds

Status: RESOLVED DUPLICATE of bug 977725

(Firefox OS Graveyard :: Vendcom, defect)

Description

[Dale Harvey (:daleharvey)]

In the last year dogfooding I think I got a fix once, I know we have the whole partner / service issue, but unless I can get a phone with working GPS then its pretty much a brick to me. 

Hopefully the new location services stuff helps

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I don't see any locsrv in the logcat; what I get instead is : 
01-31 02:02:48.770: E/QCALOG(190): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent]
01-31 02:02:49.000: E/QCALOG(190): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent]
01-31 02:02:49.000: E/QCALOG(190): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent]

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

To note: I used a buri device.

Alexandre Lissy pointed out to two things that could be the issue:
1) "Reuben fixed a permission issue
(https://bugzilla.mozilla.org/show_bug.cgi?id=955906) that was
specifically triggered with geolocation. I've used geolocation no later
than one hour ago with a build done a few hours ago, both on Nexus S and
HTC Desire Z."

2) https://bugzilla.mozilla.org/show_bug.cgi?id=908151#c7
Though I'm pretty sure QC uses /system/etc/gps.conf and it's not embedded in the bootloader.  I could be mistaken for the geeksphone.  Meaning the cert can be created for the server that we're now switched to, all we have to do is create a SuplRootCert : http://blog.cryptomilk.org/2012/07/24/how-to-create-a-suplrootcert-for-supl-google-com/ is my guess.

Comment 3

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I think this bug might be a dup of bug 955880, reading on their issue.

Comment 4

[Doug Turner (:dougt)]

for more information:
   https://wiki.mozilla.org/B2G/Geolocation

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Geolocation is still broken in today's build which does have the fix in bug 955906: 
01-31 17:04:47.319: E/QCALOG(187): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent]
01-31 17:04:47.339: E/QCALOG(187): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent]
01-31 17:04:47.349: E/QCALOG(187): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent]

Gaia      aedd5c9636f305d4433491056a0ca984dfb859b1
Gecko     http://hg.mozilla.org/mozilla-central/rev/735a648bca0d
BuildID   20140131095418
Version   29.0a1
ro.build.version.incremental=324
ro.build.date=Thu Dec 19 14:04:55 CST 2013
Buri

If the GPS doesn't work without the QC geolocation and only our code, how is "Where's my fox?" going to work?  Also what about the MWC demo devices that rely on the use of GPS?

Comment 6

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Attachment: gps_buri_v1.2_devices.zip

To note, I can get GPS working with the configs that I have in this zip file using Google SUPL server for v1.2_devices.cfg OEM build.

Using the same configs, I cannot get it to work for 1.4

Comment 7

[Doug Turner (:dougt)]

Hey Naoki!

This is a very important observation.  As I mentioned on IRC, the blobs from QC *must* match the gecko we are running or there is a chance for RIL and Geolocation breakage.  I believe that is what you are seeing here.  If you want to test against 1.4, you will need to ask the OEM to provide a QC blob that contains an update.


For everyone else -- Do NOT point at Google SUPL server.  We have absolutely zero right to do that.

Comment 8

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

If I understand this correctly, this would pose as a blocker per device for testing "Where's my fox?"

Comment 10

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Attachment: gps_buri1.2_iza.zip

revamped to using the supl.izatcloud.net server.

Comment 11

[Tony Chung [:tchung]]

Affects the Sora device as well, running 1.3.   John, can you attach any logs and STR when you reproduce?

Comment 12

[John Hammink]

Attachment: here maps does not find a location

Comment 13

[John Hammink]

Attachment: facebook checkin does find a location

Comment 14

[John Hammink]

Attached the two logs from different geolocation tests.  Here maps does not work, fb checkin does - but it's very inconsistent.  I would definitely not want to have to demo this, as it's simply not reliable.

Sora build 3:
Gaia      741869c9f0eaae242351f312c18fa6051715c086
Gecko     96b3233f80637206d502b52f238196fa86769ec9
BuildID   20140207155315
Version   28.0
ro.build.version.incremental=221

Comment 15

[Al Tsai [:atsai]]

Tested with v1.3 buri

Gaia      df60e9b49207d64da5647ab15760c122adabfba4
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/0714a73350d8
BuildID   20140217164003
Version   28.0

It doesn't work. Mark it as v1.3?

Comment 17

[Jason Smith [:jsmith]]

Note - there's two problems here:

* Browser case is bug 951785
* App case is bug 974976

I've duped to one of the two bugs, but technically this is a dupe of both bugs.

Comment 18

[Dale Harvey (:daleharvey)]

On the latest build here maps opened to the netherlands, so im gonna go ahead and reopen

Comment 19

[Jason Smith [:jsmith]]

(In reply to Dale Harvey (:daleharvey) from comment #18)
> On the latest build here maps opened to the netherlands, so im gonna go
> ahead and reopen

That's not the same bug as this. Please open a specific bug focusing on the exact context of the problem, not a "geolocation is broken" bug.

Comment 20

[Jason Smith [:jsmith]]

(In reply to Jason Smith [:jsmith] from comment #19)
> (In reply to Dale Harvey (:daleharvey) from comment #18)
> > On the latest build here maps opened to the netherlands, so im gonna go
> > ahead and reopen
> 
> That's not the same bug as this. Please open a specific bug focusing on the
> exact context of the problem, not a "geolocation is broken" bug.
> 
> *** This bug has been marked as a duplicate of bug 951785 ***

Although I don't think what you are describing is a bug anyways - HERE Maps won't open to your location until your location is found. Your location is found when the dot goes green.

Comment 21

[Dale Harvey (:daleharvey)]

and the dot will not go green because geolocation is broken on non release builds which is the exact context the problem that I reported this bug for

Comment 22

[Dietrich Ayala (:dietrich)]

Requesting blocking. This is a *development blocker*. Anyone using eng builds cannot test geolocation features at all.

Comment 23

[Dale Harvey (:daleharvey)]

I remember seeing doug mention tarako will be using mozilla location services, are we just going to have all non production builds use them? bug open to track?

Comment 24

[Preeti Raghunath(:Preeti)]

Doug,

Is there anything steps pending on Moz' end? This seems to be an ongoing release issue.

Please weigh in.

Comment 25

[Doug Turner (:dougt)]

will be fixed by 977725.  kind of.

See https://wiki.mozilla.org/B2G/Geolocation for background.