-
-
Notifications
You must be signed in to change notification settings - Fork 11.6k
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
Android 15 not work #3188
Comments
more logs: 2024-11-21 16:57:42.035 24310-24318 s.plugin.kcptun com...hub.shadowsocks.plugin.kcptun E Failed to send jdwp-handshake response.: Broken pipe 2024-11-21 17:40:39.015 7621-14047 WM-SystemJobScheduler com.github.shadowsocks D Scheduling work ID a2787dd7-2db5-482b-9120-c28ffbc22c78Job ID 27 |
Are you using OnePlus? Maybe a device specific issuse. termux/termux-app#4219. |
realme, but realme and oneplus all belong oppo, maybe same problem, seem kcptun is killed by OS |
same with #2954 , i try run kcptun-client in termux + ss without kcptun, it's works |
Seems so. I've upgraded my OnePlus 12 from ColorOS 14 to 15, and shadowsocks android with the v2ray plugin won't connect to the server which toasts |
Termux installed from f droid has issues setting up bootstraps (script killed when opening termux), but the one from Google play store runs pretty fine. Maybe shadowsocks android is having the same issue? |
After upgrading shadowsocks android to 534 from GitHub repo release, it can connect but no connection would go through the VPN set up by it. Same environment and same message as in #3185 |
After last system upgrade, it's works again, seem OS bug |
A newer OS version fixed the issue. The Google Play Store version works. |
Please read contributing guidelines. Thanks.
Describe the bug
SS With KCPTUN not work, without kcptun will be ok
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should be work
Screenshots
Smartphone (please complete the following information):
Configuration
Put an
x
inside the [ ] that applies.Additional context
Add any other context about the problem here.
logs file:
log.log
The text was updated successfully, but these errors were encountered: