Device drop out / appear offline

Hi,

I'm running a self-hosted instance. I noticed that Android Phones loose connectivity after a while (10-30mins) and do not submit positions anymore. The GUI does not show these devices as offline.

• This concerns a variety of phones (Pixel 9, Pixel 3 XL, Noika 7.2, Pixel 7a, Core Z5, Oneplus A6003, Galaxy Note 10) and Android versions (every phone has latest stock).
• This happens with phones having solely a WLAN uplink as well as with phones having only a cellular uplink.
• The phones do not reconnect and remain offline.
• I tried to disable all Battery Optimization. Chargers were attached all the time. I enable to stay awake in the Android debugging options.
• All phones are on my desk all time.
• The application does not show any error. Due to the screen being awake, I can toggle the background swtich all the time. When re-toggling, the phone continues to submit data.
• Although offline Buffering is enabled, new positions are not submitted when the devices submit positions to the server again.
  The positions are lost.
• The log is inclusive. When I click "Status" I only find entries with timestamps at times, when the device was submitting data. Hitting the refresh button doesn't help.

What can be wrong here? How can I keep traccar logging?

Many thanks in advance,
yanosz

If devices are on your desk, then won't be sending data because they're stationary.

Thanks for your response.

Is there a way to force sending positions for debugging?

You can enable heartbeat.

Thanks - I didn't find that one. Will setting the distance to '0' have the same effect?

No, it doesn't.

https://www.traccar.org/client-configuration/

Many thanks for your feedback., I read the client configuration multiple times, but struggled a bit to understand it. Some UX feedback - should I put it into a ticket?

• The webapp says "online" when the device is submitting data. However, this suggest to a user that a device is connected to the server. I was suprised that this means that the device is moving. From an UX perspective I assumed that the devices dropped out. The webpage could be more explaining, here
• A status in the Android App could be helpful. I didn't expect to see a debugging log. Especially, not submitting positions due to not moving might be helpful.
• One cannot configure a heartbeat smaller than 60 seconds - this minimum is not explained.
• Even after reading the documentation many times, it is not clear to me what a distance of "0" actually means and why this is different from the hearbeat model.

You should also read this:

https://github.com/transistorsoft/flutter_background_geolocation/wiki/Philosophy-of-Operation

Thanks!