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

feat: T-Deck w/ 2.6 MUI, Maps does not show fixed position when GPS is unavailable #6166

Open
antijingoist opened this issue Feb 27, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@antijingoist
Copy link

antijingoist commented Feb 27, 2025

Category

Other

Hardware

T-Deck

Firmware Version

2.6.0.0b106d4

Description

On T-Decks without a GPS, GPS set to NOT_PRESENT, and using fixed_position to manually set location:

Opening the Maps tab on the T-Deck defaults to Big Ben in UK, and assumes device position is at that location.

Device position is still sent out accurately, this only appears to affect the maps.

Expected:
Location set using fixed position would be what Maps shows.

Relevant log output

@antijingoist antijingoist added the bug Something isn't working label Feb 27, 2025
@caveman99
Copy link
Member

Which map do you mean? on the actual t-deck or in the andriod/ios app?

@antijingoist
Copy link
Author

The map on the T-Deck

@mverch67
Copy link
Collaborator

mverch67 commented Feb 27, 2025

The field fixed position is not / cannot be used for the MUI map. Instead the map has it's own persistent home position which can be set by long pressing the crosshair button and returned to by short pressing.

[Edit:] a resonable change that I can offer is that this home position is set in the device as fixed GPS position (in case a GPS is not present). Note: this fixed position field is write-only, cannot be read.

@mverch67 mverch67 changed the title [Bug]: T-Deck w/ 2.6 MUI, Maps does not show fixed position when GPS is unavailable feat: T-Deck w/ 2.6 MUI, Maps does not show fixed position when GPS is unavailable Feb 27, 2025
@antijingoist
Copy link
Author

If fixed_position coordinates are write-only, keeping a separate home location makes sense. I really did try to look into it, but didn't find anything with that information. 😁

Just to clarify:

  • fixed_position coordinates cannot be read using the API MUI uses. Is this something that could change in the future or doubtful?
  • the change you are offering, is this to set the fixed_position field to the home position when you long-press the crosshairs? ie: "No GPS detected, set your position" type of thing? Usability wise, it seems like a great idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants