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

[BUG] GPS Timeout is too short #78

Closed
a-leithner opened this issue Aug 18, 2024 · 5 comments
Closed

[BUG] GPS Timeout is too short #78

a-leithner opened this issue Aug 18, 2024 · 5 comments
Milestone

Comments

@a-leithner
Copy link

Describe the bug

I'm trying to use the app on a Fairphone 3+ with Lineage OS 21 without Google Services. After enabling location services and granting the location permission, the app starts up but fails almost immediately with the message "No GPS signal found".

Testing with "My Location" from F-Droid, it takes indeed a couple of minutes for getting a position (waiting for enough satellites with enough signal strength to become available).

This bars me from using the app. (Logging in on desktop also doesn't fix it for me, though that's a different issue.)

To Reproduce

Steps to reproduce the behavior:

  1. Open the app
  2. Wait for about one second
  3. Error message is displayed
  4. Search page displays "no more users" message

Expected behavior

The app waits until an actual GPS signal could be found by the device and then reads the location.

Screenshots

N/A

Device (please complete the following information):

  • OS: Android
  • OS version: Lineage OS 21
  • Device: Fairphone 3+

Native Application:

  • Version 1.11.0
  • Origin F-Droid

Web application

N/A

Additional context

N/A

@a-leithner
Copy link
Author

Ideally, the app shouldn't need to rely on GPS location whatsoever. Personally, I deeply object reading GPS data for any purpose (other than emergencies).

IMHO, Heavens Above has a pretty elegant, three-fold solution to manual position entry. Displaying a Map (provided by OpenStreetMap, just like HA) and letting users pinpoint their approximate location should be pretty straight forward, shouldn't it?

Manually entering lat/long would also do it for me, since I can gather that info from apps that actually wait for the location data to be available. What3Words or LocationIQ could be nice to have, alternatively, but aren't free to use at a scale.

@a-leithner
Copy link
Author

Also, what happened to manual location entry as teased in another issue?

@Nonononoki
Copy link
Contributor

The problem is that I havent found a good react-native library where the user can choose their own location. Got any suggestions?

Development speed is kinda low at the moment as I have to deal with personal matters. Feel free to submit pull requests tho!

@a-leithner
Copy link
Author

Thanks for the fast response. Sadly, I'm a Java Developer by trade and have no experience whatsover with React nor React Native.

As for the map-based idea, after a little googling I found this Medium article which seems to implement just this. Though I'm usure if that also applies to React Native. If it doesn't it could be possible to implement using this repo.

Then there's also this from AirBnB which might have pluggable providers though the README doesn't communicate this clearly.

The "cheapest" solution so far would probably be to just provide manual lat/long entry fields, as a "quick" fix/workaround, as I think I've seen multiple reports of location problems in the backend repo.

Best wishes

@Nonononoki Nonononoki added this to the 2.0 milestone Dec 25, 2024
@Nonononoki
Copy link
Contributor

Implemented it 9034ec8 and will be available once 2.0 releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants