Porting to Samsung Galaxy Note 4 SM-N910P

[flohack]

@tigerpro All porting efforts should be made with the Halium guide only now. Anything else you find might be outdated.

See here: http://docs.halium.org/en/latest/porting/first-steps.html

BR

[tigerpro]

@flohack is this guide up to date for ubports? It does mention Halium as well as state to get Halium to compile first

https://docs.ubports.com/en/latest/porting/introduction.html

Is the guide I'm referring to

[UniSuperBox]

@tigerpro

That guide is correct.

Source: I wrote it.

[tigerpro]

@unisuperbox thank you for an updated guide, one question that I didn't see in the guide though, does Halium just have to compile, or does it have to boot as well?

[doniks]

@tigerpro the normal process is to get it running. However, keep in mind that porting is always a trial and error process. Nobody stops you from attempting UBports rootfs even though you might still have problems with halium rootfs. Equally well, nobody stops you from switching back and forth between the two

[tigerpro]

@doniks thank you doniks, I am currently trying to get it running, have an error with /init, haven't had a chance to try and fix it due to a recent family death, I'll keep ya posted

[doniks]

@tigerpro Sorry to hear. All the best!

[tigerpro]

@doniks thank you, I managed to get a test boot of my latest compile in, no change from the previous attempt, I think I have to modify my Mount points to get it working at this point. I'm going to redo that step and see if there's a change from this last attempt. I think if I can get a telnet or ssh interface I'm on the right track. I'm going to just mess with the data point for now to just speed up my attempts, once I get more successful results then I can apply it to the rest of the points.

[doniks]

@tigerpro solid plan! Yeah, telnet and ssh are important milestones and yes I think you need to do the fix mount points thing and yes I think the only partition you really need is the data partition.

NB: the guys are working on an alternative to hybris-boot named halium-boot and somehow that will not need the fix mount points stuff, but I'm not sure how it works or whether it is fully fleshed out. I am personally holding off with trying halium-boot because it seems that there are just too many changes happening at once now and I want to wait until that stabilizes a bit.

[tigerpro]

@doniks oh, I did not know that, I will definitely have to keep an eye out for it. I agree waiting for the changes to be less sporadic is a good idea, otherwise you could end up compiling something that is outdated before you even finish compiling it, which gets annoying very quickly IMO. I'll let ya know how my next attempt goes, hopefully much better.

[flohack]

@tigerpro Are you in the Halium Telegram group yet?

[tigerpro]

@flohack I am not, I am however in the Halium IRC, although admittedly I have not looked at it in a few days

[flohack]

@tigerpro You definitely should, IRC is lacking screenshots and such features - The group is very busy sometimes, so I find it easier to follow also on Telegram. But it´s good you are connected already. This will be your main source for porting questions.

I am working on S3 Neo port, so we can discuss common stuff like Heimdall and how to modify our install system to allow Samsung phones to be installed

BR

[tigerpro]

@flohack OK you can stop twisting my arm lol jk I signed up for telegram as well, I don't know of I'll be able to pay any more attention to it or not, but at least I'm now on it. I haven't had a chance to work on my data Mount point yet as I've been busy with family obligations, but I do intend to look at it in the coming days.

[tigerpro]

So an update, I compiled halium-boot, which successfully boots, loads Ubuntu gives me ssh, but the phone stays on the power on screen. I do have a few tips to try and fix it, but I am at least making progress, then I managed to break my ssh access so now I gotta fix that before I can move forward. The problem I get is that when I assign a IP on my developer machine, it gives me a "no route to host" error, and with lsusb it says google device for my phone I stead of Sony device, not sure its related but it is all I can find for clues to whether or not it will let me connect.

[doniks]

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

So an update, I compiled halium-boot, which successfully boots, loads Ubuntu gives me ssh, but the phone stays on the power on screen. I do have a few tips to try and fix it, but I am at least making progress,

nice!

then I managed to break my ssh access so now I gotta fix that before I can move forward. The problem I get is that when I assign a IP on my developer machine, it gives me a "no route to host" error, and with lsusb it says google device for my phone I stead of Sony device, not sure its related but it is all I can find for clues to whether or not it will let me connect.

I might be completely off, but two thoughts:

• maybe it's some network interface managing software on your development machine, like Network Manager who thinks it has to take over the rndis interface and reconfigure it. What happens if you simply do the configuration of the rndis interface again?

• or maybe it is something that the lxc container does. what happens if you disable the starting of the lxc container? does the losing of ssh persist?

[tigerpro]

@doniks I actually figure out my networking issue this morning, I re-compiled halium-boot, but I had to specify my boot partition as well cause it was booting to telnet (wasn't reading the "serial" as I did t realize something changed) so now I'm back to trying to figure out the GUI. From the commands I got through telegram, it appears as though the container isn't starting like of should be, hoping I can figure that out soon.

[tigerpro]

@doniks heres a link hot off the google docs of the freshest halium-boot, i got no idea what im looking at but thats a full dmesg:

https://docs.google.com/document/d/1CFQldnHxsCo75jRnjFUSfEDQKs4L6plMpfzM04__yjc/edit?usp=sharing

[doniks]

@tigerpro

1. I see
   [ 3.874744] initrd: WARNING: Failed to mount Android system.img.
   Can you post the output of mount and find /root/var/lib/lxc/android/ /var/lib/lxc/android/. Please use some pastebin service like https://paste.ubuntu.com/ rather than google doc
2. Can you get to the spinning spiral if you boot halium rootfs, following the guide?
3. Did you try plasma mobile?
4. For UT, did you do this: https://docs.ubports.com/en/latest/porting/building-ubports-boot.html#build-the-image

[tigerpro]

@doniks said in Porting to Samsung Galaxy Note 4 SM-N910P:

@tigerpro

1. I see
   [ 3.874744] initrd: WARNING: Failed to mount Android system.img.
   Can you post the output of mount and find /root/var/lib/lxc/android/ /var/lib/lxc/android/. Please use some pastebin service like https://paste.ubuntu.com/ rather than google doc
2. Can you get to the spinning spiral if you boot halium rootfs, following the guide?
3. Did you try plasma mobile?
4. For UT, did you do this: https://docs.ubports.com/en/latest/porting/building-ubports-boot.html#build-the-image

For 1 I don't how I missed that when I was looking through the dmesg, if I had seen that I could have tried fixing that. I haven't tried the halium rootfs cause I have heard that the tests in the halium rootfs don't work with halium-boot so I thought trying that would be a moot point. I haven't tried plasma mobile as I wanted to try and get one roots working before I try others, and I tried to boot ubports-boot but I only get to a telnet spot, halium-boot gets to a ssh spot. Based o your feedback and the entry you pointed out, I'm thinking I still have a Mount point issue which means I have to try a different Mount point entry for for /data and maybe /boot even though halium-boot would only give me telnet until I changed /dev/block/by-name/<block> to /dev/<block> in the fstab.qcom file. Any advice on what I can try next?