yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] DuChene:
Yeap

Now I will ready to make and developing themes projects to Manila 2.5...

Thanx
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] osiedacz:
CABs to avoid with XDA_UC

I have found that Resco Explorer and Resco Backup don't play well with XDA_UC. If I install them using the root XDA_UC folder, Sense starts back up right after the CAB installs and doesn't wait for XDA_UC to finish running. If I put them in the "SD" folder of XDA_UC, they don't install at all. No dialog comes up.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
If you are installing to your storage card, there is no need to install it through XDA_UC. Just install it manually to your Storage Card. Then create a reg file for the settings to put in the XDA_UC folder. And copy the lnk file in XDA_UC\Sense\Start Menu\Programs

If you are installing to the device, you may want to try creating your own cab after installing. Just about any cab can be opened with WinRar. Then you will be able to see all the files in it and where they go. If it can't then you will need to find all the spots that it puts the files and probably will need to do a registry dump before and after installation.

Most cabs contain a file _setup.xml

In the XML, all the files extracted that are needed are mapped to the real file names and locations.

In the XML, all the reg entries are also listed.

Then, you can use Visual Studio to create a cab.

Or you can use Quick Cab, which is free.

WinCECabManager is also a great program, but it is about $100.

It can be alot of work to do this. But, it should save alot on your flashing.

If you do create your own cab, you can not and must not share it, since those are both commercial products that are not free.

I decided to download Resco Explorer. It does contain a setup.dll, so more work will be needed to make a cab that won't require it.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Kaxkas Man:
im using Energy.RHODIUM.29017.Sense2.5.Cookie.2.0.sencity.Mar.21, with the locker that comes with it, the one that you have to slide down to unlock, with no pin. ive changed the home tab a bit, i switched off the extra shortcuts on it. ive installed InCall Keylock, but it worked without a problem, tough i have tested this issue with and without InCall Keylock. when someone call me, all i see is the lockscreen with the slider to unlock and it doesnt work. i cant see the name and picture of the caller. I cant see the slider to answer or ignore but if i press the place where the slider its suposed to be, the slider comes out of nowhere, tough i cant see the green and red bar with the answer and ignore texts
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
How to troubleshoot this - how to hard reset - Why it is needed to troubleshoot

Have you tried it right after a flash, without running XDA_UC?

You can hard reset to do this also?

How to hard reset from the Rhodium Wiki

When promted to run XDA, select No.

Do at least 1 soft reset after the phone fully starts up.

Test the phone for a while like this.

I am pretty confident that it will work fine. Now start manually applying things you change or install 1 by 1. Test it after each thing you change or install.

Important piece about uninstall and why a hard reset is needed to test.

It would not surprise me if when In Call Keylock is uninstalled that the registry still contain changes. Uninstall will only restore values that were affected by the install. It will not restore values that were changed by the program when the program is run.

A hard reset completely wipes everything, so it is in the state as if you just flashed the ROM.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
More Mobile Macro from Developer

EDIT: Hey, I think I figured it out. The bug that freaks out the calibration during a macro recording appears to be activated when a user touches Start (lower lefthand of screen). If a user simply starts a macro recording, then touches Menu, then touches it again, the original calibration stays in place, and a user can finish recording the macro.

This, from my POV, ties into your theory of 6.5 vs 6.53.

At any rate, the program is usable

--

@ CFB--

Not to flog a dead horse, but I got another note from Artel Developers:

Hello Jake,

>>Many thanks for your response, and I'm very sorry to hear that Mobile Macros will be retired. Strangely enough, I was able to get the program to work ONE time and was able to make a macro I need for HanDBase database viewing.<<

I can assume that your device has some app which use the same method for catch touchscreen events from system (something with handwriting recognition and etc.), and when they are temporary disabled then Mobile Macros could work.

---------

This intrigues me. Any idea as to which installed, running program in EnergyROM (something to do w/ the screen) that would interfere w/ MM?

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] nradu:
I also have the same problem from time to time, without having InCall Keylock installed. I creates me random problems with the Windows built-in slide lock and with the Android style lock. Also it created problems with CHT Lock Screen, but only very few (now I cannot use it anymore because of Exchange policy of mandatory PIN).

I saw this behaviour with all ENERGY ROMs tested, but also with the OFFICIAL WM6.5 firmware from HTC.

So I don't think it's the fault of the ROM or of any program installed, I really believe it's a Windows related issue. Maybe someone with deep knowledge in WM6.5 will be able to dig into it.

Radu
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] awalt:
I have tested and verified everything in my streamlined setup, so I can do future ROM flashes quickly! Everything works very well, thanks so much for everyone's help!

I only have one problem left (that I know of <g>) - my provisioning of wireless networks that require a password does not work after a ROM flash. I also have an XML file for Gmail account provisioning, and that works perfectly; both are in the XDA_UC folder. I also tried converting this xml file to a cab but it does the same thing.

What happens is when I click on one of these two wireless networks to connect, it still prompts me for the security code. I used Makisu to set this up, and it looks correct to me - AEP Personal 2 security, access point, etc. etc. Does anyone see anything obvious, or know how I can debug this further? When I had a cab version of this xml file, I also tried just running it after flash was done, and it still prompted for security key. Do I have to do anything special, like turn off WiFi or something else? I assume it should be able to accept the security key since Makisu prompts for it in the xml file setup.

Thanks for your help!

The wifi xml file:

<wap-provisioningdoc>

<characteristic type="CM_WiFiEntries">

<characteristic type="SSID Name 1">

<parm name="DestID" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>

</characteristic>

</characteristic>

<characteristic type="Wi-Fi">

<characteristic type="access-point">

<characteristic type="SSID Name 1">

<parm name="Hidden" value="0"/>

<parm name="DestId" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>

<parm name="Encryption" value="6"/>

<parm name="Authentication" value="7"/>

<parm name="KeyIndex" value="1"/>

<parm name="NetworkKey" value="password"/>

<parm name="KeyProvided" value="0"/>

<parm name="Use8021x" value="1"/>

<parm name="EAPType" value="13"/>

</characteristic>

</characteristic>

</characteristic>

<characteristic type="CM_WiFiEntries">

<characteristic type="SSIS Name 2">

<parm name="DestID" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>

</characteristic>

</characteristic>

<characteristic type="Wi-Fi">

<characteristic type="access-point">

<characteristic type="SSID Name 2">

<parm name="Hidden" value="0"/>

<parm name="DestId" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>

<parm name="Encryption" value="6"/>

<parm name="Authentication" value="7"/>

<parm name="KeyIndex" value="1"/>

<parm name="NetworkKey" value="password"/>

<parm name="KeyProvided" value="0"/>

<parm name="Use8021x" value="1"/>

<parm name="EAPType" value="13"/>

</characteristic>

</characteristic>

</characteristic>

</wap-provisioningdoc>
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bipinsen:
I can only speak for Resco Explorer and Photo Manager since I don't use Resco Backup. Resco Explorer (and Photo Manager) installs just fine via XDA_UC. There is one prompt for user language that you have to click OK for. Otherwise, the program installs just fine to phone memory. I have about 10 cab files that are installed via XDA_UC, with Resco install coming in somewhere in between.

[Resco Explorer 2010 v8.10]
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] osiedacz:
Hmm, interesting. Do you have the cab file in the rot XDA_UC folder, or in the SD folder below the root? I have tried both and I never get a prompt regarding language. All I get is Sense starting up once RE is installed, which causes potential issues with the rest of XDA_UC running. Sometimes the remaining items install and sometimes they don't.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bipinsen:
I have it as \Storage Card\XDA_UC\Resco.cab
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] hefman:
The issue with the Android style lock screen (the one you are using) and caller ID has been around for a while. There were several posts about this a few months ago, when NRG started cooking it in, but I don't think it was ever resolved. If I recall, the ultimate recommendation for caller ID was to use a different lock, like S2U2.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
My home network is not very secure. I live in a house. I have unlimited internet usage and there are no publically accesible servers on the home network. No computers have any files or resources shared on the network.

Back to your problem

It sounds like 1 will work correctly, but the other does not. I suspect that is because the DestID is the same for both of your networks.

<parm name="DestID" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>

Try changing the value in both places for the 2nd one to

{D0CFCACE-486F-497f-8530-43B49111A717}

I used GuidGen.exe to get a new value. I am pretty sure that is what is needed. I will look more into it to confirm, but if you can test and report before I have time, that would help.

I don't think there is anything special about the value 436EF144-B4FB-4863-A041-8F905A62C572

I did do some reading. That guid does have a meaning of Internet. It still might work using a different GUID for the second connection though.

But, on msdn I found this
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] martian07:
CAB analyzer

As always nice informative answers by you. Just wanted to add about an old small WinCE CAB analyzer utility which is quick and works great for getting these XML info from the cab files. The utility called MSCEInfEn runs on your PC. Drag any cab files to it and you simply switch through tabs to find all reg entries, all file to be copied and their target locations, shortcuts created and best you can simply drag a file from this to any folder to extract it. And much more. I love it its a one step view for all the details. Hope its helpful to some. Here is the XDA thread about it.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Kaxkas Man:
just one thing, what is the XDA_UC? i hard reset-ed my phone, and i dont no where i have to say no to XDA_UC cause i dont know what it is
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] hefman:
If you are running a rom with it cooked in (like EnergyROM), it will come up shortly after first boot, if you have anything in your XDA_UC folder on your SD card.

Post #7 has a FAQ for XDA_UC. I would suggest starting there if you have questions.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Joe Bleau:
Re: XDA_UC Links

+1 for that.

XDA_UC FAQ in this thread post #7, page #1. BTW maybe NRGZ28 could add the links below to his post?

And since this NRG ROM thread is turning into an XDA_UC thread, maybe further detailed discussions could be done in Serfer222's XDA_UC_NET - portable UC, Sense GUI. (0.9.4.4) and in the XDA_UC creator's Noonski thread: [UC]XDA_UC V2.RC1, Automated & Silent User & Cook, Configuration Service.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] gregb882:
New ROMs are up!!! And I can't play with them until tomorrow :mad:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] madnish30:
MOD NOTE: rkub, latinohot, wmg316 guys relax ! This is a ROM thread, cribbing about the chefs won't take you far on this thread.

Request for the fix you want, but in the end it's upto the chef whether he/she wants to work on it or not, you can't flame him/her just becaue he/she did not look at your request. And neither can you flame someone requesting for a fix.

So let's keep it to that, be patient, enjoy you devices !

Hope I don't have to delete your posts (again), and send you guys on a vacation sometime soon.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] mtorre5:
Is there a cab for the start menu format?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] martian07:
Transparent Toggle Switch for sencity

For the NRG sencity ROM fans, I did not like the all black toggle switch free links specially when I want to use a lighter background. So I just made those switch masks transparent ~50% with gradient. To me it looks good on both light and dark wallpaper and still visible on both. If you like it just copy the files to your windows directory, backup your original. Make sure you have turned off sense before copy and restart afterward.

All credits to original Sencity theme. Enjoy!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] martian07:
Startmenu Layout

If you mean different startmenu layout switching used by NRG. Each one of them have different Cab file in their respective dev thread or websites. If you mean how the switching is done in NRG ROMs, he does it by different mort scripts files in windows directory most of them start with st*.mscr. I am not sure if there is one cab for this, because chef cooks this in his ROMs.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] awalt:
Thanks JVH3 for the tips to try on getting my WiFi provisioning to work. I'll do some research on it today/tomorrow and report back, but I won't bog down the thread with non-ROM type questions! I appreciate your help and tips greatly.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
New ROMs went up last night.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
@martian07

These are fantastic, thank you, thank you. I'm running Joe Bleau's pure black background and so all that show is the wifi/data/bt emblem itself, with a circle around it if it's activated.

It makes for a great economy of screen.

FWIW, the emblems don't sit in the exact middle of the circle, they lie on the left side, or at least they do with my specs:

T-Mobile HTC Touch Pro 2

Energy.RHODIUM.29017.Sense2.5.Cookie.2.0.Mar.29.7z

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
Noonski XDA_UC is not the same as XDA_UC in Energy ROMs - link to Energy XDA_UC

The XDA_UC in Energy ROMs is not the same as the XDA_UC that Noonski originally made. NRGZ28 made alot of changes to it. It is simplified. Some things in Noonski's do not exist in Energy ROMs. The original Noonski XDA_UC is good, but much was done that was more complicated than it needed to be. And some things are not done exactly the same way between versions.

Here is a link to Energy ROM XDA_UC tips. It is specific to the Rhodium, but, it applies to all Windows Mobile Energy ROMs. There is alot of very good information in this thread for configuring Energy ROMs. It is also a better spot to discuss XDA_UC related information for Energy ROMs.

http://xdaforums.com/showthread.php?t=671163

There just a little over 300 posts in it, so there is no reason not to read the whole thread.

For new users on August 30th, 2010, I wrote a small tutorial in that thread at post 200.

There are also enhancements to the XDA_UC for advanced users created by BenjamminzIS to give some features not present in the Energy ROM variant of XDA_UC. BenjamminzIS created this while using Raphael Energy ROMs, which contain the same XDA_UC code.

http://xdaforums.com/showthread.php?t=684865
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] awalt:
I got it to work. Basically I took out my EAP param, and created 2 xmls, made cabs for each, and they both provisioned fine through XDA_UC. My args are a little different than yours I think because my security is WPA2-Personal and AES Encryption.

From my reading it seems it has to have a GUID of {436EF144-B4FB-4863-A041-8F905A62C572} to denote Internet, vs. My Work. My SSID is broadcasted, some people's are not so they would use different values too. Also, be sure the xml file is Unicode!

To close the loop for anyone searching, here is what I used for both, just changing the SSID name and password (which could be clear text) for both:

<wap-provisioningdoc>

<characteristic type="CM_WiFiEntries">

<characteristic type="SSIDName">

<parm name="DestID" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>

</characteristic>

</characteristic>

<characteristic type="Wi-Fi">

<characteristic type="access-point">

<characteristic type="SSIDName">

<parm name="DestId" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>

<parm name="Encryption" value="6"/>

<parm name="Authentication" value="7"/>

<parm name="Hidden" value="0"/>

<parm name="KeyProvided" value="0"/>

<parm name="NetworkKey" value="password-in-clear-text"/>

<parm name="KeyIndex" value="1"/>

<parm name="Use8021x" value="1"/>

</characteristic>

</characteristic>

</characteristic>

</wap-provisioningdoc>
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
In the future refrain from policing my threads. Please PM me, FIRST. Thank you.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
The "fix" is the right blend of directx renderers and codecs. Problem is... it's difficult to do, without giving up the nice Leo volume overlay that we see over some media apps. I didn't this is broken again in my ROMs, I'll look into it again today. I'm pretty sure "widlchild's" fix wont work in my ROMs anyway, or will break something else.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] martian07:
Transparent Toggle Switch for sencity

I am trying to use all the widgets transparent, I like it that way it gives me a feeling of less cluttered and bigger screen. I found most of them this was one I did not get that's why had to do it.

I am not sure about the emblems, they all seem different, in mine the data one looks lot to left but the others seem OK to me, unless my aging eyes betraying me. Attachment, also shows how it looks on light and dark bkg.

BTW how is the Mar29 29017 ROM. Is this stable and do you have any problem of losing sound with BT switching specially when you connect and disconnect A2DP/stereo. I flashed last 29017 but had too many resets so quickly reverted. May be just a bad flash.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bennyg1:
Upload video to Youtube from Albums

Hello I have flashed the Energy 29017 Sense 2.5 Reference rom and cannot get video uploaded from Albums. I also can not log into Youtube under the sense settings, data services. I have checked to make sure I the right username and password via my desktop. I am on ATT and have radio 4.49.25.95
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
You Tube HQ Video

NRGZ28. Yes, I would confirm that the You Tube HQ video does not work on your ROMs...it has been an issue for a while.

Thanks for looking into it!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] pink_floyd:
New Mar 29 ROMs

Have flashed the Mar 29 29017 ROM.

Flashing went quicker and smoother then ever, new ROM looks good so far, no issues.

Needs to settle down though.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
You Tube player

I was just chatting with NRGZ28 about it. It is not a problem on the CDMA Rhodium. He tested it with the Cat Fight video and it played fine.

In that chat he said that the CDMA ROM has a different set of codecs.

And from the chat and his last post, it sounds like he knows what to do to fix it for us.

In the end, this is not a deal breaker for me. I really don't watch that many You Tube videos and it's not a problem for me to watch in Fast Download mode. But it is a nice to have feature. And nice when showing someone the phone.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
Agreed! I probably watch less than you!! :D

But it has been an issue with a lot of posters here...so I thought it would be good to report.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Alcoholic:
Just read the past few pages. Looks like i'm the only one having problems with the sense twitter tab.

I haven't found a need to upgrade to the latest ROM (using jan build) but this is a good enough reason.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Joe Bleau:
XDA_UC Links & Mods

Useful info, could those links & info be added to XDA_UC FAQ post#7 or general FAQ post #6, on page #1?

_________

Mods Fight :p

Hey! You guys tell us not to fight in the thread... can't you PM each other? :confused:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rkub:
Ok let's not instigate here Joe, just let it go..lol Besides they're mods and they weren't fighting, NRG was just asking the other mod to let him take care of his own thread... :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
That's not "fighting". I'm being territorial.. :)

Go to your room and let the grownups talk :D:p
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
Exactly... ;)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
Hi, martian07--

I solved the lean-to-the-left dilemma with one fell swoop. I used your CHT_switch_off icon for both off and on. It occurred to me that since I already have icons on the top right screen that come on when these services are accessed, why do I need a toggle telling me the same thing?

So now I have the tiny emblems that save me screen real estate, and I already know if they're off or on. Thanks again for that.

As for the new ROM, I like it fine. While the red of the Contacts has been removed (I don't know if you were following that dilemma), so far, I occasionally find the contact to be black-on-black, which does make phone number viewing difficult :)

But going to another number restores it to white-on-black, and it's no big deal. And it may be a glitch with my own specs; it'll be interesting to see if others find the same thing.

The ROM overclocks well at 748, my apps install fine, Sense is Sense, meaning that occasionally it needs to be stopped, then started, especially on a soft reset, but that's nothing too problematic.

WinStart 2.2 Retail continues its memory magic.

The 28244 ROMs are, as the forum veterans say, a little snappier, but I'm going to stick w/ the 29017 ROMS as the battery life of the 29017 is significantly more robust.

Re: BT sound; I'll have to see what others say, since I just use BT to sync, file swap, and Linux tether.

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
Indirectly, it already is and has been for quite some time.

Post #6 of this thread

That link takes you to this post:

I keep a list of links in that post to useful posts with tips and tricks that I have found or made. I have kept it in reverse chronological order (newest on top), so that people can check it periodically to see if anything new appears. Of course not everything that I find or make ends up in that post.

I also keep a link to that post in my signature. Since I usually post something every day, it is easy to get to.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
YouTube HQ fix

From NRGZ28 on Twitter:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
The youtube HQ video issue has been resolved. Unfortunately it involves replacing system drivers, so a patch would not work. Uploading new ROMs with this fix included. You dont need to download it, if you dont care about this issue :)