mwu mentioned it was misconfigured, testing a correct config didnt test for me. But it means anything that uses geolocation doesnt work on the dogfood device.

To be precise, CAPABILITIES was set to 0x27. I asked dale to change it to 0x7 and it sounds like that wasn't enough. Kanru, do you have any ideas?

I've been able to get GPS fixes with the unagi in the past, although my phone is currently decommissioned. Is this a recent regression?

I could still get fixes on Otoro. I haven't tested it on Unagi but it shouldn't change anything. Note that without A-GPS you have to wait a very long time to get the first fix. I'm trying to make A-GPS enabled by default, see bug 813876

Marking as a soft blocker since we'd really like to get this fixed but can't block the release on it.

(In reply to Andrew Overholt [:overholt] from comment #5) > Marking as a soft blocker since we'd really like to get this fixed but can't > block the release on it. Do we know if this happens on otoro too?

It works on a fresh flash on Otoro, I cant test whether this is an otoro vs unagi or update vs fresh flash bug since I am attempting to not flash my unagi

FYI, Geolocation seems to work fine on my otoro even after updates. I re-flashed some time last week but since did updates on the "nightly" channel (18.0 builds) practically daily and using Geolocation often via my Lantea Maps app, where it works fine. I had some problems some time ago when I set the prompt to "Remember my choice" when allowing Geolocation, so I'm explicitly ACK-ing the prompt every time right now. Back then it seemed to not use Geolocation at all when it was permanently granted. I didn't have time to really conclusively test that and report a bug though.

Not device specific (see 825680) - giving it a plus.

this is different from 825680.

This works on my otoro (you need to be outside and have a clear view of the sky).