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

Release 0.4.4-beta #169

Merged
merged 24 commits into from
Jul 26, 2023
Merged

Release 0.4.4-beta #169

merged 24 commits into from
Jul 26, 2023

Conversation

tsterbak
Copy link
Member

@tsterbak tsterbak commented May 29, 2023

This Release adds:

  • Samsung A5 2017 (a5y17lte) thanks to @Gredin67
  • Support for device code beyond2 for Samsung Galaxy S10+.
  • Support for device code evert_n for Motorola Moto G6 plus.
  • Add config file for Samsung Tab S2 gts210vewifi T813 thanks to @freechelmi
  • a "request support for device" button if no config for the device code is found

Fixes:

  • Update the unlocking instructions for FP3/4 and add
    fastboot_unlock_critical command.

Changes:

  • Set a min width/height for the window to solve basic responsiveness issues

Gredin67 and others added 2 commits May 29, 2023 20:08
@tsterbak tsterbak added this to the Release Beta-Version 0.4.4 milestone May 29, 2023
@tsterbak tsterbak self-assigned this May 29, 2023
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@Gredin67
Copy link
Contributor

Gredin67 commented Jun 5, 2023

Note that I did not test with LineageOS (but I could)

@MagicLike
Copy link
Member

MagicLike commented Jun 5, 2023

Note that I did not test with LineageOS (but I could)

Would be neat if you could do it!

tsterbak and others added 9 commits June 12, 2023 08:02
Enable the config for device code: `evert_n`
Enable the config for device code: `evert_n`
…#175)

This PR adds:
- A button that appears when no config is found for a device code. The
button redirects to a github issue requesting support for the device.
@freechelmi
Copy link
Contributor

Hello , anything blocking us to release this ?

@MagicLike
Copy link
Member

Hello , anything blocking us to release this ?

I guess the issues on the 0.4.4 milestone...

@tsterbak
Copy link
Member Author

This is a bit of a question of a release strategy and I'm not sure what a good approach is.

We could do a minor release now under 0.4.4 and then work on a larger release with more new features and fixes under 0.5.0.

Right now, I was settling for less but larger releases but we could also do otherwise.
What are your opinions on this @freechelmi @MagicLike ?

@MagicLike
Copy link
Member

This is a bit of a question of a release strategy and I'm not sure what a good approach is.

We could do a minor release now under 0.4.4 and then work on a larger release with more new features and fixes under 0.5.0.

Right now, I was settling for less but larger releases but we could also do otherwise. What are your opinions on this @freechelmi @MagicLike ?

I think it would be better to release 0.4.4 now, as it contains new devices, expands support for existing devices, fixes the scaling issue and even makes it easier to use for newcomers, who did not check if their device is supported. - Other stuff that can't be fixed quickly should be moved to 0.5 or even a possible 0.4.5...

- Update the unlocking instructions for FP3/4 and add
fastboot_unlock_critical command.
- Update tests and fix formatting.
@tsterbak tsterbak merged commit f656346 into main Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants