The same problem for me.
A partial solution to the problem (at least aesthetic, so as not to leave the
scope as a blank page) is the ability to save a fictional location that allows
the scope to upload the location information and do not stay white. Only if the
GPS provides location data, then t
Nearby GPS positioning has got many problems. It is a very slow process
at phone start-up and it doesn't work very well in my opinion. I'm in
Italy, in Rome, and before to find the exact location, it takes always
at least 4/5 attempts: it's frustrating. My phone is a BQ Aquaris E5. I
have to tell a
With the Pro 5, the problem still exists. Last year I reviewed the MX4
and NearBy located me in the city of Gemünden, about 500 KM away from my
real location in Berlin. Refreshing did not work in most cases. The Pro
5 locates me in the exact same place that the MX4 did. I have no idea
why location
Small update with MX4. I've switched from UT to Cyanogenmod 12.1 and tested GPS
fix.
It get that fix in 2-3 seconds with data mobile and WiFi turned off! So problem
isn't hardware, is software (at least in MX4).
--
You received this bug notification because you are a member of Ubuntu
Touch seed
** Changed in: unity-scopes-api (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1481240
Title:
Can't get correct locat
Regarding GPS fix I think that it's hardware problem (GPS used in Cortex),
because I look at several android phones and here're my results:
- all phones tested with Snapdragon (Nexus 4, LG L fino, one HTC) get first fix
below 10 seconds;
- all phones tested with Cortex (Lenovo A820, MX4, Kazam) g
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
ht
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: location-service (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
http
this branch contains an armhf click of a scope that shows the location
passed (mentioned in comment #8) through Searchmetat obj as both a
single scope result and into scope-registry.log:
lp:~knitzsche/savilerow/location_tester
--
You received this bug notification because you are a member of Ubu
I'm not convinced that location-service is causing issues here. We do
not switch on positioning unless someone explicitly asks us to do so. In
that case, it will take ~30 seconds until network-based positioning
kicks in and likely another 2 - 3 minutes until the GPS hands us a
position. With that,
Scopes-api is innocent here. I just passes the location info it gets
from the shell without touching or caching it. Adding the shell and
location-service to the bug.
** Also affects: location-service (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity-scopes-shell (Ubuntu)
If I have a proper precise (GPS based) location (lat&long) in a scope
from SearchMetadata.location().latitude()|longitude(), and then disable
Location indicator > Location detection OR GPS, then reenable it and
refresh the scope, I never get a precise location back. I am stuck with
geo IP derived l
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-scopes-api (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https:
The scopes shell plugin does cache the GeoIP location, yes. It also has
a timeout, and is refreshed periodically.
As soon as your device acquires a proper GPS lock, however, the scopes
shell plugin immediately prefers the true GPS lock.
However, the location service does not provide any high leve
Pete, wasn't there some issue with location services being slow and
falling back to IP location, which then gets cached for a while?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.laun
I have added unity-scopes-api since I don't think this has anything to
do with the NearBy scope implementation.
** Also affects: unity-scopes-api (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
16 matches
Mail list logo