[APP] WiMoSpeed: [2011-09-20] V1.09

Search This thread

iwfratz

Senior Member
Oct 14, 2008
143
248
WiMoSpeed and Blackstone

As some users reported there is a problem with WiMoSpeed and Blackstone-devices. To solve the problem I need more information, because actual I have no clue why it happens.

  • Are there any Blackstone users without speed cut in half after a sleep ?
  • Are there any Blackstone users using a radio-version higher than 1.17.25.09 (e.g 4.49.25.x) ? Are you having this problem too ?
Please report your ROM and RADIO version.


The best way to work this out would be a Blackstone-device I could work on, but my device is a Rhodium.
  • Anyone out there having a Blackstone and willing to lend it ?
  • Or are there enough Blackstone users donating to buy a used Blackstone ?
 

dschoms

Senior Member
Mar 23, 2010
87
9
Denver
I ran SKTools benchmarks using Win Mo Speed. The fastest that I have been able to achieve is 787.2, anything above that results in an instant freeze. The attached table shows the results under WMS and OCT under which 768 was the maximum achievable speed. The results are pretty consistent with a couple of exceptions mostly with regard to the SD card (16gb class 6) and the SKTools loading (it's on the SD card, thus consistent). Because of this inconsistency, I ran the 787 benchmark several times and while the numbers bounced around, the range didn't vary much.

Since the majority of my programs are loaded on the SD card, I'm trying to figure out if the slower times are having an impact on performance. If those of you who are more experienced than I have any thoughts, I'd appreciate you sharing them.

As they say in the NFL, upon further review, the SKTools load time in the attached table was valid at 787.2. When I backed down to 768, applications loaded noticeably faster. The load time at 768 was 5753 ms and at 787.2 it was 8514 ms. At 528 it was 6221 ms. Keep in mind that every time the benchmarks were run the numbers were a little differedt, but the spread was pretty consistent. I'm running my Sprint TP2 at 768 and am happy.
 
Last edited:

Monster Jacky

New member
Dec 20, 2010
2
0
Having Touch HD problem with speed cut in half.
OS Version: 5.2.21877
Manila: 2.5.19211619.0
Radio: 1.09.25.14
Could not remember what ROM did i download, sorry...
 

WallyGator

Senior Member
Jan 23, 2009
118
10
Outer space
As some users reported there is a problem with WiMoSpeed and Blackstone-devices. To solve the problem I need more information, because actual I have no clue why it happens.

  • Are there any Blackstone users without speed cut in half after a sleep ?
  • Are there any Blackstone users using a radio-version higher than 1.17.25.09 (e.g 4.49.25.x) ? Are you having this problem too ?
Please report your ROM and RADIO version.

My ROM: [WWE]blackSTONEhenge™HyPer v3.6.28244 (going to be upgraded to 3.9.28244)
Radio: 1.17.25.09
Msm7kCpuSpeed overclocks without problems: after waking up speed is as was set.
 

James62370

Senior Member
Feb 22, 2007
909
102
As some users reported there is a problem with WiMoSpeed and Blackstone-devices. To solve the problem I need more information, because actual I have no clue why it happens.

  • Are there any Blackstone users without speed cut in half after a sleep ?
  • Are there any Blackstone users using a radio-version higher than 1.17.25.09 (e.g 4.49.25.x) ? Are you having this problem too ?
Please report your ROM and RADIO version.

I am using [WWE] |Dec 20| Energy 6.5|21916 / Sense 2019 with SenCity Theme
Radio 1.17.25.09

I too have the above issue with speed cut in half after wake. Also since my previous question went unanswered, I will try one more time.

When using WiMoSpeed, and selecting the value for a new CPU-Speed, if I exit the application, is my Blackstone still overclocked, or do I need to keep it running?

Thanks for your help.
 
  • Like
Reactions: trevoroni

jruss08

Senior Member
Jun 7, 2010
59
4
Hi,

I am using a program called speedbooster 2.0.020
It's can show you after short benchmark if your speed is better or stayed the same.

About the temp, there is no increase, I am using program called tbattery that comes with NRG rom.

About stability,
If all works fine then Phone is stable.
If It's stuck on any condition as power plug in,
Missed call, just after a finished call, on wake up manually,

Then it's bad!

Here is the program
View attachment 474245

I get score of 5.80 on 528 Mhz , CPU 5.70
And Score of 6.10 on 691 Mhz , CPU 6.45 !!!

And phone works allot faster then on 528 :)

^ I'm using the same! I agree! My HTC Imagio (Whitestone) is running smoothly at 787.2 MHz. With speedbooster, I have an CPU score of 7.13 up from 5.95 @ 528 MHz!
 

James62370

Senior Member
Feb 22, 2007
909
102
Yes your device is still overclocked, WiMoSpeed does not need to run after setting.

Thank you for your response. Hopefully the issue with half speed on wake for our Blackstones can be resolved :)

Thanks again for your application and I hope you and your family have a Happy, Healthy & Prosperous New Year!
 

nerys71

Senior Member
May 13, 2008
2,107
422
wow thank you so much. I worked it up to 710 and it is VISIBLY SNAPPIER and no bad behaviour so far.

WOW what an improvement. that "little too much sluggishness" is nearly gone now!! (touch pro 2 sprint 6.5 stock rom cht2.0)
 

hobes128

New member
Dec 13, 2010
2
0
I'm running this on my Blackstone. When it keeps the settings (672Mhz), it's snappy and quick.

However, it seems to change the speed down to 326.4 Mhz by itself for no apparent reason.

What am I doing wrong?

I've been trying WiMoSpeed on myphone, and having the same problem as described above.

Phone: HTC Touch HD
ROM: Energy rom Dec 13
OS version 5.2.23151 (23151.5.3.12)
Manila Version 2.5.20191914.0
Radio version 1.09.25.14

I can over-clock up to a max of 614.4 Mhz (multiplyer on 32), but above that, my phone locks up straight away, and I have to soft reset. I did some benchmark testing using the benchmark option in coreplayer, and can see higher scores once over-clocked. I saw other people in this thread saying they are getting stable performance on their tough HD at 670Mhz or above, but mine definitely wont run that fast (I guess there's nothing I can do about that?)

I've added a short cut to my start-up folder, so it over-clocks as soon as I power on my phone.

I've spent a bit of time tonight trying to work out exactly what circumstances cause the clock speed to half. At first I thought it happen every time I put my phone onto stand-by (by pressing the button on the top of the phone), but that is not the case. It only does it intermittently.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 81
    CAUTION !!!
    - USE THIS TOOL AT YOUR OWN RISK !!
    - Overclocking your cpu may damage your device.
    - Before autostarting the app be sure that your device will not hang.
    - backup is always recommended !!


    DESCRIPTION :
    WiMoSpeed lets you change the CPU-speed. In opposite to other tools, even to the predecessor OverClockTool (OCT), it manipulates the values WM uses for clock control. So it works reliable on battery and AC without any scripting or active components.


    USAGE :
    - WiMoSpeed needs .NET CF 3.5
    - Download and install the CAB
    - Start WiMoSpeed.exe. If it reports that it cannot identify your ROM: read LIMITATIONS/PROBLEMS
    - Select Speed
    - Set Speed
    - Exit WiMoSpeed.exe
    - Your device still runs with speed you set


    Auto start WiMoSpeed to desired speed:
    Note: one advantage to installing WiMoSpeed to storage card is that if device ever won't boot at new speed, the card can be removed and the device will boot at original speed.

    1. MOST IMPORTANT: Ensure WinMoSpeed will function safely on your device at desired speed by using it for several days while setting the speed manually.
    2. Run WiMoSpeed, set to desired speed, click "create link with current settings". This will create a lnk file under the install directory, usually "/Program Files/WiMoSpeed" or "/Storage Card/Program Files/WiMoSpeed".
    3. Copy that lnk file to the "/Windows/Start Up" folder.
    4. Reboot device.
    5. Run WiMoSpeed to verify "current CPU speed" is correct.

    LIMITATIONS / PROBLEMS
    I am working on this in my spare time, beside my job, my mate and some other interest. I own a Rhodium-device only, so I can not reproduce errors on other devices and debugging is very difficult and time-consuming. Be patient.

    WiMoSpeed supports Qualcomm MSM7200 (and compatible) and is actually limited to ROMs of
    • Rhodium,
    • RhodiumW
    • Topaz
    • Blackstone
    • Whitestone / Imagio
    • Raphael / Fuze
    • Diamond
    • Kovsky / Xperia
    • Quartz
    • Pure
    • test (!) support for Jade, Panther, Mega and Rose

    !!! If you have a device listed above and WiMoSpeed could not identify your ROM please post here what part of your ROM WiMoSpeed couldn't identify (OEMXIP and / or RADIO-ROM) and include a download-link of your ROM (OS, RADIO) !!! Otherwise I will ignore your post. Thank you.

    If you are going to report an error please include the ROM identification of WiMoSpeed shown in the GUI (e.g. OS "Rhod016 / PLL2", Radio "4.49.25.91")

    TECHNIQUE
    Basically WiMoSpeed is hardware-independent, because it lets WM change clock speed. But I couldn't get WM to switch the clock reliable on request so WiMoSpeed had to switch the clock registers itself on setting a new speed.
    Therefore WiMoSpeed depends on CPU-hardware, RADIO- and OS-ROM.

    Raising or lowering cpu speed didn't change battery drain or device temperature noticeable. So there isn't dynamic clocking in WiMoSpeed, but WM is still controlling and changing cpu-speed on battery.


    thanks to
    -all donators for the support
    -eboelzner for Sense UI SDK
    -dmvandijk for the icon
    -the internet ;)

    TODO-LIST
    • ?

    Support for
    • non-HTC MSM7200/7201
    • non-MSM7200/7201
    devices is uncertain.

    Please do not mirror WiMoSpeed !

    Version 1.09
    - added support for more OEMXIPs (1xRhodium, 1xTopaz, 1xRaphael)
    - added support for more radios (1.11.30F, 3.54.25.25, 1.20.OliNex)
    - PINVOKE error should be solved (moved to another compiler)

    - test (!) support for Jade, Panther, Mega, Rose and Radios

    Version 1.08
    - added support for more OEMXIPs (1 x Diamond, 1 x Blackstone)
    - added support for more RADIOs (0.93.25.NS16, 1.02.25.32, 1.10.25.18, 1.11.25.71, 1.11.25.76)

    Version 1.07 (3.233 views)
    - set os-versions in CAB-Information-File, maybe it solves installation problems
    - added support for more OEMXIPs (1 x Topaz, 1 x Blackstone)
    - added support for more RADIOs (1.02.25.28)

    Version 1.06 (6.000 views)
    - checks ROM-identification at startup
    - support for Pure
    - added support for more OEMXIPs
    - added support for more RADIOs

    Version 1.05
    - support for Quartz
    - added support for more OEMXIPs
    - added support for more RADIOs

    Version 1.04
    - blackstone problem should be solved now (tested by tsalta with Blac016 / 1.17.25.09)
    - added support for more ROMs
    - support for Raphael / Fuze, Diamond, Kovsky / Xperia
    - GUI shows ROM identification

    Version 1.03
    - blackstone problem (speed cut in half after sleep) should be solved
    - added support for more ROMs
    - changes in GUI (you have to create your links again; old ones starts the GUI only)

    Version 1.02
    - added support for more devices
    - added support for more ROMs

    Version 1.01
    - added support for more OS-ROMs
    - added support for more radio-ROM
    - new function: restore default speed (528 MHz)

    Version 1.00
    - Initial release
    - Rhodium, RhodiumW
    17
    radios
    • 0.93.25.NS16
    • 1.00.25.03, 1.00.25.05, 1.00.25.07, 1.00.25.08, 1.00.25.16
    • 1.02.25.11, 1.02.25.19, 1.02.25.28, 1.02.25.32
    • 1.02.35.31
    • 1.08.25.08, 1.08.25.20
    • 1.09.25.07, 1.09.25.08, 1.09.25.14, 1.09.25.23, 1.09.25.23M, 1.09.25.35
    • 1.10.25.18, 1.10.25.25
    • 1.11.25.01, 1.11.25.71, , 1.11.25.76, 1.11.30F
    • 1.12.25.16, 1.12.25.16D3, 1.12.25.16DE, 1.12.25.19
    • 1.13.25.24, 1.13.25.55
    • 1.14.25.05, 1.14.25.24, 1.14.25.35, 1.14.25.55
    • 1.15.25.14, 1.15.25.55
    • 1.16.25.48
    • 1.17.25.09
    • 1.20.OliNex
    • 1.40.00WF
    • 1.87.00WV
    • 1.88.07WV
    • 1.92.00WV
    • 1.96.00WF
    • 2.05.00WV, 2.05.75WVL
    • 2.18.00WV, 2.18.02WV
    • 2.21.00WV
    • 2.23.00WV
    • 2.25.00WVL, 2.25.02.WVL
    • 2.30.00WV
    • 2.32.00WF, 2.32.00WU
    • 2.35.00WV
    • 2.37.00WV
    • 2.49.25.204
    • 3.43.25.19, 3.43.25.19DE
    • 3.44.25.27
    • 3.45.25.14, 3.45.25.21
    • 3.46.25.18, 3.46.25.30
    • 3.54.25.25
    • 4.46.25.24
    • 4.47.25.24
    • 4.48.25.20
    • 4.49.25.05, 4.49.25.17, 4.49.25.57, 4.49.25.77, 4.49.25.88, 4.49.25.91, 4.49.25.94, 4.49.25.95
    • 1.96.10WU
    • 2.23.00WU
    • 2.32.00WU
    8
    reserved for the OP
    7
    new version released

    • set os-versions in CAB-Information-File, maybe it solves installation problems
    • added support for more OEMXIPs (1 x Topaz, 1 x Blackstone)
    • added support for more RADIOs (1.02.25.28)
    6
    new version released

    WiMoSpeed V1.05
    • support for Quartz (3 OEMXIP)
    • added support for more OEMXIPs (5 x Raphael, 5 x Diamond, 1 x Kovsky)
    • added support for more RADIOs (1.96.10.WU, 1.14.25.35, 1.02.35.31, 1.08.25.08, 1.15.25.55, 1.02.25.31, 1.12.25.19)

    Hope, that I got all ROM-links posted here, there were quite a lot. If I missed one, I am sorry. Please post again.