| *** neerad <neerad!~neerad@112.133.229.170> has quit IRC (Ping timeout: 240 seconds) | 00:40 | |
| *** jooncheol <jooncheol!~jooncheol@2.49.173.40> has quit IRC (Quit: This computer has gone to sleep) | 05:04 | |
| *** jooncheol <jooncheol!~jooncheol@2.49.173.40> has joined #sfdroid | 05:26 | |
| *** jooncheol <jooncheol!~jooncheol@2.49.173.40> has quit IRC (Client Quit) | 05:29 | |
| *** jooncheol <jooncheol!~jooncheol@2.50.177.88> has joined #sfdroid | 06:46 | |
| *** CrKit <CrKit!~nekit@176.59.117.53> has joined #sfdroid | 08:43 | |
| *** neerad <neerad!~neerad@112.133.229.170> has joined #sfdroid | 08:52 | |
| *** krnlyng_ <krnlyng_!~liar@178.114.189.90.wireless.dyn.drei.com> has joined #sfdroid | 09:17 | |
| *** krnlyng__ <krnlyng__!~liar@178.112.219.58.wireless.dyn.drei.com> has quit IRC (Ping timeout: 258 seconds) | 09:20 | |
| *** cvp[Mobile] <cvp[Mobile]!~sailfish@x59cc8b85.dyn.telefonica.de> has quit IRC (Ping timeout: 252 seconds) | 09:24 | |
| *** horuxan <horuxan!~horuxanxx@201.46.189.63> has quit IRC (Ping timeout: 240 seconds) | 10:32 | |
| *** horuxan <horuxan!~horuxanxx@201.46.189.63> has joined #sfdroid | 10:35 | |
| *** neerad <neerad!~neerad@112.133.229.170> has quit IRC (Quit: Leaving) | 12:00 | |
| *** neerad <neerad!~neerad@112.133.229.170> has joined #sfdroid | 12:00 | |
| neerad | Okay tell me the exact and correct procedure to make sfdroid, the one which will work with less glitches. | 12:07 |
|---|---|---|
| *** cvp <cvp!~cvp@dslb-178-000-012-103.178.000.pools.vodafone-ip.de> has joined #sfdroid | 12:09 | |
| *** mp107 <mp107!~mp107@user-94-254-163-26.play-internet.pl> has joined #sfdroid | 12:32 | |
| neerad | How to make sfdroid ? Please tell me anybody who has successfully built sfdroid | 12:32 |
| *** mp107 <mp107!~mp107@user-94-254-163-26.play-internet.pl> has quit IRC (Remote host closed the connection) | 12:33 | |
| *** mp107 <mp107!~mp107@user-94-254-163-26.play-internet.pl> has joined #sfdroid | 12:34 | |
| neerad | mal: Does your sfdroid works? If yes how did you do it, tell me from the very beginning | 12:34 |
| mal | when someone manages to make a working method for building I think we should create a repo for sfdroid which would contain Android.mk with a sfdroid target so we could just use "make sfdroid" | 12:35 |
| neerad | yes that makes life way much easier | 12:35 |
| mal | neerad: it doesn't work anymore, it used work partially a long time ago but not right now | 12:35 |
| neerad | krnlyng_: I think you have successfully installed and ran sfdroid, how did you do it? | 12:36 |
| neerad | mal: How is that possible? It worked and stopped working? App crash or android just wont start | 12:36 |
| neerad | kimmoli: Same question... How did you do it? Tell me from top down | 12:37 |
| mal | neerad: I changed to rebased repos made by someone else and haven't gotten those to work | 12:37 |
| neerad | mal: okay | 12:38 |
| mal | neerad: there is a script by kimmoli in channel logs | 12:38 |
| neerad | and that works | 12:38 |
| neerad | *? | 12:38 |
| mal | not sure | 12:38 |
| mal | neerad: I think if you build whole android it should probably work? | 12:38 |
| neerad | mal:Which files should I install and which shouldn't I how would I know? | 12:39 |
| neerad | mal: Or are you saying building the whole android but copying only those specific files mentioned by saidinesh5 and/or kimmoli or krnlyng_ should work | 12:40 |
| saidinesh5 | mal: yeah i was building it using sfdroid.mk itself btw. | 12:40 |
| neerad | saidensh5:sfdroid.mk but it isn't there in the repos | 12:41 |
| saidinesh5 | i didnt publish those changes yet | 12:41 |
| saidinesh5 | i am still trying to get it via. chroot remember? | 12:41 |
| neerad | saidinesh5:oh yeah | 12:41 |
| neerad | saidinesh5: Services are still failing I guess | 12:42 |
| saidinesh5 | the last issue i remembered was init was somehow wiping out my bind mounted /dev/ | 12:42 |
| mal | neerad: yes, I meant build the whole android and then extract the needed files and package those | 12:42 |
| neerad | mal: Yeah I got that | 12:42 |
| neerad | saidiensh5: How is krnlyng_ and kimmoli made it work but others can't is it device specific? | 12:43 |
| mal | neerad: make sure it builds the dbus repo also | 12:43 |
| neerad | mal: Yep it made that too I added the sfdroid repos to the local_manifest file of my CyanogneMod_12.1 dir | 12:43 |
| mal | neerad: the patches might be device specific sometimes | 12:43 |
| saidinesh5 | well it depends.. their how their base init files were | 12:44 |
| neerad | mal,saidinesh5: Well that's fuckin' crazy and might be the reason for sfdroid_renderer failure | 12:44 |
| saidinesh5 | renderer would usually fail if other services aren tstarting | 12:44 |
| neerad | saidinesh5: Yeah I have seen that but have not been able to debug those | 12:45 |
| saidinesh5 | yeah but you know at least what you should be looking at now | 12:45 |
| neerad | mal: I would try to build the whole of android and copy those files and see if it works, although I am skeptical it might not. | 12:46 |
| neerad | saidinesh5: Yea that's one step forward | 12:47 |
| mal | there was some bug I found in the repos | 12:47 |
| neerad | mal: What bugs? | 12:47 |
| mal | some typoe somewhere | 12:47 |
| saidinesh5 | is it fixed? | 12:48 |
| neerad | mal:which dir? | 12:48 |
| neerad | mal: and yeah is it fixed? | 12:48 |
| mal | nope, I have it only lically | 12:48 |
| saidinesh5 | Ahh | 12:49 |
| neerad | ohh | 12:49 |
| mal | http://pastebin.com/EMBqSQZN to frameworks/base | 12:49 |
| mal | saidinesh5: neerad ^ | 12:50 |
| saidinesh5 | yeah looking | 12:50 |
| mal | https://github.com/sfdroid/android_frameworks_base/commit/76b9994afecba9758159916cdff306b63e5f5b15 | 12:50 |
| mal | that is the faulty patch | 12:50 |
| neerad | mal: Yep | 12:51 |
| mal | quite obvious mistake | 12:51 |
| saidinesh5 | Ah not sure if it affects the chroot issue | 12:52 |
| neerad | mal: So have you tested that commit? | 12:52 |
| neerad | Somehow that faulty commit made the oneplus-onyx and mako run sfdroid | 12:54 |
| neerad | It won't be a start-up issue I guess. | 12:54 |
| neerad | mal: One more question if I build the whole android so do I use the kernel config for SFOS or just the default kernel config | 12:56 |
| saidinesh5 | doesn't matter | 12:57 |
| saidinesh5 | unless you plan on running that kernel on some kind of emulator/vm.. | 12:57 |
| neerad | saidinesh5: So none of the patched files is dependent on kernel config | 12:58 |
| saidinesh5 | you wont be shipping a kernel at all | 12:58 |
| neerad | saidinesh5: Yeah I know but will it affect the files I will be shipping? | 12:58 |
| saidinesh5 | nope | 12:58 |
| neerad | saidinesh5: You sure? | 12:59 |
| saidinesh5 | yup | 12:59 |
| neerad | saidinesh5: Okay then building it wish me luck. | 12:59 |
| saidinesh5 | (Y) | 12:59 |
| *** nh1402 <nh1402!~nh1402@host81-133-137-69.in-addr.btopenworld.com> has joined #sfdroid | 13:00 | |
| mal | neerad: saidinesh5 but if you look at the commit you can clearly see there is bug | 13:00 |
| neerad | saidinesh5: Is there a difference if I use sfdroid repo files directly or use CyanogenMod repo and patch it | 13:00 |
| neerad | saidinesh5: Does it make a difference? | 13:01 |
| saidinesh5 | i was using sfdroid repos directly (hence my local manifest) | 13:01 |
| neerad | saidinesh5: Yeah but would it affect the files? | 13:01 |
| saidinesh5 | sfdroid repos ARE cyanogenmod repos with the patches applied. at least for onyx | 13:02 |
| neerad | saidinesh5: yeah I am using onyx branch tree | 13:02 |
| saidinesh5 | mal: btw. where do i find code for droid-hal-init? | 13:02 |
| saidinesh5 | neerad: there is a sfdroid-12.1YOG7D branch too. now. you can look into that | 13:03 |
| mal | saidinesh5: that is just patched android init, in https://github.com/mer-hybris/android_system_core/tree/hybris-12.1/init | 13:03 |
| neerad | saidinesh5: and both onyx and sfdroid12.1YOG7D are even | 13:03 |
| mal | neerad: sfdroid-12.1YOG7D was made from onyx branch by me | 13:04 |
| neerad | mal: I know you told us about that | 13:04 |
| saidinesh5 | interesting: https://github.com/mer-hybris/android_system_core/blob/b06e8773ee1cb9b8400e472ca72d8dacda92f3e2/init/init.c#L1064 | 13:06 |
| saidinesh5 | so this is what's nuking my dev dir apparently | 13:06 |
| saidinesh5 | (i was bind mounting dev, devpts, sockets) | 13:07 |
| mal | saidinesh5: could be, maybe try patching init | 13:07 |
| saidinesh5 | yeah .. | 13:07 |
| saidinesh5 | I am tempted to simply reuse droid-hal-init at the moment | 13:09 |
| saidinesh5 | has the patch to even use the proper log dir | 13:09 |
| saidinesh5 | i should be studying damn | 13:09 |
| *** neerad <neerad!~neerad@112.133.229.170> has quit IRC (Ping timeout: 240 seconds) | 13:12 | |
| *** mp107 <mp107!~mp107@user-94-254-163-26.play-internet.pl> has quit IRC () | 13:12 | |
| saidinesh5 | interesting.. now i get a segfault | 13:16 |
| *** mp107 <mp107!~mp107@PC-109-125-232-42.wegrow.domtel.com.pl> has joined #sfdroid | 13:17 | |
| *** neerad <neerad!~neerad@112.133.229.170> has joined #sfdroid | 13:21 | |
| neerad | How is /data/dalvik-cache/arm/ created ? Any ideas? | 13:21 |
| saidinesh5 | why not boot into cyanogenmod to create it? | 13:26 |
| saidinesh5 | i am guessing it has to deal with dex2opt or some such tool | 13:26 |
| neerad | Actually when I booted to cyanogenmod that dir was present but when I clean flashed SFOS it isn't created? | 13:26 |
| saidinesh5 | during the "optimizing application" phase | 13:27 |
| neerad | yep | 13:27 |
| saidinesh5 | define clean flashed? | 13:27 |
| neerad | I guess that is the problem | 13:27 |
| neerad | yes | 13:27 |
| saidinesh5 | you wiped /data before flashing sfos? | 13:27 |
| neerad | Removing everything | 13:27 |
| neerad | yes except /media | 13:27 |
| saidinesh5 | Ah | 13:27 |
| saidinesh5 | well just fastboot boot boot.img | 13:28 |
| saidinesh5 | also you wont have to do a clean flash for sfos to boot | 13:28 |
| neerad | boot.img is the SFOS kernel right? | 13:28 |
| saidinesh5 | no. android boot.img | 13:28 |
| neerad | oh i see | 13:28 |
| neerad | But how would SFOS boot then? | 13:28 |
| saidinesh5 | reboot? | 13:29 |
| saidinesh5 | fastboot boot simply boots . wihtout flashing | 13:29 |
| neerad | no without sfos kernel how would sfos boot up? | 13:29 |
| saidinesh5 | fastboot boot doesnt touch your sfos kernel | 13:30 |
| neerad | oh yeah jesus you said fastboot boot not fastboot flash sorry my bad | 13:31 |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has joined #sfdroid | 13:34 | |
| *** neerad <neerad!~neerad@112.133.229.170> has quit IRC (Ping timeout: 240 seconds) | 13:36 | |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has quit IRC (Client Quit) | 13:38 | |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has joined #sfdroid | 13:38 | |
| neerad_ | make: *** No rule to make target `/home/neerad/CyanogenMod_12.1/out/target/common/obj/JAVA_LIBRARIES/qcmediaplayer_intermediates/classes.jar', needed by `/home/neerad/CyanogenMod_12.1/out/target/common/obj/PACKAGING/boot-jars-package-check_intermediates/stamp'. Stop. | 14:02 |
| neerad_ | how to solve this error | 14:03 |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has quit IRC (Ping timeout: 258 seconds) | 14:26 | |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has joined #sfdroid | 14:38 | |
| *** CrKit <CrKit!~nekit@176.59.117.53> has quit IRC (Ping timeout: 255 seconds) | 15:09 | |
| *** CrKit <CrKit!~nekit@85-95-187-85.saransk.ru> has joined #sfdroid | 15:24 | |
| saidinesh5 | neerad_: add that to your manifest and sync | 15:52 |
| neerad_ | saidinesh5: add what? | 15:52 |
| saidinesh5 | see what provides qcmediaplayer | 15:52 |
| neerad_ | saidinesh5: okay | 15:53 |
| neerad_ | you can see it is some boot-jars-package-check | 15:53 |
| *** mp107 <mp107!~mp107@PC-109-125-232-42.wegrow.domtel.com.pl> has quit IRC (Ping timeout: 240 seconds) | 16:14 | |
| *** jooncheol <jooncheol!~jooncheol@2.50.177.88> has quit IRC (Quit: This computer has gone to sleep) | 16:17 | |
| *** nh1402 <nh1402!~nh1402@host81-133-137-69.in-addr.btopenworld.com> has quit IRC (Quit: Leaving) | 16:27 | |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has quit IRC (Ping timeout: 240 seconds) | 16:28 | |
| *** phlixi <phlixi!~phlixi@ppp-93-104-77-156.dynamic.mnet-online.de> has quit IRC (Read error: Connection reset by peer) | 16:37 | |
| *** phlixi <phlixi!~phlixi@ppp-93-104-77-156.dynamic.mnet-online.de> has joined #sfdroid | 16:37 | |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has joined #sfdroid | 16:42 | |
| *** cvp <cvp!~cvp@dslb-178-000-012-103.178.000.pools.vodafone-ip.de> has quit IRC (Remote host closed the connection) | 18:06 | |
| *** NeKit <NeKit!~nekit@85-95-187-85.saransk.ru> has quit IRC (Remote host closed the connection) | 18:30 | |
| neerad_ | which commit from which branch should I incorporate in frameworks/av | 18:33 |
| neerad_ | there is no oneplus_onyx or sfdroid12.1YOG7D in frameworks/av | 18:34 |
| saidinesh5 | ignore av for now | 18:34 |
| saidinesh5 | first you need to get sfdroid up and running | 18:34 |
| neerad_ | ignore? | 18:34 |
| neerad_ | okay | 18:34 |
| neerad_ | Does make command automatically makes libdbus and sfdroid_sensors and sharebuffer too | 18:37 |
| saidinesh5 | depends on what you're making | 18:39 |
| neerad_ | It's making all | 18:39 |
| neerad_ | command is make -j10 | 18:39 |
| saidinesh5 | did you add PRODUCT_PACKAGES += \ dbus sharebuffer.default sfdroid_sensors.default to your $DEVICE.mk ? | 18:40 |
| saidinesh5 | did you add PRODUCT_PACKAGES += dbus sharebuffer.default sfdroid_sensors.default to your $DEVICE.mk ? | 18:40 |
| neerad_ | nope | 18:40 |
| neerad_ | okay I got your point | 18:40 |
| neerad_ | I will make it separately | 18:41 |
| saidinesh5 | Yeah | 18:41 |
| neerad_ | BOOT_JAR_PACKAGE needs something to be included? | 18:42 |
| neerad_ | does* | 18:42 |
| saidinesh5 | not sure | 18:42 |
| neerad_ | what does your device.mk show? | 18:43 |
| saidinesh5 | i wrote a custom sfdroid.mk and added it to vendor-setup | 18:43 |
| saidinesh5 | https://paste.kde.org/porihyxps | 18:43 |
| saidinesh5 | so it shows up in my lunch menu too | 18:44 |
| saidinesh5 | btw. if youre building CyanogenMod, enable your ccache before you start | 18:44 |
| saidinesh5 | chances are you will be iterating over this process like 5-10 times before getting it right | 18:44 |
| neerad_ | yeah I enabled it | 18:44 |
| neerad_ | so you made it seperately that's cool and made the work easier | 18:46 |
| neerad_ | BTW did your chroot problem got solved? | 18:46 |
| saidinesh5 | nope. droid-hal-init is crashing inside chroot | 18:46 |
| neerad_ | init? | 18:46 |
| saidinesh5 | and gdb was giving me no backtraces | 18:46 |
| neerad_ | What does the logcat show? | 18:47 |
| saidinesh5 | init nukes /dev/ .. so the whole device needs a reboot if you want to use it again | 18:47 |
| saidinesh5 | (i was bind mounting /dev/ with the one in my SFOS, keeping my init.rc to a minimum) | 18:47 |
| saidinesh5 | plus afaik init needs to be patched to use the correct log location too | 18:48 |
| neerad_ | Yeah it needs to be patched for more than that | 18:48 |
| mal | saidinesh5: want to share your sfdroid.mk you told about | 18:48 |
| neerad_ | mal: He shared it above | 18:48 |
| saidinesh5 | mal: https://paste.kde.org/porihyxps | 18:48 |
| saidinesh5 | just imports genericdevice notelephony | 18:48 |
| mal | saidinesh5: does that work fine? I mean the built sfdroid? | 18:49 |
| saidinesh5 | sfdroid gets built that way, but i am still unable to start it | 18:49 |
| saidinesh5 | still trying to figure out why | 18:49 |
| neerad_ | saidinesh5: I guess init has to do with that | 18:49 |
| mal | saidinesh5: have you tried without chroot? | 18:50 |
| neerad_ | becuase it controls service loading and permissions too | 18:50 |
| saidinesh5 | mal: in the beginning yes. afaik it wasn't starting. and every time i try out sfdroid, it nukes my dalvik-cache .. so i had to put up with the "optimizing app" screen everytime i boot into android | 18:51 |
| neerad_ | Saidinesh5: I guess not starting up might be the problem in ART and dalvik-cache | 18:51 |
| saidinesh5 | that's why tryinng out chroot because i dont have to deal with device reboots etc.. | 18:51 |
| saidinesh5 | at least fewer overheating | 18:52 |
| neerad_ | That aside but did you try without chroot did it boot up? | 18:52 |
| saidinesh5 | i tried without chroot . but it didnt boot at all. | 18:53 |
| neerad_ | Which device btw saidinesh5? | 18:53 |
| saidinesh5 | Xiaomi Mi3.. (and Mi4 from Nokius) | 18:53 |
| neerad_ | Xiaomi Redmi 2 | 18:53 |
| saidinesh5 | yup | 18:53 |
| neerad_ | oh yeah silly me cancro .... *hmph* | 18:54 |
| saidinesh5 | btw. mal neerad_ : https://paste.kde.org/pimhtuqsg spec file to package whole of sfdroid | 18:54 |
| saidinesh5 | except vendor/ for obvious reasons | 18:55 |
| neerad_ | https://paste.kde.org/prmkwaoin Is it different from this? | 18:56 |
| saidinesh5 | neerad_: your link is what i used when i wasnt trying it with chroot | 18:57 |
| saidinesh5 | now with chroot i am packing a whole rootfs into the rpm | 18:57 |
| saidinesh5 | https://paste.kde.org/pqoigk2zr this is how i am starting the chroot btw. | 18:57 |
| neerad_ | I guess I might also try with chroot too, see if it works | 18:58 |
| neerad_ | because without chroot sfdroid won't even show it's face | 18:59 |
| saidinesh5 | yeah without chroot the debugging was becoming a nightmare.. | 18:59 |
| saidinesh5 | the logcat disappears by the time my device boots up | 18:59 |
| saidinesh5 | neerad_: if you want to try out chroot, you need to patch your init | 19:00 |
| neerad_ | What lines should I add/remove? | 19:00 |
| neerad_ | The one you provided | 19:00 |
| neerad_ | Paste you patched init | 19:01 |
| neerad_ | BTW saidinesh5 I disabled DEX_PREOPT will it make a difference? | 19:02 |
| saidinesh5 | no clue | 19:03 |
| neerad_ | or USE_DEXPREOPT i guess something like that DEX pre optimization | 19:03 |
| neerad_ | It increases system image size | 19:03 |
| saidinesh5 | neerad_: i didnt patch my init yet. but you can look into the patches made to the commits: https://github.com/sfdroid/android_frameworks_base/commit/76b9994afecba9758159916cdff306b63e5f5b15 | 19:03 |
| neerad_ | however making the android slow | 19:03 |
| neerad_ | saidinesh5: Does logcat shows boot.art being installed in your system when you fire up sfdroid? | 19:08 |
| neerad_ | Paste your logcat after your sfdroid fails to launch | 19:09 |
| saidinesh5 | there is no logcat as my /dev/ is nuked | 19:09 |
| saidinesh5 | actually even my scoket connection was terminated iirc | 19:09 |
| neerad_ | Debugging just got fucked up | 19:10 |
| neerad_ | and without chroot does logcat run? | 19:10 |
| saidinesh5 | without chroot, my logcat is filled with messages from boot time | 19:10 |
| neerad_ | nothing with sfdroid messages? | 19:10 |
| neerad_ | strange :O | 19:10 |
| saidinesh5 | cant remember, but it was a long time ago | 19:11 |
| neerad_ | Just try it out and see if it contains boot.art message in it.... | 19:11 |
| saidinesh5 | can't at the moment. need to set everything up for that | 19:11 |
| saidinesh5 | right now i compiled things to work as if it is in chroot | 19:12 |
| neerad_ | okay | 19:12 |
| neerad_ | dmesg is useless i guess it just contains virtual input being loaded and all | 19:12 |
| *** NeKit <NeKit!~nekit@85-95-187-85.saransk.ru> has joined #sfdroid | 19:12 | |
| saidinesh5 | most of the debugging for sfdroid, youll need logcat | 19:13 |
| neerad_ | i know | 19:14 |
| saidinesh5 | mal: droid-hal-init is linked with glibc or bionic? | 19:14 |
| mal | saidinesh5: it's built in make hybris-hal | 19:14 |
| mal | so I assume bionic | 19:15 |
| saidinesh5 | so bionic.. right? | 19:15 |
| saidinesh5 | hmm | 19:15 |
| saidinesh5 | (gdb) bt | 19:15 |
| saidinesh5 | #0 0x00009150 in ?? () | 19:15 |
| saidinesh5 | #1 0x00000000 in ?? () | 19:15 |
| saidinesh5 | not at all helpful while debugging it | 19:15 |
| neerad_ | no info | 19:15 |
| saidinesh5 | neerad_: i am beginning to think you need to even compile patched bionic if you want chroot | 19:18 |
| saidinesh5 | especially for the /dev/log vs. /dev/alog | 19:18 |
| neerad_ | sfdroid repos do have android_bionic but is it patched for chroot? I haven't seen it yet | 19:18 |
| saidinesh5 | i actually didnt notice android_bionic in there | 19:21 |
| saidinesh5 | but i meant the patches from mer-hybris | 19:22 |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has quit IRC (Read error: Connection reset by peer) | 19:31 | |
| krnlyng_ | saidinesh5, android_bionic was only needed for mako cm10 | 19:42 |
| saidinesh5 | krnlyng_: Ahh.. i was trying to run a separate init in a chroot.. and the droid-hal-init was segfaulting for me | 19:43 |
| saidinesh5 | so wanted to see what all bionic changes it needs | 19:43 |
| saidinesh5 | (trying to run a stripped down init.rc with services needed by sfdroid in chroot.) | 19:44 |
| saidinesh5 | oddly i dont have /dev/alog directory at all | 19:44 |
| krnlyng_ | saidinesh5, if you're bind mounting /dev and so on, then you need to patch init | 19:44 |
| saidinesh5 | krnlyng_: yup. learned it the hardway | 19:45 |
| saidinesh5 | krnlyng_: can i just run ueventd once more, and not bindmount /dev ? | 19:45 |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has joined #sfdroid | 19:48 | |
| krnlyng_ | saidinesh5, i am not 100% sure but on harmattandroid we just ran ueventd whilst harmattan was running | 19:50 |
| krnlyng_ | so it might be possible | 19:50 |
| saidinesh5 | interesting | 19:50 |
| neerad_ | krnlyng_: So you used chroot or non-chroot to run sfdroid? | 19:51 |
| krnlyng_ | neerad_, non-chroot | 19:51 |
| neerad_ | krnlyng_: okay tell me the exact procedure from top down to bottom detailed how to build sfdroid | 19:52 |
| krnlyng_ | neerad_, patch everything build modified libs copy to your device, build sfdroid_renderer | 19:53 |
| krnlyng_ | modify init.rc | 19:53 |
| neerad_ | krnlyng_: and does building sfdroid_renderer depend upon device-specific files/dirs? | 19:53 |
| krnlyng_ | neerad_, yes, but if the api is not different you can use sfdroid_renderer from a different device. mako and hammerhead were compatible | 19:54 |
| neerad_ | krnlyng_: I guess that is the reason it is failing in my device | 19:54 |
| krnlyng_ | neerad_, what have you done so far and where does it fail? | 19:55 |
| neerad_ | krnlyng_: Did you made the whole android sources or only the patched ones? | 19:55 |
| krnlyng_ | neerad_, usually i build everything once and check whether it is compatible with sfos then start patching | 19:55 |
| neerad_ | krnlyng_: You mean you built the whole of android sources for sfdroid | 19:56 |
| neerad_ | krnlyng_: okay that might be another reason for failure | 19:56 |
| neerad_ | krnlyng_: logcat shows there is no /data/dalvik-cache/arm dir does it sound familiar? | 19:57 |
| neerad_ | krnlyng_: although i checked there is /data/dalvik-cache/profiles folder | 19:57 |
| krnlyng_ | neerad_, check where this folder is first created | 19:58 |
| neerad_ | krnlyng_: there is no mention does patched init.rc contains it ? | 19:58 |
| krnlyng_ | no | 19:59 |
| neerad_ | krnlyng_: So how to debug this then? | 19:59 |
| krnlyng_ | if it is not in original init.rc it is also not in sfdroid init.rc | 19:59 |
| neerad_ | krnlyng_:hmmm okay got it | 19:59 |
| krnlyng_ | neerad_, find the place where the folder should be created | 19:59 |
| neerad_ | krnlyng_:well obviously I tried to create the folder myself and the issue was resolved but another one popped in | 20:00 |
| krnlyng_ | neerad_, which issue? | 20:00 |
| neerad_ | krnlyng_: That somehow zygote was not running "Error was that only zygote is allowed to create boot image" | 20:01 |
| krnlyng_ | neerad_, and try to find the problem with the folder don't just create it.. | 20:01 |
| krnlyng_ | maybe you created the folder with the wrong permissions | 20:01 |
| neerad_ | krnlyng_: I felt so but how to correct it and I will later find how that folder is not created | 20:02 |
| neerad_ | krnlyng_: BTW is that folder created with sfos or is it just created when sfdroid runs? | 20:02 |
| krnlyng_ | neerad_, i am not 100% sure but i think permissions should be 0771 system system | 20:02 |
| neerad_ | okay I will chown that | 20:02 |
| krnlyng_ | neerad_, that folder has nothing to do with sfos | 20:02 |
| neerad_ | krnlyng_: List the files which needed to be copied to the device | 20:03 |
| neerad_ | krnlyng_: I am reconfirming only | 20:03 |
| krnlyng_ | neerad_, https://www.dropbox.com/sh/4ywnxsbifqguvuq/AACy8Q3Cmr-mbDVLWXDZXDUja?dl=0 | 20:04 |
| krnlyng_ | neerad_, check the contents | 20:04 |
| neerad_ | krnlyng_: I am building the whole android sources and building sfdroid_renderer too. Let's see where it gets me. | 20:06 |
| neerad_ | krnlyng_: One last query, how to build sfdroid_renderer rpm pckg? | 20:06 |
| krnlyng_ | neerad_, you need to build the android sources with sfdroid patches | 20:06 |
| neerad_ | Yeah I included them in my local_manifest | 20:06 |
| neerad_ | So they are patched and I guess device independent too.... I selected oneplus-onyx branch for all of them except frameworks_av which I guess is non-relevant at this point. | 20:08 |
| neerad_ | krnlyng_: How to build sfdroid_renderer ? In sb2 I guess? | 20:09 |
| krnlyng_ | mal, is libhardware device dependant? or does it just include the device specific headers from a different place? otherwise it will probably break | 20:13 |
| krnlyng_ | neerad_, mb2 build | 20:13 |
| neerad_ | well it fails | 20:13 |
| neerad_ | DEP error | 20:13 |
| mal | krnlyng_: I think it might be device specific, not sure | 20:16 |
| saidinesh5 | okay copying the libc.so from droid-hybris made half the crashes stop | 20:17 |
| neerad_ | saidinesh5: Great news | 20:17 |
| saidinesh5 | vold, lmkd, debuggerd, mediaserver are running | 20:18 |
| saidinesh5 | plus ueventd.. | 20:18 |
| neerad_ | saidinesh5: what all remains? | 20:18 |
| saidinesh5 | netd, surfaceflinger | 20:18 |
| saidinesh5 | let me reboot | 20:20 |
| neerad_ | cool let us know | 20:20 |
| saidinesh5 | when i did a Ctrl C, there was an issue | 20:20 |
| saidinesh5 | only init was killed and not the subprocesses | 20:20 |
| neerad_ | Reboot and see. | 20:20 |
| saidinesh5 | krnlyng_: btw. what's the powerup binary for? | 20:22 |
| saidinesh5 | i mean is the power key press necessary? | 20:22 |
| krnlyng_ | saidinesh5, it's a silly hack | 20:22 |
| krnlyng_ | and yes it is necessary | 20:22 |
| saidinesh5 | but where is it necessary? | 20:22 |
| krnlyng_ | android goes to sleep | 20:22 |
| krnlyng_ | and touch inputs don't wake it up | 20:22 |
| saidinesh5 | Ahhh | 20:22 |
| saidinesh5 | I see | 20:22 |
| krnlyng_ | => power up event | 20:22 |
| saidinesh5 | odd. i only see ueventd and healthd | 20:24 |
| neerad_ | saidinesh5: Does logcat works? | 20:26 |
| saidinesh5 | not sure actually | 20:26 |
| saidinesh5 | i am guessing it works | 20:26 |
| neerad_ | saidinesh5: If it works check for boot.art and let me know | 20:26 |
| saidinesh5 | no such messages yet | 20:27 |
| neerad_ | saidinesh5: sfdroid running ? | 20:27 |
| saidinesh5 | without surfaceflinger it wont run | 20:27 |
| neerad_ | saidinesh5: But no boot.art mssg? | 20:28 |
| saidinesh5 | nope | 20:28 |
| neerad_ | Paste you logcat after sfdroid run | 20:28 |
| saidinesh5 | nothing at all/ nothing interesting | 20:31 |
| neerad_ | saidinesh5: Nothing related to sfdroid? | 20:32 |
| saidinesh5 | yep | 20:32 |
| neerad_ | saidinesh5: :O | 20:32 |
| neerad_ | saidinesh5: strace it might be helpful, I am not sure | 20:32 |
| saidinesh5 | nah this time vold, mediaservice didnt start | 20:32 |
| neerad_ | saidinesh5: rebooting it failed it??? | 20:33 |
| saidinesh5 | it didnt work much | 20:33 |
| neerad_ | saidinesh5: I think you must try to debug in non-chroot might be more helpful than doing it in chroot. Give it a shot when you get time. | 20:34 |
| saidinesh5 | nope. without chroot debugging is actually harder | 20:34 |
| saidinesh5 | logcat disappears soon | 20:34 |
| saidinesh5 | plus all the device reboots overheat the device in like 15 minutes | 20:35 |
| saidinesh5 | with chroot, at least i can start and stop things as i see fit | 20:35 |
| neerad_ | saidinesh5: You have got some issues with chroot I guess. Nobody needed chroot afaik. | 20:35 |
| saidinesh5 | even without chroot it wasnt working for me | 20:36 |
| saidinesh5 | might as well try to make it work in an environment i have more control over.. | 20:36 |
| neerad_ | saidinesh5: It might be chroot is causing more trouble. | 20:37 |
| saidinesh5 | sure, like the trouble with needing patched bionic etc.. | 20:37 |
| saidinesh5 | but with chroot i can "start and stop" sfdroid when needed | 20:38 |
| neerad_ | saidinesh5: Yeah exactly additional shits. | 20:38 |
| saidinesh5 | without making my device reboot or overheat | 20:38 |
| neerad_ | saidinesh5: That is not a problem in my device, rebooting and all | 20:38 |
| saidinesh5 | plus i get to not mess up my /data/ partition | 20:38 |
| saidinesh5 | which is important | 20:38 |
| saidinesh5 | (this is my primary device) | 20:38 |
| neerad_ | ohhhh | 20:39 |
| neerad_ | packages/providers/ThemesProvider/src/org/cyanogenmod/themes/provider/PreviewGenerationService.java:95: error: cannot find symbol | 21:02 |
| neerad_ | c.getInt(c.getColumnIndex(ThemesColumns.MODIFIES_LIVE_LOCK_SCREEN)) == 1; | 21:02 |
| neerad_ | ^ | 21:02 |
| neerad_ | symbol: variable MODIFIES_LIVE_LOCK_SCREEN | 21:02 |
| neerad_ | location: class ThemesColumns | 21:02 |
| neerad_ | Sorry for this but anybody fix this compilation error | 21:03 |
| neerad_ | http://paste.ubuntu.com/23943486/ | 21:03 |
| saidinesh5 | you probably removed some repo it needed from the manifest. | 21:05 |
| neerad_ | What could be it? | 21:05 |
| saidinesh5 | git diff on my packages/providers/ThemesProvider gives me nothing | 21:05 |
| saidinesh5 | not sure | 21:05 |
| neerad_ | Yeah i remember removing some | 21:05 |
| neerad_ | Let me compare | 21:05 |
| saidinesh5 | i am off to bed | 21:13 |
| saidinesh5 | nighters | 21:13 |
| *** nh1402 <nh1402!~nh1402@2.26.4.134> has joined #sfdroid | 21:16 | |
| nh1402 | saidinesh5: well I've just realised that you can't build the emulator for arm even though I was going to run an arm-emulator image with it, I suppose I'll just have to chroot into it, but first I would like to see if I can get it running on the tablet | 21:26 |
| nh1402 | for "funsies" | 21:26 |
| *** CrKit <CrKit!~nekit@85-95-187-85.saransk.ru> has quit IRC (Ping timeout: 252 seconds) | 21:41 | |
| *** Bluebell_ <Bluebell_!~blue@54-242-47-212.rev.cloud.scaleway.com> has joined #sfdroid | 21:41 | |
| *** Bluebell_ <Bluebell_!~blue@54-242-47-212.rev.cloud.scaleway.com> has left #sfdroid | 21:46 | |
| *** nh1402 <nh1402!~nh1402@2.26.4.134> has quit IRC (Quit: Leaving) | 21:56 | |
| *** neerad_ <neerad_!~neerad@112.133.229.170> has quit IRC (Ping timeout: 276 seconds) | 22:52 | |
| *** ballock_ <ballock_!~ballock@194.181.150.131> has joined #sfdroid | 23:30 | |
| *** Tofe_ <Tofe_!~Tofe@nor75-20-82-247-155-176.fbx.proxad.net> has joined #sfdroid | 23:33 | |
| *** NeKit <NeKit!~nekit@85-95-187-85.saransk.ru> has quit IRC (*.net *.split) | 23:34 | |
| *** ballock <ballock!~ballock@194.181.150.131> has quit IRC (*.net *.split) | 23:34 | |
| *** nh1402[m] <nh1402[m]!nh1402matr@gateway/shell/matrix.org/x-ewtoukzgtiobnvhu> has quit IRC (*.net *.split) | 23:34 | |
| *** entil <entil!~mjt@static.73.71.47.78.clients.your-server.de> has quit IRC (*.net *.split) | 23:34 | |
| *** Tofe <Tofe!~Tofe@nor75-20-82-247-155-176.fbx.proxad.net> has quit IRC (*.net *.split) | 23:34 | |
| *** taaem <taaem!~taaem@unaffiliated/taaem> has quit IRC (Ping timeout: 276 seconds) | 23:34 | |
| *** taaem <taaem!~taaem@unaffiliated/taaem> has joined #sfdroid | 23:36 | |
| *** NeKit <NeKit!~nekit@85-95-187-85.saransk.ru> has joined #sfdroid | 23:41 | |
| *** nh1402[m] <nh1402[m]!nh1402matr@gateway/shell/matrix.org/x-qggeroamjvuaqylw> has joined #sfdroid | 23:41 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!