[Kitchen] WVGA Touch Pro 2 Collaboration

[shane6374]

Originally Posted by TMartin

That one was easy....I just converted the app.reg to a provxml.

With others that have setupdll.dll's, I normally make a backup of my registry, install the cab, backup my registry again and then compare the two registry backups.

I'm about to really show my n00bness. How do you get the display of the registry on to your computer so you can work with it there instead of finding it on the phone then making the edits in the kitchen?

[Sharkie405]

Originally Posted by shane6374

I'm about to really show my n00bness. How do you get the display of the registry on to your computer so you can work with it there instead of finding it on the phone then making the edits in the kitchen?

Do a google search for CEReg Editor. That's what I use and it's uber easy! I'd post it but I'm at work.

[shane6374]

Thanks Sharkie!

[Blades]

Wow, I'm having a helluva time trying to get CHT/2016 to work with rstg's rhodium add-on. The slider icons are slightly distorted, but get 'un-distorted' when i swipe up to reveal the full 4x4 quicklinks grid. Not to mention, its rediculously slow. I also have an issue where my end key is not mapped to turn off the phone.. but I think thats a LPEK program.

What are you guys using with 21911? Are you avoiding 2016?

uhh i think i just had my first SleepODeath happen. I definately screwed up my original kitchen and the rstg addon is the only one that will build a rom. I think the original sprint stuff is screwing around with manila. I tried to get rid of as much as I could.

[corey1138]

on 23128 if i leave any app open it eventually it closes. I dont have any htc taskmanager in my rom. Any ideas?

[willysp]

Originally Posted by corey1138

on 23128 if i leave any app open it eventually it closes. I dont have any htc taskmanager in my rom. Any ideas?

Since the 23128 release was a bit unusual (no lang), and there is a known "To:" SMS problem, I have continued to use 23127.

Perhaps you might try that?

[shane6374]

Originally Posted by willysp

Since the 23128 release was a bit unusual (no lang), and there is a known "To:" SMS problem, I have continued to use 23127.

Perhaps you might try that?

So I see I wasn't the only one having that issue with 23128. I went back to 23126 myself. I did notice the "problem" of apps closing while in the background for the few days I was running it. I just have had many other issues to fix, and dumping a different sys is an easy fix.

[willysp]

Originally Posted by shane6374

So I see I wasn't the only one having that issue with 23128. I went back to 23126 myself. I did notice the "problem" of apps closing while in the background for the few days I was running it. I just have had many other issues to fix, and dumping a different sys is an easy fix.

Glad I helped - appreciate the "Thanks"! (=:

[Formula84]

Originally Posted by TMartin

That one was easy....I just converted the app.reg to a provxml.

With others that have setupdll.dll's, I normally make a backup of my registry, install the cab, backup my registry again and then compare the two registry backups.

What do you use for the reg compare on your pc? also does making it a provxml update on every boot? never quite fully understood xml's.

[rstoyguy]

Originally Posted by Formula84

What do you use for the reg compare on your pc? also does making it a provxml update on every boot? never quite fully understood xml's.

I use CeRegEditor. You can export and then compare the two files. Here's the link : http://ceregeditor.mdsoft.pl/

And for provxml, Here's the scoop from micro$oft: http://msdn.microsoft.com/en-us/library/ms889522.aspx

mxipupdate - updates when the package is updated/boot. I usually cook'em, so I use this as it usually doesn't get updated...
mxipcold - updates only on first boot.

edit: And a rgu2xml that comes in handy for making those RGU's and app.reg files into xml. Then just rename it...