Related
Thanks for all the help. Just a few days ago I couldn't boil water and now I'm upgrading Radio Stacks and Cooking Ext ROM. Couldn't have done it without your help.
I found a post the other day about how to bypass the screen alignment on a hard reset for the 100th time. I have lost track of the post and can't find it. I tried searching for align with no luck. Does anyone know where the post is or how to skip align? Thanks in advance.
In the mean time I'm working my way through config.txt deleting stuff I don't use. So far I'm just deleting the references in config.txt.
Is there a way to make a line a comment in config.txt? I would love to preserve the line I'm testing deleting so if I need it I can uncomment it. I have a good backup of the whole ext rom including config.txt
Thanks again
Re: Comment in config.txt in ext rom and skipping screen ali
To disable calibration you should create a file named "welcome.not" (without quotes) in the root directory of your storage card or in your "\storage" folder. I have not tested that, but this is written in MS docs. This will skip the whole "welcome" process and may cause Extended_ROM programs not to be installed.
To comment a line in a config.txt you can try to place any symbol in the beginning of the line. It seems that autorun.exe ignores the lines it cannot understand.
It needs to be in \storage card. Having it in \storage doesn't work.
Beware... unless you preload your calibration settings, you will find
that a never-calibrated display probably won't let you get to the
screen alignment control panel.
The other "missing" function is timezone setting, but that can be preloaded in the registry (since it's not device dependent) or entered through its normal control panel.
I've asked one of the guys on PDAPhoneHome to put together a native app that calls the screen alignment routine.
Ehud
gavron said:
It needs to be in \storage card. Having it in \storage doesn't work.
Beware... unless you preload your calibration settings, you will find
that a never-calibrated display probably won't let you get to the
screen alignment control panel.
The other "missing" function is timezone setting, but that can be preloaded in the registry (since it's not device dependent) or entered through its normal control panel.
I've asked one of the guys on PDAPhoneHome to put together a native app that calls the screen alignment routine.
Ehud
Click to expand...
Click to collapse
I bet the calibration values are stored in the registry somewhere... maybe they could be exported (along with time zone) and then imported as part of the extended rom install... end result is auto-calibrated screen and correct time zone without rescheduling that dentist appointment with Dr. Johnson!
Dan
They are stored, and easily copied. Trouble is, they are device-dependent (different from touch screen to touch screen), wouldn't work if you replaced your device... and may drift from time to time.
IvanLasston came up with a method of getting to it with hard keys only which is fairly clever... using the up/down pad and the keyboard-tab to switch tabs... works like a charm.
E
Yeah I meant we could incorporate the registry entries into our own personal cooked extroms. Of course, going through the setup process after each hard reset really only takes 15 seconds or so...
Dan
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"="508,518 155,255 155,778 861,783 869,255"
That's mine. It's now part of platformxxx.reg in Customize.sa.CAB
You'll note that it's clearly of the format
C(X,Y) UL(X,Y) LL(X,Y) LR(X,Y) UR(X,Y)
Ehud
Hi folks,
Is there a way to make permanent registry changes? I found the sound after pressing the dial button very annoying and tried to set initVol to 0 in the registry, but after a reboot the setting is back.
Same goes for some other settings in the telephone which I wanted to change permanently. Like, changing the default locations of the images being saved by the camera to \Storage Card\My Documents\My Pictures instead of the DCIM directory. Is there a way to do this?
I noticed there are some OEM settings, but somehow the telephone denies those registry settings when I try to set them to new values. Write protected?
How could this be done?
Thanks in advance.
negrooid said:
Hi folks,
Is there a way to make permanent registry changes? I found the sound after pressing the dial button very annoying and tried to set initVol to 0 in the registry, but after a reboot the setting is back.
Same goes for some other settings in the telephone which I wanted to change permanently. Like, changing the default locations of the images being saved by the camera to \Storage Card\My Documents\My Pictures instead of the DCIM directory. Is there a way to do this?
I noticed there are some OEM settings, but somehow the telephone denies those registry settings when I try to set them to new values. Write protected?
How could this be done?
Thanks in advance.
Click to expand...
Click to collapse
Hi,
The registry keys where the changes are not permanent is set to default at restart. The only way I know how to make these permanent is to alter the ROM before it is cooked and flashed...
Are you sure your tweeking the registry and not the profile?
Look up HKEY_CURRENT_USER\ControlPanel\SoundCategories\CallStart
Change the InitVol value to 0 (I know you posted it but doesnt hurt to mention again.)
I have had this set on my phone for a while now without issue, and sticking after several reboots. Now of course if something else is bugging the phone it could be restoring the initial values, computers sometimes do this but usually require user input to do it...
Weird, what registry editor are you useing? Does it automatically restor a backup incase you mess something up?
I know sometimes when I have been changing things in my cars ECU it sometimes takes two or three times for the new coding to stick, might be something like that...
negrooid said:
Hi folks,
Is there a way to make permanent registry changes? I found the sound after pressing the dial button very annoying and tried to set initVol to 0 in the registry, but after a reboot the setting is back.
Same goes for some other settings in the telephone which I wanted to change permanently. Like, changing the default locations of the images being saved by the camera to \Storage Card\My Documents\My Pictures instead of the DCIM directory. Is there a way to do this?
I noticed there are some OEM settings, but somehow the telephone denies those registry settings when I try to set them to new values. Write protected?
How could this be done?
Thanks in advance.
Click to expand...
Click to collapse
Had the same problem with the sound af call start and solved it like this:
1. Use Total Commander (freeware) and copy the file Silent.prof.xml from the folder Application data\Profiles to the folder \Application data.
2. Then rename the copied file to Normal.prof.xml (or Meeting.prof.xml, if wished, this is the buzzing profile).
3. Now move the new Normal.prof.xml (or Meeting.prof.xml) back to the folder Application data\Profiles and overwrite the old file.
4. After this you'll to have to reconfigure your settings in the normal (and/or meeting) profile but the sound at call start won't return, even if device is restarted. After a hard reset you'll have to repeat the above mentioned actions to get rid of the sound again.
Got this solution from another S730 forum. Seems the Silent.prof.xml file is the only profile in which the sound at call start is disabled.
Ehm, looks like a nice solution but trough both Active Sync as Total Commander I only find the Meeting.prof.xml file (even if I change my Profile to Silence or normal or whatever).
JunkieXP said:
Ehm, looks like a nice solution but trough both Active Sync as Total Commander I only find the Meeting.prof.xml file (even if I change my Profile to Silence or normal or whatever).
Click to expand...
Click to collapse
Could it be that you're using the desktop version of Total Commander? The link i used in my previous post contains a download of TC for windows smartphone. You'll have to install it on you device and work with your device. For some reason then you will be able to see the Silent.prof.xml and perform the steps in my previous post.
I just installed the Cab File which provided in your link.
It's a strange world .
Edit: Never Mind, got the Registry Fix Done, Thanks Anyway (I Love all those Registry Tweaks)
JunkieXP said:
Ehm, looks like a nice solution but trough both Active Sync as Total Commander I only find the Meeting.prof.xml file (even if I change my Profile to Silence or normal or whatever).
Click to expand...
Click to collapse
If you dont have "show hidden files and folders" enabled you might not be able to see them either, not sure but its also a possibility.
nightcrow said:
Got this solution from another S730 forum. Seems the Silent.prof.xml file is the only profile in which the sound at call start is disabled.
Click to expand...
Click to collapse
Perhaps a stupid question, but will the sound disappear in ALL the profiles using this technique? Or only in the new profile?
And is there also a way to disable the sound made at the end of a call?
Thanks for the solution!
I think the sound won't disappear from all the profiles. E.g. the outside profile can't be found even if you use TC on your device. Therefore you won't be able to overwrite that profile. I'm personally using the normal, buzzing and silent profiles most often so I can live with this solution. You might want to try and rename a copied Silent.prof.xml to Outside.prof.xml, move it to the original folder and see if anything happens. Never tried this.
Never been aware of a sound at hang-up, so don't know if it was there before I changed the profiles. In any case I'm not hearing any sound now.
That's what I figured. Thanks for the reply.
Seems like I totally scr*wed up my Meeting Profile.
At first i'd just try to edit the CallStart Value in the XML file from 2 to 0 and uploaded this via Active Sync My Documents. After that I remapped the File to Application Data/Profiles and Overwrite the Current Meeting Profile.
All worked Fine until I changed my Profile to Normal and back to Meeting. From now on I can't select or edit the Meeting profile. I've also tried to replace the Meeting profile with another profile using Meeting.prof.xml but without any result, Also tried to reset the profiles within the phone using Profile -> Menu -> Option 4 but still I can't do anything with my Meeting profile.
Does anyone has Any Idea?
Edit: A Couple of hours after the first apparence of this issue it resolved itself without a restart or any other handling, does anyone has any idea how I can change the CallStart value without disabling the Meeting Profile, I compared both Meeting and Silent and i'm 95% sure it must be this CallStart Value which has to be Changed.
Are you just trying to kill the sound on specific profiles or from the whole phone? Have you verefied that the registry edit will not stick for you?
From your issue it sounds like something was not put into the profile properly causing the issues, and window's found the problem and reset it to work again.
If I use the Registry Change I can do this everytime I change my Profile.
Using the XML file I was also trying to change the Vibration mode (I want to Combine Vibration and Sound but the Pulsating of a Text message has to be different from the Call Sound).
Does anyone has any idea about what's going to happen after you completely remove the CallStart Entry from your register? Doesn't this solve the problem or does this cause an error or something.
Several things could happen, its not a huge key so windows might just pass over it, however if the profiles are looking for it then you might run into some stability issues there. If you delete the key from profiles from looking for it in the registry as well then you might not have any problems.
Either way windows could either become unstable during calls or associated sounds, windows will restore the key, or nothing will happen.
I now also tried to edit the XML via Total Commander and saved it the Normal way, as Unicode and as Text, but all disables the use of the specified profile until a "reset to standard".
Anyone has any idea how to change XML profile files without making them incompatible.
I found the solution - just edit the properties of Normal.prof.xml and enable system flag (e.g. in Total Commander). That's all
I totally love you Radiax , you are my Hero for today .
First it wasn't possible cause I didn't catch Total Commander update of April 24th but now I've installed Total Commander 2.5 and it works flawless.
Damn I'm so darn Happy!
Let's create a new topic about possible Settings of the Script value . I can't manage to let my ringtone ring while my vibrator () is pulsing.
v0.3w0.2v0.3p is working but pv0.3w02.v0.3 isn't working.
In learning how to cook from the many good resources on this site I have read in several places that the contents of the mxip* provxml files will get re-written on every device boot. This means that some changes to the regsitry must be cooked in, or they will be lost on a reboot.
One such thread/post that details this is here.
Now the official thread from MSDN on these files is here, and it says this:
An Image Update Package can contain two types of provisioning files:
Cold boot files that will be processed by Configuration Manager only when the device is cold booted. The provisioning file name must have one of the following formats:
mxipcold_PACKAGENAME_*.provxml
or
mxip_PACKAGENAME_*.provxml
where PACKAGENAME is the name of Image Update package.
These files should contain settings that you intend to be applied only during cold boot.
Update files that will be processed by Configuration Manager both when the device is cold booted and, if their associated packages have been updated, during Image Update. The provisioning file name must have the following format:
mxipupdate_PACKAGENAME_*.provxml
All settings contained in these files will be re-applied whenever their associated packages are updated, regardless of whether they have or have not changed. Therefore, these files should only contain settings that you intend to be reapplied every time their packages are updated.
Microsoft recommends that you use a three-digit number in the name of your .provxml files in ROM, such as mxip_opr_100, mxip_opr_200, mxip_opr_300, so that there is an adequate number of ordinals to identify successive versions of the file.
Note Mobile Operators should avoid using provxml files to override (shadow) entries in Microsoft-owned provxml filesNote 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.Now the reason I am posting is based on my experience and the underlined section above. This seems to state that a "cold boot" is equal to "when the device is initially configured."
What this means is that these mxip files DO get processed on a cold boot, but that a cold boot does not mean a reset/full-power off, but rather a CLEAR STORAGE.
My own tests show this to be the case. For instance, I have taken reg entries from several mxip, mxipupdate, and mxipcold PROVXML files which shipped with the latest AT&T stock ROM (decompiled with KaiserKitchen).
When I delete these values on my device THEY DO NOT COME BACK AFTER A REBOOT.
Based on these two facts it would seem to me that any statement which claims that these provxml files re-write the registry at every reboot is incorrect.
I would love for this to be corroborated by others or in fact, I would love to be proven this incorrect.
Not only do I want to know what it right...but I have a particular instance where a registry key is getting re-written at every boot. This value being overwritten is not defined in any XML, so my assumption is a DLL or other system service is resetting it. At this point, the particular value is not important to the discussion but if indeed there were a way to define in a provxml file a registry key which would be overwritten at reboot, that would be helpful.
Please advise!
thx
Anyone?
I'm looking for any proof that any xml files cooked into a ROM can reset registry entries on a standard reboot.
Cold-reboot = hard-reset, and as such yes all your provisioning files will re-run.
However it seems to me that the only thing which would re-apply a registry key would be a service/application/driver which is hard coded to do so and not anything specified in a provisioning file.
bengalih said:
Anyone?
I'm looking for any proof that any xml files cooked into a ROM can reset registry entries on a standard reboot.
Cold-reboot = hard-reset, and as such yes all your provisioning files will re-run.
However it seems to me that the only thing which would re-apply a registry key would be a service/application/driver which is hard coded to do so and not anything specified in a provisioning file.
Click to expand...
Click to collapse
If by "standard reboot" you mean soft reset then of course no settings are loaded into registry from any of your provisioning or other XMLs (unless you have some specifically set to be loaded at start up). The registry settings stay the same as you had them before soft reset.
But obviously they are read and loaded into reg after every hard reset, not only because autorun (customization) starts after hard reset - what does not happen after soft reset - but also because registry itself is recreated 'from scratch' after hard reset, *with* the settings from your XMLs (of course if there are pointers to them in your settings, otherwise even if they are there they will be 'excluded' or 'omitted' and become what I call "ghost files" - a files that don't do nothing but taking up space /edit: best example of XML "ghost file" is i.e. config.xml which didn't have its pointer in Config.txt thus all its registry settings were entirely omitted on every hard reset, as I saw in one of the ROMs).
You won't find "any proof that any xml files cooked into a ROM can reset registry entries on a standard reboot" because it is impossible (again - if by standard reboot you mean soft reset and not hard reset).
Thanks for your reply. What you are saying backs up what my beliefs are and my experience suggests. I don't want to call anyone out for providing false information (unintentionally I'm sure). But I have seen several posts by well regarded members that speak differently.
-888- said:
If by "standard reboot" you mean soft reset then of course no settings are loaded into registry from any of your provisioning or other XMLs (unless you have some specifically set to be loaded at start up). The registry settings stay the same as you had them before soft reset.
Click to expand...
Click to collapse
Again, I agree. However how do you explain this post and the others in the thread supporting the fact that a certain registry setting must be cooked in and will not survive a reboot?:
http://forum.xda-developers.com/showthread.php?p=2106160#post2106160
Also, what do you mean by "unless you have some specifically set to be loaded at start up"? How do you have a registry key specifically set to be loaded at start up? All regsitry keys are loaded at start-up (obviously). I pick out this comment because maybe this is the crux of the issue, if there is something I am unaware of. Are you saying there is a section in the registry that will automatically load certaind reg entries at boot (effectively overwriting them)? I would be unaware of anything like this, so please explain the statement.
-888- said:
But obviously they are read and loaded into reg after every hard reset, not only because autorun (customization) starts after hard reset - what does not happen after soft reset - but also because registry itself is recreated 'from scratch' after hard reset, *with* the settings from your XMLs (of course if there are pointers to them in your settings, otherwise even if they are there they will be 'excluded' or 'omitted' and become what I call "ghost files" - a files that don't do nothing but taking up space /edit: best example of XML "ghost file" is i.e. config.xml which didn't have its pointer in Config.txt thus all its registry settings were entirely omitted on every hard reset, as I saw in one of the ROMs).
Click to expand...
Click to collapse
I think this pretty accurate. However, I think technically the registry is created at cooking from the .REG files. The .REG files combine to make the .hv files, which are basically the flat file system that gets loaded to make the registry. The .XMLs which contain registry entries then get additionally loaded during customization, but the majority of the registry already exists in the .hv files. Would you agree?
-888- said:
You won't find "any proof that any xml files cooked into a ROM can reset registry entries on a standard reboot" because it is impossible (again - if by standard reboot you mean soft reset and not hard reset).
Click to expand...
Click to collapse
Right, ok, I am thinking as much. But still would like to understand why posts like the one I referenced claim that settings need to be cooked in or they will be lost on a reboot. These posts clearly seem to mean a standard-reboot, as a user who makes a regsitry change would obviously expect that change to be lost on a hard-reset. These posts definitly infer that the changes get lost on a "standard" reboot.
Cold Boot = Hard Reset or Clear Storage or Nand/OS Format (via Mtty/Ptty)
Provisioning xml's are most typically used by Operators to limit functionality, i.e AT&T uses them to disable the "Multiple Data Sessions Hack" by changing the AGPN RIL settings. These are used to overwrite certain registry settings established on boot before the OS even loads. Similarly, the standard provxml files do NOTHING, unless called for. This does not happen at a soft reset, only at hard reset & the difference is in the type of registry setting you are targeting. As stated before, some registry settings are loaded very early into the boot cycle, before the os even initializes, & are persistent so that they cannot be changed manually period. The RIL settings, used to enable the use of MediaNet & BBC concurrently are one such example. Provisioning Xml's only run when called for or when manually initiated with the use of a program capable of importing the xml's, such as SKTools.
There are indeed many setting that will revert when a soft reset is made.
bengalih said:
Again, I agree. However how do you explain this post and the others in the thread supporting the fact that a certain registry setting must be cooked in and will not survive a reboot?:
http://forum.xda-developers.com/showthread.php?p=2106160#post2106160
These posts clearly seem to mean a standard-reboot, as a user who makes a regsitry change would obviously expect that change to be lost on a hard-reset. These posts definitly infer that the changes get lost on a "standard" reboot.
Click to expand...
Click to collapse
i think these guys are gettin confused with reboots... maybe i'm wrong, but they also said that the hives get rebuilt on every reboot, i really doubt it...
agreed that provxml files only apply to a hard reset, but also did a little testing with that particular reg key... changed both values, reboot, activesync'd and surfed the net, reboot, same values, changed them back to original, reboot, everything sticks... i don't know what these guys are talking about, but it doesn't make any sense...
also, i can't find those settings in the stock att provxml files in OperatorPKG...
Thanks for replying GSLEON3. I understand everything you are saying about PROVXMLs, and I think we are on the same page, but I am still confused about some things you are saying...
For example in your post about the AGPSNVSetting. You state that you need to change it in the PROVXML file. You also state:
THIS HAS TO BE COOKED IN, REG EDITS AFTER INSTALLING WILL NOT STICK
Click to expand...
Click to collapse
My question is, what do you mean by it won't stick? If I go in with a registry editor after I have flashed the ROM and try to change it from 6 to 5. What happens? Either:
A) When I reboot the value will revert back to 6.
B) The value will remain at the 5 I set it to, but it won't actually work.
If the answer is A, then I ask how? How does it get set back to 6 if we established that the PROVXML files only get run during a cold boot/reset?
If the answer is B, then i ask how? A reg entry is a reg entry is a reg entry. If the value is set to 5, then whatever service reads that value should be seeing a 5. It shouldn't matter if that value was originally 6, as long as it is now 5 (and remains that way after a reboot).
This also leads into the comment you just made:
some registry settings are loaded very early into the boot cycle, before the os even initializes, & are persistent so that they cannot be changed manually period
Click to expand...
Click to collapse
I don't know if I totally agree with that. I think it depends when the OS loads. I would think that since all your registry entries are stored in the .hv file on your device that the OS needs to load first in order to initizlize the drivers to read that .hv file and mount it to the registry. That might just be nit-picky if you mean before you get the higher leverl drivers and GUI initialized.
But, the question still is what makes them "persistent so that they cannot be changed"?
In summary, a provxml only writes a reg entry ONCE, on cold boot/reset. This value appears in my experiments to be able to be changed afterwards and sticks (meaning it stays the same value after a normal reboot). Why then would a registry entry need cooking in instead of just a manual change afterwards?
I am not trying to argue here, OR prove you wrong.. I am just really trying to understand why you state what you do.
Thanks!
If you change the registry and then soft reset via pressing the reset button within a few seconds upto even a couple minutes then your edit is lost, as the registry is cached in ram and only written out after a bit...
You can get an edit to "stick" by
doing the change, then wait a bit, then power off, then power on, then wait a bit, then soft reset. All the above it to convince WinMO to flush the cache.
Or use any software-based soft reset (those let the OS know its resetting, so it flushes the reg cache.
Either that, or there is something running in the background resetting registry entries. HTC_Guardian, for example, is/was an app used to reset connection settings, at least under sprint. That evil thing slammed the "correct" values into the registry every 5 minutes or so... what a waste.
In either case, the proxml things only run on a hard reset/first boot init.
schettj said:
If you change the registry and then soft reset via pressing the reset button within a few seconds upto even a couple minutes then your edit is lost, as the registry is cached in ram and only written out after a bit...
Click to expand...
Click to collapse
Thanks for the feedback. I don't buy that however (at least not on the Kaiser). I can make a regsitry change with say, PHM and the split-second after I make that change I push in the reset button... that change is kept.
If it does that for one reg entry, it should do that for all. I don't believe that some entries get cached like that and other don't
schettj said:
Either that, or there is something running in the background resetting registry entries. HTC_Guardian, for example, is/was an app used to reset connection settings, at least under sprint. That evil thing slammed the "correct" values into the registry every 5 minutes or so... what a waste.
Click to expand...
Click to collapse
See, I think you are correct here. I believe that in all the cases where I have seen a registry entry get reset on a reboot is because a driver is hard coded to reset it at boot time. On the latest AT&T release for instance if you change the LockLevel for backlight it is always reset to 0 after a reboot. There is no reference to this registry value in the rgu's or provxmls in the decompiled ROM.
schettj said:
In either case, the proxml things only run on a hard reset/first boot init.
Click to expand...
Click to collapse
agreed
bengalih said:
Thanks for the feedback. I don't buy that however (at least not on the Kaiser). I can make a regsitry change with say, PHM and the split-second after I make that change I push in the reset button... that change is kept.
Click to expand...
Click to collapse
You don't have to believe it, but i know this can be true. I can't speak to the cause, but i know that often times i must make my entry and then exit the program before i soft reset or my settings will not be kept. Also, I have experience many times where i will make a registry edit, and if i do not soft reset before doing anything else then my edit does not take effect. For example, i'll reply to a sms before soft resetting and my entries won't take effect. For this to be true then the original entries must be stored somewhere, at least temporarily. It certainly could depend on the software used though, and may have nothing to do with the rom. As i said, i can't speak to the reasons why this would occur as well as man others, but i can state my experiences through making thousands of registry changes.
I just tested this. 5 times, 5 different registy entries using PHM Reg Editor with both the stock AT&T and HTC 6.1 ROMs.
Each time I made a change, I pushed my stylus into the reset button immediately after clicking on OK to the change.
In every case, my registry entry remained the way I changed it to prior to boot.
I would be interested if you could recreate results to the contrary and if so what ROM and registry editor you are using.
scotchua said:
You don't have to believe it, but i know this can be true. I can't speak to the cause, but i know that often times i must make my entry and then exit the program before i soft reset or my settings will not be kept. Also, I have experience many times where i will make a registry edit, and if i do not soft reset before doing anything else then my edit does not take effect. For example, i'll reply to a sms before soft resetting and my entries won't take effect. For this to be true then the original entries must be stored somewhere, at least temporarily. It certainly could depend on the software used though, and may have nothing to do with the rom. As i said, i can't speak to the reasons why this would occur as well as man others, but i can state my experiences through making thousands of registry changes.
Click to expand...
Click to collapse
Hard reset, softt reset, rom update, cold boot, warm boot, clear boot,image update...
Hello
I found some usefull links.
The well-known articles about mixp, mixpudate and mixpcold...:
msdn.microsoft.com/en-us/library/ms889522.aspx
msdn.microsoft.com/en-us/library/bb737254.aspx
Definitions of Power States Transitions
msdn.microsoft.com/en-us/library/aa450592.aspx
Definitios of "clean/cold/warm booting" and their issues:
msdn.microsoft.com/en-us/library/ee490762.aspx
Terms of "Image Update"
msdn.microsoft.com/en-us/library/bb737478.aspx
msdn.microsoft.com/en-us/library/bb737638.aspx
I think that a Soft-reset is like a warm-boot, a Hard-reset is like a clean-boot and you only have to remove all de batteries (all power off) to get a cold-boot. I now understand why some fellows tells to me to remove the battery two minutes .
So
remove the battery or exhausted -> cold boot -> mixp & mixpcold & mixpupdate
hard-reset -> clear boot -> mixp & mixpcold & mixpudate
soft-reset -> warm-boot -> no mixp*
rom update -> image-update of all parts of the rom -> mixp & mixpcold & mixpudate
So normally, every time that you change the rom or order a hard-reset you mobile should execute all mixp*
From time to time something goes wrong when processing mixps during the fisrt boot after a rom-update and then you need to order a hard-reset to execute all mixp*again. I suspect that this happens when hard-spl does not force a cold-boot after the rom-update process and a warm-boot happens.
Finally
File System Boot Process. Describe which and when the actions happens:
msdn.microsoft.com/en-us/library/ee490357.aspx
Best regards.
I know this reply is seriously late in coming, but I was working thru a few registry issues and fixing a few chef cooked roms and this thread popped up.
Maybe it'll help someone in the future, trying to understand this dying architecture. (Curse you M$)
What you are failing to see, is that there are several ways that provisioning xml's can be delivered. Via cab files, straight provxml file or even xml's called on startup, not justat cold/hot boot.
AT&T as well as other OEM's used to have a bad habit of SHADOWING MS or HTC registry settings (Overwritting reg values thru use of xml provisioning). AT&T would call for their OEM Network Provisioning xml to silently install at every reset, much like a 2577 cab file. The OEM can also use the OAL (OEM Adaptation Layer) to overide or change settings in the registry, even thru the use of provisioning xmls.
The old AT&T APN provisioning via cab file we saw in Kaiser & first TP rom is a very good example of bad practices with regards to xml usage.
You can also set certain reg keys to be persistent. Try deleting the "Windows Default" (CHome) today registry key. without negating the setting with a nocharacteristic xml setting or a reg such as [-hklm/current user/etc...] this key will be persitent and also cannot be deleted.
Provxml's are good for moving things & certain settings, however, I have come to believe that registry optimization is a key component in device performance & with the new HV editing tools, you are better off adding entries directly to the hive & keeping the windows directory clean & light.
I wish only more chef's would utiolize these new tools & features. Have you ever gone thru a cooked rom registry & found all of the hanging & invalid registry keys?
The common cooked rom, even from the bvest cooks at XDA, usually have anywhere from 12% to 24% of empty or invalid registry settings. On top of that, you can have upwards of 12% - 18% invalid system type registry settings & then another 24% - 28% invalid user type registry settings.
The average cooked rom has a reg size of 811088. This number when optimized with proper settings & true removal of defunct values/keys would be more in the 647000 size range. That is common for a good chef, now imagine the guy using the standard rom kitchen based on a straight OEM rom. Cooks forget that registry values come from xml's, cab's, registry hives, even some executables. Setting are often duplicated between packages and hive and OEM provisioning files. This means that just because you remove a package from your kitchen does NOT mean that all the related registry data for that package will also be removed. For this you really need to modify the hives manually with the new HV editing tools, or completely rebuild the hives using a newer kitchen like OS Builder that allows you to build HV files from scratch. even then I recommend usign HV editing tools to confirm nothing is left behind unintentionally.
An optimized registry absolutely means increased performance.
Hello,
I have the HTC Touch Diamond with WM6.1. I love the phone but my exchange administrator has implemented password protection for my email account. So every hour my phone is locked until I enter the password. Does anyone know how to extend the time or disable the password in the registry. I have found several references to the registry setting in WM5 but that did not work so I am wondering if it is a different entry in WM6.1 Any ideas?
Can anyone help me with this?
This should work on WM6.1:
\hklm\security\policies\policies
Change value name "00001023" from '0' to '1'.
Or: http://cid-79cd30393341a619.skydrive.live.com/self.aspx/Public/WMSimulateKeyPress.zip
Or: http://www.modernnomads.info/wiki/i...ation+when+your+PocketPC+is+on+external+power
Or: http://mobilitytoday.com/forum/showthread.php?t=13030&page=2
Btw, think about it before you remove this policy. The sysadmin does not enforce this policy for nothing. I learned to live with it, it also has some advantages (for example when your device is stolen and you won't accidently push any buttons)
Thanks for the reply. the 3rd link which is Zen's program does not seem to work in WM6.1 in the Diamond. The registry entry definitely does not work because I have set it and reset the phone and it still locks. You have a point about why the password is there but it becomes a safety issue when I am driving and need to make a phone call. I am not sure what the Simulate Key press does could you provide any more information?
I am finding that with the HTC diamond alot of the customization has changed alot of the functions for the registry. I wish I could find someone that has figured all this out.
is there a simple way to change the location of ringtones such as edit the registry?? everytime i change a ringtone it need to send to the main memory..i want to make it easier.. THX
HKEY_CURRENT_USER\ControlPanel\SoundCategories\RingDirectory = Storage Card\music
How
I am new to this community and just got my first WM phone a couple of days a go, TOPAZ..
How do I use regedit to alternate like shown above???
You can try PHM regedit. It's same like desktop pc regedit.
you can also try the "pocket version" of TotalCommander, there a biult-in Plugin for the registry
Problemo
Hey
Couldn't get it to work, and couldn't actually find the exact HKEY either from HKEY_CURRENT_USER\ControlPanel\SoundCategories\Rin gDirectory = Storage Card\music.
For me it was identical up till \SoundCategories, but no RingDirectory key. It looked something like HKEY_CURRENT_USER\ControlPanel\SoundCategories\Ring\Directory
Modifying the Ring\Directory into "Storage Card\music" didn't help either, any ideas what could be the problem?
Also cannot get this to work. Have changed the setting from original \windows\ to Storage Card\music. Can anyone advise on the exact think to type in the space. Even tried adding the \ in front but same results
I tried it as well and didn't work. The strange thing is that I also used SKTools and found this as a configurable setting and it did nothing as well, seems that it was changing the same registry value.