62 replies to this topic

[Snap.IT]

android@sam, on 12 August 2012 - 04:11 PM, said:

You are most welcome! !

I am extremely impressed with the speed, i've got an old 4GB that i'm testing this on and the speed is way over any expectations i had.

One tip is to use script-manager widgets for bootsd.sh (in the nand rom) and bootnand.sh (in the SD rom). That way rebooting into your other rom is as easy as clicking the shortcut on your homescreen.

[vNa5h]

Snap.IT, on 12 August 2012 - 05:44 PM, said:

I am extremely impressed with the speed, i've got an old 4GB that i'm testing this on and the speed is way over any expectations i had.

One tip is to use script-manager widgets for bootsd.sh (in the nand rom) and bootnand.sh (in the SD rom). That way rebooting into your other rom is as easy as clicking the shortcut on your homescreen.

still better ROM devs can include a option in power menu to reboot into the respective ROM
is there any way we can do it ourself

[vNa5h]

WE have to decompile/recompile framework file
here a tutorial to add screenshot
http://forum.xda-dev...d.php?t=1692080

we can do it similarly

[Snap.IT]

vNa5h, on 13 August 2012 - 08:03 AM, said:

still better ROM devs can include a option in power menu to reboot into the respective ROM
is there any way we can do it ourself

Well, sure there is a way to do it (all it does is flash the boot.img from the ROM you want to boot to and reboot the phone) but a widget is just as easy.

There are bigger issues that need to be resolved before that.

When installing burstlams rom into nand and rebooting it will actually move the data from the sd data partition (second partition or mmcblk0p2) to the nand data. The reason for this is that S2E looks at the partition, sees the data, figures that it should be in /data (since the option to move it to sd-ext is not set) and moves it to /data.

I think the proper solution would be to leave the second partition for sd-ext and use mmcblk0p3 and mmcblk0p4 for /data and /system respectively. This also solves the problem with wiping/factory reset which will wipe the data partition for the SD-ROM since it mounts it as sd-ext.

I don't really know what happens when you swapon the /system partition though so that needs to be edited out of the init.d/swapon.80 of the burstlam ICS before installing it.

Edited by Snap.IT, 13 August 2012 - 01:52 PM.

[iShubham]

I have a question...
Does this slow down the device? I mean my chinese blade is slow with any ROM...so putting 2 roms would be more slow or it wont affect speed?

[Snap.IT]

iShubham, on 13 August 2012 - 01:35 PM, said:

I have a question...
Does this slow down the device? I mean my chinese blade is slow with any ROM...so putting 2 roms would be more slow or it wont affect speed?

It won't affect the *memory* (RAM) of the phone at all, all it does is that it allows you to install a second ROM onto external storage (SD-Card).

The way it does this is to change the updater-script that installs the rom (and other packages, like gapps) to install the second rom into the partitions you created on your sdcard (first partition (mmcblk0p2) is mounted as /data and second partition (mmcblk0p3) is mounted as /system). To make it work the init.rc of your boot.img is changed so that at boot it will mount the /system and /data to the partitions on your sdcard rather than on nand storage. You then shift between the roms by using the scripts which flash the boot partition with the respective kernel (bootsd.img to mount and boot your SD-ROM and boot.img to mount and boot your nand ROM). So when booting the nand rom it's as if you never made the procedure at all (except that you can't use mount2sd, S2E or any other solution that moves data to sd-ext), everything will work just like if you only had one ROM on your phone except for the part where you can run the script to boot another ROM of your choice now.

The second rom will be slower (since read/write speeds are slower on the external storage (SD-Card)) than the one installed into your nand (internal storage) but the one on the nand won't be affected at all.

So the answer to your question without the explanation is, no it won't slow your phone down.

[android@sam]

Sorry guys.The upload isn't just working. I will post the update tomorrow.

[Penmax]

Just thinking dont know anything about how android or booting is built but would it be possible to use the cache as a boot menu instead since its not used?

Edited by Penmax, 13 August 2012 - 11:03 PM.

[Snap.IT]

Penmax, on 13 August 2012 - 11:02 PM, said:

Just thinking dont know anything about how android or booting is built but would it be possible to use the cache as a boot menu instead since its not used?

No.

The phone will boot whatever is in the boot partition, i explained how it works above.

[Snap.IT]

I've got it setup just right at the moment.

I've got Swedish Snow on the SD-Card, partition 3 for data (one gig worth of storage, who needs S2E) and partition 4 for system. It took some tinkering with the init.rc and the update scripts (not just for SSRLS7 but for all the little things that i want installed along with it, like the dialer, Adreno libs and so on). This is my daily driver.

Then on the nand i have paranoid android with S2E (i need S2E) working as usual on partition 2.

It was a lot simpler just changing the partitions for the SD rom install than it would have been to change it for S2E (damn thing restores it at every boot).

If i could just mount a loop filesystem instead i wouldn't have to worry about partitioning and i could have as many as my sdcard can hold.

Edited by Snap.IT, 14 August 2012 - 12:31 AM.

[iShubham]

Snap.IT, on 13 August 2012 - 01:50 PM, said:

It won't affect the *memory* (RAM) of the phone at all, all it does is that it allows you to install a second ROM onto external storage (SD-Card).

The way it does this is to change the updater-script that installs the rom (and other packages, like gapps) to install the second rom into the partitions you created on your sdcard (first partition (mmcblk0p2) is mounted as /data and second partition (mmcblk0p3) is mounted as /system). To make it work the init.rc of your boot.img is changed so that at boot it will mount the /system and /data to the partitions on your sdcard rather than on nand storage. You then shift between the roms by using the scripts which flash the boot partition with the respective kernel (bootsd.img to mount and boot your SD-ROM and boot.img to mount and boot your nand ROM). So when booting the nand rom it's as if you never made the procedure at all (except that you can't use mount2sd, S2E or any other solution that moves data to sd-ext), everything will work just like if you only had one ROM on your phone except for the part where you can run the script to boot another ROM of your choice now.

The second rom will be slower (since read/write speeds are slower on the external storage (SD-Card)) than the one installed into your nand (internal storage) but the one on the nand won't be affected at all.

So the answer to your question without the explanation is, no it won't slow your phone down.

Thanks for explaining it ill try it!

[android@sam]

Tool updated! !!

[Snap.IT]

I've been trying to get a looped filesystem to work but it doesn't work properly.

After installing SSRLS7 to the SD card i thought i'd try to create a couple of loop files, mount them and copy the contents of the partitions to those respective files. So i did that.

Then i put them on the sdcard (on an ext2 partition, partition no2) and changed the init.rc to like this:


# mount mtd partitions
mkdir /mnt/mb
mount ext2 /dev/block/mmcblk0p2 /mnt/mb
losetup /dev/loop0 /mnt/mb/multiboot/snow/system
losetup /dev/loop1 /mnt/mb/multiboot/snow/data
mount ext2 /dev/loop0 /system
# Mount /system rw first to give the filesystem a chance to save a checkpoint
# mount ext2 /dev/block/mmcblk0p4 /system
# Mount /system ro as stricter security settings required, ZTE_BOOT_LIWEI_20110307
# Move To "on post-fs" part to leave a chance to modify /system in "on fs" part, ZTE_BOOT_LIWEI_20110331
# mount yaffs2 mtd@system /system ro remount
mount ext2 /dev/loop1 /data
# mount ext2 /dev/block/mmcblk0p3 /data nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev

on post-fs
# ZTE_JCD_CTSCONFIG, 2011.05.03, BEGIN
mkdir /system/lost+found 0770
chmod 0770 /system/lost+found
# ZTE_JCD_CTSCONFIG 2011.05.03, END
# once system is setup, no need to modify /system , ZTE_BOOT_LIWEI_20110331
mount ext2 /dev/loop0 /system ro remount
# mount ext2 /dev/block/mmcblk0p4 /system ro remount

It doesn't work though and i don't know why.

The problem has to be in the init.rc script because i've checked everything several times, i've tried mounting the files on linux and that works just fine, i've ensured that they are in the correct folder on the sdcard and that the partition is mmcblk0p2.

If anyone can spot the problem, please tell me.

[byf]

Snap.IT, on 15 August 2012 - 01:10 AM, said:

I've been trying to get a looped filesystem to work but it doesn't work properly.

After installing SSRLS7 to the SD card i thought i'd try to create a couple of loop files, mount them and copy the contents of the partitions to those respective files. So i did that.

Then i put them on the sdcard (on an ext2 partition, partition no2) and changed the init.rc to like this:


# mount mtd partitions
mkdir /mnt/mb
mount ext2 /dev/block/mmcblk0p2 /mnt/mb
losetup /dev/loop0 /mnt/mb/multiboot/snow/system
losetup /dev/loop1 /mnt/mb/multiboot/snow/data
mount ext2 /dev/loop0 /system
# Mount /system rw first to give the filesystem a chance to save a checkpoint
# mount ext2 /dev/block/mmcblk0p4 /system
# Mount /system ro as stricter security settings required, ZTE_BOOT_LIWEI_20110307
# Move To "on post-fs" part to leave a chance to modify /system in "on fs" part, ZTE_BOOT_LIWEI_20110331
# mount yaffs2 mtd@system /system ro remount
mount ext2 /dev/loop1 /data
# mount ext2 /dev/block/mmcblk0p3 /data nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev

on post-fs
# ZTE_JCD_CTSCONFIG, 2011.05.03, BEGIN
mkdir /system/lost+found 0770
chmod 0770 /system/lost+found
# ZTE_JCD_CTSCONFIG 2011.05.03, END
# once system is setup, no need to modify /system , ZTE_BOOT_LIWEI_20110331
mount ext2 /dev/loop0 /system ro remount
# mount ext2 /dev/block/mmcblk0p4 /system ro remount

It doesn't work though and i don't know why.

The problem has to be in the init.rc script because i've checked everything several times, i've tried mounting the files on linux and that works just fine, i've ensured that they are in the correct folder on the sdcard and that the partition is mmcblk0p2.

If anyone can spot the problem, please tell me.

try to redirect command output to a logfile like this

losetup /dev/loop1 /mnt/mb/multiboot/snow/data >> /sdcard/log.txt

and check logfile may helo

Edited by byf, 16 August 2012 - 09:25 AM.

[Snap.IT]

byf, on 16 August 2012 - 09:25 AM, said:

try to redirect command output to a logfile like this

losetup /dev/loop1 /mnt/mb/multiboot/snow/data >> /sdcard/log.txt

and check logfile may helo

I had to add a line to mount the sdcard before that, like this: mount vfat /dev/block/mmcblk0p1 /mnt/sdcard and then i added >> /mnt/sdcard/log.txt at the end of the losetup lines but when i reboot to check the log.txt there is no such file there.

[Snap.IT]

Here's the latest incarnation with busybox included in the ROM and mounting the files on the regular vfat partition rather than having to make extra partitions.

################################################################################################################
#when who where, what, why
#2010-05-17 mengxf chmod fota_api ZTE_FOTA_MXF_001
#2010-08-04 ruijiagui add service of sd_log ZTE_RIL_RJG_20100804
#2011-01-07 zhangbaisheng ZTE_ZBS_20110107 Add wlan wpa_supplicant service
#2011-03-09 yaosujuan add property to control drmHost service for GCF ZTE_RIL_YAOSUJUAN_20110309
#2011-04-20 zhengchao modify the file interface permission for PM ZTE_PM_ZHENGCHAO_001
#2011-05-04 jiangchd modify permission for CTS ZTE_JCD_CTSCONFIG
#2011-05-12 lianghouxing ZTE_PM_LIANGHOUXING_001: enable APP key to wakeup
#2011-09-26 huoliping ZTE_HLP_PARTNERAPP add program of uninstalling partnerApps
################################################################################################################

on early-init
start ueventd

on init

sysclktz 0

loglevel 3

# setup the global environment
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export EXTERNAL_STORAGE /mnt/sdcard
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/qcnvitems.jar:/system/framework/qcrilhook.jar

# Backward compatibility
symlink /system/etc /etc
symlink /sys/kernel/debug /d

# Right now vendor lives on the same filesystem as system,
# but someday that may change.
symlink /system/vendor /vendor

# create mountpoints
mkdir /mnt 0775 root system
mkdir /mnt/sdcard 0000 system system

# Create cgroup mount point for cpu accounting
mkdir /acct
mount cgroup none /acct cpuacct
mkdir /acct/uid

# Backwards Compat - XXX: Going away in G*
symlink /mnt/sdcard /sdcard
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /config 0500 root root
mkdir /sqlite_stmt_journals 01777 root root
mount tmpfs tmpfs /sqlite_stmt_journals size=4m
# ZTE_JCD_CTSCONFIG, 2011.05.03, begin
chmod 01770 /sqlite_stmt_journals
# ZTE_JCD_CTSCONFIG, 2011.05.03, end

# Directory for putting things only root should see.
mkdir /mnt/secure 0700 root root

# Directory for staging bindmounts
mkdir /mnt/secure/staging 0700 root root

# Directory-target for where the secure container
# imagefile directory will be bind-mounted
mkdir /mnt/secure/asec 0700 root root

# Secure container public mount points.
mkdir /mnt/asec 0700 root system
mount tmpfs tmpfs /mnt/asec mode=0755,gid=1000

# Filesystem image public mount points.
mkdir /mnt/obb 0700 root system
mount tmpfs tmpfs /mnt/obb mode=0755,gid=1000

write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
write /proc/cpu/alignment 4
write /proc/sys/kernel/sched_latency_ns 10000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000
write /proc/sys/kernel/sched_compat_yield 1
write /proc/sys/kernel/sched_child_runs_first 0

# ZTE_PM_ZHENGCHAO_001:zhengchao modify the permissions of PM interface
chmod 0660 /sys/bus/platform/drivers/msm-battery/usb_chg_enable
chmod 0660 /sys/bus/platform/drivers/msm-battery/enable_to_shutdown
chmod 0660 /proc/gpiowake
chmod 0660 /proc/zte_alarm
chmod 0660 /sys/kernel/debug/gpio/gpio_get
chmod 0660 /sys/kernel/debug/gpio/gpio_out_l
chmod 0660 /sys/kernel/debug/gpio/gpio_out_h

chown root system /sys/bus/platform/drivers/msm-battery/usb_chg_enable
chown root system /sys/bus/platform/drivers/msm-battery/enable_to_shutdown
chown root system /proc/gpiowake
chown root system /proc/zte_alarm
chown root system /sys/kernel/debug/gpio/gpio_get
chown root system /sys/kernel/debug/gpio/gpio_out_l
chown root system /sys/kernel/debug/gpio/gpio_out_h
# ZTE_PM_ZHENGCHAO_001:end

# ZTE_SYS_CHENXIHUA_001:chenxihua control read of /dev/log/system
# chmod 0622 /dev/log/system
# ZTE_SYS_CHENXIHUA_001 end

# ZTE_PM_LIANGHOUXING_001: enable APP key to wakeup
on property:persist.sys.wakeup.key=A
write /proc/gpiowake A
on property:persist.sys.wakeup.key=B
write /proc/gpiowake B
on property:persist.sys.wakeup.key=H
write /proc/gpiowake H
on property:persist.sys.wakeup.key=M
write /proc/gpiowake M
on property:persist.sys.wakeup.key=D
write /proc/gpiowake D
# ZTE_PM_LIANGHOUXING_001:end

# Create cgroup mount points for process groups
mkdir /dev/cpuctl
mount cgroup none /dev/cpuctl cpu
chown system system /dev/cpuctl
chown system system /dev/cpuctl/tasks
chmod 0777 /dev/cpuctl/tasks
write /dev/cpuctl/cpu.shares 1024

mkdir /dev/cpuctl/fg_boost
chown system system /dev/cpuctl/fg_boost/tasks
chmod 0777 /dev/cpuctl/fg_boost/tasks
write /dev/cpuctl/fg_boost/cpu.shares 1024

mkdir /dev/cpuctl/bg_non_interactive
chown system system /dev/cpuctl/bg_non_interactive/tasks
chmod 0777 /dev/cpuctl/bg_non_interactive/tasks
# 5.0 %
write /dev/cpuctl/bg_non_interactive/cpu.shares 52

on fs
# mount mtd partitions
/sbin/busybox mount vfat /dev/block/mmcblk0p1 /mnt/sdcard
/sbin/busybox losetup /dev/block/loop0 /mnt/sdcard/multiboot/snow/system.img >> /mnt/sdcard/logger.txt
/sbin/busybox losetup /dev/block/loop1 /mnt/sdcard/multiboot/snow/data.img >> /mnt/sdcard/logger.txt
mount ext2 /dev/block/loop0 /system >> /mnt/sdcard/logger.txt
# Mount /system rw first to give the filesystem a chance to save a checkpoint
# mount ext2 /dev/block/mmcblk0p4 /system
# Mount /system ro as stricter security settings required, ZTE_BOOT_LIWEI_20110307
# Move To "on post-fs" part to leave a chance to modify /system in "on fs" part, ZTE_BOOT_LIWEI_20110331
# mount yaffs2 mtd@system /system ro remount
mount ext2 /dev/block/loop1 /data >> /mnt/sdcard/logger.txt
# mount ext2 /dev/block/mmcblk0p3 /data nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev

on post-fs
# ZTE_JCD_CTSCONFIG, 2011.05.03, BEGIN
mkdir /system/lost+found 0770
chmod 0770 /system/lost+found
# ZTE_JCD_CTSCONFIG 2011.05.03, END
# once system is setup, no need to modify /system , ZTE_BOOT_LIWEI_20110331
mount ext2 /dev/block/loop0 /system ro remount >> /mnt/sdcard/logger.txt
# mount ext2 /dev/block/mmcblk0p4 /system ro remount

# once everything is setup, no need to modify /
mount rootfs rootfs / ro remount

# We chown/chmod /data again so because mount is run as root + defaults
chown system system /data
chmod 0771 /data

# Create dump dir and collect dumps.
# Do this before we mount cache so eventually we can use cache for
# storing dumps on platforms which do not have a dedicated dump partition.

mkdir /data/dontpanic
chown root log /data/dontpanic
chmod 0750 /data/dontpanic
mkdir /data/anr
chown system system /data/anr
chmod 0777 /data/anr


chown root system /system/bin/Tgetmem
chmod 4550 /system/bin/Tgetmem

chown root root /system/bin/fota_api
chmod 4555 /system/bin/fota_api
# mengxiangfei ZTE_FOTA_MXF_001

# Collect apanic data, free resources and re-arm trigger
copy /proc/apanic_console /data/dontpanic/apanic_console
chown root log /data/dontpanic/apanic_console
chmod 0640 /data/dontpanic/apanic_console

copy /proc/apanic_threads /data/dontpanic/apanic_threads
chown root log /data/dontpanic/apanic_threads
chmod 0640 /data/dontpanic/apanic_threads

write /proc/apanic_console 1

# Same reason as /data above
chown system cache /cache
chmod 0770 /cache

# This may have been created by the recovery system with odd permissions
chown system cache /cache/recovery
chmod 0770 /cache/recovery

#change permissions on vmallocinfo so we can grab it from bugreports
chown root log /proc/vmallocinfo
chmod 0440 /proc/vmallocinfo

#change permissions on kmsg & sysrq-trigger so bugreports can grab kthread stacks
chown root system /proc/kmsg
chmod 0440 /proc/kmsg
chown root system /proc/sysrq-trigger
chmod 0220 /proc/sysrq-trigger

# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/bluetooth 0770 system system
mkdir /data/misc/keystore 0700 keystore keystore
mkdir /data/misc/vpn 0770 system system
mkdir /data/misc/systemkeys 0700 system system
mkdir /data/misc/vpn/profiles 0770 system system

# ZTE_ZBS_20110107 +++
#=======create WLAN filesystem structure +++==========================
#give system access to wpa_supplicant.conf for backup and restore
mkdir /data/misc/wifi 0770 wifi wifi
mkdir /data/misc/wifi/wpa_supplicant 0770 wifi wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
#wpa_supplicant ctrl sockets
mkdir /data/misc/wifi/sockets 0770 system wifi

mkdir /data/misc/dhcp 0770 dhcp dhcp
mkdir /data/system 0775 system system
symlink /data/misc/wifi/wpa_supplicant /data/system/wpa_supplicant

#set the right for wlan driver to control slot2's polling property
chown system system /sys/bus/platform/devices/msm_sdcc.2/polling
#=======create WLAN filesystem structure ---==========================
# ZTE_ZBS_20110107 ---

chmod 0666 /sys/module/g_android/parameters/product_id
mkdir /data/local 0771 shell shell
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root
mkdir /data/radio 0770 radio radio
chown radio system /dev/pm_monitor

# create dalvik-cache and double-check the perms
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache

# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770
mkdir /cache/lost+found 0770

# double check the perms, in case lost+found already exists, and set owner
chown root root /data/lost+found
chmod 0770 /data/lost+found
chown root root /cache/lost+found
chmod 0770 /cache/lost+found

#irdeto: begin
# create the OMA directories, so as to enforce our permissions
mkdir /data/oma 1777
chmod 1777 /data/oma
#irdeto: end

#change product_id prio
chown root system /sys/module/g_android/parameters/product_id
chmod 0664 /sys/module/g_android/parameters/product_id

on boot
# basic network init
ifup lo
hostname localhost
domainname localdomain

# set RLIMIT_NICE to allow priorities from 19 to -20
setrlimit 13 40 40

# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.PERCEPTIBLE_APP_ADJ 2
setprop ro.HEAVY_WEIGHT_APP_ADJ 3
setprop ro.SECONDARY_SERVER_ADJ 4
setprop ro.BACKUP_APP_ADJ 5
setprop ro.HOME_APP_ADJ 6
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.EMPTY_APP_ADJ 15

# ZTE set opengl version 2.0 for eclair by liuhaitao 2011-01-27 start.
setprop ro.opengles.version 131072
# ZTE set opengl version 2.0 for eclair by liuhaitao 2011-01-27 end.

# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
setprop ro.FOREGROUND_APP_MEM 2048
setprop ro.VISIBLE_APP_MEM 3072
setprop ro.PERCEPTIBLE_APP_MEM 4096
setprop ro.HEAVY_WEIGHT_APP_MEM 4096
setprop ro.SECONDARY_SERVER_MEM 6144
setprop ro.BACKUP_APP_MEM 6144
setprop ro.HOME_APP_MEM 6144
setprop ro.HIDDEN_APP_MEM 7168
setprop ro.EMPTY_APP_MEM 8192


#ZTE_ZHP_20110714 add getlogtofile control,user version is close and eng version is open by default.
# setprop persist.sys.ztelog.enable 1
#add end

# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have combined some of
# the classes into the same memory level; the associated processes of higher
# classes will still be killed first.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,4,7,15

write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
write /sys/module/lowmemorykiller/parameters/minfree 2048,3072,4096,6144,7168,8192

# Set init its forked children's oom_adj.
write /proc/1/oom_adj -16

# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5

# Permissions for System Server and daemons.
chown radio system /sys/android_power/state
chown radio system /sys/android_power/request_state
chown radio system /sys/android_power/acquire_full_wake_lock
chown radio system /sys/android_power/acquire_partial_wake_lock
chown radio system /sys/android_power/release_wake_lock
chown radio system /sys/power/state
chown radio system /sys/power/wake_lock
chown radio system /sys/power/wake_unlock
chmod 0660 /sys/power/state
chmod 0660 /sys/power/wake_lock
chmod 0660 /sys/power/wake_unlock
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/leds/keyboard-backlight/brightness
chown system system /sys/class/leds/lcd-backlight/brightness
chown system system /sys/class/leds/button-backlight/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm

#sys to light path for blink ZTE_HWY_20110307 begin
chown system system /sys/class/leds/red/blink
chown system system /sys/class/leds/green/blink
#sys to light path for blink ZTE_HWY_20110307 end

chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm

#sys to light path for blink ZTE_HWY_20110307 begin
chown system system /sys/class/leds/red/blink
chown system system /sys/class/leds/green/blink
#sys to light path for blink ZTE_HWY_20110307 end

#change owner&group for ti-gague enable chenchongbao.20110725_1 begin
chown root system /sys/bus/i2c/drivers/ti-fuel-gauge/enable
chown root system /sys/bus/i2c/drivers/ti-fuel-gauge/upmode
chown root system /sys/bus/i2c/drivers/ti-fuel-gauge/Control
#change owner&group for ti-gague enable chenchongbao.20110725_1 end

chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/module/sco/parameters/disable_esco
chown system system /sys/kernel/ipv4/tcp_wmem_min
chown system system /sys/kernel/ipv4/tcp_wmem_def
chown system system /sys/kernel/ipv4/tcp_wmem_max
chown system system /sys/kernel/ipv4/tcp_rmem_min
chown system system /sys/kernel/ipv4/tcp_rmem_def
chown system system /sys/kernel/ipv4/tcp_rmem_max
chown root radio /proc/cmdline

start sysinit
on property:cm.filesystem.ready=1

class_start default

## Daemon processes to be run by init.
##
service ueventd /sbin/ueventd
critical

service console /system/bin/sh
console
disabled
user shell
group log


service usbconfig /sbin/usbconfig
oneshot

on property:ro.secure=0
start console

# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled

# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd

on property:persist.service.adb.enable=1
start adbd

on property:persist.service.adb.enable=0
stop adbd

on property:persist.sys.wifi.wl=1
mkdir /data/wifi
start wifi_wl_test

on property:persist.sys.wifi.wl=0
stop wifi_wl_test

service wifi_wl_test /system/bin/sh /system/etc/wifi_wl_test.sh
user root
disabled
oneshot

service servicemanager /system/bin/servicemanager
user system
critical
onrestart restart zygote
onrestart restart media

service vold /system/bin/vold
socket vold stream 0660 root mount
ioprio be 2

service netd /system/bin/netd
socket netd stream 0660 root system

service qmuxd /system/bin/qmuxd
service ril-daemon /system/bin/rild
socket rild stream 660 root radio
socket rild-debug stream 660 radio system
user root
group radio cache inet misc audio sdcard_rw qcom_oncrpc

#ZTE_RIL_RJG_20100804 begin
service sdlog-daemon /system/bin/sdlog
disabled

on property:persist.service.sdlog.enable=1
start sdlog-daemon
#ZTE_RIL_RJG_20100804 end

service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
socket zygote stream 666
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media
onrestart restart netd

#irdeto
service DrmHost /system/bin/DrmHost
# ZTE_RIL_YAOSUJUAN_20110309 begin
on property:ro.gcftest=1
stop DrmHost
# ZTE_RIL_YAOSUJUAN_20110309 end

service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot

service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw
ioprio rt 4

service bootanim /system/bin/bootanimation
user graphics
group graphics
disabled
oneshot

service dbus /system/bin/dbus-daemon --system --nofork
socket dbus stream 660 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin

service bluetoothd /system/bin/bluetoothd -n
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled

service hfag /system/bin/sdptool add --channel=10 HFAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot

service hsag /system/bin/sdptool add --channel=11 HSAG
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot

service opush /system/bin/sdptool add --channel=12 OPUSH
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot

service pbap /system/bin/sdptool add --channel=19 PBAP
user bluetooth
group bluetooth net_bt_admin
disabled
oneshot

service installd /system/bin/installd
socket installd stream 600 system system

service flash_recovery /system/etc/install-recovery.sh
oneshot

# ZTE_ZBS_20110107 +++
service wlan_prop /system/bin/sh /system/etc/init.wlanprop.sh
oneshot

service wpa_supplicant /system/bin/wpa_supplicant -Dwext -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf
disabled
oneshot

service hostapd /system/bin/hostapd /data/misc/wifi/hostapd.conf
socket hostapd_wl0.1 dgram 660 root wifi
user root
group wifi
oneshot
disabled

service dhcpcd_wlan0 /system/bin/dhcpcd -ABKL wlan0
disabled
oneshot

service iprenew_wlan0 /system/bin/iprenew
disabled
oneshot

service wlan_tool /system/bin/wlan_tool
user root
group root
disabled
oneshot

service dbgar6003 /system/bin/recEvent --logfile=/data/ar6k.log --srcdir=/system/wifi/ --reclimit=10000
oneshot

service dbgar6002 /system/bin/recEvent /data/ar6k.log 0x10000000
disabled
# AR6002
service abtfilt /system/bin/abtfilt -c -d -z -n
disabled
oneshot

# Special for the ugly AR6003 code
service abtfilt1 /system/bin/abtfilt -n -d -v -z -s
disabled
oneshot

service tcmd_app /system/bin/tcmd_app -a -p /system/wifi/ar6000.ko
disabled
oneshot
# ZTE_ZBS_20110107 +++ ---

service racoon /system/bin/racoon
socket racoon stream 600 system system
# racoon will setuid to vpn after getting necessary resources.
group net_admin
disabled
oneshot

service mtpd /system/bin/mtpd
socket mtpd stream 600 system system
user vpn
group vpn net_admin net_raw
disabled
oneshot

service keystore /system/bin/keystore /data/misc/keystore
user keystore
group keystore
socket keystore stream 666

service dumpstate /system/bin/dumpstate -s
socket dumpstate stream 0660 shell log
disabled
oneshot
service dumpsurface /system/bin/sf.sh
disabled
oneshot

service bootsound /system/bin/stagefright -a -o /system/media/audio/ui/bootsound.mp3
user media
group audio
disabled
oneshot

on property:init.svc.bootanim=running
start bootsound

on property:dev.bootcomplete=1
stop bootsound

Still doesn't work and still no logger.txt on the /mnt/sdcard.

Edited by Snap.IT, 16 August 2012 - 05:18 PM.

[byf]

Change loglevel it to 8 (the highest)  in the /init.rc file and then use dmesg command to check logs?

[Snap.IT]

byf, on 17 August 2012 - 02:46 AM, said:

Change loglevel it to 8 (the highest)  in the /init.rc file and then use dmesg command to check logs?

Yeah, that won't help since it won't boot to that filesystem on reboot.

[android@sam]

Snap.IT, on 17 August 2012 - 03:35 PM, said:

Yeah, that won't help since it won't boot to that filesystem on reboot.

I got success in reading log.txt by Qtadb.Some kind of input/output or  read error is there.I will try soon on loop system.

[tokariew]

i have newbie question. i should use modify boot for which rom this what i want on sdcard or nand, the same for update-script. i feel a little confused after reading the guide.

Edited by tokariew, 22 August 2012 - 05:49 PM.