@Flohack Hi, sorry for the lengthy follow-up, I've been busy with competitive exams…

I am sorry to say that I won't be able to try and port this anymore: probably because of a power surge, my phone USB port is dead and I can't transmit anymore data to the phone…

Thanks for the help, I'll try to contribute some other way (but after the oral part of my exams).

Hi everyone,

I am currently trying to port our recently dead OS to my phone (surnia).
It has a CM/LineageOS 12.1 port which makes it quite straightforward, but I am stuck with a situation close to the bullhead port.
My build boots, but not graphically, ADB does not start, RNDIS does and I can look around the running system.

But the thing is, I don't know what to look for!

I checked common places I know of, here is my dmesg, and some random commands.
What bothers me most is:

• [ 111.491674] systemd-hostnamed[881]: Failed to run event loop: Connection timed out
• root@ubuntu-phablet:/# systemctl status
  Failed to get D-Bus connection: Operation not permitted

But I don't know what to think about it… Nor how to fix it…

What do you think? Thanks

PS: really looking forward a LineageOS 14.1 rebase, any way to help?

@Flohack This was already in my random commands (OP), but here it is:

root@ubuntu-phablet:/# lxc-info -n android
Name:           android
State:          RUNNING
PID:            591
IP:             192.168.2.15
CPU use:        3.44 seconds

OK so the property ro.product.device used by Ubuntu's init to determine the device was set by Android's init too late (this is an unified device tree). It is now fixed (hardcoded in my system.prop).

[   19.324825] initrd: device is surnia_umts
...
[   28.163553] init: Found radio id: 0x4 setting build properties for surnia_umts device

I have dumped my udev rules and placed them in /etc/udev/rules.d/70-surnia_umts.rules. I haven't noticed any change so far (except for udev complaining about unknown users and groups).

You were right, the debug boot option broke the boot, causing a boot loop I'll check in the console-ramoops when I have the time.

Will I really need to patch AppArmor? I already run Linux 3.10.49…