Related
I've been trying to get to the bottom of this Windows Live Messenger business and finally after going through several redundant threads, this is what I found. Hope it helps to rid everybody of all doubts regarding the various versions of this crappy but kind of must-need software.
LATEST VERSION
CLICK HERE
Information
Version: 10.7.0061.0500
Date Published: 1/8/2010 (Jan 8th 2010)
Language: English
Credits: Post Reference
There are 2 files available at the download site. Please note that WindowsLive_0409.PPC2005_arm.cab is English-only.
OLDER VERSIONS
1) 10.6.31.1600 (aka 10.6.0031.1600)
This is the first version of Live Messenger to get rid of that most annoying Contact Sync feature which would copy all your MSN contacts to your phone book.
2) 10.6.31.2600
This one has been around in the various forums for a while now. I'm yet to try it out though. I don't imagine there will be too much of a change between this and the previous version.
I found 2 cabs of the .31.2600 from 2 different users. The one posted by 'duttythroy' is 1.80 MB while the other one is 1.97 MB.
3) 10.6.32.2100
I found 2 cabs of the .32.2100 from 2 different users again. Both of them don't install to the Storage card even though during setup you are prompted for the destination.
Both are almost the same size and were posted by 2 different users, one of them being 'duttythroy'. The one posted by 'duttythroy' is 18,89,104 bytes while the other file is 18,91,699 bytes.
Except for fewer files in v10.6.32.2100 (56 files) compared to v10.6.31.1600 (155 files), I couldn't find anything else different. If aything it'll reduce the time needed to browse through your Windows folder compared to the when the previous versions were installed. Also the option to disable copying of all MSN contacts to the phonebook is still there. NO WORRIES THERE. Phew.
4) 10.6.33.0600
I honestly can't see anything different with this release. However there is some increase in file sizes of most of the DLL's. The overall package has gone from 1.80MB of the last version (10.6.32.2100) to 2MB for this version (10.6.33.0600)
Note: There was a small registry entry problem with this cab. It has now been fixed and will work fresh off the bat.
5) 10.6.34.0800
As before, there isn't any noticeable difference from the previous version with the exception of an increase in filesize.
Thanks to qtek_metanol who made this version available to us.
PROBLEMS and TROUBLESHOOTING
There have been lots of people who have had trouble with installing and running Windows Live and Live Messeger. There are few things you can do to avoid these problems.
1) DO NOT INSTALL TO THE STORAGE CARD. Some of the file references have been hardcoded into the DLL's. Hence as far as I know, installing Windows Live to your Storage Card will not work. It will install but nothing will happen when you run the program.
2) Make sure you uninstall any previous version of Windows Live that you may have. I would suggest going into Safe Mode to uninstall it to make sure that all files and registry entries are completely removed. You can get access to Safe Mode if you have monocube's Safemode program or SPB Pocket Plus. If you can't do this, then atleast sign out, disable email sync and then soft reset your device before attempting to uninstall.
3) If you have just hard reseted your device, then please make sure that one of the first programs you install is Windows Live. Many users have complained that Live Messenger doesn't work after installing some programs and alternate Language support.
4) The Windows Live versions posted here, give you the option to either copy your MSN contacts to the phonebook or not. If you chose to copy your MSN contacts to the phonebook during installation and then later decided you wanted to remove them from the phonebook... whatever you do, DO NOT DELETE YOUR MSN CONTACTS FROM THE PHONEBOOK. This will result in you loosing all your MSN contacts completely (from the MSN Server). The safe way to remove MSN contacts from your phonebook it to go to Windows Live -> Menu -> Options -> Sync Options -> Uncheck "Store Windows Live Contacts in your mobile phone's Contact List"
5) As a rule of thumb, it's always a good idea to backup your MSN contacts on your desktop. The desktop version of Windows Live Messenger or MSN Messenger has an option to export all your contacts to a file on your computer. There have been a few users that have complained about Live Contacts getting inadvertently copied to the Phonebook despite unchecking the option to sync MSN contacts to the phonebook. This is usually the result of an error during installation or what Microsoft calls a gremlin in the depths of the code. In such cases having a file with all your contacts makes it easy for you recover from an accidental deletion of all your contacts.
STEP-BY-STEP
INSTALLATION
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SETUP
Windows Live
Live Messenger
Nice one
but...how can I make this work over WIFI on my Vario III?
Cheers,
DJ
/edit got it working
Next question....how can I stop T-Mobile from knowing I'm using instant messaging on a tarriff that doesnt allow it
Difference between 10.6.32.2100 (duttythroy) and 10.6.32.2100 (Fixed)
The (Fixed) cab has one extra file named mxipupdate_windowslive_1.provxml
These are the contents of the file.
<wap-provisioningdoc>
<characteristic type="FileOperation">
<characteristic type="%CE11%" translation="install">
<characteristic type="MakeDir" />
<characteristic type="Windows Live.lnk" translation="install">
<characteristic type="Copy">
<parm name="Source" value="\Windows\WLMLauncher.lnk" translation="install" />
</characteristic>
</characteristic>
</characteristic>
<characteristic type="%CE11%" translation="install">
<characteristic type="MakeDir" />
<characteristic type="Windows Messenger.lnk" translation="install">
<characteristic type="Copy">
<parm name="Source" value="\Windows\WLMMessenger.lnk" translation="install" />
</characteristic>
</characteristic>
</characteristic>
<characteristic type="%CE11%\Pocket MSN.lnk" translation="install">
<characteristic type="Delete">
<parm name="ForceDelete"/>
</characteristic>
</characteristic>
<characteristic type="%CE2%\Help\Pocket MSN.lnk" translation="install">
<characteristic type="Delete">
<parm name="ForceDelete"/>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
anothe one for you guys enjoy
duttythroy Windows Live 10.6.33.600.zip
LOL... Thanks very much for that dutty(throy) much appreciated. Just flashed one of your Supa Dupa ROMS... love it.
lol
I havent remember seeing you on the hermes forum
More of a silent reader than anything else... Love my Hermes a lot more thanks to your SUPA CLEAN ROM
Updated the first post with the latest version.
leepriestenator said:
More of a silent reader than anything else... Love my Hermes a lot more thanks to your SUPA CLEAN ROM
Updated the first post with the latest version.
Click to expand...
Click to collapse
enjoy If i encounter any other new releases I will update you, glad to see a fellow men who loves Windows live like me
Absolutely... thought i'll just help clear up all the redundant... "Which one is the latest Windows Live version?" threads.
Thanks duttythroy... much appreciated.
10.6.33.600 - LATEST
Click to expand...
Click to collapse
The last version doesn't have any special improvement in relation to the formers versions. The contacts bug is still present, the option to install to the Storage Card works!
@qtek_metanol... could you please check if your Windows folder had any files that start with the names WLM?
I tried installing every version to the storage card and none of them work post installation. Wierd.
Hey there,
just wanted to say great thread and ask 1 question
Does anybody know why my hotmail account wont sync with windows live mobile? Everytime it begins to sync it stays there forever untill it says that " the remote server didnt resond or something like that".
It's really annoying since I was able to sync everything with the first build that was shipped with the TOuch.
Any help would be highly appreciated, thanks!
That happens to me sometimes when i'm on a GPRS connection. What does work for me is using the Send / Recieve option inside the Messaging app over a WiFi connection. The data load during the first sync after installation can be quite large. GPRS connections tend to time out.
leepriestenator said:
@qtek_metanol... could you please check if your Windows folder had any files that start with the names WLM?
I tried installing every version to the storage card and none of them work post installation. Wierd.
Click to expand...
Click to collapse
Hi leepriestenator,
I have some WLM files in the Windows folder, but the reason is because I am using a Windows 6 Version which has the WLM application fixed to the OS.
Bu anyway, the installer of the new WLM version gave me the option to install the application on the Storage Card and I did so, now i have a folder Windows on the Storage Card and there can i see all the WLM files from the new version, after a check of the data, the working version is the new fresh installed one and not the older one from ROM.
someone making a cab for the latest ver?
@ qtek... if it's not too much to ask... could you please make a list off all the files starting with WLM in the Root Windows folder and post them here. Also I would appreciate it if you could export your entire registry and send it to me.
A fresh installation of WLM will not work if installed to the storage card. I think the version number is coded into the exe's and when you run the application it is relying on some critical files which are in your windows folder even though they are older versions.
If you can post the names of the files in the Main Windows folder, then i'll probably be able to work off it and create a new cab that can work straight from the Storage Card with minimal dependencies in the Root Windows folder.
@jakeypoo... Latest version? As far as I know v10.6.33.0600 is at the moment the latest. Let me know if you know otherwise.
Thanks
I've heard that this version is actually an older version?
How so? According to the version number, it is the latest. This is currently the latest build available in the forum.
I have downloaded the latest version and try to install on storage card, unfortunately my Dopod D810 with official WM6 complainted that it does not have authority to install. But when i select install to device, it installed properly and run ok.
So with all the cooked roms im sure this isnt going to interest alot of people but will post it anyway.. Looks like the only thing that changed was the CE version and some things added/removed/fixed.. Nevertheless, Enjoy!
From
Software version
GSM Radio: 1.27.14.09
Protocol version: 22.45.88.07H
CE version: 1.60.502.3
OS build: Windows Mobile 6 AKU 0.4.4 Build 18128
To
Software version
GSM Radio: 1.27.14.09
Protocol version: 22.45.88.07H
CE version: 1.61.502.2
OS build: Windows Mobile 6 AKU 0.4.4 Build 18128
Feature Added
Add MTV Cribs
Issues Fixed
Remove MySpace
Fast Forward and Rewind don't work with BT headset
Complaints of excessive background noise, BT HS, noisy
environment - Using BT Mot HS820.
Volume control doesn't work with BT.
The HTC phone failed to provide the capability to adjust the
audio volume.
MSN-Not able to block the contact.
Wrong user message to invitee when group membership
invitation is accepted.
Download me here
I'm new to this forum but I'm currently using Schap's 4.3 and Radio 1.27.12.17 on an ATT Tilt. Been having issues with static over the BT. Do our cooks take anything from oem roms? I'm hoping that the fixes in this rom get incorporated in the next version of cooked roms.
Great work. Any idea the date that this was released? Also, even though its not listed, any word on video performance?
thanks for the ROM
Nice work mate!
Is this a shipping ROM, from currently sold devices? (Nothing is altered?)
Thanks
this would be a shipping rom, not an altered or cooked rom.... this is not currently released by ATT yet
I figured, what the heck. I'm a flash-a-holic now...
Trying it out to see what happens. Might try cooking it myself too (if I'm feeling crazy enough).
Can anyone else verify what I am seeing? I am cooking with this ROM atm, and I am getting some new icons in Settings -> Connections: SMS Service, CSL Line Type (or something like that), and one other I believe. I actually removed the ROM from my device for the time being, but I would love to hear if anyone else is seeing that.
its nice to see HTC and AT-T making more roms for the kaiser~ they let us hermes users in the dark for a while
Thanks ,will try it tomorrow
its a oem rom so fulll of bloatware like game demos and appllications that encourage you to spend more money on your service plan its just ATT capitalizing ,nothing personel only business ! BS
Shadow7789 said:
Can anyone else verify what I am seeing? I am cooking with this ROM atm, and I am getting some new icons in Settings -> Connections: SMS Service, CSL Line Type (or something like that), and one other I believe. I actually removed the ROM from my device for the time being, but I would love to hear if anyone else is seeing that.
Click to expand...
Click to collapse
SMS Service and CSD Line Type are in the original 1.60 rom, but they are removed from connections menu through some registry edits in the operator package. You can get them back along with HSDPA by editing your registry.
are you serious about that MTV cribs thing that cant be a real app
Thanks for the response.
looked into the rom a bit and didn't find too many changes. lots of things i don't use seem to be updated including ptt, telenav, oz and some other bloatware. the only notable changes include and updated wavedev.dll and the following registry entry:
[HKEY_LOCAL_MACHINE\Software\OEM\Bluetooth]
"PhoneVol"=dword:C8 ; Default value : 200 (GSM_GAIN_4)
also in the operator package there is an addidtional entry:
<!-- ATT Reject Msg is enabled. 2007-12-10 -->
<characteristic type="Registry">
<characteristic type="HKLM\Drivers\BuiltIn\RIL" translation="filesystem" >
<parm name="EnableATTRejectMsg" datatype="integer" value="1" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
not exactly sure what that does. the SYS folder seems to be identical to 1.60.502.3
akadonny said:
looked into the rom a bit and didn't find too many changes. lots of things i don't use seem to be updated including ptt, telenav, oz and some other bloatware. the only notable changes include and updated wavedev.dll and the following registry entry:
Click to expand...
Click to collapse
i would imagine those changes there were to fix the volume problems as stated in the fixed section.
leoiden said:
its a oem rom so fulll of bloatware like game demos and appllications that encourage you to spend more money on your service plan its just ATT capitalizing ,nothing personel only business ! BS
Click to expand...
Click to collapse
Don't like, don't use it.
Thanks OP!
Cab with Audio Fix
For any interested parties, attached is a cab with the dll and registry entry. I personally don't use any kind of bluetooth headset so I can't tell you if this actually improves anything.
Edit: cab removed. seems to kill all audio. sorry about that folks. just unintstall and audio returns.
I frequently use a bluetooth ear piece so I'll be installing this to see if theres any change
How does one extract a CAB from a ROM?
For instance if I want to cook my own ROM, but I want to use some of the applications in say Dutty's latest release, how do I get those cab packages to install on my own?
Particularly, i am interested in pulling the latest remote desktop off of the latest test Tilt ROM because it has the ability to map the mobile's local storage.
thanks!
one word: RTFW.
Read The FFing Wiki!!
If I could find it on here I wouldn't have posted asking about it.
This is the first of my posts that have been met with a response like this, but honestly go troll somewhere else. It is 0% productive to make responses like that. You are cluttering up the forum with usesless posts (as much as I would be guilty of if this is indeed described in the wiki). If it's in the wiki, why don't you point me to where?
The wiki isn't a single page as much as you'd like to believe, it' links to hundreds and thousands of posts of information.
I have CIM and SIM unlocked my device, flashed about 5 different ROMS and radios and done numerous other things with info I have gotten from the wiki. I read through the ROM cooking kitchen tutorials, but could not find anything which mentions my task at hand. I found information and links on the cooking tutorials to use OEM cabs that people had already extracted....but what if the one I want isn't there? Where is the info that tells me how to pull one OUT of a ROM (instead of putting one already extracted IN)?
So, either you are misunderstanding what i want to do, or else the way i am phrasing it is misleading, both to you and to myself, which is maybe why i can't find the info I want.
So, please your brilliance, point me to location in the Wiki that would describe a procedure where i would be able to extract a .CAB (like Windows Mobile Desktop) from the latest AT&T test ROM.
Otherwise your contributions to this thread are unwanted.
while maarten might have pointed you in the wrong direction, your thread is still a redundant one. if you tried to search, you will find lots of threads covering this subject. and yea, your search results are probably gonna end up with tons of threads that end up looking like this thread, but if you sift through the results.......and by sift i mean u really really sift, i promise you, you will find something useful.
Simple Answer...
...You can't extract a CAB from a ROM usually.
Explanation: In the ROM itself things like windows live are extracted from the CAB already and are installed, so the CAB itself is not there. If your original question was how do I extract the files needed to MAKE a CAB.. then that's more complex, a different question, and a waste of your time if you don't already know how to do it.
If you really want to learn you will have to search.. if you just want a CAB of the latest windows live messenger get the build number by installing the ROM and looking in the application for it.. then use the google search of xda-developers (e.g. "Windows Live" <build number> )and you can be sure you will find someone has already done the hard work for you.
hope that helps.
You find threads on converting CAB's to OEM packages but not the other way round.
The trouble is when you extract a ROM, you'll probably find in the SYS directory, the OEM folder you want with all the relevent files. BUT you won't know where they all go. And if the files you want are in the OEMApps folder you won't know what files need to go together. What I do is look at a similar OEM package (See Alex's excellent work) and this will show the files you need, where they go plus any registry settings. You can probably copy over the newer files from your extracted ROM to the OEM package, overwriting the older files.
If the OEM package doesn't exist it will be a long, long job!! You need to search through the files on a device with the installed ROM and make a note of the location of the application files - this is required for the install.txt file. The next problem (& the major one) is to find any relevant registry settings - again you can search through the registry of the installed ROM. Now all this take a lot of time and effort...
odyseus said:
The next problem (& the major one) is to find any relevant registry settings - again you can search through the registry of the installed ROM. Now all this take a lot of time and effort...
Click to expand...
Click to collapse
You can cheat a little bit here though, some apps will recreate any missing entries with sensible defaults if you leave them out.. others wont.. for those you can find ANY version of the CAB that you want to use (even an older one say) and use its registry as a guide to where to find the ones for the new version.. the registry locations dont change that much between versions usually.
you'll still get issues.. but in most cases this helps if not works
Thanks for your info sambartle and odyseus. I had feared as much based on what I had found through search already, but thought there might have been a way... I guess _Alex_ and others do quite alot of legwork to extract and make all these things themselves.
I can't quite understand it however.... If I take a windows PC for example (which is similar in it's registry) I couldn't necessarily find all the associated files and registry keys associated with an application. If you are lucky they are all under one folder and one key of the registry... but something like MS Office installs so many shared files, and classes objects into the registry it would be nigh impossible to recreate that (even given the time).
Unfortunately, if the last posts I read are accurate the developers here won't be providing new OEM dumps for a while. Maybe once 6.1 is more widely released microsoft will allow download of the new mobile desktop.
Ah well, thanks for your help.... and to the other posters...it's worthless posts like yours that contribute nothing to the forum that makes extracting useful information through the forum more difficult than it should be.
bengalih said:
Thanks for your info sambartle and odyseus. I had feared as much based on what I had found through search already, but thought there might have been a way... I guess _Alex_ and others do quite alot of legwork to extract and make all these things themselves.
I can't quite understand it however.... If I take a windows PC for example (which is similar in it's registry) I couldn't necessarily find all the associated files and registry keys associated with an application. If you are lucky they are all under one folder and one key of the registry... but something like MS Office installs so many shared files, and classes objects into the registry it would be nigh impossible to recreate that (even given the time).
Click to expand...
Click to collapse
It requires alot of testing and re-installing or re-flashing, sometimes on the same ROM, sometimes on different ones, just to iron out the bugs. It's one of the reasons why I released AT&T and HTC versions in the past, just so that I can have two platforms to test on.
Windows CE is alot simpler than Windows XP by at least 10 fold. Yet there are people who have created portable versions of Microsoft Office through the use of deployment applications like thinstall, so anything *IS* possible, with automation.
Automation that works at the functionality of thinstall for CE doesn't exist because of economies of scale (e.g., it's not worth any developer's time to create a deployment package as robust as Thinstall for the PPC).
bengalih said:
Unfortunately, if the last posts I read are accurate the developers here won't be providing new OEM dumps for a while. Maybe once 6.1 is more widely released microsoft will allow download of the new mobile desktop.
Click to expand...
Click to collapse
Dumping and stripping is relatively easy once you've gotten the hang of it. You just need to keep at it.
Personally, I just don't find it to be challenging any more, since I've done quite a few AT&T/HTC WM6.0s and HTC WM6.1s and I'm now waiting for an official shipped version (no more leaked betas!!!).
bengalih said:
Ah well, thanks for your help.... and to the other posters...it's worthless posts like yours that contribute nothing to the forum that makes extracting useful information through the forum more difficult than it should be.
Click to expand...
Click to collapse
Your initial question / thread starter didn't have many details, so I would have flamed you too, although I would have also provided a link to my OEM Package Tutorial (Creating Packages from ROM files section)
It never hurts to be overly verbose when asking a question. This would make the flamers leave you alone (because they'll just get tired of reading) and should *NOBODY* respond within a couple of days, when you bump it (with flowery encouraging yet challenging words, like 'You guys are so great, but nobody could answer my question?'), nobody will mind that you did, and you will get answers after that bump...
FWIW, I still think this should have been a question asked in the OEM Tutorial thread, which I have subscribed and respond to much more frequently than new threads which I'm not aware of until I actually have the time to READ new threads. It's also because, should anyone have similar questions, it'd be much easier to fiind in the bigger OEM Tutorial thread than in this one...
Hope this helps!
Thanks Alex... as you said you would have provided me the link to your Creating Packages from ROM section which I did gloss over briefly previously but didn't totally see how it helped me (since I was looking for Cabs). But, now that you point me there I again I took another look and got some useful information.
So this is where i am at:
Ok,
So first I extract the ROM using your kitched script, then in the SYS folder I find two folders that seem to be what i want:
RemoteDesktopMobile
RemoteDesktopMobile_Lang_0409
Inside the first folder are subfolders with names like:
MvkLib.dll
and
wpctsc.exe
and inside those are an actual DLL or EXE file, and some other files called imageinfo.bin, imageinfo.txt, and some files S001, S002, s003, etc...
I am going under the assumption that all I need is the .DLL file, and the rest are some sort of uncompiled form of the DLL? (Please let me know if i need to pay attention to those other files.)
So I take all those DLL and EXE files. I also look for and find an INITFLASHFILES.DAT and don't see any references to these files, so i assume they all go in \WINDOWS?
There is also an RGU file inside here that has a few registry keys for this application.
Inside the second folder is just a DSM, and a couple of .txt and .htm files. Since these files aren't in INITFLASHFILES.DAT either, I assume they just go in \WINDOWS?
I also find a provxml file in \OEM\OEM_Lang_0409 called mxipupdate_RemoteDesktopMobile.provxml.
The contents are:
Code:
<wap-provisioningdoc>
<characteristic type="FileOperation">
<characteristic type="%CE11%" translation="install">
<characteristic type="MakeDir" />
<characteristic type="Remote Desktop Mobile.lnk" translation="install">
<characteristic type="Copy">
<parm name="Source" value="%CE2%\wpctsc.lnk" translation="install" />
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Based on my reading of the links off your page and some further research this file seems to say the following:
Make a directory (if it doesn't exist) called \Windows\Programs (%CE11%)
Make a shortcut in the directory called Remote Desktop Mobile.lnk (the decimal ASCII text) that maps to \Windows\wpctsc.lnk (%CE2%)
So... now I have:
A handful of files...I need to put them in \Windows
I have an RGU file with a couple registry entries I need to import into the registry
I need to make
a shortcut to the exe int the \Programs directory
How then do I now package all this up into a CAB that will automatically perform the above operations?
I know about "makecab" to actually package all these up into a cab. But how to i write the command file that tells it how to do all the provisioning and registry entries?
Please let me know I am on the right track.
Thanks!
Ok...I found a program called WinCE Cab manager that made the process pretty easy. I installed it on my device and it seems to work well.
I have uploaded it here:
http://rapidshare.com/files/104977265/Windows_Mobile_Desktop_6.1.cab.html
Where is the appropriate place to post this to share with others?
yeah like people have said dumping the rom is the way to do it but most roms nowaday dont have the files for you to recook(so no oems)
so the best thing is to do is get the cab yourself and convert it to an oem with ervius's package creator
sorry kidnamedAlbert...I'm not sure where you were getting at there... the whole point of my post was how to get those cabs made from the ROM in the first place. As you can see from the previous posts it seems I have already resolved (or started my way to) getting this done.
Personally, i prefer to have the cab file as I am more interested on just being able to install it on my device then cook it into a ROM. If someone wants to cook it into a ROM that seems to be a well documented procedure if the cab file is already available.
In my case, there was no cab file available for the latest version of Windows Mobile Desktop...so i made my own from the ROM.
Maarten_0031 said:
one word: RTFW.
Read The FFing Wiki!!
Click to expand...
Click to collapse
One word: RELAX and STOP SWEARING, geez.
Okay here is the super short super simple cooking tip/hack that is great for Multiple APN's & being able to utilize BES, BIS, Blackberry Connect, AcvtiveSync, & your primary data connections (i.e. MediaNet, etc...) at the same time
There is a simple provisioning XML that makes registry changes related to the RIL settings. In your dumped ROM folders locate the "OEM" Folder & within the OEM folder locate OperatorPKG.
Within the OperatorPKG you will find this provisioning XML:
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Drivers\BuiltIn\RIL">
[B][COLOR="Red"]<parm name="AGPSNVSetting" datatype="integer" value="6" />[/COLOR][/B]
<parm name="NIEnable" datatype="integer" value="1" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
The registry setting we want to change via this provisioning XML is the "AGPSNVSetting" value.
*ALSO NOTE: THIS HAS TO BE COOKED IN, REG EDITS AFTER INSTALLING WILL NOT STICK
Change this value to "5" & you will have multi-apn's at least where bbc & primary data (medianet, etc.) are concerned. The final revised xml doc should now look like this:
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Drivers\BuiltIn\RIL">
[B][COLOR="Blue"]<parm name="AGPSNVSetting" datatype="integer" value=[SIZE="3"]"5"[/SIZE] />[/COLOR][/B]
<parm name="NIEnable" datatype="integer" value="1" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
I've also been playing with 4 as a setting & while it also allows ISP + BBC + MediaNet, (from time to time) it is still only works intermitently. The 5 value is solid as a rock though!
Make this change & your BBC ROM users will thank you as they will no longer have to Kill one data session to use the other!
Dude....search and read the wiki! Jeez!
OH WAIT! This is not a n00b question. Dang, my brain automatically switches to n00b defending mode!
Anyway, thank you for the tip. I will give it a try.
Very cool hack my friend,
I'm going to try it right away
Leo
What do you mean it won't stick? Does it unstick on soft-reset, or during runtime?
It's Persistent Registry. Any boot, or system level function & the value will revert to the that ascribed by the xml. So, for example AT&T limits it to one connection at any given time to save B/W. If you edited it with a registry explorer & then played around changing things or reboot, the value they set in the xml will return.
Dude....search and read the wiki! Jeez!
OH WAIT! This is not a n00b question. Dang, my brain automatically switches to n00b defending mode!
Anyway, thank you for the tip. I will give it a try.
Click to expand...
Click to collapse
I'm a special Noobie, I mean don't you know how I am? I'm unique! I don't need to read, duh!
Noobie Flaming Mode is more like it
Let me be a nOOb
Does this mean that all values in a .provxml overule values in a .rgu?
GSLEON3 said:
It's Persistent Registry. Any boot, or system level function & the value will revert to the that ascribed by the xml. So, for example AT&T limits it to one connection at any given time to save B/W. If you edited it with a registry explorer & then played around changing things or reboot, the value they set in the xml will return.
I'm a special Noobie, I mean don't you know how I am? I'm unique! I don't need to read, duh!
Noobie Flaming Mode is more like it
Click to expand...
Click to collapse
Gzzzz... gzzzz.. well... I cooked ROM with the new values meanwhile LoL
Goodnight, talk to you tomorrow.
yes on every reboot or cold start the default.hv and the boot.hv are rebuilt from scatch hence why back in the hermes days turning clear type on in land scape never stuck after a reboot Its always better to change the .rovxml or .xml files and or cook the settings you like into the rom by editing the .hv files while cooking using regucomp
Well... I don't sleep yet, thank you!
I learned a lot of new things tonight
austinsnyc said:
yes on every reboot or cold start the default.hv and the boot.hv are rebuilt from scatch hence why back in the hermes days turning clear type on in land scape never stuck after a reboot Its always better to change the .rovxml or .xml files and or cook the settings you like into the rom by editing the .hv files while cooking using regucomp
Click to expand...
Click to collapse
GSLEON3 said:
It's Persistent Registry. Any boot, or system level function & the value will revert to the that ascribed by the xml.
Click to expand...
Click to collapse
So it reverts only on boot, or calling functions into the kernel too? Seems overly paranoid for it to do that for system functions.
Well, if it's only on boot, I can build an extension to KaiserSimFix that'll restore previous settings. Read a user-defined XML or something to "restore". Or KaiserTweak can do this too if can be set to run after boot, for those running the vanilla ROMs.
Very Nice!
It seems that' akadonny's DK rom (at least the latest 3.14) has the value already changed to 5.
PM
isant there anyway to make the registry edit stick without it being cooked in the rom?
ChInEsE ChIcKeN said:
isant there anyway to make the registry edit stick without it being cooked in the rom?
Click to expand...
Click to collapse
Don't think so. The provisiong xml's are all rom protected. You may be able to create a new provisioning xml & use something like SK Tools to import it, but I've never tried it & don't know if the imported overwrite would stick. Give it a try.
Great, been try to find the root course of this issue even since using BBC. now is the question of lean to cook rom or wait someone's rom has this hack built in... I wounder.
can we confirm any rom was using this hack please.
Confirm what? Cooked ROMs? I know of these for certain (cooked Roms):
1. Sleuth v1.2 WM6.0
2. Sleuth v3.0 WM6.1
3. Dutty Hybrid WM6.1[April 1]
4. Dutty Hybrid WM6.1 [April 9]
5. akadonny's DK rom 3.14
Possibly others, but these are the ones I know of. I also believe L26 will have this shortly if not already. As for cooking it in, it's quite easy. Just search for making provisioning XML's, there are a few good tutorials around & replace the existing. To do this use the Imgfs tools, extract & dump rom, then rebuild the os.nb.
GSLEON3 said:
Confirm what? Cooked ROMs? I know of these for certain (cooked Roms):
1. Sleuth v1.2 WM6.0
2. Sleuth v3.0 WM6.1
3. Dutty Hybrid WM6.1[April 1]
4. Dutty Hybrid WM6.1 [April 9]
5. akadonny's DK rom 3.14
Possibly others, but these are the ones I know of. I also believe L26 will have this shortly if not already. As for cooking it in, it's quite easy. Just search for making provisioning XML's, there are a few good tutorials around & replace the existing. To do this use the Imgfs tools, extract & dump rom, then rebuild the os.nb.
Click to expand...
Click to collapse
Maybe it just me then. I was on
Dutty Hybrid WM6.1[April 1] and can't get t-mobile Internet working together with BBC connection at the same time.
So I just flash the Dutty Hybrid WM6.1 [April 9], all default condition. using the built in network config to set to t-mobile uk gprs setting, using reg edit to change the add on version to 0.4.2 as suggested in wiki and install BBC 4.0.0.97. everything works fine(bbc can get ping, and connected etc) but just can't get both connection on. as before. once BBC connected, if you try to using IE and start t-mobile internet connection, it kick BBC off. btw my radio version is 1.58.16.27 if that would make any difference....
With all the rom I been tried so far, it almost like to me the xml change does not effect my issue here. Any Suggestion GSLEON3?
Don't know what to tell you. I dug thru the rom's specifically to find a solution to this issue for Dutty's rom. I use BBC & wanted both MediaNet & BBC working on Dutty, Dutty's ROM was the whole reason I even looked into the issue. I beta'd both of those roms for Dutty & both worked for me. I currently am using a moddified IMGFS version of the April 1 Hybrid to post this via MediaNet & I'm still connected to BBC.
ok so call me stupid but how do i get two data sessions working at the same time? i want to use media net for push email but i want to use MyIsp for internet how do i do that?
i am posting here because this kinda seems relevant to my question:
when on edge in att network internet is automatically suspended when a call is answered and stays suspended for the entire duration of the call. connection stays activ in 3g and hsdpa.
Is there any want to keep connection active while on edge or this can't be done due to limitations of edge?
thanks in advance
Hi,
i am searching for the "Work URL Exceptions" in the Windows Mobile 5 registry, but i cant find.
Anyone a idea where i can find it ? I need it for provisoning!
Or has anyone another idea for provioning the "Work URL Exceptions" ?
Thanks.
Ok, it takes a while but i found something.
Code:
<wap-provisioningdoc>
<characteristic type="CM_Mappings">
<characteristic type="16777216">
<parm name="Pattern" value="*://192.168.10.15"/>
<parm name="Network" value="{A1182988-0D73-439E-87AD-2A5B369F808B}"/>
</characteristic>
</characteristic>
<wap-provisioningdoc>
This code SnipIt adds the IP 192.168.10.15 to the url exceptions list.
These exceptions should be numbered from 16777216 to 16842751.
Link:
http://msdn.microsoft.com/library/d.../html/wce51howConnectionManagerURLMapping.asp
Not sure if there was a specific reason you were looking for it in the registry, for a program your writing?
I have 6.1 on my phone, so I'm not sure the location is gonna be the same. But on 6.1 you go to the following;
Start > Settings
Select Connections tab
Select Connections icon
Select Advanced tab
Select Exceptions button
After I did that, I was able to do a search for what I added to find the location in the registry.
I need it for provisioning, i have to configure 30 PDAs, and i dont wont to do it manually.
I had the same idea, add a exception and search in the registry....but i dont find anything i add. Anyway now it works.
HTC Touch Diamond
WM 6.1
German Vodafone ROM
bye
Hi, can you explain how you apply this xml provisioning file ?
I have to configure 600 PDA and i'd like to use a SD Card to update configuration in a single operation (using the autorun mecanism of SDCards)
smotrs said:
Not sure if there was a specific reason you were looking for it in the registry, for a program your writing?
I have 6.1 on my phone, so I'm not sure the location is gonna be the same. But on 6.1 you go to the following;
Start > Settings
Select Connections tab
Select Connections icon
Select Advanced tab
Select Exceptions button
After I did that, I was able to do a search for what I added to find the location in the registry.
Click to expand...
Click to collapse
Hi,
What was the registry location for the work url exceptions? I tried the same steps then did a registry search but that didn't find the entry I created.
Thanks for your help.
HTC Touch Diamond
Windows Mobile 6.1