ProvXML Reference for Developers
 

With a lot of questions and sharing going on concerning Provisioning XML, I found a couple of links that might be of use to everyone!

http://msdn.microsoft.com/en-us/library/bb737536.aspx
^ This link has all the available options that Provisioning XML has to offer. It has lots of goodies

http://msdn.microsoft.com/en-us/library/bb737572.aspx
^ This link has goes to all the examples of the Provisioning XML options.

http://msdn.microsoft.com/en-us/library/aa924450.aspx
^ This link is for any one that is interested in FileOperations and would like to all the CE Strings

Hopefully all the developers will like this and learn a few things. I know I am learning quite a bit!

Re: ProvXML Reference for Developers
 

Outstanding links mrgoeff! I peer into roms whenever I get a chance and I am seeing provxml being used more by manufacturers and the ppckitchen crew. I'll know how I'll spend my day off tomorrow. Here is a link I'd like to add:

http://msdn.microsoft.com/en-us/library/ms889522.aspx
^ Explanation of MXIP* files.

Re: ProvXML Reference for Developers
 

As much as I talk about the mxip and the mxipupdate.... I should of had that one in there as well! lol

Re: ProvXML Reference for Developers
 

... not implying that either of you missed anything, but I eventually dug deep enough to the direct link to the file operations example code and thought I would add it to the fray ...

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

Best regards,
-boggsie

Re: ProvXML Reference for Developers
 

Almost exactly like regular .xml code isn't it...Actually I can't find any difference other than the naming scheme..

On a side note, I'm going to do an experament this weekend. I want to take as many of the mxip*.provxml files in a rom and convert them to regular RGU registry entries. I'm thinking it may be slowing down bootup speed as I've been using them alot lately since I've figured them out....

Re: ProvXML Reference for Developers
 

I didn't want to specify one type that the ProvXML could handle. I wanted to give the master list to show what else it is capable of besides file operations and email setup :)

Re: ProvXML Reference for Developers
 

Let me know how that turns out. I'll be interested as to what needs to be applied at every boot.

Re: ProvXML Reference for Developers
 

I'll go ahead and open myself up to a bludgeoning in the hope that if a better idea exists, you'll let me have it ...

What I am doing is chaining all of the provxml stuff that is new to me into a massive _setup.xml and then building that into ~RegSettings.cab which I run as the last command in my sdconfig.txt.

I am trying very, very hard to limit what I do with (inside of the kitchens) with PPCKitchen so that when updates come out, I don't spend time re-implementing my PPCKitchen tweaks.

Plus, there are still a few esoteric things (rstoyguy is cutting that list down) that I install with UC and I have settings, etc. that I want to take care of for those programs.

Best regards,
-boggsie

Re: ProvXML Reference for Developers
 

I'm expecting some interesting results. I can tell you I had strange results with changing my mxip_mail*.provxml to a mxipcold_mail*.provxml... My thought process it would only load it once...I'll test that some more.

I'm sure that 50%+ of the provxml's in the stock rom are there to make it easy for tech support. Soft reset your phone and alot of sprint specific stuff get's reloaded. I just wanna know how does that affect bootup time...

Re: ProvXML Reference for Developers
 

I forgot to ask.... are you doing the provxml > rgu conversion by hand or are you using a tool? All I have seen so far is going rgu > provxml.

I'm starting to think that going back to the dogguy kitchen is the best thing for me :(

Re: ProvXML Reference for Developers
 

by hand. I wish there was a tool. I started but I overwrote the oem directory accidentally when I was helping someone with their rom. I'll start it again, but it's a painfull cut n paste deal. :) Then there are still security certificates and what not. I might have some time later this week. I have noticed that the newer roms seem to take longer to soft reset, so the curiosity is still there, just no time lately...

Re: ProvXML Reference for Developers
 

I know it will be a lenghty process... but if I move away from from the PPCKitchen, it will be a necessary evil.

I hear ya on the no time. Sounds like you sold your soul doing the OEM requests :mrgreen:

Re: ProvXML Reference for Developers
 

A little more than I expected... :) But if I do it, I'll detail the provxml's I did so they can be deleted, and include an OEM. They are pretty much standard so far in the different rom's that I've seen. Except the 3-4 that the different carriers include to tweak their cube/roms. I may come up with a ..\sys oem and then I'll do the sprint stuff.

Re: ProvXML Reference for Developers
 

so... mxipCOLD is only for a hard reset/first flash? ie it won't run on a soft-reset?

leaving mxipUPDATE.. says it will only run when the given package is updated, so is it the processing of all XML's to see if there was any update during a softreset that you think is slowing the boot times down?

not second guessing you at all, just trying to determine if i am following the mxip*.provxml stuff correctly...

Re: ProvXML Reference for Developers
 

According to the SDK, mxipCOLD is treated the same as mxip. mxipUPDATE only processes on an "image update". The "image update", I think is basically a soft-reset. In the last Sprint Vogue ROM release there were:

mxip_*_*.provxml = 9 files
mxipcold_*_*.provxml = 3 files
mxipupdate_*_*.provxml = 19 files

So on first boot you have 31 additional files processed...

And on a soft reset you have an additional 19 files that must be processed...

So yes, I think it is slowing down the boot process. By how much??? Who knows, but most of the mxipupdate* files are designed to bring the sprint settings back. I assume when little johny messes up his phone, one call to sprint tech support, they have johny reset and all is back to how it was.

Re: ProvXML Reference for Developers
 

If you do ever have to time for that, it would be pretty cool. I was going to try and do that sometime this week or this coming weekend. It's not a big rush to me.

Re: ProvXML Reference for Developers
 

Anyone have any luck getting a path to the \Storage Card\somedirectory to work in a provxml on a Touch/Vogue
Here is a line that just won't go into the registry, but after flashing I can add this entry manually without problems. BTW this is formatted properly within the xml file, just didn't want to paste the whole thing. ;-)
<parm name="weatherIconPath" datatype="string" value="\Storage Card\WPIcons"/>
be nice if storage card had a %ce00% for consistancy across devices.

EDIT...
The more I think about this, I believe it must just be the WeatherPanel program overwriting this registry entry, because I'm pretty sure I could put /nopath/nofile and that would get written to the registy verbatim since it's really just a string.

Re: ProvXML Reference for Developers
 

As an update, I'm going to first take all the file operations and convert those to a regular initflashfiles.txt file and see what happens. Most of what I've seen in the ..\SYS folder are file operations and security certs...

I'm sure with all that file moving around, that should speed it up....anyone got a stopwatch? I forgot I use an app on my phone... :)

Re: ProvXML Reference for Developers
 

Generally speaking (non-PPCKitchen) is finding these things just the trial and error process of opening up the various provxml files?

for example ... things like:
ActiveSync
Calendar
Contacts
Help
Internet Explorer
Internet Sharing
Messaging
Notes
Phone

I've learned (thanks to your examples and tips) how to move/delete these with (prov)XML (_setup.xml) in a FileOperation.cab, but as I am learning, that is simply taking more time to do something that was just done as part of the phone setup.

I'm trying to follow, but am I on the right track, here?

EDIT: It looks as if most of what I was / am looking for is in initflashes.dat.


Best regards,
-boggsie

Re: ProvXML Reference for Developers
 

I've been doing a lot of research in regards to these files and am planning on posting my compiled findings, but I wanted to check in with ya'll first.
specifically did you notice any speed improvement rstoyguy? I'm guessing only @ first boot.
2nd, has anyone proven mxip_update files are ran @ soft reset? I'm betting not.

Re: ProvXML Reference for Developers
 

can you,guys,tell me how to convert provxml to rgu?I hate provxmls lol

Re: ProvXML Reference for Developers
 

i've been using XMLtoReg.exe by AlexVallat over @ xda. I attached the file since their server's flaky right now.

it will only do reg entries, so file ops and certs will need to be manully dealt with.
I make the reg, then convert it back to xml for easy comparison to the original provxml.

Re: ProvXML Reference for Developers
 

Im digging the verizon issues (too many posts with complains in vogue section).I converted vzw carriers provxmls into rgu and found this


[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD\VZW Customization]
"Version"="Vogue-VZW-071112"

Im with sprint and I dont have this entry at all.Anybody knows whats that for and is it safe to remove it?

and 1 more question,not sure where should I post it.....

[HKEY_LOCAL_MACHINE\Software\OEM]
"ROMVersion"="3.08.666.1"
"PhoneCDMAType"=dword:00000001
"ModelID"="VOGU200"

why my model is vogu200 in reg,but when I go to start/settings/system/device info -its showing vogu100 ?

Re: ProvXML Reference for Developers
 

i am having some issues with provxml. The problem is i have this code written to rearrange my startm menu shortcuts and put them in different folders. Now this works when i have it in a cab but when i have it in its own OEM file all it does when i re-flash the rom with it is create the folders but nothing else? Does anyone have a clew of what might be happening and how i can fix it?

Re: ProvXML Reference for Developers
 

So, arranging start menu items via provxml, as you are experiencing, is a very challenging thing to pull off.

When you are executing the cab file, you know exactly ... exactly where every shortcut is located, because you stage the cab file to execute a precise point in the post-flash process. you do this either manually, via SDconfig or sashimi.

The same cannot be said of the provxml execution. It is entirely possible, and likely, that you are trying to move items via provxml, that don't exist yet in their source location. One thing to consider is that other provxml is also executing to do exactly the same thing that you are doing. The creation of Microsoft Office shortcuts are a perfect example as they are copied via provxml. Your provxml is trying to move them, when the Microsoft Office provxml hasn't copied them to thier source location, yet.

So in order to avoid this with provxml, you need to give your provxml oem file a name which helps to ensure that it will execute as the last provxml in your flash process.

However, if you are looking for a less painful approach, I can tell you that after working on this for a long, long time, I have come to learn that doing this particular task is so much easier via mortscript. One of the very nice things about mortscirpt, is that each copy/move can be setup as a elseif statement, whereby if the items doesn't exist, the script just proceeds to the next command. As you are learning, provxml is very unforgiving. If one statement for a copy or move cannot be executed, the script will die.

Best regards,
-boggsie

Re: ProvXML Reference for Developers
 

alright so you mean if i named the provxml file itself or the OEM folder its in starting with the letter z it will be executed last? Also for mortscript how would you get it to run at start up im very new to this as well lol?

Re: ProvXML Reference for Developers
 

I'd try leaving the OEM alone and then use this as your file name for the provxml:

mxipupdate_zzzOrganizeStartMenu_100.provxml

Best regards,
-boggsie

Re: ProvXML Reference for Developers
 

do i have to change it in the dsm file as well?

Re: ProvXML Reference for Developers
 

In this case, it is fine if the dsm file to be a blank, empty, or null identifier for the package.

Now as I say that, I probably should add that DSM files created through oemizer or other package creation tools are a binary file which includes the package contents (list of files).

Best regards,
-boggsie

Re: ProvXML Reference for Developers
 

alright ya i use oemizer and it created a dsm file which is not blank but my only file is that provxml so its it ok for me to clear it?

Re: ProvXML Reference for Developers
 

Yep ... open it up in a text editor, select everything, delete and save the file.

Best regards,
-boggsie

Re: ProvXML Reference for Developers
 

i tried that and i got it to cook properly but the only thing it does is creates the folders for the shortcuts to go into but moves no shortcuts

Re: ProvXML Reference for Developers
 

Doesn't surprise me ... this is very, very difficult to get working.

In the end, to get it to process, I broke the provxml into sections and ran each section as a cab file or, if you have the tool in your rom, you can apply provxml via Advanced Configuration.

Frankly, this isn't worth the effort. Go over to xda and read through the mortscript thread(s) and look at the examples compilation. You might invest two or three hours trying to track down the offending provxml in your current file, and that solution will be good until you change just one thing in your ROM folder structure. On the other hand, with the if/then structure available in mortscript, if in the furutre the source location of a shortcut changes, that one single call in the script will fail and everything else will execute as you expect. Then you don't change the existing (non-executing) mortscript call, you just add a new section to account for the change.

Best regards,
-boggsie