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
Hey all,
Sorry if this has been answered/asked already, but is there a way you can prevent SetCPU from getting killed by AutoKiller? I have the autokill-profile in AutoKiller set to "Default", but the system assigns SetCPU an OOM value of 11-14, which is the highest value for getting killed (essentially regarding it as extremely non-important). How does one PERMANENTLY set SetCPU on the "Do-Not-Kill List"?
Thanks in advance.
PS: I'm running KaosFroyo v35-1 and so I can't uninstall Autokiller.
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Hungry Man said:
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Click to expand...
Click to collapse
Lol...funny stuff
As for OP you can uninstall autokiller if you want too...just look up how to remove apps through adb or terminal on phone.
Hungry Man said:
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Click to expand...
Click to collapse
why cant you just lower the oom value by clicking and holding setcpu under the processed tab and select lower oom value, it will drop it to -17, which practically means it is being ignored.
"Practically" is not what he asked for. What he asked for is a permanent solution.
tyler1524 said:
why cant you just lower the oom value by clicking and holding setcpu under the processed tab and select lower oom value, it will drop it to -17, which practically means it is being ignored.
Click to expand...
Click to collapse
That only works for about 3 minutes, until the system automatically increases the OOM value back to like 12 or 13.
I don't understand... even when I have it set to system default, after a while, it still kills it. So that means, even if I were to uninstall Autokiller, the SetCPU would still be killed after a while?
Doesnt matter if its killed. Its android, itll come right back
Nikolai2.1 said:
Doesnt matter if its killed. Its android, itll come right back
Click to expand...
Click to collapse
That's the problem. SetCPU doesn't.
Acrono said:
That's the problem. SetCPU doesn't.
Click to expand...
Click to collapse
I check my processes constanly and i dont see it going away. Maybe im wrong
Maybe Autokiller is correctly determining that SetCPU is consuming more power and Country cycles than its providing. I've certainly found that to be the case with Kaos Froyo
-------------------------------------
Sent via the XDA Tapatalk App
I'm joking about Autokiller's intuition but serious about the dubious benefits of SetCPU on an already overclocked ROM
-------------------------------------
Sent via the XDA Tapatalk App
Nikolai2.1 said:
I check my processes constanly and i dont see it going away. Maybe im wrong
Click to expand...
Click to collapse
It's always killed after 10-15 minutes, even on the default setting. If I set it to aggressive, immediately after it goes into the background, it's killed within a matter of seconds.
paulbonner said:
I'm joking about Autokiller's intuition but serious about the dubious benefits of SetCPU on an already overclocked ROM
Click to expand...
Click to collapse
KaosFroyo is already overclocked? I notice a huge performance gain when I enable SetCPU and OC it to 710mhz. If KaosFroyo is indeed overclocked already, then it must be set pretty low, or at least, very close to stock settings....
Acrono said:
KaosFroyo is already overclocked? I notice a huge performance gain when I enable SetCPU and OC it to 710mhz. If KaosFroyo is indeed overclocked already, then it must be set pretty low, or at least, very close to stock settings....
Click to expand...
Click to collapse
Ocd to 710 by default
Edit: I've had the best results ditching setcpu and using the collin_ph script, just btw
I see that setcpu is at a constant 2 ooms. Now im using Zen express but idk if that makes a difference. And im set to strict
The real and best answer I have for the first post (and what I do, and advise everyone I am around to do)
Stop using Autokiller.
Android does a great job killing processes.
Most users use 4-5 apps constantly throughout the day, and if the few most commonly used ones stay in memory more often than not, the phone is FASTER, as a result of calling up apps instead of having to completely relaunch them every time.
YES, using autokiller to adjust your memory settings can help if you are normally running process-intense apps in the background (like I sometimes run a VNC for work that will chew up some processor time if I just hit 'home' when I'm done instead of killing the task, or sometimes a small game that you figured was not in memory anymore, is still chewing up processor time).
BUT
That is what, and only what, I use a task killer for. I open up Free Advanced Task Manager, kill my background process that I don't want running, and move on with life.
9 days out of 10, I don't use a task killer, and I NEVER use auto killer.
If you want to keep your phone faster than not, use 'back' to get out of apps instead of pushing 'home'. Unless 'back' is mapped to something in the app (like for some apps), back will end the process rather than leave it running.
I could write ten pages on why to not use autokiller, but a lot of guys who are a lot smarter than me will swear by it. I just find it slowing down my phone by forcing me to re-launch things like Handcent SMS, my Web Browser, and Google Voice, when I'd rather have those things stay running in the background. They don't chew up much processor time just sitting in the 'background', and my phone is WAY faster if it takes 1 second to open up each app instead of 3-6 seconds (because autokiller made my phone already automatically kill the task).
Good luck with your decision, sir.
And if you're using xtrSense, you can just set up your GScript to overclock how you want (mine's at 806800), and if you're using Froyo ROMs, you can use the battery tweak. SetCPU isn't that useful for most of these ROMs, since the methods of overclocking by collin_ph's battery tweak and xtrSense's GScript are faster and more efficient, and don't require a background process like SetCPU to be running.
But that's just my opinion. I hope it helps.
I use System Panel to basically monitor my memory instead of just relying on Autokiller to manage them for me. I also found that the way I use my phone, similar to the way pkopelek mentions, a few select apps a day, my free memory stays fairly close to what it did with autokiller installed. Average around 40-60 and if I kill a few off, up to 90-100.
One thing I have noticed is that System Panel comes with a cpu scale and shows your clock speed. With no SetCPU installed my CPU will drop down to 245 and then bounce around and finally settling back to 245 then the cycle starts again. With Collins tweak I get the same response. However, with SetCPU installed my CPU will clock down to 245 and sit there until I touch the screen. I have to believe that SetCPU is doing something that collin's isn't. Now the only way I can get it to behave this way is if I change the advanced parameters.
just my 2 cents.....
When I used AutoKiller and SetCPU (I used both between May and August) before I started using xtrSENSE v4.x, I never had a problem with SetCPU quitting working under any ROM, including any Froyo that was out at the time.
I only mean that perhaps the problem isn't between SetCPU and AutoKiller. Maybe it is the ROM??? Just guessing here.
Nikolai2.1 said:
I see that setcpu is at a constant 2 ooms. Now im using Zen express but idk if that makes a difference. And im set to strict
Click to expand...
Click to collapse
I'm using this: http://forum.xda-developers.com/showthread.php?t=685594 and the value is ALWAYS above 9. I've never had it down that low except when I temporarily add it to the ignore list (it falls out after about 5 minutes).
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 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.
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