*** This bug is a duplicate of bug 1367244 ***
https://bugs.launchpad.net/bugs/1367244
** This bug has been marked a duplicate of private bug 1367244
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
** Tags added: rtm14
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1375896
Title:
location not working reliably in browser or webapps
To manage notifications about this
In my experience, due to LP #1367244 it's rare that HERE works on boot.
However, I can reliably get a position in my regular testing setup by
restarting ubuntu-location-provider-here-posclientd after boot. Then I
always get a position after 30s in OSMTouch and in webapps.
--
You received this
So the conclusion is that this is not a webbrowser-app/container problem
anymore at this stage. Marking invalid for the web part.
** Changed in: webbrowser-app
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
There have been reports from others that after wiping their phone, that
both Google and HERE work but then after updating they don't continue to
work. ChickenCutlass has experienced this and I believe pmcgowan has as
well.
** Changed in: location-service (Ubuntu)
Importance: Undecided =
My recent experience:
Location is determined at app launch or quickly thereafter on nexus 4
using google maps
On krillin, I did not get a location fix in Here or Google across multiple
reboots
Also on krillin, I was not originally prompted to enable access for the webapp,
after a reboot and
Thanks for filing the bug. Could you please specify which versions you
were using, i.e., devel-proposed, rtm etc.?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1375896
krillin build 72, which is rtm-proposed
On Tue, Sep 30, 2014 at 3:14 PM, Thomas Voß 1375...@bugs.launchpad.net
wrote:
Thanks for filing the bug. Could you please specify which versions you
were using, i.e., devel-proposed, rtm etc.?
--
You received this bug notification because you are
FWIW, here’s my experience: I flashed image #72 (14.09-proposed) onto my
krillin and tested both maps.google.com and here.com, for which I got
geolocation working. I then applied the OTA update to #73, rebooted, and
it is still working.
--
You received this bug notification because you are a
I run OSMtouch app and it is able to locate me. I do get a popup
saying No GPS available. Position is approximate but the location
on the map is roughly accurate.
I had a look at OSMtouch’s code, and this message indicates that the app
failed to get a position fix from the location service,
10 matches
Mail list logo
