Before this change, kickstart will possiblely be launched at two point:

1. Boot complete, and property service load persist properties from
       file, then start service "kickstart" when set property
       "persist.radio.kickstart" to "on".

    2. Later, the same in group "core", ks_checker first disables
       kickstart, checking the ralated files, and restart kickstart.

With above procedure, kicstart might be terminated during firmware
downloaded stage, and it will cause modem booting failed. In this
change, we don't launch kickstart just after booted and leave it to be
performed by ks_checker.

Change-Id: If4d0473da69c0d1cdd05f1b24a66c7caafb25c6e
Signed-off-by: Raphanus Lo <raphanus_lo@asus.com>

init.flo.rc

@@ -311,10 +311,10 @@ service asus-dbug-d /data/data/com.asus.debugger/files/asus-debugger-d
     class late_start
     disabled
 
-on property:persist.radio.kickstart=on
+on property:gsm.radio.kickstart=on
     start kickstart
 
-on property:persist.radio.kickstart=off
+on property:gsm.radio.kickstart=off
     stop kickstart
 
 on property:ril.asus_debugger_running=1

kickstart_checker.sh

@@ -1,5 +1,5 @@
 #!/system/bin/sh
-setprop persist.radio.kickstart off
+setprop gsm.radio.kickstart off
 
 if [ $(getprop ro.boot.baseband) == "mdm" ]; then
 
@@ -18,5 +18,5 @@ if [ $(getprop ro.boot.baseband) == "mdm" ]; then
 
     echo 1 > /sys/module/rmnet_usb/parameters/rmnet_data_init
 
-    setprop persist.radio.kickstart on
+    setprop gsm.radio.kickstart on
 fi