Avatar for msdeibel

msdeibel

Member since Feb 2020 • Last active Jul 2022
  • 12 conversations
  • 27 comments

Most recent activity

    • 9 comments
    • 1,517 views
  • in Bangle.js
    Avatar for msdeibel

    I tried about 30-40 times during the last few days, also with different firmwares. Mostly with the edge builds, hoping that the package content would make a difference.

    Just tried again and with the 2.12.28 release it worked.
    I used an Android 10 phone and the nRF Toolbox app.

    Happy to have the little bugger alive again :D

  • in Bangle.js
    Avatar for msdeibel

    I tried from a Windows 10 PC and an Android 10 mobile.

  • in Bangle.js
    Avatar for msdeibel

    I bricked my Bangle 2 but still hope there is a way to recover it.

    After updating to 2.12.16 the message displaying didn't work for me so I tried to go back to an earlier version and might have had an update error there.

    That didn't work out and I got an error. I tried down to version 2.10, all the same.
    During the last three days I also tried to get the latest edge builds on in but to no avail.

    I get into the DFU Start without problems and am presented with

    DFU Start
    BTN1 = REBOOT
    CONNECT
    

    I then start the flashing operation, wich goes up to 99% and then hangs, with the watch showing

    DFU Start
    BTN1 = REBOOT
    CONNECT
    ERROR
    

    After about 30s the watch reboots by itself an the presents the following message

    SW RESET
    DFU2V12
    
    CHECK STORAGE
    NO NEW FW
    BANK0 INVALID
    BTN1 = REBOOT
    

    Is there any way to get another working FW back onto the Bangle 2 or does it need recycling?

    I tried uploading the FW with the IDE Flasher and the nRF Toolbox.

  • in Bangle.js
    Avatar for msdeibel

    This has been solved by removing the Bangle2 from the "Paired Devices" list in the phone and disabling the Discovery and pairing -> Ignore connected devices (option names translated from German) option in Gadgetbridge.

  • in Bangle.js
    Avatar for msdeibel

    Objection denied

    My objection was denied by Geman customs on the grounds that the IOSS number was not included in the customs announcement(?) ( I guess that's where Royal Mail fucked it up). It's not enough to just have the number on the receipt and/or packaging slip.

    They made it clear that the only way to handle this is to go through the seller/sender.

    Pretty sad.

  • in Bangle.js
    Avatar for msdeibel

    If you had to pay the additional VAT in Germany you can reclaim it from customs.

    What you need is a "Abgabenbescheid" which you can get at
    https://www.dhl.de/de/privatkunden/hilfe­-kundenservice/formulare/abgabenbescheid­-anfordern.html

    Requested on 19-Nov-2021

    Received on 23-Nov-2021

    Then, since we are in Germany, you have to obey ... erm ... I mean follow the process:
    https://www.zoll.de/DE/Fachthemen/Zoelle­/Abgabenerhebung/Erlass-Erstattung/Verfa­hren/verfahren_node.html#doc298948bodyTe­xt2

    Objection sent 23-Nov-2021

    Still being handled by the customs office - haven't heard back 04-Dec-2021

    With luck you can also get your 6EUR fee from DHL back using this link (once you have the "Abgabenbescheid").
    https://www.dhl.de/nachentgelt

    Important
    The label on my package says that there is a one month deadline for this.
    So be quick or be screwed (well not totally, since Gordon is so nice to reimburse you, but anyway).

    I can't yet say if this works, since I've only gotten around step 1 before writing up this post.

    Source: https://www.paketda.de/zoll/zoll-reklami­eren.html

    Objection denied on 17-Jan-2022 (see post below)

    Updates
    Action dates added

  • in Bangle.js
    Avatar for msdeibel

    Hi all,

    I have a problem connecting the Bangle 2 to Gadgetbridge on my Fairphone 3.

    It looks like Gadgetbridge does not find the device, but that is apparently not the case as the log contains the following lines:

    20:30:49.972 [main] WARN  n.f.g.i.GBDeviceCandidate - no cached services available for (unknown): 11:96:F1:C6:80:C0 (UNKNOWN)
    20:30:50.013 [main] WARN  n.f.g.a.DiscoveryActivity - Bangle.js 14a7: 62
    20:30:50.016 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Bangle.js 14a7, C8:1D:A7:B8:14:A7
    20:30:50.016 [main] DEBUG n.f.g.a.DiscoveryActivity -   supports uuid: 6e400001-b5a3-f393-e0a9-e50e24dcca9e
    20:30:51.374 [main] WARN  n.f.g.a.DiscoveryActivity - Bangle.js 14a7: 62
    20:30:51.378 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Bangle.js 14a7, C8:1D:A7:B8:14:A7
    20:30:51.378 [main] DEBUG n.f.g.a.DiscoveryActivity -   supports uuid: 6e400001-b5a3-f393-e0a9-e50e24dcca9e
    20:30:52.505 [main] WARN  n.f.g.a.DiscoveryActivity - Bangle.js 14a7: 62
    20:30:52.509 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Bangle.js 14a7, C8:1D:A7:B8:14:A7
    20:30:52.510 [main] DEBUG n.f.g.a.DiscoveryActivity -   supports uuid: 6e400001-b5a3-f393-e0a9-e50e24dcca9e
    20:30:52.886 [main] WARN  n.f.g.a.DiscoveryActivity - Bangle.js 14a7: 62
    20:30:52.889 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Bangle.js 14a7, C8:1D:A7:B8:14:A7
    20:30:52.890 [main] DEBUG n.f.g.a.DiscoveryActivity -   supports uuid: 6e400001-b5a3-f393-e0a9-e50e24dcca9e
    

    So it looks as if only displaying the device in GB's list is problematic.

    I already updated the watch to FW 2.10.223 but that didn't help.

    Is that something that the FW can change or rather an issue that needs to be fixed in GB?

    Cheers
    MSD

Actions