ProvXML Reference for Developers

[EtrnlWolf]

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...

[rstoyguy]

Originally Posted by EtrnlWolf

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...

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.