| *** Acou_Bass <Acou_Bass!~Acou_Bass@host-89-241-253-62.as13285.net> has joined #sfdroid | 00:05 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 240 seconds) | 00:08 | |
| *** locusf <locusf!locusfdisr@gateway/shell/matrix.org/x-fgbffpjoplxzjlbj> has joined #sfdroid | 00:10 | |
| *** danPixl <danPixl!sjroijvcoi@gateway/shell/matrix.org/x-joprwvfeoonihskb> has joined #sfdroid | 00:13 | |
| *** nh1402[m] <nh1402[m]!nh1402matr@gateway/shell/matrix.org/x-ktnmdmqtoshpaksh> has joined #sfdroid | 00:13 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 00:18 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Remote host closed the connection) | 00:27 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 00:27 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Remote host closed the connection) | 00:36 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 00:39 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 260 seconds) | 00:44 | |
| *** rinigus <rinigus!~rinigus@kybi.ioc.ee> has joined #sfdroid | 05:59 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 06:50 | |
| *** TheKit <TheKit!~nekit@85-95-179-81.saransk.ru> has quit IRC (Ping timeout: 255 seconds) | 07:20 | |
| *** srohmen <srohmen!~srohmen@x4e31b0ec.dyn.telefonica.de> has joined #sfdroid | 07:20 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 248 seconds) | 07:21 | |
| *** Fantick <Fantick!~sailfish@83.220.238.104> has joined #sfdroid | 07:24 | |
| *** Fantick <Fantick!~sailfish@83.220.238.104> has quit IRC (Remote host closed the connection) | 07:27 | |
| *** Fantick <Fantick!~sailfish@83.220.238.104> has joined #sfdroid | 07:28 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 07:29 | |
| *** Fantick <Fantick!~sailfish@83.220.238.104> has quit IRC (Remote host closed the connection) | 07:30 | |
| *** Fantick <Fantick!~sailfish@83.220.238.104> has joined #sfdroid | 07:31 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.236.124> has joined #sfdroid | 07:33 | |
| *** Fantick <Fantick!~sailfish@83.220.238.104> has quit IRC (Ping timeout: 240 seconds) | 07:35 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 240 seconds) | 07:36 | |
| *** piggz_ <piggz_!~piggz@92.40.249.235.threembb.co.uk> has joined #sfdroid | 07:36 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.236.124> has quit IRC (Remote host closed the connection) | 07:58 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.236.124> has joined #sfdroid | 07:59 | |
| *** nh1402 <nh1402!~nh1402@host81-133-137-69.in-addr.btopenworld.com> has joined #sfdroid | 07:59 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.236.124> has quit IRC (Remote host closed the connection) | 08:02 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.236.124> has joined #sfdroid | 08:03 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 08:06 | |
| *** piggz_ <piggz_!~piggz@92.40.249.235.threembb.co.uk> has quit IRC (Ping timeout: 246 seconds) | 08:09 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.236.124> has quit IRC (Remote host closed the connection) | 08:26 | |
| *** Fantick <Fantick!~sailfish@83.220.236.124> has joined #sfdroid | 08:26 | |
| *** Fantick <Fantick!~sailfish@83.220.236.124> has quit IRC (Remote host closed the connection) | 08:36 | |
| *** Fantick <Fantick!~sailfish@83.220.236.124> has joined #sfdroid | 08:36 | |
| *** Fantick <Fantick!~sailfish@83.220.236.124> has quit IRC (Remote host closed the connection) | 08:47 | |
| *** Fantick <Fantick!~sailfish@83.220.236.124> has joined #sfdroid | 08:48 | |
| *** jakibaki <jakibaki!~textual@ipservice-092-217-212-051.092.217.pools.vodafone-ip.de> has quit IRC (Quit: Textual IRC Client: www.textualapp.com) | 08:54 | |
| *** jakibaki <jakibaki!~textual@ipservice-092-217-212-051.092.217.pools.vodafone-ip.de> has joined #sfdroid | 08:54 | |
| *** Fantick <Fantick!~sailfish@83.220.236.124> has quit IRC (Remote host closed the connection) | 09:02 | |
| *** Fantick <Fantick!~sailfish@83.220.236.124> has joined #sfdroid | 09:02 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.239.170> has joined #sfdroid | 09:04 | |
| *** Fantick <Fantick!~sailfish@83.220.236.124> has quit IRC (Ping timeout: 240 seconds) | 09:06 | |
| *** Mister_Magister <Mister_Magister!~mister@user-94-254-229-123.play-internet.pl> has joined #sfdroid | 09:15 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.239.170> has quit IRC (Remote host closed the connection) | 09:37 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.239.170> has joined #sfdroid | 09:38 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.239.170> has quit IRC (Remote host closed the connection) | 09:47 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.239.170> has joined #sfdroid | 09:48 | |
| *** Fantick <Fantick!~sailfish@83.220.239.201> has joined #sfdroid | 09:49 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.239.170> has quit IRC (Ping timeout: 240 seconds) | 09:52 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.237.88> has joined #sfdroid | 09:53 | |
| *** Fantick <Fantick!~sailfish@83.220.239.201> has quit IRC (Ping timeout: 240 seconds) | 09:53 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.237.88> has quit IRC (Remote host closed the connection) | 09:59 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.237.88> has joined #sfdroid | 10:00 | |
| *** Mister_Magister <Mister_Magister!~mister@user-94-254-229-123.play-internet.pl> has quit IRC (Ping timeout: 240 seconds) | 10:14 | |
| *** Mister_Magister <Mister_Magister!~mister@user-94-254-147-187.play-internet.pl> has joined #sfdroid | 10:15 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.237.88> has quit IRC (Remote host closed the connection) | 10:17 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.237.88> has joined #sfdroid | 10:17 | |
| nh1402 | saidinesh5: I had a look at how to get anbox to support touchscreen devices, on the sdl side of things it looks straight forward, android side would be merging the mouse and how touch support is done for mobiles. | 10:24 |
|---|---|---|
| nh1402 | I could give it a thwack later, but won't actually be able to test it due to obvious reasons. | 10:25 |
| nh1402 | saidinesh5: you free later today to help try and get it booting on my n5? | 10:25 |
| *** Fantick <Fantick!~sailfish@83.220.238.16> has joined #sfdroid | 10:27 | |
| saidinesh5 | nh1402: lol. i couldn't get it to boot on my xiaomi mi3 :P | 10:30 |
| saidinesh5 | i thought the best time to start it again is once the 3.18 kernel is out for my device | 10:31 |
| *** Fantick_ <Fantick_!~sailfish@83.220.237.88> has quit IRC (Ping timeout: 260 seconds) | 10:31 | |
| saidinesh5 | otherwise it seems like a pain to tinker with these things | 10:31 |
| nh1402 | saidinesh5: maybe we can help each other then | 10:34 |
| nh1402 | I can get sources and build a new image based on latest sources, you can build latest manager stuff on obs | 10:35 |
| saidinesh5 | nh1402: Sure but I think the thing to do is really wait for the 3.18 kernel.. So far all the issues i had were mainly b/c of my kernel being ooold | 10:35 |
| nh1402 | what the heck am I supposed to do, remotely fix image and anbox stuff, and hope it works on your device? | 10:36 |
| saidinesh5 | lol. no. if my device is getting a 3.10+ kernel , your device will definitely get it.. | 10:37 |
| saidinesh5 | so look for that kernel and get sailfish up and running on it.. | 10:37 |
| nh1402 | development for n5 has really slowed down on xda, I doubt it's coming | 10:37 |
| saidinesh5 | hmm.. same for my device.. all i have is a screenshot.. and that guy said he will release it along with Android O | 10:39 |
| nh1402 | saidinesh5: the only guy that was working on the 3.10 kernel stopped over a year ago... | 10:39 |
| saidinesh5 | i hope he isn't just faking it.. | 10:39 |
| *** Fantick_ <Fantick_!~sailfish@83.220.237.16> has joined #sfdroid | 10:40 | |
| nh1402 | saidinesh5: I still think it's worth getting it working on 3.4 kernel | 10:40 |
| saidinesh5 | will have to try harder i guess | 10:41 |
| *** Fantick <Fantick!~sailfish@83.220.238.16> has quit IRC (Ping timeout: 240 seconds) | 10:41 | |
| *** Fantick_ <Fantick_!~sailfish@83.220.237.16> has quit IRC (Remote host closed the connection) | 11:10 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 260 seconds) | 12:42 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 13:01 | |
| *** rinigus <rinigus!~rinigus@kybi.ioc.ee> has quit IRC (Quit: Leaving) | 13:03 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Quit: Konversation terminated!) | 13:07 | |
| *** piggz_ <piggz_!~piggz@94.197.120.90.threembb.co.uk> has joined #sfdroid | 13:30 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 13:59 | |
| *** piggz_ <piggz_!~piggz@94.197.120.90.threembb.co.uk> has quit IRC (Ping timeout: 240 seconds) | 14:02 | |
| *** jakibaki <jakibaki!~textual@ipservice-092-217-212-051.092.217.pools.vodafone-ip.de> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…) | 15:12 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Quit: Konversation terminated!) | 15:18 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 15:19 | |
| *** jakibaki <jakibaki!~textual@ipservice-092-217-212-051.092.217.pools.vodafone-ip.de> has joined #sfdroid | 15:30 | |
| *** jakibaki <jakibaki!~textual@ipservice-092-217-212-051.092.217.pools.vodafone-ip.de> has quit IRC (Ping timeout: 240 seconds) | 15:34 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 240 seconds) | 15:35 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 15:44 | |
| *** nh1402 <nh1402!~nh1402@host81-133-137-69.in-addr.btopenworld.com> has quit IRC (Quit: Leaving) | 15:48 | |
| *** rinigus <rinigus!~rinigus@keila-gw.levikom.ee> has joined #sfdroid | 15:55 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 240 seconds) | 16:14 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 16:18 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Quit: Konversation terminated!) | 16:33 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 16:33 | |
| *** jakibaki <jakibaki!~textual@ipservice-092-217-212-051.092.217.pools.vodafone-ip.de> has joined #sfdroid | 16:40 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 240 seconds) | 16:50 | |
| *** piggz <piggz!~piggz@188.29.165.35.threembb.co.uk> has joined #sfdroid | 16:51 | |
| *** NeKit <NeKit!~nekit@178.45.157.7> has joined #sfdroid | 17:04 | |
| *** NeKit <NeKit!~nekit@178.45.157.7> has quit IRC (Ping timeout: 240 seconds) | 17:19 | |
| piggz | saidinesh5: nh1402[m]: im willing to help out to get it up on the mido ... i already have the kernel parts in my build, just need to spend some time on image building. | 17:26 |
| saidinesh5 | piggz: why not use the existing anbox image from the repo? | 17:27 |
| piggz | saidinesh5: i need a 64bit image | 17:28 |
| saidinesh5 | how come? the rest of your stack is 32 bit itself right? | 17:28 |
| saidinesh5 | the image itself is self contained rootfs too.. | 17:29 |
| piggz | im sure last time I tried to boot it, the advice was to build a 64bit image... | 17:29 |
| mal | saidinesh5: do you happen to know how to capture the stdout from the anbox-init.sh script, or does that go somewhere, I tried to pipe some data to some file but without success | 17:29 |
| saidinesh5 | mal: could you check if you can even run an sh in chroot? for me that was the issue.. so before even anbox-init.sh starts.. sh was crashing inside the chroot | 17:30 |
| saidinesh5 | thereby no ... logs | 17:30 |
| saidinesh5 | piggz: Ah.. well you can try buiding the 64bit image but i think you have to ask krnlyng about the patches ... | 17:31 |
| saidinesh5 | i am not entirely sure of what patches he put in to build the anbox-image compatible with sfdroid | 17:31 |
| mal | saidinesh5: could you explain how to test a chroot | 17:32 |
| saidinesh5 | anbox itself mounts everything inside /var/lib/anbox/root iirc | 17:32 |
| saidinesh5 | try chrooting into that.. | 17:33 |
| saidinesh5 | for me chroot <path> /sbin/sh was crashing | 17:33 |
| saidinesh5 | "everything" = anbox-image + the files from your device as overlay | 17:34 |
| mal | saidinesh5: sh-3.2# chroot /var/lib/anbox/rootfs /system/bin/sh | 17:36 |
| mal | Killed | 17:36 |
| saidinesh5 | yep | 17:37 |
| saidinesh5 | that's the bit where i am stuck too | 17:37 |
| saidinesh5 | need to see why that process was getting killed | 17:37 |
| mal | saidinesh5: "Ensure that the /usr/sbin/execerror command is available on the new root file system so that descriptive error messages are returned in the event of a chroot failure. Otherwise, if there is an error, chroot returns Killed and nothing more." | 17:39 |
| saidinesh5 | (also you may get a little further if you bind mount the dev, sys etc.. into that path before chrooting) | 17:39 |
| saidinesh5 | Ohh. I will try that.. | 17:39 |
| mal | saidinesh5: looks like at least issue with /dev, strace gave: | 17:40 |
| mal | openat(AT_FDCWD, "/dev/urandom", O_RDONLY|O_LARGEFILE|O_NOFOLLOW|O_CLOEXEC) = -1 ENOENT (No such file or directory) | 17:40 |
| mal | tgkill(18315, 18315, SIGKILL <unfinished ...> | 17:40 |
| saidinesh5 | Yep.. after bind mounting that you will get a little further inside chroot | 17:40 |
| saidinesh5 | but iirc there was some weird behavior inside chroot | 17:41 |
| saidinesh5 | when trying to exec some files. | 17:41 |
| mal | saidinesh5: after bind mounting it doesn't get killed anymore | 17:43 |
| saidinesh5 | mhm. but when you try to exec files inside chroot you may see that weird behavior of processes getting killed.. | 17:44 |
| mal | what do you mean? | 17:44 |
| saidinesh5 | i will have to look at my logs, but inside chroot some commands like cd / ls were failing iirc | 17:45 |
| mal | saidinesh5: last thing in strace is "failed to resend signal during crash" | 17:46 |
| saidinesh5 | that sounds familiar... | 17:47 |
| saidinesh5 | which command was it you were trying to strace btw? | 17:47 |
| mal | saidinesh5: even just sh gives that, also ls | 17:47 |
| saidinesh5 | yep | 17:48 |
| saidinesh5 | i think something was wrong with our kernel configs/lxc flags or something. i am not exactly sure but this is where i paused the work | 17:48 |
| saidinesh5 | also ls wasn't even ls'ing all files in one attempt | 17:49 |
| mal | saidinesh5: I cannot get any output from any command | 17:50 |
| saidinesh5 | but cd should work iirc... | 17:50 |
| *** piggz <piggz!~piggz@188.29.165.35.threembb.co.uk> has quit IRC (Ping timeout: 240 seconds) | 17:50 | |
| saidinesh5 | i remember something like cd working but ls not working.. | 17:50 |
| mal | saidinesh5: actually for example ls --help gives the help info correctly | 17:50 |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 17:50 | |
| saidinesh5 | yup. ls not listing basically | 17:51 |
| mal | saidinesh5: like this chroot /var/lib/anbox/rootfs /system/bin/ls --help | 17:51 |
| saidinesh5 | Ahh | 17:51 |
| saidinesh5 | i tried it inside the chroot actually | 17:51 |
| saidinesh5 | i could start a chrooted /sbin/sh | 17:51 |
| saidinesh5 | but everything inside that shell was similar to your ls issues | 17:51 |
| saidinesh5 | i was able to cd up and down directories etc.. but not able to ls them | 17:51 |
| saidinesh5 | seemed like some namespace/permissions issue then | 17:52 |
| *** srohmen <srohmen!~srohmen@x4e31b0ec.dyn.telefonica.de> has quit IRC (Quit: Leaving.) | 17:58 | |
| mal | saidinesh5: this works chroot /var/lib/anbox/rootfs /system/bin/ls -l /vendor/ | 18:04 |
| mal | saidinesh5: ls of root does not because missing permissions probably | 18:05 |
| mal | saidinesh5: so it's not completely broken | 18:07 |
| saidinesh5 | yep. similar experience even for me | 18:08 |
| saidinesh5 | so that's how i thought that was an issue with namespaces... | 18:08 |
| saidinesh5 | mal: could you disable every non required namespace related kernel config and try? | 18:09 |
| saidinesh5 | thats one thing i wanted to do.. | 18:09 |
| saidinesh5 | in the lxc-checkconfig | 18:09 |
| saidinesh5 | basically everything that is not required, disable it.. | 18:09 |
| saidinesh5 | i have been told that lxc was very broken on 3.4 kernels.. but some OSes.. (ubports, webos etc..) run their android hal inside an lxc | 18:10 |
| saidinesh5 | even for devices with 3.4 kernel | 18:10 |
| mal | saidinesh5: yep, so it has to be possible | 18:11 |
| saidinesh5 | also disabling dev pts namespace fixed lxc from crashing for me iirc.... | 18:11 |
| saidinesh5 | yep, but iirc they wanted something like usernamespace to implement the input etc.. properly inside the container.. and they got stuck there for 3.4 kernel devices | 18:12 |
| mal | saidinesh5: I'm having a look at ubports fp2 kernel config | 18:16 |
| saidinesh5 | lucky you .. lol. i am supposed to create a kernel config for cancro for ubports too.... | 18:16 |
| mal | saidinesh5: at least they have a lot of namespaces enabled | 18:17 |
| saidinesh5 | Yep | 18:17 |
| saidinesh5 | actually i can do that too | 18:18 |
| saidinesh5 | compare the lxc checkconfig flags ... . | 18:18 |
| mal | also they use backported bt drivers | 18:18 |
| saidinesh5 | with the ones from fp2 | 18:18 |
| saidinesh5 | oh? backported from? | 18:18 |
| mal | 4.2 | 18:19 |
| saidinesh5 | oh wow.. any specific reason for that extra work? | 18:19 |
| mal | it's actually not much work, those exist readily | 18:19 |
| mal | you get bt le with those backported drivers and bluez5 | 18:20 |
| saidinesh5 | Ahh.. even for cancro a lot of the HAL is lately opensourced iirc.. gps hal, camera hal . should be worth it to take a look at them too.. | 18:21 |
| mal | saidinesh5: bt is usually just in kernel | 18:25 |
| mal | saidinesh5: quite many differences in ubports config vs my current config | 18:25 |
| saidinesh5 | mal: yup but look at just the flags related to lxc-checkconfig | 18:26 |
| mal | saidinesh5: I was talking about those | 18:26 |
| saidinesh5 | also ubports => a whole lot of other things needed by Mir, apparmour snapd, and what not | 18:26 |
| saidinesh5 | oh | 18:26 |
| saidinesh5 | so you have a point of attack then! | 18:26 |
| mal | saidinesh5: many things I have enabled are not enabled in ubports | 18:27 |
| mal | mostly cgroups | 18:27 |
| saidinesh5 | disable them all! | 18:28 |
| mal | +some network related | 18:28 |
| saidinesh5 | devpts is definitely broken on 3.4 kernel | 18:28 |
| saidinesh5 | dev pts namespace that is | 18:28 |
| mal | saidinesh5: yep, dev, memctrl and cpuset are disabled | 18:29 |
| saidinesh5 | maybe i should give this a shot too before waiting for 3.10 kernel | 18:30 |
| mal | saidinesh5: I'm now building | 18:38 |
| saidinesh5 | Aye. I will stay up.. keep me in the loop mal | 18:39 |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 240 seconds) | 18:41 | |
| *** NeKit <NeKit!~nekit@178.45.157.7> has joined #sfdroid | 18:43 | |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 18:47 | |
| mal | saidinesh5: now it fails to start to container | 18:53 |
| saidinesh5 | Ahh what does thelog say the reason as? | 18:53 |
| mal | saidinesh5: it seems to require the devices cgroup | 18:53 |
| saidinesh5 | Ahh | 18:53 |
| mal | saidinesh5: but if ubports uses lxc how do they do that | 18:54 |
| saidinesh5 | they run a very stripped down hal.. | 18:54 |
| saidinesh5 | plus you can actually use lxc and manually do the same.. with the namespaces that you need | 18:54 |
| saidinesh5 | anbox is mostly a thin wrapper around lxc + some changes to android bits to accept input/showUI / share audio | 18:55 |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 246 seconds) | 18:58 | |
| *** jakibaki <jakibaki!~textual@ipservice-092-217-212-051.092.217.pools.vodafone-ip.de> has quit IRC (*.net *.split) | 19:03 | |
| *** Mister_Magister <Mister_Magister!~mister@user-94-254-147-187.play-internet.pl> has quit IRC (*.net *.split) | 19:03 | |
| *** jakibaki <jakibaki!~textual@ipservice-092-217-212-051.092.217.pools.vodafone-ip.de> has joined #sfdroid | 19:04 | |
| *** captain42 <captain42!~captain42@unaffiliated/captain42> has quit IRC (Ping timeout: 240 seconds) | 19:05 | |
| *** Mister_Magister <Mister_Magister!~mister@user-94-254-147-187.play-internet.pl> has joined #sfdroid | 19:06 | |
| *** captain42 <captain42!~captain42@185.99.132.199> has joined #sfdroid | 19:06 | |
| mal | saidinesh5: where does the lxc configuration come from for anbox | 19:07 |
| saidinesh5 | https://github.com/sfdroid/anbox/blob/anbox/src/anbox/container/lxc_container.cpp | 19:08 |
| mal | it doesn't have the values I see in /var/lib/anbox/containers/default/config, maybe it gets the defaults from somewhere else | 19:11 |
| mal | some are set elsewhere | 19:13 |
| *** piggz <piggz!~piggz@185.175.148.15> has joined #sfdroid | 19:14 | |
| mal | saidinesh5: it's still interesting that there are no errors in lxc log about anything relevant if everything is enabled, container claims to start ok | 19:19 |
| mal | saidinesh5: container claims to start fine | 19:20 |
| saidinesh5 | Mal what about ps auxf ? | 19:21 |
| saidinesh5 | Does it show the container tree? | 19:21 |
| mal | saidinesh5: but the container shuts down because the init exits or something like that | 19:24 |
| saidinesh5 | Ah try stracing the init .. | 19:26 |
| saidinesh5 | But before that make sure chroot works like it should? | 19:26 |
| mal | saidinesh5: log even says "Started "/anbox-init.sh" | 19:26 |
| mal | saidinesh5: and then Container "default" is in "RUNNING" state. | 19:27 |
| saidinesh5 | Yeah but it could crash at the first command in anbox -init.sh right? | 19:27 |
| mal | saidinesh5: then Container init process 2440 exited | 19:27 |
| saidinesh5 | Yep. Just like normal anbox log... | 19:27 |
| mal | saidinesh5: "Failed to initialize property area" | 19:30 |
| mal | saidinesh5: that is where init fails in chroot | 19:31 |
| saidinesh5 | Ah that's bound to happen inside a chroot if you bind mount dev | 19:31 |
| *** krnlyng <krnlyng!~frajo@212095008156.public.telering.at> has joined #sfdroid | 19:31 | |
| mal | saidinesh5: ok, how to try it then? | 19:32 |
| saidinesh5 | Your droid hal outside the chroot has a device node inside related to property service.. (Android init owns that bit) | 19:32 |
| mal | saidinesh5: so now what? | 19:33 |
| saidinesh5 | I am not entirely sure. What happens if you normal mount Dev? | 19:34 |
| saidinesh5 | (before trying to look into name space for this) | 19:34 |
| mal | not sure if I understand | 19:34 |
| saidinesh5 | 1 sec looking | 19:36 |
| saidinesh5 | mal: how about just mounting a tmpfs for dev inside the chroot | 19:38 |
| saidinesh5 | and bind mounting just the needed files? | 19:39 |
| saidinesh5 | like maybe urandom etc... | 19:39 |
| mal | ok, I'll try | 19:39 |
| nh1402[m] | how do you guys even know what you're talking about | 19:39 |
| saidinesh5 | this one? https://github.com/sfdroid/anbox/blob/anbox/src/anbox/container/lxc_container.cpp#L161 | 19:41 |
| mal | saidinesh5: now it went further | 19:51 |
| saidinesh5 | define further :P | 19:51 |
| saidinesh5 | does ps auxf show the tree? | 19:51 |
| mal | saidinesh5: it tried to start some services but those failed for some reason | 19:53 |
| saidinesh5 | Ah but init survives now right? | 19:54 |
| mal | yes | 19:54 |
| saidinesh5 | ah that's a lot of progress | 19:54 |
| saidinesh5 | chances are .. the reason some of those processes failed because of some missing kernel configs for android usually | 19:54 |
| saidinesh5 | or bad permissions | 19:54 |
| saidinesh5 | when trying things with chroot i had surfaceflinger failing causing some other dependent processes failing | 19:56 |
| saidinesh5 | so chances are if you are able to fix one of the failing processes , others would start just fine | 19:56 |
| mal | saidinesh5: after some changes to the mounts it went even further, I can it continuously trying to start the services | 20:02 |
| saidinesh5 | out of curiosity, which services? | 20:04 |
| saidinesh5 | also mal you need to bind mmount dev/ion or something like that ... | 20:04 |
| saidinesh5 | afaik you find find this list in extra_bind_mounts | 20:05 |
| saidinesh5 | in /var/lib/anbox/soemwhere iirc | 20:06 |
| mal | saidinesh5: servicemanager fails for some reason but it just gives Service 'servicemanager' (pid 3980) exited with status 0 | 20:07 |
| saidinesh5 | Ahh now this is bringing back the memories from my chroot experiements... | 20:08 |
| mal | saidinesh5: pretty much all services | 20:08 |
| saidinesh5 | yeah they prolly depend on service manager for something or the other | 20:08 |
| mal | saidinesh5: yes, all others are killed it servicemanager stops | 20:09 |
| saidinesh5 | yep | 20:09 |
| saidinesh5 | i think its failing because of some missing dev node.. | 20:09 |
| saidinesh5 | look at the extra_bind_mounts file.. | 20:09 |
| saidinesh5 | that should give us some idea.. | 20:09 |
| saidinesh5 | Also iirc the crazy thing about android's init was if some critical service fails like 3-4 times it rebooted the device.. so that was a pain too.. | 20:10 |
| mal | saidinesh5: I do get some memory violations from debuggerd and healthd | 20:10 |
| saidinesh5 | Ahh | 20:10 |
| saidinesh5 | from service manager? | 20:10 |
| mal | no | 20:12 |
| saidinesh5 | hmm.. | 20:13 |
| mal | saidinesh5: probably I have done something wrong with the mounts | 20:15 |
| saidinesh5 | Maybe some mounts are missing too | 20:16 |
| saidinesh5 | Plus it could be the linker going kaput when mixing Android 7.1 rootfs with your vendor from Android 5.x? | 20:17 |
| saidinesh5 | (for the libEGL etc..) | 20:17 |
| nh1402[m] | nonsense it booted on krnlyng's Jolla C, right? | 20:19 |
| nh1402[m] | that has the same Android 5 vendor iirc | 20:19 |
| nh1402[m] | well not same same, same version of Android | 20:19 |
| krnlyng | the script that copies the data to the overlay is very cautious | 20:19 |
| krnlyng | the blobs | 20:19 |
| krnlyng | but it is maybe also broken | 20:19 |
| mal | need to continue tomorrow | 20:21 |
| saidinesh5 | nh1402[m]: iirc even krnlyng had to put in some linker hacks. And recompile some libraries | 20:21 |
| *** rinigus <rinigus!~rinigus@keila-gw.levikom.ee> has quit IRC (Quit: Leaving) | 20:22 | |
| krnlyng | yup | 20:23 |
| mal | like what? | 20:24 |
| krnlyng | mal, there were missing symbols that i redirected to abort because they were referenced but not really used | 20:26 |
| krnlyng | and iirc then there were some which were acutally called | 20:27 |
| krnlyng | which i reimplemented | 20:27 |
| krnlyng | first is linker hack | 20:27 |
| krnlyng | second is recompile some libraries | 20:27 |
| mal | krnlyng: ok, how did it behave before that? | 20:30 |
| mal | krnlyng: I mean because I cannot see anything anywhere from init | 20:30 |
| krnlyng | only surfaceflinger crashed | 20:34 |
| mal | ok | 20:35 |
| *** NeKit <NeKit!~nekit@178.45.157.7> has quit IRC (Ping timeout: 240 seconds) | 20:42 | |
| *** piggz <piggz!~piggz@185.175.148.15> has quit IRC (Ping timeout: 240 seconds) | 20:48 | |
| *** Mister_Magister <Mister_Magister!~mister@user-94-254-147-187.play-internet.pl> has quit IRC (Ping timeout: 246 seconds) | 21:07 | |
| *** jakibaki <jakibaki!~textual@ipservice-092-217-212-051.092.217.pools.vodafone-ip.de> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…) | 21:31 | |
| *** krnlyng <krnlyng!~frajo@212095008156.public.telering.at> has quit IRC (Ping timeout: 248 seconds) | 22:08 | |
| *** captain42 <captain42!~captain42@185.99.132.199> has quit IRC (Ping timeout: 246 seconds) | 22:17 | |
| *** captain42 <captain42!~captain42@185.99.132.199> has joined #sfdroid | 22:20 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!