organicmaps/organicmaps-tmp

Archived

Fork 1

On the app launch map view scrolls to current location without updating it #2836

New issue

Open

opened 2022-06-27 04:00:35 +00:00 by PetbkA · 12 comments

PetbkA commented

2022-06-27 04:00:35 +00:00

(Migrated from github.com)

OS: LineageOS 17.1 (Android 10)
OM: version 2022.05.31-10-FDroid
Device: Xiaomi Redmi Note 9 Pro

Doesn't always reproduce so can't attach logs and video.

Sometimes I'm planning my trip and adding bookmarks in other city while sitting home.

Next day I'm going to subway and launch OM to continue planning.

But instead of showing me the position I was yesterday (i.e. the other city), it starts to scroll to the last detected position. And may be that would be fine if the location was my real location (somewhere in my city), but it scrolls to some "cached" location which is my home or even other address which has been "cached" (location arrow is
greyed out).

I suggest to disable auto scrolling to location on start, at least until it hasn't been really updated

**OS:** LineageOS 17.1 (Android 10) **OM:** version 2022.05.31-10-FDroid **Device:** Xiaomi Redmi Note 9 Pro Doesn't always reproduce so can't attach logs and video. Sometimes I'm planning my trip and adding bookmarks in other city while sitting home. Next day I'm going to subway and launch OM to continue planning. But instead of showing me the position I was yesterday (i.e. the other city), it starts to scroll to the last detected position. And may be that would be fine if the location was my _real_ location (somewhere in my city), but it scrolls to some "cached" location which is my home or even other address which has been "cached" (location arrow is [greyed out](https://user-images.githubusercontent.com/22843816/175857053-8d00da61-e946-4fc5-96e4-a234617a97cc.png)). I suggest to disable auto scrolling to location on start, at least until it hasn't been _really_ updated

biodranik commented

2022-06-27 05:49:39 +00:00

(Migrated from github.com)

@vng it looks like a bug. Did you insert 24 hours timer to restore "my position" mode? But what is that "cached" position then?

@PetbkA can you please enable logs and reproduce it?

@vng it looks like a bug. Did you insert 24 hours timer to restore "my position" mode? But what is that "cached" position then? @PetbkA can you please enable logs and reproduce it?

PetbkA commented

2022-06-27 05:56:57 +00:00

(Migrated from github.com)

@biodranik , I'll try, but now the location is cleared so there's no arrow at all

PetbkA commented

2022-06-29 03:11:52 +00:00

(Migrated from github.com)

@biodranik , tried yesterday on 05.31 but couldn't reproduce auto scrolling to position - OM always starts on the last map view location and doesn't scroll to "current" location.

The only thing that's still here on 2022.06.18-2-FDroid is that it scrolls to greyed out arrow when location search is triggered manually (video, logs), although this isn't the case of this bug

@biodranik , tried yesterday on **05.31** but couldn't reproduce auto scrolling to position - OM always starts on the last map view location and doesn't scroll to "current" location. The only thing that's still here on **2022.06.18-2-FDroid** is that it scrolls to greyed out arrow when location search is triggered manually ([video](https://user-images.githubusercontent.com/22843816/176342745-1553e3aa-8ca2-4613-944c-cfa7467e4788.mp4), [logs](https://github.com/organicmaps/organicmaps/files/9006932/logs.zip)), although this isn't the case of this bug

biodranik commented

2022-06-29 06:31:19 +00:00

(Migrated from github.com)

So it is not possible to reproduce the original issue, right? Did you try after more than 24 hours?
What is the last issue about? When you press the location button, it centers on greyed location. Right? What is the issue?

1. So it is not possible to reproduce the original issue, right? Did you try after more than 24 hours? 2. What is the last issue about? When you press the location button, it centers on greyed location. Right? What is the issue?

PetbkA commented

2022-06-29 08:09:05 +00:00

(Migrated from github.com)

So it is not possible to reproduce the original issue, right?

Guess it isn't.

Did you try after more than 24 hours?

Nope. The above try was after 5 or 6 hours from certain location detection. And now there's no arrow at all.

When you press the location button, it centers on greyed location. Right?

Yes.

What is the issue?

Considering the time that passed after the last location detection, it would be better to search for location again. On the other hand, it would be better to just remove the arrow.

I guess for now there's no real issue

> So it is not possible to reproduce the original issue, right? Guess it isn't. > Did you try after more than 24 hours? Nope. The above try was after 5 or 6 hours from certain location detection. And now there's no arrow at all. > When you press the location button, it centers on greyed location. Right? Yes. > What is the issue? Considering the time that passed after the last location detection, it would be better to search for location again. On the other hand, it would be better to just remove the arrow. I guess for now there's no real issue

biodranik commented

2022-06-29 09:10:12 +00:00

(Migrated from github.com)

So the bug is that the grey arrow is displayed for a very outdated location. Right? Then it should be fixed. Can you please reproduce it with enabled logs and confirm that our code still shows a location which is > 5min old?

PetbkA commented

2022-06-29 09:15:56 +00:00

(Migrated from github.com)

Can you please reproduce it with enabled logs and confirm that our code still shows a location which is > 5min old?

OK, I'll try again right after 6+ minutes from the last location detection

> Can you please reproduce it with enabled logs and confirm that our code still shows a location which is > 5min old? OK, I'll try again right after 6+ minutes from the last location detection

PetbkA commented

2022-06-30 03:08:03 +00:00

(Migrated from github.com)

@biodranik , tried yesterday:

In about 19:55 GMT+3 started OM and found my location. Exited OM with navbar Back button;
In about 20:10 started OM again - greu arrow was there. Exited OM with back button;
But in 20:14 there already was no arrow.

Here are the logs

@biodranik , tried yesterday: 1. In about 19:55 GMT+3 started OM and found my location. Exited OM with navbar _Back_ button; 2. In about 20:10 started OM again - greu arrow was there. Exited OM with back button; 3. But in 20:14 there already was no arrow. Here are the [logs](https://github.com/organicmaps/organicmaps/files/9016121/logs.zip)

biodranik commented

2022-06-30 05:43:50 +00:00

(Migrated from github.com)

@vng what is the current timeout for the outdated location? 15 minutes looks too much, it was 5 minutes as I remember.

PetbkA commented

2022-07-31 05:51:50 +00:00

(Migrated from github.com)

2022.07.01-6-FDroid - reproduced again, i.e. app scrolled to "grey" position after launch, although 9 hours have passed since previous launch (according to app.log).

Here are the logs.zip. Logging has been enabled all the time since I created this issue, and archive has been manually created in Android\data right after reproducing the bug

**2022.07.01-6-FDroid** - reproduced again, i.e. app scrolled to "grey" position after launch, although 9 hours have passed since previous launch (according to app.log). Here are the [logs.zip](https://github.com/organicmaps/organicmaps/files/9228129/logs.zip). Logging has been enabled all the time since I created this issue, and archive has been manually created in Android\data right after reproducing the bug

biodranik commented

2022-08-04 06:50:45 +00:00

(Migrated from github.com)

@rtsisyk @vng why the old position is not ignored after 9 hours on Android?