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

Scanning failed and no networks found #13

Open
tuxayo opened this issue Mar 19, 2022 · 1 comment
Open

Scanning failed and no networks found #13

tuxayo opened this issue Mar 19, 2022 · 1 comment

Comments

@tuxayo
Copy link

tuxayo commented Mar 19, 2022

When opening the app it immediately says "Scanning failed"

03-19 16:15:30.407   564 11897 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=net.yolosec.routerkeygen2/org.exobel.routerkeygen.ui.NetworksListActivity bnds=[792,1591][1045,1858]} from uid 10095
03-19 16:15:30.431 16493 16493 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@63d43a6
03-19 16:15:30.488   564  1398 D WifiService: setWifiEnabled: true pid=16493, uid=10180, package=net.yolosec.routerkeygen2
03-19 16:15:30.488   564  1398 I WifiService: setWifiEnabled package=net.yolosec.routerkeygen2 uid=10180 enable=true
03-19 16:15:30.488   564  1398 I WifiService: setWifiEnabled in Airplane mode: only Settings can enable wifi
03-19 16:15:30.490   564   585 I WifiService: startScan uid=10180
03-19 16:15:30.492   564 10210 W ActivityManager: Receiver with filter android.content.IntentFilter@bb5f2e7 already registered for pid 16493, callerPackage is net.yolosec.routerkeygen2
03-19 16:15:30.493   564   586 I WifiService: startScan uid=10180
03-19 16:15:30.515 16493 16517 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-19 16:15:30.516 16493 16517 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
03-19 16:15:30.561   564   616 I ActivityManager: Displayed net.yolosec.routerkeygen2/org.exobel.routerkeygen.ui.NetworksListActivity: +139ms
03-19 16:15:30.734   404   883 W SurfaceFlinger: Attempting to set client state on removed layer: Splash Screen net.yolosec.routerkeygen2#0
03-19 16:15:30.734   404   883 W SurfaceFlinger: Attempting to destroy on removed layer: Splash Screen net.yolosec.routerkeygen2#0
03-19 16:15:31.001   404   522 W SurfaceFlinger: Attempting to set client state on removed layer: Surface(name=AppWindowToken{51e37cc token=Token{907edff ActivityRecord{358a11e u0 net.yolosec.routerkeygen2/org.exobel.routerkeygen.ui.NetworksListActivity t4937}}})/@0xc2988a6 - animation-leash#0
03-19 16:15:31.002   404   522 W SurfaceFlinger: Attempting to set client state on removed layer: Surface(name=AppWindowToken{b52ce5f token=Token{c3b46fe ActivityRecord{b93d2b9 u0 com.android.launcher3/.lineage.LineageLauncher t4896}}})/@0xc6cc247 - animation-leash#0
03-19 16:15:31.002   404   522 W SurfaceFlinger: Attempting to destroy on removed layer: Surface(name=AppWindowToken{51e37cc token=Token{907edff ActivityRecord{358a11e u0 net.yolosec.routerkeygen2/org.exobel.routerkeygen.ui.NetworksListActivity t4937}}})/@0xc2988a6 - animation-leash#0
03-19 16:15:31.002   404   522 W SurfaceFlinger: Attempting to destroy on removed layer: Surface(name=AppWindowToken{b52ce5f token=Token{c3b46fe ActivityRecord{b93d2b9 u0 com.android.launcher3/.lineage.LineageLauncher t4896}}})/@0xc6cc247 - animation-leash#0
03-19 16:15:33.884   564 10210 W ActivityManager: Unable to start service Intent { act=android.security.IKeyChainService cmp=com.android.keychain/.KeyChainService } U=10: not found
03-19 16:15:33.885   895 16645 I SecurityController: could not bind to KeyChainService

I can run the actual scan and here are the logs

03-19 16:15:40.504   564  1398 W ActivityManager: Receiver with filter android.content.IntentFilter@11092fb already registered for pid 16493, callerPackage is net.yolosec.routerkeygen2
03-19 16:15:40.505   564 29083 I WifiService: startScan uid=10180
03-19 16:15:40.873   564   585 W ActivityManager: Receiver with filter android.content.IntentFilter@9f93f18 already registered for pid 16493, callerPackage is net.yolosec.routerkeygen2
03-19 16:15:40.874   564 10210 I WifiService: startScan uid=10180
03-19 16:15:50.512   564 17260 W ActivityManager: Receiver with filter android.content.IntentFilter@d4b63d7 already registered for pid 16493, callerPackage is net.yolosec.routerkeygen2
03-19 16:15:50.515   564 12497 I WifiService: startScan uid=10180
03-19 16:16:00.538   564  9931 W ActivityManager: Receiver with filter android.content.IntentFilter@7f86673 already registered for pid 16493, callerPackage is net.yolosec.routerkeygen2
03-19 16:16:00.543   564   990 I WifiService: startScan uid=10180
03-19 16:16:10.560   564   585 W ActivityManager: Receiver with filter android.content.IntentFilter@ffe585c already registered for pid 16493, callerPackage is net.yolosec.routerkeygen2
03-19 16:16:10.564   564   990 I WifiService: startScan uid=10180
03-19 16:16:20.581   564   585 W ActivityManager: Receiver with filter android.content.IntentFilter@3a830eb already registered for pid 16493, callerPackage is net.yolosec.routerkeygen2
03-19 16:16:20.585   564   990 I WifiService: startScan uid=10180
03-19 16:16:30.592   564  9930 W ActivityManager: Receiver with filter android.content.IntentFilter@bfb84e1 already registered for pid 16493, callerPackage is net.yolosec.routerkeygen2

Maybe the issue is "Receiver with filter android.content.IntentFilter@be92e97 already registered for pid 19896, callerPackage is net.yolosec.routerkeygen2"
It's there when launching the app even after force closing it.

@tuxayo tuxayo mentioned this issue Mar 19, 2022
@AndnixSH
Copy link

Same on my Moto G G5 phone running Android 11

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

No branches or pull requests

2 participants