Skip to content
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

Update to 0.2.2 looses all settings #78

Closed
u-hafner opened this issue Aug 4, 2020 · 4 comments · Fixed by #105
Closed

Update to 0.2.2 looses all settings #78

u-hafner opened this issue Aug 4, 2020 · 4 comments · Fixed by #105
Assignees
Labels
bug Something isn't working
Milestone

Comments

@u-hafner
Copy link

u-hafner commented Aug 4, 2020

Describe the bug
Updating the firmware to 0.2.2 from 0.2.0 looses all my keyboard and light settings.
After the update the color scheme is black ! and highlights keys pressed.
Before that it was light blue (as delivered) and some keys where adjusted to my language needs. Especially layer 1.

To Reproduce
Steps to reproduce the behavior:
Use a customized keyboard setting in firmware 0.2.0 and update firmware.

  • go to rainbow theme
  • press start for countdown.
  • press esc (before countdown ends)
  • blinking neuron
  • all black (?? unexpected but still pressing esc)
  • used mouse to click on bazecor to see if it still working. suddenly dialog closes which showed firmware upload.
  • release esc key
  • Bazecor was not able to show keyboard settings. Not working correctly anymore.
  • had to close and reopen bazecor.
  • All black lights. Keyboard settings resetted!

Expected behavior
Old keyboard settings stay.
OR: WARNING before flashing that they will be lost.
AND: possibility to save and reload old settings

Desktop (please complete the following information):

  • OS: Windows 10
  • Bazecor Version: 0.2.2
@u-hafner u-hafner added the bug Something isn't working label Aug 4, 2020
@AlexDygma AlexDygma self-assigned this Nov 12, 2020
@AlexDygma AlexDygma added this to the 0.2.5 milestone Nov 12, 2020
@AlexDygma AlexDygma linked a pull request Nov 12, 2020 that will close this issue
@AlexDygma
Copy link
Member

Hello @u-hafner !

Clearly your flashing process went badly, the question is why, i have fixed some flashing issues in the latest 0.2.3+ Bazecor version, so if you could follow up this issue with your experience with the updated bazecor versions to be sure the bug is no longer present we would be able to close this with certainty.

for the time being i'll close this either way, you can comment here and i'll reopen it if the issue persist.

@u-hafner
Copy link
Author

Hello @AlexDygma

The 0.2.4 version was the first version that actually flashed without problems (as I already had problems with 0.2.0). so great - thanks.

Would love to give you more feedback about the 0.2.4 but flashing was about it that worked. As I seem to have a hardware problem it took 1-2 min until my Raise stopped working. So I unplugged it again waiting for a response from Dygma - haven't got one yet.
I reached out to Dygma about my other problem already 3 times in the last 4 weeks. But no one answered yet.

@AlexDygma
Copy link
Member

Hello again @u-hafner !

I'm sorry to hear that, it's strange that you haven't got an answer from them as they usually don't take more than a day to reply to a new request.

Please contact them linking this GitHub issue so we can help you with your problem.

@u-hafner
Copy link
Author

@AlexDygma This issue is not related to my hardware problem. I'll try contacting them again.
I think this issue with flashing is closed for me. As it worked as expected. Thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants