[Galaxy S III Android Development] auras76:
Kernels / mods

- KERNELS :

- STOCK KERNEL XXALF2 CWM :

- http://hotfile.com/dl/159553137/dceeced/KERNEL_STOCK_XXALF2.zip.html

- MODS FOR ROMAUR ROM :

- CALL RECORD :

- https://hotfile.com/dl/159805877/5cd97e2/Call_record.zip.html

- BATTERY STOCK XXALF2 :

- http://hotfile.com/dl/159649156/65bad87/Battery_stock_XXALF2.zip.html

HERE IS MY TWEAKS

INIT.D TWEAKS :

-Zpaling - Zipaling apps on every boot , this make the phone to boot faster and better ram usage.

-Complete - Remount system to rw (only read).

-Sqlite - Optimizing and defragging database files.

–Mount system with noauto for better apps loading.

-Mount system with noatime for speed system.

-Remove dalvik-cache on every boot (rm-r).

-Syctl – Enable sysctl.conf from system /etc

SYSCTL:

-vm.dirty_background_ratio= 55

-vm.dirty_ratio = 90

-The first of the two (vm.dirty_background_ratio) defines the percentage of memory that can become dirty before a background flushing of the pages to disk starts. Until this percentage is reached no pages are flushed to disk. However when the flushing starts, then it's done in the background without disrupting any of the running processes in the foreground.

-Now the second of the two parameters (vm.dirty_ratio) defines the percentage of memory which can be occupied by dirty pages before a forced flush starts. If the percentage of dirty pages reaches this number, then all processes become synchronous, they are not allowed to continue until the io operation they have requested is actually performed and the data is on disk. In case of high performance I/O machines, this causes a problem as the data caching is cut away and all of the processes doing I/O (the important ones in dCache pool) become blocked to wait for io. This will cause a big number of hanging processes, which leads to high load, which leads to unstable system and crappy performance.

-vm.swappiness=0 - We don't swap

-sysctl -w vm.panic_on_oom=1

-This enables or disables panic on out-of-memory feature. If this is set to 1, the kernel panics when out-of-memory happens. If this is set to 0, the kernel will kill some rogue process, by calling oom_kill(). Usually, oom_killer can kill rogue processes and system will survive. If you want to panic the system rather than killing rogue processes, set this to 1.

-vm.vfs_cache_pressure=20

-This is more interesting. File system cache (dentry/inode) is really more important than the block cache above, so we really want the kernel to use up much of the RAM for them. The default value is 100, and what you want to do is lower that value to tell the kernel to favor the file system cache and not drop them aggressively.

BUILD.PROP

-debug.sf.hw=1 - Render UI with GPU

-debug.performance.tuning=1 - video.accelerate.hw=1 -( Increase overall touch responsiveness)

- wifi.supplicant_scan_interval=180 - pm.sleep_mode=1 - ro.ril.disable.power.collapse=0 - (Save battery)

- windowsmgr.max_events_per_sec=200 - (Scrolling responsiveness)

- ro.media.enc.jpeg.quality=100 - (Raise JPG quality to 100%)

KERNEL :

- ro.secure=0 -(This gives access to all adb root commands)

- ro.debuggable=1 - (Enable adb on usb by default)

- persist.sys.usb.config=mtp,adb - (Enable usb debugging)