This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ABORT_EPHEMERIS_REQUEST Error messages in Logfiles, EPO update broken

With the latest app version 4.16.1 these error messages are repeating endlessly in the app logfiles (you can download the app log in settings menu, diagnostics);

[FONT=courier new]Mar-19;6:02:57.801PM [DispatcherRead (D0:B7:FC:AF:B8:30)] D/GFDI#GpsEphemerisManager@dcb353b [D0:B7:FC:AF:B8:30] - ABORT_EPHEMERIS_REQUEST
Mar-19;6:02:57.802PM [DispatcherRead (D0:B7:FC:AF:B8:30)] D/GFDI#GpsEphemerisManager@dcb353b [D0:B7:FC:AF:B8:30] - Deleted /data/user/0/com.garmin.android.apps.connectmobile/files/downloads/3945602876_343608_epo.tmp
Mar-19;6:02:57.804PM [DispatcherRead (D0:B7:FC:AF:B8:30)] D/GFDI#GpsEphemerisManager@dcb353b [D0:B7:FC:AF:B8:30] - Remote device has requested the entire transfer to be aborted! Flush the transfer queue: [com.garmin.android.gfdi.gpsephemeris.GpsEphemerisManager$TransferItem@f87fb9f, (...)[/FONT]


This basically leads to the succeeding error "Remote device has requested the entire transfer to be aborted" which kills the upload of EPO.BIN to the watch.
Eventually, EPO.BIN is not updated on the watch, as this error process repeats endlessly preventing the prediction orbits for GPS to be updated.

Is anyone else having this problem? Is this a bug in the app or in the watch firmware or both?!

I'd try to approach Garmin support, but unfortunately, I have some doubts the first level support is able to understand these errors as they keep sending me standard replies from the FAQ...
  • Hello!

    So I need to get me a PC/Mac to update EPO?????

    If so, I sell my Fenix 5 and by another brand.

    Possibly not so saggy..

    Im tired waiting 10minutes out in the cold to get a gps signal lock..

    :-(

  • From my point of view this is purely an issue of the GCM app with certain phones / Android versions. With a super clean Android directly from Google but on Marshmallow 6.0.1 I was no longer able to update the EPO.

    Chaning to a newer phone with at least Android Oreo (v8) it worked again without any further issues.

    I strongly suggest to look here if you want to analyze any issues with that.