Hi You'd probably get your problem solved a lot quicker if you provided the ramdisk.img ( or boot.img ) you are using. At a guess however I would make sure the .rc permissions are set to 644 otherwise the init process will class the file as unsafe and refuse to process it which is probably the likely cause here.... You can find out for sure by running adb shell dmesg during the boot process, assuming you have it all enabled.. You should see a message like "skipping insecure file <filename>".
Hope that Helps On Monday, 24 March 2014 19:59:12 UTC, Ravishka Fernando wrote: > > Hello all :) sorry for posting an off topic question but this is the only > forum which I found close to my situation.. > > My device (HTC Amaze 4G) executes some system/bin files in the boot > process for various services, such as (qcks, ks, ewmutzd, akmd, uimq) bin > files.. Well I ported kernel 3.4 to htc amaze 4G, and for ramdisk i mostly > used the stuff from stock ics ramdisk but when my rom (JB Sense) boots none > of those files get executed.. I tried > > service kickstart /system/bin/qcks 1 > class core > oneshot > > Like in stock when it didn't work I entered "start kickstart" under post-fs > Still nothing happening..The files are there in the system/bin directory > but the service doesn't start :/ what am i missing? > > -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
