yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] speeraer:
Strange; yesterday OmapScaler worked quite well for me, but now I have the same problem as Guybrush; a seemingly 100% CPU load non-stop...

(Using qtek9100 ROM2.18 )
[Windows Mobile Development and Hacking General] Oliy:
speeraer, which version are you using? Did it change to 100% load when you swtiched from v0.1 to v0.11?

oldsap, just run the program OmapScaler.exe, it looks for omapclock.exe in the windows directory automatically.

laggflor, I will make a version you can run without the GUI. That will hopefully save on memory.

Oliy
[Windows Mobile Development and Hacking General] laggflor:
First battery measuring

So folks, here are my first battery usage statistics:

I used the following scenario:

Device: HTC Charmer, TI OMAP 850 with 195 MHz

Device is turned "always on", Backlight "always on" (so that I can see whats going on without touching the device), no programs running (except windows mobile, today plugins and built-in battery monitor

Each test case was done this way: I charged the battery until it was 100 % full. Then I disconnected the charger and looked at the (windows-built-in) battery monitor.

Because of less time i waited until the device reaches 95% battery. Other values in the table are calculated.

I know - this is a very short period but I didn't have more time for now. Maybe I find the time for some overnight tests.

Test cases:

1. overclocked to 240 MHz without omapscaler running

2. (clocked to 195 MHz without omapscaler running) - THIS TEST FAILED. I'll try again in above mentioned overnight tests.

3. underclocked to 80 MHz without omapscaler running

4. underclocked to 80 MHz with omapscaler running, interval=1000ms

TEST CASES | Time 95% (s) | Runtime
-------------------------------------
Test case 1 | 1583 | 08:47:40
Test case 2 | failed | failed
Test case 3 | 2045 | 11:21:40
Test case 4 | 2038 | 11:19:20

What we can say now:

1. The battery usage is not influenced much by running this application

2. Overclocking consumes much more battery then Underclocking

What we can not say now:

1. How much battery is saved by underclocking (because test case 2 failed)

Maybe someone has more time to test? I want to make a test over 8 hours each with phone turned off (while I'm sleeping). I hope I can post it after 4 nights ;-)
[Windows Mobile Development and Hacking General] speeraer:
I used v0.11 from the start. However, today I upgraded my ROM with the MrClean AKU2.3 package. OmapScaler works again like a charm...
[Windows Mobile Development and Hacking General] Guybrush:
i have 2.18.9.1 ITA ROM maybe the problem of CPU Load depends from it.
[Windows Mobile Development and Hacking General] laggflor:
*** Conclusio ***

I updated the Tests I made before (now with all tests):

Remember - I only waited until the battery is down to 95 %.

Test cases:

1. overclocked to 240 MHz without omapscaler running

2. clocked to 195 MHz without omapscaler running

3. underclocked to 80 MHz without omapscaler running

4. underclocked to 80 MHz with omapscaler running, interval=1000ms

TEST CASES | Time 95% (s) | run time | % time
-----------------------------------------------
Test case 1 | 1583 | 08:47:40 | 95,0 % overclock to 240 MHz manually
Test case 2 | 1667 | 09:15:40 | 100,0 % * default device (195 MHz)
Test case 3 | 2045 | 11:21:40 | 122,7 % underclocked to 80 MHz manually
Test case 4 | 2038 | 11:19:20 | 122,2 % * device underclocked to 80 MHz by omapscaler (interval 1000 ms)

1. The program saves battery when running underclocked (see case 2 + case 4)

2. Underclocking without this program running remains in almost same run time (see cause 3 + cause 4)

3. Overclocking consumes much more battery then Underclocking (see case 1 + case 3)

I hope we get the cpu-load issue and a version without gui running.

But now we may say: It works as it should, congratulations to all helping here.

Special thanks to Oliy - good work.
[Windows Mobile Development and Hacking General] :
Hmmm ... when I try to start Omapscaler on my HTC Tornado Smartphone I just get the Exception "NotSupportedException". Any ideas what I do wrong`?
[Windows Mobile Development and Hacking General] laggflor:
Just as it tells here i think: GetIdleTime (i think it should be this command) is not supported on your device. See http://www.modaco.com/index.php?showtopic=87455
[Windows Mobile Development and Hacking General] kenonbliss:
Autostart

Kudos on the app, I traced it while running a slew of different apps, and it performs like a dream. If it makes the battery run a few hours longer, and supports the apps when needed, it's worth its weight in gold.

So, seeing as how this could be defined as a "must have" in the day-to-day operations, any way you could write it to autostart? Say, once you've set your parameters on the settings page, it just kicks in without a screen when you soft-reset.

Much appreciated.

Testing on Cingular 8125 w/ 2.25 SHIPPED ROM
[Windows Mobile Development and Hacking General] burnout:
hi,

does the prog stil works after sleeping mode ? And after SR ?

Thanks for answer
[Windows Mobile Development and Hacking General] speeraer:
I used v0.11 from the start. However, today I upgraded my ROM with the MrClean AKU2.3 package. OmapScaler works again like a charm...[/quote]

mmmhhhh.... the 100% load issue just returned. without any significant change or action from my side. omapscer just started reading the cpu load as 100% again...
[Windows Mobile Development and Hacking General] laggflor:
I just found a bug:

I tried to clean up my display with my stylus - as I mentioned this stresses my device with constantly 30-40 % cpu load.

OmapScaler is configured to clock to normal speed over 20 % - but it doesn't.

It stays in underclocked mode.

Oliy could you look at this issue? Thx.
[Windows Mobile Development and Hacking General] Guybrush:
Rhynostat calc in a good way CPU load and works on my Wizard... maybe this software use a different way to calc CPU load
[Windows Mobile Development and Hacking General] Oliy:
laggflor,

It will only overclock if the load exceeds the "overclock" threshold.

1. Load is below "underclock" threshold -> underclock

2. Load is above "overclock" threshold -> overclock

3. Load is between thresholds -> retain current clockspeed

I'm still working on making a GUI-less version, hopefully I will have solved the problems with it soon.

kenonbliss, if you put a shortcut in the "\windows\startup" folder it should run it automatically.

Regarding those of you experiencing 100% CPU load, I'm afraid I currently have no solution. The functions I use are exported from coredll.dll and so if they don't work properly there is nothing I can do. I've had a look on the web and can't find any alternative. A fair few people seem to have no problem with it, which is confusing to say the least!

burnout, it should run all the time, including after sleep, but if you do a soft reset you will have to run it again unless you add a shortcut to your startup folder.

Hopefully next release will be soon but I have to pack up my house to move back home and get a job!
[Windows Mobile Development and Hacking General] Guybrush:
maybe it could be implemented with GetThreadTimes() now i'm looking for a new way because getIldleTime isn't implemented in all devices... as mine :cry:
[Windows Mobile Development and Hacking General] laggflor:
Final battery statistics

So, here are some stats to look at:

I did test case 2 + 4 (see earlier post) again - for a longer period.

Here I can see that it saves lesser battery as measured before.

I changed the following:

* I turned off phone + bluetooth during test to have no influence from there

* I tested over night - 12 hours for test case 2, 10 hours for test case 4

Here are the results:

TEST CASES | batt after Xh | run time | % time
------------------------------------------------
Test case 2 | 53% 12:16 | 26:05:57 | 100,0% * default device (195 MHz)
Test case 4 | 64% 09:54 | 27:30:00 | 105,4% * device underclocked to 80 MHz by omapscaler (interval 1000 ms)

You see - we have low battery savings (5,4 %) on my device. I will not make test case 1 + 3 because I dont think the results differ from earlier results that much.

@oliy:

shouldn't the device clock to normal speed if we are in the margins between under + overclock?

You need a job? Is there someone out who wants to hire a programmer? I just opened my own support company but I have almost no work for an programmer right now - sorry.
[Windows Mobile Development and Hacking General] jmel:
unfortunate theres no battery savings then :(
[Windows Mobile Development and Hacking General] laggflor:
There is a small difference between "none" and 1,5 hours. But not really much. Maybe the device gets older ;-)

I personally love the tool because I do not have to make links for single applications I want to run faster.
[Windows Mobile Development and Hacking General] hanmin:
Nice app. Anyway, I'm thinking.

If I were to (say) under-clock it to 80Mhz

(1) What will the clock speed when the device is in sleep/suspend (e.g. by the auto-off feature) mode? Does having a low clock speed during suspend/sleep mode helps in saving battery?

(2) What if you clock it up (say 195Mhz) every time you switch/wake the phone up from suspend mode? How much difference does that make as compared with the omapscaler?

I'm using the omapclock now, which overclock my device upon waking up. However, I didn't really find much difference to it on my daily usage. I even tried the ultra processing power hunger software (e.g. PocketSNES), and overclocking the Charmer doesn't seems to help. As such, since I didn't feel any difference in speed overclocking it, I under clock it. And, as expected, I do feel the difference underclocking it. When I has it at 80Mhz, my screen ripple like an old CRT monitor (some area of the screen), until I push it up to 135Mhz.

laggflor, what software are you using that has noticable performance when overclocked? I even started by tomtom and the 45second start up time doesn't seems to have reduced much on overclocked Charmer.

BTW, how do you see the current clock speed? You look at omapclock, right? Not the Device information under Settings-> System, right? The one at Device information always stuck on 195Mhz.
[Windows Mobile Development and Hacking General] Guybrush:
i tried to ask directly to I-mate for the getIdleTime() problems on 2.18 ROM... i wish they can give me a usefull reply
[Windows Mobile Development and Hacking General] laggflor:
hanmin, you have many questions at once. I will start answering those belonging to me...

Good question - as the overclock-values of omapclock get lost after suspend I think this happens to underclock-values too. But this application downclocks it immediatly before (or after) turning on (if runing on low load). If anyone knows it better kindly let us know.

195 MHz should be default speed after suspend. As mentioned above this application over- or underclocks the device based on cpu-load after suspend. omapclock doesn't. you must set the clock again after suspend (or use a tool to do so).

Best example is "Navigon Mobile Navigator": Without overclocking it was nearly not possible to calculate a route when the car is moving. If I overclock the device to 240MHz this works perfectly.

Good other examples are Skype, and even syncing my media libary to my charmer is faster when the device is overclocked. Even if you have no program running slow - you should see a difference if you are running an "cpu killer application" and get a phone call the same time - sometimes you cannot press the green key fast enough ;-)

If you have no problems on your device - don't overclock!

Right. The device information tells you what type of hardware you are using. These values are constants provided by the device. My cpu e.g. is an OMAP850 @ 195 MHz (as yours).

Look at the Value LCD: here you should have 240x320. Try to turn to landscape mode and start device info again - it shows 240x320 again - but you switched to 320x240.

If anyone finds typing mistakes here: you may keep it.

Any more questions?
[Windows Mobile Development and Hacking General] Oliy:
Ok guys I've created "OmapScalerLite" which runs without a GUI.

It works fine and takes up less memory than the full app, and you can't even tell it's running, it only appears in the extended view of the task manager.

I just have a few bugs to fix, and to test it in the startup folder, and I will release it.

laggflor, thanks for your tests. I guess the battery saving isn't as great as I'd hoped it would be but as we all know how badly the Wizard needs overclocking it seems this feature is still useful.

The device stays at whatever speed it is currently at if the load is between the underclock and overclock margins. This is because at the current speed (whatever it may be) the device is stressed enough that it shouldn't slow down any further, but is not so stressed that it is required to clock up.

guybrush, and others having problems with 100% cpu load, I don't have time to search for alternative solutions for finding cpu load but if you find some (preferably C#) code and paste it here I will have a go at making an alternate class to measure cpu load.

Oliy
[Windows Mobile Development and Hacking General] tracer20:
Hi

What do you think about adding option which will auto overclock when we connect external power?

I think that would be great for car navigation
[Windows Mobile Development and Hacking General] Turist:
will it use cmd line parameters instead of gui?

will task kill be the only one way to shut it down?

Thanks a lot!

I tried it playing mp3 wmp via a2dp. at 195mhz interface respons is too slow, but overclocking up to 240mhz makes difference.
[Windows Mobile Development and Hacking General] Turist:
Battery statistics

for those interested in battery statistics. may be helpfull.
[Windows Mobile Development and Hacking General] Turist:
minor bug (or improvement)

there could be a check, if default clock is changed during normal operation (between under/overclock thresholds) and cpu clock should be adjusted. now it happens

only when reverting from over/underclocked state.

BR!
[Windows Mobile Development and Hacking General] Turist:
and actually it should go to default clock if underclocked and underclock checkbox is unchecked.

ps: i`m not sure, if it is necessary to get rid of gui. it consumes not too much memory anyway but is more userfriendly. maybe only "minimize on startup" or something like this. it works pretty fine, when you add it to exclusion list for app-closing application (handyswitcher or spb+ etc.)

BR!
[Windows Mobile Development and Hacking General] Oliy:
Hi Turist,

Could you please explain exactly what you mean?

Currently, the checkboxes for "overclock" and "underclock" do not work, if you do not want to underclock then simply set the "underclock" frequency to the same value as "default clock".

Oliy
[Windows Mobile Development and Hacking General] Turist:
Hi Oliy :)

it seemed that checkboxes work, but nevermind. i mean, that when i will change default clock from 195 to lets say 210 it will do nothing - just write underclocked in green instead of making my clock 210.
[Windows Mobile Development and Hacking General] Oliy:
Ah, I think what is probably is happening is this:

1. Your device clocks to "underclocked" frequency (for example underclocked = default clock = 195MHz). It will display "default clock" because it compares the current clock speed with the default clockspeed and finds it is the same.

2. You change the default clockspeed to 210MHz (the program remains at 195MHz because it is not under load).

3. The device compares the current speed (195MHz) with the default speed (210MHz) and decides that it is underclocked.

The default clock setting doesn't actually do much, other than be a reference point when deciding "underclocked" and "overclocked", and also a node on the sliding scale of possible clock speeds. It used to be a stable state but is now a much less stable one. Eventually it will have other uses, such as clocking the device back to default when the program is exited.

The program will clock your cpu (depending on load of course) from range of values from underclock =< default clock =< overclock.
[Windows Mobile Development and Hacking General] monamibouli:
I download the log named "OmapScaler v0.11.zip" but when I look in "about", I see OmapScaler v0.1, why ? is it v0.1 or v0.11 ?

Thanks
[Windows Mobile Development and Hacking General] Oliy:
It's v0.11, I just forgot to update that screen :)
[Windows Mobile Development and Hacking General] sporkguy:
Smashing stuff Oliy.

Once you have a polished build up I'll post this on the front page of MoDaCo :)

Cheers - keep it up!
[Windows Mobile Development and Hacking General] Turist:
Hi, Oliy

exactly as you described. But in my opinion this is a little bit incorrect and somehow reduces app usability :)

what should i do, if i decide, that current clock of 195 is not enough and it would be good to have default clock set at 210 all the time? i suggest something like making small button "Set" near the default clock box. actually it will go to desired 210, but only once under/overclocked. it means that now i have to artificially load cpu above overclock threshold to make default clock work.

BR!

PS: just tell me "It`s so because it was the idea" and it will be ok! :)
[Windows Mobile Development and Hacking General] Millenius:
I have an idea to improve omapscaler :

1: add an launch option "-minimize". Because, after a softreboot, you must always minimize the omapscaler

2: add new settings, to set the mhz for some softwares. For example, i use MortPlayer to listen mp3 => The CPU load is between 20 and 37 %, and the omapscaler up and down every time :/

When Mortplayer is running : OmapScaler set 120 Mhz all the time

When Mortplayer is finished : OmapScaler start again the underclock / defaultclock / overclock

Mortplayer is an example, but others softwares must be settings in OmapScaler.

(sorry for my bad english)
[Windows Mobile Development and Hacking General] Oliy:
Milennius,

I have already made a program "OmapScalerLite" which does not have a user interface. I will release it soon but at the moment it has some bugs which I need to sort out before I release it.

As to having specialised program settings, this would

1) Require lots of hard-coding for which I don't have time for

2) Defeat the object of the program - to adjust clock speed based on load only. You are suggesting it should be changed depending what program you are running, regardless if it requires it or not.

It may be possible that I can make a generic way for you to specify clockspeeds for particular programs, which will make this program more complete. I just don't have the time at the moment however!
[Windows Mobile Development and Hacking General] Turist:
Oliy,

here some strange situation:

i have omapscaler in autostart and always when it starts it shows 100% load. even after all the plugins etc finished startup. if you look in settings - you will notice that overclock checkbox is unchecked, but program says overclocked and clock is set correctly. if you just check overclock checkbox cpu load drops in a second and everythig goes fine after it.

just my 2c

BR!

PS: this -minimize option would be not bad really
[Windows Mobile Development and Hacking General] Oliy:
I've had an extremely unproductive hour or so trying to solve some of the problems in OmapScalerLite (non GUI version) and not solved any of the problems, which are:

1. There seems to be a small memory leak somewhere, may just be the garbage collector being lazy.

2. There is nothing to stop multiple instances being launched.

3. There is no way to close the program.

In regards to 2 and 3, I hope to be able to solve these together by terminating the program when it is run a second time.

I have tried using CreateMutex but it doesn't seem to work (2), and I do not know how to kill the app which holds the mutex (3).

If anyone knows how to accomplish this please let me know.

Anyway, attached is OmapScalerLite v0.1. It has no GUI and therefore takes less memory. It will be visible in the alternate view in task manager, and you can only stop it from there.

Place the exe in the same directory as OmapScaler.exe and it will read the same config.xml file (use OmapScaler to set up the config.xml first).

Oliy
[Windows Mobile Development and Hacking General] ghazaly:
Suggestion

Hi all...

first of all, thanks Oliy for coming out with this extremely useful program. I am currently using version 0.11 with omapclock 0.2, and it seems to work OK. One slight problem if I leave my Wizard connected to my PC via USB for recharging... the phone will soft-reset after a while... don't know why :?

I have a suggestion for the "Clock threshold" setting. I think there should be two separate settings for "overclock" and "underclock", because at the moment, I see that the speed fluctuates a lot when I'm using my Wizard. When I start to launch an application.. the clock will shoot up, and then a few seconds after that (when the load settles), the clock returns back to default or underclock (if i enable underclock).

What I think should happen is that my Wizard would go into overclock mode when i start to use it (launching an app)... and should stay overclocked until I stop using it (idle) for a certain period (e.g. 1 mins or 30secs)... not immediately after I launch an application and wondering which document I want to open
[Windows Mobile Development and Hacking General] hanmin:
Overclocking a Charmer

As there is a new ROM for the Charmer, I ought to upgrade the ROM and reinstall the system. As such, I did a clean system benchmarking on the old and new ROM in both defaul and overclocking condition to see the difference in performances. Attached is a xml file with details of the benchmarking.

The comparing system, Magician index is taken from this thread and the iPaq3600 index/results are from Spb website.

The conclusion of this benchmarking are:

(1) Charmer is a slow machine*, except for the graphics processing power

(2) There are significant improvements overclocking the unit

* Note: Some may say that since Charmer is using OMAP processor, it is un-fair to judge the unit based on any means of benchmarking that doesn't utilized the advantages of OMAP. However, there are some of the SBP benchmarking actually uses the built-in application (e.g. Word, IE, File Exp) and none of them (except the graphic related one) score less than reference unit (iPaq). If the applications that came with the unit (of which you are using) are not utilizing the advantage of the OMAP, the unit is in fact slow.
[Windows Mobile Development and Hacking General] temiatwork:
Hello Oliy and thanks for taking time developing these tools, (same goes to all you guys in this forum).

unfortunately, when i installed and load OmapScalerLite at startup it gives me several errors....1st softreset, my screen went blank and i was forced to press softreset again. 2nd problem, my calendar display does not show from my customized today screen but the space is there and if you click it, the calendar opens. btw, you mentioned that this can be stopped fom the task manager? it also does not appear there. so, there is no way of me telling if it really overclocks or not if i run an app. unless i use the GUI ver.

i think i will play some more with OmapScaler instead and wait for further version or maybe running OmapClock @ 240 is still the solution for me, i always carry a charger anyway. its the extra speed is what i need.

More power to all you guys!!!