SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview - Page 72 - maemo.org

edp17 | # 711 | 2019-11-14, 08:22 | Report

It has completed!
I guess this is not an error

Code:

Pool started (with 5 workers)
Pool finished
DBus unavailable, falling back to libssu
* Check /home/edp17/mer/android/droid/hybris/droid-hal-version-hammerhead.log for full log. 
!! Please set the desired RELEASE variable in ~/.hadk.env to build an image for

Last edited by edp17; 2019-11-14 at 09:38. Reason: typo

The Following User Says Thank You to edp17 For This Useful Post:
juiceme

edp17 | # 712 | 2019-11-14, 08:28 | Report

...and the step '8.5 Building the Image with MIC' has also started.

Edit1: "Info[11/14 08:50:07] : Finished."

Edit2: Installed on the phone.

Edit3: ... but it doesn't boot.

and cannot be ssh to the phone either.

Anyway, ...to be continued.

Last edited by edp17; 2019-11-14 at 09:07. Reason: Added extra info

The Following 2 Users Say Thank You to edp17 For This Useful Post:
juiceme, mautz

mautz | # 713 | 2019-11-14, 09:07 | Report

And does it work?

The Following 2 Users Say Thank You to mautz For This Useful Post:
edp17, juiceme

edp17 | # 714 | 2019-11-14, 09:43 | Report

Originally Posted by mautz View Post

And does it work?

No, it stuck at Google logo. Plus cannot be access via ssh from the PC. I have rebooted twice and waited over 20 minutes each time. The little led at the bottom either not light up.
I have flashed with the cm-12.1-20160704-UNOFFICIAL-hammerhead-nocheck.zip base (mentioned here). That might can cause this behaviour?

The Following User Says Thank You to edp17 For This Useful Post:
juiceme

mautz | # 715 | 2019-11-14, 10:02 | Report

I don't think so, looks like there are some things missing in the kernel. Can you telnet into the device via USB(192.168.2.25:23)?

The Following 2 Users Say Thank You to mautz For This Useful Post:
edp17, juiceme

edp17 | # 716 | 2019-11-14, 10:29 | Report

Originally Posted by mautz View Post

I don't think so, looks like there are some things missing in the kernel. Can you telnet into the device via USB(192.168.2.25:23)?

I will try to telnet into it once I am at home.

The hadk says all errors can be ignored if the zip file is generated. Maybe it is not entirely true

. I have went through the kernel log file but there is no error just warnings. Plus I didn't get any error messages on the screen during the build or maybe they written out into files that I didn't check.

Now I am downloading an older cm-12.1 image (a snapshot from 2015) and trying that.
I will report once downloaded, installed and tested.

Edit: The cm-12.1 image (snapshot 2015) that I had didn't install. (The TWRP rebooted itself when tried to flash with the sailfish image.)
Therefore I re-installed the cm-12.1 (20160704-UNOFFICIAL) with the new Sailfish image. Later I will try to telnet into it.

Last edited by edp17; 2019-11-14 at 11:29.

The Following User Says Thank You to edp17 For This Useful Post:
juiceme

edp17 | # 717 | 2019-11-14, 20:05 | Report

Originally Posted by mautz View Post

I don't think so, looks like there are some things missing in the kernel. Can you telnet into the device via USB(192.168.2.25:23)?

Telnet doesn't work either. I tried with name, with IP address, with and without the port number: 'Unable to connect to remote host: No route to host'
However I can ping the device, so it somehow is connected to the PC.

(I tried IP 192.168.2.15 not 192.168.2.25.)

The 'lsusb' sees the device:

Code:

Bus 002 Device 010: ID 18d1:d001 Google Inc.

and the 'usb-devices' too:

Code:

T:  Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 10 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=18d1 ProdID=d001 Rev=02.32
S:  Manufacturer=Mer Boat Loader
S:  Product=init-debug in real rootfs
S:  SerialNumber=Mer Debug telnet on port 2323 on rndis0 192.168.2.15 - also running udhcpd
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=ff Driver=rndis_host
I:  If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=rndis_host

Last edited by edp17; 2019-11-14 at 20:12.

The Following 2 Users Say Thank You to edp17 For This Useful Post:
juiceme, mautz

mautz | # 718 | 2019-11-14, 20:30 | Report

Code:

Mer Debug telnet on port 2323 on rndis0 192.168.2.15 - also running udhcpd

Have you tried telnet 192.168.2.15:2323 ?

The Following 2 Users Say Thank You to mautz For This Useful Post:
edp17, juiceme

edp17 | # 719 | 2019-11-14, 21:09 | Report

Originally Posted by mautz View Post

Code:

Mer Debug telnet on port 2323 on rndis0 192.168.2.15 - also running udhcpd

Have you tried telnet 192.168.2.15:2323 ?

Yes, I tried. As the same as with port 23.

Edit: Well, almost the same:

Code:

could not resolve 192.168.2.15:2323/telnet: Name or service not known

The Following User Says Thank You to edp17 For This Useful Post:
juiceme

edp17 | # 720 | 2019-11-14, 21:16 | Report

adb devices shows nothing:

Code:

edp17@edp17-ubuntu:~$ adb devices
List of devices attached

edp17@edp17-ubuntu:~$

The Following User Says Thank You to edp17 For This Useful Post:
juiceme