Related
hello ppl,
just installed wm2005 ,looks awesome,though I have just issue with it,it kinda lags, when I click start,takes time for the menu to pop ,when I change programs again takes time for it to happen ,even when I close a program it takes a 6-8 seconds for it to close while in wm2003 it was instanteneous (2-3 sec)
I have installed all the patches which are posted on wiki and the ftp with the new rom,are there any more registry patches with which I can make this baby go little faster and sort this issue ,it's kinda running xp on a old machine
or everyone is facing the same problem ?
WM5.0 is slower. However, you can improve its speed by:
- Removing un-needed Today items like MSN Mobile, Spb Pocket, Resco Today plugin (if installed).
- Disable as many sound options as you can.
- Overclock your processor to 530 MHz. (This might be unsafe, do it at your own responsibility. It works great for me though).
- Set the clock to always show on all programs (Go to the clock settings and the option is available on the 3rd tab).
You'll have a smoother performance, but still not as fast as WM2003SE.
pakiyabhai, my start menu pops in a fraction of a second. And do you call 2-3 seconds instantaneous? I have almost all my programs gone and the today screen back in around 1 second on WM5! I only show the message and calendar box on the today screen, though.
thanx for the tips,
mastif hehe ,ok thanx for the correction , i have no today plugin installed,all of em are disabled
I tried the clock options ,but no diffrence as of now
I am seriously considering the overclockin option ,but won't it drain my batttery faster ?
It will, probably... try it for a day and see if it drains or reaches a critical level. If it doesn't, then that's okay you can recharge your PDA during the night I guess... on vacations, don't overclock hehe
... and just as a tip: go back to WM2003SE right away! That's what I did. First, this is still very experimental; I need a working device. Second, there's no wireless modem, and Pocket Word lacks drawing, and Powerpoint is like read-only as I saw... lots of missing features and not working ones... Slow slow slow. I'm on 1.40 i-mate ROM now with overclocked bus speed. Now that's my lovely Blue Angel :roll:
For me, WM5's speed is about 85-90% of WM2003SE, which is acceptable.
KTamas said:
For me, WM5's speed is about 85-90% of WM2003SE, which is acceptable.
Click to expand...
Click to collapse
That may be acceptable,but the b/t problems on WM5 is not acceptable! I switched back again.
Later............... 8)
I hv come across this overclock utility for TI OMAP, OmapClock 0.2
I have tried it on DOPOD 818, overclock up to 240MHz, runs without problem. Opening SMS dan File Explorer is now alot faster.
Anyone with TI OMAP processor should have this !!!!
It should run on Smartphone too.
main thread:
http://forum.xda-developers.com/viewtopic.php?t=40284
Great find...thanks...
Works brilliantly. Thanks
Impressive! What about CPU temperature?
I'm equally impressed by the speed gains of this little program, but am somewhat concerned about other potential side-effects; like frying the CPU!! :?
Anyway, I'm using 'batti' to keep a close look on the temperature. It's qite a handy little tool.
http://pda.jasnapaka.com/batti/
Please let us all know how you get on with this program over time.
P.S. Does anybody know what temperature should NOT be exceeded by this CPU? Mine is currently at 30 degrees and it was at 24 when I started using the overclocker.
Correct me if i'm worng but the batti app looks like it shows battery temp, not cpu temp? (prehaps your battery temp ahs gone up because you've been holding your pda ;-p)
My Bad! Temp is for battery NOT CPU!!
tintoy said:
Correct me if i'm worng but the batti app looks like it shows battery temp, not cpu temp? (prehaps your battery temp ahs gone up because you've been holding your pda ;-p)
Click to expand...
Click to collapse
Your absolutely right!!
Thanks for bringing my attention to this very important point. :wink:
Anyone know of an application that accurately shows the CPU temperature? :lol:
when i run in 300MHz which Mini S, it will hard reset.. I don't know why
hi minhbu_sg,
when i drive a 90° curve with my car at 100 miles per hour i always have to leave the road just kidding. the reason for hard reset is just of physical nature. you have exceeded the limits of your built-in omap cpu. at 300mhz it does something but not what it is supposed to do. same thing when you have, let's say, a glass of whisky. having one glass of whisky does slightly influence your cpu (brain) and everything you are trying to do is a little bit easier (at least you feel so) but having a bottle of whisky drives you doing things you don't want to do at all.
so keep overclocking you omap moderately and you get the best benefit out of it.
regards
peter
300 mhz
hi
i install this software and i put my device clock to 300 and it stop working.
i try soft reset but it didn't start. and i try to hard reset it also didn't go
please help what should i do.
thanking you in advanced
when i drive a 90° curve with my car at 100 miles per hour i always have to leave the road just kidding. the reason for hard reset is just of physical nature. you have exceeded the limits of your built-in omap cpu. at 300mhz it does something but not what it is supposed to do. same thing when you have, let's say, a glass of whisky. having one glass of whisky does slightly influence your cpu (brain) and everything you are trying to do is a little bit easier (at least you feel so) but having a bottle of whisky drives you doing things you don't want to do at all.
so keep overclocking you omap moderately and you get the best benefit out of it.
regards
peter[/quote]
i installed this on my kjam and worked great with noticeable speed boost, BUT....
when i suspend the kjam, and open it again, the speed goes back to the defauls 180.
is this normal? or something has to be done to enable the speed i choose until the next soft reset at least?
Yes, it's normal - and yes, you would have to use some manner of application to re-start the overclock after a suspend. See also the original thread: http://forum.xda-developers.com/viewtopic.php?t=40284
Can somebody tell me how to run this program. Im pretty new to all of this and not sure where to install on my qtek s200 and how to run it.
Thanks!
Kanjibankers said:
Can somebody tell me how to run this program. Im pretty new to all of this and not sure where to install on my qtek s200 and how to run it.
Thanks!
Click to expand...
Click to collapse
U device (Qtek s200) is a HTC Magican. This forum is about HTC Wizard. Try to look in Magican forum.
People! When wizard is in suspend it runs on 180 mhz? Can we decrease this value in suspend mode?
oh yeah!!! now, my device [818 Pro] run faster @240MHz...it seems as same as XDA Mini...[even better]...thanx!!!
cheers...Oi...!
i'm confused
i'm using a Dopod 818pro,and i already used the omap overclock v.0.2 ... i copied it into my device (not storage card).then i run it on 252Mhz,and set action..so the speed is already 252Mhz and very fast... but i've got some problem,when i turn my device to standby mode,and when i push the power button to sms someone,i check my speed,it went back to 180MHz,is it normal?? cause if it runs under 180MHz,that means it didn't run at 252MHz right????
thanx any way.....
sort of off topic but that batti program is nice...
it's kind of like the battery meter that comes with spb, but better...
Re: i'm confused
K4V4N4 said:
i'm using a Dopod 818pro,and i already used the omap overclock v.0.2 ... i copied it into my device (not storage card).then i run it on 252Mhz,and set action..so the speed is already 252Mhz and very fast... but i've got some problem,when i turn my device to standby mode,and when i push the power button to sms someone,i check my speed,it went back to 180MHz,is it normal?? cause if it runs under 180MHz,that means it didn't run at 252MHz right????
thanx any way.....
Click to expand...
Click to collapse
Use this cab instead http://forum.xda-developers.com/viewtopic.php?t=56057
Or this one
http://forum.xda-developers.com/viewtopic.php?t=55782
:lol:
Hi: I've super-upgraded to TuMa 1.3 with very good happy time till now!
Many thanks guys, especially Tuma!!
i just have one problem, when typing on my keyboard, sometimes, not all the time, keys stick and after pressing a key i get something likeeeeeee thissssssssssssssssssssssssssssssssssssssssssssssssssssssss
or, even worse, the backspace key gets stucked the same way and it erases all EAAARRRHHHGGGG!!!
is this fixable??, is anyone else having this problem???
I use the keyboard big deal...
Have the exact same problem with helmi 1.3
tehCORE said:
Have the exact same problem with helmi 1.3
Click to expand...
Click to collapse
So, I see now that upgrading (something I had planned) to helmi 1.3 doesn't repair this problem. I would like to know where this problem originates to find a solution. I'm using now Pocket Hack MAster with the device running at 597 Mhz and the problem is still there! :evil:
Some advice??
EDIT: I've removed the CPU Meter on the upper bar. It seems to work faster and better. Still waiting to see if the problem arises again..
i'm on helmi_c 1.1b and have this problem too. May be that is hardware problem or driver time bomb?
change the keyboard repeat settings, and delay settings, I have had this problem with every wm5 rom, and by changing the settings it appears to fix this prob.
tesing.. thanks for reply...
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Black6spdZ said:
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Click to expand...
Click to collapse
probably something to do with the ROM as well... it was present on Tuma 1.3 and Helmi AKU 2.3, but after flashing AKU3.0 1.2 keyboard is working fine, be it 200mhz or 570mhz using xcpuscalar.
I've had success with changing the keyboard repeat settings but it comes back eventially. I've had the problem on every WM5 ROM, but less-so on the most recent Helmi ROMs with the AKU update.
its only in the built-in mail program... try typing in O2 SMSPlus or IE or something else
Black6spdZ said:
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Click to expand...
Click to collapse
I'm now using Pocket Hack Master with the feature of using different speeds for different apps. It happens less, so, could be the driver priority on CPU intensive apps. Because the SMS app now seems to need more CPU power than before :? :? (bar & text space redraw or something), it is one of the apps I've selected to run at 590 Mhz:shock:.
Black6spdZ said:
its only in the built-in mail program... try typing in O2 SMSPlus or IE or something else
Click to expand...
Click to collapse
I'm having this problem with other programs also (i.e.: Softmaker TextMaker, Pocket MindMap). Also, someone said that when using the e-mail (nor the SMS) part of the program the problem doesn't happens.. I've not tried myself as I don't currently use e-mail on my device.
xykosomatik said:
probably something to do with the ROM as well... it was present on Tuma 1.3 and Helmi AKU 2.3, but after flashing AKU3.0 1.2 keyboard is working fine, be it 200mhz or 570mhz using xcpuscalar.
Click to expand...
Click to collapse
Please, xykosomatik, confirm so. I would be eager to upgrade if this problem is solved on this ROM, as I use the keyboard typing 80% of the time on my device.
Thanks all.
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
It seemed to make an improvement for me, but time will tell. This issue seems to come and go on my phone.
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
arieltools said:
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*** DANGER WILL ROBINSON ***
If people continually try tweaking the Priority of drivers to ABOVE Real-Time or OS/Services level, and then claim that it makes things better - go right ahead. Sure, it "might" make it seem to operate better - BUT THAT'S ONLY BECAUSE IT'S SERVICING YOUR KEYBOARD AT REAL-TIME RATES ABOVE THE OPERATING SYSTEM ITSELF! ARRGH!
Have fun, enjoy playing with task/thread priorities, and don't complain when your device locks up because your keyboard driver is above the RAM driver, and locks up your device waiting on RAM access.
PLEASE ... read the MSDN articles on Priority settings before posting silly suggestions like setting the Priority to 1. Not even the OS is running at priority 1.
haven't had any lockups yet.. and anything to make the damn keyboard usable in wm5 is good in my opinion
Tuatara said:
arieltools said:
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*** DANGER WILL ROBINSON ***
If people continually try tweaking the Priority of drivers to ABOVE Real-Time or OS/Services level, and then claim that it makes things better - go right ahead. Sure, it "might" make it seem to operate better - BUT THAT'S ONLY BECAUSE IT'S SERVICING YOUR KEYBOARD AT REAL-TIME RATES ABOVE THE OPERATING SYSTEM ITSELF! ARRGH!
Have fun, enjoy playing with task/thread priorities, and don't complain when your device locks up because your keyboard driver is above the RAM driver, and locks up your device waiting on RAM access.
PLEASE ... read the MSDN articles on Priority settings before posting silly suggestions like setting the Priority to 1. Not even the OS is running at priority 1.
Click to expand...
Click to collapse
maybe we could do a compromise, i little higher than the OS priority
the keyboard problem is really annoying
what would be a decent value for this, just to raise the priority to a decent level to get a good response from the keyboard?
*sigh* ... why do people still keep punching in random numbers into the registry without checking what the values could or should be? *sigh*
Black6spdZ said:
haven't had any lockups yet.. and anything to make the damn keyboard usable in wm5 is good in my opinion
Click to expand...
Click to collapse
gh0st said:
maybe we could do a compromise, i little higher than the OS priority
Click to expand...
Click to collapse
Ok ... before this gets out of hand, and other people start doing "silly" and "stupid" things with Priority256 ... especially without understanding what you're changing, READ THIS! Otherwise you WILL cause untold problems for your device.
http://msdn.microsoft.com/library/d...html/wce50conRealTimePrioritySystemLevels.asp
To give you the comparison for Windows XP ... just open Task Manager, select an application which is using 100% CPU, running at Normal Priority, and switch it to Real-Time. Then enjoy how "responsive" the one application is (unless it's accessing the video display and/or disk - i.e. try doing it to an explorer window file copy! ;-)). You'll enjoy a "locked" machine, and admire how you're unable to do anything else - even open the start menu! You may have to hard-reset your machine depending on the application you choose to make Real-Time.
THANKFULLY ... the Keyboard Driver (QwertyKey) has a FORCED time-delay in it (debounce delay) which ensures it can not take 100% CPU time, and through this ... and ONLY through this fact, it hasn't killed your device. Had you done this to ANY other device driver, I'm sure your device would need a hard-reset, and you could start re-installing everything again.
By raising the priority above everything ... ALL you are doing is making the QwertyKey device driver get serviced AHEAD of any other pending interrupt. While this MAY make a slight difference, it will only do so at the expense of EVERYTHING else in the OS. (Like WiFi, Network, USB, ActiveSync, Memory Management, Compaction, etc ...)
gh0st said:
the keyboard problem is really annoying
Click to expand...
Click to collapse
Yes, I have had the same issue, but there is a LIMIT to which you can go with the driver Priority in order to "fix" what is fundamentally a hardware and driver problem.
gh0st said:
what would be a decent value for this, just to raise the priority to a decent level to get a good response from the keyboard?
Click to expand...
Click to collapse
In my testing, and throughout the TuMa ROMs I've used 0x81 - or a priority of 129. This was carefully chosen to be below the Wave device (which was or should be set at 0x80 or 128 for best performance on the BA - again due to driver issues), so that sounds/rings happen at a higher priority than the keyboard. Yes, this is eventhough BOTH Priority256 values for these drivers were tweaked above the default recommendations from MSDN.
If you're finding that the keyboard is causing you grief, you could try inverting these two devices, and setting the keyboard HIGHER than the sound driver - i.e. to 0x7F or 127, and see if the system sound servicing is the cause of the keyboard stuttering delay. However, you may introduce stuttering into the sound output at this point ... i.e. even when you're NOT using the keyboard (which is most of the time).
At the ABSOLUTE HIGHEST level I would even consider, would be just below that of the touch-screen (0x6D). At this level (or above) would cause handwriting recognition issues, as the touch-screen would not be serviced at the correct rate to track the line drawings.
Never even consider going above the Power Manager Resume Priority Level ... if the driver supports power management, and is taking too much CPU, then the power management thread will never be able to "shut it down", and/or wake it up ... ever. Result = lockup.
So ... in summary:
QwertyKey: 0x81 ... or 0x7F to invert priorities
Wave Device: 0x80
I'd still like to test all this with the latest AKU3.x ROMs and see if the Priority settings are still valid, but for the moment, I'll assume that they are.
Good luck to anyone using priorities outside "sane" values ... you will create "priority inversion" conditions, where a driver is waiting on another driver to run, but it never will, since the priorities are reversed. You have been warned ... but enjoy playing with it anyways. Device recovery is only a hard-reset away.
Thanks for clearing this up Tuatara, good post!
oops! i'm reverting the priority values....
Thanks for the post, @Tuatara. it was very enlightening.
http://www.oliy.co.uk/download.asp?dir=\software\OmapScaler
it is working fine in my wizard but some ppl complain about causing soft resets or not working at all:
about resets: ver .11 have a "max clock step" option, try to reduce it, my wizard works fine with 50 but some ppl r using 25 or even 20...
about not working at all:
1- unpack
2- copy to windows folder in device
3- copy also omapclock.exe to windows folder in device
ftp://xda:[email protected]/Wizard/Misc/OmapClock_v0.2.zip
4- create an icon or run manually
5- set ur desired options and press save
6- copy the .lnk created to windows\startup so it stats with windows everytime (but test it carefully before doing so or u can end with a neverending soft-reset cycle)
my config (working)
- overclock marked and 240mhz (some ppl report soft resets over 220,
reduce this number also)
- above 70%
- underclock marked and 120mhz
- below 30%
- default speed 214mhz (this is the speed center, used if u dont mark
overclock or underclock)
- max clock step 50 (if u have soft resets reduce this number)(mine
work fine at 50 but resets over 70 as example)
- update period 2000 i guess this is the time between system
monitoring of speed in miliseconds, but please correct me if im wrong
- clock threshold 2 (i guess this is the step between clock changes,
but im not sure what is a period...maybe an internal clock tick?)
ok, i tested this one, if u increase it it takes more time between clock changes,
another thing to try to solve soft-resets, i tested 3 and 4...and takes more time
between changes...
some comment: it speeds up depending on the cpu usage but for some reason it dont get along fine with agile messenger in my setup...if agile is connecting it appear as if the device hang but in fact it resumes operation in 10 secs or so...so try to test it first without loaded applications...then load 1 by 1 and test...
lets talk about this and try to solve problems for the ones that have them...
btw...im using molskis rom and working flawlesly...
hi, there,
I followed your instruction fully.
however, when I clicked Omapscaler, I got an "error exception".
I wanted to show you the details..... but I couldn't "copy & paste" the message.
Noted that, I have been running smartskey + Omapclock at 252 stably for long time, and now with Risidoro 2.26 ROM.
hope to get it working.......
thanks,
ecchi
Cool, I'll give this a try ASAP and report back
Activesync quits
I installed the Omapscaler. It seems to work fine. I have it set fairly conservative - middle at 200, underclock at 170 and overclock at 230.
If I am connected to activesync, it quits after a few minutes of idle time. Have you noticed this?
-Kal.
Mine does the same, but in my case it puts a red cross over the green circle, it didnt sync anymore but i can explore the wizard files...and it does it also without the omapscaler, i guess that that have some relation maybe with the proccessor clock losing sync with the pc...dunno...but in my case is not related to omapscaler...but related with the overclock...
Yeah, I saw the same problem with ActiveSync and rom updates.
Just disable the omapscaler, run omapclock and set the speed to 200 or so, then try again.
Oliy, great program, thank you
Again...in my case i tested activesync just using omapclock (NO omapscaler) and does exactly the same...
Since I got the "error exception" with Omapscalar.witrh my current ROM (risidoro), I have started trying XCPUScalar. However, it is not any more stabler as some ppl had mentioned.
Bottom line:
Omap + smartskey ==> most stable, tried at 252, but about 1 day of battery only.
XCPUscalar ==> fixed at 232, stable. fixed at 247 reboot sometimes. Autoscaling b/t 117 and 247 reboot 50% of the time when you launch/close/activesync. I am testing now autoscaling between 117 and 232. Hope it will work.
soft resets with max clock step at 10
I had the max clock step at the default 50, and got a soft reset. Then, per the advice on this thread, I reduced it all the way down to 10. It still soft resets. I have top speed at 230, default at 200, and bottom at 170.
So, I am giving up on this program.
just a q. it stays at least some seconds or die instantly? omapclock alone works?
Yes, it stays up for a while. It seems like it stays up until it goes into standby mode, or I put it in standby manually. A bit after that, it soft resets.
I have not used Omapclock by itself. I have never felt the need for it. But, something that automatically scales up and down to suit the load seems very useful to me; so I tried it. I am willing to keep trying it, if there are bug fix versions.
-Kal.
Maybe ur problem is with the overclock per se, not omapscaler...try using the device with omapclock fixed...if ur device resets then omapscaler is not the faulty...also, what rom do u have? maybe we can pinpoint the problem to a specific rom or set of roms...
hmm... the problem cannot be overclocking, because it goes into the soft reset directly from standby mode. I would think it would be *underclocking* when it is on standby mode, no? Let me do some experimentation with both overclocking and underclocking using smarskey with omapclock, and see what I can figure out. But somehow I doubt that is the issue.
I have standard stock Cingular 2.25.11 rom.
-Kal.
I have been running Omapclock at 230MHz for a while now, with no problems. The Omapscaler would have definitely reset by now.
And what device exactly and with what rom do u have?
It's a Cingular 8125 device, ROM version 2.25.11.1 WWE (stock ROM that came with the device from Cingular).
Omapclock has been running for almost a day now, with no problems, so the problem must be with the scaler.
-Kal.
A theory...
In case the developer is monitoring this thread:
I saw in the other thread on this forum that someone reported that XCPUScaler has the same problem as I have with resetting when in standby mode on a Cingular 8125 with stock rom as well. It may be that these units have some kind of daemon processes that run even while the unit is standby (I know for instance that my unit retreives email when in standby mode), and that causes activity that pushes the scaler to try to scale up. And maybe the unit (or the rom os version) doesn't like the processer speed being mucked around when in standby mode. Or maybe, even that the API call to sense the CPU load craps out when in standby.
This is a conjecture of course, but it seems to me that there can't be very heavy activity during standby. So, could the developer please try to disable scaling when in standby mode? This may solve the problem. Or maybe, just make that an option that people with this kind of a problem can select.
Just a suggestion...
-Kal.
error exception log
I can run omapclock with smartskey @252 stable.
But when I reconfig my wizard to use omapscaler, I got the following exception on launch:
=============================================
OmapScaler.exe
Exception
CompareInfoRef::.ctor+0x35
CompareInfoCache::GetCompareInfoRef+0x9c
CompareInfo::GetCompareInfo+0xc
CultureInfo::get_CompareInfo+0x19
DataTable::RecomputeCompareInfo+0x11
DataTable::Reset+0x6
DataTable::.ctor+0x113
DataTable::.ctor+0x6
ConfigDB::setupConfigDB+0x32
ConfigDB::Load+0x2a
ConfigManager::setupConfigDB+0x14
ConfigManager::Get+0xc
ConfigManager::get_ocLoad+0x15
CpuClocker::readConfigSettings+0xb
CpuClocker::.ctor+0x56
MainForm::MainForm_Load+0xb
Form::OnLoad+0x15
Form::_SetVisibleNotify+0x1d
Control::set_Visible+0x1f
Application::Run+0x7
MainForm::Main+0xa
==========================================
I have a Molski Rom WWE (30MB) G3 Wiza, installed with CE Star (language tool), and some 7 today plug-ins.
any idea?
astromusic said:
In case the developer is monitoring this thread:
I saw in the other thread on this forum that someone reported that XCPUScaler has the same problem as I have with resetting when in standby mode on a Cingular 8125 with stock rom as well. It may be that these units have some kind of daemon processes that run even while the unit is standby (I know for instance that my unit retreives email when in standby mode), and that causes activity that pushes the scaler to try to scale up. And maybe the unit (or the rom os version) doesn't like the processer speed being mucked around when in standby mode. Or maybe, even that the API call to sense the CPU load craps out when in standby.
This is a conjecture of course, but it seems to me that there can't be very heavy activity during standby. So, could the developer please try to disable scaling when in standby mode? This may solve the problem. Or maybe, just make that an option that people with this kind of a problem can select.
Just a suggestion...
-Kal.
Click to expand...
Click to collapse
i have read around that there r several levels of standby, full, partial, etc...maybe he only need to modify it to work only on "full on"...
but maybe we r both wrong thinking about it a lil longer...maybe he already thought about that and omapscaler dont work when on any kind of partial standby, in any case the device is in standby, u r not going to notice if it takes 20 more seconds downloading the mail as example...
and btw, xcpuscalar didnt worked for me also, random softresets, but omapscaler worked like a charm (now im using batterystatus solution and also works fine)
worked great for a while then kept force closeing anyone haveing problems??
It seems to be working fine for me. One thing is that when I set the clock to 128 or something, the status displayed on the widget still shows 527. The performance is significantly slowed so I assume it's doing it's job.
Overall I think it's a nice little widget. Great for maxing out performance, and maxing battery life by limiting performance.
Phone:
Black G1
JF 1.51
Yup...me too
I will make the change but it sometimes does not refresh the gui. It will also not work if you reboot. (if i remember correctly) also tons of force closes. I am on 6.01 and have tried JF1.5 and am curently on HERO but have not had success with the widgets on the build yet so I dont have a confirmation.
Could someone post the previous version of this app please? The updated version on the market shows "problem loading gadget" on the Hero rom when you add it to the screen..previous versions worked without any problems. Thanks in advance.
edit: nm..fixed it..just had to run the odex optimization script and all is good again
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
what is a good configeration for over clock..i dotn want to mess up my phone??
I was thinking the same and should I have it on always max. Or what?
I've got mine set to 128Mhz min and 527Mhz max, it has drastically increased my battery life. Batter life barely drops 1% overnight.
Anyone have the Version before the 1.7 update. The new update doesnt seem to work on hero w/ Rosie.
You can grab the 1.6 apk from the Dev's Google Site (check the Files section).
1.7 doesn't work with Ion for me either
zgmf-x322a said:
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
Click to expand...
Click to collapse
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
IronCross1788 said:
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
Click to expand...
Click to collapse
The creator of the original Overclock app hasn't updated his application for even Cupcake build support yet. I thought he removed it from the market.
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yeah NeoBlade (thanks!) gave me the tip on that one yesterday. Seems to be helping a ton.
Min384Max527
Screen off Min128Max245
I can't find Overclock Widget in Market, was it removed?
I have the Overclock Widget and my question is, is it bad for my phone that while my screen is on i have it a min 527 max 527 then while screen off min 128 max 245... I've noticed that phone charges last longer but the useage of going back and forth determental to the phone? Thanks
coolbho3000 said:
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
Click to expand...
Click to collapse
Thanks, that would be of great help. Specially the battery profile settings. If you could also put a monitor, be it a widget or something on the notification bar it would be beyond awesome, or maybe a just notification of when the speed is changed and to what it was changed to.
Does anyobdy know if this SETCPU works on Hero ?
And must the app be on after i set the clock or can i close the app after ?
*bump* need to know