Related
Ive tried it, seems to improve launcher responsiveness and scrolling, much less lag.
http://forum.xda-developers.com/showthread.php?t=991276
which group of settings did you find to work best on the script?
i only tried one option #2 I think
chrisrotolo said:
i only tried one option #2 I think
Click to expand...
Click to collapse
I have tried both the V6 and ram optimization in the General thread on page two. I dont notice a difference in UI speed. Maybe because I use ADW EX launcher.
I will run it for a day and see how either affect my battery or other performance.
Thanks for the heads up.
I tried it with option 7(?) one of the ones with 512mb optimization and my phone wouldn't boot on 1.9.1. I thought it meant 512mb optimized, but in hindsight maybe it meant that much to be FREE which would render the phone essentially useless.
I may try again with a different option.
looking at the script it seems to work in the same manner autokiller memory optimizer does on market by modifying the mem values and some other stuff.
Autokiller has other functions and stuff, but one of it's features is to allow you to fudge with the memory values. When i used it i only used it for that and I dont recall noticing any real changes at all and that's why I uninstalled it.
You should read my OP.
Nothing else fixes OOM groupings. AKMO didn't do anything because the apps werent where you thought they were.
was using aggressive performance #1, the top option, now moved to the 2nd to top option. The only thing I may be concerned about is when plugging in USB, seems to hav some lag issue.(probably cause that service was asleep/killed and needed to be restarted, but it was much slower than normal. Also had a few random reboots, which I dont usually have.
not sure how changing OOM values could alter reponsiveness of scrolling..
Actually, it's the OOM grouping rearranging that does wonders...
Anybody try the 3G TurboCharger or Kick Ass Kernel Tweaks?
I tried it and keep getting an error about /~somepath~/minfree file doesn't exist.
zeppelinrox said:
Actually, it's the OOM grouping rearranging that does wonders...
Anybody try the 3G TurboCharger or Kick Ass Kernel Tweaks?
Click to expand...
Click to collapse
I tried it on my last install of Streakadroid 1.9.1 and didn't notice any improvement whatsoever... also tried the 3g deal and the other without any noticeable improvements.
We Streak owners have come to the realization that for most tweaks to have any noticeable effect they have to be tailored just for the streak
Looking at the 3G settings, Now I believe it will work for some phones in some areas. For me it made my connection worse in both upload and download. I ran the test from Speakeasy.net/speedtest and for me it went from averaging 1.21d 0.4u to .56d .48u. I ran the test plugged in and ran the test after a reboot 5 times.
I made a change to 3g TurboCharger that needs testing...
Edits to build.prop...
Code:
ro.ril.hsxpa=3
ro.ril.gprsclass=34
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=28
ro.ril.enable.a53=1
ro.ril.enable.a52=0
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=268449905
ro.ril.hsupa.category=9
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
ro.ril.enable.sdr=1
ro.ril.enable.gea3=1
ro.ril.enable.fd.plmn.prefix=23402,23410,23411
ro.ril.disable.power.collapse=0
Difference between this and update 2:
ro.ril.gprsclass=34 (instead of 12)
ro.ril.htcmaskw1=268449905 (instead of 14449)
I've actually seen gprsclass=32 in the past but 12 is the most common setting so I had used 12.
After researching today, seems that 32 would indeed be better than 12 BUT there is a new gprs class 34 so this would be a first for testing it at 34! (as far as I know) lol
So, I'd be interested in seeing if this is better than the 3G TurboCharger update 2 tweak!
do u understand that the streak uses GPRS Class 12 and HSxPA Cat 8/6?
I understand that it actually depends on your provider.
But after some testing, seems that the first 2 lines work better like this:
ro.ril.hsxpa=5
ro.ril.gprsclass=32
I'M A SUPPORTER OF BRINGING OFFICIAL ICS TO THE VIBRANT AND OTHER GALAXY S DEVICES!
> CLICK HERE FOR MORE INFORMATION <
Click to expand...
Click to collapse
CAPTIVATE edition of the Platypus Revolutions kernel
This Project is inactive/low activity for a longer period of time
Kernel
CM7 & MIUI only
NEO series
(since May 24th '11)
Do you want to discuss on this kernel, get the news on the current state of development, or test kernels even fresher than fresh ?
connect via webchat from your browser:
http://webchat.quakenet.org/
and join #platypus-kernel
(recommended)
Fire up your IRC client, and join via client
the server (for now is) : irc.quakenet.org
port : 6667
Channel : #platypus-kernel
(thanks to Tk for the layout idea )
before you ask for any ETAs:
The first rule of CyanogenMod [and this project]: DO NOT ASK FOR AN ETA!
---------------------------------------------------------------------------------------
First step before install & kernel switch:
Always have this cleaning script on your internal SD card ready
If you're
- switching kernels,
- have issues with auto-rotation,
- the cam,
- bootloops
- want to remove init script
- recover from a failed overclock attempt
please give either:
- lippol94's updated cleaning script (apply via CWM recovery): http://www.multiupload.com/XFH1GCK4MB
or
- WiwiPouPou's SYSTEM CLEANER SCRIPT (also apply via CWM recovery): (http://forum.xda-developers.com/showpost.php?p=14805606&postcount=21739)
a try
the kernel already applies some cleaning steps during install but sometimes that's not enough ...
---------------------------------------------------------------------------------------
Introduction:
Hi guys,
this is my first modded kernel for the SGS (CM7/MIUI only)
I first needed to test it to make sure that it'll be stable & boot at the first place
so far it's very fast & responsive & smooth
This thread shall serve as the center for my testing kernels (stability & functionality-wise)
DISCLAIMER: the kernel (binary) and driver modules are provided as is. If problems occcur they most probably are from upstream and can be fixed with the newest version. Since I'm doing this in my free spare time as a hobby (quenching my thirst for tweaks & performance) updates will occur irregularly as time permits and I see fit (most probably when new features & bugfixes arrive). YOU are responsible for the actions that you take (such as over- or underclocking), etc. You agree that I can not be held liable for any potential damage that arises from your actions in combination with or the usage of this kernel and other related parts.
Kudos:
* Google, Andy Rubin & the whole Android crew
* Linus Torvalds & the kernel hackers for upstream Linux
* cyanogen & all the devs out there hacking on this
* Supercurio for enriching our media experience of this smartphone
* codeworkx, coolya, guiper, atinm - the whole teamhacksung|cmsgsteam crew and all other hackers working on CM7
* laststufo, hardcore, nikademus, existz and all the other kernel hackers on the SGS forum
* zen-kernel team for inspiration to create a kernel, too
* all other contributors (devs, users, etc.) who make this possible
The purpose of these kernels is extensive stability testing addressing the following sticking points:
- overall stability & functioning of the kernel and phone
- call drops, missed calls, etc.
- lags (suggestions for improvements are welcome)
- auto-rotation, sensors, etc.
- Voodoo Control Plus [any crashes ? compatibility problems ?]
- working on CM7 or MIUI ?
- scheduler, sound, video synchronisation & lags: Tap Tap Revenge 4 (especially at the beginning of songs)
- scheduler, sound, video synchronisation and any other issues: doodle dash (while shooting & sound activated)
- proper pmem memory layout & settings: proper functioning of Google Googles
for those who love SAUCE (Source):
old source:
ALL MY SAUCE for QUORRA KernalZ ^^
new source:
android_kernel_samsung_aries
(fork and 1:1 update to upstream kernel source - changes in different branches)
(latest changes sometimes might not be in [yet] but in the whole repo everything should be available)
current UV & OC stable values:
Recommended apps for OC/UV:
- Pimp my CPU (also available here on XDA for those who don't have a credit card, etc.)
- Xan's VoltageControl
on stability testing:
http://forum.xda-developers.com/showpost.php?p=13255871&postcount=5
(start with "Q: I'm new in OC/OV operations so please could you explain to me how to set it in the best way?")
the following OC/UV values are only applicable for kernels with the old OC/UV implementation (max. 1.3 GHz)
my current UV (undervolt) stable Values :
old OC/UV implementation (morfic, bilboa1/kang, TheEscapist):
1300000 0 (haven't tested 1.3 GHz much yet)
1200000 -25
1000000 -50
800000 -75
600000 -100
400000 -100
200000 -125
100000 -150
edit:
1200000 -50
1000000 -75
800000 -75
600000 -225
400000 -125
200000 -150
100000 -175
thanks jetcz !
new OC/UV implementation (morfic, bilboa1/kang, TheEscapist - Tk-Glitch):
Tk-Glitch said:
Note that these UV settings will be unstable on many devices. It's only informative.
1600 MHz - 1.500v / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1500 MHz - 1.500v / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1440 MHz - 1.475v / -75mv
1400 MHz - 1.450v / -75mv
1300 MHz - 1.400v / -75mv
1200 MHz - 1.350v / -75mv
1000 MHz - 1.250v / -50mv - If you have stability issues, try to let this one by default.
800 MHz - 1.200v / -75mv
400 MHz - 1.050v / -100mv
200 MHz - 0.950v / -150mv
100 MHz - 0.950v / -200mv - (can be very different between two devices)
More volts is not always equal to more stability. Try to add more UV (less volts) if the frequency you're trying to achieve is unstable.
Considering all phones will respond differently to OC/UV, to tweak the values to suit your device will be required.
By default, no overclock/undervolt is applied. You'll need to use one of the tools below to adjust the frequencies and voltages.
Note : Never ever use SetCPU with this kernel. You could encounter many stability problems like random reboots or bootloops.
Click to expand...
Click to collapse
3D performance and games:
recommended apps:
[root] Chainfire3D
1st backup post (kernels)
Kernels:
kernels are listed in descending order
older -> newer (newest at the bottom - for now)
officially declared new stable kernels will be up soon !
for now please go to the IRC channel (1st post to get the newest test-builds)
NEO 17 -r12 codename: Butterfly
http://forum.xda-developers.com/showpost.php?p=17339783&postcount=21
NEO 17 -r18 codename: Butterfly
http://forum.xda-developers.com/showpost.php?p=18268518&postcount=132
NEO 18-update1 codename: funky fish
NEO XX.1-update1 codename: mighty rhino
http://forum.xda-developers.com/showpost.php?p=19999998&postcount=192
ALL USERS MUST UPDATE (this fixes yet another potential data loss trigger)
2nd backup post (Changelogs)
Changelog list:
obsolete right now
3rd backup post (modems list)
modems:
Description:
Modems play a crucial role in how much battery drains in standy.
e.g. if you have a good signal area and the modem still has high
"Time without a signal" indicator under Cell standby you still will get bad standby time
make sure you have little to no "Time without a signal" in Cell standby
there also somewhat seems to be a connection between "Time without a signal" and high "Android OS" number in battery use (!)
Following modems are only compatible with new radio (modem) partition layout:
radio-cm-7-GalaxyS-JVP-signed.zip (4.29 MB)
md5sum: fb38dbf82daf0720fd2328f5f649013e radio-cm-7-GalaxyS-JVP-signed.zip
For more modems & bootloaders please go to siky_dude's Modem Thread:
[CM7/MIUI][28.08.11] Modems + Bootloaders(MD5)
[SGS / i9000 Thread so some frequencies might be missing, e.g. 850 MHz]
for more modems please refer to a modem thread in the Captivate Forums section
4th backup post (results)
Results & FAQ/Documentation
Results:
(04/27/2011) Results for platypus-kernel_20110427_18_quorra_r1:
- broken auto-rotation & sensors for some [insert ROM (CM7 ? MIUI ?)]
- stable
(05/03/2011) Results for CM7_SGS_platypus-kernel_20110503_17_quorra-r4_exp
- high battery drain, either due to kernel config or optimization flags, fixed with >= quorra r5 (2nd update)
FAQ / Documentation
@bootloop / boot post victims ^^
Hi guys,
could you please try to replace the existing kernel on your MIUI or CM7 nightly CWM-Package with my kernel, modules and its scripts ?
then install that updated package (with the new kernel, modules and scripts)
after that all should work
the bootloops seem to be an issue with bml_over_mtd (broken sectors on the SSD on your phone)
I'll investigate this and see if anything needs to be rewritten and/or updated in that regard
Thanks !
Overclocking / Undervolting:
Q: I'm new in OC/OV operations so please could you explain to me how to set it in the best way?
A: start with -50 mV (delta from default value) other values probably are too low
my testing includes:
- Angry Birds Rio (several missions)
- Gun Bros (for some time)
- mp3 playback, (flac playback - optional)
- surfing the web via browser, opening up bit.ly links from cmsgsteam twitter feed
- watching youtube video
- watching video via rockplayer lite or mobo video player
- running benchmarks (Smartbench 2011, quadrant standard, an3dbenchXL, anTutuBench)
- Labyrinth Lite (for gravity sensor), auto-rotation (also for sensor)
when 1 GHz (1,2 or 1,3) is OK - go lower with undervolt value (e.g. -75 mV)
after it gets un-stable - go back to last known stable value
then you can limit max frequency to lower one, e.g. 800 MHz
and repeat testing for that frequency
for more info: checkout shaolin95's Mini Overclocking Guide:
Link: http://forum.xda-developers.com/showthread.php?p=12910471#post12910471
LED Support FAQ
Q: Do LED notification require an app, such as BLN, etc ?
A: No. It uses Android's and Cyanogen settings, other apps are not required, although some that are designed for regular LEDs may work.
Q: How to I turn off LED notifications, scheduled or/and complete turn off?
A: Use Cyanogen's Quiet Hours feature (settings>cyanogen>sound>quiet hours) and check "Dim the LEDs during quiet hours" (in reality it will turn them off on the SGS). If you schedule a complete day, then LED notifications will be off all the time.
Q: How do I setup per app, find other LED settings etc?
A: Settings>cyanogen>interface>LED notifications
Q: What to do with LED color settings?
A: We have only one color, so that doesn't work. Use Green as default setting. Some non-bright colors turn off notification, as it's the equivalent as diming LEDs (note that on real LEDs if you dim them too much they look like off too anyway, the difference is that it's gradual. On the SGS the LEDs can be only on or off, not gradual)
Q: How can I troubleshot my system, I can use ADB but...
A: adb logcat | grep lights (on linux) will show you Android requests to turn LED on or off. "status" tells you what we decide will be interpreted as "turn LED on" (1= on, 0 = off)
adb shell cat /proc/kmsg for live view (or adb shell dmesg if you're using adb after the issues occurs - careful the backlog is limited in size so don't be too slow)
notify_led_on and notify_led_off are requests to the kernel to turn LED on or off.
touch key write/read errors (cypress) are non-fatal failures to ask the touch key to do something (eg lit up the LED), when the hardware goes crazy or there's a logical error in the code (can be both)
touch key recovery routine or "stopped responding" are either hardware errors, either a logical error where the driver would try to write something the touchkey doesnt understand. in some occasion lock&unlock fix those as a work around, of course a permanent fix is required
Voodoo Color settings:
Q: I don't have that nice ice-ish white color on my screen anymore - you suck !
Q: my screen looks like someone pissed on the screen - you suck !
(sorry for the language ^^)
A: I love you too ^^
download Voodoo Control or Voodoo Control Plus
Screen RGB multipliers:
- Red: 321*
- Green: 321*
- Blue: 429*
Screen v1 gamma hack:
- use Alt. settings
- or if you prefer others - use: "Reset to 2.3.3 defaults", "Punchy settings" (punchy could lead to a great screen while locking the screen and having "screen off" animation disabled)
other recommended settings:
Also a lil tip for people who use voodoo color!
1 )Color Profiles: Voodoo Profile V1
2 ) Screen v1 gamma hack :
- 50 red
- 53 green
- 44 blue
3 ) SRB multipliers:
Red ="2300875360"
Green ="2300875360"
Blue ="2709919680"
With those adjustment, black colors are BLACK and white colors are WHITE. Everyone should try this.
Click to expand...
Click to collapse
SGS CM7 nightlies wiki
http://sgscm7nightlies.pbworks.com/w/page/41483487/FrontPage
Android OS bug, :
(thanks to ceriko ! and his awesome guide for DarkyROM 10.1)
If your battery drains very fast and your battery stats mentions Android OS above 10%, often between 40 and 60%, sometimes more, this is the best to do as far as I know:
- Remove the 2/3 system files as per the beginning part of this guideguide about batterie issues.
- Install WatchDog and open (I set it to "moderate", then I close it, that's all), this app will warn you whenever an app or a process miss-behaves by draining the battery excessively. It will not fix it but just flag it and you will see a notification.
- Reboot usually stops the drain for a while until it naturally comes back, so reboot whenever you see Android OS above 10% and rising or after you see WatchDog mentioning "Suspend" process using too much battery (the suspend process hanging is the Android OS bug).
- Some apps trigger it, most common are Gameloft games (blame Samsung, not the games/apps). No need to use apps or games for this drain to happen, it also happens straight after boot once phone has been fully charged.
This bug can not be fixed by anyone but Samsung. Some never see it, some will experience it everyday no matters what they do... It's just annoying and unfair but that's the same on all Gingerbread releases by Samsung (JVK, JVB, JVO, JVH). Apparently even the SGS2 has this...
screenstate scaling aka my governor won't change after screen locked:
So what is this all about ?
it's an init script that is put in to /system/etc/init.d
and switches between the configured governors in the script
depending on whether the screen is on (AWAKE_GOVERNOR) or off (SLEEP_GOVERNOR)
in most cases your phone is off - in that case it would be good to use a governor which doesn't fire up the cpu frequency too fast since you don't need it (no GUI, smooth scrolling, etc. needed while the screen is off - lol),
so conservative governor is set
when using the phone (screen on) it really depends on what you want to do: e.g. latency & smoothness is crucial: try smartass2, smartass, ondemand;
you're mainly browsing & reading stuff: try ondemandb, conservative (the screen is already burning enough battery so you don't need another component burning yet more)
only use one governor at a time
e.g.
AWAKE_GOVERNOR
# AWAKE_GOVERNOR
# AWAKE_GOVERNOR
SLEEP_GOVERNOR
# SLEEP_GOVERNOR
# SLEEP_GOVERNOR
that means lines with "#" are commented out and not used by the script
e.g.
# AWAKE_GOVERNOR
AWAKE_GOVERNOR
# AWAKE_GOVERNOR
SLEEP_GOVERNOR
# SLEEP_GOVERNOR
# SLEEP_GOVERNOR
also would work (intentionally not filled in any governors)
@all:
Neo 17 r10 is available on IRC !
Changelog said:
NEO 17 (r10 - codename Butterfly) changelog [SGS/Telus, Captivate, Vibrant]
Changes (from r9 - 2nd testbuild):
• bumped RAM up to 348 MB (everything should still work, incl. Youtube HD recording)
• ported over smartass2 governor (super-smooth & battery-efficient, hopefully no issues anymore with getting stuck on high frequencies - unless due to system & broken apps)
• back to cm7 vanilla/stock yaffs2 driver - let's see if this fixes the discouraged random resets for few people (loss of contacts, apps gone, etc.)
Click to expand...
Click to collapse
Wow! New thread finally!
I'm testing with the Neo 17 R10 Kernel now.
Thanks!
Woohoo!
Sent from the frozen tundra known as Canada.
Spectacular. Gave it a shot from r7 and loving it since. Looking forward to future updates.
And about time for your own thread!
Sent from my I897 using Tapatalk
Thanks for the awesome kernels, they always work great, and I always look forward to the progression of this kernel. Thanks again for all your hard work, you are very talented.
Sent from my I897 using XDA App
I'm loving it as well, I don't oc much, maybe uv a little, and I do like the vc. Great work.
Sent from the frozen tundra known as Canada.
Thanks zach, r11 + smartassV2 is really super-smooth! You are doing an amazing job.
No problems so far, I got my last SOD on r9.
So on Neo 17 v11 what is set for governor(not showing in pimp)?? I got confused when reading the whole thing. Plus did you say it won't change from awake governor to sleep governor with the screen off? If so how do I make it so it does?? I don't see a screenstate scaling in root exploring under the right location. I have in the past but.can't now.
Sent from my I897 using XDA App
buresh.kevin said:
So on Neo 17 v11 what is set for governor(not showing in pimp)?? I got confused when reading the whole thing. Plus did you say it won't change from awake governor to sleep governor with the screen off? If so how do I make it so it does?? I don't see a screenstate scaling in root exploring under the right location. I have in the past but.can't now.
Sent from my I897 using XDA App
Click to expand...
Click to collapse
Uninstall Pimp My CPU.
Delete the Pimp My CPU folder in your SD Card.
Reflash the Neo 17 R11 Kernel and the V51 Script again.
Install back Pimp My CPU.
OK, you'll see the Governor and Scheduler which already been set by Neo 17 R11 Kernela and the V51 Script.
the new platypus 17r11 is superfast, my CAPPY felt great with it
thanks Zach
hope the color issue soon to be fix since i like to customize the color temp
Fate-Silver said:
Uninstall Pimp My CPU.
Delete the Pimp My CPU folder in your SD Card.
Reflash the Neo 17 R11 Kernel and the V51 Script again.
Install back Pimp My CPU.
OK, you'll see the Governor and Scheduler which already been set by Neo 17 R11 Kernela and the V51 Script.
Click to expand...
Click to collapse
Did you have this problem as well?? ha! I found the V51 Script, I think!
I tried to change awake governor but it's not showing in Pimp my Cpu. I rebooted, tried deleting & installing it again but no luck.
I edited the script with text editor from Root Explorer, put # infront of ondemandb, and took # from smartass2. Rebooted but pimp my cpu is showing ondemandb.
hi. can you flash this using the orange cwm that comes with cm7?
yuhenyo said:
hi. can you flash this using the orange cwm that comes with cm7?
Click to expand...
Click to collapse
Yes you can.
Sent from my I897 using Tapatalk
simple man said:
Yes you can.
Sent from my I897 using Tapatalk
Click to expand...
Click to collapse
awesome! can't wait to flash this. So is the download link in the other thread? I can't seem to find it on this one. or is it?
yuhenyo said:
awesome! can't wait to flash this. So is the download link in the other thread? I can't seem to find it on this one. or is it?
Click to expand...
Click to collapse
http://webchat.quakenet.org/
The instructions are in the O.P., but you'll need to login, download the file, extract the unpack_me.zip pick the kernel of your choice, download the kernel cleaning script 1st page this thread,flash it, then your kernel, then the screen state script.
Sent from my I897 using Tapatalk
This is all guide with bug fixing on minicm7 2.1.X
Screen Cut:
Only in CWM/CWR
NMEAListener:
I think NMEAListener is GPS
I found that gps.conf is europe settings
since that i have no problem with it
for non-europe residence Here Patch
Compass:
Wait till nAa fix
Video Recording Lag:
did you experience this
use this file Download
Auto Brightness:
use this tutorial
Code:
1. disable auto brightness first in display
2. go to cm settings --> display --> automatic backlight --> choose use custom and allow light decrease
3. tick edit other level
4. set number of levels to 13
5. look at this pic [URL="http://attachments.xda-developers.com/attachment.php?attachmentid=874309&stc=1&d=1327627892"]Here[/URL] And [URL="http://attachments.xda-developers.com/attachment.php?attachmentid=874311&stc=1&d=1327627892"]Here[/URL]
6. enable auto brightness in settings (not cm)
7. restart
8. enjoy
Android market app won't show up:
clear data on app settings
Just use recommended tweak:
Non-Recommended tweak make ur phone less stable
Recommended:
SuperCharger
Ram Manager / PRO
Juwe Ram's script
Etc...
Non-Recommended
Build.prop tweak
init.d tweak
IPV4/IPV6
Etc...
End of first post continued in 2nd post
Guide for Minicm7
Notice ADW launcher Lag use this settings:
Code:
1) Screen Preferences - Desktop scrolling speed - set to something low-ish like 150-200, default settings are just plain moronic here. Desktop overshoot should be fine at 30 or 40.
2) Drawer Settings - Horizontal Drawer definite on (this is far superior to the scrolling drawer if you have more than a few apps, and feels much smoother).
3) Drawer Settings - Zoom effect speed - 400 is a decent setting, default was way too high.
4) Drawer Settings - Columns/Rows - 4x4 is a nice setting for portrait, if you don't like a crammed screen.
5) System Preferences - Wallpaper Hack - check this. If you have issues, change wallpapers to something of a sane size.
6) System Preferences - Use Screen Cache - check this.
7) System Preferences - Scrollable Widget support - you should start with this unchecked. Only check it if you have issues with some
Make ur phone fast without tweaks?
here my perfomance settings
Go to CyanogenMod Settings --> perfomance settings
Code:
1.) Set compcache ram usage to 18%
2.) Enable use jit
3.) Disable Surface Dithering (optional)
4.) Enable 16bit transparency
5.) Enable Allow purging of assets
6.) VM heap size 48mb
7.)
SDcard cache size 1024kb Class 1,2
SDcard cache size 2048kb Class 3,4
SDcard cache size 3072kb Class 4,5,6,7,8
SDcard cache size 4096kb Class 9,10
Go to CyanogenMod Settings --> perfomance settings --> cpu settings
Code:
1.) Available gorvernor set to smartassV2
2.) Min Cpu frequency 245mhz
3.) Max Cpu frequency 691mhz+ (optional)
4.) Set on Boot
Make minicm7 more battery save?
here my battery save settings
Note: this settings overwrite "Make ur phone fast without tweaks"
Go to CyanogenMod Settings --> perfomance settings --> cpu settings
Code:
1.) Available gorvernor set to smartassV2
2.) Min Cpu frequency 19mhz
3.) Undervolt
4.) Set on Boot
final step: Delete Unused App
Extra Section
Coming Soon
End Of My Post
LtHuNTer_StepheN said:
Don't use any tweaks:
tweaks make your phone fast but less stable
and don't use xloud and mobile bravia
they are fake
Click to expand...
Click to collapse
+1 10char..
I agree with other settings, but would you mind explaining why VM heap size is 48? I've read that 32 is better in the FAQ thread of minicm7, and 2048 sd cache cause hiccups while playing music in lower class sd cards, if you can, try to edit some things for lower class cards and higher class cards, for lower class cards 128 sd cache is better and doesnt cause hiccups, just a suggestion . On the other hand, I will try your CPU settings, the smartass v2 settings with min 248mhz and 691mhz, 691mhz is indeed the most stable for nAa kernel. BTW I use tweaks without any stability issues, supercharger v8 and sometimes ram manager pro.
This is the thread that I have read:
forum.xda-developers.com/showthread.php?p=17648469
hixvolnutt said:
I agree with other settings, but would you mind explaining why VM heap size is 48? I've read that 32 is better in the FAQ thread of minicm7, and 2048 sd cache cause hiccups while playing music in lower class sd cards, if you can, try to edit some things for lower class cards and higher class cards, for lower class cards 128 sd cache is better and doesnt cause hiccups, just a suggestion . On the other hand, I will try your CPU settings, the smartass v2 settings with min 248mhz and 691mhz, 691mhz is indeed the most stable for nAa kernel. BTW I use tweaks without any stability issues, supercharger v8 and sometimes ram manager pro.
This is the thread that I have read:
forum.xda-developers.com/showthread.php?p=17648469
Click to expand...
Click to collapse
For Perfomance it's better set 48mb
this help app memory management
this heap size is usefull for HD games
Oh i forgot
i will edit it
for that tweak is already tested
what i say is
Code:
build.prop tweak
mobile bravia engine
and useless tweak
for that tweak it may increase stability
i will edit so people understand
Post Updated
Thanks
Is there any way to fix compass?the compass is somehow inverse
for auto brightness setting, how many level are you using? Ultra brightness enable or not?
Sorry, but screen cutting still exist even with bootanim enabled..especialy when in recovery..
Btw nice thread...^^v
Sent from my E15i using Tapatalk
Post Updated
LtHuNTer_StepheN said:
Post Updated
Click to expand...
Click to collapse
Oops, i'm still using nAa 08...maybe because of that...0_x
Sent from my E15i using Tapatalk
bayumahendra24 said:
Sorry, but screen cutting still exist even with bootanim enabled..especialy when in recovery..
Btw nice thread...^^v
Sent from my E15i using Tapatalk
Click to expand...
Click to collapse
i think screen cut happen with smartass v2
D E V I L said:
i think screen cut happen with smartass v2
Click to expand...
Click to collapse
Flash the new nAa-08b kerner. This fix the problem
Hi!! I have just one question. The tethering wifi always disconnects when screen turns off. I tried wi-fi settings, advanced, never sleep but does not work. Do you have other solutions? Thanks
still score highly!!!
plus avent updated kernel and rarely get screen cuts!!
so id say great rom plus kernel!!
flegga92 said:
Flash the new nAa-08b kerner. This fix the problem
Click to expand...
Click to collapse
Still using nAa 08 (havent change kernel because what i see on the changelog, the difference between nAa 08 and 08b only the screen cuts fix) with:
- Cpu freq 19-600mhz
- smartassv2 on
- undervolt on
- bootanimation enabled
No more screen cuts since my prev post.
Screen cuts SOMETIMES only appear when i'm in cwm req...thats good enough for me..
For the video lag fix,does it work with other rom which have the same problem?flash with xrec or cwm?
Hello to everyone and excuse me if my question is probably going to be dumb (for sure it's an OT so please forgive me about that) but I'm quite clueless about the issue I'm experiencing and I hope to find an advice here.
I own and X10 mini with MiniCM 2.1.6 and 2.6.29.6-nAa-08 kernel. Everyhing's fine, really a great piece of work that has put new life into my beloved X10 Mini but I'm experiencing the 'screen cut' issue that's discussed here too: it happens only with some apps (Labyrinth for example) but it happens and I'd like to get rid of this.
I don't know if it could be an issue related to the apps not being designed for Gingerbread but I don't think so because I expect something different should this be the case.
I've read that the kernel nAa-08b is intended to solve this issue but it seems (maybe I'm wrong) that it isn't suitable for my X10 mini (I've made some digging around and the latest kernel version for my mini seems the one that I've already installed while the 08b seems to be intended for the X8). I'm sure that the reply is already around here but I couldn't succeed in finding it though I've read a lot (really a lot!) of posts here and there, especially on the official thread:
http://forum.xda-developers.com/showthread.php?t=1068553
where unfortunately I couldn't post because I'm a new member with less than ten posts. Some advices? Thanks anyway!
very good guide
thanks you very mach!
post updated
sorry im busy lately
Hi Guys,
Thought I'd start a little thread for people to share their tweaks and tips so that others can enjoy too
Since I'm new to the Dell Streak, this would benifit me as well.
My Tweaks & Tips:
Boot Animation:
ICS Boot Animation Landscape (Full Screen Boot)
http://forum.xda-developers.com/showthread.php?t=1459717
Just edit the 'desc.txt' file to '800 480 24p 0 0 part0'
Apps:
-Rotation Locker (force landscape/portrait for all apps)
-Startup Manager (disable startup apps to save memory)
-Battery Defender (wifi off when screen turns off, bypass reboot bug! **WiFi Policy Bug**)
-Ram Manager Pro (great memory management app) ~50MB more
-System Cleanup (move apps from /data/app to/from /system/app/)
-Rescan Media (turn off media scanning service, to increase boot time)
Tweaks:
-Increase SD Cache (Speedup SD Write/Read Speeds) *Can be done by app*
Game Compatibility Tweak(Build.prop)
Change the build.prop brand & model :
ro.product.model=HTC Vision
ro.product.brand=HTC
ro.product.manufacturer=HTC
Signal Boost Tweak:
Follow djscopesofm's guide here:
http://forum.xda-developers.com/showthread.php?t=924440
Build.prop Tweaks:
**Make sure to Backup Nandroid before playing with Build.prop**
( I broke the WiFi connectivity while playing with some unknown settings, had to nandroid restore and test over and over again. )
#Signal Boost
ro.ril.enable.dtm=1
ro.ril.gprsclass=10
ro.ril.hep=0
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.enable.a53=1
net.dns1=8.8.8.8
net.dns2=8.8.4.4
# Force launcher into memory
ro.HOME_APP_ADJ=1
#WiFi Scan to 3mins
wifi.supplicant_scan_interval=180
#Increase Touch Responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Net speed tweaks, choose what you need
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wimax = 4096,221184,524288,4096,16384,110208
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
The Following Tweaks causes instability on certain roms/builds. (Make sure to backup before changing settings to test)
**Broke my DHCP on WiFi**
# Allow power collapse, increases battery life
ro.ril.disable.power.collapse=0
# Puts the CPU into deep sleep but preserves registers
pm.sleep_mode=1
# When moving through zones or losing signal, having a delay
# smooths out constant disconnects and reconnects, saves battery life
ro.mot.eri.losalert.delay=1000
#To disable USB debugging popup
persist.adb.notify=0
#Disable error checking
ro.kernel.android.checkjni=0
#Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
#Decrease dialing out delay
ro.telephony.call_ring.delay=0
#Raise photo and video recording quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
#camera/video
ro.camcorder.videoModes=true
ro.media.capture.maxres=5m
#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
#Disable Boot Animation
debug.sf.nobootanimation=0
Click to expand...
Click to collapse
Fixes:
-change build.prop to HTC Vision/Google Nexus One for apps compatibility. (Games mostly)
-Delete Rogers's APN (isp.apn) to enable WiFi Tethering **Rogers AT&T Network related**
I will continue to keep adding to this list as I keep playing with my Streak.
Hope you guys share some tips with me too!
ROM
Official Olleh 407, thanks to http://www.streaksmart.com/ for the heads-up and to the Manii for the manual and support.
Set ro.secure=0 in default.prop by flashing a boot.img from GingerStreak 2.4
Cleanup
Used adb to delete unwanted apps:
Removed all Olleh market apps
Removed Lota, Logservice and Logmaster2 (both apk and odex files)
Removed Accuweather and ZinioReader
Tweaks
Installed free ADWLauncher from the market, replacing Dell Stage UI
Locked main screen to portrait
Custom Bootanimation
Removed the camera_click.ogg file from system/media/audio/ui
Custom /etc/hosts file sending advertising sites to 127.0.0.1
Dr Doppio said:
ROM
Set ro.secure=0 in default.prop by flashing a boot.img from GingerStreak 2.4
Click to expand...
Click to collapse
whats this sposed to do mate?
ro.secure is already set to 0 in all custom kernels.
I'm pretty sure you cant change it once the device has booted up, you need to modify the kernel (or rather it's ramdisk) and reflash.
crashDebug said:
whats this sposed to do mate?
Click to expand...
Click to collapse
Gives you root rights from adb without installing superuser and busybox. My approach may not be the proper way to achieve this, see below.
TheManii said:
ro.secure is already set to 0 in all custom kernels.
Click to expand...
Click to collapse
Yes, but I had flashed the official Olleh ROM, since that was the first time I was changing ROM and I wanted to be on the safe(r) side. I would now recommend to other noobs such as myself to go for a streamlined ROM, but then I didn't know better.
I'm pretty sure you cant change it once the device has booted up, you need to modify the kernel (or rather it's ramdisk) and reflash.
Click to expand...
Click to collapse
As far as I figured, changing dafault.prop required unpacking the bootimg, editing the file, repacking the image and flashing it back. I took a riskier shortcut to extract a bootimg from a different ROM that I assumed was pre-rooted and likely to have ro.secure=0. It was a stupid thing to do, but it luckily worked, and all it took was three lines with fastboot. I may add that the contents of the file changed a few times after reboots, and I noticed a file with ro.secure=1, ro.debuggable=1 at some point. I've also found in the file /firstboot/permissionadb.err a line "date time <adb>: permission secure=1", supposedly logging an error that I had caused by fooling around...
official olleh 407 installed + deodexed + language pack + portrait hack by themanii + superuser (rooted) + MattedbBlues theme + GoLauncher EX.
-tweaks
-using handcent sms (with darkness skin) for simple solution to everride the convertion from sms to mms
-i consider a tweak that i don't have any memory manager or things like that, i just use the applications i need and if something bothers me, i just freeze it using titanium backup.
-for end call freeze problem, i just use the option from settings>accesibility>power button ends call, solves that problem and i think is more "accesible".
-everything runs smooth, almost no problems i would say, but i noticed some problems, wifi tends to "lag" when using instant messaging applications, i know that this is a known bug, but works pretty ok otherwise, also i use Wifi Static for almost any wireless network i connect to.
-another problem i have noticed is that sometimes it just doesn't want to send SMS's, it just gives me a undelivered notification, and i resend it again, i also noticed that the sms is sent, but not entirely, so when this happens, if i resend it 4 times, that person recieves 3 incomplete messages and finally the complete one, also, this is a farly rare bug.
hope this helps!
Added new tweaks.
We thank you very much for your time in order to have the best settings in our phones...Is it possible to change the wifi settings in order to see channels 12-14 at 2.2.2 official android?
these are pretty 407/olleh related, and I confirm they are working in this rom ONLY.
here goes
ro.build.CUSTOMER_CONFIG_KT=0
to disable the sms/mms conversion in the stock messaging app.
note that there also is a line like this
ro.build.CONFIG_CUSTOMER_KT
which I have no idea what it does (but set it to 0 anyway)
ro.build.FEATURE.SHUTTERSOUND=0
set to 0 to show the shutter option in the camera app (note: this option alone does NOT disable the shutter sound, it just shows the option in the app!)
ro.build.OEM_PRESET_APN_LOCK=1
ro.build.OEM_PRESET_APN_HIDE=1
grants the ability to disable and delete preset APNs from Wireless Settings. They are locked in 407
debug.composition.type=gpu
to enable the "CRT off" animation which is disabled by default.
these are not all my findings, thanks to the original discoverers!
-----NEW FIX
I had a problem for some time now with long sms's, not the mms to sms convertion, solved it with handcent sms, but the phone would simply not send bigger than 3-4x160 sms's.
Code:
-put your mobile phone to GSM only mode, at mobile networks settings.
(this problem seems to be solved for now, hope this helps...)
Ya'll have covered just about everything I already do. One quick easy littke thing I found helpful is GPS Status & Toolbox for keeping the GPS and compass in line. Letting the app update AGPS data daily helps GPS lock time and there is a compass calibration app that I need to use regurely.
I'm not sure if other gb roms have it but in dsc 0.72 I stumbled upon the option to set up peak and non peak hours and shut data off after a set amount of time, if anyone's interested here's how to get to it
settings>wireless and networks>mobile networks>schedule data connection
with the non peak hours set up for when i'm asleep and peak to 15 minutes I'm able to get close to two and half days on a single charge with a few 5 minute phone calls and ~400 texts sent per day
Edit:
Setting this up WILL prevent all apps that rely on syncing while the phone is asleep from syncing, it's not much of an issue for me but to those who rely on apps syncing while the phone is asleep should be advised to set up non peak hours data shut off only.
[FIX] Wallstreak app - to center my 800 x 480 wallpapers perfectly
[TIP] Gingerstreak - 2.4.4 Rom with DSC-Team-Phoenix kernel , works flawless
[TIP] A Touch of ICS theme - to give it a nice black and blue look
[FIX] Widgetlocker - to bypass the default lock screen and make it a bit more usefull
[TIP] Extended controls - when the default power controll app is just a bit to limited for your taste
[FIX] Opera Mobile - a bug that my streak has is a browser that takes forever to load, Opera mobile solves this
[TIP] Streakled - a nice app that uses the Streaks led lights to notify you when youve received a e-mail or text message
simonbuschers said:
...
[FIX] Opera Mobile - a bug that my streak has is a browser that takes forever to load, Opera mobile solves this
...
Click to expand...
Click to collapse
I have noticed that cleaning up the cache changes browser load times immensely, from almost instanteneous after clean up to close to 1 minute after a couple of weeks without one. Other than that, I love desktop Opera, but haven't used the mobile version yet...
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
WARNINGI 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