[Samsung Galaxy SL i9003] shy.less:
PART3

Build.prop and android params

Listed partial by TheFrankestain, thanks

* YOU MUST ADD IT AT BOTTOM OF /system/build.prop and delete cache and reboot*

ro.ril.hsxpa=2

This will enable High-Speed_Downlink_Packet_Access and High-Speed Uplink Packet Access ( HSDPA and HSUPA )

ro.ril.gprsclass=10

gprs class, see this LINK

ro.ril.hep=1

0 meaning off, 1 activated

ro.ril.enable.dtm=0

Dual Transfer Mode , set 1 only if your network support it

ro.ril.hsdpa.category=8

Folllow this ( thanks to tnpapadakos )

#ro.ril.hsdpa.category :
# Cat 1 = 1.2 Mbit/s
# Cat 2 = 1.2 Mbit/s
# Cat 3 = 1.8 Mbit/s
# Cat 4 = 1.8 Mbit/s
# Cat 5 = 3.6 Mbit/s
# Cat 6 = 3.6 Mbit/s
# Cat 7 = 7.2 Mbit/s
# Cat 8 = 7.2 Mbit/s
# Cat 9 = 10.1 Mbit/s
# Cat 10 = 14.0 Mbit/s
# Cat 11 = 0.9 Mbit/s
# Cat 12 = 1.8 Mbit/s
# Cat 13 = 17.6 Mbit/s
# Cat 14 = 21.1 Mbit/s
# Cat 15 = 23.4 Mbit/s
# Cat 16 = 27.9 Mbit/s
# Cat 19 = 35.3 Mbit/s
# Cat 20 = 42.2 Mbit/s
# Cat 21 = 23.4 Mbit/s
# Cat 22 = 27.9 Mbit/s
# Cat 23 = 35.3 Mbit/s
# Cat 24 = 42.2 Mbit/s
# Cat 25 = 46.8 Mbit/s
# Cat 26 = 55.9 Mbit/s
# Cat 27 = 70.6 Mbit/s
# Cat 28 = 84.4 Mbit/s

ro.ril.enable.a53=1

a53 enabling

ro.ril.enable.3g.prefix=1

1 will show 3g prefix next to network signal

ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449

bitmask &

ro.ril.hsupa.category=6

See this:

#ro.ril.hsupa.category :
# Cat 1 = 0.73 Mbit/s
# Cat 2 = 1.46 Mbit/s
# Cat 3 = 1.46 Mbit/s
# Cat 4 = 2.93 Mbit/s
# Cat 5 = 2.00 Mbit/s
# Cat 6 = 5.76 Mbit/s
# Cat 7 = 11.5 Mbit/s

net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960

Redefinite TCP Standard size packet, it will increased overall speed

ro.ext4fs=1

will set ext4fs prop to android system, increased performance if you are under ext4

persist.sys.purgeable_assets=1

More speed!

persist.sys.shutdown.mode=hibernate

NOT COMPATIBLE FOR OUR PHONE, we have not hibernate shutdown mode

ro.ril.disable.power.collapse=0

is ultra-battery-life mode, when phone're sleeping

ro.ril.enable.cnap

Celler name presentation

debug.sf.hw=0

Render with GPU Apps ( see last #3 post for better info )

pm.sleep_mode=1

Permits better sleep mode ( battery ++ )

wifi.supplicant_scan_interval=150

Android ( when wifi on ) periodically scan for new network, you can set time between its for better battery when wifi on

windowsmgr.max_events_per_sec=150

Increase the max events record by windows manager , better scroll

debug.performance.tuning=1
video.accelerate.hw=1

GPU Tune for scrolling performance

debug.sf.nobootanimation=1

for me, not work, it will theorically disable boot animation for faster boot

ro.HOME_APP_ADJ=1

USE ONLY IF YOU DONT USE SUPERCHANGER

ro.lge.proximity.delay=25
mot.proximity.delay=25

decrease proximity delay for better experience

ro.sf.lcd_density=240

Simply not sense

ro.kernel.android.checkjni=0

disable check jni

ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000

increase media quality

WHICH GOVERNOR DO U USE?
​

( ref: Simba501 )

SEE THIS

Anyway i suggest:

- Smartassv2 if you want performance over less battery

- InteractiveX if you want battery over less performance

CAN ANY KERNEL DEVELOPER INCLUDE LULZACTIVE CPUFREQ-DRIVER IN OUR KERNELS? ITS THE PERFECT GOVERNOR , EITHER FOR BATTERY AND PERFORMANCE

EGL TWEAK!​

Android header said:

#
# One line per configuration, of the form:
#
# D I TAG
#
# D: display (0: default)
# I: implementation (0: software, 1: hardware)
# TAG: a unique tag
#
# The library name loaded by EGL is constructed as (in that order):
#
# /system/lib/egl/libGLES_$TAG.so
# /system/lib/egl/lib{EGL|GLESv1_CM|GLESv2}_$TAG.so
#

in the stock ROM the egl.cfg is:

0 0 android
0 1 POWERVR_SGX530_125

what's meaning?

simply using cpu ( with gpu too ) to render all apps and system

if you modify to:

0 1 POWERVR_SGX530_125

it will use overall GPU render only, more fast and imho better Battery life because, CPU in our cases with overclock consume more than GPU

See original post: http://xdaforums.com/showpost.php?p=14323192&postcount=8