Update of new watch consistently fails

[bitreaper]

Hi,

I was wondering if others had run into this issue, and if there's any suggestions on how to fix it.  Need to see if there's something I can do before having to RMA the watch.

Preliminary details:

• I bought the dev kit
  
• The sealed watch does not make it through the first update step (upgrade of infinitime from stock 0.7.1 to 1.0)
  
• The dev watch does make it through the update list.
  

I have attempted:

• Following instructions on the update wiki page
  
• using GadgetBridge to upload initially
  
• uninstalling GadgetBridge while using nRF Connect, to ensure there's no conflict
  
• most attempts used nRF Connect, latest version 4.24
  
• Connecting, bonding, changing LE phy from
  
• Trying from two different phones, a Galaxy 20 Note (first attempts) finally going to Galaxy 8 Note.  Same result.
  

Symptoms of each try:

• Gets through some percentage of the load, random each time.  Sometimes 75%, sometimes 18%.
  
• Connection drops, nRF Connect attempts to restart it
  
• watch bluetooth is offline until I reset it with the 8-second-button-press reboot trick.
  
• until retry, watch isn't in scan list
  

It also just occurred to me that while I had the watch charging I was playing with it attached to GadgetBridge, and noticed that some notifications got through, but then it dropped off being attached.  I wonder if the bluetooth transceiver is at fault and not a software glitch.

Thoughts from the community?

UPDATE:  I was finally able to get the watch to update 100%, and then the following updates to the bootloader and rescue went OK as well.  In the true vein of that phrase "definition of insanity is doing the same thing over again and again expecting different results" I tried again.  I think the only thing I changed was letting nRF Connect pick the PHY.  It was glacial to update though compared to the dev watch.  Since then, It hasn't lost bluetooth connectivity to my phone running GadgetBridge.  I'm mostly interested in WASP-OS, so I'll be attempting that later today.  We'll see how that goes.

[atomdmac]

I received my developer kit yesterday and had the exact same experience when updating the firmware.

1. Connect to the watch via Gadget Bridge
2. Download and open the DFU package (I used the Seafile client to download it and open it)
3. Proceed with installation in Gadget Bridge by tapping the `Install` button
4. Upload commences.  A progress bar appears on the phone and the watch
5. At some random point during the upload the `Upload failed` message appears on the phone and `Error` on the watch.

After every failure, I had to reset the watch in order for Gadget Bridge to connect to the watch again.  If I repeat these steps enough times, I eventually get lucky and the upload completes successfully. 

I ended up having to do this again today because I reset my watch and it reverted to the stock 0.7.1 firmware.  I have no idea what's causing this but I'm glad I'm not the only one that has experienced it.  I thought I was going crazy!

My setup:
- Pixel 2
- Gadget Bridge 0.58.1
- Upgrading firmware from 0.7.1 to 1.2.0

[atomdmac]

I've just tried this a few times using nrfConnect as well (from the same phone) and I'm hitting the same issue.  I guess that means it's either an issue with my phone or with my PineTime(s).  I'm not sure how to determine which, though.  I'm looking around to see if there's any place where errors are being dumped to logs etc. but haven't been able to find anything so far.

[atomdmac]

Almost immediately after my last post I found the logs in nrfConnect. They seem to indicate that a timeout is occurring but I'm not sure whether it's happening on the phone or watch side (or what is causing it).

Here are what (I think) are the relevant portions of the log:

```
...
A 15:54:48.974 [DFU] Initialize DFU Parameters completed
I 15:54:49.922 [DFU] Notification received from 00001531-1212-efde-1523-785feabcd123, value (0x): 10-02-01
A 15:54:49.922 [DFU] Response received (Op Code = 2, Status = 1)
V 15:54:49.922 [DFU] Writing to characteristic 00001531-1212-efde-1523-785feabcd123
D 15:54:49.922 [DFU] gatt.writeCharacteristic(00001531-1212-efde-1523-785feabcd123)
I 15:54:50.009 [DFU] Data written to 00001531-1212-efde-1523-785feabcd123, value (0x): 03
A 15:54:50.009 [DFU] Receive Firmware Image request sent
A 15:54:50.036 [DFU] Uploading firmware...
V 15:54:50.036 [DFU] Sending firmware to characteristic 00001532-1212-efde-1523-785feabcd123...
D 15:54:56.280 [Callback] Connection state changed with status: 8 and new state: DISCONNECTED (0)
E 15:54:56.280 Error 8 (0x8): GATT CONN TIMEOUT
I 15:54:56.280 Disconnected
E 15:54:56.307 [DFU] Device has disconnected
D 15:54:56.307 [DFU] gatt.disconnect()
D 15:54:56.307 [DFU] gatt.close()
D 15:54:56.319 [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED
D 15:54:56.334 [DFU] [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED
V 15:54:56.334 [DFU] DFU service started
I 15:54:56.334 [DFU] Firmware file opened successfully
D 15:54:56.334 [DFU] wait(1000)
D 15:54:57.323 [DFU] wait(1000)
V 15:54:58.323 [DFU] Connecting to DFU target...
D 15:54:58.361 [DFU] gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferredPhy = LE_1M | LE_2M)
...
```

[atomdmac]

Good news! It appears that the connection stability issues during upgrade may have been due to a bug in the 0.7.1 software.

After upgrading my dev/unsealed watch to 1.2.0, I've been able to upload the same 1.2.0 image to the watch 4x in a row without any issues. I have basically no experience with the inner workings of the software so my diagnosis here is probably naive and simplistic _but_ it does seem that the OTA upload connection is much more stable after the 1.2.0 upgrade.

To anyone else experiencing this issue: I would suggest using nrfConnect to perform the initial 0.7.x -> 1.2.x update as it will automatically connect+retry the upload after you reset the watch. It will _eventually_ work but you might have to keep at it for awhile.

[feketej]

It is definitely an Android or nRF connect app bug, because I was able to upload firmware using my pinephone (mobian) with siglo app.
So te problem is noth with the pinetime device.