Porting to Samsung Galaxy Note 4 SM-N910P
-
@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.
-
@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.
-
@tigerpro Are you in the Halium Telegram group yet?
-
@flohack I am not, I am however in the Halium IRC, although admittedly I have not looked at it in a few days
-
@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
-
@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. -
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.
-
@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?
-
-
@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.
-
@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
-
- I see
[ 3.874744] initrd: WARNING: Failed to mount Android system.img.
Can you post the output ofmountandfind /root/var/lib/lxc/android/ /var/lib/lxc/android/. Please use some pastebin service like https://paste.ubuntu.com/ rather than google doc - Can you get to the spinning spiral if you boot halium rootfs, following the guide?
- Did you try plasma mobile?
- For UT, did you do this: https://docs.ubports.com/en/latest/porting/building-ubports-boot.html#build-the-image
- I see
-
@doniks said in Porting to Samsung Galaxy Note 4 SM-N910P:
- I see
[ 3.874744] initrd: WARNING: Failed to mount Android system.img.
Can you post the output ofmountandfind /root/var/lib/lxc/android/ /var/lib/lxc/android/. Please use some pastebin service like https://paste.ubuntu.com/ rather than google doc - Can you get to the spinning spiral if you boot halium rootfs, following the guide?
- Did you try plasma mobile?
- 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?
- I see
-
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
I totally get why you want to stick to one thing at a time. I'm in the same place really
Still, in time when you get to it, it might offer some insight and it will teach yourself where to look and what to check. Could easily be that the halium rootfs does not (yet) (fully) work with halium-boot, so you would be back at hybris-boot As for immediate next steps ...
Can you post the output of mount and find /root/var/lib/lxc/android/ /var/lib/lxc/android/.
-
@doniks said in Porting to Samsung Galaxy Note 4 SM-N910P:
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
I totally get why you want to stick to one thing at a time. I'm in the same place really
Still, in time when you get to it, it might offer some insight and it will teach yourself where to look and what to check. Could easily be that the halium rootfs does not (yet) (fully) work with halium-boot, so you would be back at hybris-boot As for immediate next steps ...
Can you post the output of mount and find /root/var/lib/lxc/android/ /var/lib/lxc/android/.
output of mount:
https://paste.ubuntu.com/p/gpmj9H43NN/
and if i do find /root/var/lib/lxc/android/ /var/lib/lxc/android/. it gives me a list as if I typed ls -
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
output of mount:
there's two outputs of mount in there, with different result. what's the difference? how much time was there approx in between?
and if i do find /root/var/lib/lxc/android/ /var/lib/lxc/android/. it gives me a list as if I typed ls
exactly. could you paste the result. it's to check whether the mounting of the android container is successful
-
@doniks said in Porting to Samsung Galaxy Note 4 SM-N910P:
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
output of mount:
there's two outputs of mount in there, with different result. what's the difference? how much time was there approx in between?
and if i do find /root/var/lib/lxc/android/ /var/lib/lxc/android/. it gives me a list as if I typed ls
exactly. could you paste the result. it's to check whether the mounting of the android container is successful
The second one was maybe a minute after the first one, I had some lag going on cause I was using a vnc connection at the time and it just spammed both. I'm not in front of my desk ATM but I will get that output for you when I get home from work
-
@doniks I booted the phone, left it alone for roughly 15 minutes then connected and got the outputs for you, I tried lxc-android-config instead of systemctl and got a "command not found" error. heres the outputs for you:
https://paste.ubuntu.com/p/vXjbTk7Xdr/
let me know what you think I might be doing wrong or missing.
Thank You
Edit:
I noticed the output of find this time is much smaller than what I got last time, but again, I connected to the phone (it reset connection a couple times which is the errors at the top of the log output) and ran the commands you asked me too and copy and pasted
-
Hey sorry for the long stretch of silence, so some news first, I finally managed to get hybris-boot to boot and start the android container, the downside ... It takes 30-40 minutes to connect to my dev machine from my phone. I have found anything involving graphics with the reference rootfs causes my device to just crash. I have tried plasma and that just doesn't do anything at all (phone stays on the Samsung logo) and ubports as of my last attempt boots, connects to my dev machine, however it refuses to let me login saying my password is wrong (even though it is not). I have added my udev rules after the first successful boot to the reference rootfs before I ran any tests. I think at this point my issue is that I need a CAF rootfs for the OSes I want to try. I have also been using JBB's install script (albeit an older version but it has always worked for me). I will try again in a day or two as time permits and report back.
-
Sorry for duplicate posts, I just attempted to boot ubports again, after adjusting my fstab file, I was able to get ubports to boot, I still don't get past my devices power on screen, when I ssh in it says "Welcome to Ubuntu" I do "sudo -I" followed by "lxc-info -n android" which reports that the container is running, I don't fully know what to do from here but I will be doing some research into it and see if maybe I'm missing anything. I tried the steps that are part of the #40 issues as well just to see if it made any difference (it didn't) and if I do "test_egl" it just segfaults which hybris-boot would do, with the difference of hybris-boot would cause the device to crash where as halium-boot doesn't crash but produces the same error.
-
I think the best known way right now is this faq:
https://pad.ubports.com/p/porting-faq and of course the bunch of smart people in the ubports porting telegram chat
