Porting to Samsung Galaxy Note 4 SM-N910P
-
@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 -
@doniks thank you for the link, I will look through it and try the relevant parts. I think I may have tried these before and went from a booting device to a bootloop device, but that could be a different thing I had tried previously. I did get the latest edge roots from that though so I will try that first and go from there. I hope to have an update soon. I was using the telegram for awhile however most of the people on there that try to help me end up either guiding me to a bootloop or don't know enough to fully help yet so I try to keep that as a last resort now. I do need to fix my repo though with all my tweaks so far.
-
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
@doniks thank you for the link, I will look through it and try the relevant parts. I think I may have tried these before and went from a booting device to a bootloop device,
well, there is no guarantee that it will happen again, but I guess it's still a step forward. Next step would then be hunting down the specific reason for the boot loop
fwiw, this is the selection of things I took from the faq:
https://github.com/Halium/projectmanagement/issues/22
take frameworks/native and bionic from the porting-faq rm graphics-android-caf.so.10 fix /run/user/32011 (porting-faq) fix dbus-daemon-launch-helper (porting-faq)but that could be a different thing I had tried previously. I did get the latest edge roots from that though so I will try that first and go from there. I hope to have an update soon.
good luck
I was using the telegram for awhile however most of the people on there that try to help me end up either guiding me to a bootloop or don't know enough to fully help yet so I try to keep that as a last resort now. I do need to fix my repo though with all my tweaks so far.
I hear you. I personally also like the format of a forum or a mailing list, where you can formulate a more elaborate question or answer and have the full context of the conversation. But I think many people prefer tg, at least I have often gotten the answer I was needed on tg eventually.
-
@doniks I have some mostly good news, I did the first few things in the link you provided, I now get the Ubuntu Touch boot screen with the scrolling dots, I have yet to get it to go any further than that though. I can ssh in so I dont fully know if this is the spinner that is referred to or if it a different screen all together. Ill just leave it be and see if it eventually does something more cause the screen does dim after awhile then eventually shut off and if I press the home button it comes back up with the same screen. I appreciate all your help so far.
-
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
@doniks I have some mostly good news, I did the first few things in the link you provided, I now get the Ubuntu Touch boot screen with the scrolling dots, I have yet to get it to go any further than that though. I can ssh in so I dont fully know if this is the spinner that is referred to or if it a different screen all together.
That's great! And yes, that is the "spinner" (I had the same question:) ).
I think what I had to do at that point was the stuff about
/run/user/32011- it's in the FAQ. You should see something about it in the logs: http://docs.ubports.com/en/latest/porting/common-problems-run.html#getting-more-mir-logs -
@doniks I was thinking that could be part of the issue but the part in the parenthesis indicates it was fixed 10/28/18 and I'm using edge roots from 12/6/18 however I could try that, if that doesn't resolve it then I'll try getting the logs and see if those shed any light on the matter. I have to stop for a little bit today, but I'll look at it later.
-
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
@doniks I was thinking that could be part of the issue but the part in the parenthesis indicates it was fixed 10/28/18
yeah, saw that. seems it wasn't really fixed ... I guess ... I had to do it and I also had a newer rootfs
-
@doniks OK, I will try that as soon as I can. I wanna keep going now that I'm so close I can practically taste it, lol. I know I will have more to do once I get the GUI, for example I expect BT to not work cause I had to disable BT in the defconfig to get halium to compile successfully, but once I have a working boot I can at least go from there with it. I am thinking I'll focus on getting the device stuff that doesn't work (like BT) working then I can go from there to start working on the network based stuff (like WiFi and LTE) if needed. I am also working on a plan for a DIY dock to utilize the desktop GUI but that is a different topic for a different time.
-
@doniks so trying that didn't work, when I tried to get the logs following the FAQ my device rebooted after I issued the last command so I'm kinda stuck at this point (tried 3 times to no avail) I have a gut feeling that something isn't configured right for my device but figuring that out is gonna be very time consuming. I'll try it again tomorrow with a fresh rootfs (the merge list for edge is quite big so there may be a fix in place for that) and if it still doesn't let me do what I need I'll see what my options are.
-
@doniks I have News, I finally got the device to go past the spinner, it was a combo of my udev rules and the 32011 stuff, I now have a fully working GUI, working touchscreen, and working file access, thats about it though, the wifi is detected but it isnt finding the wifi network for some reason, Ill have to play with it in terminal I guess, as for the rest, any idea where I could start with getting the rest to work?
-
So I have been trying to get my ofono stack working, as of now it seems like the android stuff can't access its own stuff in the /proc folder.
The list of what isn't working as of this writing is:Cellular (Ofono sees the cellular modem but can't access its own folder in /proc)
Bluetooth (completely untested)
Rotation (sensors are found but no values generated)
GPS (test_gps segfaults in halium-boot but not in hybris-boot)
Audio (untested)
S-Pen (kernel sees it as a input device but disables it for some reason)
If anyone reading this has a note 4 and wants to take on any of these tests let me know your findings and I will update the list as issues are resolved. I also welcome any advice anyone may have if they read this and are not in telegram but have an idea of what's going on.
-
So I have an update for anyone following this that isn't on telegram or IRC, there are now a couple people working with me on the Note 4 port, the devices are the Sprint, the T-Mobile, and the Trltexx. We have managed to get audio somewhat working, all the hardware as far as we can tell is seen by the kernel, and we are now just trying to get everything working on the GUI side. I have switched to telegram as the primary communication method so dont expect many updates on here, if you have a galaxy note 4 and would like to contribute, you can find me on telegram in the UBPorts group, the UBPorts porting group, and the halium group.