[ Discontinued ][ v4.2 ][ 6.5.x / 6.5 / 6.1 ] Calkulin's Visual VGA Kitchen & ROMs

[sampson]

hrm well it looks like the file is skipped entirely and changing attributes doesn't help

[aceracer24]

Originally Posted by sampson

hrm well it looks like the file is skipped entirely and changing attributes doesn't help

Are you able to manually fix it by editing the registry from the phone? From my experience with .rgu's and .provxml's, there is a hierarchy. Alphabetically and name length seem to be playing a part in when a file is read/used. He could have a reg edit someplace else that is read AFTER the above one and forcing the reg back. If you can manually change it on the phone then the above problem is most likely the issue.

[chuckz07]

Originally Posted by aceracer24

Are you able to manually fix it by editing the registry from the phone? From my experience with .rgu's and .provxml's, there is a hierarchy. Alphabetically and name length seem to be playing a part in when a file is read/used. He could have a reg edit someplace else that is read AFTER the above one and forcing the reg back. If you can manually change it on the phone then the above problem is most likely the issue.

Though that fix does fix the keyboard issue, I flashed back to my beta 1 rom and the reg entries are identical to those sampson said to change. It looks as though Calkulin has set them up that way to preload or something. I read through his .rgu's and saw a few entries for the preload. But like I previously stated, I have flashed with the 1.4 and the keyboard works, but I am slowly narrowing it down.

[sampson]

It definitely is skipping the file over entirely. I checked a few other registry entries inside the file and none of them were applied so something's wrong with it.

[chuckz07]

One more flash to confirm, but I think I've got it.

[aceracer24]

Originally Posted by sampson

It definitely is skipping the file over entirely. I checked a few other registry entries inside the file and none of them were applied so something's wrong with it.

.provxml's will always override a .rgu. .rgu is used during the cooking process. Then there are two types of .provxml's. One is used when the phone first boots up (this I believe is why the phone takes much longer on initial boot) and the other one is used after initial boot.

Note Mobile Operators should avoid using provxml files to override (shadow) entries in Microsoft-owned provxml files

Note Mxip_*_*.provxml is imported only at cold boot when the device is initially configured. In effect, mxip_*_*.provxml and mxipcold_*_*.provxml are handled the same.

Note Mxipupdate_*_*.provxml files are imported after cold boot and when the package containing them is updated.

http://msdn.microsoft.com/en-us/library/ms889522.aspx

I know Calcu had removed some of the .rgu files in a few OEM's and applied reg edits through the provxml files. He might have missed one someplace.

[chuckz07]

Ok, I've got a ROM built and flashed with the 1.4 kitchen with a fully functional hard keyboard. If there are no objections, I will upload kitchen for everyone to test. Temporarily of course, until Calkulin returns from his trip. Any objections?

[sampson]

*shrug* i just edited the registry by hand... was there a version he had up after 1.4a that was pulled or is that most recent?

[chuckz07]

Originally Posted by sampson

*shrug* i just edited the registry by hand... was there a version he had up after 1.4a that was pulled or is that most recent?

In this order...1.4 until I found keyboard issue, 1.4a he thought might have fixed keyboard issue.

[sampson]

ah... might as well just upload a .reg file to save people downloading time since they won't see the issue 80 pages in until they have a botched keyboard