View Single Post
  #14 (permalink)  
Old 08-17-2010, 11:47 PM
Maxx134's Avatar
Maxx134
VIP Member
Offline
Location: NYC
 
Join Date: Jan 2007
Posts: 1,272
Reputation: 4320
Maxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributions
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
All overclock solutions one post!!

FOR MAIN LATEST LINKS MAIN 3 OVERCLOCK SOLUTIONS INFO AS OF DEC, LOOKY THIS POST HERE!!::
EDIT: NEWEST APP IS THE NEW iwfratz APP AS OF DEC 2010



1-DIFFERENT APP NOT THE NetRipper app BUT "iwfratz" APPs:

EDIT: NEW APP as od DEC 2010:
WiMoSpeed_V1.01.CAB (701.7 KB)
It is newer version which uses better method than his previous.
It may be better than netripper but I haven't tried yet.
Posters have commented better results on going higher speed:

[APP] WiMoSpeed: [2011-01-05] V1.03

- - - - - - - - - - -
FOR older iwfratz OCT app, which has dynamic overclock, AND does not require morscript and is totally different approach than Netripper Msm7k app..
Go Here:
http://forum.xda-developers.com/show...&postcount=162
EDIT:
The interval setting in this app IS NOT same as "polling speed" in other apps. It is just CPU "load" checking.
I would personally not want to lower the interval as it results in more cpu usage, as it checks the "load" faster, which makes Dynamic scallig jump around faster, giving more chance for SOD(in my opinion)...
Setting to zero will disable this feature.

Author of the app recommends now FOR SOME users to set steps at zero (no scalling) if users do not want to encounter any SOD...
Dynamic scaling is cause on some units getting an SOD on call or sleep...
BUT we "may" avoid SOD on scaling steps 1 & up by installing the SOD cab already posted here....try it.

================================================== ==================



2-APP BASED SOULUTION for Netripper Msm7k app:
The "SetCpuSpeed1.0d" cab is an app type solution, which in theory is supposed to be better than the early "Script" base solutions..
GO HERE:
Overclock TP2 in WM?
For latest "setcpuspeed 1d cab" and good info..
This app is good for those who want to ride highest unstable overclock with lowest polling...
That is why the "low" polling time is needed/used for them,
as lowering gives less chance for the OS to reset speed & freeze at high overclock.
This app seems to respond quiker at low polling compared to the "script solutions".
The "Checktime" only goes down to 50, so I made more choices: 18, 20, 24 & 30 in a easy cab for all.


3-SCRIPT SOLUTION for NetRipper Msm7k app:
It is common consensus (almost) that the script based solutions have more option/control;
and run more solid/smoother for some, soo..
Of the "script" solutions, I recommend "nayr1482" scripts for TP2, the latest "OC_ Auto_v4.21.cab" here:
Overclock TP2 in WM?
Update thread for Nayr1482, updated by "bteljuice" here...
It has interface and simple to install/use.
All that is needed is make shure you have latest netripper Msm7k cab installed and of course mortscript.
For me it worked better than "SetCpuSpeed1.0d" cab, but with so many variables, each user will have different results.
Example is lowest polling actually did not have better results.
There are other Scripts out there but they are not cabbed and are for other devices as well.

EDIT::
Quote:
Originally Posted by nayr1482 View Post
Some useful information for everyone...

OC_Auto_x.xx - prevents against SOD caused by backlight off, phone calls, and lockscreen (default). it does this by throttling your cpu back to a lower speed when these events occur.
IMO, this seems to be the most stable for most people.
The drawback - it uses more CPU power than SetCpuSpeed (but keep in mind...we are achieving like 50% OC's and the script uses around 2% when set to 1000ms polling).
Netripper's app does the work, the script basically controls the application.

SetCpuSpeed - prevents SOD only caused by backlight off. also does this by throttling your cpu back to a lower speed when this event occurs.
The pros - uses less CPU power than scripts even with faster polling.




GENERAL TIPS:
THINGS TO LOOK FOR in speed limits:
look to see if the "Msm7kcpu" app blinks steady.
look to see if you can quikly swipe pictures in sense tab without lag.
look to see if unit freeze while using keyboard on texting or Opera posting.


Also made the "phoneSleep" reg setting cab for SOD on calls, into a cab...
This cab is FOR ANY solution...

Also delay startup in another cab.
This cab is not for OCT app solution..

You can Install any of these cabs AFTER installation of either cab solutions...
EDIT: Remember the "Msm7k_Set_CheckTimeToXX.cab" cabs are only for the "setcpuspeed 1d" app based solution.


Last edited by Maxx134; 01-08-2011 at 10:21 PM. Reason: NEWER "iwfratz" APP !
Reply With Quote
This post has been thanked 17 times.