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

Search This thread

Z=A

New member
Jul 20, 2009
4
0
thanks for the great work and the attrative tool. But my HD can't be recognized by OEMXIP. Would you help?

Roms are in below link:


h t t p://u.115.com/folder/f977f866ac3
 

iwfratz

Senior Member
Oct 14, 2008
143
248
new version released

I released 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)

but no solution for the pinvoke-problem.
 

markiarom

Senior Member
Aug 23, 2009
366
83
it doesn't work on my htc touch 3g with original radio, rom etc.
any suggestion?
it say that it can't find radio and oemxip version... sigh sigh

i read on older posts that i can change the oemxip and radio key of registry value, but i don't know what value i have to put... please help me thanks
 
Last edited:

Oby™

New member
Sep 3, 2009
1
0
Thanks!
HTC TOUCH HD 8282
Current speed 614.4 Mhz-OS Blac016-Radio 1.17.25.09
Do not work higer to 614.4 Mhz,crashes and reboots.
 

markiarom

Senior Member
Aug 23, 2009
366
83
614 mhz imho is too slow... maybe the program don't work great...
i could try on my touch 3g because sometimes,changing oemxip and radio key value, it work, and i had successfully go up to 700...
 

LoopyLoo

Senior Member
Jul 5, 2007
99
0
Any Real Effect?

As always, I applaud and thank the author(s) of any software(s) posted on the XDA community site. And I was particularly happy to learn that the issues surrounding the Touch HD had now been solved.

I like my HD and have had it almost 2.5yrs, but I've always wished it was just a little faster. So it was with great glee that I installed WinMoSpeed1.08 on my device just recently...

After my initial pleasure in noting that the app actually recognised my KWBR ROM, I was then a little disappointed to discovered I couldnt get beyond 614MHz (my HD just froze any faster than that). OK, I'm used to overclocking h/w and therefore quite realistic about my expectations. After all, 614MHz is still a 16% boost so not to be sniffed at...

And yet, whatever I do on my overclocked HD, which ever app or task I run, whatever laggy button sequence I press, absolutely NOTHING seems to run/execute/work any faster than w/o overclocking!?

So!...

Have I missed a trick here?... Or is it the case, maybe, that (in the HD at least) the overclocked h/w is not the actual bottleneck in the HD's performance???...

Loopy
 

michoob

Retired Recognized Developer
Dec 19, 2008
1,270
65
Brussels
@LoopyLoo: you can find my feedback in the following post. I am actually now at level 33 (633MHz) for more stability, because at higher levels, Opera 10b3 freezes from time to time.
 

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.