It still amazes me that you have the same address range on your wifi.
Does it work if you disable your laptop wifi?
What about setting the same address statically as the one from the Xperia? Maybe there’s another host you’re trying to connect to with the same IP on SSH.
You can get the MAC of the ip by inspecting with the arp command and compare to the one of the phone
For me, networks are a closed book, so unfortunately I don’t get what you mean
I tried the steps you described:
Disabling wifi doesn’t change anything
I tried with the command ifconfig enxa6e4ca642714 192.168.2.14 you proposed above (interface replaced by the actual device name, seems to change everytime I connect the phone). I get a Connection refused as answer, it doesn’t complain a missing route. I don’t think it tries to connect to another device, as the device only shows up with ifconfig as soon as I connect my phone.
Success! I had a look in the thread you linked and in the third post (https://forum.sailfishos.org/t/q-had-to-setup-new-my-linux-laptop-now-cant-ssh-to-sailfish-phone-no-more-what-can-i-do/16687/3) it was proposed to use the -v option for ssh. Although this should only turn on the verbose mode, as far as I understand, after a lot of debugging output I suddenly was asked to confirm the fingerprint. As soon as I confirmed, I was asked for the password of my phone and then I was logged in
I don’t know why that worked (in the line above I tried the same command without -v), and in fact I can’t really say what worked. The strange thing is: with infonfig I see my phone connected as 192.168.2.14, because I tried to set a static IP. But the successfull connection was with ssh into 192.168.2.15.
This is all very confusing (at least for me), but now I can ssh into my phone
Now that I can log into the phone I faced two issues:
It seems that I can’t make the fingerprint reader work. I can register one or two fingerprints with the preinstalled community app, but after registration they seem to be not recognised.
I can’t delete the unencrypted home, because in step 2 of the instructions, the device always claims that the umount doesn’t work because the resource is busy
But otherwise: it works really nicely, thank you so much
I think I may have drawn the fingerprint circle only for registration in that app. To use it to unlock the device you need a patch to modify the lock screen: Project: patch-lockscreen-touchArea (install patchmanager and you’ll find it in web catalog)
I think this is because when ssh-ing, it defaults the working directory to /home/defaultuser. This means you need to change directory to e.g. root, then devel-su and stop the user session & umount. You can find the processes using /home with a command such as lsof /home
In this case encryption was not so super important, because at the journey it acted more like a toy which I was trying out, while my Xperia 10 III still acted as my main device. But if I had set it up properly, I would have been really glad to have it encrypted
I hope I’ll find another one for a good price when I’m back home.
But nevertheless, it was an interesting journey with you fixing the issues. Thanks a lot, I can absolutely recommend your port to anyone considering this device!
There are no changes impacting the port in the upstream since 11 vs 13 were only appsupportr related, but I have inserted one adaptation change, the signalling of the cutout presence which should by default move the clock a little lower. I will update the clock patch anyway but sometimes later.
Edit: there is one update though, which I made after the release, so you need to
# zypper ref -r adaptation-community && zypper up -r adaptation-community
and that is, the five cameras don’t need a patch anymore, and droidmedia was reverted back to an original commit from sailfish repo - in the previous update it was using a testing patch.
