Map stuck for many seconds while driving #2030
Labels
No labels
Accessibility
Accessibility
Address
Address
Android
Android
Android Auto
Android Auto
Android Automotive (AAOS)
Android Automotive (AAOS)
API
API
AppGallery
AppGallery
AppStore
AppStore
Battery and Performance
Battery and Performance
Blocker
Blocker
Bookmarks and Tracks
Bookmarks and Tracks
Borders
Borders
Bug
Bug
Build
Build
CarPlay
CarPlay
Classificator
Classificator
Community
Community
Core
Core
CrashReports
CrashReports
Cycling
Cycling
Desktop
Desktop
DevEx
DevEx
DevOps
DevOps
dev_sandbox
dev_sandbox
Directions
Directions
Documentation
Documentation
Downloader
Downloader
Drape
Drape
Driving
Driving
Duplicate
Duplicate
Editor
Editor
Elevation
Elevation
Enhancement
Enhancement
Epic
Epic
External Map Datasets
External Map Datasets
F-Droid
F-Droid
Fonts
Fonts
Frequently User Reported
Frequently User Reported
Fund
Fund
Generator
Generator
Good first issue
Good first issue
Google Play
Google Play
GPS
GPS
GSoC
GSoC
iCloud
iCloud
Icons
Icons
iOS
iOS
Legal
Legal
Linux Desktop
Linux Desktop
Linux packaging
Linux packaging
Linux Phone
Linux Phone
Mac OS
Mac OS
Map Data
Map Data
Metro
Metro
Navigation
Navigation
Need Feedback
Need Feedback
Night Mode
Night Mode
NLnet 2024-06-281
NLnet 2024-06-281
No Feature Parity
No Feature Parity
Opening Hours
Opening Hours
Outdoors
Outdoors
POI Info
POI Info
Privacy
Privacy
Public Transport
Public Transport
Raw Idea
Raw Idea
Refactoring
Refactoring
Regional
Regional
Regression
Regression
Releases
Releases
RoboTest
RoboTest
Route Planning
Route Planning
Routing
Routing
Ruler
Ruler
Search
Search
Security
Security
Styles
Styles
Tests
Tests
Track Recording
Track Recording
Translations
Translations
TTS
TTS
UI
UI
UX
UX
Walk Navigation
Walk Navigation
Watches
Watches
Web
Web
Wikipedia
Wikipedia
Windows
Windows
Won't fix
Won't fix
World Map
World Map
No milestone
No project
No assignees
2 participants
Due date
No due date set.
Dependencies
No dependencies set.
Reference: organicmaps/organicmaps-tmp#2030
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While I was driving in Taichung (Taiwan), the map was continuously getting stuck for many seconds. It seemed like an app has very heavy load (a lot of rendering taking place?), e.g. sometimes after few seconds new label popped up on the screen or it took time to zoom out.
The GNSS location update from the phone was fine as guidance panel with next instruction was updated smoothly (see mismatch on screenshot).
When I drove out of the city, the problem was not visible. I have used the app in few other cities in Taiwan (e.g. Kaohsiung, Tainan, Chiayi) and it is the first time I have experienced this issue. I have updated the app and the map to the latest but the problem was still there.
As you can see in the screenshot, there is a lot of house numbers. Could the app stop showing house numbers in driving mode? Maybe that would help.
System: Android 8
Phone: Asus ZenFone 4 (ASUS_Z01KD)
House numbers could be unrelated, but we already discussed that they pollute the screen too much. @pastk @vng let's try to remove them for vehicle (navigation) style for all zooms except the last one? I'll test it on a branch.
IMHO, house numbers is the key information in city navigation mode. Is there a discussion about them?
There was a discussion here #1935 recently
ATM house numbers are displayed starting at z16.
Do we know to which vehicle speed this zoom level corresponds? (when auto-zoom is on)
When navigating house numbers are usually needed when very close to destination and slowing down to e.g. stop by a particular building number.
So maybe makes sense to display them starting at ~20-30kph speed. What zoom level this will be?
Discussion makes sense in general map view. But my point is about Navigation mode. Now they draw in 17-19 and I think its good.
Navigation mode uses z16- also. There are two sets of rules:
I guess above is for standalone address tags not attached to buildings.
And this is the case for buildings with addresses attached.
Ah, yes. So they definitely should be equal. I propose to make [addr:housenumber][addr:street] starting from z17 like buildings in Navigation Mode.
My proposal is to draw building addresses from z18 in navigation mode and see how it helps to clear the map and see more important names. I'm ready to test it.
As I showed in organicmaps/organicmaps#1656, house numbers are only part of the issue. If you are using bike or foot navigation in a city, all the POIs shown destroy the performance especially when using perspective view. Ideally the map engine should take into account the perspective and the zoom level to decide when to show POIs or house numbers.
Can you tell at which speed roughly house numbers appear on the map ATM?
BTW atm on the "regular" map we prefer to display building names if they exist, however in navigation mode house numbers are preferred.
For me a building name is a better navigation landmark than its house number, however a building name will take much more screen space...
@tomekem-gh do you store maps on SD card? If yes, can you please try to move the downloaded map(s) to the internal memory (or better to delete them, set storage to internal device location, and redownload again), and try to reproduce the bug?
[Slow/counterfeit/fake/wore off] SD cards very often cause lags according to our user reports.
No, it's on internal memory, I don't have SD card.
I cannot reproduce the problem right now as I don't live in the city in question (and I might not be there any time soon).
What are my options? Would reproducing it with fake GPS provider do? Would logs help you?