After a bit more investigation, it seems that for my local network, either the ssh client or ssh server device needs to be in the fixed IP list in the router. If both are using DHCP addresses I cannot get a connection.
I don't understand the reason, but it seems reliable. I can ssh to my servers (all on fixed ip) from any device, and they can all ssh into the Pro1.
Added the Pro1 to fixed ip list and instantly can connect to it from anywhere.
Probably just another gaping hole in my understanding, but it likely explains a similar issue I have one machine on my remote (vpn connected) network.
After a bit more investigation, it seems that for my local network, either the ssh client or ssh server device needs to be in the fixed IP list in the router. If both are using DHCP addresses I cannot get a connection.
I would check network data when DHCP is active - so what IP address you get, what is the default gateway and DNS address(es).
Another direction would be to ping router IP from Pro1 or if it works, an other server like 8.8.8.8
Also, you may ping Pro1's address from another machine, moreover, you may try to ping the same IP address even if Pro1's network is switched off.
So, you may try to investigate what is the cause of this problem - for example, if there is a static IP given to a computer in the same range your DHCP allocates addresses.
I am sorry if that caused any inconvenience, but I didn't see it as a duplicate since both posts point to the same gist source that I can update if needed. I just posted the link into two threads that may gather different people: a broad audience in the other thread and just those that were already considering SFOS for their Proš here. I did add it to real posts in the first post of this very thread, and the TJC wiki.
My thinking was that if people in the bigger F(x)tec thread notice that they can easily copy-paste command lines to get started with Sailfish and still be able to restore stock Android, that might draw attention beyond the already strong-hearted ones who already did decide to go Sailfish. I didn't mean to cause any confusion. :<
Thanks for posting Pcfe's article too, it's a nice one and he helped proofreading the instructions above.
Running Sailfish OS on Fxtec Pro1, using it as everyday phone. Used instructions from https://community.fxtec.com/topic/24...or-fxtec-pro1/ to install Sailfish OS (note: adb package from De**an repositories was too ancient, I had to download the platform-tools directly from Google's website in order to be able to do "fastboot set_active a" without getting "error: Could not get suffixes.").
Aurora wallpaper in Sailfish OS is stunning - looking forward to setting a live/animated wallpaper (if it's not too battery-consuming) to reflect on season of the year, time of day and holidays.
Icons are nice. Terminal in the list of applications is encouraging. Haven't got a Jolla account so far.
When a call is coming in, with default Ringtone (which is nicer than Android's default Ringtone, by the way)... As the volume is raising second after second... After certain dB level, speakers start adding "white-noise" on top of sound. Is it just me, or do all retail Fxtec Pro1 units suffer from this problem? Is it hardware problem or software problem? I should probably test with music instead of ringtone (in case it is some radio-interference problem).
Will test yellow arrow modifier key later - it was driving me up the wall in Android when I could not type the question mark in an SMS.
Audio calls are fine, but, quiet. And, there is echo audible (probably depends on whether "Loudspeaker" mode is on or off).
Thank you. Best wishes.
~~~~~~~~~~~~~~~~~
Per aspera ad astra...
Indeed it does! Is there any way to make Advanced Camera the default camera app (i.e. the one you get by swiping up from the bottom of the lockscreen if "quick access to camera" is enabled)?
