Improve performance and remove flickers and enhance buffering

[hasanm08]

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.

List which issues are fixed by this PR. You must list at least one issue.

• Updates README to indicate that Android SDK <21 is no longer supported.
• Improves buffering performance with optimized memory usage.
• Enhances video loading speed with better resource management.
• Reduces UI freezes during playback of high-resolution content.
• Fixes stuttering issues on initial video playback.
• Improves overall video playback performance across platforms.

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under¹.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩² ↩³

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[hasanm08]

#168114
flutter/flutter#168114

[hasanm08]

@ianloic @sethladd @kevmoo @darrenaustin
please review

[stuartmorgan-g]

Thanks for the contribution!

@ianloic @sethladd @kevmoo @darrenaustin please review

Please re-read the contributor documentation linked from the PR checklist; the way reviewers is assigned is via a standard weekly triage process, not by pinging (random) people.

You’ve checked boxes in the PR checklist above that are not reflected in this PR (e.g., both of the entries regarding testing), so I’m assuming this is a work in progress and am marking it as a Draft. Please review the checklist, updating the PR as appropriate, and when the state of the PR as posted reflects the checklist please feel free to mark it as ready for review.

Also, as a general note, PRs that are scoped to specific issues are strongly preferred over PRs that make a variety of unrelated changes, so this should very likely be multiple PRs given the list of things in the PR description.