Database Users

[MOD] Build.Prop Tweaks

I’ve been scouring XDA and the net for some ways to make our phones a little bit better. What I have found is that you can alter your Build.Prop to work to your advantage.
Did you know that if there is an app exclusive to the Droid X and only works for the Droid X (not withstanding hardware issues), we can change our Build.Prop from Milestone XT720 to Droid X (whatever that model number is) and get into the market and download it?
There also other “tweaks” to you Build.Prop that are beneficial in many other ways, Data strength, Video and Camera resolution, GPS lock, Power saves,…
The below is what I have been able to find, save and test for most of our builds on the Milestone XT720, but first…
Choice is something that has been fought for, relinquished, dreamt of and lost. Here in XDA we have a choice to either use on not to use. This is YOUR choice. If YOU decide to use these tweaks, any problems that arise are YOUR responsibility. Now that is out of the way, here you are.
Oh and one other thing:::::::::::Make a backup of at the very least your /system because if something goes awry while editing the Build.Prop, all you have to do is restore your /system, since that is where the Build.Prop is located.
**XT720 Users->I have not tested these on any of the MIUI builds or Fjfalcon's CM7 release (per Sebastiman -all tweaks but camera work on Fjfalcon's CM7).**
Per Fjfalcon some of these are NOT working on [ROM][KANG][2012.01.30] CyanogenMod 7.2.0 RC0 Milestone XT720
If any Devs want to use these, that is cool. Just make sure you put in your OP that they are already on there so no one duplicates them on their Build.Prop.
Motorola XT720 "Stock" Build.Props are located here (thanks to AA1973 and 3rdstring) http://forum.xda-developers.com/show....php?t=1327141
I presume most of us are using Root Explorer or something extremely similar. You just need to have Root access and able to edit the Build.Prop text. I user Root Explore so that is what these are based off.
1, Open "Root Explorer" and click the R/W
2, Go to /system/build.prop.
3, Long-presson Build.Prop and you’ll see a pop up.
4, Text Editor.
5, Type in those few line of words below into the last line of the text then save.
6. Reboot twice
Data Tweaks Increase download/upload/3G speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=0
ro.ril.hsdpa.category=8 (or 10,12,14) Still looking for more of these though.
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
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
For some reason XDA won't let me take out the spaces between 4096, 16384. I have edited it twice and it still shows up with the spaces on OP. Should read 4096,16384 for all 5 (default, wifi, umts, gprs and edge) with no space between 6,1 or 16384
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
POWER SAVES
Allows the phone to sleep better
ro.ril.disable.power.collapse=1
Saves power when phone is sleep
pm.sleep_mode=1
Allows your wifi to scan less, saving more battery
wifi.supplicant_scan_interval=150 or 180 (your choice)
Helps Scrolling Responsiveness
windowsmgr.max_events_per_sec=150
Increase overal touch responsivenss
Debug.performance.tuning=1
Video.accelerate.hw=1
MEDIA TWEAKS
Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
Increases quality of photo and videos
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Raises quality of JPEG images
ro.media.enc.jpeg.quality=90 or 100 (your choice)
Better camera and video taking results
camera/camcorder mods
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led ***May interfere with Xenon
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
BOOT TWEAKS
Gives your phone no boot animation
debug.sf.nobootanimation=1 ***This might freak out some people not seeing their animation and cause unnecessary battery pulls***
SYSTEM TWEAKS
Forces your home launcher into memory
ro.HOME_APP_ADJ=1
Change the Dalvik VM heap size
dalvik.vm.heapsize=64m can use 24, 32 is default, 48, 64
To disable usb debugging popup
persist.adb.notify=0
To give your phone an HD effect fitting a little more on the screen, look for this in your current build.prop and change the 240 to:
qemu.sf.lcd_density=X (225 or 230) ***This has been known to cause FC’s for the Market, so may not be a good tweak but I still put it in here just in case*** See Changelog
To stop the phone from waking up when pressing the volume key
ro.config.hwfeature_wakeupkey=0
To make the phone ring faster when dialing out
ro.telephony.call_ring.delay=800
Disable black screen issue after call
ro.lge.proximity.delay=25
mot.proximity.delay=25
Screen ppi or font density
ro.sf.lcd_density=240
THESE ARE ONES THAT I DO NOT KNOW WHAT THEY DO AND HAVE NOT TESTED
To enable the hard key lights to stay on while the screen is on and not timeout
ro.mot.buttonlight.timeout=0
Try disabling BLN if your having trouble getting this to work
To make the phone come off of the "black screen" in the middle of, or the end of phone calls when you pull the phone away from your face
mot.proximity.delay=150
**May kill the dialer**
Render UI with GPU
debug.sf.hw=1
Fix some application issues
ro.kernel.android.checkjni=0
Defrags database files
for I in \
‘find /data –iname “*.db”’
do \
sqlite3 $i ‘VACUUM; ’ ; ***This might be something for devs to look into using for something, not sure what***
Credits to the following and links to their pages.
Master&Slaves http://forum.xda-developers.com/showthread.php?t=1151608
knzo http://forum.xda-developers.com/showthread.php?t=1227269
Jokersax11 http://forum.xda-developers.com/showthread.php?t=1263768
Change/Edit log:
11/4/11:::
1-Per peshovec qemu.sf.lcd_density::: if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
2-Per Sebastiman all tweaks work on Fjfalcon's CM7 except camera ones (caused boot loop)
11/9/11:::
Took out spaces in net.tcp.buffersize as was a copy/paste issue from Word.doc to XDA.
1/6/12:::
Took out some of the Motorola XT720 ROM specific verbiage as this is being view by way more people/devices than the XT
2/1/12:::
Noted the some of these are not working on [ROM][KANG][2012.01.30] CyanogenMod 7.2.0 RC0 Milestone XT720

WOW Awesome dude! Nice work! Can't wait to test them! I wonder if there are reversals? Or probably is if I knew anything about coding lol. Great job dude looks promising. Can't believe the excitement we are still getting out of our phones lol.

LibertyMonger said:
I wonder if there are reversals?
Click to expand...
Click to collapse
Just make sure you have a back up of /system because that is where the build.prop "lives". Also I have found that when I edit them, it creates a .bak backup, but you can never fail restoring a nandroid of just the /system.
As a side note, AA1973 gave the "stock" Build.Pro for the MIUI and 3rdstring (of course) uploaded a .zip with damn near the rest of them here http://forum.xda-developers.com/showthread.php?t=1327141
Plus is you adjust a value, wirte down what the original was and if new doesn't work for you, jsut pust back in the original. This way you shoudl only have to restore /system nandroid is something screws up majorly.

Great work there!
I'd like to call attention to
Code:
Change the Dalvik VM heap size
dalvik.vm.heapsize=64m
Since we have rather limited memory, its better if we stick to a heap size of 32 (default in most roms) personally I use 24 and feel that multitasking is much better than at 32 when most apps get killed repeatedly.

That's cool. I know that when I was on Kahl's V4, mine was at 48 and never had a problem with it. Think the intervals are 24, 32, 48, 64
Edited OP with that.

look cool man, will be take time to check & test soon!

ro.media.capture.flash=led ***Might want to check with MZ or Fjfalcon on these b/c of Xenon... In tweaking the camrera and camcorder is it ok to skip this one if it is not sure?

abet1017 said:
ro.media.capture.flash=led ***Might want to check with MZ or Fjfalcon on these b/c of Xenon... In tweaking the camrera and camcorder is it ok to skip this one if it is not sure?
Click to expand...
Click to collapse
Try it out but ok to skip too. I have read that this might have something to to with the LED notifications that we have all been looking for. Will keep looking into this weekend for that part.

build.prop text files
Hey Wood, would we be able to use these build.prop tweaks? There are text files to download and place on SDCard rename them to build.prop then use root explorer to move them to /system

Woodrube said:
To give your phone an HD effect fitting a little more on the screen, look for this in your current build.prop and change the 240 to:
ro.sf.lcd_density=X (225 or 230) ***This has been known to cause FC’s for the Market, so may not be a good tweak but I still put it in here just in case***
Screen ppi or font density
ro.sf.lcd_density=240 ***This is how MZ and Peshovec fixed the tiny little Korean keyboard on CM6***
Defrags database files
for I in \
‘find /data –iname “*.db”’
do \
sqlite3 $i ‘VACUUM; ’ ; ***This might be something for MZ, Fjfalcon and Peshovec could use for something, not sure what***
Click to expand...
Click to collapse
Thanks for your hard work, i'd like to put some comments
ro.sf.lcd_density -> if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
qemu.sf.lcd_density (here there is typo for the keyboard it should be qemu.sf.lcd_density, instead of ro.sf.lcd_density)
about defraging the database, may be including as part of openrecovery is better. I don't see the point to be defraged at every start..

After applying the tweaks, headset is not working... I don't know if it is related with the tweaks..... I'm using mz cm6 rc3 rom.
By rebooting I resolve the issue......

abet1017 said:
After applying the tweaks, headset is not working... I don't know if it is related with the tweaks..... I'm using mz cm6 rc3 rom.
By rebooting I resolve the issue......
Click to expand...
Click to collapse
Cool dude! Be interested in your feedback!

abet1017 said:
By rebooting I resolve the issue......
Click to expand...
Click to collapse
Don't forget you have to reboot twice.

peshovec said:
ro.sf.lcd_density -> if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
qemu.sf.lcd_density (here there is typo for the keyboard it should be qemu.sf.lcd_density, instead of ro.sf.lcd_density).
Click to expand...
Click to collapse
I will edit OP later on when I get to PC. Thanks for re-checking the lcd.density issue too

build.prop
All tweaks work fine on fjfalcons cm7
except the camera tweaks. it causes the phone to bootloop.

sebastimau said:
All tweaks work fine on fjfalcons cm7
except the camera tweaks. it causes the phone to bootloop.
Click to expand...
Click to collapse
Excellent. Will update OP and start working on fixing the camera tweaks.

Woodrube said:
Data Tweaks Increase download/upload/3G speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=0
ro.ril.hsdpa.category=8 (or 10,12,14) Still looking for more of these though.
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
Click to expand...
Click to collapse
Hey Wood, do I type in all these commands? save after the first set? Or what do I do...?
---------- Post added at 08:47 PM ---------- Previous post was at 08:27 PM ----------
Woodrube said:
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960[/B]
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
Click to expand...
Click to collapse
You see any typo's in here? The space between 163 84,? Is that correct?
***also have you tested these on Bravo?
***I got all the tweaks saved but I think I better leave well enough alone lol. Bravo is almost perfect as is everything is running great. What do you think Brian? Should I try these?

LibertyMonger said:
Hey Wood, do I type in all these commands? save after the first set? Or what do I do...?
Click to expand...
Click to collapse
You can type them all in at the same time, but when I did it I did ti in pieces to make sure each one was taking effect and if I got looped was able to determine which one caused it problem (like typo ro something like that).
LibertyMonger said:
You see any typo's in here? The space between 163 84,? Is that correct?
***also have you tested these on Bravo?
***I got all the tweaks saved but I think I better leave well enough alone lol. Bravo is almost perfect as is everything is running great. What do you think Brian? Should I try these?
Click to expand...
Click to collapse
I'll fix that in the OP. No spaces between 163 84. Should be 16384. XDA must have remarginalized them when I put it in here. I copied them from a WORD.doc when I was compiling.
I tested the data tweaks and a few of the system tweaks on Bravo and they worked fine. But if you have everything working fine for you, I would suggest either leaving it alone or bit-piece them in there. Don't want the lightning rod effect like you had in HM's ROM.
p.s. - Sorry I didn't respond sooner, I was mostly off-line this weekend and took a few extra days off. Kind of a brain recharge thing.

anybody have descriptions of these?
A lot of these are smaller / larger than what the "change to" value is...not sure how they're going to affect things, such as--
1. why are there 6 numbers for the tcp buffer sizes
2. I don't notice any performance diff modifying the max_events_per_sec
3. Proximity Delay-- is that in ms? If I think my prox delay is "too long" when I take phone away from face, I should make this smaller, right? How small is OK?

rancur3p1c said:
anybody have descriptions of these?
A lot of these are smaller / larger than what the "change to" value is...not sure how they're going to affect things, such as--
1. why are there 6 numbers for the tcp buffer sizes
2. I don't notice any performance diff modifying the max_events_per_sec
3. Proximity Delay-- is that in ms? If I think my prox delay is "too long" when I take phone away from face, I should make this smaller, right? How small is OK?
Click to expand...
Click to collapse
What ROM are you running? That would help me answer your questions a bit more clearly.

[CWM] Skeleton zips for system and user apps & build.prop optimization

http://forum.xda-developers.com/showthread.php?p=24233846
Just download the attached zip file according to your need, add apps.. flash.. enjoy.. Tested with cwm 5.0.2.7 touch..
********************************************************************************************************************************************************
Editing build.prop.
Even though some of the things are well known for us, some of them are new for me..So im jus posting it.
1.Force launcher into memory
Property
ro.HOME_APP_ADJ = 1
Function
This will force the Default launcher into memory. But your device should be having enough free memory, otherwise you will meet lags and performance will be reduced severely. Use a light weight launcher for this.
Values
0 : Turns off the feature. Frees up memory.
1: Keeps the default launcher in memory .Will have highest priority and Android auto kills it only when it’s really necessary.
2.Improving Camera Image quality
Property
ro.media.enc.jpeg.quality=100
Function
This will force the camera application to use 100% quality setting when saving camera images as JPEG
Values
1-100 : with 1 as the worst quality and 100 as the best quality.
3.Increase resolution of panorama image
Property
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
Function
This will force the panorama mode in the camera app to save the image at a higher resolution. This may not be supported by all phones. And since it is an Android 4.0 feature , you will need that android version as well.
Values
defres: Provide the full panorama image resolution.Consisting of all images.
frameres: Provide the resolution of each frame of panorama.
4.Improve performance in video playback and streaming
Property
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=true
media.stagefright.enable-record=true
Function
Android uses the media framework named “Stagefright” from Froyo ( Android 2.2 ) onwards. While Stagefright is more open and simple, it is sometimes buggy compared to the previously used OpenCore framework. However, Google has greatly improved its stability. These values might affect the stability of playback in some devices, if it is ruining your experience , then revert to the original values.
5.Improve touch responsiveness through Hardware Rendering
Property
debug.sf.hw=1
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
Function
This will force the system to use GPU for rendering each 2D frame in applications. Since android uses frame by frame rendering of the screen normally, this will offload the rendering to GPU by a huge amount and will make the user experience smoother.
Values
debug.composition.type values : GPU / CPU . GPU will make use of the graphic chip on your device for rendering each frame.
6.Disable Error Profiler
Property
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
Function
These commands enable or disable the error profiler in the android. For most android users, there is no use in having error profiling . however , some applications might make use of this for generating error reports.
Values
0 :Enable the feature. Better to delete the property if you don’t want to disable it.
1: Disables the feature.
7.Modify WiFi network scanning time.
Property
wifi.supplicant_scan_interval=180
Function
This command will be already present in all build.prop files. This controls the number of seconds the device waits before scanning for WiFi networks.
Values
Default value is 180 . It is in seconds . You can increase the value if you want to save more battery and doesn’t use WiFi extensively. Or else , you can decrease it , if you are dropping your WiFi signal often.
8.Disable logcat – Android Logger
Property
logcat.live=disable
Function
This command controls the Android Logcat file generation. This file is mainly used for debugging. Expensive disk reads/writes can be reduced by disabling Android logcat.
Values
disable / enable
9.Improve Voice Call clarity
Property
ro.ril.enable.amr.wideband=1
Function
This command controls the AMR audio codec’s property.AMR codec is used for voice calls.
Values
1 or 0 .
10.Disable Extended JNI Checks
Property
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
Function
“JNI does very little error checking. Errors usually result in a crash. Android also offers a mode called CheckJNI, where the JavaVM and JNIEnv function table pointers are switched to tables of functions that do an extended series of checks before calling the standard implementation.” . That’s the definition from Android developers documentation. While disabling this may cause some data loss when the application crashes, most applications ,which are popular, have been thoroughly checked and hence will be using precious CPU time for extended checks . Save that time by disabling this.
Values
0 / 1 : disable / enable .
11.Disable Android Device Check In.
Property
ro.config.nocheckin=1
Function
Every Android device checks in at the Google Servers when an internet connection is found, this helps Google in tracking the number of installations and the statistics of different android versions. This can be disabled to save for saving traffic and some CPU time, due to the frequent polling for checking internet connection.
Values
1/0 for disabling and enabling , respectively.
12.Increase Voice Call Audio Adjustment Steps.
Property
ro.config.vc_call_steps=20
Function
By Default, android offers seven audio levels for calls. This can be altered through this command , if you want to fine adjust the volume of your voice calls. This won’t increase the volume if it’s already low. But you can manage it by more precisely.
Values
Number of steps as integers. 7-20 is recommended. 7 is the default.
Editing Build.Prop
For editing build.prop, your device should be rooted. That’s the first requirement.
It is at /system/
If you have Root Explorer / ES File Explorer installed on your device you can edit from the device itself. More easier method is to get he application named build.prop Editor . It can be used to change the values and add new fields.

works only in cm10 based roms.

Souron29 said:
works only in cm10 based roms.
Click to expand...
Click to collapse
Of course

doesn't CM10 Rom for O1 include this? U posted it separately so thought might be working with CM9 or CM7

Souron29 said:
works only in cm10 based roms.
Click to expand...
Click to collapse
Then what is the point?
Sent from my LG-P500

This tread should be named as:[APP][CM10] messaging app with quick reply, popup notifications
Sent from my LG-P500 using xda premium

It has been taken from the latest nightly.. I dono whether our cm10 build by rashed have this..:laugh:

carrthee89 said:
It has been taken from the latest nightly.. I dono whether our cm10 build by rashed have this..:laugh:
Click to expand...
Click to collapse
I think we have this
Sent from my LG-P500 using Tapatalk 2

Bump.Now the thread is usefull
Sent from my LG-P500 using xda premium

Updated with build.prop optimizations

[GUIDE] Tweak Your Phone Yourself

I've been playing around with a lot of settings, and these particularly made my phone smoother, faster, lag free and much more resposnsive despite the large amount of apps on my phone.
I tried to keep too much technical details out while covering the basic function of each attribute being altered
Tested on : Stock 4.2.2, 4.2.2 based AOSP ROMs, 4.4.x based AOSP ROMs
What do you need :
1. Root Access
2. Busy Box
3. App - Performance Control by @h0rn3t - Original thread (check the download tab for apk) - http://forum.xda-developers.com/showthread.php?t=2444376
4. Root Explorer like ES Explorer - https://play.google.com/store/apps/details?id=com.estrongs.android.pop
5. A little patience
WARNING​I have and am currently using these tweaks on my phone without any issues. So if your phone goes BOOM, tries to take over the world or tries to eat your brain, it's not my fault.​
Performance Control Tweaks​
First of all, take screenshots of your default settings that you are going to alter. So if this doesn't work for you and you want to revert to original settings, you can do that on your own
1. Install the Performance Control application from above (or app with similar features)
NOTE: If you are on any custom ROM like PAC-MAN, the system might have it's own version of performance control (check Settings>Performance Control option). Follow these instructions to install the current one.
Download the latest apk from the above thread, rename it "PerformanceControl.apk"
Mount System. Copy the apk to /system/app and overwrite with the current application. Give it -rw-r--r-- permissions. Then Reboot. Done!
2. In Performance Control :
The first screen is CPU Settings, as shown I'm using interactive Governor with cfq I/O scheduler, after selecting them check the "Set on Boot" option.
NOTE: If you are on a custom kernel and you have SmartassV2 governor with CFQ or SIO I/O scheduler available, use that instead.
Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency and therefore better for performance.
SmartassV2 is a rewrite of interactive governor with major tweaks that boost both battery and scaling of frequencies when performance is needed.
cfq I/O scheduler is basically for fair queing of processes, so it's better for multi-tasking in my opinion.
SIO I/O scheduler is a mix between noop and deadline but works with no reordering or sorting (downside) but still performs well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
The second screen is Memory Settings, please "Aggressive" or "Very Aggressive", screenshot there for reference if you want to set it manually, and check the "Set on Boot" option.
This handles how much memory is to be allocated and freed to and from the applications.
Since 4.4 ROMs we have also been provided with the KSM feature in our kernel.
To enable this, simply click "Enable KSM" then Select "Settings".
Here you alter the pages to be scanned and the sleep time, i.e., how often should they be scanned.
I've found the following values to work well for me without compromising performance,
Pages to scan : 256
Sleep : 1500 ms
Once you have set the values, press "Apply Values", go back and check "Set on Boot"
KSM is a kernel thread that runs in the background and compares pages in memory that have been marked MADV_MERGEABLE by user-space. If two pages are found to be the same, the KSM thread merges them back as a single copy-on-write page of memory. KSM will save memory over time on a running system at the cost of CPU Power which can have an affect on battery life on long running devices.​
For 4.4 ROMs running custom kernel, zRAM.
NOTE: I am explaining this since it's a feature provided to us, but I do not recommend using it unless you keep running low on RAM.
To enable this, simply click on zRAM, configure the value in MBs (18%-25%), 200MB - 256 MB should be optimal. Then Click on Start.
In zRAM unnecessary/un-used storage resources/processes are compressed and then moved to a reserved area in the fixed RAM. This reserved area is referred to as zRAM and acts like a virtual swap area. This virtual space is what you configure in settings.
Advantage of using this feature is that it allows more RAM to stay free for use as well as keep apps and their data in standby mode so they are readily available when needed. This is very beneficial for low RAM devices is why it has been added to the official Kitkat.
However, the down-side of using this feature is that the compression (and de-compression) of data when it is stored away (or brought up for use) uses more CPU power and time. Which would mean, using this feature actively would probably reduce a little battery backup of your phone.​​
The third screen is Advanced Settings, simply click on the SD read ahead option, and select 4096 (or 2048, lower value if you prefer) and check the "Set on Boot" option.
This is the read ahead speed for your internal and external memories. It helps your phone read any and all data faster while you are using it.
Now we have VM Settings, please select each value and set it according to specific value (screenshots available for reference) and "Apply Values" to save the alterations after you are done editing, then check the "Set on Boot" option.
PLEASE NOTE : we are only editing these values :
vm.dirty_background_ratio : 70
vm.dirty_expire_centisecs : 500/1000
vm.dirty_ratio : 90
vm.dirty_writeback_centisecs : 1000/2000
vm.drop_caches : 3
vm.min_free_kbytes : 4096
vm.overcommit_ratio : 100
vm.swappiness : 20
vm.vfs_cache_pressure : 10
Each of settings is a direct tweak on how system and kernel handle the data.
Dirty Ratio and Dirty Background Ratio control how often the kernel writes data to disk (Increasing these might decrease a little lag but might also affect negatively on performance, so skip these if you want to).
Dirty expire and writeback centisecs are used to define when dirty data is old enough to be eligible for writeout by the kernel flusher threads (higher values are supposed to decrease lag and increase battery by flushing data less often, again, might lower the AnTuTu score a little bit, so stick to the lower values if you want).
Drop caches : Writing to this will cause the kernel to drop clean caches, dentries and inodes from memory, causing that memory to become free. This will drop data sectors at each boot and let the kernel start caching as soon as the boot is complete.
1 => To free pagecache
2 => To free dentries and inodes
3 => To free pagecache, dentries and inodes
Minfree kbytes, like the name suggests, it's the minimum Kbs the system VM keeps free for each zone of memory
Overcommit Ratio allows the processes to allocate (but not use) more memory than is actually available
Swappiness is the tendency of a kernel to use physical memory instead of actual RAM, so you might want to keep this value around 20-30.
VFS Cache pressure is the file system cache pressure, so for faster operation we want the kernel to prefer RAM for this, so keep this value at 10-20
​
Scroll to the last Screen, Tools. Here we have a lot of useful options that can be used for personal use, but we are mainly concerned with Optimize DBs option. Simply click Optimize Databases, it will ask you to confirm and take a minute or two to complete the command.
You can re-use this command every two weeks or so, since it's like de-fragmenting your phone's DB.
Use of this is, when a large amount of data is deleted from the database file (while being used by system or app) it leaves behind empty space, or free, unused database pages. This means the database file might be larger than necessary. Running VACUUM to rebuild the database reclaims this space and reduces the size of the database file. In other cases, database file becomes fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file​​
Build.prop Tweaks​
First of all, take a backup of your original build.prop before altering anything. So if this doesn't work for you and you want to revert to original settings, you can do that on your own
How to do it?
1. Install a Root Explorer. I'll be using ES Explorer.
2. Give it root permission to access the Root Explorer mode.
3. Click the Root Explorer to get the following menu, and choose "MOUNT R/W" to mount /system partition in read/write mode.
4. Navigate to /system folder to find build.prop
Now you have two options, either Open and Edit it right there or copy build.prop to your PC and edit it using any utility like Notepad++.
If you use your PC to edit the file, you will have to copy and overwrite the original file with rw--r--r-- permissions (can be found by selecting build.prop in ES and selecting it's properties).
NOTE: /system will go back to Read only mode after each reboot, if you get any error unable to edit/copy build.prop you probably haven't mounted the /system partition as R/W.​
NOTES : Please Read
1. All the tweaks that I am about to list have been available on XDA and several other sites. I am just listing the ones I found useful and have tested myself.
2: I'm using CM's default build.prop as reference. As each ROM's build.prop is different, please check if the developer has already added the tweak before adding it again. If the value or tweak is already present, you may edit it's value if you need to.
3: Add the new tweaks/lines at the end of the build.prop, so that you can easily find or remove them if needed.
4: You don't have to use all the tweaks, just the ones you feel you need.​
The fun stuff
Lines that are not present in stock CM11 and can be added directly, are listed under TO-ADD.
Lines that are present but the values need to be edited are listed under TO-CHANGE
Lines that start with #DONTCOPY are for your information purposes only, and ofcourse don't need to copy them.
'#' - Hash Tags are used as comments in build.prop for sorting purposes, so even if you copy the # line, it will not give you any errors.
TO-CHANGE
#For Dalvik App performance
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
​
TO-ADD
# Camera and Video Tweaks
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.camcorder.videoModes=true
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
# Camera and Video Flash Tweaks
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
# Disable Sending Usage Data
ro.config.nocheckin=1
# Enable sensor sleep
ro.ril.sensor.sleep.control=1
# EGL debug for system performance
debug.egl.hw=1
debug.egl.profiler=1
# Frees More RAM
persist.sys.purgeable_assets=1
# Incoming and Outgoing Call Tweaks
ro.telephony.call_ring.delay=0
ring.delay=0
# Increase Responsiveness
windowsmgr.max_events_per_sec=140
video.accelerate.hw=1
# Increase Performance
debug.performance.tuning=1
# Media Tweaks
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=true
media.stagefright.enable-record=true
# Net Speed Tweaks
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
net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
#DONTCOPY there's no space between any number here, but XDA is displaying it anyway. please remove it while copying into build.prop
# Pointer duration optimize for better scrolling
ro.min_pointer_dur=8
# Power saving
ro.ril.power.collapse=1
pm.sleep_mode=1
#DONTCOPY pm.sleep_mode=1 -> collapse - will totally power off the cpu
#DONTCOPY pm.sleep_mode=2 -> sleep - cpu is still on, but put into low power mode
# Proximity Sensor responsiveness during Calls
ro.lge.proximity.delay=25
mot.proximity.delay=25
# Signal Reception Tweaks
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
# Scrolling Tweak
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
# HW debug and Persist SystemUI HW
debug.sf.hw=1
persist.sys.ui.hw=1
# WiFi to Scan Less Frequently
wifi.supplicant_scan_interval=180​
Let me know if it worked for you
If any member has any other sysctl, VM or build.prop tweak that I might have missed or a setting value that works better for them, please let me know. I would be happy to test and post here

Edit (Change-log in OP)
-----Edited March 10, 2014-----
Reason :
- Modified the Power Collapse tweak
- Reduced max_events_per_sec
- Added build.prop tweaks
Enable sensor sleep
EGL debug for system performance
Improve Voice Quality during Calls
Pointer duration for better scrolling
Signal Reception Tweaks
SystemUI HW
-----Edited : Feb 21, 2014-----
Reason :
- Highlighted VM explanations
- Fixed "wifi.supplicant_scan_interval" in build,prop
- Added explanation and values for zRAM for 4.4.2 kernel
-----Edited : Jan 26, 2014-----
Reason : Added VM property drop_caches (Performance Control)
-----Edited : Jan 26, 2014-----
Reason : Added Scrolling tweak for Build.prop
-----Edited : Jan 21, 2014-----
Reason : Added Warning. (LOL )
-----Edited : Jan 21, 2014-----
Reason :
-Renamed the thread to [GUIDE] Tweak Your Phone Yourself
-Reordered the OP to make room for build.prop tweaks
-Put the explanations in a separate box for Performance Control
-Added info about SmartassV2 and SIO for custom kernel
-Added KSM settings info and config
-Added Dirty expire and writeback centisecs config and info for VMSettings
-Added instructions to alter build.prop file
-Added build.prop tweaks
-----Edited : Jan 1, 2014-----
Reason : Added "Tested on : Stock 4.2.2, 4.2.2 based AOSP ROMs, 4.4.x based AOSP ROMs" to the OP
-----Edited : Nov 9, 2013-----
Reason : Added install instructions for custom ROMs like PACMAN which have their own old PerformanceControl
-----Edited : Nov 06, 2013-----
Reason : Performance Control version used : 2.1.8.
-UI and implementation changes in PerformanceControl and added Optimize DBs in the OP

Great, will try out, been using sd booster.
Sent from my GT-I9082 using xda app-developers app

wiryawang said:
Great, will try out, been using sd booster.
Sent from my GT-I9082 using xda app-developers app
Click to expand...
Click to collapse
Let me know how it works out for you

nice ....

can this be used on stock rom?

felcont12 said:
can this be used on stock rom?
Click to expand...
Click to collapse
Yes, should work the same

This tweak works great, very smooth result.

Testing
Will Test these tweaks for 24 Hours...see how they perform against the other packs I've installed in my device.
Will post results. Will then run Benchmark and Stability test.
Cheers,
Paul

Really Worked For Me.
Thanks A Lot!
---------- Post added at 11:46 PM ---------- Previous post was at 11:45 PM ----------
Really Worked For Me.
Thanks A Lot!

TeSt and replay

Not able to download performance control app
Sent from my GT-I9100 using XDA Premium 4 mobile app

ashutiwari3003 said:
Not able to download performance control app
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It will not work in the XDA mobile app
Try to open the link in any android browser
Sent from my GT-I9082 using xda premium

Seems to be a little quicker. Any issues will report back. Funny thing is my rom already had a version of performance control in it so I wondered why it wouldn't install version 2, it's because I had an older version installed but it worked once I uninstalled the old version
Sent from my SCH-I535 using xda premium

i try this and this is fast and smooth
@ashutiwari3003 this is a direct link for App - Performance Control hit thanks if i help you
http://get.xda-developers.com/dl/6/0/0/PerformanceControl-2.1.4.apk?key=afM0PWLUPDaF6n6Uv5d6GA&ts=1382029384

medozse7s said:
i try this and this is fast and smooth
@ashutiwari3003 this is a direct link for App - Performance Control hit thanks if i help you
http://get.xda-developers.com/dl/6/....apk?key=afM0PWLUPDaF6n6Uv5d6GA&ts=1382029384
Click to expand...
Click to collapse
Link is dead FYI
Sent from my SCH-I535 using xda premium

medozse7s said:
ok the apk in attached
Click to expand...
Click to collapse
Thanks but I've already downloaded it from OP
Sent from my SCH-I535 using xda premium

Thanks, I've been looking for a clear explanation a lot of these terms, specifically the VM settings. As far as kernel-tweaking apps go, I've been using Trickster Mod (on the advice of several devs), but everyone should use what works for them. It covers the SD read-ahead buffer, but not the min-free settings, so I might look around for my own combination of apps.
I'm especially glad to hear anyone's experience with the SD read-ahead buffer. The only thing I had been able to determine was: that my S3 works best in multiples of 1024. But then, there were times that I had lag, & I wasn't sure if it was because of my large buffer, or some other things that I had messed with. It really threw me when I noticed a couple of custom kernels that come with a small default buffer.
Can't wait to try this, but I might not get to it tonight. Sick Children.
Sent from my Nexus 7 using Tapatalk 4

--------------OP Edited--------------
Updated SD read ahead speed to 3072
medozse7s said:
ok the apk in attached
Click to expand...
Click to collapse
Please do not give direct links or apk for the applications used. The reason I used a thread link is to support the dev who made this great app. Anyone who needs it can go the thread and get it, it is working fine I just checked it. Thank you
pbr2 said:
Thanks, I've been looking for a clear explanation a lot of these terms, specifically the VM settings. As far as kernel-tweaking apps go, I've been using Trickster Mod (on the advice of several devs), but everyone should use what works for them. It covers the SD read-ahead buffer, but not the min-free settings, so I might look around for my own combination of apps.
I'm especially glad to hear anyone's experience with the SD read-ahead buffer. The only thing I had been able to determine was: that my S3 works best in multiples of 1024. But then, there were times that I had lag, & I wasn't sure if it was because of my large buffer, or some other things that I had messed with. It really threw me when I noticed a couple of custom kernels that come with a small default buffer.
Can't wait to try this, but I might not get to it tonight. Sick Children.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Hi, VM Settings are basically part of sysctl.config that decide how the linux os and kernel handle the data that is stored on RAM, both physical and virtual and how often to write it. Trickster Mod yes is a great app that gives you a great interface to handle a lot of features, and in there recent version they included sysctl.config as well
Version 2.6.770 (20131005)
- Add Sysctl editor (donate)
Click to expand...
Click to collapse
But the main issue would be to find the specific settings I'm referring to. If you open the editor you will the config file goes on forever. But yes the Trickster Mod can be used to edit them.
Regarding the SD card buffer, the reason I didn't simply use the 4th screen in my post to edit SD read ahead speed is because like most apps, Performance Control and possibly Trickster Mod as well, is that they only edit either sdCard or extSdCard, usually not both. Try installing SD Booster which I mentioned above, when you open the app it displays current read ahead speed of both of your storage, and probably only one of them would be the one you have set through Trickster. You can edit and monitor both through this app and even set different read ahead for each.
Lastly, yes 1024 multiples are used to be set as read ahead as it covers one entire kB/MB of data. The most common altered value is 2048, and honestly I've been experimenting and the difference after 2048 (3072/4096) isn't that much except that 3072 seems to have a little boost
Hope your children feel better today
(Benchmark of my 16GB class 10 card using Rom ToolBox Pro)

I can't download it
Sent from my GT-I9082 using XDA Premium 4 mobile app

[GUIDE]Build.prop explained [Updated 11/30]

Hello fellow xda members. Today i present you my little tutorial about the build.prop file. I have taken the reference build.prop from k2wl's aokp rom.
Please make a nandroid backup in case something goes wrong.
I´m not responsible for any damages to your phone.
CREDITS
-Chris_84
-k2wl (for refrence build.prop)
-xda-developers
Click to expand...
Click to collapse
What is the build.prop ?
TheManii: Build.prop is what holds the majority of the runtime flags that are used when android boots, think of it as being
similar to config.sys on dos or environment variables in various OS's. It only holds variables, it cant run any scripts on it's own. Whatever is placed inside depends on android itself to pay attention to the flag and actually use it.
In easier words it is a file in your android system that maintains certain parameters on your phone in order for your phone to run.
These properties are device specific and can change depending upon the various specifications of the device and also includes some system properties.
Click to expand...
Click to collapse
Where is build.prop located?
You will find the build.prop file in root/system/build.prop. You can open it with a root explorer/es explorer which has a built in text editor.
Click to expand...
Click to collapse
How to edit build.prop?
1.With a root explorer or ES file exploreror.
copy /system/build.prop to the root of the internal sdcard (/mnt/sdcard).
2.Edit it using a text editor (ES and root explorer have an inbuilt text editor) or on computer using notepad++.
3.Be careful as some of the parameters already exist. Just change their values.
4. Overwrite /system/build.prop with the edited file.
5. Make sure that the permissions are still rw-r--r--:
6. Reboot into recovery
wipe cache and dalvik cache.
Make sure to edit existing line if present
Click to expand...
Click to collapse
LETS BEGIN
This mentions that the build prop is built by build info shell script during the compilation of the ROM.
# begin build properties
# autogenerated by buildinfo.sh
Version name of 4.2.2(jellybean)
ro.build.id=JDQ39
Current rom version on phone
ro.build.display.id=aokp_i9082-userdebug 4.2.2 JDQ39 eng.k2wl.20130827.005402
Your current modem version
ro.build.version.incremental= eng.k2wl.20130827.005402
Current sdk version of framework plus codename
ro.build.version.sdk=17
ro.build.version.codename=REL
Current android version on phone
ro.build.version.release=4.2.2
This is the time and date of when the Kernel was built.
ro.build.date=Aug 27 00:54:58 IST 2013
Other Kernal Details
ro.build.date.utc=1377545098
ro.build.type=userdebug
ro.build.user=android-build
ro.build.host=k2wl-HP-EliteBook-8440p
Test keys means that the ROM is not an official version of the ROM. Release keys are for official releases.
ro.build.tags=release-keys
Model Number
ro.product.model=GT-I9082
Phone Manufacturer
ro.product.brand=samsung
This name is the codename of the
device.
For example-
HTC Explorer - pico,
Nexus 7 - grouper
Nexus 4 - mako
Galaxy Ace - cooper
Grand - baffin
ro.product.name=baffin
System Images
It is the first instruction set (CPU + ABI
convention type) of the code. Ours is an arm type arch cpu and abi version 7a )
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
Default Country settings.
Language of software
Region of software
ro.product.locale.language=en
ro.product.locale.region=GB
If you not able to connect to your wifi, you can try to set here the same number of channels as your router currently got. For example: Your router is set to 12 channels you can paste the same number in here.
ro.wifi.channels=
Here you can set the standard media sounds for each notification. But the file should be present in system/media/...
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=A_toy_watch.ogg
Your phone is still usable, even if sim card is not inserted.
keyguard.no_require_sim=true
Default format of date
ro.com.android.dateformat=mm-dd-yyyy
Your bluetooth name
net.bt.name=Samsung Galaxy Grand Duos
Disable Boot Animation
debug.sf.nobootanimation=1
Your battery capacity (in MHz)
ro.semc.batt.capacity=1200
The setup wizard when you flash a custom rom and it asks your language, gmail id etc
ro.setupwizard.mode=DISABLED (or ENABLED or OPTIONAL)
Here you can set the default density (in pixel per inch)(default is 240)
ro.sf.lcd_density=240
Minimum brightness of your screen
ro.lcd_min_brightness=40
Your default brightness
ro.lcd_brightness=160
Basically you control the class-loading and dalvik-vm there. Here you can set different values.
v=a means verify all,
v=f means verify full,
o=v means optimize verify,
v=n will turn off bytecode verification
u=n means do not optimize for unprocessor
m=y means register maps yes
dalvik.vm.dexopt-flags=m=y
Enables multi touch
ro.product.multi_touch_enabled=true
Max number of multi touches
ro.product.max_num_touch=2
Disable sending usage data
ro.config.nocheckin=1
Here you can set the delay of time your phone starts to ring when you recieve a call.
ro.telephony.call_ring.delay=0 (0 means disabled)
Disable waking up of phone by volume buttons ro.config.hwfeature_wakeupkey=0
Off the proximity quickly after call
mot.proximity.delay=25
ro.lge.proximity.delay=25
This property is supposed to keep the launcher in memory under the assumption that it would somehow make it faster
ro.HOME_APP_ADJ=1
Allows your phone to use an ext-4 file system
ro.ext4fs=1
Disables debug icon on status bar
persist.adb.notify=0
Key lights stay on while screen is on
ro.mot.buttonlight.timeout=0
Disable notification sound when SD is inserted
persist.service.mount.playsnd=0
Disables location of device. Also delete /system/app/networklocation.apk and /system/framework/com.android.location.provider
.jar
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
To enable the timeout of hard key lights to stay on when screen is on and lights off when screen is off
ro.mot.buttonlight.timeout=0
To enable the menu button too unlock the phone
Not sure if it works
ro.config.hw_menu_unlockscreen=true
Proximity sensor debounce time
mot.proximity.delay=450
mot.proximity.distance=60
Default data roaming is enabled
ro.com.android.dataroaming=true
Judging from its name I assume people think it disables some kind of logging mechanism. But 'no'.The “ulog” referred to in this property is an HTC-specific service that HTC calls the User Behavior Logging Service. This service is centered around tracking user behavior related to the HTC Sense launcher. The HTC ULog tracks some basic things like the number of ANRs and/or crashes, but it also potentially tacks things like your wallpaper selection, your installed apps and your locatio (HTC specific)
profiler.force_disable_ulog=1
Unlike the latter, this one actually does turn off sending device crash log data to HTC. This will make your device run faster/smoother/better (HTC specific)
profiler.force_disable_err_rpt=1
# Increase Quality Of MediaStreaming
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
# Net Speed Tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,
16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163
84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163
84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163
84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163
84,256960
# Google DNS Tweak
net.wlan0.dns1=8.8.8.8
net.wlan0.dns2=8.8.4.4
net.pdp0.dns1=8.8.8.8
net.pdp0.dns2=8.8.4.4
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.eth0.dns1=8.8.8.8
net.eth0.dns2=8.8.4.4
net.gprs.dns1=8.8.8.8
net.gprs.dns2=8.8.4.4
# Touch Responsiveness
Scrolling Responsiveness
Faster Scrolling
debug.performance.tuning=1
video.accelerate.hw=1
windowsmgr.max_events_per_sec=500
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
# Media Tweaks
Increase photo and video quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.jpeg.quality=100
Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
Better Flashlight intensity & camera-flash quality
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=65
ro.media.capture.flashIntensity=70
# Signal Tweaks
Defines weither to use [0=UMTS] [1=HSDPA only] [2=HSDPA & HSUPA] [5=No significant information has been found but it makes the switch between WiFi and HSxPA nearly instantaneous (note works like "2" but better)]
Here you can improve your Data speed if your provider supports it. Set this to 0 if you want lower speeds, and up to 2 for faster speeds.
ro.ril.hsxpa=2
Defines what class speeds to use with EDGE.
Class 10 will significantly save battery, unless you use EDGE/GPRS instead of 3G)
12 is the default value for most modern phones.
Setting this value to 12 can improve the data speed significant on lower connections.
ro.ril.gprsclass=10
0=off
1=Default
no change when turned off. In some phones stability is increased when turned off.
ro.ril.hep=1
Enable "dual transfer mode" on EDGE networks. Requires different GPRS class settings. Only set this to 1 if your network allows simultaneous transfer of Circuit switched (CS) voice and Packet switched (PS) data over the same radio channel (ARFCN). Turning this off on some carriers, including Optus (AU) and AT&T increases upload speeds.
ro.ril.enable.dtm=1
Enable increased ciphering on
HSDPA/HSUPA, for increased security, but decrease in performance.
ro.ril.enable.a53=1
Adds the 3G prefix e.g. Optus 3G, etc. Purely cosmetic
ro.ril.enable.3g.prefix=1
Other signal tweaks
ro.ril.hsdpa.category=10
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
# Dalvik VM tweaks
This controls the smallest amount of memory given to a single application.
dalvik.vm.heapstartsize=5m
This value represents the maximum allowed amount of memory that the Dalvik Virtual Machine can allocate to the applications. A higher value means faster apps but more RAM consumption.
dalvik.vm.heapgrowthlimit=48m
The dalvik.vm.heapsize property defines an absolute maximum for the heap size for an application
dalvik.vm.heapsize=128m
This point stands for "Debug SurfaceFlinger Hardware" or GPU hardware acceleration
debug.sf.hw=1
Explained Earlier(change to this to load apps faster and free more ram)
dalvik.vm.dexopt-flags=m=v,o=y or m=y
This property can set the execution mode of the Dalvik VM. The VM can run in three modes: fast, portable, and JIT. It is possible to compile Android without JIT support, but the default is to include it. In general, JIT is the execution mode you are going to want on your device. This is why you will see most build.prop files setting this property to “int:jit”.
In ICS or lower , there is no need to define this setting in your build.prop
dalvik.vm.execution-mode=int:jit or int:fast
Others
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapmaxfree=2m
dalvik.vm.lockprof.threshold=500
# Improve battery
improve battery under no signal
ro.mot.eri.losalert.delay=1000
Bluetooth OPP low speed to save power
debug.bt.lowspeed=true
Wifi to scan less frequently
wifi.supplicant_scan_interval=240
System can free more Ram when needed
persist.sys.purgeable_assets=1
This property purports to significantly increase your battery life by putting signaling your device to use a better power mode when your phone is idle. Recommended values range from 0, 1, 4 with the most common be 1
pm.sleep_mode=1
To save battery turn off wifi, internet, bluetooth, gps, lower the brightness at night, kill all apps running in background, clear ram, underclock if kernal supports and also switch off the animations settings>display>no animation.

Reserved
Sent from my GT-I9082 using XDA Premium 4 mobile app

that is awesome work

informative posts. :good:

medozse7s said:
that is awesome work
Click to expand...
Click to collapse
Dwama said:
informative posts. :good:
Click to expand...
Click to collapse
Thank you very much! It's a honor to get such a good feedback from ual!
Sent from my GT-I9082 using XDA Premium 4 mobile app

Digitizer problem
Hello,
any idea if there is a property which would control the digitizer orientation? My digitizer got mixed up after flashing a new ROM version and the manufacturer`s stock is not the same stock as used to be inside the tablet.
ATM my digitizer is mirrored top-down in landscape and there might be a build.prop to compensate. Does such setting exist?
Joe

awesome NOOB guide for the build.prop! had a doubt, can i edit the build.prop and change the wallpaper?
when the rom is loaded i want the default wallpaper to be like the stock rom! is it possible?
if so then which are the lines i need to edit! pls inform!
WBR
ReyTech.

Awesome Awesome Guide....Very informative Post...Keep up the good work...
Sent from my GT-I9082 using XDA Premium 4 mobile app

Awesome work... Hats off..... Thank you...
Sent from my GT-I9082 using XDA Premium 4 mobile app

joeprusa said:
Hello,
any idea if there is a property which would control the digitizer orientation? My digitizer got mixed up after flashing a new ROM version and the manufacturer`s stock is not the same stock as used to be inside the tablet.
ATM my digitizer is mirrored top-down in landscape and there might be a build.prop to compensate. Does such setting exist?
Joe
Click to expand...
Click to collapse
Two methods to do that.
1. By editing your build.prop
ro.sf.hwrotation=xx in /system/build.prop should do the job.
xx = 00 (portrait mode - default)
xx = 90 (landscape mode)
xx = 180 (full tilted)
2. What you need to do is edit yourAndroidManifest.xml*file and specify the orientation for your activity, as well as handle orientation changes yourself:
Then your activity will always run in a landscape mode regardless of the device orientation.
However note that this will affect all applications running on the device.
ReyTech said:
awesome NOOB guide for the build.prop! had a doubt, can i edit the build.prop and change the wallpaper?
when the rom is loaded i want the default wallpa per to be like the stock rom! is it possible?
if so then which are the lines i need to edit! pls inform!
WBR
ReyTech.
Click to expand...
Click to collapse
Decompile framework-res.apk then go to
res/drawable-sw600dp-nodpi/default_wallpaper.jpg
Replace the image that you want with resolution of 1440x1080.
Recompile and push the framework-res.apk to system/framework/here.
Hope it helps.

Amazing!!!!!!!!!!!!!!!!!!
Wowwwwwwwwwww..... Great Work Mate...........
Thumbs Up :good:

Thanks man ......helped a lot to understand the inside of android.....
Sent from my GT-I9082 using Tapatalk

GREAT explanation !! Is all of the information still relevant to KitKat ? I just want to be sure.

Can anyone tell me what line is this for?
" persist.sys.recovery_update=false "

thankss alott

Any way to enable the notification led from the build

Sounds Great, Thanks for sharing.

Great topic

losing signal
hi any one has/have an idea for fixing my problem to my kata i3s mt6582 kitkat 4.4.2 when in my house i have a signal i can use data connection surfing etc,
but when it come to my work or when i go to my work my signal are losing and its totally drop the signal,
any idea on how to fix lossing of signal
:crying::crying::crying::crying::crying::crying::crying::crying:

persist.sys.recovery_update=false
subhad43 said:
Can anyone tell me what line is this for?
" persist.sys.recovery_update=false "
Click to expand...
Click to collapse
This basically means that when the system will update/auto update over the air, or OTA, or Delta updates, or for that sake even when you manually flash the new update, the system will not replace your custom recovery.
You can view this under the Developer Option, where the option "Update Recovery" or "Update Cyanogen Recovery" is turned off by default.
This is to help with custom recovery , as inbuilt recovery is limited and does not have all the customisations.

[UPDATE 4.0] Xiaomi.EU Redmi Note 4 ROM Multi Tasking Fix and Battery Improvements

DISCLAIMER: DO ALL OF THIS AT YOUR OWN RISK. IT WORKED FOR ME AND I CAN'T GUARANTEE THAT IT'LL WORK FOR YOU ETC, SO DO NECESSARY THINGS LIKE TWRP BACKUPS OR SOMETHING LOL GOOD LUCK
USAGE SCREENSHOTS/STATS:
https://forum.xda-developers.com/showpost.php?p=70915389&postcount=37
https://forum.xda-developers.com/showpost.php?p=70915456&postcount=39
https://forum.xda-developers.com/showpost.php?p=70915425&postcount=38
UPDATE 3.0 (A) RAM FIX MULTITASKING
SIMPLER METHOD (ROOT)
ZRAM increase and fixes
1. Using a file manager, go to system/etc/ and rename mcd_default.conf to mcd_default.conf.bak
2. Download this file and place it in system/etc
3. Reboot
4. Go to developer options and go to memory optimizations and set to HIGH
5. Reboot.
6. Install kernel audiotor and go to LMK and change the values to medium. Remember to set on boot.
7. Reboot.
UPDATE 3.0 (B) BATTERY LIFE IMPROVEMENT
SIMPLER METHOD (ROOT)
Changed the values to less aggressive ones. Minimal battery life improvement but it it better than nothing in my opinion.
1. Go to system/etc and rename perfservscntbl.txt to perfservscntbl.txt.bak
2. Download this and place in system/etc
3. Reboot
UPDATE 3.0 (C) PERFORMANCE IMPROVEMENT
SIMPLER METHOD (ROOT)
These are some cherrypicks from android 7.1.1
1. Make sure you are rooted
2. Go to su/su.d and place this file in that folder
3. Give the file 0755 permission as shown below
X X X
X -- X
X -- X
4. Reboot.
As per usual all of these require root and please do backups in case anything goes wrong. I suggest using FX file manager to do these tweaks.
USAGE SCREENSHOTS/STATS:
https://forum.xda-developers.com/showpost.php?p=70915389&postcount=37
https://forum.xda-developers.com/showpost.php?p=70915456&postcount=39
https://forum.xda-developers.com/showpost.php?p=70915425&postcount=38
OLD METHOD BELOW
FOR MULTITASKING, THERE ARE 2 PARTS; PART (A) TO ACTUALLY FIX ZRAM AND PART (B) TO ACTUALLY ENABLE ZRAM. XIAOMI FOR SOME REASON THOUGHT THAT OUR DEVICE DOESNT NEED ZRAM (IT NEEDS IT LOL)
PART 1 (A)- MULTITASKING
The Redmi Note 4, in my opinion, suffers a lot of RAM management issues. The symptoms are as follow;
- Constant reloading of app like instagram, chrome, facebook, and others when switching apps
- Constant reloading of apps whenever you switch to a system app like phone, camera, messaging (background apps get killed when you launch system apps)
Things I have I tried to remedy the issue/problem
- Lock app
- Change memory optimization settings in developer options
NONE OF THEM WORKED. I got so frustrated because this device has like 3GB of RAM which should eliminate problems concerning apps getting killed.
So I went out and did my own research and found out that MIUI controls ram management via a service called 'mcd' and this service depends on a file called 'mcd_default.conf' in system/etc. Naturally what I did was tinker around with the contents of the file and edited it using trial and error. Each time I tested, I would launch 10-12 apps that included Chrome, Spotify, Instagram, Twitter, Color-Note, Phone, Messaging, Gallery, Google Photos and others. (YES 10 TO 12 APPS)
Yes, ladies and gentleman. 3GB of ram should be able to handle all those apps without reloading every single one of them.
Finally, after tinkering around with some values I think I cracked the code/solution to the problem by editing some lines. The lines I edited affect how zram works on our device and I think I fixed it. The file I edited is attached below.
HOW TO USE THE FILE
I TESTED THIS ON THE LATEST XIAOMI.EU ROM which can be found here. TEST IT OUT ON OTHER ROMS AT YOUR OWN RISK. FU** STOCK MIUI ROM.
XIAOMI.EU ROM LINK
1. Make sure you are rooted and you have the latest busybox installed (its on the playstore)
2. Download the file attached HERE IS THE FILE
3. Browse to system/etc using your root file manager of choice (I prefer fx file manager)
4. Backup the existing mcd_default.conf bye renaming it to mcd_default.conf.bak
5. Place the file I attached in system/etc
6. Reboot
7. Go to developer settings and set memory optimization to LOW and reboot
8. Test out multitasking for yourself
PART 1 (B)- MULTITASKING
1. Install Kernel audiotor
2. Open, give it root permission
3. Swipe from left and go to init.d
4. Press the + button and enter name ZRAM
5. Enter these values
echo 1073741824 > /sys/block/zram0/disksize
/system/xbin/mkswap /dev/block/zram0
/system/xbin/swapon /dev/block/zram0
echo 100 (you can choose between 100 to 0. higher number better zram usage) > /proc/sys/vm/swappiness
6. Save and enable set on boot
7. Reboot and test out multitasking
8. Open Kernel Audiotor and change LMK values to medium. Set on boot and reboot.
Important things to know
- It's normal for background apps to close when you use camera because the camera app uses a lot of RAM and resources to process images ESPECIALLY if you use burst mode (hold shutter button)
SO FAR MY EXPERIENCE
- Improved multitasking
- No other problem like fingerprint sensor not working bla bla bla
PART 2 - BATTERY LIFE IMPROVEMENTS
I noticed that the helio x20 is quite the power hungry chip so I dug around XDA MIUI devices forums for other devices and found out that Xiaomi MIUI roms use a service called 'perfservice' to control the CPU and can sometime be a hit and miss, so I did something;
DISABLE PERFSERVICE and MY BATTERY LIFE HAS IMPROVED DRAMATICALLY. IM TALKING REDMI NOTE 3 SNAPDRAGON LEVELS. 7 HOURS SCREEN ON TIME, 20 HOURS STANDBY.
What happens when perfservice is disabled is the cpu is controlled by MTK's cpu manager (not sure what it is called) and uses the stock interactive governer (which is good).
HOW TO DISABLE/IMPROVE BATTERY
1. Make sure you are rooted
2. use your root file explorer of choice (I prefer fx file manager)
3. go to /system and backup build.prop by copying and pasting it somewhere else
4. edit build.prop and find the line ro.mtk_perfservice_support=1 and change it to ro.mtk_perfservice_support=0 and save file
5. go to /system/etC and find a file named perfservapplist.txt and rename it to perfservapplist.txt.bak
6. go to /system/etc and find a file named perfservscntbl.txt and rename it to perfservscntbl.txt.bak
7. Reboot and test out the result yourself
I hope this helps any of you in any way.
I now LOVE my phone but it's a pity that Xiaomi doesn't want to fix problems like these. Maybe they don't consider these problems as actual problems. We'll never know tbh.
SPECIAL THANKS TO THIS THREAD AND ITS OWNER
http://forum.xda-developers.com/redmi-note-2/development/b-skinny-pro-t3347906
BECAUSE IT TAUGHT ME A LOT ABOUT HOW XIAOMI ROM WORKS TO MANAGE OUR RAM AND CPU

Thanks for this, really great work. Definitely interested in trying the battery improvement as it had gotten better since I used the 4G fix, but still could be a bit better. Is there any way these could be made into flashable zips? I have TWRP but not using root. Thanks again.
Sent from my Redmi Note 4 using Tapatalk

gsmyth said:
Thanks for this, really great work. Definitely interested in trying the battery improvement as it had gotten better since I used the 4G fix, but still could be a bit better. Is there any way these could be made into flashable zips? I have TWRP but not using root. Thanks again.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Twrp has a file manager within the recovery. You can rename, move, and, copy files with it. You can try it out

asusm930 said:
Twrp has a file manager within the recovery. You can rename, move, and, copy files with it. You can try it out
Click to expand...
Click to collapse
Wow didn't know that! Must take a look.
Sent from my Redmi Note 4 using Tapatalk

gsmyth said:
Wow didn't know that! Must take a look.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Its under 'advanced' but before that mount system using the 'mount' option
As for editing the build.prop file, copy it to your phone and then edit the copy, after that replace the original build.prop with the edited one using twrp's file manager

asusm930 said:
Its under 'advanced' but before that mount system using the 'mount' option
Click to expand...
Click to collapse
Ah thanks, forgot to mount and couldn't see the build prop file, will try again later.
Sent from my Redmi Note 4 using Tapatalk

Maybe we can make a flashable zip with AnyKernel 2 like CosmicDan does here http://forum.xda-developers.com/redmi-note-4/development/tweaks-cosmictweaks-v2016-11-26-t3507291

prismk said:
Maybe we can make a flashable zip with AnyKernel 2 like CosmicDan does here http://forum.xda-developers.com/redmi-note-4/development/tweaks-cosmictweaks-v2016-11-26-t3507291
Click to expand...
Click to collapse
I prefer having people doing it manually so that people know what they're doing and know what files to backup and so on

asusm930 said:
DISCLAIMER: DO ALL OF THIS AT YOUR OWN RISK. IT WORKED FOR ME AND I CAN'T GUARANTEE THAT IT'LL WORK FOR YOU ETC, SO DO NECESSARY THINGS LIKE TWRP BACKUPS OR SOMETHING LOL GOOD LUCK
PART 1 (A)- MULTITASKING
The Redmi Note 4, in my opinion, suffers a lot of RAM management issues. The symptoms are as follow;
- Constant reloading of app like instagram, chrome, facebook, and others when switching apps
- Constant reloading of apps whenever you switch to a system app like phone, camera, messaging (background apps get killed when you launch system apps)
Things I have I tried to remedy the issue/problem
- Lock app
- Change memory optimization settings in developer options
NONE OF THEM WORKED. I got so frustrated because this device has like 3GB of RAM which should eliminate problems concerning apps getting killed.
So I went out and did my own research and found out that MIUI controls ram management via a service called 'mcd' and this service depends on a file called 'mcd_default.conf' in system/etc. Naturally what I did was tinker around with the contents of the file and edited it using trial and error. Each time I tested, I would launch 10-12 apps that included Chrome, Spotify, Instagram, Twitter, Color-Note, Phone, Messaging, Gallery, Google Photos and others. (YES 10 TO 12 APPS)
Yes, ladies and gentleman. 3GB of ram should be able to handle all those apps without reloading every single one of them.
Finally, after tinkering around with some values I think I cracked the code/solution to the problem by editing some lines. The lines I edited affect how zram works on our device and I think I fixed it. The file I edited is attached below.
HOW TO USE THE FILE
I TESTED THIS ON THE LATEST XIAOMI.EU ROM which can be found here. TEST IT OUT ON OTHER ROMS AT YOUR OWN RISK. FU** STOCK MIUI ROM.
XIAOMI.EU ROM LINK
1. Make sure you are rooted
2. Download the file attached HERE IS THE FILE
3. Browse to system/etc using your root file manager of choice (I prefer fx file manager)
4. Backup the existing mcd_default.conf bye renaming it to mcd_default.conf.bak
5. Place the file I attached in system/etc
6. Reboot
7. Go to developer settings and set memory optimization to LOW and reboot
8. Test out multitasking for yourself
PART 1 (B)- MULTITASKING
1. Install Kernel audiotor
2. Open, give it root permission
3. Swipe from left and go to init.d
4. Press the + button and enter name ZRAM
5. Enter these values
echo 1073741824 > /sys/block/zram0/disksize
/system/xbin/mkswap /dev/block/zram0
/system/xbin/swapon /dev/block/zram0
echo 0 > /proc/sys/vm/swappiness
6. Save and enable set on boot
7. Reboot and test out multitasking
Important things to know
- It's normal for background apps to close when you use camera because the camera app uses a lot of RAM and resources to process images ESPECIALLY if you use burst mode (hold shutter button)
SO FAR MY EXPERIENCE
- Improved multitasking
- No other problem like fingerprint sensor not working bla bla bla
PART 2 - BATTERY LIFE IMPROVEMENTS
I noticed that the helio x20 is quite the power hungry chip so I dug around XDA MIUI devices forums for other devices and found out that Xiaomi MIUI roms use a service called 'perfservice' to control the CPU and can sometime be a hit and miss, so I did something;
DISABLE PERFSERVICE and MY BATTERY LIFE HAS IMPROVED DRAMATICALLY. IM TALKING REDMI NOTE 3 SNAPDRAGON LEVELS. 7 HOURS SCREEN ON TIME, 20 HOURS STANDBY.
What happens when perfservice is disabled is the cpu is controlled by MTK's cpu manager (not sure what it is called) and uses the stock interactive governer (which is good).
HOW TO DISABLE/IMPROVE BATTERY
1. Make sure you are rooted
2. use your root file explorer of choice (I prefer fx file manager)
3. go to /system and backup build.prop by copying and pasting it somewhere else
4. edit build.prop and find the line ro.mtk_perfservice_support=1 and change it to ro.mtk_perfservice_support=0 and save file
5. go to /system/etC and find a file named perfservapplist.txt and rename it to perfservapplist.txt.bak
6. go to /system/etc and find a file named perfservscntbl.txt and rename it to perfservscntbl.txt.bak
7. Reboot and test out the result yourself
I hope this helps any of you in any way.
I now LOVE my phone but it's a pity that Xiaomi doesn't want to fix problems like these. Maybe they don't consider these problems as actual problems. We'll never know tbh.
SPECIAL THANKS TO THIS THREAD AND ITS OWNER
http://forum.xda-developers.com/redmi-note-2/development/b-skinny-pro-t3347906
BECAUSE IT TAUGHT ME A LOT ABOUT HOW XIAOMI ROM WORKS TO MANAGE OUR RAM AND CPU
Click to expand...
Click to collapse
Really interesting post. I've been frustrated with processes getting killed for no apparent reason but I'm a little dubious about the mods. Are you able to post a before and after video or something showing the improvements?
Also, how does disabling perfservice affect performance?

spr33 said:
Really interesting post. I've been frustrated with processes getting killed for no apparent reason but I'm a little dubious about the mods. Are you able to post a before and after video or something showing the improvements?
Also, how does disabling perfservice affect performance?
Click to expand...
Click to collapse
I can't post videos but I can personally that multitasking is way better now.
disabling perfservice does not affect performance at all. Its still snappy as ever

asusm930 said:
I can't post videos but I can personally that multitasking is way better now.
disabling perfservice does not affect performance at all. Its still snappy as ever
Click to expand...
Click to collapse
I don't know why but I got the standby problem when WIFI is ON (I tried everything, turn off location, scanning). Here is what I have tested CAREFULLY:
1> WIFI ON , SCREEN OFF
Drain 1.5-2.5%/ hour
2> WIFI OFF, MOBILE DATA ON, SCREEN OFF
Drain 1%/ 90 minutes or even a bit more
3> WIFI OFF, MOBILE DATA OFF, SCREEN OFF
Drain 1%/ 3-4 hours or even a bit more
It's really weird when WIFI drains MUCH MORE battery than mobile data, even the deep sleep rate is still 89% - 90% when WIFI is ON.
Do you have any idea how to fix this?

phamhuytung192 said:
I don't know why but I got the standby problem when WIFI is ON (I tried everything, turn off location, scanning). Here is what I have tested CAREFULLY:
1> WIFI ON , SCREEN OFF
Drain 1.5-2.5%/ hour
2> WIFI OFF, MOBILE DATA ON, SCREEN OFF
Drain 1%/ 90 minutes or even a bit more
3> WIFI OFF, MOBILE DATA OFF, SCREEN OFF
Drain 1%/ 3-4 hours or even a bit more
It's really weird when WIFI drains MUCH MORE battery than mobile data, even the deep sleep rate is still 89% - 90% when WIFI is ON.
Do you have any idea how to fix this?
Click to expand...
Click to collapse
my last bet is going to Additional settings > Privacy > Location > Google Location History > and turn it off for every account
I also have sync on WLAN only too in sync settings if that helps

asusm930 said:
my last bet is going to Additional settings > Privacy > Location > Google Location History > and turn it off for every account
I also have sync on WLAN only too in sync settings if that helps
Click to expand...
Click to collapse
I already tried all of this, nothing change , I think the problem is because of Mediatek wifi chipset. Do you have the same problem?

phamhuytung192 said:
I already tried all of this, nothing change , I think the problem is because of Mediatek wifi chipset. Do you have the same problem?
Click to expand...
Click to collapse
I dont think so. I lose like 2% like after 6 hours. I do have both wifi and data turned on though (by turned on i mean the toggles are switched on but in actuality when wifi is on, android turns off data even though the toggle shows that its on up until wifi signal is gone)

asusm930 said:
I dont think so. I lose like 2% like after 6 hours. I do have both wifi and data turned on though (by turned on i mean the toggles are switched on but in actuality when wifi is on, android turns off data even though the toggle shows that its on up until wifi signal is gone)
Click to expand...
Click to collapse
Do you have any apps in background? I usually have Messenger + Chrome in background with 2 SIM. How many SIM are you using and in which sim slot (If only 1 sim)?

phamhuytung192 said:
Do you have any apps in background? I usually have Messenger + Chrome in background with 2 SIM. How many SIM are you using and in which sim slot (If only 1 sim)?
Click to expand...
Click to collapse
I have 1 sim (in slot 1) and an SDcard.
Try installing Link2SD and disable "Battery Saver" and MiCloud, MiCloudBackup, Cleaner, Metok, LocationEM2, MiDrive, MiDrop, Music, Search, Video, Wallpaper Carousel AND Browser. These are the apps I have disabled.

asusm930 said:
I have 1 sim (in slot 1) and an SDcard.
Try installing Link2SD and disable "Battery Saver" and MiCloud, MiCloudBackup, Cleaner, Metok, LocationEM2, MiDrive, MiDrop, Music, Search, Video, Wallpaper Carousel AND Browser. These are the apps I have disabled.
Click to expand...
Click to collapse
Yes I tried 1 SIM card with an SD Card before, the standby on WIFI was much better, really don't understand why. Can you tried to test WIFI standby with 2 SIM online?

phamhuytung192 said:
Yes I tried 1 SIM card with an SD Card before, the standby on WIFI was much better, really don't understand why. Can you tried to test WIFI standby with 2 SIM online?
Click to expand...
Click to collapse
I think I read somewhere that someone else was having this problem. It could be the culprit (having 2 sims).
Unfortunately, I don't have another sim that i can use to confirm this bug, but I'm very sure that I've read other people mentioning this problem too (2 sims draining battery)

asusm930 said:
I think I read somewhere that someone else was having this problem. It could be the culprit (having 2 sims).
Unfortunately, I don't have another sim that i can use to confirm this bug, but I'm very sure that I've read other people mentioning this problem too (2 sims draining battery)
Click to expand...
Click to collapse
I will try again, someone said that it is because of the wifi router, I tried this afternoon to use my laptop as WIFI hotspot and also DISABLE all the apps like you said, it drains only 2-3% / 6 hours .

asusm930 said:
I think I read somewhere that someone else was having this problem. It could be the culprit (having 2 sims).
Unfortunately, I don't have another sim that i can use to confirm this bug, but I'm very sure that I've read other people mentioning this problem too (2 sims draining battery)
Click to expand...
Click to collapse
I tried yesterday and it is because of the WIFI Router, also in WIFI Advanced Setting I changed the option "Keep WIFI on during sleep" to "Never", the battery is really much better and WIFI is even not turn off during sleep, I can still receive calls from Facebook as well as messages. I think this is definitely an error.