yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] pcarvalho:
i have a small issue with 29017,

since i have to apply the caller id fix (old device)

my alarms dont ring, device is asleep and alarm only rings when i wake the device up, is it just me or am i missing some fix...i already almost missed work :)

thanks and cheers
[Windows Mobile] sharkie405:
Just you, unfortunately... I use the caller id fix with 29017 and my alarms work fine. I haven't heard of any official alarm fix that is needed. You have tried with different builds and still have the alarm issue?
[Windows Mobile] pcarvalho:
it seems to be kind of random...today alarms worked...cant pinpoint where issue is...thanks anyway

cheers
[Windows Mobile] derliebewolf:
Could it be that your device was set to "Mute" so the alarm went off, but you simply could not hear anything?
[Windows Mobile] pcarvalho:
It is set on mute but alarm is set to play anyway. always worked. so it isn't that. cheers
[Windows Mobile] derliebewolf:
those settings are working just fine with me...
[Windows Mobile] prabhat:
Latest WinMo 6.1 Standard Build That I can use for T-Mob Shadow

Hello,

I know this question is very late to ask here and WinMo 6.1 is dead now... But I got one T-Mob Shadow for my family member.

I got a T-Mobile Shadow and that comes with WinMo 6.0 Standard [CE 5.2.1711 (Build 18170.0.5.1)].

So I was thinking If I can cook a Latest available 6.1 Standard Build for the device:confused: and a Kitchen where I can cook as well?

BTW: I use osKitchen, and the kitchen does not support the device :(.

I know I can use some of the already cooked ROM Like-1 or Like-2, but thinking to have the ROM clean and as close as the stock one :).

So expecting some chef will have the 6.1 Build that I can use and some kitchen that will support the device as well... Looking forward for any pointers?

Thanks.
[Windows Mobile] _Madmatt:
Why not use a 6.5 Standard build? I think there is more chance to find a build like that. Only thing you need then, is a native kernel (nk.exe) adapted for your device.

Good luck!
[Windows Mobile] prabhat:
Yes, this sounds good. May be some one can help me to get these :confused:

Thanks for your input friend.
[Windows Mobile] _Madmatt:
I'll take a look if there's a nk.exe available ;)
[Windows Mobile] Spiaatie:
There is no need for WM6.5 native kernel. He can use the same one that device already have, he will just need to recmod some modules in SYS folder.

You can get WM6.5 Standard build 23137 from [here]
[Windows Mobile] _Madmatt:
Yeah, but I've experienced a much smoother build with a native kernel instead of a 6.1 one on a Touch Pro/Fuze.

However, without is possible and osKitchen will tell you what modules to recMod normally ;)

Happy cooking!
[Windows Mobile] prabhat:
Thanks please do let me know... Also I read you next post abt kitchen...

Thanks friend... I will download the SYS and try to do a quick build with the existing nk. NOt sure if my osKitchen will support this or not... what device I should select as Shadow does not appear in list :( for osKitchen...

Yes _Madmatt, osKitchen does tell those and I am downloading the build as well... but as the osKitchen does have Shadow as device list so what device I should select? :confused:

Any other suggestion for kitchen here?

Thanks.
[Windows Mobile] _Madmatt:
Have you tried with just leaving the Device Model field blank? :)
[Windows Mobile] prabhat:
When I left the name blank or just entered as "Shadow" it asked the device name is not in the supported list do you wish to continue? When YES -> It imported the Base ROM and gave below message:

The device profile currently selected uses a pre-6.5 kernel, therefore the module allocation space will be extremely limited.

Do you want to automatically enable "Module to File" conversion for a list of recommended windows mobile packages?

I hit Yes to proceed.. and looks like several issues.. and resolved almost all... Dont know if this will work :confused:
[Windows Mobile] _Madmatt:
Normally it should work ;) Build the ROM and flash it to try it out :) If the kitchen doesn't crash while building, good luck :)
[Windows Mobile] prabhat:
I was about to post .... The kitchen crashed during build :( with below error:

Platformbuilder has crashed,probably due to some unsupported module.

Please try changing your package selection and try again.

Thanks.
[Windows Mobile] _Madmatt:
You should try to find out what module is crashing the kitchen, and then RecMod it ;) Disable them one by one and build. If it doesn't crash with that module disabled, you re-enable it and RecMod it.

Good luck!
[Windows Mobile] jean-flavien:
Where can i find it in French( the build 29007) for HTC Touch Pro 2 ( WVGA)
[Windows Mobile] Nixeus:
Hello my french friend ,

The latest FRECNH packages are in the 23563 build ! I don't have the link, but search it on the forum.
[Windows Mobile] jean-flavien:
Thanks but i already have this version, it is a beta and i prefer the 29007.
[Windows Mobile] Nixeus:
There is NO 29007 French language.

Use just the MUI file from 23563 ! An MUI file contain just TEXT, so, there is no bug in !
[Windows Mobile] Farmer Ted:
All the builds are beta. If you're worried about the watermark, just search your registry for "Beta", and you'll see the key to edit to fix this. Or, search the forum-this has been addressed a million times, and is easy to find or fix on your own. I'd tell you the answer, but would prefer that you find it yourself.

Patching timebombs is also very easy. I'm not sure if 23653 had the timebomb, but most kitchens will do it, and there are tools to patch the timebomb. Just search for them. If you need the French lang files, and the only place to get them is 23653 (as posted above), then just get them from there.
[Windows Mobile] mureta:
One help please !

Hello guys,

I downloaded the latest build 29017 DFT but when I trigger a video camera to always keeps crashing. How can I fix this? Use of the kitchen and cook for vistang the Omnia i900.

I am a beginner cook and all help will be of good size.

mureta.
[Windows Mobile] ai6908:
SYS file probably does not cause it to crash, it might be something in ext pkgs that is not compatible or missing...
[Windows Mobile] Farmer Ted:
I suspect you're missing a dependency. Do you have the full oem/ext from the stock rom cooked in? You may be missing one of the HTC dependency packages, or possibly an oem driver or something like that.
[Windows Mobile] mureta:
@ai6908 and @Farmer Ted

Sorry for the delay and I appreciate the quick response and consideration.

I think I've been cleaning my other and my XipKernel SYS.

I'll pay more attention now and hope to report something positive.

GOD that pays double your support.

mureta.
[Windows Mobile] BoomerCE:
Hi friends,

29018 is up on DFT, go download it :)
[Windows Mobile] AndrewSh:
BoomerCE, thanx buddy! The **** is that the whole world is downloading now :) Freaking slow :( I was not even able to leave the post at DFT - so writing it here - thnx again :)
[Windows Mobile] Z80-Man:
It may be true for the kernel, I don't know... But definitely not for a lot of programs. Some executables only work in WWE and ignore any MUI files you would provide. Of course, it may be HTC or other third party software. I'm not sure about pure Microsoft Windows Mobile ones.

That said, I think I should try to find and save that 23569 package... That WM6.5.5 build was actually wonderful. :cool:
[Windows Mobile] AndrewSh:
29018_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT

Windows CE: 5.2 Build 6212 (Mar 13 2011. 15:48:25)

Thanx to BoomerCE (DFT) for sharing, thanx to rewwps (asusmobile.ru) for reuploading
[Windows Mobile] Z80-Man:
Yeah, I was looking for it, too ! :D

I need the original shell files to add transparency... ;)

I'm amazed most people posting for problems in this topic actually report very ROM-specific issues, absolutely not related to XIP kernel builds. :eek:

Sense related problems are absolutely disconnected from Windows Mobile... So are third party utilities.

Come on, guys, this topic is just turning into a damn jungle... :rolleyes:

Please ask the cooks who made your ROMs on the appropriate topics, when you've got ROM-related problems...

Edit : Thanks for the 2018 ! :)
[Windows Mobile] jmart518:
Thanks BoomerCE for sharing and AndrewSh for the mirror!
[Windows Mobile] mwang:
4 more build will coming soon...........:)
[Windows Mobile] Nixeus:
HUmmmm, a new com2 ? Or.....a com9 ? :D
[Windows Mobile] Pumpiron579:
Thanks for sharing....., AndrewSh, mwang & boomer Nice to have these new builds
[Windows Mobile] programatix:
But the video call will crash the "phone", meaning, the system doesn't crash, only that you can't make any call anymore as you can't start the dialer anymore until you soft reset.
[Windows Mobile] bipinsen:
Contact info missing

Hi there guys. New to the cooking arena, so sorry if the answer is plain. I just cooked in build 23676, and most things work fine. The one thing I don't see is when I click on contact details, I don't see anything. Just a blank sheet. Is this a known problem? Any fix for this? Thanks!! :)
[Windows Mobile] raiderfan247365:
no you also need the video telephony EXT package
[Windows Mobile] + Que PPC:
Thanks for the mirrors AndrewSH, BTW i vote for you in the mod talk thread ;)
[Windows Mobile] indagroove:
I don't have that problem on my TP2, but it doesn't support videocall anyway.
[Windows Mobile] programatix:
Have you tried making/receiving video call?

It works fine as long as you don't do video call.
[Windows Mobile] indagroove:
Yes. I just get this error menu, but no lockup or need to soft reset:
[Windows Mobile] programatix:
Yup. If you keep retrying, then it will lockup. Normally 3 times.
[Windows Mobile] Wajk:
thnx for new SYS guys!

i have one problem:

in Phone settings the reject call with sms option is not working. (not openned setting panel, just button selected)

other phone settings opened, like "Call forwarding", etc.

i think exe or dll missing. Anybody know what's need for it? :confused:

thnx
[Windows Mobile] indagroove:
I just tried 7 times and no lock up. But why would I try more than once if it didn't work the first time?
[Windows Mobile] programatix:
Maybe yours is not calling the module. In my case, my phone support Video Call, thus invoking Video Call still show me that screen, which should only be shown when I'm not in 3G coverage. If I retry multiple times, then the phone feature crash. I guess since your phone does not support Video Call, the video call module is never executed, thus you do not experience the crashing problem. As far as I can tell, most Touch Pro users experience this.
[Windows Mobile] fubo73:
I was using 236xx branch, but I have to admit the 231xx feels better.
[Windows Mobile] williyung:
Hi programatix,

My X1 which support video call also doesn't crash/lock up with the huashan dialer/VT though I tried it multiple times. The problem is just the VT can't work as well.
[Windows Mobile] programatix:
Hmm, maybe I'll retry with the latest Huashan test rom.
[Windows Mobile] Ham3r:
I have problem with SYS or.. i have problem with me.

how is possible to skining checkboxes and buttons on COM2 builds? :O

I have that.

it's pure optimized 21908.
[Windows Mobile] BoomerCE:
any chance for HD2 to use native COM3 dialer without replacing DLLs in SYS? :)
[Windows Mobile] rstoyguy:
What I do is overwrite mxipcold_wpc_2.provxml (from the sys), and mxipupdate_TMOUS_100.provxml (from HD2's OEM). Basically blanked them in the following EXT, and then I used oskitchens package converter to take a .tsk file and converted it to an EXT which is attached. Look in the app.reg file and you can decode all the *.png files to find the look you want. Most of the png files are located in your SYS files.

edit: find the png files in the app.reg under:

[HKEY_CURRENT_USER\Software\Microsoft\Today\RadioButton]

[HKEY_CURRENT_USER\Software\Microsoft\Today\CheckBox] to skin them...
[Windows Mobile] Ham3r:
You don't understand my question.

That skining is possible on offical COM2 builds?

I have old style kitchen, with optimized 21908 by me (i don't have mxicold_wpc_2.provxml).

I think: 21908 is real death 219xx branch (old core, new graphics engine).
[Windows Mobile] fire_z:
21914 and 23129 xip.bin

Can anyone upload 21914 and 23129 xip.bin

Thank you very much in advance:)
[Windows Mobile] mureta:
@BoomerCE

Tks for the info!:)

@AndrewSh

Tks for Mirror for all information passed on and updated. :)

mureta.
[Windows Mobile] AndrewSh:
21690_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT

Windows CE: 5.2 Build 3600 (Mar 29 2011. 15:43:01)

Thnx to Boomer for sharing and to rewwps for re-uploading
[Windows Mobile] mureta:
help please !

Hello guys,

Thanks again AndrewSh. Super fast your updates!

One doubt :

My steps: I leave only the dpi96/resh240x400 ... everything related to the Omnia, the retreat langs SIM_TKit 0409, SYS, I put my langs 0416 (Brazil) and also removed the msxipkernel (hd.dll and osaxst0.dll).

One question:

What am I doing wrong, I can not make it work on my Omnia these builds 29017 and 29018? :(

Loads the boot but no screen appears welcomehead to continue, it might be? :mad:

Any help will be of great size.

Tks so much.

mureta.
[Windows Mobile] nikagandovsky:
language pack

Friends, could somebody tell me how to get the language pack of my language 0C0A (spanish) for the 29xxx build? Thanks in advance.
[Windows Mobile] mureta:
Go here :)

mureta.
[Windows Mobile] AndrewSh:
29019_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT

Windows CE: 5.2 Build 6212 (Mar 13 2011. 15:48:25)

the same Thnx to the same persons as usually :)
[Windows Mobile] prabhat:
Thanks AndrewSh for mirror and sharing.

I am just wondering how all these builds are released/leaked at same date/time :confused:.

29018_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT

Windows CE: 5.2 Build 6212 (Mar 13 2011. 15:48:25)

29019_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT

Windows CE: 5.2 Build 6212 (Mar 13 2011. 15:48:25)

Thanks.
[Windows Mobile] AndrewSh:
prabhat, I already explained the situation with the build date and number for more then 100 times already here at xda!

So, should I do that again?
[Windows Mobile] cajunflavoredbob:
Of course you should explain it again. It's not like XDA has a "Search" function. :p
[Windows Mobile] Farmer Ted:
It's because they're all exactly the same thing; the only difference between the builds is the build number.
[Windows Mobile] bikertibi:
from office dll's you can find the date of 29019 release to be 07 Apr 2011, 19:20:16
[Windows Mobile] AndrewSh:
Ok - no problem. But xda really has "Search" function.

So -

Comparing 29018 - 29019:

besides office.dll, welcomecenter.exe and dsm files, the difference (in hex) -

MSXIPKernel - mxip_lang.vol

BaseApps - msdrm.dll; pimstore.dll; rmactivate.dll; secprop.dll.

BROWSING - browser.dll

BTDUN - atcmdint.dll

MediaOS - wmcore.dll; wmpocx.dll

OS - ossvcs.dll

Redist - cplmain.cpl

Shell - syncmgr.dll

Webview - webview.dll

WMWidgets - riplugin.dll; systemstateom.dll; widgetsom.dll

СE OS and build (29018 - 29019) is being changed in dsm MSXIPKernel and in cplmain.cpl and correspondent dsm, build # (6212) and date is fixed in ril.dll. It's absolutely clear that if the ril.dll is not updated - the official release # and date - stay the same as in previous build.

Also office.dll и wmcore.dll both contain the updated build #.

The rest changes are real build updates.

P.S. cajunflavoredbob, New Orleans? :)

Like your funerals!
[Windows Mobile] pupakota:
Oo

(sorry, really couldn't resist)
[Windows Mobile] AndrewSh:
Nothin aka pupakota is killing me :)

Not your funerals, but New Orleans' traditional ones :)
[Windows Mobile] cajunflavoredbob:
Heh. I was only kidding about the "search" function. It was sarcasm. I am certain that it's been answered several times before to look at the build date for office, and not the posted date. Some users just don't like to search and read is all.

Off-topic

Our funerals are the way they are because of a tradition in the city about spirits and hauntings. It is said, that by playing loud music and carrying the deceased around the streets in a seemingly random pattern, that it will disorient the spirit and prevent it from returning home. That is the origin of the tradition. Now it is more of a Jazz band parade to celebrate your passing from this life into the next. This area is very spiritual in some form or fashion. It is rare to find anyone who doesn't believe in some deity here.
[Windows Mobile] pupakota:
hehh, i understand now, A :).

Btw, it is tragic what happened to N.O. not so long ago..

p.s. thanks for new builds...good to see movement in matter.

long live WM, best mobile system for adv. users, imo.

Happy Easter egg, guys.
[Windows Mobile] ai6908:
Now I know why we do it that way back home!:D

PS: Sorry for SPAM...;)
[Windows Mobile] joojoobee666:
Thanks for keepin us in the loop AndrewSH :cool:
[Windows Mobile] bajok!:
great job!!!

@AndrewSH

...thank you very much for the new builds and to all responsible to keep WM6.5 alive...!:)
[Windows Mobile] c_shekhar:
I fail to understand one thing that with such a negligible change they are releasing/leaking a new build?
[Windows Mobile] AndrewSh:
c_shekhar, about minor updates - it's Windows. How often do you get Windows Update notifications on your computer? Almost every day? Why do you think that Mobile Windows differs from other Windows?

Why "they" are releasing? Normally their aim - not to make you happy with new rom but to debug OS. Guys are just fixing some mistakes in the system.... And guys are not "leaking" anything to you or to me.....
[Windows Mobile] NinoFR:
Dear all,

What would be the most stable/recent build between 21690 and 29019 ?

Thanks in advance.

Kind regards,

Nino
[Windows Mobile] akash_bidhuna:
will this build work on htc elfin

i cooked rom by using this build 29019_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT

and it is stuck at smart mobility

any idea
[Windows Mobile] NinoFR:
OK thanks for your feedback.

Regards,

Nino
[Windows Mobile] pupakota:
is wincenls present in your set?
[Windows Mobile] akash_bidhuna:
problem in startin elfin after flashing

i cooked a rom using official rom of htc elfin i.e wm6.1 and 29019_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT without removing any pakages from it

but after flashing by using this rom it stuck at smart mobility

i am using ipl 3.07 and spl 3.1 cmon hardspl

this is first time i am cooking.So i hav no idea about it.
[Windows Mobile] pupakota:
sigh. read my question, again...
[Windows Mobile] akash_bidhuna:
wincel

i dont know what the wincel is?
[Windows Mobile] AndrewSh:
The post of akash_bidhuna has nothing common with feedback because the guy did not manage to make bootable rom for his device.

Both builds are absolutely OK - you can use any one you like
[Windows Mobile] akash_bidhuna:
wince.lns

i checked my system folder wince.nls file is not present
[Windows Mobile] malatest:
ppgprov missed in 29019?

First of all, thanks for all.

Is possible that build 29019 doesn´t need ppgprov package? Or is missed and I have to replace with one of another version? Thanks
[Windows Mobile] AndrewSh:
Normally ppgprov is a piece of registry, which configures Push Proxy Gateway for SMS... Actually - you have your SIM card with predefined settings to configure it.

It's absolutely static thing so you can use any ppgprov package from any build.
[Windows Mobile] NRGZ28:
That would be.. Microsoft's programmers :) Sorry couldn't resist.. lol
[Windows Mobile] NRGZ28:
That file never changes anyway.. u can use it from any other build.
[Windows Mobile] akash_bidhuna:
drivers instalation problem

by using wince.nls file from other build i am able install the windows.

But there is a problem at the time of installation screem alingnment option does not appears, and nor the customization option ,because of that not a single application is installed in my phone which i defined while cooking and also there is singnal and touch screen is not working properly

any idea what is happening?
[Windows Mobile] Farmer Ted:
Make sure you're sending custom.lnk to the startup folder with your initflashfiles.dat.

You should probably ask this stuff in the cooking for beginners thread.
[Windows Mobile] pupakota:
check oem for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Welcome reg key, maybe it is set for ffffffff, then you won't get calibration on first boot(what's not a problem for device with startmenu hardkey and dpad, as it is possible to get into screen options, but it may be serious prob for buttonless devices without predefined screen alignment).

it may be a part of solution, i'd recommend check initflashfiles.dat for links to startup processes, too.

or you cut too much.
[Windows Mobile] akash_bidhuna:
where will i get these files in dumped base rom or in new build

please give me the path .
[Windows Mobile] mureta:
29017 and 29018

I am repeating my question again since I got no response or the way my question is very complex, does not find anything about it, if they can at least tell me where can I read about this I doubt I will be more than grateful and not wanting to interfere with topic.

I thank all.

My steps:

I leave only the dpi96/resh240x400 ... everything related to the Omnia, the retreat langs SIM_TKit 0409, SYS, I put my langs 0416 (Brazil) and also removed the msxipkernel (hd.dll and osaxst0.dll).

My question:

What am I doing wrong, I can not make it work on my Omnia these builds 29017 and 29018?

Loads the boot but no screen appears welcomehead to continue, it might be?

Any help will be of great size.

Tks so much.

mureta.
[Windows Mobile] Farmer Ted:
The easiest and fastest thing to do is just search your kitchen directory.

It sounds like you may be leaving out wince.nls as well, but really, you could be doing any of hundreds of things wrong, and it's next to impossible for anyone else to figure it out, unless it's one of the obvious things. I'd recommend either putting wince.nls in your oemxipkernel or in your oem and leaving it there. Personally, I keep mine in the kernel.
[Windows Mobile] pcarvalho:
hi all,

im having a strange issue...i cant sync email on build 29019 and i dont know why...

i didn't change anything from previous builds...just applied COM3 caller id fix and added threaded email from 23569...to this COM...

i always get:

email: failed to login. please try again

i can login to msn but cant get emails

...any ideas?

thanks in advance

cheers
[Windows Mobile] akash_bidhuna:
files not found

i am not able to find custom.lnk and initflash.dat files in my kitchen's directory.

Iread somewhere in the forum that these files hav to be created manually for custom roms,if i am correct can u please explain me the procedure for it.
[Windows Mobile] pkoper:
It´s initflashfiles.dat you are looking for.

If you dumped a stock rom it is there.
[Windows Mobile] akash_bidhuna:
custom.lnk

what about the custom.lnk file where i can get it.
[Windows Mobile] c_shekhar:
My dear, I very well know why and how the updates are released having been on this forum for the past >7 yrs ;)

The sole idea for my comment was to invite the deliberations on the issue. because the report few posts back was that only office has change of date.
[Windows Mobile] AndrewSh:
My dear, hopefully we both will not take a ruler to start measurements :) We have almost the same length :)

Actually your comment was few posts after my builds changelog report. And the office.dll was mentioned as one non-significant thing among other changes. The post of bikertibi (to which you had referred) was only about detecting the real date of the release.
[Windows Mobile] Farmer Ted:
It's in one of the sys packages. I'm not going to tell you which one, because searching is easy to do. It may be a hidden file.

Maybe the person compiling the build left out something really trivial, so they did a re-build with whatever it was fixed. I would guess that they have to keep records of everything at microsoft. Or, perhaps they are just two nearly identical builds with a tiny, insignificant difference. You'd really have to ask the person/people who compiled the build.
[Windows Mobile] NIKOSXRI:
Mod Edited