Related
Alright...so i wanna see what else is working for other ppl.... Like many others im sure u like ur devices quick and snappy....
Ive noticed that disabling surface dithering helps performance for me.....
With Compcache my home screen doesnt have to reload as much when i go back to it from an app.
I have Jit enabled....still cant decide if it hurts or helps.....anybody else?
I left the vm heap size at 16 (stock) ....im guessing its virtual memory but havent tested different settings...
In ADW launcher I have it set up for 4 screens cuz i dont really need anymore...
I set the Desktop scrolling and overshoot both to 0 and have disabled scrollable widget support, and also disabled the Animated drawer effect and the Fade App Labels.
I have the screen cache and system persistent enabled.
I know the adw launcher settings might not be real performance...but it does make the homescreen and app drawer feel much quicker.
What else do you guys use? Whats working for u?
Avoid froyo2sd like the plague.
There are good things about it, but its implementation is riddled with memory and cpu consumption. We need to kill all 8 trillion redundant mounts and all the encryption to make it viable.... that and get the dalvik cache and home directories onto the sdcard with the apk.
guess ill be moving the apps back to the phone to test out performance....thanx
CM6 has been one of the fastest roms I've ever flashed. Here's my current settings:
I've always used compcache so I'm not sure if it helps performance or not anymore.
VM heap size as I understand it from a few google searches is related to the amount of ram dedicated/allocated to/per background process(es). I currently have mine a 12mb with no weird side effects.
The argument for jit is that it makes opening apps a little slower but it helps out with intensive apps like maps and browser. I have it on and my dialer still opens within 2 seconds, and browser seems better so idk.
ADW with 0 scrolling speed looks ugly and jerky =p I usually stick within 300-400, using only three screens, no dockbar, no nexus dots, sliding top paginator, no drawer animation, no status bar (you can swipe up/down and it shows up anyway), no background on the lab/rab/launcher,no scrollable widgets, screen cache, etc. I only use the calendar, powercontrol, and 4*4 music widget and a handful of icons. I find those settings to be smooth as butter.
I also turned off autorrotation except for 180*, I always find it annoying when I have my phone in my lap or I'm laying down watching tv and it rotates on me, and sometimes it's more comfortable to hold the phone upside down (I also use it when i listen to music so the headphones are on top). Also 3D gallery has no rotate bugs for me....
Yeah those settings haven't failed me yet. I haven't even gotten around to overclocking since its so good and speedy.
I noticed a huge difference when I swapped from adwlauncher to launcherpro, launcherpro just seems a lot faster and smoother then adw. I'm also running compcache and jit, overclocked to 610mhz. I'm getting linpack scores of.4.25 MFLOPS, quadrant scores of 370 and neocore scores of 21FPS(sound) and 24.1FPS(no sound). My phone is definitely running faster then it ever has..now the real test is mastering swype...
Sent from my HTC Dream using XDA App
how did U overclock to 610
chrisgto4 said:
how did U overclock to 610
Click to expand...
Click to collapse
same question. what kernal did you use to overclock above 576? when you used a different kernal, did it break wifi or anything?
my experience:
I left OC at 576,
turned off dithering
turned compcache on
turned jit on, and reboot
no swap, but type free in terminal to make sure compcache is working.
go into normal phone settings > display > turned off all animations
go into ADW settings and turned off animations, turned desktop scrolling speed to as fast as possible, turned off animated drawer, make sure system persistent is checked, and just made sure all scrolling speeds are set to as fast as possible with no animations or fades.
for me this thing is flying. as fast as any donut I ever flashed and way faster then any 2.1. with the above settings, im constantly getting a little over 4 mflops.
no lag, and only once in a while will it reload the launcher when returning to home. if i enable swap it may never do it
get a random FC every one in a while (not often at all) but no big deal.
just wanted to share what i did and my experience so far
still wondering if anyone has OC past 576 and with what kernal. if so, what any problems? or battery life issues?
I really don't suggest a bigger OC then 576 unless you have a big battery....
My findings are each Mhz of overclock drives down battery 2%. My phone overclocks steady at 691 w/ no reboot but battery doesn't live more then a few hours. I haven't even used set cpu yet since I feel the rom is fast enough.
Oh and linpack results don't really matter at all.... Your phone does not often have to perform loads of math and java calculations...
mejorguille said:
I really don't suggest a bigger OC then 576 unless you have a big battery....
My findings are each Mhz of overclock drives down battery 2%. My phone overclocks steady at 691 w/ no reboot but battery doesn't live more then a few hours. I haven't even used set cpu yet since I feel the rom is fast enough.
Oh and linpack results don't really matter at all.... Your hpone does not often have to preform loads of math and java calculations...
Click to expand...
Click to collapse
ok thanks.
i know you said you have not used set cpu yet, but I think CM6 is overclocked to 576 automatically upon flashing the rom
at least when i hit autodetect, it detected 576 and 122
I hate all you people.
CM6 runs HORRIBLY slow for me. Tried every speed tip I can do - it's just unreasonably slow. Yes, I wiped before I flashed, even redownloaded CM6 and have latest gapps. Is anyone else experiencing this? I'm talking about so slow I can't get to my homescreen from an app in less than 30 seconds.
r3s-rt said:
I hate all you people.
CM6 runs HORRIBLY slow for me. Tried every speed tip I can do - it's just unreasonably slow. Yes, I wiped before I flashed, even redownloaded CM6 and have latest gapps. Is anyone else experiencing this? I'm talking about so slow I can't get to my homescreen from an app in less than 30 seconds.
Click to expand...
Click to collapse
im on mytouch 32b also. sorry to hear about your really bad experience.
i know you tried everything, but you could always re-wipe everything, flash rom, flash gaps 3 then try all the tweaks I posted in this thread on previous page
r3s-rt said:
I hate all you people.
CM6 runs HORRIBLY slow for me. Tried every speed tip I can do - it's just unreasonably slow. Yes, I wiped before I flashed, even redownloaded CM6 and have latest gapps. Is anyone else experiencing this? I'm talking about so slow I can't get to my homescreen from an app in less than 30 seconds.
Click to expand...
Click to collapse
Try checking persistant home in ADW settings
r3s-rt said:
I hate all you people.
CM6 runs HORRIBLY slow for me. Tried every speed tip I can do - it's just unreasonably slow. Yes, I wiped before I flashed, even redownloaded CM6 and have latest gapps. Is anyone else experiencing this? I'm talking about so slow I can't get to my homescreen from an app in less than 30 seconds.
Click to expand...
Click to collapse
do the persistant thing in adw it keeps launcher in memory after that rare home reloads use set cpu and oc to 576 and a528 thats what i have and i would suggest doing fix_permissions through terminal just did that it took like 3 min but damn its freaking fast now and i was about to get rid of cm6 cause it was starting to run sluggish
I've been using: compcache on, JIT on, dithering off (which was a big one), and VM size set to 16. Also I ditched ADW for LauncherPro and CM6 is no slower than CM5 was for me, if anything its faster. I'm loving that my G1 boots twice as fast on CM6
kboater said:
same question. what kernal did you use to overclock above 576? when you used a different kernal, did it break wifi or anything?
Click to expand...
Click to collapse
I used dumfuqs 610 kernel to OC it runs fine with wifi. I agree it strains the battery but I'm not overly fussed over battery life.
Sent from my HTC Dream using XDA App
ftruck90 said:
I used dumfuqs 610 kernel to OC it runs fine with wifi. I agree it strains the battery but I'm not overly fussed over battery life.
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
it was either the 710 or 614......
gringo69 said:
it was either the 710 or 614......
Click to expand...
Click to collapse
Hahaha **** at time of writing I must of been confused too I meant the 614 .
kboater said:
im on mytouch 32b also. sorry to hear about your really bad experience.
i know you tried everything, but you could always re-wipe everything, flash rom, flash gaps 3 then try all the tweaks I posted in this thread on previous page
Click to expand...
Click to collapse
mejorguille said:
Try checking persistant home in ADW settings
Click to expand...
Click to collapse
skater4690 said:
do the persistant thing in adw it keeps launcher in memory after that rare home reloads use set cpu and oc to 576 and a528 thats what i have and i would suggest doing fix_permissions through terminal just did that it took like 3 min but damn its freaking fast now and i was about to get rid of cm6 cause it was starting to run sluggish
Click to expand...
Click to collapse
Done it all. :/ When I mean horribly laggy, I mean that I would miss a phone call before the phone got off of the lockscreen to accept it. :/
I'm persistent, though, and tried again today. For some reason everything seems to be running like it should now. Time to finally get to try these speed tips. =]
Dialer
anyone else having problems with being able to answer calls? the slider doesnt show at all
ive tried:
kanging the Phone.apk from the LFD froyo
&
installing the Phone.apk from the Cytown thread none which have worked and yes ive flashed, wiped and done everything correctly
I just want to know if anyone else is running this script. I refused to believe my Nexus S was not behaving, after all, it's a Nexus S! But, eventually even I had to get real. Truth is, lately, no matter what ROM I'm running after a few days things would slow down way too much. Lag, Launcher redraws, FCs due to lag. Things were too slow.
Anyway, I used the V6 SuperCharger script and it really has changed things. I used the MegaRAM option for 512 MB phones and I swear it has been a revelation. Even overclocking couldn't bring about this change. Currently, I'm on MIUI which most people consider to be a bit heavy and clunky. However, after supercharging with the MegaRAM option and Bulletproofing the launcher it's unstoppable! Highly recommended for those of you experiencing phone lag. Make sure to follow the Dev's instructions for using his script. All credit to user: zeppelinrox. Amazing stuff!
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
I used the 2nd MegaRAM option as well. But, I'm going to test out the first option. As I understand it, the more memory you want free in the 3rd slot the less multi tasking you can do (as this is where the secondary apps will be places)...I THINK!
As per that thread if 25 MB is good enough on a Milestone, a Nexus S should do well with 40 MB.
THIS from the thread:
zeppelinrox said:
Additional Info: You can find each app's priority and OOM.
....................... In AMM, Press Menu > Running Processes > Group by OOM grouping.
....................... Expand each group and see what apps are included and each app's priority level. (Higher numbers get killed first!)
....................... If you tap on an app, you can get additional info. Tip: Check and see what's included with android.process.acore
The default minfree values ("kill thresholds") for each OOM group are, as far as I can tell: 6, 8, 16, 20, 22 and 24 mb. (CyanogenMod 6.1.2)
This means that: when free memory lowers to 24 mb, EMPTY_APPS get killed; at 22 mb free ram, CONTENT_PROVIDER apps get killed; and so on...
Now, because the Milestone has only 256 mb of memory, I found these numbers too low, especially the 3rd one.
Basically, with those settings, you will usually be sitting with only 20 - 25 mb of ram.
Possibly less. Basically, it's the 3rd number (16) + 5. That's your free memory.
And my phone just chokes when it has that little ram available. Lag, home screen redrawing, the launcher getting killed.... ugh....
After extensive fiddling around, I've come to the conclusion that setting the third slot to about 25mb works great.
No home screen redraws while not being too aggressive on secondary/background apps while having about 30-35mb free all the time
BTW, free ram is not wasted. Android will use that memory to cache the file system and this speeds things up. See this informative post.
Click to expand...
Click to collapse
Si_NZ said:
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
Click to expand...
Click to collapse
Just tested the 1st MegaRAM option and things are quite smooth. Launcher is not as buttery as with the 2nd option but, it's still great. The browser does quite well too, pinch to zoom is smooth but, scrolling is a little stuttery on a heavy page like Engadget's.
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
never heard of this till this morning, thanks for bringing it up
trying it out now
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
I love it when a tweaker tells tweakers not to tweak.
Really!
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
you should know that two scripts running can cause issues......
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
I didn't said anything against your script, just told the users to not use it on my custom ROM. A think that as maker of your script you should know - two RAM scripts on same ROM are doing only damage.
They don't stay running.
They execute and end.
Whichever one runs last is the one that sticks.
Many people were using juwe's script with the V6 script and things ran fine so it's not a big deal.
Of course, if somebody wanted to, they can delete the minfrees in any of their custom roms and plug them into supercharger...
Why do you guys like scaring the crap out of people for nothing? lol
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
Great to hear from you. Haha. Just about to ask you
does it work well with cm7?
mohsin125 said:
does it work well with cm7?
Click to expand...
Click to collapse
I'm running it on cm7, and my phone seemed to be a bit snappier
time will tell though
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
rican408 said:
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
Click to expand...
Click to collapse
use this guide, and it will be easier than you could imagine
http://forum.xda-developers.com/showthread.php?t=1126940
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Haizum74 said:
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Click to expand...
Click to collapse
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Just an update on my settings. The MegaRAM seem to really speed everything up but, I find that they weren't being nice to my Whatsapp (I was missing messages now and then) I think Whatsapp would receive the message but get immediately killed before it could broadcast the notification. Once it even seemed to exit in app for no reason at all. So I switched to Balanced Settings 3 and so far Whatsapp as well as the launcher and phone in general has been very responsive.
Sent from my Google Nexus S using XDA App
deejaylobo said:
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
I went for Megaram option 1 (I think). I disabled password and it then worked but by this time I had uninstalled the script. Any particular option you suggest? Cheers for the reply too.
It depends on your usage. I would suggest starting out with Balanced settings 3 and moving up or down the menu depending on whether you want more(down) or less speed(up). I've found that the trade off is speed vs multitasking. Though, I think zeppelinrox could confirm whether I'm right.
i am running cm7 nightly 44 on my DX and ive installed the v6 surpercharger with awesome results, when i tried out the 3g turbocharger, and kernel tweaks, i reboot like SM says and when i do, i get no data no cell signal wifi wont work, and airplane mode wont toggle. ive tried a few times with the same results. Ive searched and found nothing specific to my setup either. what am i doing wrong? any help would be appreciated! thanks!
You probably have 2.3.4 and its made for 2.3.3.
Sent from my DROIDX using XDA App
Actually I'm on 2.3.5 so that explains it too
It's weird... on the same phone wifi will be fine with stock but not okay with a custom rom.
Android version doesn't matter.
But 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
Ill try the update ill let you know. Thanks.
Or how would I implement that? Editing the build.prop?
yes.. if you have update 2 applied it only involved changing 2 entries
I applied both tweaks and edited the build.prop with the new values you suggested and with 34 I got no 3g no cell signal airplane wouldn't toggle and error when turning on wifi. I then tried 32 and no 3g no cell signal and error for wifi but airplane would toggle then.
ok.. 34 is out of the equation...
At 32 its the same as before
Well I wonder what's not working then I apply the kernal tweaks first then 3g Turbo then reboot. All with script manager
Does the baseband matter?
Does the 3g turbocharge work on all android devices or strictly the DX? I want to do this on my Evo 4g, but the process seems a bit over my head.
Is the increased 3g speed attributed to ONLY the changed values in the build.prob? If so, can this be done manually by editing build.prop with a text editor, to achieve the same results?
Evo! said:
Does the 3g turbocharge work on all android devices or strictly the DX? I want to do this on my Evo 4g, but the process seems a bit over my head.
Is the increased 3g speed attributed to ONLY the changed values in the build.prob? If so, can this be done manually by editing build.prop with a text editor, to achieve the same results?
Click to expand...
Click to collapse
I don't know about all android devices, but I have an EVO 4g, and it seems to work fine for me. Still messing with it cause i think the 98kickasskerneltweak isn't working, but I'm working on that now
Dramanis420 said:
I don't know about all android devices, but I have an EVO 4g, and it seems to work fine for me. Still messing with it cause i think the 98kickasskerneltweak isn't working, but I'm working on that now
Click to expand...
Click to collapse
Me too...
FYI...
Updated September 3: - V6 SuperCharger Update9 Beta3
Fixed - Cleaning of local.prop. It was leaving a mess behind.
Enhanced - User notification of events a little more
Updated September 3: - 98KickAssKernelTweaksInstallerUpdate3 test3
Fixed - A big error (I doubt the io scheduling tweaks were being applied in Update 3 test 2)
Improved - Application of io scheduling tweaks so that it is much more selective and safer
Runs - 98kickasskernel after creating 98kickasskernel!
Notifies - You of the I/O Scheduler in use - Before AND After running 98kickasskernel
Defaults - To using Deadline (of available) instead of Noop io schedular.
Updated September 3: - 3GTurboChargerInstallerUpdate3 test 9
Added - Complete menu with 4 configurations!
Installs - /sdcard/3GTurboCharger.txt which has specific details of the 4 options.
This is what it looks like:
Code:
================================================
\\\\ 3 G T U R B O C H A R G E R - M E N U ////
==============================================
1. Fast?
2. Faster?
3. Fastest?
4. Experimental!
5. UnTurboCharger
6. REBOOT! (WARNING - There is NO Warning!)
7. Exit
Your Mileage WILL Vary!
View settings in /sdcard/3GTurboCharger.txt!
Test all 4 to see which works best for you!
The SpeedTest.Net app is highly recommended :)
Please enter option [1 - 7]:
Download from the usual place http://forum.xda-developers.com/showpost.php?p=15948434&postcount=1127
All 4 updated files are 100% untested by me... so good luck
How much speed increase does this actually help
Sent from my DROIDX using xda premium
Ok a couple of more updates... on account of me being a n00b
Updated September 4: - 98KickAssKernelTweaksInstallerUpdate3 test4
Tweaked - io scheduling tweaks some more so that it is even more selective and safer
Updated September 4: - 3GTurboChargerInstallerUpdate3 test 10
Fixed - Yesterday's file (Update 3 test9) didn't apply ANY variations so now it's fixed.
Added - Another configuration. Some people reported great results with yesterday's version (removes limits?) so added a "nulled" configuration.
what does 98KickAssKernelTweaks do?
Thank to Workshed for finding the errors!
Universal Script for Android Phone No more RING lag phone rings by the 2nd ring and screen and caller ID pops right up.
There are a few vers to test I am uploading my ver of it now it has a few tweaks removed for the CPU and kernals. But added a few thats it works much better now and it will get along with other Twaeks like supercharger.
All Zips from this post are flashable from recovery.
Here is the link to the OP I found it on. http://forum.xda-developers.com/showthread.php?t=1205259
This Is VER 2 there where errors in the 1st ver and also on the OP that i found this on.
I patched it up and also tested it and the file is running great without any errors as far as I can see.
By the end of the 2nd ring the phone lights right up with caller ID and rings even with custom ringtone. The dialer when placing a call is so much faster when it opens it just POPS.
#!/system/bin/sh
#00Ring_lag_v2 computerfreek#
MAX_PHONE() # remove lag when answering phone calls
pidphone=`pidof com.android.phone`;
if [ $pidphone ];
then
echo -17 > /proc/$pidphone/oom_adj; # exclude com.android.phone from oom-killer;
renice -20 $pidphone; # set highest nice level for com.android.phone;
log -p i -t ScreenState "*** MAX phone *** set oom_adj(-17) and nice(-20) for com.android.phone";
exit;
else
sleep 1;
MAX_PHONE;
# Background process to check screen state;
(while [ 1 ];
do
cat /sys/power/wait_for_fb_wake;
AWAKE_MODE;
cat /sys/power/wait_for_fb_sleep;
SLEEP_MODE;
then
# One-time process to optimize com.android.phone;
(while [ 1 ];
sleep 10;
MAX_PHONE;
; \ fi
Click to expand...
Click to collapse
Here is the Links
http://dl.dropbox.com/u/17779317/New%20folder/00Ring_Lag_v2.sh
http://dl.dropbox.com/u/17779317/00Ring_Lag_v2 Raw TEXT to place in a file and add it to your init.d folder.
http://dl.dropbox.com/u/17779317/ringlagv2/00ring_lag_v2.zip Flashable Ver 2
If you are runing the v4.0 of worksheds GSB then here is a Patch that will replace the One on ROM with V2 http://dl.dropbox.com/u/17779317/ringlagv2/00ring_lag_v2_GSB_patch.zip
computerfreek said:
OH that sucks ! Download prankdial from market and prank your self! lol it will call you.
If you pm me your number and I can call you from my gv.
Hows the phone runing with other things after adding the script?
Click to expand...
Click to collapse
Sorry to jump threads on you, I didn't want to clog up CondemnedSoul's thread with questions/comments specifically about this script....
After loading & rebooting, I didn't notice any problems. The phone seems a bit snappier with this in general, although I still haven't tested the incoming calls thoroughly yet. I am running this script on Comndemned v17 S2h in combination with the v6 SuperCharger, and the 3G & Kernel Tweaks. Based on a recommendation from CS, I also modified the following line in the build.prop from
ro.telephony.call_ring.delay=500
to
ro.telephony.call_ring.delay=0
I haven't noticed any conflicts or issues yet, but I wouldn't necessarily classify myself as a heavy user.
I have another question for you. Since it was easy enough to modify the CPU speed, if I change the governor in the following line
GOVERNOR_SCALE="ondemand";
to smartass so that it will match my CM7 performance settings, will that cause any issues? Does this script need to be set to ondemand in order to work correctly?
computerfreek said:
I found this Universal Script for Android Phone it just ROCKS I am testing it on GSB3.8 workshed and now when I call my cell it starts ringing after just 1 ring! I tested it on Gin-sen-tazz but I don't think it is working on GINGER SENSE ROMS
Here is the link to the fourm I found it on. http://forum.xda-developers.com/showthread.php?t=1205259
The only thing I changed on the it was the MAX CPU from 800 to 710 and it all seems to be working great. I will see in a few hours after leting the phone sit and then calling it.
Hope this will help Others on CM7 GB roms.
Here is the one I am useed on my phone. http://dl.dropbox.com/u/17779317/00tweaks
Click to expand...
Click to collapse
So all you have to do is copy 00tweaks and put it in your init.d folder???
PillClinton said:
Sorry to jump threads on you, I didn't want to clog up CondemnedSoul's thread with questions/comments specifically about this script....
After loading & rebooting, I didn't notice any problems. The phone seems a bit snappier with this in general, although I still haven't tested the incoming calls thoroughly yet. I am running this script on Comndemned v17 S2h in combination with the v6 SuperCharger, and the 3G & Kernel Tweaks. Based on a recommendation from CS, I also modified the following line in the build.prop from
ro.telephony.call_ring.delay=500
to
ro.telephony.call_ring.delay=0
I haven't noticed any conflicts or issues yet, but I wouldn't necessarily classify myself as a heavy user.
I have another question for you. Since it was easy enough to modify the CPU speed, if I change the governor in the following line
GOVERNOR_SCALE="ondemand";
to smartass so that it will match my CM7 performance settings, will that cause any issues? Does this script need to be set to ondemand in order to work correctly?
Click to expand...
Click to collapse
That shouldn't cause any issues at all. It should just default your governor to smartass instead of ondemand.
CondemnedSoul said:
That shouldn't cause any issues at all. It should just default your governor to smartass instead of ondemand.
Click to expand...
Click to collapse
Done, & no issues to report yet. I also changed
GOVERNOR_FREQENCY_MIN="245760"; to GOVERNOR_FREQENCY_MIN="480000"; for the purpose of matching my CM7 settings.
bigdaddyblues said:
So all you have to do is copy 00tweaks and put it in your init.d folder???
Click to expand...
Click to collapse
Well you chave to copy and set the permissions.
Or use flashable ver of the 710MHZ for eris http://dl.dropbox.com/u/17779317/00tweaks.zip
PillClinton said:
Done, & no issues to report yet. I also changed
GOVERNOR_FREQENCY_MIN="245760"; to GOVERNOR_FREQENCY_MIN="480000"; for the purpose of matching my CM7 settings.
Click to expand...
Click to collapse
I don't think matching it matters so much as it is set to RUN the the CPU speed set 1 time on start up be for cm7 sets it's speed. CM7 looks like it will override it after it's booted. So even if you load the 710MHZ ver and have cm7 set at 600mhz it will drop to 600 after cm7 is fully loaded.
I think there may be a conflict between this script & zeppelin's v6 supercharger. I had 3 screen redraws today for the first time in ages. When I was using the supercharger by itself, I had no problems.
I removed the 00tweaks & rebooted for now.
Sent from my Condemned Eris
One other question about the 00tweaks. I looked through the script & noticed it has some tweaks built in for dialer one. Since I don't use dialer one, could it be modified to tweak go contacts ex instead?
Sent from my Condemned Eris
PillClinton said:
One other question about the 00tweaks. I looked through the script & noticed it has some tweaks built in for dialer one. Since I don't use dialer one, could it be modified to tweak go contacts ex instead?
Sent from my Condemned Eris
Click to expand...
Click to collapse
I was thinking the same thing I don't see why not it looks like it will work for any service app I don't know if contacts is a service or not. You can PM tazz811 on the OP. And see if you can help you with that. Link to OP If you get it working for other apps please post back here so we can all use it. http://forum.xda-developers.com/showthread.php?t=1205259
PillClinton said:
I think there may be a conflict between this script & zeppelin's v6 supercharger. I had 3 screen redraws today for the first time in ages. When I was using the supercharger by itself, I had no problems.
I removed the 00tweaks & rebooted for now.
Sent from my Condemned Eris
Click to expand...
Click to collapse
I have been testing it with and without supercharger and it seems fine for me. However it be nice if we can just make a new script for just rintone lag so there will be no conflicts at will even if your just OC with CPUboost.
I think we will see soon DEV apping just the phone LAG stuff into there ROMS. This way we can just boost or OC with any other apps or scripts.
I don't think they are playing well. I don't usually use the super charger script, but had applied multi tasker setting after a few apps were killed by system that I wanted running in background. First, I notice extremely poor battery life - some service kept the phone awake all night so it didn't fully charge. This also happened yesterday with xda app, but don't know what did it last night. Also, notice that the super charger minfree values did not stick, so the 00tweaks must over ride them at startup. I was having the background app problem before the tweaks, so I suspect that the super charger kernel tweaks conflict with the 00tweaks. Undid both for now
Sent from my ERIS using XDA App
Getting rid of the 00Tweaks seems to have solved my screen redraw issue for the moment. I was also having some issues with lag after leaving certain apps, and that is gone too.
klobkelosh said:
I don't think they are playing well. I don't usually use the super charger script, but had applied multi tasker setting after a few apps were killed by system that I wanted running in background. First, I notice extremely poor battery life - some service kept the phone awake all night so it didn't fully charge. This also happened yesterday with xda app, but don't know what did it last night. Also, notice that the super charger minfree values did not stick, so the 00tweaks must over ride them at startup. I was having the background app problem before the tweaks, so I suspect that the super charger kernel tweaks conflict with the 00tweaks. Undid both for now
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
What desktop launcher are you rinning ? I am running launcherpro plus with no redraws.
Adw stock with cm7.
Sent from my ERIS using XDA App
klobkelosh said:
Adw stock with cm7.
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Maybe it the laucher or the ROM your on mine is working great, But has also been the same with or without supercharger is I do not get redraws or any teaking. I am Runing worksheds last release 3.8 and it is working great. I never use ADW so can't tell you if it is that or not. As if I test or use a rom and it has ADW or any other lanucher on it I always add lancher pro on it and resign the rom befor I even install it.
Maybe you can talk to TAZZ811 on the like from the OP. and see if he can help use out with just the phone lag tweak with no mem or kernals tweaks. Thats what I think we need.
I am sicking with it on my phone I hate missing calls And with this tweak my phone lights right up with the caller ID and it's ringing just as the 2nd ring starts. I hope others try this out and see if they get the same thing.
It maybe as easy as just removing or #out the kernal and mem tweaks on the script.
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
klobkelosh said:
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
Click to expand...
Click to collapse
Nice, I did the same thing. I tried leaving in a few of the other tweaks to see if I notice any difference (either way). If I start running into problems again, I'll check your version out.
klobkelosh said:
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
Click to expand...
Click to collapse
Nice I was testing with that also. I hope it all works out for you with your setup. I can make a flash .zip ver of each one to make it easy for others.
Thanks for testing this out. I hope DEV's just start rolling it in there roms.
klobkelosh said:
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
Click to expand...
Click to collapse
klobkelosh, sorry for the newbie question... how do i get to the init.d folder? and i tried deleting the extension in file manager with no luck
I’ve been scouring XDA and the net for some ways to make our phones a little bit better. What I have found is that you can alter your Build.Prop to work to your advantage.
Did you know that if there is an app exclusive to the Droid X and only works for the Droid X (not withstanding hardware issues), we can change our Build.Prop from Milestone XT720 to Droid X (whatever that model number is) and get into the market and download it?
There also other “tweaks” to you Build.Prop that are beneficial in many other ways, Data strength, Video and Camera resolution, GPS lock, Power saves,…
The below is what I have been able to find, save and test for most of our builds on the Milestone XT720, but first…
Choice is something that has been fought for, relinquished, dreamt of and lost. Here in XDA we have a choice to either use on not to use. This is YOUR choice. If YOU decide to use these tweaks, any problems that arise are YOUR responsibility. Now that is out of the way, here you are.
Oh and one other thing:::::::::::Make a backup of at the very least your /system because if something goes awry while editing the Build.Prop, all you have to do is restore your /system, since that is where the Build.Prop is located.
**XT720 Users->I have not tested these on any of the MIUI builds or Fjfalcon's CM7 release (per Sebastiman -all tweaks but camera work on Fjfalcon's CM7).**
Per Fjfalcon some of these are NOT working on [ROM][KANG][2012.01.30] CyanogenMod 7.2.0 RC0 Milestone XT720
If any Devs want to use these, that is cool. Just make sure you put in your OP that they are already on there so no one duplicates them on their Build.Prop.
Motorola XT720 "Stock" Build.Props are located here (thanks to AA1973 and 3rdstring) http://forum.xda-developers.com/show....php?t=1327141
I presume most of us are using Root Explorer or something extremely similar. You just need to have Root access and able to edit the Build.Prop text. I user Root Explore so that is what these are based off.
1, Open "Root Explorer" and click the R/W
2, Go to /system/build.prop.
3, Long-presson Build.Prop and you’ll see a pop up.
4, Text Editor.
5, Type in those few line of words below into the last line of the text then save.
6. Reboot twice
Data Tweaks Increase download/upload/3G speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=0
ro.ril.hsdpa.category=8 (or 10,12,14) Still looking for more of these though.
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
For some reason XDA won't let me take out the spaces between 4096, 16384. I have edited it twice and it still shows up with the spaces on OP. Should read 4096,16384 for all 5 (default, wifi, umts, gprs and edge) with no space between 6,1 or 16384
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
POWER SAVES
Allows the phone to sleep better
ro.ril.disable.power.collapse=1
Saves power when phone is sleep
pm.sleep_mode=1
Allows your wifi to scan less, saving more battery
wifi.supplicant_scan_interval=150 or 180 (your choice)
Helps Scrolling Responsiveness
windowsmgr.max_events_per_sec=150
Increase overal touch responsivenss
Debug.performance.tuning=1
Video.accelerate.hw=1
MEDIA TWEAKS
Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
Increases quality of photo and videos
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Raises quality of JPEG images
ro.media.enc.jpeg.quality=90 or 100 (your choice)
Better camera and video taking results
camera/camcorder mods
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led ***May interfere with Xenon
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
BOOT TWEAKS
Gives your phone no boot animation
debug.sf.nobootanimation=1 ***This might freak out some people not seeing their animation and cause unnecessary battery pulls***
SYSTEM TWEAKS
Forces your home launcher into memory
ro.HOME_APP_ADJ=1
Change the Dalvik VM heap size
dalvik.vm.heapsize=64m can use 24, 32 is default, 48, 64
To disable usb debugging popup
persist.adb.notify=0
To give your phone an HD effect fitting a little more on the screen, look for this in your current build.prop and change the 240 to:
qemu.sf.lcd_density=X (225 or 230) ***This has been known to cause FC’s for the Market, so may not be a good tweak but I still put it in here just in case*** See Changelog
To stop the phone from waking up when pressing the volume key
ro.config.hwfeature_wakeupkey=0
To make the phone ring faster when dialing out
ro.telephony.call_ring.delay=800
Disable black screen issue after call
ro.lge.proximity.delay=25
mot.proximity.delay=25
Screen ppi or font density
ro.sf.lcd_density=240
THESE ARE ONES THAT I DO NOT KNOW WHAT THEY DO AND HAVE NOT TESTED
To enable the hard key lights to stay on while the screen is on and not timeout
ro.mot.buttonlight.timeout=0
Try disabling BLN if your having trouble getting this to work
To make the phone come off of the "black screen" in the middle of, or the end of phone calls when you pull the phone away from your face
mot.proximity.delay=150
**May kill the dialer**
Render UI with GPU
debug.sf.hw=1
Fix some application issues
ro.kernel.android.checkjni=0
Defrags database files
for I in \
‘find /data –iname “*.db”’
do \
sqlite3 $i ‘VACUUM; ’ ; ***This might be something for devs to look into using for something, not sure what***
Credits to the following and links to their pages.
Master&Slaves http://forum.xda-developers.com/showthread.php?t=1151608
knzo http://forum.xda-developers.com/showthread.php?t=1227269
Jokersax11 http://forum.xda-developers.com/showthread.php?t=1263768
Change/Edit log:
11/4/11:::
1-Per peshovec qemu.sf.lcd_density::: if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
2-Per Sebastiman all tweaks work on Fjfalcon's CM7 except camera ones (caused boot loop)
11/9/11:::
Took out spaces in net.tcp.buffersize as was a copy/paste issue from Word.doc to XDA.
1/6/12:::
Took out some of the Motorola XT720 ROM specific verbiage as this is being view by way more people/devices than the XT
2/1/12:::
Noted the some of these are not working on [ROM][KANG][2012.01.30] CyanogenMod 7.2.0 RC0 Milestone XT720
WOW Awesome dude! Nice work! Can't wait to test them! I wonder if there are reversals? Or probably is if I knew anything about coding lol. Great job dude looks promising. Can't believe the excitement we are still getting out of our phones lol.
LibertyMonger said:
I wonder if there are reversals?
Click to expand...
Click to collapse
Just make sure you have a back up of /system because that is where the build.prop "lives". Also I have found that when I edit them, it creates a .bak backup, but you can never fail restoring a nandroid of just the /system.
As a side note, AA1973 gave the "stock" Build.Pro for the MIUI and 3rdstring (of course) uploaded a .zip with damn near the rest of them here http://forum.xda-developers.com/showthread.php?t=1327141
Plus is you adjust a value, wirte down what the original was and if new doesn't work for you, jsut pust back in the original. This way you shoudl only have to restore /system nandroid is something screws up majorly.
Great work there!
I'd like to call attention to
Code:
Change the Dalvik VM heap size
dalvik.vm.heapsize=64m
Since we have rather limited memory, its better if we stick to a heap size of 32 (default in most roms) personally I use 24 and feel that multitasking is much better than at 32 when most apps get killed repeatedly.
That's cool. I know that when I was on Kahl's V4, mine was at 48 and never had a problem with it. Think the intervals are 24, 32, 48, 64
Edited OP with that.
look cool man, will be take time to check & test soon!
ro.media.capture.flash=led ***Might want to check with MZ or Fjfalcon on these b/c of Xenon... In tweaking the camrera and camcorder is it ok to skip this one if it is not sure?
abet1017 said:
ro.media.capture.flash=led ***Might want to check with MZ or Fjfalcon on these b/c of Xenon... In tweaking the camrera and camcorder is it ok to skip this one if it is not sure?
Click to expand...
Click to collapse
Try it out but ok to skip too. I have read that this might have something to to with the LED notifications that we have all been looking for. Will keep looking into this weekend for that part.
build.prop text files
Hey Wood, would we be able to use these build.prop tweaks? There are text files to download and place on SDCard rename them to build.prop then use root explorer to move them to /system
Woodrube said:
To give your phone an HD effect fitting a little more on the screen, look for this in your current build.prop and change the 240 to:
ro.sf.lcd_density=X (225 or 230) ***This has been known to cause FC’s for the Market, so may not be a good tweak but I still put it in here just in case***
Screen ppi or font density
ro.sf.lcd_density=240 ***This is how MZ and Peshovec fixed the tiny little Korean keyboard on CM6***
Defrags database files
for I in \
‘find /data –iname “*.db”’
do \
sqlite3 $i ‘VACUUM; ’ ; ***This might be something for MZ, Fjfalcon and Peshovec could use for something, not sure what***
Click to expand...
Click to collapse
Thanks for your hard work, i'd like to put some comments
ro.sf.lcd_density -> if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
qemu.sf.lcd_density (here there is typo for the keyboard it should be qemu.sf.lcd_density, instead of ro.sf.lcd_density)
about defraging the database, may be including as part of openrecovery is better. I don't see the point to be defraged at every start..
After applying the tweaks, headset is not working... I don't know if it is related with the tweaks..... I'm using mz cm6 rc3 rom.
By rebooting I resolve the issue......
abet1017 said:
After applying the tweaks, headset is not working... I don't know if it is related with the tweaks..... I'm using mz cm6 rc3 rom.
By rebooting I resolve the issue......
Click to expand...
Click to collapse
Cool dude! Be interested in your feedback!
abet1017 said:
By rebooting I resolve the issue......
Click to expand...
Click to collapse
Don't forget you have to reboot twice.
peshovec said:
ro.sf.lcd_density -> if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
qemu.sf.lcd_density (here there is typo for the keyboard it should be qemu.sf.lcd_density, instead of ro.sf.lcd_density).
Click to expand...
Click to collapse
I will edit OP later on when I get to PC. Thanks for re-checking the lcd.density issue too
build.prop
All tweaks work fine on fjfalcons cm7
except the camera tweaks. it causes the phone to bootloop.
sebastimau said:
All tweaks work fine on fjfalcons cm7
except the camera tweaks. it causes the phone to bootloop.
Click to expand...
Click to collapse
Excellent. Will update OP and start working on fixing the camera tweaks.
Woodrube said:
Data Tweaks Increase download/upload/3G speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=0
ro.ril.hsdpa.category=8 (or 10,12,14) Still looking for more of these though.
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
Click to expand...
Click to collapse
Hey Wood, do I type in all these commands? save after the first set? Or what do I do...?
---------- Post added at 08:47 PM ---------- Previous post was at 08:27 PM ----------
Woodrube said:
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960[/B]
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
Click to expand...
Click to collapse
You see any typo's in here? The space between 163 84,? Is that correct?
***also have you tested these on Bravo?
***I got all the tweaks saved but I think I better leave well enough alone lol. Bravo is almost perfect as is everything is running great. What do you think Brian? Should I try these?
LibertyMonger said:
Hey Wood, do I type in all these commands? save after the first set? Or what do I do...?
Click to expand...
Click to collapse
You can type them all in at the same time, but when I did it I did ti in pieces to make sure each one was taking effect and if I got looped was able to determine which one caused it problem (like typo ro something like that).
LibertyMonger said:
You see any typo's in here? The space between 163 84,? Is that correct?
***also have you tested these on Bravo?
***I got all the tweaks saved but I think I better leave well enough alone lol. Bravo is almost perfect as is everything is running great. What do you think Brian? Should I try these?
Click to expand...
Click to collapse
I'll fix that in the OP. No spaces between 163 84. Should be 16384. XDA must have remarginalized them when I put it in here. I copied them from a WORD.doc when I was compiling.
I tested the data tweaks and a few of the system tweaks on Bravo and they worked fine. But if you have everything working fine for you, I would suggest either leaving it alone or bit-piece them in there. Don't want the lightning rod effect like you had in HM's ROM.
p.s. - Sorry I didn't respond sooner, I was mostly off-line this weekend and took a few extra days off. Kind of a brain recharge thing.
anybody have descriptions of these?
A lot of these are smaller / larger than what the "change to" value is...not sure how they're going to affect things, such as--
1. why are there 6 numbers for the tcp buffer sizes
2. I don't notice any performance diff modifying the max_events_per_sec
3. Proximity Delay-- is that in ms? If I think my prox delay is "too long" when I take phone away from face, I should make this smaller, right? How small is OK?
rancur3p1c said:
anybody have descriptions of these?
A lot of these are smaller / larger than what the "change to" value is...not sure how they're going to affect things, such as--
1. why are there 6 numbers for the tcp buffer sizes
2. I don't notice any performance diff modifying the max_events_per_sec
3. Proximity Delay-- is that in ms? If I think my prox delay is "too long" when I take phone away from face, I should make this smaller, right? How small is OK?
Click to expand...
Click to collapse
What ROM are you running? That would help me answer your questions a bit more clearly.