Related
I have an ATT atrix on the Rogers network in canada. I have abysmal up/down-link speed. I was skimming over the build.prop HSUPA thread and i decided to do some research about the build.prop file and made a few changes.
First off, the connection speed tweak:
Code:
## Rogers Speed Tweak
#
ro.ril.hsxpa=3
ro.ril.hsdpa.category=8
ro.ril hsupa.category=5
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.gprsclass=32
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
## End Tweak
#
With this I experianced a much higher download speed and a more stable upload speed. The results were as follows:
Before:
Server 1:815 kbps down 354 kbps up
Server 2:618 kbps down 259 kbps up
Server 3:701 kbps down 301 kbps up
After:
Server 1:1224 kbps down 331 kbps up
Server 2:1358 kbps down 320 kbps up
Server 3:1206 kbps down 390 kbps up
Caveat! This is for an ATT Atrix on the rogers network so YMMV
Upon my research i found a few more parameters i decided to change. I changed the following:
Code:
#proximit sensor screen off delay
mot.proximity.delay=150
This changed the delay in the sensor when you are in a call and you move the phone away from your face. I found this delay to be WAY to long. The orginal value was 450
Code:
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=275
****NOTE: THIS KILLS THE DIALER...i am going to figure out why, best keep it at the stock 240****
I changed this to 275 as thats what it said. It filled in the icons better on my homescreen and made the widgets fill the screen more. This was a personal preference for me.
Code:
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 90
Pretty self explanitory. I am a wifi always on kind of guy and i am hoping this saves some battery. The original was 30 i believe.
I am going to do some more testing to confirm the speed increase throughout the day and also see how the battery life is effected. It may not be much, but so far the speed change has been well worth it!
STEPS
I did it the following way:
Here were my steps:
1. adb pull /system/build.prop /yourdirectoryhere
2. Open build.prop with notepad++ and make changes
3. adb push /yourdirectoryhere/build.prop /mnt/sdcard
4. Used Super Manager to navigate to the /system folder and rename the old build.prop to buildstock.prop then copied the new build.prop into the folder from /mnt/sdcard .
5. adb reboot
As GibMcFragger mentioned, you can do this all through your phone via root explorer and it will save the original as .bak as well.
Did you edit the build.prop file on the fly or had to modify it before reflash ?
As for the density of the screen, did it affect the layout in landscape as opposed to portrait and was there anything out of place on the home screens ?
Woh! Thanks dude. I just edited my lcd density to 275 and it looks much better! My custom dock fits now too. It was a little short at the default dpi of 240.
I just edited my build.prop in Root Explorer and when you save it, it automatically saves the original as a .bak
Sent from my soon-to-be-hacked Bell Atrix.
Would be awesome if the same speed settings worked with At&t though I know that would be too good to be true, wonder if we can pull the settings from another device and input them in the values you changed such as taking the values from a captivate rom...
molotof said:
Did you edit the build.prop file on the fly or had to modify it before reflash ?
As for the density of the screen, did it affect the layout in landscape as opposed to portrait and was there anything out of place on the home screens ?
Click to expand...
Click to collapse
The layout in the landscape lines up much better.
EDIT to OP: Added steps
MKVFTW said:
Code:
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=275
Click to expand...
Click to collapse
This kills the dialer. Even 248 does not work. If you are using stock dialer like I am you have to keep the density at 240.
Immix said:
This kills the dialer. Even 248 does not work. If you are using stock dialer like I am you have to keep the density at 240.
Click to expand...
Click to collapse
Holy crap, your right it does. Hmmm. Ill make note in the OP and start figuring out why. Are you stock? Or using gingerblur?
MKVFTW said:
Holy crap, your right it does. Hmmm. Ill make note in the OP and start figuring out why. Are you stock? Or using gingerblur?
Click to expand...
Click to collapse
I am rooted and deodexed (DG's adeo ROM), running 4.1.26. Do you know what was the original screen density? I don't think it was 240 and I messed up my build.prop.bak too.
yeah i just was gonna comment on how changing the dpi to 275 kills the dialer/contacts
I just changed it back to the original build.prop and everything is working again
Im using stock .157 if that helps anyone (rooted)
**EDIT
original density is 240
Immix said:
I am rooted and deodexed (DG's adeo ROM), running 4.1.26. Do you know what was the original screen density? I don't think it was 240 and I messed up my build.prop.bak too.
Click to expand...
Click to collapse
Yes it is 240
Immix said:
I am rooted and deodexed (DG's adeo ROM), running 4.1.26. Do you know what was the original screen density? I don't think it was 240 and I messed up my build.prop.bak too.
Click to expand...
Click to collapse
says 240 on my phone:
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=240
Yep. Dialer dead. Damn.
Dialer is dead, however you can still use contacts app to dial for what its worth
the DPI setting has no effect if you're using a launcher like Go Launcher or LP right?
dLo GSR said:
the DPI setting has no effect if you're using a launcher like Go Launcher or LP right?
Click to expand...
Click to collapse
It does. It changes the dpi for everything.
Sent from my soon-to-be-hacked Bell Atrix.
I use 230 LCD density, and use dialer one instead of the stock dialer which only works at 240 density. I like being able to fit more on the screen with the smaller densitiy setting.
So any u/d speed reports from any at$t users who inserted these settings ?
You can over come the dialer problem by setting a market dialer in place of the stock dialer if you like the new density.
Sent from my MB860 using XDA Premium App
hey guys anyone tried changing the
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
max number to more than 2? i tried it on 3 but still it allows only 2, however apparently the sensor would allow up to 10 max points
I've used 220 LCD Density for a few weeks now - means I can set LauncherPro to 5 cols by 7 rows, so plenty of widget space. I like to have almost everything on my front screen.
Only issues I've encountered are the dialer (so I use Dialer One instead), and I think it's responsible for my fingerprint settings page being unavailable. If you set the fingerprint lock before changing density though, the settings are retained.
Had similar speeds before the tweak as you.
Tests afterwards have been getting:
1200-3200kbs and 350kbs~ up
What exactly do your tweaks change?
I'll share with you the /system/build.prop tweaks I have in the upcoming Nova.
You can do this on any ROM, even on stock, you just need a file manager with root access and built-in editor. Edit this file and add/change/remove values as follows.
Here we go:
Code:
# Force launcher into memory
ro.HOME_APP_ADJ=1
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
# VM Heapsize; 512MB RAM = 48 is better
dalvik.vm.heapsize=48m
# Render UI with GPU
debug.sf.hw=1
# Decrease dialing out delay
ro.telephony.call_ring.delay=0
# Helps scrolling responsiveness
windowsmgr.max_events_per_sec=150
# Save battery
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
# Disable debugging notify icon on statusbar
persist.adb.notify=0
# Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Photo and video recording quality tweak
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Signal tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
# Net 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
# Disable blackscreen issue after a call
ro.lge.proximity.delay=25
mot.proximity.delay=25
# Fix some application issues
ro.kernel.android.checkjni=0
# Phone will not wake up from hitting the volume rocker
ro.config.hwfeature_wakeupkey=0
# Force button lights on when screen is on
ro.mot.buttonlight.timeout=0
# Disable boot animation for faster boot
debug.sf.nobootanimation=1
# Miscellaneous flags
ro.config.hw_menu_unlockscreen=false
persist.sys.use_dithering=0
persist.sys.purgeable_assets=1
dalvik.vm.dexopt-flags=m=y
ro.mot.eri.losalert.delay=1000
# LG flags
persist.service.pcsync.enable=0
persist.service.lgospd.enable=0
Adding some more (14/08/11) for Nova v4...
Code:
# Change ROM name
# (forgot to add this one before)
ro.build.lge.version.release=My ROM name
# Disable LG ****
# (flex must be enabled or phone app will FC) - [U]needs moar testing[/U]!
user.feature.flex=true
user.feature.lgdrm=false
user.feature.lgresource=false
user.feature.lgpoweroff=false
user.feature.ls_event=false
user.feature.ls_normal=false
user.feature.sui=false
If anyone has some other tweaks or better values (tested of course) please do share.
Thanks! I go to try with the Orange stock rom v10b.
Nice Noejn.
# Helps scrolling responsiveness
windowsmgr.max_events_per_sec=150
Here I use 260 and it is very smooth and responsive. The maximum value for this tweak is 300.
# Save battery
wifi.supplicant_scan_interval=180
180 is the scan interval in seconds so you can use a lower or higher value.
Good topic
Noejn said:
Code:
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
This will make for very large files. I would suggest using a value of 90-95, this will be indistinguishable from quality 100 while leaving smaller files. You can test this yourself by encoding any high quality image using various JPEG quality settings with the image tool of your choice.
Code:
# Net 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
I don't know what those values used to be in their default state, but I am sure that it isn't sensible to use the same values for all networks. TCP buffer sizes should consider bandwidth and delay of the connection, which are both vastly different between edge and wifi for example.
Other values which seem interesting are:
Code:
user.feature.lgdrm=false # disable lg drm service
I can confirm this will disable the lg drm service - I have no idea what it does, but apparently I don't need it.
Code:
user.feature.flex # don't disable this
flex must be enabled, else com.android.phone and com.android.mms will crash constantly.
These can be disabled without visibly breaking something:
Code:
user.feature.lgresource
user.feature.lgpoweroff
user.feature.ls_event
user.feature.ls_normal
user.feature.sui
Anyone know what they do?
Click to expand...
Click to collapse
launcher into memory
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
can also be used using another launcher, like Launcher7 or Zeam? Have i change something?
Wady el-Natrun said:
can also be used using another launcher, like Launcher7 or Zeam? Have i change something?
Click to expand...
Click to collapse
Of course =) It will do the same for every launcher. It isn't specific for LG.
I really don't get it... If this value actually given a better performance, why didn't those LG's engineer use this value for stock ROM?
They do know aren't they?
i04055 said:
I really don't get it... If this value actually given a better performance, why didn't those LG's engineer use this value for stock ROM?
They do know aren't they?
Click to expand...
Click to collapse
Ask them, they come to this forum.
don't tell me they come here to learn how to make a better ROM...
Maybe the factory setting is for failsafe defaults. Like ones on computer BIOS, only advanced user dare to change to their own setting.
Sent from my LG-P970 using Tapatalk
Noejn, but...his change are already in your NOVA rom?
Becouse when i open the build.prop i found all this tweaks. (i have your rom)
of course, it is already included in teh Nova ROM....
digitalfrost said:
Noejn said:
Code:
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
This will make for very large files. I would suggest using a value of 90-95, this will be indistinguishable from quality 100 while leaving smaller files. You can test this yourself by encoding any high quality image using various JPEG quality settings with the image tool of your choice.
Click to expand...
Click to collapse
I would also prefer a quality factor of 90-95% in Nova as 100% results in much larger files and only slightly better quality.
Click to expand...
Click to collapse
lesp4ul said:
Maybe the factory setting is for failsafe defaults. Like ones on computer BIOS, only advanced user dare to change to their own setting.
Click to expand...
Click to collapse
My guess is they can't lose time on experimental values.
They will go for stable and heavily tested ones already.
digitalfrost said:
Code:
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
This will make for very large files. I would suggest using a value of 90-95, this will be indistinguishable from quality 100 while leaving smaller files. You can test this yourself by encoding any high quality image using various JPEG quality settings with the image tool of your choice.
Click to expand...
Click to collapse
Irrelevant. You have plenty of space in /system partition and having this really won't affect your internal memory because:
a) you already have reserved space for system partition
b) we're talking about 3 MB, tops. considering I removed 80% of LG applications which account for like 150 MB do you think that system partition is that small?
So it's a luxury we can perfectly have. Besides, I do notice 10% of quality difference.
digitalfrost said:
Other values which seem interesting are:
Code:
user.feature.lgdrm=false # disable lg drm service
I can confirm this will disable the lg drm service - I have no idea what it does, but apparently I don't need it.
Click to expand...
Click to collapse
Nice tip.
But they have a whole partition for that service, it's strange you don't notice a difference.
Wady el-Natrun said:
Noejn, but...his change are already in your NOVA rom?
Becouse when i open the build.prop i found all this tweaks. (i have your rom)
Click to expand...
Click to collapse
In the new version yes. In the old one I guess a missed a few.
@Noejn
build.prop tweak. it can use in stock firmware v10e?
Noejn said:
My guess is they can't lose time on experimental values.
They will go for stable and heavily tested ones already.
Click to expand...
Click to collapse
Yes it could be, too, LG r&d guys surely knew about this and decided to setup this defaults. That's why smart devs like you and other nova contributors should maximize this phone potential, what next?
Sent from my LG-P970 using Tapatalk
i04055 said:
of course, it is already included in teh Nova ROM....
Click to expand...
Click to collapse
Yeah, I didn't found any changeable because they are already tweaked haha.
Sent from my LG-P970 using Tapatalk
Is it right that i must add the most of your tweaks in stock rom?
Because i can't find these lines in stock rom build.prop!
There is only "dalvik.vm.heapsize=32m" to find!
And if i add these tweaks, i can simply write them on the end of the page?
With or without the "#" line?
Thank you
# Disable blackscreen issue after a call
ro.lge.proximity.delay=25
mot.proximity.delay=25
this option didn't work for me... I even tried to change do 10, 3, even 1, I didn't see any difference...
Applied only few tweaks to stock 10e:
mod sql by Noejn
ro.HOME_APP_ADJ=1
debug.sf.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
And now UI seems a bit too responsive and fast in some cases, heheheh
Hey Guys,
So i got my nexus 7 about a week ago and had noticed a touch response delay and it made scrolling through the homescreen and webpages a pain. I searched around last night and this morning and found these build prop tweaks.
#Response
debug.performance.tuning=1 - Increases touch responsiveness.
video.accelerate.hw=1 - Increases touch responsiveness.
windowsmgr.max_events_per_sec=150 - Increases scrolling responsiveness.
I aslo have fauxclock 123 installed from the play store and disabled the tegra 3 smart dimmer. After doing both i see a substantial increase in responsiveness. let me know if anyone else gets the same result.
Do you add these to the build prop yourself, or are these supposed to be in there already with a different value?
Did you update to 4.2.1? It fixed all my issues.
Sent from my Nexus 7 using xda premium
Im on stock rooted 4.2.2 and still have slow scrolling and bounce back issues, i have just added these lines to my build prop and am giving it a go, i will report back with result, thanks for this! I hope it makes it better!
leonclement said:
Im on stock rooted 4.2.2 and still have slow scrolling and bounce back issues, i have just added these lines to my build prop and am giving it a go, i will report back with result, thanks for this! I hope it makes it better!
Click to expand...
Click to collapse
I am running Glazed build 4.1.2. How do I apply these fixes? Is this something I can do by myself or should I rely on a dev?
Edit: Upon further research, it seems that these values should be applied to /system/build.prop right? I don't see those headings anywhere, do I just copy and paste those 3 lines anywhere into the file?
Worked perfectly on my 8GB Nexus 7 running Paranoid Android 3.15. You rock!
Atrix2destroyer said:
I aslo have fauxclock 123 installed from the play store and disabled the tegra 3 smart dimmer. After doing both i see a substantial increase in responsiveness. let me know if anyone else gets the same result.
Click to expand...
Click to collapse
there are cheaper options to disable smart dimmer than spending $4.
in terminal:
echo "0" > /sys/devices/tegradc.0>smartdimmer/enable
if you have rom toolbox, you can go into the scripter app, create a new script with that command and set it run at boot.
if you want purchase an app to do it for you: https://play.google.com/store/apps/details?id=com.widgets.big.tegra.prism.toggle
cnstarz said:
there are cheaper options to disable smart dimmer than spending $4.
in terminal:
echo "0" > /sys/devices/tegradc.0>smartdimmer/enable
if you have rom toolbox, you can go into the scripter app, create a new script with that command and set it run at boot.
if you want purchase an app to do it for you: https://play.google.com/store/apps/details?id=com.widgets.big.tegra.prism.toggle
Click to expand...
Click to collapse
Thanks for the heads up... Definitely kind of a waste to spend $4 just to disable that file. But fauxclock is a great app definitely worth the money
build.prop edits are very easy and useful, they can be applied on stock rom/kernel, i have compiled this from various sources!
For ICS, most of these will be useless
Locate build.prop
got to system/ and find build.prop
Edit with notepad++. Save and overwrite previous file, then change permissions to rw,r,r!
Change the tweaks already present and add new at the end of file!
Change android name and version
ro.build.display.id=Your ROM name
ro.build.version.release=2.3.6 (Android version number)
Decrease boot time
debug.sf.nobootanimation=1 (Disables bootanimation)
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate
dev.bootcomplete=0
Power saving
ro.ril.power_collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=120 (sets wifi scanning interval, can be increased or decreased)
ro.mot.eri.losalert.delay=1000 (might break tethering)
3G Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=5
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.rill.enable.a53=1
Telephony/ring Tweaks
ro.telephony.call_ring.delay=0
ring.delay=0
Proximity (Disable blackscreen issue after call)
mot.proximity.delay=0
ro.lge.proximity.delay=25
Smooth Scrolling
windowsmgr.max_events_per_sec=84(This value is experimental)
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
Disables error reports
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
Force home launcher into memory(use light launchers only)
ro.HOME_APP_ADJ = 1
Render UI with GPU
debug.sf.hw = 1
Disable logcat
logcat.live=disable
dalvik.vm.heapsize = 64m
Note: This value is different for different phones, the value can larger(128m) with larger RAM device, use accordingly!
Phone will not wake up from hitting volume rocker
ro.config.hwfeature_wakeupkey=0
Change LCD density
ro.sf.lcd_density=160
Allows purging of assets to free up RAM
persist.sys.purgeable_assets=1
Locate bools.xml
1. Decompile framework-res.apk
2. Go to res/values and find bools.xml
The file generally contains true and false values for various things, change true->false and false->true to see the magic!
config_sf_slowBlur
Blurred background when power menu comes up
config_automatic_brightness_available
Enable/disable automatic brightness
config_unplugTurnsOnScreen
Screen turns on after unplugging usb
config_animateScreenLights
Keep "true" for CRT OFF animation
config_disableMenuKeyInLockScreen
Disable hard key in lockscreen
lockscreen_isPortrait
Lockscreen in potrait/landscape mode(experimental)
config_batterySdCardAccessibility
Indicate whether the SD card is accessible without removing the battery.
config_carDockEnablesAccelerometer
Control whether being in the car dock should enable accelerometer based screen orientation.
config_deskDockEnablesAccelerometer
Control whether being in the desk dock should enable accelerometer based screen orientation.
skip_restoring_network_selection
If restoring network selection should be skipped The restoring is handled by modem if it is true.
Thanks for this. I have seen these tweaks before but its really nice to have an explanation.
Sent from my SGH-T989D using Tapatalk 2
cwillison94 said:
Thanks for this. I have seen these tweaks before but its really nice to have an explanation.
Click to expand...
Click to collapse
There are a lot of threads on the subject, but would Google any before using them as some work better on other devices or they don't do anything at all.
XperienceD said:
There are a lot of threads on the subject, but would Google any before using them as some work better on other devices or they don't do anything at all.
Click to expand...
Click to collapse
Yes, scrolling speed, vm heapsize, lcd density etc are different for devices!
Sent from mass relay
No point of putting CRT off animation there....
js2892 said:
Allows purging of assets to free up RAM
persist.sys.purgeable_assets=1
Click to expand...
Click to collapse
can u please explain this in details..
thanks
Sent from my GT-S5830i using xda app-developers app
srt99 said:
can u please explain this in details..
thanks
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
allows system to free ram by klling unused assets(programs) !
I once tried to change my phones model via build prop using the same method you wrote up and my phone bootlooped.
Im on n2 sgh-i317.
I fixed it but was wondering what I could have done wrong. Im slowly inching towords getting my feet wet in learning aboutvrom making. Nice thread btw.
freakboy13 said:
I once tried to change my phones model via build prop using the same method you wrote up and my phone bootlooped.
Im on n2 sgh-i317.
I fixed it but was wondering what I could have done wrong. Im slowly inching towords getting my feet wet in learning aboutvrom making. Nice thread btw.
Click to expand...
Click to collapse
u mean the android version or the phone name...
well, irrespective of that, it's quite weird that build.prop edit lead to bootloop...I've edited these things many times and worked normally for me..
if you know how to read logcat etc, u can get a logcat try that to point out the reason for the same!
Thank you, It would be usefull for me.
Thank
Thank u for this post. I will test on my devices.
Before posting things like this, I highly recommend reading this and this just so you know what works and what does nothing (hint: a lot of the tweaks don't work)
pandaball said:
Before posting things like this, I highly recommend reading this and this just so you know what works and what does nothing (hint: a lot of the tweaks don't work)
Click to expand...
Click to collapse
Well, i've read this earlier but forgot to mention about this in OP (i'm still on a GB phone)
Thanks for pointing out, i've edited the OP.
For GB, i've tested them and they work like a charm( with exceptions for some phones).
Thanks for this!
Good Job
Okay
Thanks a lot
Hlpful to me and will be for noobs like me
Really helpful. Should have pressed thanks twice if that was possible
Thanks you
Shadman0 If I help U Pls Give Thanks
My Work http://forum.xda-developers.com/showthread.php?t=2521867
Yea great thread I also am learning android development thanks to you guys. It's cool to know how to modify my devices to my liking.
Sent from my GT-N7105 using Tapatalk
This is how I setup my rom after flash, and device is working very well with 52 installed apps
1. Configure settings
-Go to wifi and disable scanning always on
-Open mobile network and chose 2G (use 3G only when you need it)
-Go to more and then to mobile broadcasts and disable all (when it enabled, consume RAM)
-configure sound,display, and interface... As you want
-go to accounts and disable sync which you don't need.
-go to About and taping on blablabla, you know to enable Developer options and rom performance.
-Go to developer options set all animations(you have three) to 0.5
-Performance??
-you don't need it, I will show you in next step.
2. Flash this:
L Speed
Or make this manualy
2.1. Install&Configure TricksterMod
-For cpu freq the best is to set device default, like on stock rom, don't forget to press Lock freq.
-Minfree setup
-8mb
-12mb
-17mb
-25mb
-29mb
-33mb
-Syscontrol setup
-Set swappiness to 60
-Set vm.vfs_cache_pressure to 40
-vm.dirty_ratio = 90
-vm.dirty_background_ratio = 70
Set this from tricksterMOD
-CPU freq
The best is
-Min freq
320Mhz
-Max freq
1008mhz
-Scheduler
SIO
-Governor
SmartassV2 or SmartassH3
-GPU freq
-That is your choice min freq will increase battery life, but some laggs is possible, max freq will drain battery faster, but there is less possibility to have lag.
After all don't forget to set run on boot.
3.Install&Configure Greenify
-You already know Hibernate what you want expect Alarm clock, messaging apps, trickster mod, etc.
You already know if you hibernate app with push notifications, you don't get it.
4. Apps
-what about apps??
There is too much apps which user don't use, that apps use ram like other.
Now you need to delete everything what you don't use (live wallpapers, cm wallpapers, etc.) or change apps with some lightweigh, like gallery and keyboard. Download QuickPIC and google keyboard (lollipop themed) {{i will add link later }}
5.build.prop
-leave build.prop to default as much as possible.
-change DPI to device standard, in some reasons my device lag on 200, then I move back to 240 as default. This is for L7.
For L5, there is no line that define DPI, you can skip this step.
-Change ro.max.fling from 4000 to 8000 (don't add ro.min)
-Change vm.heapsize to 64m (I don't go under that, but difference is big from 128 to96 choose between 96 or 64
-Change lowRAM from false to true (you will get little more free RAM).
When you change it to true, you will lose transparent statusbar.
6.init.d
-keep device without any special tweaks, devs which make this rom, they choose the best.
Helpful tips:
-Don't use battery boosters, ram boosters and apps call like that. System do better than one app. There is low memory killer (lmk).
Also this app use ram which you maybe need for something.
Nice tips buddy!
Good job!
Sent from my IdeaTab A2107A-H using Tapatalk
skyinfo said:
Nice tips buddy!
Good job!
Sent from my IdeaTab A2107A-H using Tapatalk
Click to expand...
Click to collapse
Thanks dude
Realy good,i add some of the sets into my rom,thanx!!!
NERDIFIED TILL DEATH!!!
thnx a lot, i hope it all works for me too
since gpu freq is not changing to 245 (for some reason) I decided to stick with 380 because I run ePSXe on my phone
turkiktxhc said:
thnx a lot, i hope it all works for me too
since gpu freq is not changing to 245 (for some reason) I decided to stick with 380 because I run ePSXe on my phone
Click to expand...
Click to collapse
Is device faster???
Everyone who have L7 know speed
-CALIBAN666- said:
Realy good,i add some of the sets into my rom,thanx!!!
I
NERDIFIED TILL DEATH!!!
Click to expand...
Click to collapse
I will post video tonight to see speed of my device
But say me how to post video on xda
Paget96 said:
Is device faster???
Click to expand...
Click to collapse
It's extremely fast at this point, i'm only afraid of it gradually slowing down after days of use
right now, it's really fine
-CALIBAN666- said:
Realy good,i add some of the sets into my rom,thanx!!!
NERDIFIED TILL DEATH!!!
Click to expand...
Click to collapse
Quality is too bad, but.
https://www.youtube.com/watch?v=tm5ay4alFPQ&feature=youtube_gdata_player
Vrh brate
Thank you for these settings
Paget96 said:
This is how I setup my rom after flash, and device is working very well with 52 installed apps
1. Configure settings
-Go to wifi and disable scanning always on
-Open mobile network and chose 2G (use 3G only when you need it)
-Go to more and then to mobile broadcasts and disable all (when it enabled, consume RAM)
-configure sound,display, and interface... As you want
-go to accounts and disable sync which you don't need.
-go to About and taping on blablabla, you know to enable Developer options and rom performance.
-Go to developer options set all animations(you have three) to 0.5
-Performance??
-you don't need it, I will show you in next step.
2. Install&Configure TricksterMod
-For cpu freq the best is to set device default, like on stock rom, don't forget to press Lock freq.
-Minfree setup
-8mb
-12mb
-17mb
-25mb
-29mb
-33mb
-Syscontrol setup
-Set swappiness to 60
-Set vm.vfs_cache_pressure to 40
-vm.dirty_ratio = 90
-vm.dirty_background_ratio = 70
-Gpu freq
-That is your choice min freq will increase battery life, but some laggs is possible, max freq will drain battery faster, but there is less possibility to have lag.
After all don't forget to set run on boot.
3.Install&Configure Greenify
-You already know Hibernate what you want expect Alarm clock, messahing apps, trickster mod, etc.
4. Apps
-what about apps??
There is too much apps which user don't use, that apps use ram like other.
Now you need to delete everything what you don't use or change apps with some lightweigh, like gallery and keyboard. Download QuickPIC and google keyboard (lollipop themed) {{i will add link later }}
5.build.prop
-leave build.prop to default as much as possible.
-change DPI to device standard, in some reasons my device lag on 200, then I move back to 240 as default.
-Change ro.max.fling from 4000 to 8000 (don't add ro.min)
-Change vm.heapsize to 64m (I don't go under that, but difference is big from 128 to96
-Change lowRAM from false to true (you will get little more free RAM).
6.init.d
-keep device without any special tweaks, devs which make this rom, they choose the best.
Only if you want add zipalign.
Click to expand...
Click to collapse
pretty good and usefull tips :good: :good: but if i edit the build.prob i get black screen on boot
Jobloxx said:
pretty good and usefull tips :good: :good: but if i edit the build.prob i get black screen on boot
Click to expand...
Click to collapse
You think bootloop?? Or just black screen??
Anf which device you use?
Dj_Luxor said:
Thank you for these settings
Click to expand...
Click to collapse
no problem
Thanks for using my setup.
Paget96 said:
You think bootloop?? Or just black screen??
Anf which device you use?
Click to expand...
Click to collapse
When i manually edited the build.prop I ended up black screen too, then i tried out the build.prop Editor app, which worked for me.
vangama said:
When i manually edited the build.prop I ended up black screen too, then i tried out the build.prop Editor app, which worked for me.
Click to expand...
Click to collapse
Then ok
@Paget96 really cool! This is actually what I'm trying to do bro and thanks muchly for this configuration tips. I got more infos:thumbup:
Paget96 said:
You think bootloop?? Or just black screen??
Anf which device you use?
Click to expand...
Click to collapse
No blackscreen and i have l7
junephel said:
@Paget96 really cool! This is actually what I'm trying to do bro and thanks muchly for this configuration tips. I got more infos:thumbup:
Click to expand...
Click to collapse
Ok
Thanks for helping.
Added little stuff
Maybe someone use it
Jobloxx said:
No blackscreen and i have l7
Click to expand...
Click to collapse
now working used an editor working great