ubports-installer does not detect fp2

[pixelr0]

ubports-installer does not detect fp2
i'm using ubports-installer snap - installed: 0.1.7-beta (6) 88MB devmode - on Ubuntu 16.04
and i'm on 15.04/devel r183 on the phone

i can see the phone in nautilus, and "adb shell" works fine, i can connect to the phone. i also have developer mode enabled

[NeoTheThird]

Try running adb devices while the installer is waiting for the device. If that helps, the problem is #39.

[pixelr0]

doesn't seems to help :'(

adb devices
adb server is out of date.  killing...
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: 

[pixelr0]

ok, flashed 15.04/stable/r2 and it's the same ubports-installer does not detect fp2

should i proceed with manual?

[pixelr0]

same with the appimage, so it's not snap related

[NeoTheThird]

doesn't seems to help :'(

If you get that error, try running adb devices again, please.

[NeoTheThird]

Please also try running the installer from source. See README.md

[Anne017]

@pixelr0 It seems to be the same issue than me in #36

[Anne017]

I tried to run the installer from source without success:

git clone git@github.com:ubports/ubports-installer.git
Cloning into 'ubports-installer'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

[pixelr0]

right, same permission denied (publickey) error here. you can workaround that error by using "git clone https://github.com/ubports/ubports-installer". even so on my PC ubuntu 16.04 ./setup-dev.sh hangs

[pixelr0]

phew!! finally managed to install fp2 devel. i had to run ./setup-dev.sh a couple of time since it kept hanging on random steps in npm-install. running from source recognized fp2 straight up.

[Anne017]

OK, this time everything went fine typing into the terminal:
git clone https://github.com/ubports/ubports-installer.git
cd ubports-installer
./setup-dev.sh
npm start

But after that, I still get an error between the password and the bootloader screens.
It seems the installer has been modified and now it is possible to send a bug report.
Reference is #41

[NeoTheThird]

Thanks for reporting! I'm pretty sure it's related to #39, so let's track it there.