-
Notifications
You must be signed in to change notification settings - Fork 7
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
error during setup -> You must specify a valid interface name. #7
Comments
(android) |
what model and android version are you using? |
13, latest security update and quarterly year update it's a Custom ROM based on AOSP called Kenvyra, for the Mi 9T (davinci) running with KernelSU, not Magisk |
any fixes? |
I wasn't able to reproduce this unfortunately, but I merged this pr #8 when this error happens again, the traceback should be printed on your screen, please share it here |
the app just shows "DeadNet" in ascii now and crashes, i can't get into the main ui. |
i think something's wrong in your new code, just revert the commits since turning on location makes the app crash, with or without mobile data it still makes that error |
thanks, I reverted the commit the fact the app cannot fetch the SSID name, assuming it is connected to one, means it might be an issue with location permissions / services, which are required since Android API 27 i will try to recompile the APK for a newer version (yours is API 33, assuming you use Android 13, and buildozer by default builds for 27) once i will be able to, but that will only be in a couple of days since i'm away from home :) meanwhile, it would help me immensely if you run the apk with |
i do not have access or the capability to run that for now, but i can tell you that the interface name most commonly is "wlan0". try selecting that |
the interface name should be fetched using the I compiled the app for Android API 33, under the is this one also making problems? |
I've given the app root permissions but it seems like python complains about an interface name
The text was updated successfully, but these errors were encountered: