Database Info

Restore Internet Calling in Faria's WM6 ROM?

I have been attempting to add Interenet Calling to Faria's WM6 ROM by adding the necessary files and registry changes and re-cooking the ROM but I am getting nowhere fast. I have managed to add some files to the original ROM, make a couple of registry changes fine and change some settings in the initflashfiles.dat file to remove some shortcuts I don't want and I can get this to work fine, however re-adding the IP Phone stuff is a bit more of a task.......
I have extracted the files (or modules) from the MB ROM and added the regsistry changes and the ROM cooks just fine. When I flash the Wizard though it completes sucessfully and then reboots. I get the 1st splash screen but then when the 2nd splashscreen should appear I get a white screen. The Wizard is working as I can hear the bleep when it asks you to 'tap the screen to set up the device'. It also powers on and off OK, but I only ever get this white screen.
I have tried this about 4 times now and I am convinced the registry changes and required files are correct, but each time I get this white screen. Any ideas?
Andy

http://forum.xda-developers.com/showthread.php?t=290786
Read this... especially towards the end.

trojan9x said:
http://forum.xda-developers.com/showthread.php?t=290786
Read this... especially towards the end.
Click to expand...
Click to collapse
Already read it..... I can get Internet Calling back if I launch the VoIP.CAB that is included in that thread after installation, however I want these to be integrated into the ROM like they were originally (Faria has removed them). As I said I have had some sucess with adding other files and other registry changes it is just this bit that I am stuck on.
I did manage to get a bit further but ended up with a corrupt Today screen, no idea what happened there though
Andy

What are you stuck on?... you said you didn't have it, but now you said you can get internet calling... what exactly are you trying to do?

Faria has said that his rom takes up almost the entire space alotted. Have you tried removing some files from the rom to clear up room for the VoIP files?

trojan9x said:
What are you stuck on?... you said you didn't have it, but now you said you can get internet calling... what exactly are you trying to do?
Click to expand...
Click to collapse
I want to restore the Internet Calling option in Faria's WM6 ROM - pretty simple to understand really
I can add it manually via the VoIP.cab file but this obviously takes up RAM and can be removed via 'Remove Programs'. I would like to add the files that are missing and make the necessary registry changes then re-cook the ROM. I would prefer to keep Faria's base ROM.
I haven't tried removing anything from Faria's ROM so far, I didn't realise it was near the limit - I thought we had 128MB to play with on the Wizard, are we near that already?
Andy

Listen.. that cab only does registry fixes and puts in the NECESSARY files for the current voip functionality. it does not install anything that is not needed. Extract the cab and look at the xml file. it will tell you exactly what it does...Pretty simple concept

trojan9x said:
Listen.. that cab only does registry fixes and puts in the NECESSARY files for the current voip functionality. it does not install anything that is not needed. Extract the cab and look at the xml file. it will tell you exactly what it does...Pretty simple concept
Click to expand...
Click to collapse
Yep, already done that, hence my original post.....
I have added the necessary registry changes/additions and proof-read them several times, however once the ROM is cooked and installed the thing reboots, I get the 1st splash screen OK, then the white screen when the 2nd splash screen should appear and that's it.
I will have a look at how bloated the DUMP directory is with the additional files in there and see if I am going over 128MB.
Andy

The DUMP folder is apparently 122MB (128,512,401 Bytes) but is taking up 132MB (139,141,120) on the disk on my PC. Does anyone know if this is too big? If it is what is safe to remove?
Thanks
Andy

Done it.......
If anyone is interested I managed to get Internet Calling back into Faria's ROM.....
What I did originally was correct, however the file (or modules) that are needed for Internet Calling total about 3.5MB, which I think was slightly too much and would make the ROM bigger than 128MB (I think Faria must have realised this when developing his ROM and removed them to save space). I have been through the installed applications and files and have removed some stuff that I don't use. I then re-built the ROM and low and behold it worked first time and Internet Calling is now an option...
It still doesn't work however but that is just because it needs a provisioning XML file from a provider. Hopefully when WM6 devices appear we will be able to extract a provisioning XML file and dig deeper........
And no, the ROM is not available since this is Faria's work and not mine.
Andy

Nice,
I’m new to this and the only thing that I need from WM6 is the “Internet Calling”
I have no ides how to make the voip work. But I fond this at Microsoft.
http://msdn2.microsoft.com/en-us/library/ms898226.aspx
I really would like to test this with my “asterisk server” (http://www.asterisk.org/)
/joad

Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6

joad said:
Nice,
I’m new to this and the only thing that I need from WM6 is the “Internet Calling”
I have no ides how to make the voip work. But I fond this at Microsoft.
http://msdn2.microsoft.com/en-us/library/ms898226.aspx
I really would like to test this with my “asterisk server” (http://www.asterisk.org/)
/joad
Click to expand...
Click to collapse
I have exactly the same intentions, joad. I've got wm6 on my O2 XDA mini so I can try and connect to my Asterisk server as well!
Let's hope his eventually works.
N

joad said:
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
Click to expand...
Click to collapse
You need to add the following files into the ROM (the 1st 3 are actually modules and are in directories with the same name):
dnsapi.dll
rtcdll.dll
voipphonecanvas.dll
ipdialplan.xml
ringback.wma
You also need to add the registry entries to the default.hv and user.hv that are contained in the '_setup.xml' file from the VoIP.CAB file (or extract them from another ROM that already contains Internet Calling).
HTH
Andy

joad said:
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
Click to expand...
Click to collapse
Joad,
I agree with you. The 3.5 Mb footprint is inflated.
It's only 1.75 MB (remember if you are using recmod when you are unpacking the ROM with viewimgfs, you have two copies of the files that are stored as modules: the module version and a file copy!.
--eluth.

eluth, I knew that somebody out there would have done the right job. Congratulation! Would you mind making your rom available to us?
Thank you
Gio2003

Pleaaaaaaaaaaaaase !!!!!!
There are so many people wanting to do this now - and I have a MAJOR need for this on a Hermes -- I have a solid SIP provider and can get to it with my other apps but integration I can't test ---
I am trying soooo hard to pin this down. I have not found a single ROM yet that has the "complete" add-in of what you mention here.
It would be GREATLY APPRECIATED.
Thanks
gio2003 said:
eluth, I knew that somebody out there would have done the right job. Congratulation! Would you mind making your rom available to us?
Thank you
Gio2003
Click to expand...
Click to collapse

ckolibab said:
There are so many people wanting to do this now - and I have a MAJOR need for this on a Hermes -- I have a solid SIP provider and can get to it with my other apps but integration I can't test ---
I am trying soooo hard to pin this down. I have not found a single ROM yet that has the "complete" add-in of what you mention here.
It would be GREATLY APPRECIATED.
Thanks
Click to expand...
Click to collapse
This .CAB worked on my Wizard with Faria's WM6 real thing ROM that had the VoIP stuff removed:
http://forum.xda-developers.com/showpost.php?p=1147821&postcount=138
I then added the files and registry settings back and re-cooked the ROM.
HTH
Andy

WM6 Windows Update - files & settings required?

Now I know Windows Update on WM6 doesn't work for the Wizard - It connects to the m$ update site but doesn't find any updates. I tested this previously with the MB ROM and used a sniffer to see what was going on and it does indeed connect to the windows update site using HTTP.
In Faria's WM6 ROM he has removed Windows Update by physically removing some files from the ROM and deleting some registry settings as well as commenting out a line in the 'initflashfiles.dat' file. I have attempted to re-add Windows Update to his ROM with some sucess, however I am not quite there yet....
I have restored 'autoupdate.exe' and 'AutoUpdateRes_wpc.exe.0409.mui' as well as a registry setting [HKLM\System\Autoupdate] and it's settings and uncommented the line in the 'initflashfiles.dat' file to add the shortcut back. Now Windows Update is available and when I open it it opens OK but fails to connect when I select update now. It then sort of hangs and can only be closed using Task Manager or similar.
Are there any other files or settings that need restoring to get this back. I understand it doesn't work but my curiosity is getting the better of me
Thanks
Andy

I thought I read (maybe here) that when someone did the update, they actually had a theme file that was available and it downloaded that.

No packets sent?
I have been playing around with the Windows Update application and it starts fine. If I select 'Check Now' it immediately comes back with the Error screen telling me 'connection to update server was not available....'. If I click OK and then attempt to end the application it just stays on the screen and the only way to stop it is to use Task Manager and terminate the process
I have also put a sniffer on the port my Wireless AP connects to and cannot see the Wizard transmit anything when I click select 'Update Now' (I have verified I can access the internet with IE and I can see this OK with the sniffer).
Does anyone know what I am missing to at least get the Autoupdate.exe application to attempt to connect as it did with the MB ROM?
Thanks
Andy

Anyone
Can I bump this up as I want to get this working and re-added to my ROM (I know it doesn't actually work but I would like the functionality restored anyway).
I have restored the files:
autoupdate.lnk
autoupdate.exe
AutoUpdateRes_wpc.exe.0409.mui
Added the registry settings:
[HKEY_LOCAL_MACHINE\System\Autoupdate]
"DetectionCookie"="0"
"IntervalEndTime"=dword:f0
"IntervalStartTime"=dword:3c
"OmaDmSessionTimeout"=dword:258
"NextRunNormalInterval"=dword:93a80
"Automatic"=dword:0
"OTA"=dword:0
And restored the line to the initflashfiles.dat:
Directory("\Windows\Start Menu\Programs"):-File("Windows Update.lnk","\Windows\autoupdate.lnk")
There must be something else I am missing as it never attempts to connect and hangs when trying to exit the application. I restored the files from the MB ROM to Faria's ROM as he didn't include the originals.
Thanks
Andy

I would very cautious about re-adding windows update to a beta evaluation ROM (all our WM6 roms are!!!!).
It will do no good, only harm, I think, since Windows Update as well as a few other components in these beta WM6 are actually there only to call home and manage the beta evaluation.
My position of this is that you want to remove as much as possible all these pieces of software, essentially to avoid the call-home feature and the ROM expiration process, without breaking the ROM, of course.
So, I recomment to leave Windows Update out, SQM and other modules, ceipui, the remote provisioning mechanisms, etc. I've already talked about this in diffent threads, but I'll try to post a summary of my findings in the short future.
Regards,
--eluth.

I understand and accept the implications but I would prefer it if this was restored to my ROM.
I am just after some help as to what I am missing to restore this functionality
I have listed what files and settings I have restored but AutoUpdate is obviously missing something based on it's behaviour.
Anyone?

Anyone?
Anyone know what I am missing? Surely some of the cookers on here who have removed the Windows Update from their ROMs know what they removed?
That's all I am after; not too big a task I assume?
Andy

ADB100,
I could not tell you what is missing, but I do know that it is enabled in mUn's ROM. Because I did the same as you. Hooked it up to a sniffer and looked at the packet exchange between my Wizard and the MS update site..
Regards

Projectile said:
ADB100,
I could not tell you what is missing, but I do know that it is enabled in mUn's ROM. Because I did the same as you. Hooked it up to a sniffer and looked at the packet exchange between my Wizard and the MS update site..
Regards
Click to expand...
Click to collapse
It's enabled in the original Orwells, the MB Edition, mUn's and Faria's Vanilla WM6.
However I still can't find what I am missing to get it back in my re-heat of Faria's latest 'Real Thing'.....
Andy

you are missing SQM .
ps;
there is WM6 ROM for a windows ppc that has time bomb....plus microsoft can expire your rom by update if they want.... the update feature uses .pkg and this settings will stay after hard reset.... so they can use it for any means,and so can anyone that can compile 1 of those packages. just to let you know.

faria said:
you are missing SQM .
ps;
there is WM6 ROM for a windows ppc that has time bomb....plus microsoft can expire your rom by update if they want.... the update feature uses .pkg and this settings will stay after hard reset.... so they can use it for any means,and so can anyone that can compile 1 of those packages. just to let you know.
Click to expand...
Click to collapse
All the SQM files are present and the SQM settings in the registry are identical
What else could be missing?

Also, Which rom as the timebomb and how do we find it?

hi, anibody have this files:
autoupdate.exe' and 'AutoUpdateRes_wpc.exe.0409.mui'?
Thanks

I don't have it handy, but go find the original Ingenetics dump that was posted here (do a search) and I know it has those files in it.

Andy,
The original dump by Ingenetics was pulled a few days after he posted it. But I think this link has it. Good luck on your quest.
http://rapidshare.com/users/T4RZX2

Yikes!!!

Okay,
I have had my wizard for about a year now and in that time have flashed countless ROMs without any major problems, but yesterday I came as close as I ever have to bricking my device, and the crazy thing is that I have no idea why. I am hoping that the "real men of genius" here can help me figure out what the freak happened, or specifically what I probably did wrong
Before anyone asks, yes my phone is SIM and CID unlocked and it is a G3.
I recently moved from Core 2.0n to mfrazzz XDA Mobile 6. I really liked it but with mattr_k's easy kitchen and stripped down base I figured I could play with it a little to get some more of the apps and settings I like in it from the get go, and save the space without the ones I don't. I had been playing around with the core kitchen and the first kitchen mattk_r upped so I had a pretty good idea of what to do.
here is what happened as best as I can remember ( I should have taken notes as it was happening but I was too freaked out!)
I created the OEM directory and copied the reg tweaks and packages that I wanted from Pandora's Box (v2). I ran Build OS and selected all and it completed without problem. I ran createROM.bat and no problems there. I went into flashing, built the nbf and flashed. The flash went fine with no hang ups.
When the device restarted after flashing it went to the first splash screen and then stayed white. I left it this way for 10 minutes and then it was still like this I tried a soft reset. It reset fine but stayed white. I then tried flashing back to the original mfrazzz ROM but when it got to 95% the flash tool errored out and closed. The phone was stuck with the progress bar at 95%.
I freaked out a little and then rembered that I still had a copy of wizard love on this computer so I put it in bootloader mode and then flashed that. That got the phone back up. I then tried reflashing my "cooked" ROM. It loaded this time, but the today screen was a white background and some of the today plugins were extremely distorted and it just wasn't right.
I reflashed wizard love, and then reflashed the mfrazzz's original XDA Mobile. My phone is now fine.
Any ideas on what the heck happened.

Just guessing here....did you messed with the splash screens ?

anichillus said:
Just guessing here....did you messed with the splash screens ?
Click to expand...
Click to collapse
Not on purpose, followed the steps above as far as I can recall.

You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking

When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
If you only did the OS, what is the size of your nk.nbf? If its too big it wouldn't have flashed.
BTW: Welcome to the world of rom cooking... I've scared myself a few times

ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!

When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
mattk_r said:
ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!
Click to expand...
Click to collapse
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!

boto said:
You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking
Click to expand...
Click to collapse
well it would definitely be a tragicomedy!! or perhaps a nail biting thriller! I wanted to give as much detail as possible since I hate it when someone posts, "I bricked my device, what happened?!?!?! PLEASE HELP!!!!"

dcdivenut said:
When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!
Click to expand...
Click to collapse
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.

mattk_r said:
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.
Click to expand...
Click to collapse
I don't think I entered WWE for language, but I did everything else, and didn't do anything extra. That is something to try...

UPDATE!!
I am not sure that something as simple as typing WWE in the language field is what made the difference but I did and it worked. On my home computer I redownloaded the kitchen, base and OEM packages.
I first flashed it with nothing added to the OEM folder and it worked
Then I added to the OEM folder and that worked.
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Any help from the pros in getting this up woudl be awesome! Hopefully others will be able to use them as well.

dcdivenut said:
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Click to expand...
Click to collapse
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .

mfrazzz said:
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .
Click to expand...
Click to collapse
SWEET!
Soft key - Check
Time Sync - Check
I found this in the .rgu file in the x-mfrazzz apps. is this for the softkey app or something else?
[HKEY_LOCAL_MACHINE\Services\Stk_service]
"Dll"="\\windows\\STK_Service.dll"
"Description"="STK Service"
"DisplayName"="STK Service"
"Context"=dword:00000001
"Keep"=dword:00000001
"Order"=dword:00000005
"Index"=dword:00000005
Windows Live search - In your OEM folder there are two folders, WindowsLive and WindowsLive_DPI_96. These are both currently also in the SYS folder of mattr_k's base so wouldn't this throw an error? I know I am missing something stupid here.
Ring tones - Is there anyway I can build mp3's into the ROM? I tried placing them in the x-mfrazzz settings folder in my SYS but that didn't work, even though they get built into the windows directory. I looked in the .rgu and there doesn;t seem to be anything about where to place these
PHMReg Edit - I thought I remembered you saying something about being able to export reg settings in the correct format. I was playing around with this and the closest thing I could find was backup. That created a .rbk file but I get gibberish in notepad when I try to open it. My thought process here was to use get all the reg setting the way I want, export them, get them into a .rgu file and then build them in. Any ideas?
How do I get it so that ini_tray.lnk is not automatically in startup?.

Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?

dcdivenut said:
Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?
Click to expand...
Click to collapse
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)

mfrazzz said:
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)
Click to expand...
Click to collapse
Cool, will check when I get home, any thought on post above?

Hmmmmmm...
Seems to me your mind was on your woman and not your Wizard... just a thought,ehehe!
Congrats bro!

My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...

Madcap180 said:
My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...
Click to expand...
Click to collapse
dc just got engaged.....

Congrats DC ... if you ever need someone to pick the lock on that ball and chain, let me know...j/k

(from O2 XDA Zinc) wireless today plugin that shows data status

I came across, on another forum, a today plugin pic.
The poster in fact, was posting the cabs for activating VoIP on Wm6 roms.
Cabs mostly from Xda.
But what impressed me the most, was a capture of his today screen.
He has the regular 'wireless' plugin showing the status and name of the three typical connexions: GSM, Bluetooth and Wifi.
But his plugin was showing also the status of his DATA connexion.
(I guess GPRS, EDGE, HSPDA etc.)
Any one knows where I could find the cab or the registry tweak to add this feature to the basic wireless plugin?
OK I finally got more informations, it's part of a today plugin and commanager from O2 XDA Zinc.
Any one who have access to this phone could help providing the following?
- Which registry values are present on that phone in this area:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Today\Items\"Wireless"]
- has any one got the installation cab of that plugin?
It would be great to see the _setup.xml file, maybe the tweak is there
- any one can send me the "netui.dll" in the windows directory of that phone, so I can try to run it see if that helps showing the 'data connexion status'?
Cheers

Well, 64 viewers and still no one knows about it?
1) has any one seen this wireless today plugin before?
2) has any one used it before?
3) does any one know about a registry tweak, a cab or a dll that displays this additional data connexion status?

I have it on my TyTN...sorta.
It looks just like yours with the WiFi and Blutooth, but not the Data part of it.
The registry tweak is documented in the Wiki. That's where I found it

You did not get my point
Thanks for the reply, I thought every one got scared away by the question...
Yes, I already know the registry tweaks and I also got the cab for what I called the regular/typical wireless plugin (operator name, wifi status, bluetooth status).
My point is: how about the DATA status (gprs, edge, 3G)?
Does any one know how to add this fourth information into the wireless plugin?

I updated the first post and the title with new informations
Its all about the O2 XDA Zinc phone
Could some one be kind enough to provide the following informations:
- Which registry values are present on that phone in this area:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Today\Items\ "Wireless"]
- has any one got the installation cab of that plugin?
It would be great to see the _setup.xml file, maybe the tweak is there
- any one can send me the "netui.dll" in the windows directory of that phone, so I can try to run it see if that helps showing the 'data connexion status'?
Cheers

This is actually a very intersting find. Data indicator is what always turned me away from that plugin. It'd be very interesting to find out more, unfortunatley a lot of Googeling got me nowhere and without the device in possession I feel like I have not much more to offer.
Anyone else?
//Nik

Yeah, I made some more findings, thanks to the guy the screen-shot came from...
The registry keys seem to be quite similiar EXCEPT the fact that this wireless plugin doesn't use netui.dll, it uses a dll called: WirelessManagerToday.dll
I put that dll onto my system and tried to get i working but it didn't.
It did not give me any error, but it just displayed nothing...
So what we need now, it's an installation cab of the O2 Xda Zinc Wireless Manager or something like that, to see if there is another file involved in this process (an .exe file or whatever)
And to know if there are other settings apart that registry link to that particular dll.
Any one using O2 phone can answer?

hi there fancy meeting u here
the thing is o2 zinc comm manager is different from HTC one ... as the attachment below. Also a shot of the dll ... the string value of the dll show a Wireless Manager. Zip file contains the WManager.exe & also the dll
Hope this help

Hi mate.
The world is not that wide, when we use the same nick everywhere!
;-)
I tried to send you a mail with some useful stuffs to unlock your extendedrom, but every mail failed, maybe a problem of anti-spam filter.
I post here below the applications from this site and others. Give it a try...

cheers mate
well i ll try this one ... sad to hear that u cant use the plugin yet ... keep trying mate
BTW o2 zinc is made by Asus ... not sure if a htc unlocker can unlock the ext rom ...

Hope you can unlock your extended ROM and find some useful cab related to the Wireless Manager install.
I don't like to give up, but the fact is I don't know toward which direction make the next move...
When you have time, would you make some automatic search in your registry to make sure there is no other references to those dll and exe or maybe some other components of the whole wireless system. Thanks.
Yeah, I know the manufacturer is different, but It's still the same Windows Mobile system, there might be some bridges between them.
Cheers

i only have the update rom frm o2 only now ... i cant extract the exe file ... it only show error ... maybe you can teach me how to do a rom dump maybe than it can be some help to you

i have tried compiling a cab file with both dll & the registry using wince cab manager ... hope it can work
:fingercross:

This ROM problem is driving me mad!!!

Okay. I have exhausted all possibilities that I can think of for this problem. The last few ROM's I've ported have been fine, except for one thing. After flashing (or hard reset) the ROM displays the splash screen and then goes to the welcome screen (displays welcomehead.96). However, when the LogoMsg.bmp popups up (the text that says, "The device is clearing the storage. Please wait.) it only displays for a few seconds then leaves. A few seconds later the tone that accompanies the "Tap screen to begin setting up your device" sounds. The words, "Tap screen..." do not show. However, a second or two later the tone sounds again, this time followed by the text, "Tap screen to begin...". From here everything in the ROM works fine. I just cannot figure that part out.
The LogoMsg.bmp is located in OEMDrivers, so I thought I might have accidentally removed something from the OEM folder. However, I have not found anything seemingly related. Also, I thought it might have been related to welcome.exe. Though, I've tried replacing it with an older version; still no luck. Unfortunately, I have tried so many things that I cannot remember exactly what all I have tried. I've re-ported XIP's (using Ervius' kitchen and by hand) and SYS's, as well as taking a fresh copy of my base OEM.
Essentially, I am asking if anyone has come across anything like this in your cooking, and if you have any tips. I would be more than happy to upload a copy of my ROM for you to test or upload my kitchen folders. I appreciate any help that anyone can provide.
EDIT: I'll try and upload a video later to show exactly what is happening.

Hi KMFM$
I use an official rom iolite ita for porting the xip e Sys to my kaiser. After cooking i have the same problem that you describe.
After 2 mounth there is some solution... i'm crazy for this problem
Bye
Daniele

i have the same issue when flashing any of the wm 6.5 ROM's. not sure what kitchen the chefs use but it doesnt seem to effect anything.

Well, I have yet to find a "solution" to this. However, I have just simply learn to deal with it. It does not effect the ROM in any noticeable way, and from what I've heard from other chef's, this is common in all new ROMs. Not sure what is going on in the ROM during that time frame, but again, it does not effect the standard operation of the ROM.

well dont sweat it then. yeah, i think its normal for 6.5

yep been a normal thing for all my 6.5's

hi KMFM$
the ROM is 6.1 or 6.5?

When it comes to porting it depends on build ver. ect ect. Its a big try and fail operation for moust of us when thing doesnt work as planned. But to get a true port you have to use m'relloc and manual change values in the modules, there is alot of guides on how to.
On dump of nbh in kitchen it unpacks diffrently (provider to provider or if its a "pure" HTC nbh), anyway the cue is that some of the chef`s use xip files in the ROM folder while other make mxipkernel + mxipkernelLTK in SYS and oemxipkernel in OEM then os.nb+ a folder named XIP in ROM and THAT contains boot.rgu I use the last method which for some reason works best for me.

- shifu - said:
hi KMFM$
the ROM is 6.1 or 6.5?
Click to expand...
Click to collapse
Both, actually. WM6.1 builds from about CE OS 5.2.20757+, I believe, have all given the "extra" notifier. Again, I'm over it. I've just accepted the extra tone and moved on. No big deal.