White test my z image compiled from source please.
Tell me if everything is fixed using it in cm 7.
Sent from my GT-S5360 using xda app-developers app
hello guys
0.7.2RC
fixed init.d
please test with stock rom
install stock rom
install kernel http://www.mediafire.com/?ya55snot0xc9eh5
install root
install busybox
test init.d
Seems its not fully working!
I just tried to install BacemTweak, copied its script to /etc/init.d but it doesn't work on boot -> cat /proc/sys/bacem/volt/cpu returns nothing
with smanager by setting flags su and boot for that script I could get it to work
But strangely link2sd is working without smanager.
With kernel 0.7.0 init.d didn't work at all and I had to start it as I described by setting su and boot.
Maybe you could review your Kernel again?
Seems its not fully working!
I just tried to install BacemTweak, copied its script to /etc/init.d but it doesn't work on boot -> cat /proc/sys/bacem/volt/cpu returns nothing
with smanager by setting flags su and boot for that script I could get it to work
But strangely link2sd is working without smanager.
With kernel 0.7.0 init.d didn't work at all and I had to start it as I described by setting su and boot.
Maybe you could review your Kernel again?
hello guys
0.7.2RC
fixed init.d
please test with stock rom
install stock rom
install kernel http://www.mediafire.com/?ya55snot0xc9eh5
install root
install busybox
test init.d
I found three different common method to run init.d script? which method did you use?
1. using sysinit file in /system/bin and run that file via "run sysinit" command in init.rc
2. using sysinit file in /sbin (used in vivek and mar-oc kernel) sometimes didn't work
3. using the method explained in mikstev's thread (add "start service sysinit bla bla bla" in init.rc file)
there are also irfan's method and another similar method outside there but its quite complicated. so in total, we have 5 different method to run init.d script.
hmmmmmmmm
this method !!
in init.rc !!
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
thats the method number three. if we're using that method we should also add "start sysinit" before "class start default". have you did that?
its ????start sysinit
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
class_start default
bla bla bla
#!/system/bin/sh
export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper run-parts /system/etc/init.d
start sysinit
class start default
...bla bla bla
...bla bla bla
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
...bla bla bla
#!/system/bin/sh
# auto zram activation init script with busybox search
# by show-p1984
echo "[90ZRAM]: Firing up /system/etc/init.d/90zram";
if [ ! -e /sys/block/zram0/disksize ] ; then
echo "[90ZRAM]: ERROR unable to find /sys/block/zram0/disksize";
echo "[90ZRAM]: Is this a ZRAM kernel?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
else
#find busybox in /system
bblocation=$(find /system/ -name 'busybox')
if [ -n "$bblocation" ] && [ -e "$bblocation" ] ; then
echo "[90ZRAM]: busybox found in:" $bblocation;
echo "[90ZRAM]: Setting ZRAM disksize.";
echo $((100*1024*1024)) > /sys/block/zram0/disksize
echo "[90ZRAM]: Starting ZRAM...";
bblocation=${bblocation%/*}
cd $bblocation
./busybox mkswap /dev/block/zram0
./busybox swapon /dev/block/zram0
echo "[90ZRAM]: ZRAM activated.";
else
echo "[90ZRAM]: ERROR! busybox not found!";
echo "[90ZRAM]: Is busybox installed? Symlinks set?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
fi
fi
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
mount -o remount,noauto_da_alloc /data /data