Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPS position update is very slow and remembers old position in maps.google.com in Browser #356

Open
ghost opened this issue Dec 12, 2017 · 18 comments

Comments

@ghost
Copy link

commented Dec 12, 2017

  • Device: FP2
  • Channel: RC
  • Build: 15.04 r15

Steps to reproduce

  1. Open Browser go to maps.google.com
  2. Walk around :)
  3. GPS is not "real time" it takes even couple minutes to update

Expected behavoir

Position should be updated within a reasonable time (TBD, my suggestion 10 secs)

Actual behavior

Update of position takes couple minutes. Furthermore it stores some old position when one clicks the icon to zoom in to current position. Although it had already newer positions.

Logfiles and additional information

...

@NeoTheThird NeoTheThird added the bug label Dec 12, 2017

@NeoTheThird

This comment has been minimized.

Copy link
Member

commented Dec 12, 2017

I can confirm this.

@ghost

This comment has been minimized.

Copy link
Author

commented Dec 12, 2017

Made me wander around the city quite a lot :D

@NeoTheThird

This comment has been minimized.

Copy link
Member

commented Dec 12, 2017

From my experience, GPS works a lot better in uNav, but even there it's far from perfect.

@mardy

This comment has been minimized.

Copy link
Member

commented Dec 12, 2017

This might be relevant:
https://code.launchpad.net/~mardy/location-service/last-known-position/+merge/277358
Currently, the last known position is always returned as soon as a GPS session starts; the above branch would instead deliver the last known position as a separate field, so that applications who want that information can get it, and applications who don't care about it won't be led into thinking that that is the current position.

@NeoTheThird

This comment has been minimized.

Copy link
Member

commented Dec 12, 2017

@mardy Holy shit, that has been ready since 2015!?

@mardy

This comment has been minimized.

Copy link
Member

commented Dec 13, 2017

@NeoTheThird Not really, that merge proposal is in a rather confusing state. The final commit was made on July 2016, and was never reviewed.
I find the location-service code to be very hard to read and work with, so it would be better to find someone else for working on it (or I could rewrite it from scratch :-) ).

@NeoTheThird

This comment has been minimized.

Copy link
Member

commented Dec 13, 2017

@mardy Yeah, that is true. Not fun to work with that one... Wouldn't want to waste too much of your time refactoring though, what do you think how much work that would be? Difficult decision, but the benefit could definitely be big... In the end it comes down to you. Do you want to work on that? If not, it's out of the question either way.

@mardy

This comment has been minimized.

Copy link
Member

commented Dec 18, 2017

I guess I could simply try to push that patch into the devel image, and then we can test it. But I'm afraid I'm not willing to spend much more time than that on this codebase :-)
Let's keep this bug open, eventually I'll get to make a merge proposal.

@mauricioduarte01

This comment has been minimized.

Copy link

commented Dec 19, 2017

Hi. Yeah the GPS is still broken. I hope you guys can deliver a solution on this asap because nowdays having a GPS is essential for most of us. Thank you for all of your effort!

@NeoTheThird

This comment has been minimized.

Copy link
Member

commented Dec 19, 2017

@mauricioduarte01 How's your experience in uNav? Better or equal?

@mauricioduarte01

This comment has been minimized.

Copy link

commented Dec 19, 2017

@NeoTheThird Hey Jan,
Well it depends, sometimes it connects quicker sometimes it takes some time. Tbh I dont use uNav because it lacks in functionality. Anyways, I will try tomorrow uNav gps without wifi and see what happens. Thank you

@ghost

This comment has been minimized.

Copy link
Author

commented Dec 30, 2017

In OTA-3 GPS position is not updated at all and led to restarts. Tried uNav as well.

@ghost

This comment has been minimized.

Copy link
Author

commented Dec 30, 2017

And the battery drain is very impressive. 50 percent in 1.5 hours

@jonnius

This comment has been minimized.

Copy link
Contributor

commented May 27, 2018

In 15.04 and 16.04 GPS is working well for me in unav, once I got a fix. But getting a fix may take up to 2min. I have one of the first FP2s, maybe this is relevant?

@Flohack74

This comment has been minimized.

Copy link
Member

commented May 27, 2018

2 minutes is very fast :) - People sometimes have to wait 20mins on their devices...

@Flohack74

This comment has been minimized.

Copy link
Member

commented May 27, 2018

To better understand the problem, read this: https://en.wikipedia.org/wiki/Time_to_first_fix - We are often in the cold boot situation with the GPS, since it is turned off in Ubuntu Touch, unlike Android or iOS. If you dont use it for a few days, you have to wait ages...

@Mannshoch

This comment has been minimized.

Copy link

commented Aug 22, 2018

How does Ubport handle the Almanac refresh?
Is there only the Updates from the GPS Signal ore does ubport also download almanac data from a server?

@Flohack74

This comment has been minimized.

Copy link
Member

commented Aug 22, 2018

Nothing gets downloaded... we simply start the Android GPS if it is available and then sit and wait until it gives reasonable fixtures :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.