-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix firmware update #1767
Comments
/bounty $500 |
💎 $500 bounty • omiSteps to solve:
Thank you for contributing to BasedHardware/omi! Add a bounty • Share on socials
|
@kodjima33 I would like to take this issue /attempt #1767
|
@addbounty $500 |
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! |
Issue still open, I haven't seen any demos |
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
<#1767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGXZB6G3GI6PMLKOYO3O5IT2PKGI7AVCNFSM6AAAAABWXLGEWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJSGMZTKOJRG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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 wow your github looks amazing! |
@kodjima33 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! |
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: #1682 (comment)
-- My note on the OTA updates 2.0.8: https://github.com/BasedHardware/omi/releases/tag/Omi_DK2_v2.0.8 ![]() -- The PR supports DK2's OTA updates #1393 |
hope this helps and, nice to meet @skywinder / |
ota_updates_w_instruction_steps_and_the_indicator_1.mp4ota_updates_w_instruction_steps_and_the_indicator_2.mp4 |
ota_updates_with_instructions_demo_2.mp4 |
issue: #1767 ## deploy plan - [ ] deploy backend - [ ] deploy app - [ ] update ota_update_steps to github release ``` <!-- KEY_VALUE_START release_firmware_version:2.0.8 minimum_firmware_required:2.0.5 minimum_app_version:1.0.55 minimum_app_version_code:242 ota_update_steps:no_usb,battery,internet KEY_VALUE_END --> ```
next:
|
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
The text was updated successfully, but these errors were encountered: