[QUESTION] importing

[gilcu3]

How to currently import a file? I am using the adb method, but on WearOS 3 (therefore no FilePicker).
For some reason the wifi is not recognized by this app, even though it works for adb.
Also, to make this work the app must be debuggable, is there any known way to overcome that?

[0x4f53]

How to currently import a file? I am using the adb method, but on WearOS 3 (therefore no FilePicker).

https://github.com/0x4f53/Wristkey/wiki/Transferring-Data

For some reason the wifi is not recognized by this app, even though it works for adb.

Please make sure both devices are on the same Wi-Fi network for this.

Also, to make this work the app must be debuggable, is there any known way to overcome that?

You can clone it and build it manually via gradle.

[gilcu3]

How to currently import a file? I am using the adb method, but on WearOS 3 (therefore no FilePicker).

https://github.com/0x4f53/Wristkey/wiki/Transferring-Data

For some reason the wifi is not recognized by this app, even though it works for adb.

Please make sure both devices are on the same Wi-Fi network for this.

I did exactly that, but the wear os app could not detect the wifi connection.

[0x4f53]

Can you send me a logcat then?

[gilcu3]

Yes, I should have done that from the beginning. This log.txt comes from a debug build I did myself, in sync with the latest commit here. I already have some accounts working (setup using adb method). I just pressed the wifi button and got the cannot detect wifi sign, while at the same time I am actually capturing the logcat through adb wifi.

And btw to get adb import to work I had to modify the source code to import a specific json file, as the file picker is not present in wear OS 3 I did not have a way to say which file to import in the version 3.x UI.

[0x4f53]

well the adb debug method is really only for devices without wifi (only one that comes to mind). the main way is now via wifi.

[gilcu3]

well the adb debug method is really only for devices without wifi (only one that comes to mind). the main way is now via wifi.

Got it, it makes sense to deprecate that feature. That makes it even more important to figure out why Wifi is not detected on the Ticwatch

[0x4f53]

@gilcu3 Any luck with this? I don't have a TicWatch with me so I cannot figure this one out. The logcat doesn't seem to have anything unusual either.

[gilcu3]

No, unfortunately, I have been using the app with my own debug build to workaround the issue.