Related
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.
filesys.exe remains at 16.4mb.. and wondering if this is normal or how to reduce it to normal? Or any fix to this?
royalbloodvi said:
filesys.exe remains at 16.4mb.. and wondering if this is normal or how to reduce it to normal? Or any fix to this?
Click to expand...
Click to collapse
I think its normal, it uses 16.3mb in my xperia...
Huh?? Not for me. It takes 2129kb.
Cool eh?
That's defniately not taking up 95% of its ram though, considering it has like 200.48 MB of program memory. Check your programs running, make sure you dont have alot of stuff running, and restart your phone. If it starts up and stays at 95%, youve got a problem. Either alot of apps are opening at the start for some strange reason, or youve got a very screwed up ROM.
im using gttrab's barebone r3.6. very stable.
one thing i noticed was: when i take out storage card, filesys.exe: 7mb.
doesnt ANYBODY have this problem too?
im just running normal stuff, spb shell, voice command, s2u2. thats it....
So from what I understand linix swap is a method to make your phone run faster. My phone has been acting a bit sluggish lately when loading the home screen.
When partitioning my sd card (using ra recovery) it asked how large of a swap to use, I checked another thread and found out that the recommened size for cupcake is 64mb. I set it at that. Is my phone currently using the swap or do I need to activate it/ use an app
In addition to the obove questions could someone outline the advantages/disadvantages.
Thanks a lot for any help.
asb123 said:
So from what I understand linix swap is a method to make your phone run faster. My phone has been acting a bit sluggish lately when loading the home screen.
When partitioning my sd card (using ra recovery) it asked how large of a swap to use, I checked another thread and found out that the recommened size for cupcake is 64mb. I set it at that. Is my phone currently using the swap or do I need to activate it/ use an app
In addition to the obove questions could someone outline the advantages/disadvantages.
Thanks a lot for any help.
Click to expand...
Click to collapse
In cyanogen you will need to edit the user.conf or userinit.sh, I'm not sure which, to activate linux-swap as he uses compcache as default
It depends on who you ask... CompCache (CC), IMO, is better than swap for many reasons, the most of which is that it seems to be faster in scientific testing, and the best test of all, the seat of your pants test.
The problem with CC is that if you want to flash a ROM that is huge, ie a Hero ROM, you run out of room, so it becomes slower compared to a swap where you are actually adding "RAM" by using the SD card to do this. Some have been able to make Hero small enough to work with CC, but not enough for most people wanting all the bells and whistle's of Hero.
CC has some draw backs, the biggest being that it is slower than no CC in a solo task since the CPU has to uncompress the data when you re-open a program (You really see this when you open your browser back up and it takes 5 seconds to "reload" the page). But this is about the only real draw back.
Swap has a few more draw backs... it burns up your SD card, although it isn't a "huge" deal, it is still a draw back. As well, like CC, the CPU has to pull this data off the SD card, it isn't just sitting in memory like true RAM, so it's speed is limited by the speed of the SD card and the speed of the G1 at reading the SD card. In the end, since swap tends not to be compressed anywhere close to what CC is, it ends up being not that big of a deal in terms of actual speed... ie the browser might take half a second longer to open than CC right out of the box, but if you end up with 15 apps running and Rosie(what makes a Hero ROM a Hero ROM) it will take less time since it is at least still in the "RAM" and doesn't have to be re-opened 100%.
I hope this makes sense, and for those wiser than I, if I misrepresented let me know and I shall bow down like red chowder bows down to white chowder.
you can also use the app "user.conf v.030"
that's what i use, because i can control swappiness
i have now compcach enabled 64MB, ccbackinswap (swappiness 50), and 128MB linux-swap (swappiness 50)
works like a charm
shmigao said:
you can also use the app "user.conf v.030"
that's what i use, because i can control swappiness
i have now compcach enabled 64MB, ccbackinswap (swappiness 50), and 128MB linux-swap (swappiness 50)
works like a charm
Click to expand...
Click to collapse
And I take it that this will make my phone run quicker? My phone has been a bit sluggish in loading the home dash
would this make my phone run quicker? and cold you explain swappiness
asb123 said:
would this make my phone run quicker? and cold you explain swappiness
Click to expand...
Click to collapse
It depends, try it out and see how it works for you. Every person uses their phone differnetly, so for some it is an improvement, for others it is not.
And "swappiness" means the actual amount of data being swapped...
ie:
I have my linux-swap partition at 200MB, and my swappiness set at 96MB, meaning that only 96MB of data are actually being swapped on to the SD card.
Now, I don't use swap at all myself on donut, I stick to compcache or nothing depending on what the chef decided to do. If it uses swap out of the box, I will turn it off and put it onto compcache for a donut build.
Before you start playing around with swap, maybe get a task killer installed and use it sparingly (Android runs better when you don't kill stuff because of the way it is designed, but there is a limit, so task killers are nice, especially to kill something like music player or video player running in the background) This will speed things up just by keeping heavy CPU/RAM use programs actually fully closed.
Also, how slow is slow? At first, any ROM fly's on snapping back etc... but they all slow down a bit, some more than others. Actions should not and will not be instant, they should take time... not 15 seconds, but if it takes a second to load the home screen, so be it, that is damn good my friend.
Hey all,
Sorry if i sound dumb, but i can't quite figure out what these lag fixes do, or if i should try to put one on my device. I've tried to read the threads pertaining to the lag fixes but all the ext2 ext4 stuff confuses me haha. In my mind i picture it fixing the delay on the 4 buttons (menu, home, back, search).
If anyone could break it down for me i'd very much appreciate it
Thanks
One of things it does is makes those button 2-3x faster. Also i think it makes the general experience of the phone a lot more smoother from what i have noticed.
ViniD said:
One of things it does is makes those button 2-3x faster. Also i think it makes the general experience of the phone a lot more smoother from what i have noticed.
Click to expand...
Click to collapse
Ahh i guess i shoulda followed my gut, or just tired it haha. Thanks for the heads up, i think i'm gonna try it right now
Ok so i just ran the one click lag fix. I can't say i notice a difference in pressing the bottom buttons but to make myself feel better i downloaded that quadrant thing, ran it and it gave me a score of 2264. Now i have no idea what that proves but at least i don't feel bad now about applying the lag fix lol
Sometimes the phone seems to lag or hesitate at times if you press a button, open an application, etc. These are the "lags" the fixes are addressing. It's literally taking the phone longer than it could to read and write files on the device.
The lag fixes move your system files into a different file system (sort of like a virtual drive on PC's, all done in software.) Samsung uses a file system called rfs, which is running very slowly on these phones. Lag fixes use different file systems from Linux, such as ext2 or ext4, which perform better.
The risk in using a lag fix (albeit small) is that your data might become corrupted if you don't shut down your phone properly; for example, say if you pulled the battery while the phone is running.
I hope that helps you understand what they do better.
Sent from my SAMSUNG-SGH-I897 using XDA App
ag4vr said:
Sometimes the phone seems to lag or hesitate at times if you press a button, open an application, etc. These are the "lags" the fixes are addressing. It's literally taking the phone longer than it could to read and write files on the device.
The lag fixes move your system files into a different file system (sort of like a virtual drive on PC's, all done in software.) Samsung uses a file system called rfs, which is running very slowly on these phones. Lag fixes use different file systems from Linux, such as ext2 or ext4, which perform better.
The risk in using a lag fix (albeit small) is that your data might become corrupted if you don't shut down your phone properly; for example, say if you pulled the battery while the phone is running.
I hope that helps you understand what they do better.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
This was a perfect explanation. I saw someone who was wanting to make a new guide, i suggest you send that exact post to him. If i can understand it anyone can haha.
This does raise some questions now though,
1. I know it can now be corrupted but is this on the internal or external sd card? 2. Once corrupt what exactly is stored in this location (if i remember right i had to chose a size to apply this lag fix to)?
3. Is this a corruption like i can just reflash a rom and everything is back to stock, or is that piece completely broken?
Thanks again =)