Auto (balance) mode: replace current strategies with clearer goal-based modes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Read the related issue #2502 for the balancer tuning plumbing and first-alive strategy mentioned here. Then trace how Auto (balance) strategies are presented and mapped to balancer or url-test parameters in the app; the issue does not name files or tests. Done means replacing the confusing strategy choices with the proposed goal-based modes and their intended connection priorities.
Written by the indexing model from the issue text.
Description
Summary
Feedback on the Auto (balance) mode from support experience with thousands of users: the current strategies are confusing and in practice don't work well. Almost every user with connection problems was fixed by switching to lowest (lowest ping) or selecting a config manually.
Problems with the current options
- Round-robin rotation between configs, the strategy that picks a config based on logs/history, and sticking to one config look good on paper but do not give a good user experience.
- The names and differences are unclear to normal users.
- The rest of the app is clear and simple; this part is the exception.
Suggested alternative modes (user-facing, outcome-based)
- Best Stability: most stable connection
- Highest Speed: highest throughput
- First Alive: first healthy server
- Gaming Mode: prioritise latency and jitter
- Streaming Mode: prioritise speed and stability
Each mode can map to existing balancer/url-test parameters internally; the user only sees the goal.
Related
- #2502 (balancer tuning plumbing, first-alive strategy)
- Dominant language
- Dart
- Stars
- 33.9k
- Forks
- 3.2k
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 22
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hiddify/hiddify-app
-
bug from-telegram platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiddify/hiddify-app#2592 ·
Maintainers usually reply within 1 day
-
from-telegram logs platform:android
Difficulty 3/5 1-2 days Newbie friendliness 52/100
hiddify/hiddify-app#2593 ·
Maintainers usually reply within 1 day
-
area:connection bug from-telegram platform:android
Difficulty 4/5 3-5 days Newbie friendliness 18/100
hiddify/hiddify-app#2591 ·
Maintainers usually reply within 1 day
-
[Logs] Extra security mode with WARP fails to connect on v5.9.8 (works with Psiphon and on v5.5.5)Openarea:connection from-telegram logs platform:android
Difficulty 4/5 3-5 days Newbie friendliness 28/100
hiddify/hiddify-app#2590 ·
Maintainers usually reply within 1 day
-
[Logs] AmneziaWG profile fails to connect on Android (server on 3x-ui), works in AmneziaVPN clientOpenarea:connection from-telegram logs platform:android
Difficulty 4/5 3-5 days Newbie friendliness 25/100
hiddify/hiddify-app#2589 ·
Maintainers usually reply within 1 day
All issues in hiddify/hiddify-app
Similar issues
-
Bug Dart
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getsentry/sentry-dart#4167 · 2 comments ·
Maintainers usually reply within 2 days
-
bug enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cogwheel0/conduit#1122 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bannzai/shoppinglist#779 ·
Maintainers usually reply within 1 day
-
Android bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PostHog/posthog-flutter#731 · 1 comment ·
Maintainers usually reply within 1 day