Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Geocoded location unknown on OnePlus 7T until it is rebooted but goes back to unknown after a short period of time
See original GitHub issueHome Assistant Android version: 2022.1.1-full Android version: 11 Phone model: OnePlus 7T Home Assistant version: core-2021.12.10 Home Assistant OS 7.2 supervisor-2022.01.1 stable Last working Home Assistant release (if known):
Description of problem: Geocoded location is only available after the phone is rebooted. It stays there for an hour or so and then goes to unknown. Other Android phones are OK. I have seen this reported somewhere in the community forums again with OnePlus but can’t recall what model, so it may be OnePlus related. Traceback (if applicable, to get the logs you may refer to: https://companion.home-assistant.io/docs/troubleshooting/faqs/#android-crash-logs):
Screenshot of problem:
Additional information: I have followed all suggestions I could find, turning off and on location services, enabling high accuracy, etc. Nothing helps. Once the phone is rebooted, geocoded location is available for an hour and then disappears. Other Android phones are OK like Samsung A22, Huawei P10 Lite.
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yep, agreed. I’m OK to close this.
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Daniel Shokouhi @.> Sent: Tuesday, February 22, 2022 6:10:21 PM To: home-assistant/android @.> Cc: dnedeltchev @.>; Author @.> Subject: Re: [home-assistant/android] Geocoded location unknown on OnePlus 7T until it is rebooted but goes back to unknown after a short period of time (Issue #2225)
I do, but I never had these problems with LOS.
This points to a bug in the official ROM, and as we see in the link they already accepted the issue and notified their development team. Very specific testing done there and that is indeed the API we use
https://github.com/home-assistant/android/blob/master/app/src/full/java/io/homeassistant/companion/android/sensors/GeocodeSensorManager.kt#L79
I think we may need to close this issue until we hear back from One Plus on what their development team said because this bugs behavior mimics the post in their forums.
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/android/issues/2225#issuecomment-1048074143, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AONHCL3ULHDTB6UTKN7K55LU4PGQ3ANCNFSM5NKTZZ2A. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
This points to a bug in the official ROM, and as we see in the link they already accepted the issue and notified their development team. Very specific testing done there and that is indeed the API we use
https://github.com/home-assistant/android/blob/master/app/src/full/java/io/homeassistant/companion/android/sensors/GeocodeSensorManager.kt#L79
I think we may need to close this issue until we hear back from One Plus on what their development team said because this bugs behavior mimics the post in their forums.