owntracks / android

OwnTracks Android App

Home Page:http://owntracks.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

No Datatransfer in Mobile Phone network

Tuc69 opened this issue · comments

In Beta 2.5 all works fine in a WLAN at home.but when on the Road the queue grows and nothing ist transferred via LTE or 5G.
Settings are OK and all other Apps can transfer data.

There is a reason, you know, why issue trackers have a template like we do:

<!--
Thanks for asking a question or wanting to report an issue you've found.
Please delete this text and fill in the template below.
If unsure about something, just do as best as you're able.

Make sure to read http://owntracks.org/booklet/features/android/ for a list
of known issues and restrictions before posting. Thank you.
-->

* **App build number**: <!-- See About, then line under Changelog, Version -->
* **Android version**: <!-- See Device Preferences, System, About Phone, Android Version -->
* **Device**: <!-- Manufacturer and Device name -->
* **Installation source**: <!-- Did you install from Google Play, F-Droid, or manually from the APK? -->

Be advised I'm having to delete > 60 KB of garbage from your emails, and that they contain your address in the signature. The deleted comments remain on github; there's nothing we can do about it.

Also keep in mind that our Android dev speaks English. ;)

2.5.0 Beta 1 had an issue that could prevent data transfer. 2.5.0 Beta 2 fixes this. I'd suggest you update to the latest version and confirm this is still an issue, as I suspect it's already been addressed.

Your log cut off before 0646 (which is where I assume it gets interesting).

Might be a github limit. Can you attach as an attachment?

You seem to be sync'ing A LOT of contact locations back to the app! Have you tried turning that off to see if mobile data updates are fine? You might be reaching a timeout on the transfer (I have seen that when sending too large of image cards).

If it's only happening on the mobile data and not wifi, that sounds like more of a limit of the mobile carrier network than inside the app though.

2 questions:

  1. What does the connection state say when you're on mobile. Connecting? Timed out?
  2. Can you access your endpoint on mobile with your browser?

I'll try and add some more specific logging on http and cut a new beta later today.

What sort of endpoint is it the mobile app calling into?

@Tuc69 screenshots are not attached when responding by mail.

Screenshot_20240612-073404
here is the screenshot

I can't replicate this at all. Across multiple devices and network contexts (mobile and wifi), I don't see any issues with mobile data just "stopping".

commented
commented

When you say "beta 13" are you talking about Android 13 Beta? Those builds can be buggy and that might be your issue right there.

commented
commented

This might be an issue with the Motorola. Even though it's running Android, they all do their "twist" to the OS for their needs. If you ever have seen a Samsung, it doesn't remotely look the same as a pure Android that you see on a Pixel for example. They might be suspending apps when on mobile data to give better battery life numbers.

If you leave the OwnTracks app open in the foreground, this still happens when the screen is locked?

commented
commented

Do you get email notifications on those phones when they are locked as well? Maybe your mobile provider configures the phones to restrict background data transfers?

commented
commented

Which version of Android are you using? They did a change with the battery optimization menu in a recent Android 14 update:

  1. Select 'Settings' -> 'Apps' -> 'OwnTracks' - > 'App Battery Usage'.
  2. For Android 14 QPR1 and older with the three radio box selection, select the 'Unrestricted' radio button:
    Screenshot 2024-07-01 130813
  3. For Android 14 QPR2 and newer with the single 'Allow background usage' slider:
  • Select the slider.
  • Tap the text for 'Allow background usage'.
  • Select 'Unrestricted'.
    Screenshot 2024-07-01 130743
commented
commented

Stupid question, but have you re-installed 2.4.12 and confirmed that it still works as expected? Maybe your mobile provider did a change about the same time you installed 2.5.0.

commented
commented
commented

But have you tried uninstalling 2.5.0 and reinstalling 2.4.12 on those phones to see if it fixes it? That might give a clue on where the break point could be.

commented