yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
But there's no going back, if it's in Startup and it doesn't fly right on someone's phone. The OS won't load--I think some users install WinSpeed on the sd card, then put speed link in Startup. If there's a problem, they can delete the WinSpeed directory on sd card, rendering the Startup link useless.

I live dangerously, installing on phone memory and linking 748 speed in Startup :)

But your OS is popular, with many different makes of phones, and some phones might not load at a speed you choose.

Just worryin',

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] mmalka:
WiMo allows you to create a link for a set speed. Then I put that link in the start up folder.

However, I would recommend that you set it at the default (non OC) speed, and let each user check how high they want/can go. Different devices (even of the same model) are experiencing success (or failure) at different speeds.

I could go up to 748MHz. At 768MHz I had issues, while other people did not.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] hasbrone:
Video H.264

He who tested the HD video (H.264)?

Here is my configuration:

Video

Codec: H.264

Size: 800x480

Bitrate: 512 kbps (mp4 iso v.2)

Frames: 29.97 fps

Audio

Codec: MPEG2/4 Audio

Frequency: 48000 Hz (16 bit)

Bitrate: 160 kbps

Channel: Stereo

Someone used more Bitrate?, To much?...

THANKS.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bipinsen:
I disagree with this. With the new set of ROMs, the speed is so far improved that I have stopped using this app. There is absolutely no discernible difference in user experience with it on or off.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Puff1911:
Hmm i say you cook it in.. but leave the speeds at default.. just have the application available..

That way no one can come back and throw out complaints about any issues with the overclocking..

Leave it for the individual users to configure themselves.. it's simple enough to do yourself :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] awalt:
My feedback would be not to cook it in. I run at 748, and have WinMoSpeed installed to SD card, so if I ever hose it or clock too high I can boot without the SD card and fix things. It's easy enough to install and drop a link in Startup using XDA_UC. My .02..
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
Hmm then maybe we should create a little FAQ on how to install it on the SD card and use it properly.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] mmalka:
The information is already on the WiMo thread. I did not add to the FAQ as it does not pertain to the EnergyROM specifically.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] awalt:
FYI I just finished flashing to the Energy.RHODIUM.29020.Sense2.5.Cookie.2.0.Apr.26 ROM with no problems!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] gregb882:
The biggest difference I notice is when turning off something, like WiFi or getting out of Opera, then quickly trying to swipe to a different page. It's fairly jerky and hesitant without WinMoSpeed, smooth with - at least on my TP2. Otherwse it's pretty tough to see a diffrerence (and I really don't chew through the battery much faster). Oh, start up is about 3 seconds quicker, too.

I do use WinMoSpeed at start up, but from the storage card. I like the security of being able to pull the card out in the event of some problem, although that has not happened to me; so I guess I'd vote for not cooked in.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bipinsen:
Three whole seconds? One one thousand.. two one thousand.. three one thousand... :p

Lets see.. if I restart my phone 10 times a day, every day for the next 30 years, I'll waste about 4 days of my life. Cook it in, I say! :eek:

Kidding aside, you summarized the user experience pretty well with the app.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bipinsen:
Caller ID screen overlap

Just noticed this - pretty sure it wasn't there in other versions. When I get an incoming call, I can see the graphics and text from my home screen. Bug? Feature?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
Hmm probably because Ameba isnt positioning the screen anymore. Anyone else seeing this ?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] awalt:
Yes it happens on mine too, didn't notice it. Good catch!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
uTask Position Fix

Start, Tools, X Button Settings, Position fix tab: check "Enable Position Fix" and check "Automatic Mode"...soft reset...

That fixed it for me.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] hefman:
Yep -- one drawback to not using AMeBa. There is another utility out there that only does screen positioning, but I don't recall the name.

Edit: Just noticed WMG's post...

Also, I'm somewhat against cooking in WinmoSpeed -- only because a user who erroneously sets up a startup link for a speed that is too high may be facing a hard reset. The storage card install will always give the user an easy escape route...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] hefman:
Wow. I didn't know uTask had a position fix. Nice find...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bipinsen:
Nice. That did it! Thanks!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Monfro:
I think it is better not to cook it, or to cook and leave it at standard speed.

Devices are different...and i have read of some phones that can oc only to 690 for example; so there can be devices that will not launch Windows and freeze forever.

A lot of people also is using Android...and they need to run at stock speed (also i sometimes forget to low down to stock speed before launching Android): if they don't know how to lower their speed they will freeze the device everytime and we will have a storm of people writing about this.

And the most important thing: i think that Netripper's Msm7kCpuSpeed is really faster than WiMoSpeed.

For sure WiMoSpeed is easier to use...but Msm7kCpuSpeed makes TP2 raging :)

If you want to try, here are my files (speed 748):

1 - Install 01_Msm7kCpuSpeed_v2

2 - Install 02_SetCpuSpeed-1.0d: do the settings to defaults (we will change them in step 3) and click NO when it ask to soft reset.

3 - Import with Regedit 03_speed748noSOD.reg (inside the attached zip).

4 - Soft Reset and enjoy pure speed!!

02_SetCpuSpeed-1.0d will install some of its files to storage card: you can pull out storage card & reboot to be able to regedit & lower your speed.

To change the speed:

[HKEY_LOCAL_MACHINE\SOFTWARE\Msm7kCpuSpeed]"PerformanceLevel"

Here are some examples of PerformanceLevel (decimal):

41=787 MHz

40=768 MHz

39=748 MHz

38=729 MHz

37=710 MHz

36=691 MHz

35=672 MHz

34=652 MHz

33=633 MHz

32=614 MHz

31=604 MHz

30=576 MHz

29=556 MHz

28=537 MHz

Leave the other parameters as they are, to avoid sod and freezes.

NOTE: The overclock will start some seconds after the full boot of the phone.

To control the speed go to Start/Tools and launch Msm7kCpuSpeed, then Exit (don't change the speed from here).
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
Yeah I didnt want to turn on utask's automatic positioning out of fear that it might screw things up. I will turn it on in the next batch of ROMs. Until then... you guys can live with it :D :D:p
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
So if one is using Gen.Y Dualboot and we have the speed set at say 768 in WM...and we soft reset and want to go directly into Android via Gen.Y, after the soft reset, is the speed at the default (528) so that Android will boot? Or in that same scenario, do we still have to speed-down to 528 before a soft reset to make sure the device is at default speed before booting into Android?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] awalt:
Fixed it on mine too. Is this something we should make a note to apply with each new ROM, or is there a setting we can apply via XDA_UC, or will it be baked into the next ROM? [Edit: never mind - saw NRGZ28's later post he will cook it in at a later point. Thanks...]
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Monfro:
I use Gen.Y Dualboot too.

Msm7kCpuSpeed will start after Windows is fully loaded, so there are no problems choosing Android with Gen.Y Dualboot.

In 03_speed748noSOD.reg a lot of important parameters are set, to improve performance and stability of the application. Now it is really perfect (no sod, freezes or yo-yo).

There are only 2 things that can be changed without problems:

- speed (as i wrote in the other post)

- boot time

You can change Boot Time this way:

HKLM\Software\Msm7kCpuSpeed

I have set Boot Time to 90000, you can set to a bigger number to have Msm7kCpuSpeed start later (for example 120000): it is important that the phone fully boot up before the OC kicks in.

Test it and let me know if you see a big difference in speed, as i.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] dsdmarin:
Compact Start Menu

When I try to use the compact start menu, It will not start up after reboot. Sense works fine but I am not able to use the start menu when compact is selected. I had to switch back to normal menu. Does anyone else have this issue? It worked fine for me in the 3-30 Rom

Thanks
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] gregb882:
Yeah, I was really agreeing with you that the current ROMs are darn fast all by themselves, but I do see enough performance improvement that I like to use it because I don't see much of a hit with battery life.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Monfro:
It is because some entries in the script that changes menu still refers to Ameba.

NRGZ knows this and will fix for the next release.

Workaround:

1. total commander, windows\utaskconfig, windows key, configure key tab, Execute, (set to) windows\start.exe, save

2. settings, startmenu switch, run the one you want, reboot
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] motisu:
Because WinMo doesn't need any reg entries, I installed it once on my SD and left it there ever since. I copy the 768Mhz link to my startup via XDA_UC after every HR an it runs fine without any installation. 1 less .CAB to install after HR. :),

My recommendation would be to create a subdirectory of all the different speeds, and then let the end user copy his choice to the startup directory.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bipinsen:
And I was fully agreeing with you! Just couldn't help having a little fun with numbers! :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
WinStart on Energy ROMs

For all you WinStart users on NRG's ROM...new release v2.4 out

here
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] awalt:
One thing I have noticed that I'll offer for comment...on the Apr 23 ROM (which I believe used PagePool setting of 20, as does Apr 26), RSS Hub would not seem to stay in memory and download new RSS feeds on its time schedule, and Gmail mail would not stay in memory (I noticed because the folder I wouldn't move" messages to always was reset back to default of Inbox and I had to click another). On a lark, when flashing the Apr 26 ROM, I set the page pool to 18 first, and I noticed both are staying in memory - RSS Hub is downloading on schedule, and Gmail has the last folder I used still selected. It's not a big thing, I more mention it wondering if I have properly identified cause and effect, that the page pool setting is likely changing what stays in memory?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
Awalt explores an interesting idea. For the 4/26 ROMs, I too have set the pagepool to 18. I did so for the extra ram, and I do not notice a diminishment in speed. Since I don't use the same scheduled tasks, I can't reproduce his successes, but over all, I prefer an 18 pagepool.

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Joe Bleau:
Re: ROM Apr.26 Broken Start Menu Layout Switch & Fix

It's not only the QuickMenu that's not working, it's the same for "Panel" & "Sense", etc. when using the Start > Settings > Start Menu Layout Switch in the Energy Apr.26 ROM. Also, if uninstalling WinStart 2.3 (w/ Windows Start menu disabled to save 20MB of RAM compared to stock Apr.26) & rebooting, there is no Start menu at all.

Thanks Monfro for reposting teradog's fix from the CDMA NRG ROM in the ppcgeeks' forum:

Edited thanks to the post by monomer888 below. No need for Total Commander in Apr.26 before switching to alternate Start menus:

Create a quicklink on Home to "X Button Settings" to open UTaskConfig.exe (or to uTask if you fixed the link's label & icon). You'll need that if you are stuck w/o a Start menu later when tapping on the soft Start button.

Start > Settings > Start Menu Layout Switch and select Panel, QuickMenu (a.k.a.Compact in NRG's Switch), "Sense" or "Normal". Dunno about 'List view".

Start UTaskConfig.exe with the link created above.

The "Windows" Key is highlighted by default, if not do select it.

Tap on the ">>" box top right, select Execute and type exactly:

For Panel: \Windows\Start.exe and hit Save.

For QuickMenu: \Windows\quickmenu.exe and hit Save.

For "Sense": \Windows\sensemenu.exe

For "Normal", the default Windows Start menu RAM hog: select "Standard action" instead of Execute.

If you already switched the Start menu to Panel or QuickMenu, etc and are stuck w/o a Start menu at all then use the quicklink to UTaskConfig.exe that you created above.

*****

Extra Links with uTask

As you can see in the screen capture above, you can also map Close key (long press) and Home key (long press) in UTaskConfig.exe so besides the 2 links in the uTask button, you can add 2 other additional links. Home key (long press) opens Comm Manager by default in Apr.26 ROM as mentioned previously but what UTaskConfig.exe labels as Home corresponds to the soft Start key in the Apr.26 ROM.

Maybe in the next ROM that label could be changed to Start soft key or Windows button softkey and the "X Button Settings" in Start > Tools could be renamed uTask or uTask Config for clarity? It would it easier to talk about it in the thread also IMO. Same for the label "Compact" in the Start Menu Layout Switch that could have the same name as the app it's selecting: QuickMenu.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] vinceweis:
I found it interesting that after setting my device to the compact start menu, I also had the problem with the windows icon on the screen not opening the compact start menu. The hardware windows button would work fine. After using the workaround above, the hardware button opens the compact menu and the onscreen icon open the panel menu. I kind of like having both at my fingertips. The compact start menu gives me access to settings and the panel gives me a better graphical interrface to programs, games, and others. I have not seen much loss in available RAM.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] monomer888:
I flashed the Apr26 29020 Standard ROM to see what it's like.

For some reason I found changing the file to "\windows\start.exe" only brought up the Panel menu even if I used the Settings > Start Menu Layout to CSM or Sense (similar to what vinceweis posted whilst I was typing this message). For the CSM to show properly I had to specifically tell utask to execute "\windows\quickmenu.exe".
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] vinceweis:
I'm not sure exactly what I did to get both available. I started with the compact start menu enabled but saw that the screen icon did nothing. I then only did the first part of the "fix". I did not try to select a different start menu after that. It probably buys me nothing having both available but it's fun to play with. I like overloading my phone with so much stuff that it starts to choke.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] monomer888:
I think I know what happened. The option to enable compact start menu correctly bound the CSM/quickmenu to the windows hardware key.

The fix as described tells utask what to launch when the software windows key is pressed. As we set it to execute "start.exe" it launches the Panel menu. I'm assuming the script is meant to change the "start.exe" file to whichever menu is chosen in Settings, but for some reason it doesn't so the Panel menu is what we get for the software windows key unless we change it manually ourselves.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Joe Bleau:
Re: ROM Apr.26 Broken Start Menu Layout Switch & Fix

Hey, you are right. :p After selecting QuickMenu & rebooting, the soft Start button opens Panel if uTask is set to \Windows\Start.exe in UTaskConfig.exe. Editing it to \windows\quickmenu.exe does open QuickMenu.

It's the same for the "Sense" menu. After selecting it with Start Menu Layout Switch & rebooting, soft Start still opened Panel. Editing uTask to \windows\sensemenu.exe fixed it. I will edit the post above, thanks! Done & includes "Normal" Start menu setting.

Is all this related to the script file \windows\stc.mscr and what it does to "Security\Shell\StartMenu"?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] GT247:
I have the March 8th ROM installed with the start menu on the top... on my today screen I have two rows of quicklinks displayed, and obviously of I flick up the screen it reveals a full panel of quicklinks and the clock leaves the page..with the clock displayed and I flick the quicklinks right or left they scroll beneath the clock as the clock does not leave the screen until I flick up or down...I'd like to know if the new ROM version mainains this behavior of the quicklink pages
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
Why would that change ? Does it ever change ?! :rolleyes::confused:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] GT247:
I tried a sencity ROM of yours and as I scrolled the quicklinks to the right, the clock left the screen and the entire quicklink page was displayed, I thought at that time that that was how the new ROMs were designed so here I am now asking my stupid questio....waittasec, I just caught myself almost making an incorrect staetement...I remember now...there are no stupid questions....just inquisitive idiots...lol
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
Is 748 your fastest/stable speed?

I uninstalled WiMoSpeed, soft reset, and then installed your two cabs and reg edit.

I tried at 787 first (that's where I would run WiMoSpeed). I maneuvered around a bit...confirmed the speed by selecting Msm7kCpuSpeed in Tools folder...REALLY fast...but I let it sit for a couple of minutes and when I tried to wake...no luck...SOD. :eek:

I rebooted and went down to 768...maneuvered around a bit...confirmed the speed by selecting Msm7kCpuSpeed in Tools folder...still really fast...but I let it sit a couple of minutes and when I tried to wake...no luck...SOD again. :eek:

So...reboot...down to 748...maneuvered around a bit...let sit a couple of minutes...all seems fine...woke up!

BUT...

As I was typing this above, I let it sit (still at 748) for about 3-4 minutes...and I tried to wake phone up...no luck...SOD. :(

I followed your instructions to the letter in this post, only changing the speed in the registry: [HKEY_LOCAL_MACHINE\SOFTWARE\Msm7kCpuSpeed]"PerformanceLevel"

I do agree that Msm7kCpuSpeed did seem faster than WiMoSpeed comparing speed-setting to speed-setting (i.e., 787 with Msm7kCpuSpeed was FASTER than 787 with WiMoSpeed; same at 768)...but down to 748 in Msm7kCpuSpeed seemed to be the same as 768 in WiMoSpeed.

Not real sure why I was getting the SODs?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
The option you are referring to is a feature of CHT2.0, not the ROM. You can enable or disable that feature in the CHT2.0 ROMs by going to CHT Editor > Quicklinks > toggle Independent page count.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] GT247:
Thank you Mr Cajun :) I wasn't sure if I was explaining myself very well...the rom I have now is cookies 1.8.5.1 ...I think I'll load the new rom and see if it does it and if it doesn't, reload the rom I have on the phone now and STFU and not bother folks...lol
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jerryhou85:
I'm using WinMoSpeed on 23, Apr ROM at 787, stable for over 18 hrs. :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] martian07:
Start menu Layout changer

I have edited the files for the start softkey reference to Utask. Just copy the files to your windows directory (overwrite) and all the layouts should work fine. I tested it on TP2, all worked. But I think Tilt2 has a hardware win key, so I am not sure about that. I know most of you have already edited the Utask settings but just in case. Oh forgot, Credit:NRG for wonderful ROMs. Thanks!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
Well no.. credit to YOU for making a useful patch, when I was too lazy to... :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Joe Bleau:
ROM Apr.26 + WinStart + X Button = Fishy

I tried the same thing on a fresh flash of Energy ROM Apr.26 and WinStart 2.4 (WS) paid version: opened WS and closed it with the X button 6 times and managed to get 6 WS processes accumulating. At the 7th. attempt, the phone froze and it was not possible to use QuickShutdown to restart the phone. Only the hardware Reset button did the trick. Maybe it's related to the uTask/AMeBa thing above? :confused:

So until it's fixed either by NRGZ28, a user or petititi I will be using only the Start button or Menu > Quit and not the X button to close WinStart. Thanks for the pointer Jake. :cool:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
WinStart and the X button solution in April 26 Energy ROM

I posted the solution here: http://xdaforums.com/showpost.php?p=13307113&postcount=149

I decided to quote it here, since with the new ROM the problem now appears with the WinStart software. It is technically not a ROM issue, since WinStart is not cooked in. It is also not technically an issue with WinStart, since it is only a problem when using ultrashot's uTask. Since WinStart is commonly installed by EnergyROM users, it seemed appropriate to post it here. In any case, this is the solution.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Joe Bleau:
Re: WinStart and the X button solution in April 26 Energy ROM

Just tested your fix and it works on NRG Apr.26 ROM, thanks!

When checking with the cooked dotfred's Task Manager v3.1, it shows only 1 WinStart process after opening & closing it multiple times with the X button. Note that when closing with WinStart's > Menu > Quit, there is no more WS process showing in Task Manager.

I have an other Tilt 2 with NRG Apr.23, WinStart 2.3 and the original uTask 1.4 cab as it was not cooked in that ROM and there is no problem of accumulating WS processes like on Apr.26 when closing WS with X so it could be a problem related to the way uTask was cooked in and not a WinStart nor a uTask problem per say.

Start > Tools > Microsoft My Phone: the X button does not work for me after finishing the sync. I can still see My Phone in ArkSwitch and processes in Task Manager and that's with My Phone set to manual, not automatic sync.