Connecting Sony Xperia 10 III to PC as debug device for SDK

Platform Development
1

Hello all,

@moderators if that is not the right part of Forum, please move the topic.

I tried to find similar topic, but I don’t see one, so starting the new one.

I am now on the point, that the Sailfish SDK is installed (MX Linux, debian based with offitial debian kernel). Example APPS are working now in the emulator mode. Now I am trying to setup the USB connection in development mode, but this is not working. Here is the HowTo: Your First App | Sailfish OS Documentation . If I folow all the stepps, in the wizard I have no connection to the phone with error:

SSH connection failure. defaultuser@192.168.2.15: Permission denied (publickey,password).

If I try to ssh fromn terminal, I can connect directly.

Some ideas?

2

At which step do you encounter the error?

3

device preparation.

image
image812×505 21.1 KB

4

previous step for key Deployment, I created the key pair and tryed to deploy the public key, but:

image
image805×499 39.9 KB

5

but with terminal:

image
image507×155 21.5 KB

6

That’s quite strange, assuming you entered the password correctly. Anyway, you should be able to deploy the public key manually as well. Just add it to .ssh/authorized_keys on your device.

1 Like
7

I was not asked for password in the wizard.

you mean, i should add the key in my xperia?

where is the .ssh/… located?

and how to add? my public key looks like that:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQCxRT9ZXYPfkpTZyX4j1xXZWxLkdzowNs7eWh3aJZgU+r92xX77mdYhykYEAAsqnMB04nKfH8frFn8d9srL8LoLr+UjjHb3M1vdOcLsAwGgL9twsDkDegfw4BUe5ZYy3aoVZPkJo0TfhmY+gVdIQLHHZEWtZ4Ucwe8vdgmW3lP0iw== user@mx25

should I add only the key itselv or complete string?

8

I think, I found the issue. in the public key, generated with wizard, there wase my user on my PC entered, not the defaultuser@Xperia10III

after I changed this, it look like working now.

THANKS anyway!

1 Like
9

That should’t really matter. But I’m glad you got it working!

1 Like
10

Sometimes I have had problems to connect the SDK to a device. My possibilities have been USB cable, home WLAN and sharing the network from my Jolla C2 device. I have ended to the situation that I share the connection with my Jolla C2 device. The good point is that the device ip stays always the same 172.28.172.1 which helps SDK setup to stay fixed when managed to get it to a working status.

For other devices I create only rpm files manually and move them to the devices manually with the cable and install them by Filemanager. Sometimes it is easiest to utilize Chum testing for older devices than try to develope straight with SDK.

I have a docker version of the SDK. One day in history I messed my VirtualBox and did not have power to find what is wrong.

Happy hacking!

11

In my case it was the wrong user info in the public key file. Now it working fine with USB

Edit: Some misswording changed..

2 Likes