Yes. I have always been doing:
Code:
F5321: / $ su
F5321: / # setprop service.adb.tcp.port 5555
F5321: / # adb kill-server
F5321: / # adb tcpip 5555
F5321: / # stop adbd
F5321: / # start adbd
F5321: / # adb connect localhost:5555
And it always asks for authorization as the first time.
---------- Post added at 07:03 PM ---------- Previous post was at 06:11 PM ----------
Thank you, Surge.
Sorry for a dumb question, but what is "it" that is scanning for "the keys"? Which keys?
Are you saying something is searching for adb_keys in /sdcard instead of /data/misc?
If so, should I copy /data/misc/adb/adb_keys to /sdcard? I will give that a shot.
If you don't get the pop up, I can understand that it's not a big deal. I DO get the pop up and want to get rid of it.
One of the app I use draw over other apps and prevent me from tapping "OK" on the auth dialog. I have to disable the app, authorize adb, then enable the app back. I eventually want to script all steps from adb connecting to mounting encrypted volume for easy one click and obviously not being able to click "OK" gets in the way.
What is this virtual emulator on 5554? Is it always there when adb is listening to port 5555? I have seen "emulator-5554" when I try connecting to localhost and wondered what it is. I have seen both at the same time:
Code:
F5321: / # adb connect localhost:5555
F5321: / # adb devices
localhost:5555 unauthorized
emulator-5554 unauthorized
My observations are:
- "emulator-5554" always asks for authorization even with the key copied in /data/misc/adb/adb_keys, just like localhost.
- adb shows only one authorization dialog. If I get emulator-5554, that's the only one that gets authorized, effectively preventing me from authorizing localhost.
- I still have no idea where emulator-5554 came from, but I took a wild guess and uninstalled an app called "WiFI ADB" that I had on my phone. I have not seen emulator-5554 ever since.
If connecting to emulator-5554 does exactly the same as connecting to localhost, I don't mind using either one (if emulator-5554 ever come back). However, emulator-5554 still asks for authorization on my machine, therefore won't solve my problem.