| *** krnlyng_ <krnlyng_!~liar@178.114.138.9.wireless.dyn.drei.com> has joined #sfdroid | 00:29 | |
| *** krnlyng__ <krnlyng__!~liar@178.114.153.172.wireless.dyn.drei.com> has quit IRC (Ping timeout: 260 seconds) | 00:32 | |
| saidinesh5 | krnlyng_: any idea what maybe the cause of this issue? http://pastebin.com/RTL2pDhK | 04:11 |
|---|---|---|
| saidinesh5 | basically zygote is failing because: F/art ( 9925): art/runtime/jni_internal.cc:769] JNI FatalError called: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting... | 04:12 |
| saidinesh5 | BUT, when i grep for RuntimeInit in /system in a working CM install and inside the chroot, i get the same set of files | 04:12 |
| saidinesh5 | mal: ^ | 04:28 |
| *** krnlyng|mobile <krnlyng|mobile!~liar@47.61.102.27> has quit IRC (Ping timeout: 240 seconds) | 05:44 | |
| *** nh1402 <nh1402!~nh1402@host81-133-137-69.in-addr.btopenworld.com> has joined #sfdroid | 08:13 | |
| *** krnlyng|mobile <krnlyng|mobile!~liar@47.61.102.27> has joined #sfdroid | 08:15 | |
| *** neerad <neerad!~neerad@112.133.229.182> has joined #sfdroid | 08:47 | |
| nh1402 | saidinesh5: how's it going | 08:48 |
| saidinesh5 | nh1402: any idea on basically zygote is failing because: F/art ( 9925): art/runtime/jni_internal.cc:769] JNI FatalError called: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting... ? | 08:49 |
| saidinesh5 | but when i grep for that RuntimeInit class the same files match in both chroot and the cyanogenmod system that is working | 08:49 |
| nh1402 | saidinesh5: something to do with libnativehelper.so maybe? | 08:55 |
| saidinesh5 | looking into sfdroid patches basically to figure that out atm | 08:55 |
| saidinesh5 | but before that need to build a 2.1 build | 08:56 |
| *** krnlyng|mobile <krnlyng|mobile!~liar@47.61.102.27> has quit IRC (Remote host closed the connection) | 08:57 | |
| saidinesh5 | hbu? which arch / desktop environment did you finally pick? | 08:58 |
| nh1402 | saidinesh5: it's not me who's picking, it's whatever the laptop decides it wants to boot to | 08:59 |
| saidinesh5 | lol | 08:59 |
| saidinesh5 | and that is? | 08:59 |
| nh1402 | saidinesh5: going to try manjaro again | 08:59 |
| saidinesh5 | Ahh | 08:59 |
| saidinesh5 | do visit their IRC channel while doing so btw. | 09:00 |
| saidinesh5 | its usually a very active channel helping people out | 09:00 |
| nh1402 | the preview release with the same kernel as antergos which actually boots to the liveusb | 09:00 |
| nh1402 | but last time I tried, it didn't boot | 09:01 |
| nh1402 | but antergos with the same kernel does | 09:02 |
| nh1402 | will download and check md5 before trying this evening | 09:03 |
| saidinesh5 | nh1402: i am guessing that has to do with Nvidia | 09:03 |
| saidinesh5 | Optimus can be a bitch when it comes to things | 09:03 |
| saidinesh5 | i personally disabled my Nvidia card in Bios so i wont have to put up with it when in linux | 09:03 |
| saidinesh5 | Also iirc manjaro shipped its own patches to kernel / drivers etc.. | 09:04 |
| nh1402 | the optimus junk has been disabled in bios for over a year | 09:04 |
| saidinesh5 | Ahh | 09:04 |
| saidinesh5 | could it be some secureboot thing? | 09:05 |
| saidinesh5 | iirc only *buntu were shipping the keys | 09:05 |
| nh1402 | that's disabled too | 09:05 |
| nh1402 | so is UEFI | 09:05 |
| saidinesh5 | hmm | 09:05 |
| nh1402 | saidinesh5: how useful is the antergos channel? | 09:07 |
| saidinesh5 | never been there.. never had to though | 09:07 |
| saidinesh5 | manjaro i had to because of the optimus thing itself iirc. | 09:07 |
| saidinesh5 | nh1402: if you're trying out antergos, might as well use Arch linux channels too | 09:08 |
| saidinesh5 | it is almost vanilla arch.. plus it's custom installer | 09:08 |
| nh1402 | well the main issue is with the installer | 09:11 |
| nh1402 | If I select console, KDE, cinnamon, Gnome, xfce it just freezes permanently | 09:12 |
| nh1402 | I can force close it, but the installer then refuses to start again. | 09:12 |
| nh1402 | I checked the md5 and it's the same | 09:13 |
| saidinesh5 | Ah... i remember something similar | 09:13 |
| saidinesh5 | installer actually was doing everythign on main thread and when you crash the installer probably the lock file isnt deleted | 09:14 |
| saidinesh5 | installer's name was cinchi or something right? | 09:14 |
| nh1402 | yse | 09:14 |
| nh1402 | yes* | 09:14 |
| saidinesh5 | nh1402: next time start the installer from command line. i remember it printing out logs | 09:16 |
| saidinesh5 | or you could patiently install Arch manually :p | 09:17 |
| nh1402 | but I don't know how | 09:17 |
| nh1402 | to do either | 09:17 |
| saidinesh5 | oh there are tons of youtube videos, guides/tutorials and Arch wiki itself is the best resource on it | 09:18 |
| saidinesh5 | learned a lot from there | 09:18 |
| saidinesh5 | the installer for arch itself is very minimal. all it gives you is a shell. and expects you to read the wiki on how to partition your disk, install your arch base system into it, setup users etc.. while reading from the wiki | 09:19 |
| saidinesh5 | https://wiki.archlinux.org/index.php?title=Installation_guide&redirect=no | 09:20 |
| nh1402 | no | 09:25 |
| nh1402 | saidinesh5: any luck? | 09:59 |
| *** neerad <neerad!~neerad@112.133.229.182> has quit IRC (Ping timeout: 240 seconds) | 10:02 | |
| saidinesh5 | no | 10:11 |
| nh1402 | saidinesh5: is libnativehelper.so in the right location in the chroot system? | 10:15 |
| saidinesh5 | yup: -rwxr-xr-x 1 root root 21688 Feb 20 02:56 /usr/libexec/sfdroid/root/system/lib/libnativehelper.so | 10:16 |
| *** neerad <neerad!~neerad@112.133.229.182> has joined #sfdroid | 10:18 | |
| *** cvp <cvp!~cvp@pD9EE388F.dip0.t-ipconnect.de> has joined #sfdroid | 10:48 | |
| *** neerad <neerad!~neerad@112.133.229.182> has quit IRC (Ping timeout: 240 seconds) | 10:52 | |
| *** neerad <neerad!~neerad@112.133.229.182> has joined #sfdroid | 10:52 | |
| *** cvp <cvp!~cvp@pD9EE388F.dip0.t-ipconnect.de> has quit IRC (Read error: Connection reset by peer) | 10:56 | |
| *** cvp <cvp!~cvp@pD9EE388F.dip0.t-ipconnect.de> has joined #sfdroid | 10:56 | |
| *** neerad <neerad!~neerad@112.133.229.182> has quit IRC (Ping timeout: 260 seconds) | 10:57 | |
| *** neerad <neerad!~neerad@112.133.229.182> has joined #sfdroid | 11:10 | |
| *** neerad <neerad!~neerad@112.133.229.182> has quit IRC (Ping timeout: 268 seconds) | 11:23 | |
| *** neerad <neerad!~neerad@112.133.229.182> has joined #sfdroid | 11:35 | |
| *** neerad <neerad!~neerad@112.133.229.182> has quit IRC (Client Quit) | 11:36 | |
| *** neerad <neerad!~neerad@112.133.229.182> has joined #sfdroid | 11:36 | |
| *** Mister_Magister <Mister_Magister!~foidbgen@user-94-254-163-131.play-internet.pl> has joined #sfdroid | 13:09 | |
| nh1402 | saidinesh5: well just checked on my phone, and that looks fine, bar the permissions being rw-r--r-- | 13:22 |
| saidinesh5 | Ah hmm.. | 13:22 |
| saidinesh5 | i think it is some environment variable somewhere or something | 13:22 |
| saidinesh5 | right now updating my Sailfish to 2.1 for my device, so I will have to look into the issue after that | 13:23 |
| *** cvp <cvp!~cvp@pD9EE388F.dip0.t-ipconnect.de> has quit IRC (Remote host closed the connection) | 13:24 | |
| nh1402 | saidinesh5: interesting, I was just looking around, and in default.prop dalvik.vm.usejit=true dalvik.vm.usejitprofiles=true | 13:25 |
| saidinesh5 | i have tried by disabling them too | 13:26 |
| saidinesh5 | for an unrelated issue.. not much changed | 13:26 |
| nh1402 | what does your init.environ.rc look like? | 13:26 |
| saidinesh5 | for sfdroid? | 13:26 |
| nh1402 | yes | 13:27 |
| saidinesh5 | http://pastebin.ca/3774457 | 13:28 |
| vesim | hmmm, sfdroid working like a chroot? | 13:28 |
| saidinesh5 | vesim: i am trying to make it work within a chroot. right now sfdroid starts up with your droid-hal-init | 13:29 |
| nh1402 | saidinesh5: shouldn't ANDROID_ROOT be wherever the chroot folder is? eg. /usr/libexec/sfdroid/root/system/ | 13:30 |
| saidinesh5 | nh1402: not within the chroot. this is started from the init inside the chroot. | 13:30 |
| vesim | saidinesh5: nexus 5 is the best choice for sos and sfdroid? :P | 13:30 |
| saidinesh5 | vesim: not sure. i have a Xiaomi Mi3, which is closer to Nexus 5 in terms of specs though | 13:31 |
| saidinesh5 | although i think people have already gotten sfdroid up and running with nexus 5 | 13:31 |
| nh1402 | saidinesh5: not on the cm13 base yet, but the cm13 based image isn't even out yet | 13:33 |
| saidinesh5 | isnt it better if we directly jump to Lineage 14.1 at this point though? | 13:33 |
| saidinesh5 | when we jump that is | 13:33 |
| nh1402 | that's what I was saying, but haven't got hybris working with that yet, as far as I know. | 13:34 |
| saidinesh5 | Ahh | 13:34 |
| nh1402 | I think mal said he would try, not sure if he has had time to try yet though. I think it was mal. | 13:35 |
| saidinesh5 | 14.1 ? yup | 13:36 |
| mal | I have partially working build of hybris-14.1, need to try to fix the rest of it soon | 13:40 |
| nh1402 | saidinesh5: once I finally get a linux distro with a non-hair rippingly irritating desktop manager, I was thinking of either start working on cm13 sfdroid (the current way), jumping straight to get it working via a chroot, or try with the emulator image. | 13:41 |
| nh1402 | and I'm blaming you if I can't get any of them to work | 13:42 |
| saidinesh5 | nh1402: if you're trying within chroot, might as well update your kernel and go for lineage 14 based one | 13:42 |
| saidinesh5 | lol | 13:42 |
| saidinesh5 | my time will be a little more limited, need to prepare for more tests | 13:43 |
| nh1402 | saidinesh5: you mean rebase to 14.1 once its more than partially working, and then try chroot with lineage 14.1? | 13:44 |
| saidinesh5 | no, if you are running things inside chroot, might as well try running 14.1 inside chroot | 13:44 |
| saidinesh5 | infact the chromeos guys found that a lot easier to base it on 14, at least that's what their talk says | 13:45 |
| nh1402 | saidinesh5: are you sure that doesn't need a 14.1 compatible kernel | 13:45 |
| nh1402 | ie being rebased with it | 13:45 |
| saidinesh5 | hence the " might as well update your kernel " | 13:45 |
| saidinesh5 | chances are your 14.1 kernel will run your Sailfish OS just fine | 13:46 |
| nh1402 | which is why I was saying i would need to rebase sailfish to 14.1 | 13:46 |
| saidinesh5 | nooo.. just the kernel | 13:46 |
| saidinesh5 | not Sailfish. rebasing whole Sailfish is a lot bigger work | 13:46 |
| saidinesh5 | iirc pulseaudio had defines specific to android version. i am expecting gstdroid and ofono to have the same.. | 13:47 |
| nh1402 | saidinesh5: prove it will still work, update to a 14.1 compatible kernel and then try chroot-ing into the 12.1 image | 13:47 |
| saidinesh5 | my first version of Sailfish port was running on a CM 13 kernel back then, while the sailfish was based on 12.1 | 13:48 |
| saidinesh5 | but yeah once i get the current SFdroid to run inside the chroot, the first thing i am doing is moving it to 14.0 | 13:48 |
| nh1402 | why not 14.1 | 13:51 |
| saidinesh5 | lol 14.1 | 13:51 |
| nh1402 | saidinesh5: and then try 14.1 in an lxc container? | 13:52 |
| saidinesh5 | you mean sfdroid? | 13:53 |
| nh1402 | yes | 13:53 |
| saidinesh5 | I think lxc wont bring us any more advantages than chroot tbh.. | 13:54 |
| nh1402 | what was the other thing | 13:54 |
| nh1402 | docker or something | 13:55 |
| saidinesh5 | i thought docker was just rebranded LXC with a fancy scripting language? | 13:55 |
| nh1402 | no idea | 13:55 |
| nh1402 | so the plan is successfully boot into chroot image, update kernel, successfully boot into latest android image via chroot, and then package it in an rpm? | 13:57 |
| saidinesh5 | i already do things via. an RPM. but yes, that is the rest of the plan | 13:57 |
| saidinesh5 | with chroot, the code can be cleaned up a lot too | 13:58 |
| nh1402 | and for me, update kernel, successfully boot into latest android image via chroot, then add features, like Mister_Magister much requested notification pass through. | 13:59 |
| Mister_Magister | nh1402: i didn't requested :D | 14:00 |
| nh1402 | wait a minute. if we chroot into sfdroid wouldn't we break the dbus client server connection? | 14:00 |
| saidinesh5 | nh1402: you can piggy back on kde connect, if you want notification pass through.. so try porting kde connect first :P | 14:00 |
| saidinesh5 | nh1402: nope, i am sharing some directories (and sockets) so that resources are shared between chroot and sailfish | 14:01 |
| saidinesh5 | right now that is /tmp/sfdroid, /var, /dev I think | 14:01 |
| saidinesh5 | hooooly. that reminds me of what all i need to back up before flashing the 2.1 update | 14:01 |
| saidinesh5 | i was almost about to have done it without any back up! | 14:02 |
| nh1402 | I already know what to do, more or less for notification pass-through, no need to port kde connect | 14:02 |
| nh1402 | what I don't know how to do yet though is how to add android icons in the sailfish app drawer and launch the app (or boot to sfdroid if it hasn't already booted, and then launch the selected app) | 14:04 |
| saidinesh5 | you need some kind of service inside android for that | 14:05 |
| saidinesh5 | to listen to intents on application installed/removed and then create .desktop files in the applications directory | 14:05 |
| saidinesh5 | desktop files can launch applications using am to send an intent to open that application | 14:06 |
| nh1402 | can you use am outside of the chroot? | 14:06 |
| saidinesh5 | i think so. am seems to be working from outside chroot as it can access the same binder and sockets as the services running within chroot | 14:07 |
| saidinesh5 | if not, we will have to run a neutered adb inside chroot to listen to commands from outside via. a socket | 14:08 |
| saidinesh5 | neutered adb - so it wont hijack usb | 14:08 |
| nh1402 | I have created an app that listens for apps installs before, that also grabs the app icon, but want to do it at a lower level | 14:08 |
| nh1402 | which is much more difficult. | 14:08 |
| saidinesh5 | what do you mean lower level? | 14:08 |
| nh1402 | not at the app level | 14:08 |
| nh1402 | in the android system level | 14:09 |
| saidinesh5 | there are only activities and services inside android.. | 14:09 |
| saidinesh5 | you should just create a service that starts up at boot time and listens to these intents | 14:09 |
| nh1402 | in the package manager service is what I meant | 14:10 |
| saidinesh5 | Ah why? i mean it can work perfectly well even as a normal android service right? | 14:11 |
| saidinesh5 | the fewer the number of patches to android's source, the easier it would be to upgrade android version... | 14:12 |
| nh1402 | well you wouldn't be able to create the desktop files in the same location as sailfish as that would be outside the chroot, and you wouldn't be able to do that without root access which we don't want the user to be forced to do. | 14:13 |
| saidinesh5 | you dont need root to create a desktop file inside user's home directory | 14:13 |
| nh1402 | but don't you need the desktop files in a specific directory to be seen in Sailfish? | 14:14 |
| saidinesh5 | either /usr/share/applications or /home/nemo/somepath | 14:15 |
| nh1402 | you what, are you sure about /home/nemo/somepath | 14:15 |
| nh1402 | also you wouldn't be able to use dbus from the app level to show the notification in Sailfish | 14:16 |
| saidinesh5 | yep, i used that /home/nemo/somepath for droplet browser.. | 14:18 |
| saidinesh5 | and dbus is accessible from within android even inside chroot, if you share /var/somepath | 14:19 |
| nh1402 | yes but not at the app level | 14:20 |
| saidinesh5 | hmm? it should be available even at app level if you use jdbus or some library | 14:22 |
| saidinesh5 | plus dbus aint the only IPC. for all you want, you could be using simple unix domain sockets and still be fine | 14:22 |
| saidinesh5 | dbus is mostly for many to many communication imho. | 14:23 |
| nh1402 | prove it | 14:24 |
| nh1402 | krnlyng_: has already said that can't be done | 14:27 |
| saidinesh5 | whut? sfdroid itself uses unix domain sockets to communicate with the renderer | 14:34 |
| nh1402 | ask him | 14:34 |
| *** Mister_Magister <Mister_Magister!~foidbgen@user-94-254-163-131.play-internet.pl> has quit IRC (Ping timeout: 240 seconds) | 15:23 | |
| *** nh1402 <nh1402!~nh1402@host81-133-137-69.in-addr.btopenworld.com> has quit IRC (Quit: Leaving) | 16:28 | |
| *** Mister_Magister_ <Mister_Magister_!~foidbgen@user-94-254-163-131.play-internet.pl> has joined #sfdroid | 17:15 | |
| *** Mister_Magister_ is now known as Mister_Magister | 17:18 | |
| nh1402[m] | saidinesh5 you might be blamed soon, be prepared. | 17:27 |
| *** neerad <neerad!~neerad@112.133.229.182> has quit IRC (Ping timeout: 260 seconds) | 17:58 | |
| nh1402[m] | saidinesh5 it installed, but grub did not. | 17:58 |
| nh1402[m] | Now I can't boot to anything | 17:58 |
| nh1402[m] | You're to blame saidinesh5 | 18:07 |
| *** piggz <piggz!~piggz@2.31.1.237> has joined #sfdroid | 18:11 | |
| nh1402[m] | I've managed to fix grub but it just leads to a black screen | 18:20 |
| *** neerad <neerad!~neerad@112.133.229.182> has joined #sfdroid | 18:30 | |
| *** Mister_Magister_ <Mister_Magister_!~foidbgen@user-94-254-144-179.play-internet.pl> has joined #sfdroid | 19:25 | |
| *** Mister_Magister <Mister_Magister!~foidbgen@user-94-254-163-131.play-internet.pl> has quit IRC (Ping timeout: 256 seconds) | 19:28 | |
| *** Mister_Magister_ is now known as Mister_Magister | 19:28 | |
| saidinesh5 | nh1402[m]: blank screen because? | 19:32 |
| *** piggz <piggz!~piggz@2.31.1.237> has quit IRC (Read error: Connection reset by peer) | 19:35 | |
| *** piggz <piggz!~piggz@2.31.1.237> has joined #sfdroid | 19:35 | |
| *** miau__ <miau__!~miau@55d43b5a.access.ecotel.net> has joined #sfdroid | 19:43 | |
| miau__ | Hi! | 19:44 |
| saidinesh5 | hey miau__ | 19:45 |
| miau__ | I could use a 'little' help. | 19:46 |
| miau__ | Downloaded the complete cm13 source and now i don't know what i have to do with it :-D | 19:46 |
| saidinesh5 | first make sure you build a CM 13 zip and flash it to your device and make sure Sailfish OS works with it | 19:47 |
| neerad | replace with with appropriate branch repos of sfdroid | 19:47 |
| saidinesh5 | there are no appropriate branches in sfdroid repos for CM 13 yet, so you have to manually port patches yourself | 19:47 |
| miau__ | saidinesh5: Puh, i guess compiling cm will take a long time :-D | 19:49 |
| saidinesh5 | miau__: and getting sfdroid will take even longer :P | 19:49 |
| miau__ | saidinesh5: Ok, i build cm from source, see if sfos runs on it. Aplly the patches to the source, compile everything again and see what does not work? ;-) | 19:51 |
| saidinesh5 | not exactly | 19:51 |
| saidinesh5 | once you have your CM 13 zip working with your Sailfish OS, you have to patch specific repos and add them to your device and make sure it works | 19:52 |
| miau__ | saidinesh5: That was what i wanted to say. Ok, only 23GB of free space..think i have to clean up a little before building cm. | 19:52 |
| saidinesh5 | Oh definitely have to clean up a LOT | 19:53 |
| saidinesh5 | somewhere around 80-90GBish | 19:53 |
| saidinesh5 | probably more, since you are on CM 13 | 19:53 |
| miau__ | saidinesh5: Which repos? | 19:53 |
| *** Mister_Magister <Mister_Magister!~foidbgen@user-94-254-144-179.play-internet.pl> has quit IRC (Ping timeout: 260 seconds) | 19:54 | |
| miau__ | saidinesh5: Sounds like i have to backup my whole home partition before compiling. | 19:54 |
| saidinesh5 | miau__: luckily you can compile it in other partitions too.. | 19:54 |
| saidinesh5 | and well github.com/sfdroid/ you can find the repos in there | 19:54 |
| saidinesh5 | but they are patched for CM 12.1 mostly | 19:54 |
| saidinesh5 | https://gist.github.com/saidinesh5/3262c31c88776445544c8b2804ee02df | 19:55 |
| miau__ | saidinesh5: I only have 256GB of disk space. | 19:55 |
| saidinesh5 | me too. that's why i was using an external hard drive for sfdroid building | 19:55 |
| miau__ | Any differences in compile speed? | 19:56 |
| *** Mister_Magister <Mister_Magister!~foidbgen@user-94-254-144-177.play-internet.pl> has joined #sfdroid | 19:56 | |
| miau__ | saidinesh5: I mean between external and internal harddrive. | 20:01 |
| *** nh1402 <nh1402!~nh1402@95.150.198.70> has joined #sfdroid | 20:21 | |
| saidinesh5 | miau__: my internal 256GB is an SSD, and external is a salvaged 5400 rpm hard disk from a dead laptop .. so i dont think thats a fair question :P | 20:23 |
| saidinesh5 | (bad internet here) | 20:24 |
| *** Mister_Magister <Mister_Magister!~foidbgen@user-94-254-144-177.play-internet.pl> has quit IRC (Ping timeout: 240 seconds) | 20:25 | |
| miau__ | saidinesh5: I'll let it compile overnight and see how far it goes. | 20:25 |
| saidinesh5 | miau__: make sur eyou have at least 80-90GB freespacce | 20:26 |
| saidinesh5 | probably a lot more if you enable CCACHE | 20:26 |
| saidinesh5 | and yeah for me it took like 6-7 hours | 20:26 |
| miau__ | saidinesh5: What specs has your compile system? | 20:27 |
| saidinesh5 | Core i5 laptop , 6GB ram (i had to add like 6GB of swap file just so chromium compiles inside android source) | 20:27 |
| saidinesh5 | but the bottleneck definitely is from the slow hard disk | 20:28 |
| *** Mister_Magister <Mister_Magister!~foidbgen@user-94-254-146-134.play-internet.pl> has joined #sfdroid | 20:29 | |
| miau__ | saidinesh5: Ah, ok, then i should also be finished in about 7hours time :) | 20:29 |
| saidinesh5 | yup | 20:29 |
| saidinesh5 | miau__: it helps a lot if you trim down your cyanogenmod manifest before that though | 20:30 |
| saidinesh5 | also miau__ downloading the cyanogenmod sources itself should take a lot of time.. | 20:30 |
| *** neerad <neerad!~neerad@112.133.229.182> has quit IRC (Ping timeout: 240 seconds) | 20:31 | |
| miau__ | saidinesh5: I already forgot that before syncing the source. ICould i get rid of all the non used hardware and bionic stuff | 20:31 |
| miau__ | saidinesh5: Already got the sources. | 20:31 |
| saidinesh5 | Ahh | 20:31 |
| saidinesh5 | even if you have the sources trimming them off can be really helpful in compile speeds | 20:31 |
| miau__ | saidinesh5: Or are there any other save things to delete from manifest except unused hardware and bionic? | 20:32 |
| saidinesh5 | my CM 12.1 has around 380 repos now.. down from 540ish | 20:32 |
| saidinesh5 | yeah SDK demos, probably chromium related stuff | 20:32 |
| m01 | does anyone know if someone's working on sfdroid for Fairphone 2, or what the status is there? | 20:33 |
| miau__ | saidinesh5: Ok, thanks. Time to search for my external drive and copy the sources. | 20:33 |
| saidinesh5 | m01: iirc entil was having some issue getting it to start | 20:33 |
| m01 | (I've only heard that there were some problems with it, but don't know anything more) | 20:33 |
| *** piggz <piggz!~piggz@2.31.1.237> has quit IRC (Read error: Connection reset by peer) | 20:49 | |
| *** piggz <piggz!~piggz@2.31.1.237> has joined #sfdroid | 20:49 | |
| *** baddea <baddea!5e30875d@gateway/web/freenode/ip.94.48.135.93> has joined #sfdroid | 21:02 | |
| *** krnlyng|mobile_ <krnlyng|mobile_!~sailfish@213162068173.public.t-mobile.at> has joined #sfdroid | 21:33 | |
| *** nh1402 <nh1402!~nh1402@95.150.198.70> has quit IRC (Quit: Leaving) | 21:43 | |
| Mister_Magister | sfdroid + 1GB ram + zram how bad is that idea? | 22:02 |
| saidinesh5 | very | 22:03 |
| saidinesh5 | neerad was in the same boat btw. | 22:04 |
| Mister_Magister | i had sfdroid once without zram | 22:04 |
| saidinesh5 | Mister_Magister: which device? | 22:04 |
| saidinesh5 | Ah | 22:04 |
| Mister_Magister | As always Moto G2 | 22:04 |
| saidinesh5 | Ahh | 22:04 |
| Mister_Magister | it was really working, except lack of multitasking | 22:05 |
| Mister_Magister | :D | 22:05 |
| Mister_Magister | and like sailfishos browser and 1 android app :D no more | 22:05 |
| Mister_Magister | but people really want whatsapp :D | 22:05 |
| saidinesh5 | Ah there is sfdroid multiwindow now | 22:06 |
| Mister_Magister | saidinesh5: even with one window you can run many apps right? | 22:06 |
| saidinesh5 | yup | 22:06 |
| Mister_Magister | btw is that possible to kill surfaceflinger | 22:06 |
| Mister_Magister | ? | 22:06 |
| saidinesh5 | not that i know of | 22:06 |
| saidinesh5 | not sure much about how to stop services from android init | 22:07 |
| saidinesh5 | one more reason you should also try to get it running inside chroot :p | 22:07 |
| Mister_Magister | :v | 22:07 |
| saidinesh5 | i feel like i am quite close to that though | 22:09 |
| saidinesh5 | right now only zygote seems to be crashing | 22:10 |
| *** krnlyng|mobile_ <krnlyng|mobile_!~sailfish@213162068173.public.t-mobile.at> has quit IRC (Ping timeout: 240 seconds) | 22:20 | |
| *** krnlyng|mobile <krnlyng|mobile!~sailfish@212095007143.public.telering.at> has joined #sfdroid | 22:20 | |
| miau__ | Mister_Magister: pkill surfaceflinger? | 22:32 |
| Mister_Magister | miau__: i'm just asking | 22:33 |
| Mister_Magister | i don't have sfdroid | 22:33 |
| miau__ | Mister_Magister: Ok, that command works in sfos terminal. | 22:33 |
| saidinesh5 | miau__: that usually should just restart surfaceflinger | 22:33 |
| Mister_Magister | saidinesh5: i'm talking about that | 22:34 |
| saidinesh5 | at least thats what i remember init was doing to dying processes.. | 22:34 |
| miau__ | saidinesh5: Yes that restarts surfaceflinger. | 22:34 |
| saidinesh5 | unless it is a oneshot process | 22:34 |
| Mister_Magister | how about removing restart surfaceflinger from init.rc | 22:34 |
| saidinesh5 | you mean making it oneshot? | 22:34 |
| saidinesh5 | you can give it a shot.. | 22:34 |
| miau__ | /system/bin/stop surfaceflinger | 22:35 |
| miau__ | ? | 22:35 |
| saidinesh5 | umm... | 22:35 |
| saidinesh5 | not sure | 22:35 |
| miau__ | saidinesh5: Can not test it i don't have a working installation with sfdroid at the moment. | 22:38 |
| saidinesh5 | yeah | 22:38 |
| *** Mister_Magister <Mister_Magister!~foidbgen@user-94-254-146-134.play-internet.pl> has quit IRC (Quit: Konversation terminated!) | 23:15 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!