home-assistant / home-assistant/android

High accuracy mode works well, but doesn't recover after bad connectivity for a while

Open
#5,077 6 comments 0 reactions 0 assignees View on GitHub
bug location-tracking question
Dominant language
Kotlin
Stars
3.9k
Forks
1.1k
Avg merge
1d 12h
Merged PRs (30d)
81

Description

**Home Assistant Android app version(s):**

2025.1.2-full

**Android version(s):**

15

**Device model(s):**

Pixel 7 Pro

**Home Assistant version:**

2025.3.0 and earlier - monitored this issue for the last 6 months

**Last working Home Assistant release (if known):**

n/a

**Description of problem, include YAML if issue is related to notifications:**

Using high accuracy mode works really well and battery draining is acceptable. This is true for 99% of our use cases.

But sometimes we experience extreme battery drain and the device gets really hot, all within half an hour. I was trying to find out what exactly is triggering this behaviour and after a 6-month period, I'm pretty certain that I can report about a pattern that seems to be responsible for this:

When the device enters an area with weak or no radio, it can't send location data back to the server. If it gets back to good signal fairly quickly, i.e. within a minute or so, then it recovers from that situation and we don't notice an issue. But if the device remains in bad signal area for a little longer, like 15 or 20 minutes, it won't recover from that situation and starts draining the battery.

In such scenarios, we have to force the companion app to stop completely and start it again manually. But if you're not fast enough, your battery is already on such a low level, that it doesn't really help.

**Companion App Logs:**

```

```

**Screenshot or video of problem:**

**Additional information:**

I'm happy to provide more detail and work together with maintainers to find the real reason for the issue. For now I was hoping that the described pattern would probably ring a bell and you may immediately say, we know where this is coming from and can fix it. Of course, please let me know otherwise and we then need to somehow get deeper into stuff.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.