omi icon indicating copy to clipboard operation
omi copied to clipboard

Fix firmware update

Open kodjima33 opened this issue 11 months ago • 16 comments

Our dev Kit 2 devices are shipped with 2.0.2 firmware

Problem: no one wants to do manual firmware update and auto-update doesn't work for 2.0.2

Problem2: people don't know they can update firmware

Todo

  • [ ] Fix auto-update for 2.0.2 update - autoupdate should work ($400)
  • [ ] Add auto-update sign as soon as device connected ($100)

kodjima33 avatar Feb 08 '25 06:02 kodjima33

/bounty $500

kodjima33 avatar Feb 09 '25 01:02 kodjima33

💎 $500 bounty • omi

Steps to solve:

  1. Start working: Comment /attempt #1767 with your implementation plan
  2. Submit work: Create a pull request including /claim #1767 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to BasedHardware/omi!

Add a bountyShare on socials

Attempt Started (GMT+0) Solution
🟢 @asr2003 Feb 9, 2025, 3:05:28 AM WIP

algora-pbc[bot] avatar Feb 09 '25 01:02 algora-pbc[bot]

@kodjima33 I would like to take this issue

/attempt #1767

Algora profile Completed bounties Tech Active attempts Options
@asr2003 10 bounties from 4 projects
Rust, Typescript,
Go & more
Cancel attempt

asr2003 avatar Feb 09 '25 03:02 asr2003

@addbounty $500

andrewgazelka avatar Feb 11 '25 03:02 andrewgazelka

banner button

Make a Draft PR early so others can see you are working on it! To automatically create one:

# Using npx (installed if you have NodeJS/npm)
npx bountybot solve BasedHardware/omi#1767

Join Our Discord to connect with other bounty hunters and get help.

When merged, you will receive the bounty!

addbounty avatar Feb 11 '25 03:02 addbounty

Issue still open, I haven't seen any demos

kodjima33 avatar Feb 12 '25 00:02 kodjima33

Will draft it in weekend

On Wed, 12 Feb, 2025, 5:38 am Nik Shevchenko, @.***> wrote:

Issue still open, I haven't seen any demos

— Reply to this email directly, view it on GitHub https://github.com/BasedHardware/omi/issues/1767#issuecomment-2652335917, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGXZB6G3GI6PMLKOYO3O5IT2PKGI7AVCNFSM6AAAAABWXLGEWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJSGMZTKOJRG4 . You are receiving this because you were mentioned.Message ID: @.***>

asr2003 avatar Feb 13 '25 17:02 asr2003

Just received mine—shipped a month ago with firmware version 2.0.2.

Updated successfully without any issues using the instructions here: Discord Link.

The only inconvenience was the lack of direct links in the app to copy and paste onto a laptop, which forced me to check Discord for details.

I’ve submitted a feature request to improve this UX: #1808

skywinder avatar Feb 14 '25 12:02 skywinder

@skywinder wow your github looks amazing! Can you help with this by any chance? This is such a big pain

kodjima33 avatar Feb 14 '25 23:02 kodjima33

@kodjima33
Thanks! I’ve been an open-source enthusiast and builder since 2010, and I'm excited to dive into this project. :)

Regarding the issue, I'm currently exploring the codebase, and I just got my Omi DK2 yesterday, which I’m really looking forward to experimenting with!

Let’s keep an eye on the situation since two others have committed to resolving this. If we don’t see any progress by next week, I’ll step in and do my best to tackle it!

skywinder avatar Feb 15 '25 00:02 skywinder

More context:

The current pain is that the OTA update does not work if the user plugs their device into a USB cable(either to a charger or a computer).

Without USB cable, everything works well.

--

My comment on the previous investigation: https://github.com/BasedHardware/omi/issues/1682#issuecomment-2594116010

yes sir, actually the brick mean *the device can not boot after performing the ota updates.

i also try with/without the usb connected. the result is: without the usb connected, the ota updates work fine. the device can boot with any versions, e.g. ota updates from 2.0.2 to 2.0.8 or 2.0.4 to 2.0.7 and so on.

so i guess there're something confusing the bootloader's state between the ota updates and serial updates when the usb is connected.

ofc we can also try disabling all usb interrupts while performing the ota updates. but i dont think it's a smart move.

i'm a nerd, as you know, i love deep-diving into issues. but the time is not super generous right now haha.

anw, i'm super happy when you're here and diving into this with me. looking fwd sir.

--

My note on the OTA updates 2.0.8: https://github.com/BasedHardware/omi/releases/tag/Omi_DK2_v2.0.8

Image

--

The PR supports DK2's OTA updates https://github.com/BasedHardware/omi/issues/1393

beastoin avatar Feb 15 '25 02:02 beastoin

hope this helps and, nice to meet @skywinder /

beastoin avatar Feb 15 '25 02:02 beastoin

https://github.com/user-attachments/assets/66a65f2c-cb5e-46d4-a037-ef82b156045c

https://github.com/user-attachments/assets/5e924af6-f305-4d9b-be24-32881367594b

beastoin avatar Feb 23 '25 10:02 beastoin

https://github.com/user-attachments/assets/e3484d1f-dfda-4e33-ad17-8b92fc5c1db2

beastoin avatar Feb 24 '25 05:02 beastoin

next:

  • [x] display a new popup at the home page to inform users about new firmware version, a more aggressive way to encourage firmware updates.
  • [x] add a new checkbox such as, I have disconnected the USB, i understand that a USB connection might brick my device.

beastoin avatar Feb 25 '25 03:02 beastoin

https://github.com/user-attachments/assets/6fd601a5-d6eb-4c47-9ce6-a04047ce41da

beastoin avatar Mar 01 '25 11:03 beastoin