Autor Thema: Failed to connect, queued, but never sends  (Gelesen 854 mal)

cv27

  • Newbie
  • *
  • Beiträge: 18
  • Gerät: Samsung Galaxy S4/S5
  • Version: Android 5.0.1
Failed to connect, queued, but never sends
« am: 10.01.2017, 22:02:04 »
Samsung S5, Android 6.0.1, EgiGeoZone 2.5.8, using PathSense, sending to HS3 PHLocation plugin.


I have 2 phones using the exact same configuration, a Samsung S4 (Android 5.0.1) and S5 (Android 6.0.1).  The S4 works flawlessly.  The S5 most often than not fails.  The log always shows that EgiGeoZone tried to connect, failed and says the request is queued.  First, it is unclear why it cannot connect since cellular is always on; second, the queued message is never sent later.


Some forums have mentioned the battery saving features of Android 6 as the cause for EgiGeoZone not being able to send: this would be quite disturbing.  Can anyone confirm this as an issue?


Any other thoughts or debug suggestions?

Admin

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 759
    • EgiGeoZone
  • Gerät: Xiaomi Redmi Note 5, Samsung Galaxy Note 2, S4, S5, S2, S7
  • Version: MIUI 10.0 Global, Android 4.4, 5, 6, 7, 8, 8.1, 12, 13
Re: Failed to connect, queued, but never sends
« Antwort #1 am: 11.01.2017, 06:20:49 »
Zitat
Some forums have mentioned the battery saving features of Android 6 as the cause for EgiGeoZone not being able to send: this would be quite disturbing.  Can anyone confirm this as an issue?
Yes, the battery saving features of Android 6+ are a problem for networking in the background.
To disable for the App follow the steps:
Go to the phone Settings --> Battery Usage or App optimisation --> and disable the App optimisation for EgiGeoZone
or go to Smart manager and then Battery Usage or App optimisation --> and disable the App optimisation for EgiGeoZone

Zitat
second, the queued message is never sent later.
If the app can not send the queued request later and the event is triggered again for this zone, then the first queued request is deleted.
« Letzte Änderung: 11.01.2017, 07:12:53 von Admin »
Schöne Grüße
Egmont

cv27

  • Newbie
  • *
  • Beiträge: 18
  • Gerät: Samsung Galaxy S4/S5
  • Version: Android 5.0.1
Re: Failed to connect, queued, but never sends
« Antwort #2 am: 11.01.2017, 07:51:41 »
Thanks, found the setting, will test tomorrow.

cv27

  • Newbie
  • *
  • Beiträge: 18
  • Gerät: Samsung Galaxy S4/S5
  • Version: Android 5.0.1
Re: Failed to connect, queued, but never sends
« Antwort #3 am: 15.01.2017, 20:08:57 »
Forgot to come back and say thank you!  Long running problem solved.

Admin

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 759
    • EgiGeoZone
  • Gerät: Xiaomi Redmi Note 5, Samsung Galaxy Note 2, S4, S5, S2, S7
  • Version: MIUI 10.0 Global, Android 4.4, 5, 6, 7, 8, 8.1, 12, 13
Re: Failed to connect, queued, but never sends
« Antwort #4 am: 15.01.2017, 20:57:49 »
Thanks. Good to know it and I could help you.
Schöne Grüße
Egmont