#2253 Can't install a-gps file from huafetcher

Open
opened 2 weeks ago by cyrinux · 8 comments
cyrinux commented 2 weeks ago

Before proceeding further, please confirm the following:

Device information

  • Provide device name, manufacturer and similarity to other devices:
    amazfit gts 2e

  • Specify model and firmware version if possible:
    firmware 1.3.14.04

  • I try to update a-gps with huafetcher https://codeberg.org/vanous/huafetcher/releases

When I click the cep_pak.bin, I then see like on the README.md huafetcher doc, but for gps_alm.bin, I got a "File cannot be installed, device is not ready"

Any idea?

#### Before proceeding further, please confirm the following: - [x] I have read the [wiki](https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki), and I didn't find this device mentioned there - [x] I have searched the [issues](https://codeberg.org/Freeyourgadget/Gadgetbridge/issues), and I didn't find this device mentioned there - [x] Please make sure you have read and understood the [Codeberg Terms of Use](https://codeberg.org/codeberg/org/src/branch/master/TermsOfUse.md) #### Device information - Provide device name, manufacturer and similarity to other devices: amazfit gts 2e - Specify model and firmware version if possible: firmware 1.3.14.04 - I try to update a-gps with huafetcher https://codeberg.org/vanous/huafetcher/releases When I click the cep_pak.bin, I then see like on the README.md huafetcher doc, but for gps_alm.bin, I got a "File cannot be installed, device is not ready" Any idea?
cyrinux added the
device request
label 2 weeks ago
vanous commented 2 weeks ago
Collaborator

Make sure Gadgetbridge is connected to your watch before you start uploading the agps files.

These files take time to upload and time to process by the watch so while the watch shows the "updating gps data..." message, you cannot upload another file. Wait for the first file to finish first.

Make sure Gadgetbridge is connected to your watch before you start uploading the agps files. These files take time to upload and time to process by the watch so while the watch shows the "updating gps data..." message, you cannot upload another file. Wait for the first file to finish first.
cyrinux commented 2 weeks ago
Poster

Ha, so, i'm well connected before. And sadly, I see not message on the watch.
So is it really working? I doubt.
I got a flashing firmware progress bar in GB, and at a moment, this back on the screen with the "install" button but nothing on the watch screen. Just the watch is wake and i see my watchface when i click install.

Ha, so, i'm well connected before. And sadly, I see not message on the watch. So is it really working? I doubt. I got a flashing firmware progress bar in GB, and at a moment, this back on the screen with the "install" button but nothing on the watch screen. Just the watch is wake and i see my watchface when i click install.
vanous removed the
device request
label 2 weeks ago
vanous commented 2 weeks ago
Collaborator

I do not know if this is supported for the amazfit gts 2e, i am using this on the Amazfit Bip.

I do not know if this is supported for the `amazfit gts 2e`, i am using this on the `Amazfit Bip`.
cyrinux commented 1 week ago
Poster

Hi guys,
How can I help to debug this ? :-)

Hi guys, How can I help to debug this ? :-)
vanous commented 1 week ago
Collaborator

So, one file is sent well? gps_alm.bin takes in my case 3 seconds to upload but 12 seconds (in total with the upload) to process (i can see this on my screen). The cep_pak.bin takes 50 seconds to upload but 82seconds (in total) to process. During this time, no other file can be uploaded. So check if what you observe is the loading time or if the file is not loaded at all...

So, one file is sent well? gps_alm.bin takes in my case 3 seconds to upload but 12 seconds (in total with the upload) to process (i can see this on my screen). The cep_pak.bin takes 50 seconds to upload but 82seconds (in total) to process. During this time, no other file can be uploaded. So check if what you observe is the loading time or if the file is not loaded at all...
amazfit commented 6 days ago

@cyrinux @vanous

Same for me here with my GTR2:

  • gps_alm.bin (approx. 2.06KB)
    -> File cannot be installed, device not ready.

  • cep_pak.bin (approx. 59.39 KB)
    -> Install
    -> Flashing Firmware ...
    -> after approx. 7 seconds of flashing - ERROR: Problem with the firmware metadata transfer

@cyrinux @vanous Same for me here with my GTR2: - gps_alm.bin (approx. 2.06KB) -> File cannot be installed, device not ready. - cep_pak.bin (approx. 59.39 KB) -> Install -> Flashing Firmware ... -> after approx. 7 seconds of flashing - ERROR: Problem with the firmware metadata transfer
cyrinux commented 6 days ago
Poster

So, one file is sent well? gps_alm.bin takes in my case 3 seconds to upload but 12 seconds (in total with the upload) to process (i can see this on my screen). The cep_pak.bin takes 50 seconds to upload but 82seconds (in total) to process. During this time, no other file can be uploaded. So check if what you observe is the loading time or if the file is not loaded at all...

No I think for me any file upload really works, because, when I try to start a sport activities, the GPS always say me to update a-gps data.

> So, one file is sent well? gps_alm.bin takes in my case 3 seconds to upload but 12 seconds (in total with the upload) to process (i can see this on my screen). The cep_pak.bin takes 50 seconds to upload but 82seconds (in total) to process. During this time, no other file can be uploaded. So check if what you observe is the loading time or if the file is not loaded at all... No I think for me any file upload really works, because, when I try to start a sport activities, the GPS always say me to update a-gps data.
vanous commented 6 days ago
Collaborator

So, one file is sent well? gps_alm.bin takes in my case 3 seconds to upload but 12 seconds (in total with the upload) to process (i can see this on my screen). The cep_pak.bin takes 50 seconds to upload but 82seconds (in total) to process. During this time, no other file can be uploaded. So check if what you observe is the loading time or if the file is not loaded at all...

No I think for me any file upload really works, because, when I try to start a sport activities, the GPS always say me to update a-gps data.

I am not sure how the newer devices handle this, but this message comes up on the Bip (OG) too but you press OK and wait for a fix, then the activity starts.

As for uploading the a-gps files, i am not sure if this is really supported on these newer watches and if they have the same gps chip...

> > So, one file is sent well? gps_alm.bin takes in my case 3 seconds to upload but 12 seconds (in total with the upload) to process (i can see this on my screen). The cep_pak.bin takes 50 seconds to upload but 82seconds (in total) to process. During this time, no other file can be uploaded. So check if what you observe is the loading time or if the file is not loaded at all... > > No I think for me any file upload really works, because, when I try to start a sport activities, the GPS always say me to update a-gps data. > I am not sure how the newer devices handle this, but this message comes up on the Bip (OG) too but you press OK and wait for a fix, then the activity starts. As for uploading the a-gps files, i am not sure if this is really supported on these newer watches and if they have the same gps chip...
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.