Database Develop

[Dev] Improve Internal SD card speed

http://forum.xda-developers.com/showthread.php?t=1023664
Using the same method there
by editing /sys/devices/virtual/bdi/179:0/read_ahead_kb to 4096 I seem to have imrpoved my internal SD card's speed. Only until reboot as i cant find /system/etc/init.d using root explorer.
However, can kennethpenn, Ririal and any other devs bake it into the rom?

+1 (please)

Correct me if I am wrong, but you should be able to create an init.d file in wordpad and put the script in there to run on boot. I did that for a memory tweak on my former Galaxy S.
Sent from my soon-to-be-hacked Bell Atrix.

GibMcFragger said:
Correct me if I am wrong, but you should be able to create an init.d file in wordpad and put the script in there to run on boot. I did that for a memory tweak on my former Galaxy S.
Sent from my soon-to-be-hacked Bell Atrix.
Click to expand...
Click to collapse
I'm hoping you are right!!

GibMcFragger said:
Correct me if I am wrong, but you should be able to create an init.d file in wordpad and put the script in there to run on boot. I did that for a memory tweak on my former Galaxy S.
Sent from my soon-to-be-hacked Bell Atrix.
Click to expand...
Click to collapse
I know it can... But there isnt an init.d folder in /system/etc/

(Noob question?) What are you guys use to read/edit these files (on phone)? I don't mean the ".rc" ones, but those with a page-and-badge icon in Root Explorer (example: "/init", not "/init.rc"). I'm not even sure on the file type... Thanks.

We'll see about this. I'm doubtful. But I'm adding it to my list of prospects.

kennethpenn said:
We'll see about this. I'm doubtful. But I'm adding it to my list of prospects.
Click to expand...
Click to collapse
It does show improvement in SD Tool.
However, I use my external SD for camera so gallery reads from it... so not sure if it has real world improvement...

Create a init.d folder in /system/etc and push this script there
But it won't work until you install the script or another is already installed in init.d folder
http://db.tt/18JjeOl direct link

cdesai said:
Create a init.d folder in /system/etc and push this script there
But it won't work until you install the script or another is already installed in init.d folder
http://db.tt/18JjeOl direct link
Click to expand...
Click to collapse
Do you know for sure it will be executed just by creating the folder? is the init.d folder supported?

One of the earlier versions of aroot added init.d support, however i am not sure if the later versions (gladiatrix root) does this (see this thread)
I used the aroot method when I reflashed 1.26 to do some tweaking and the init.d folder is in /system/etc/

Girgizzlemuf said:
One of the earlier versions of aroot added init.d support, however i am not sure if the later versions (gladiatrix root) does this (see this thread)
I used the aroot method when I reflashed 1.26 to do some tweaking and the init.d folder is in /system/etc/
Click to expand...
Click to collapse
The problem is I am on 4.1.57 gingerblur... And I am not sure if it has init.d support :S

tianqi said:
I know it can... But there isnt an init.d folder in /system/etc/
Click to expand...
Click to collapse
There is on mine..
Sent from my soon-to-be-hacked Bell Atrix.

My question is, will this work for the external sd card as well? I transfer most but not all of my less priority apps to my external sd card. The SD Card app that test the speed is not accurate, fyi.
I also tried the link previously and changed it to max kb but occasionally it is a hit or miss on the speed.

tianqi said:
The problem is I am on 4.1.57 gingerblur... And I am not sure if it has init.d support :S
Click to expand...
Click to collapse
Im pretty sure I flashed back to 4.1.26 to use the root method I mentioned before specifically so I could use 4.1.57 with init.d support. I did notice that the "prefered" root method doesnt make mention of init.d, but its fully working for me now
Sent from my MB860 using XDA App

What Motorola did was bake in the native linux install from the android-backend with the webtop system. Thus, the directory you're looking for is /osh/etc/init.d/
Code:
echo "$YOURLINE" >> /osh/etc/init.d/rc

Also anyone know which one to edit for the external sd? So we can improve both sd?

Request.... please pretty please..
I brought this up in the gladiatrix thread 2 days ago and was also not able to get it to work after reboot or on the external SD.
Would someone please create a CWM zip for this when it is completed?
It could be added to the wiki or the sticky's thread

tianqi said:
GibMcFragger said:
Correct me if I am wrong, but you should be able to create an init.d file in wordpad and put the script in there to run on boot. I did that for a memory tweak on my former Galaxy S.
Click to expand...
Click to collapse
I know it can... But there isnt an init.d folder in /system/etc/
Click to expand...
Click to collapse
Pulling stuff from memory, so I might be a bit off here and there.
The original root methods (SuperOneClick and aRoot) put a script in /system/etc/install-recovery (or something like that) which had one line in it which told it to execute every script in /system/etc/init.d. They also created the /system/etc/init.d directory and put a single script in there which remounted /system as rw.
But, the 4.1.57 update deleted the script, so most of you probably don't have it any longer (unless the re-root process put that script back?). In any case, I suspect that's the information you're looking for.

So 4.1.57 isnt capable of running init.d?

One click ODEXing a ROM for more RAM and better speed.

Here's an alternative way to gain more RAM and performance without odexing.
Get more RAM and faster responses by disabling verify-bytecode!
This process will usually give just as much as performance boost as odexing SYSTEM and USER app.
Click to expand...
Click to collapse
AS WITH ANY MODDING PROCEDURE/SCRIPTS FOR YOUR PHONE, THIS SCIPT ALSO COMES WITH NO WARRANTY. AUTHOR HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF RUNNING THIS SCRIPT. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING. MAKE SURE YOU HAVE AT LEAST 15% FREE ON /SYSTEM, THIS IS IMPORTANT BECAUSE IF YOU RUN OUT OF SPACE THINGS WILL GO BADLY WRONG..
Requires busybox.
If your system partition is almost full, have a look at http://forum.xda-developers.com/showthread.php?t=734236.
This script will *attempt* to odex all apks found at /system/app. Theming would be impossible once the ROM is odexed. Themes applied at the time of odexing will be preserved. If you plan on applying a theme, apply it before odexing. If you want to theme after odexing, you must deodex the ROM before theming. If you change themes often, odexing is not for you.
Quick Instructions for Windows:
Connect the phone with USB cable and enable USB debugging. (No wireless or Android Terminal shell)
Put the phone in airplane mode.
Download and extract the attached file and run odex.bat
Instructions for advanced users:
This attachment contains a folder called odex. Push that folder to data and set the permission of odex.sh to 4755. Mount system as r/w(could be done via adb remount system). Next, execute odex.sh. All of this should be done via USB using ADB shell. Do not use wireless adb or Android Terminal.
Advantages:
More free space in system partition.
Faster booting.
More free RAM(I was able to gain 20-30MB.)
Faster access to system apps.
Disadvantages:
Cannot be themed after odexing.
APK tweaks cannot be applied.
Might break some of the non-AOSP system apps such as Root Explorer if they are installed as system app.
Acknowledgments:
Only the odex.bat was created by me. Similar projects were done in past but most of the downloads are broken. So, I collected together different stuff from different places to put together this package.
adb.exe is from the RATC batch ROOT.
adb dlls are from Android SDK
odex.sh is from Paul O Brian from MoDaCo (pastebin.com/EZLWUdea)
zip, zipalign and dexopt-wrapper are from XDA (http://forum.xda-developers.com/showthread.php?t=734236)
Next aim: Odex for apps in data/app
Update:
I got 1017 on quadrant and 61.8fps on swiftdroid 2.0 M6 overclocked to 844MHz(offline mode with wifi on. No apps except system apps). It must be noted that sometimes odexed ROM performs slightly slower in benchmarks but the difference is very small. However, this does not mean their performance is lower. Odex means apps could load fast thereby making app switching, app loading really fast. And, it also reduces system RAM usage which means more apps could stay in memory making multi-tasking easier. Odexing is something like swap or compcache. Sacrifice something to gain something else. This is for some people who think odexing is useless. The drop in speed is so small that it cannot be noticed without a benchmark but the performance of the phone increases noticeably due to more space in dalvik and RAM.

Nice work.
Few remarks.
1) you need busybox installed for find
2) "busybox --install" defaults to /usr/bin (not available on android)
use "busybox --install ." when you cat-ed it to /system/xbin
Something seems not OK though with the odex.sh script?
Code:
Unable to create './Contacts.odex': File exists
zip warning: name not matched: classes.dex
zip error: Nothing to do! (./Contacts.apk)
Unable to open './Contacts.apk' as zip archive
failed on './Contacts.apk.new' - No such file or directory
Unable to create './VoiceSearch.odex': Permission denied
Unable to create './Music.odex': File exists
zip warning: name not matched: classes.dex
Cheers

Hmm, sorry, I just started to assume busybox is default since the two ROMs of concern(Joe's. Gingerbread and swiftdroid) had busybox.
Those apks are already odexed. You are on a partially odexed rom. Nothing to worry.
tweakradje said:
Nice work.
Few remarks.
1) you need busybox installed for find
2) "busybox --install" defaults to /usr/bin (not available on android)
use "busybox --install ." when you cat-ed it to /system/xbin
Something seems not OK though with the odex.sh script?
Code:
Unable to create './Contacts.odex': File exists
zip warning: name not matched: classes.dex
zip error: Nothing to do! (./Contacts.apk)
Unable to open './Contacts.apk' as zip archive
failed on './Contacts.apk.new' - No such file or directory
Unable to create './VoiceSearch.odex': Permission denied
Unable to create './Music.odex': File exists
zip warning: name not matched: classes.dex
Cheers
Click to expand...
Click to collapse
Sent from my GT540 using XDA App

i just applied a cm7 theme and the rom is still stable and the theme was applied after running the batch file

That depends on the theme. A theme that modifies odexed system apks will break things while an apk that modifies only the unodexed system apks will work. So, for most users, it would be safer to say that you shouldn't apply themes.
Sent from my GT540 using XDA App

First post has been updated.
Sent from my GT540 using XDA App

if you want to get even more ram odex your framework ... On my froyo with odexed framework i got 123mb ram with stock autokiller values This is only odexing system/app so you are able to theme your framework without problems ...

mikegapinski said:
if you want to get even more ram odex your framework ... On my froyo with odexed framework i got 123mb ram with stock autokiller values This is only odexing system/app so you are able to theme your framework without problems ...
Click to expand...
Click to collapse
I will try that. I was trying to odex data/apps. I odexed quadrant apk and saw a small gain of around 1% but it could be purely due to error or differences in conditions.
Framework isn't odexed doesn't mean all themes would work. Some themes modify other apks for more customizations. So, if you apply such a theme, it will break things. Better be safe than sorry. Saying that most themes would work, people might try to flash all themes thinking it won't break anything. It's just safer to deodex before theming. Of course, if you know what theme modify only framework and what theme modifies other apks, this shouldn't be a concern.
Update: odexing framework apk has reduced free memory to 60MB from previous 75MB

Might try add this into my app Root Toolbox if that's ok?

lukemovement1 said:
Might try add this into my app Root Toolbox if that's ok?
Click to expand...
Click to collapse
Hmm. You can but it's not a good idea. I tried odexing via terminal emulator but it fails.
Basically, this would not work if you try via root toolbox or rather it increases chances of being bricked. However, I noticed you had the scripts needed to flash an update.zip. If that's the case, you'll need to prepare an update.zip in real time and flash it via recovery.
http://forum.xda-developers.com/showthread.php?t=734236 This script moves the apps to SD and odexes. You will have to remove the appsupdate.sh and instead create an update.zip from odexed apps in sdcard. My script on the other hand, directly odexes without any user interaction.
On the other hand, I'd be glad to see this being simplified enough to pressing a button in root tool box. Only the bat script is mine. The rest are from other sources. I guess it shouldn't be a problem as long as you give credit to Paul O Brian from MoDaCo and the person who wrote deoxopt-wrapper.
And, btw, I noticed a small issue in your app. It has NO WARNINGS and NO CONFIRMATIONS! This is a real downer for an app like Root Toolbox which could brick your phone. You should ask for user confirmation whenever an user attempts to do a task that might brick your phone.

I am planning on adding the confirmation dialogs as soon as I can get back to my computer. For the odexing at runtime ill see if it works with app that don't have a GUI. If not ill do some kind of update.zip.

I'm on m6 and want to odex including framework how do I do this?
Sent from my GT540 using XDA App

Danzano said:
I'm on m6 and want to odex including framework how do I do this?
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
Read start post.
And, to odex framework, you need to modify the line which says cd /system/app to cd /system/framework in odex.sh and go through same procedure.
I odexed framework but it made my ROM very unstable.

Hmmm maybe not such a good idea then
Sent from my GT540 using XDA App

this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
starting odexing...it might take a few minutes to finish...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
your device is now odexed
is this right or is something wrong?

what way did you try and odex the rom?

the quick windows way

have you want to the system/app folder to see if any odex files there?

system/apps all apks no odex

try using script manager and set the script to run on boot to see if it work that way.

[MOD] Enable init.d scripts support on stock kernel

Hello!
This is a small mod, inspired by non other than our great DoomLord (so if it helped you, thank him/donate to him/worship him ) and his thread in the X10 section.
I am trying a lot of things on my phone, so I often switch back and forth from stock kernel to DoomKernel.
However, I use lots of init.d scripts (my favorite one being SuperCharger)
and I just don't want to lose this feature when I'm on stock.
So, without further ado, here are the steps that are needed to make init.d scripts run automatically at boot on stock kernel.
Requirements:
1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel by nAa.
5. Root Explorer or any other similar app.
Instructions:
1. Download the attached zip and place it in a folder in your SD card.
2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
a. If the file install-recovery.sh is not there, then press Menu and create a New File.
Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
Paste this text in it:
Code:
#!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
Save it and delete any .bak file that Root Explorer might have created. Set the permissions as in the attached screenshot.
OR
b. If the file install-recovery.sh is already there, long-press on it and select Open in Text Editor. Paste this text in the end:
Code:
# init.d support
busybox run-parts /system/etc/init.d/
In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***
3. Reboot into Recovery and flash the init.d-autorunner-stock.zip.
4. Reboot your phone and with Root Explorer go to /data/local/tmp.
There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".
5. Now you can use your favorite init.d scripts on stock kernel!
If you want to check if the scripts you want to use actually work, please refer to one of my older threads about how to test them.
*** I am not including an install-recovery.sh because this is the file that Link2SD depends on, so it's better if you modify it yourself, rather than use mine.
Let me know if it worked for you!

iridaki said:
Hello!
This is a small mod, inspired by non other than our great DoomLord (so if it helped you, thank him/donate to him/worship him ) and his thread in the X10 section.
I am trying a lot of things on my phone, so I often switch back and forth from stock kernel to DoomKernel.
However, I use lots of init.d scripts (my favorite one being SuperCharger)
and I just don't want to lose this feature when I'm on stock.
So, without further ado, here are the steps that are needed to make init.d scripts run automatically at boot on stock kernel.
Requirements:
1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel by nAa.
5. Root Explorer or any other similar app.
Instructions:
1. Download the attached zip and place it in a folder in your SD card.
2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
a. If the file install-recovery.sh is not there, then press Menu and create a New File.
Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
Paste this text in it:
Code:
#!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
Save it and delete any .bak file that Root Explorer might have created. Set the permissions as in the attached screenshot.
OR
b. If the file install-recovery.sh is already there, long-press on it and select Open in Text Editor. Paste this text in the end:
Code:
# init.d support
busybox run-parts /system/etc/init.d/
In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***
3. Reboot into Recovery and flash the init.d-autorunner-stock.zip.
4. Reboot your phone and with Root Explorer go to /data/local/tmp.
There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".
5. Now you can use your favorite init.d scripts on stock kernel!
If you want to check if the scripts you want to use actually work, please refer to one of my older threads about how to test them.
*** I am not including an install-recovery.sh because this is the file that Link2SD depends on, so it's better if you modify it yourself, rather than use mine.
Let me know if it worked for you!
Click to expand...
Click to collapse
Was looking for this...!!! Thanks...!!!
Sent from my LT15i using xda premium

thank you. but what is this script for? Can you explain it 2 me?

mercury_beta said:
thank you. but what is this script for? Can you explain it 2 me?
Click to expand...
Click to collapse
This is a setup in order for scripts placed in /system/etc/init.d to be executed automatically at boot. Such scripts can do lots of things, like RAM optimisation, CPU scaling, mount options, etc etc etc.

Can the script be added to hw_config.sh? Will it be execute on boot? Inteks' swap2cache script can be added to hw_config.sh too.
Sent from my digital typewriter..

emannxperia said:
Can the script be added to hw_config.sh? Will it be execute on boot? Inteks' swap2cache script can be added to hw_config.sh too.
Sent from my digital typewriter..
Click to expand...
Click to collapse
Sorry, I don't know for sure. But probably yes.

Great post mate, thanks. (already give you thanks button)

Seeing if this works on ray
I get this file in the init.d folder after.flashing the file
#!/system/bin/sh
touch /data/local/tmp/init.d_log_test.txt
echo "done" >> /data/local/tmp/init.d_log_test.txt
Not in data/ local
I have ran supercharger script and files are appearing in inlit.d folder think it's working
Edit : tested it as per the thread further up it would seem its all working!
Sweet
Hope it is ok I have shared this on the Ray thread? (I have linked back to your thread)
sent from my gorgeus Xperia Ray

Hi iridaki thanks for your little mod here! I just want to give a hint of what might been a little issue but might make your whole mod is not running. You do mention about changing permission on install-recovery.sh, but you gave it as a picture. The Problem is XDA on web these days is not arranging the image as inline, but as an attachment. So i and chiefy009 did the same mistake, not changing the permission because it is just a one line and not clear enough. Please add additional step like:
3. Make sure install-recovery.sh have permissions of rwxr-xr-x
Click to expand...
Click to collapse
Thanks

Worked for me. I'm using Sony Ericsson Xperia Pro MK16i with stock rom (root + cwm including).

Hello
doesn't worked for me ;(
Sony Xperia Arc S (LT18i) build ver. 4.1.B.0.587
nAa's CWM 5.0.2.7
rooted
there is no this test log file in /data/local/tmp afret applying the zip
so what i have after "apply zip file" in recovery meny and rebooting:
in /system/xbin new binary file run-parts
in /system/etc new folder init.d with test99 script in it
in /sysrem/etc file install-recovery.sh which was made by us previously
it looks like would work...but it does not
So, what can i do myself?
Thank you in any way

◄ ▌[24.Jan.13][MOD][Guide] Brainmaster's Tweaks for Android 4+ ▌►

◄ ▌[24.Jan.13][MOD][Guide] Brainmaster's Tweaks for Android 4+ ▌►
Here is the description of the Tweaks:
Scripts in the /system/etc/init.d folder:
08dalvik - Moves the Dalvik cache from the ext4 /data/dalvik to the faster yaffs /cache/dalvik partition
95zipalign - This is more enhanced zipaligning method. Its zipaligning the apps in the /system/app and /data/app. It also creates the database that contains infos on apps that are already zipaligned, and checks that databe on reboot. If all apps are zipaligned, it skips the zipalign process. Zipaligning is useful because its reducing the amount of used RAM
99bmtweak - Contains the tweaks that I've collected and enhanced over the time. Included are IO tweaks, TCP tweaks, SDCard ReadAhead tweak, SQLite Vacuum Database tweak
hosts file in the /system/etc folder:
Hosts file makes your Phone ADFree.
resolv.conf file in the /system/etc folder:
Google DNS Servers
placeholders in the /system/app and /data/app folders:
If you want to add a system app or install data/app with the CWM Zip file, just drop the apk in the /system/app or /data/app folder in the CWM Zip file and they will be installed when you flash the CWM Zip.
/kernel folder:
Enables the init.d script support.
updater-script in the /META-INF/com/google/android folder:
Deletes the Cache and Dalvik Cache, mounts the /data and /system partitions, copying the needed files. It sets the permissions. If you are editing that file, be SURE to use the Notepad 2 or Notepad ++ and use the Unix file system encoding when saving the file, not the regular Notepad Windows app.
build.prop tweaks Injector in the /tmp folder:
Injects the values in the /system/build.prop file. The /tmp/mytweaks.sh file shouldn't be edited! The file /tmp/misc contains the buildprop tweaks. You can add your own build.prop tweaks in that file.If you are editing that file, be SURE to use the Notepad 2 or Notepad ++ and use the Unix file system encoding when saving the file, not the regular Notepad Windows app, also IF you use comments (#Disable.ADB.Notification.Icon), DON'T use spaces, use ONLY the underline or dot character! These tweaks are included:
Code:
#Disable.ADB.Notification.Icon
persist.adb.notify=0
#Disable.Google.OTA.Checkin
ro.config.nocheckin=1
#Disable.Google.Reports
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
#Enable_Google_DNS_Servers
net.dns1=8.8.4.4
net.dns2=8.8.8.8
#HSPA.Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=16
ro.ril.hsupa.category=8
#Dalvik.Optimization
dalvik.vm.execution-mode=int:jit
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v
Installation
Step 0: You must be rooted!
Step 1: Download the Busybox installer app and install the Busybox to /system/xbin. Again - install the Busybox to /system/xbin not to /system/bin!
Step 2: Reboot to recovery and install the BM.Tweaks.NEXUS.S.zip file.
Optional Memfree tweak - set to 100 MB:
In order to use the Memfree tweak on every ROM, extract the /system/framework/services.jar from the ROM and upload it to android.mimic.ca, let the site edit the file, download the edited services.jar and put it in the BM Memfree zip file. Then flash the BM Memfree zip in the Recovery.
The attached Memfree zip is for the stock JZO54K ROM.
Optional BM Seeder:
You can read everything about the tweak here.
This is my version adjusted for the Nexus S.
How can I be sure that the tweaks are working?
Open the RootExplorer and click on the /cache folder. IF the dalvik-cache folder is present, THEN the tweaks are working properly. Check also your /system/build.prop file for the #Brainmaster Tweaks area.
The tweaks are universal - not ROM version related, and can be flashed over any ROM but ONLY for NS or NS4G.
Disclaimer:
ALWAYS make a NANDroid Backup of your current ROM so that you can go back if you don't like the tweaks.
I will NOT reply any users PM's regarding this thread or my ROMs, only the DEVs should contact me over PM.
If you are user and have questions, write HERE in the thread.
BEFORE asking any questions, make sure that you read this post.
​

I have edited the Mobile_Sensei's ROM prepare tool and added the deletion of the /sdcard/.android_secure folder.
Now when you flash new ROM and want to do a clean install, just flash this file.
It does following:
deletes /sdcard/.android_secure
deletes /cache
deletes /data/dalvik-cache
formats /cache
formats /data
formats /boot
formats /system
Happy flashing!
Here you can also find just the Dalvik-Wiper when you're updating your ROM.

Reserved 2.

Reserved 3.

Reserved 4.

Nice!
Sent from my Nexus S using XDA App

Thank you for sharing this
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.

Thanks!
Now I have something more to play with my personal version of MIUI ICS

Thanks man
But I have a question, For the ICS custom rom, most of them come with boot.img and I tried on KANGY-S but i got stock on google sign in the beginning of boot.
So can you tell me which package should I use?

Thx
10char

v2 uploaded.
Changelog: Bugfixes in Build.prop Injector script.
If you are using the /tmp/misc to add your build.prop tweaks DON'T use commented explanations, like this one:
Code:
#Disable ADB Notification Icon
Use only the tweaks!

after heard your announcement yesterday , this kinda makes me feel this is your "legacy"(no offence) ...
and , thanks for share all of these

v3 comes later today.

How do we merge multiple languages in one rom?

djjonastybe said:
How do we merge multiple languages in one rom?
Click to expand...
Click to collapse
When compiling the new ROM, fetch existing language strings and compile.
For existing ROM - like MIUI - decompile apps and framework, add language strings, recompile apps and framework. Language strings need to match every build, you can't use strings from older builds on newer without editing.
Enough said.

Changelog:
v3:
Code:
- Corrected errors in the RAM and TCP Tweaks
- Added Google DNS Servers in resolv.conf and build.prop injector
- Added tweaks for the CM9

@ Brainmaster`s Dude thanks a lot for this release,
Just I want to request something, can you make a package for gingerbread rom which come with boot.img. the one you released i doesnt come with boot.img.
i really appericate it buddy.

frost866 said:
@ Brainmaster`s Dude thanks a lot for this release,
Just I want to request something, can you make a package for gingerbread rom which come with boot.img. the one you released i doesnt come with boot.img.
i really appericate it buddy.
Click to expand...
Click to collapse
Which one? Have you checked if there is already /system/etc/init.d folder present on your ROM?

brainmaster said:
Which one? Have you checked if there is already /system/etc/init.d folder present on your ROM?[/QUOTE
Actually, Im using CM7.2.0 Kang and yes there is init.d folder on my rom, but i couldnt find any of your tweaks in this folder. can i just simply add to the rom using root explorer?
Actually , I meant the first package in the list which is belongs to ICS and gingerbread roms.
Click to expand...
Click to collapse

frost866 said:
Actually, Im using CM7.2.0 Kang and yes there is init.d folder on my rom, but i couldnt find any of your tweaks in this folder. can i just simply add to the rom using root explorer?
Actually , I meant the first package in the list which is belongs to ICS and gingerbread roms.
Click to expand...
Click to collapse
That is strange - so you have installed it through the CWM and yet there are still no tweaks present in the init.d?
Yes, copying them in the init.d folder and setting the permission to 750 also works.

Gingerbread 2.3.7 Ext3 SD build for topaz ICB-YK-5.8

Gingerbread 2.3.7 Ext3 SD build for topaz ICB-YK-5.8
This rom base on ***yi's ICEBREAD. modified for topaz only.
it work with ext3 format if use 01383 kernel.
Phone Ok,
BT ok,
WIFI ok,
GPS ok,
Market OK,
ALL ok,
how to install.
1. format the SD card to ext3. /System 200M, /Data 400M, /Cache 200M
2. unzip the npkboot.zip to root of SD card.
3. run haret and recovery the update-ICB-Yaka.zip , reboot.
4. restore the luncherpro. setup google account.
change log:
V5.8
Add more audio alarm files
Fixed First incoming call reboot bug
Modify the hosts file to block AD
V5.0
super fast.
V4.2
Add zipalign
V4.1
Add dual Mount SD,
Add GoogleQuickSearchbox
add es file explorer
replace the market to 3.4.4
Remove Calculator and add RealCalculator
add HTC calibrate
add email and remove gmail
add voicedialer
replace all google app
replace the home wallpaper,
replace SoundRcorder
replace Spareparts
replace ts-calibration for topaz
replace 3 audio lib file for topaz.
replace 5 cvs file for topaz
add more audio
Change the mode to diamond 2
Change region to CN
Modify the updater-script for original kernel with ext3
I make a download list for all versions.
Download here:***
V3.
npkboot
Update_IB_Yaka_3.zip
V4.1.
Recovery
ICB-Yaka-4.1.zip
V4.2
ICB-Yaka-4.2.zip
V5.0
Npkboot
ICB-Yaka-5.0.zip
V5.8
***

Hey, you fixed the incoming call reboot bug?!? Please provide source!!

can you please provide a little more guidance in installing this.
how to install.
1. format the SD card to ext3. /System 200M, /Data 400M, /Cache 200M
2. unzip the npkboot.zip to root of SD card.
3. run haret and recovery the update-ICB-Yaka.zip , reboot.
4. restore the luncherpro. setup google account.
questions -
1. can i not have a storage partition more than 400M?
2. Root of Sd card. Which partition is that?
3. please provide more details on step 3 & 4.

Thanks for this great ROM !!! it's the only one I was able to install.
I have a little problem with Wifi, it doesnt work
What do i need to do ?

assib said:
Thanks for this great ROM !!! it's the only one I was able to install.
I have a little problem with Wifi, it doesnt work
What do i need to do ?
Click to expand...
Click to collapse
how did you install it. can you please provide some guidance or more details please than what is above.

ds4 said:
how did you install it. can you please provide some guidance or more details please than what is above.
Click to expand...
Click to collapse
- You also need a FAT32 partition in order to unzip the directory to the root of your sdcard. Windows os can't access the ext3 partitions
- Step No. 3 "run haret and recovery the update-ICB-Yaka.zip , reboot."
After running haret, you need to choose from the menu to install android from a zip file
and then you choose the "update-ICB-Yaka.zip" file.
After installing, run haret again but don't press the volume down key just let it go.

WiFi didn't work the rom Is great and fast
also dos't support arabic . if that Possible how i do that I liked the rom very much and I want to keep useing it
thanx