yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] Laurentius26:
The post is not off-topic isn't? :)

I'm still waiting for someone to reply to our post and maybe share 23157, 23158, 23160.

It's a request and I see no reason why I should remove the post.

Anyway, a pitty I had to move a mountain before 29022 is shared, but I appriciate you do now.

Thanks!
[Windows Mobile] + Que PPC:
all efforts to have some builds are great appreciatted to Andrew and leo, just keep it up buddies
[Windows Mobile] AndrewSh:
It looks like you got the answer yesterday.....

:)

On the other hand - now it's very easy to upload new builds :)

I can share here one dsm from xip, one cplmain.cpl and one dll from Mediaplayer - and that's it. Sorry - I don't know how to patch office.dll (just did not check how to do that) but it's not a big deal :)
[Windows Mobile] Laurentius26:
Yeah cool, make your own "FINAL LEGACY" serie now that WM is dead!

30130, 40140, 23165, 23999 etc..

A lot of people will be happy with that I ques. :rolleyes:

You even don't need to upload but hex patch the files straight on the ftp if people need a new build number. :cool:

Cheers Andrew, very good idea.

Thanks! :)

Edit; I see final legacy is already used, maybe "WM Continues" or something would suit better.
[Windows Mobile] phezthie:
I prefer 6 or 7-digit builds :D:D, cheers :)
[Windows Mobile] Laurentius26:
Yeah a job that is done in a couple of seconds.

I wonder why some people need another week to change the number to 23160. :confused:

Cheers! :D
[Windows Mobile] Laurentius26:
Like I said, I don't believe in all this funny bunny. :p

Hopefully 23157, 23158 and 23160 are getting shared ASAP so everybody can enjoy. ;)
[Windows Mobile] phezthie:
Yeah, I perfectly agree with you, and probably most of the members of the community. :)

But the hard part is how to convince someone to share his stuff, be it conditionally or otherwise. No matter how noble the objective would be, by or in asking him to share it, the decision is still reposed to him and we cant do anything about it. There could be a justifiable reason or two in withholding it. The presumption is in his favor and i believe that its unnecessary to resort to any sort of compulsion or other unwarranted ways just to achieve the objective, again, no matter how noble it is.. my cent.. :)

regards,

phezthie
[Windows Mobile] Laurentius26:
Yeah that's hard indeed, I approached wrong.

Lets try a different approach. :)

http://xdaforums.com/showpost.php?p=15091744&postcount=681
[Windows Mobile] xmoo:
Hahaha Amen on that! If I find anything new, Ima share with yall!
[Windows Mobile] phezthie:
I submit, its your right too... :)

but im still hoping that there's another way to achieve the "noble objective"... cheers..
[Windows Mobile] pkoper:
From memory 21057 was a hex edit.
[Windows Mobile] pupakota:
anyway, it is perfect.
[Windows Mobile] xlightwaverx:
Latest 6.1 Sys/Xip

Looking for the latest 6.1 Sys/Xip

I would like it packaged the way DFT does it so Wes Rom tool can port the Xip in on each build. Is that something that is around?

X
[Windows Mobile] kaywchan:
Thanks for sharing AndrewSh

I haven't checked here in a while, and just saw this. Thank you AndrewSh!
[Windows Mobile] pupakota:
http://joojoobee666.ppckitchen.org/Kitchens/21057/

typical, useful set for normal use.

other builds(LOTS of them):

http://joojoobee666.ppckitchen.org/Kitchens/

nobody should beg from new semigods anymore.

it is free as we are, and nobody will change that.
[Windows Mobile] cajunflavoredbob:
It's ok. We all have bad days. While we all disagree with the direction DFT has taken to not share builds with the community, we are grateful to them and you for sharing in the past. I wish there were some way to change their minds, but I guess there isn't. Anyway, thanks to you and DFT for sharing in the past with us.

It's a shame WM has to die out like this, though. It was only just beginning, really. M$ was learning how to combine business with personal taste, but then they abandoned us and went on to WP7.... I guess we'll just have to see if that becomes a viable platform for business users in the future. Android is too much of a concern right now for me to switch completely.
[Windows Mobile] AndrewSh:
Totally agree!

Yesterday I finally started to use one nice feature of the forum - ignore list. Works perfectly and helps to reduce bad days amount.

:)
[Windows Mobile] cajunflavoredbob:
That and the report button keep me sane when I roam around in the Android side of the site. :)
[Windows Mobile] illi:
Peace everyone:)
[Windows Mobile] + Que PPC:
Ignore list! :o I want a couple of that buttons... ¬¬ everywhere :p
[Windows Mobile] Laurentius26:
Hi all,

Can anyone help me please, I'm trying several builds to find?

I'm looking for the MS build with Office which has Outlook conversation mode.

Thanks in advance. :)
[Windows Mobile] malatest:
COM5 has treathed e-mail. Is this what are you looking for?
[Windows Mobile] Laurentius26:
Yeah indeed, I'm using 23148 and tried to swop Office from 23569 but no luck.

Maybe I need to use whole SYS.

Thanks. :)
[Windows Mobile] OndraSter:
Office doesn't contain tmail and other libs needed for threaded view.
[Windows Mobile] Laurentius26:
Thanks Ondra, I ques going back too good old 23568 will do the trick. :D;)

Edit; Yep that does it, cheers!
[Windows Mobile] sharkie405:
Why don't you guys just add threaded email? So far this package (that I got from somewhere here on XDA) has worked with all 6.5.X builds I've tried.
[Windows Mobile] Laurentius26:
Hi Sharkie,

Thanks for the package, probably I'm doing something wrong but the whole rom hangs when I go to my inbox with this solution. :o

But maybe I can take the same files as in your package from 23568 and use it in 23148.

Cheers ;)
[Windows Mobile] sharkie405:
I remember when I first tried to use it it didn't work. I have to place it in my kitchen so that it is one of the last packages to get cooked. Maybe that's your issue... Actually in my kitchen, it is the LAST package that I cook in. Try that if pulling the files from another build doesn't work.
[Windows Mobile] Z80-Man:
BTW, what's wrong cooking with 23569 ? I found it was the best build ever, stable, fast, reliable, and so pleasant to use ! :cool:

I mean, COM2 hasn't moved much either, during last months, and is still worth it...

Has WM6.5.5 any unseen (for the public) compatibility problems or anything else, with latest Sense builds, for instance ?
[Windows Mobile] caliban2:
iirc, only drawback of 235xx was mem-management. gwes.exe just kept growing and never released any mem (40+mb sometimes).

but it was not that bad compared to later stuff. also depends on mods (taskbar etc)
[Windows Mobile] Z80-Man:
Oh, OK, I see...

Could be a problem with the HD (though I remember a very pleasant to use ROM, I changed only because later builds were localized for my language), but should not be a problem at all on the HD2, then. ;)
[Windows Mobile] cajunflavoredbob:
In my own ROMs, I'd seen it climb up to 54MB on my Rhodium. I stopped using the build after that. I still really like 28236 and 28244.
[Windows Mobile] Laurentius26:
I don't see a memory issue on 23568, the memory is stable and it doesn't leak.

At least on my device it isn't.

Edit, I've looked at gwes.exe with Dotfred's Taskmanager and gwes.exe is 33647 kb

Free storage memory is stable at 194.65 mb.
[Windows Mobile] caliban2:
hey, i wrote "IF i remember correctly" and "only" drawback... :p

nah, i have very good memories of com5 and think i'll cook it soon again - 29022 isn't outstanding great on mem as well. but fast & very stable, which counts a lot.

by-the-by:

from memory, i don't need dialer fix, check reg for "COM3"-stuff and htc-lockscreen needs special treatment (unlock). anything else? ^^
[Windows Mobile] NinoFR:
QVGA PhoneCanvas COM3

Dear All,

I need your help ..

I am cooking a COM3 Rom (29022) and I have fix almost the well-known issues such as CallerID fix, scroll bar.

But I still have the followings issues:

- WM left softkey (keyboard on/off) mapped to "Contact"

- DialPad softKey

- Call history windows with bad position

As far as I have searched through the forum I did not find any package that fix everything for QVGA devices, only on VGA device.

Have I missed something ?

Sorry by advance I have missed my search :(

Thanks by advance to everyone who can help me...

Best regards,

Nino
[Windows Mobile] ---UFO---:
Please, does anyone have French (040c) initflashfiles.dat for WM 6.5.3?

Thanks in advance.
[Windows Mobile] HTC0017:
From 23568 Diamond kitchen
[Windows Mobile] ---UFO---:
Thanks. You saved me.
[Windows Mobile] Z80-Man:
Do you really mean "WM", or "Sense Home" ?

They aren't managed the same way, and the latter overrides the first one.

WM left softkey

:

[HKEY_CURRENT_USER\Software\Microsoft\Today\Keys\112]

@="Contacts"

"Open"=":MSCONTACTS"

Sense left softkey

:

[HKEY_LOCAL_MACHINE\Software\HTC\Manila]

"HomeLSKArguments"=""

"HomeLSKPath"="Manila://people/browserlayer/peopleAll.page"

"HomeLSKText"="Contacts"

You can change them to whatever you want (note that on the example above, the MS softkey launches Outlook Contacts, while the Sense softkey launches HTC Contacts... But it could launch Outlook Contacts as well !)

You mean, in bubble tiled / icons display mode ? When [HKLM\Software\Microsoft\Shell\BubbleTiles]\TextModeEnabled=0 ?

As far as I know, it's inside cprog.exe

I never could solve this one, as there's no external resource file responsible for that.

If you look carefully at how it behaves, Sense is actually trying to draw a "Contacts" button on top of an existing MS "keyboard on/off" button, while adding a smaller centered "keyboard on/off" button (just compare under Sense and under Titanium, you'll understand immediately what I mean)...

There's a similar bug with the centered keyboard on/off button, that moves to the bottom left from its original position when you rotate in landscape mode, then stays misplaced after that, whatever orientation you choose.

I could find no solution for this one either, but the left softkey button displays correctly in text mode (i.e. with [HKLM\Software\Microsoft\Shell\BubbleTiles]\TextModeEnabled=1) : that's the only way I know to fix it.
[Windows Mobile] NinoFR:
No I am speaking about softkey in phone mode ...

By the way, thanks for your explanation... it will help me !:D

Ok many thanks for your answer and your precisions...

Kind regards,

Nino
[Windows Mobile] Diagrafeas:
Differences between 23569 and 29022

I haven't cooked for a while (a whole year actually), the latest build i used was 23569. Can someone tell me what is different in this new build 29022?
[Windows Mobile] pyrorob:
Anyone know which of the newer 231xx builds have voice command?
[Windows Mobile] pupakota:
[upd: nevermind]
[Windows Mobile] joojoobee666:
Yay! New builds! Thanks for the goods Boomer :D
[Windows Mobile] krazy_about_technology:
Thanks everyone at darkforcesteam as well as XDA for posting 21914, its working really well on my Omnia Pro B7610, I am so happy :)
[Windows Mobile] Farmer Ted:
If they're coming from DFT, then they probably won't have it. Only the builds leaked from the US (non-EA) have it, I believe. The Asian builds don't have it. Just put together an EXT with MSVC and use it in all builds-it's not like it's going to change.
[Windows Mobile] wsparvis:
I have the builds back to 23118 - none of them have VC built in.

Recommend you use the packages from 2356x.
[Windows Mobile] JLowe:
Cooked in the latest SYS Com2 21914, but I got always in settings/system/device information/software information

"os version 21909"

anybody can give me a hint where I have to look in the SYS-folder to correct this?
[Windows Mobile] indagroove:
Are you using XIP.bin or msxipkernel from 21914?
[Windows Mobile] JLowe:
I am using MSXIPKernel and integrated it into my Vistang-Kitchen

21914_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT.7z
[Windows Mobile] af974:
Got it from here http://xdaforums.com/showpost.php?p=7610378&postcount=641 and i can see only 21914 in OS version
[Windows Mobile] mua30:
Andrew,

I wanna thank you very much for nice posting of 21914, its so fantastic build.

just wanna ask u , voip component is related to voice over ip!!

if i removed it from ma build, does this affect the 3g!!

thx in advance again bro
[Windows Mobile] d_train:
Is there a COM3 QVGA dialer? I have a Nike device that I still use a dialer from COM2 (MEGA 2G dialer).

thanks

DT
[Windows Mobile] indagroove:
Isn't there a COM3 Mega rom somewhere?
[Windows Mobile] d_train:
Not that I am aware of - the latest MEGA - RUU_Mega_hTC_Asia_SEA_WWE_1.37.728.3_Radio_Signed_61.55t.25.38_3.54.25.25_Ship still has 21889 as the SYS

DT
[Windows Mobile] indagroove:
Oh, right, I guess I was thinking Photon, but that's hVGA. I dunno then, sorry.
[Windows Mobile] JLowe:
Mxipkernel
[Windows Mobile] alesscam:
it's very strange

i have open dsm from mxpikernel with dsm editor

and it's ok.....21914
[Windows Mobile] JLowe:
Sorry, sorry - I flashed the wrong image... :(

I had two images in the Ruu-Folder and renamed the wrong one...

Sometimes it's better to stop and go sleeping and try again next morning...
[Windows Mobile] Alexx~:
21915 AKU5095 Windows CE: 5.2 Build 3833 (August 6, 2010 16:49:39)

http://zoonay.com/xda/ROM_Builds/21915/21915_XIP.BIN_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_ALL_LANG.7z

Ah, yes - thanks ......

Original source - http://www.xda-china.com/thread-74190-1-1.html

Thank for sharing xda-china.com, as well as all people on earth who can help me in the future.
[Windows Mobile] AndrewSh:
The main point is fundamentally different Graphics, Windowing and Events Subsystems. That causes a lot of other differences.
[Windows Mobile] malatest:
23569: Last COM5, native threaded e-mail, longer RAM consume, slower but very stable. We Still use parts of this build for pacth in COM3 (phonecanvas incoming call...)

29022: Last COM3 MS branch, not threaded e-mail, fast, very fast, better RAM consume. Very stable.

23152: Last COM3 HTC branch, similar to 29022

Now I´m using 23152 (Topaz), but I´ve tried 29022, 29020... and I think 29017 was smoother for me.

Greetings
[Windows Mobile] ai6908:
I have been running 29022 for more than couple of months now, and dont seem to have any issues.:)
[Windows Mobile] caliban2:
same here, it's great! especially with the new feature in osbuilder, which lets you turn off compression for certain files. and i've finally been able to cook threaded email from com5 into it, so i'm a happy camper now. :)
[Windows Mobile] ultrashot:
I prefer using 21690 over 29022. Just seems a bit faster and may be even more stable. That's IMHO, of course. Same AKU as in 29022, so it isn't any older.
[Windows Mobile] Nixeus:
Do you think that we get new build ?

What about Windows Embedded Handeld ?
[Windows Mobile] cajunflavoredbob:
No one has reported seeing newer builds on DFT. 29022 was the last one we saw, I think. All the 290xx branch are Windows Embedded Handheld.
[Windows Mobile] Nixeus:
Thanks :)

I would like to get the latest com3 or com5 rollup build in order to having the MUI files for Office2010.

What is the latest FRA(040C) build please.

23152 ?

Anyone have a link please, it will be so great ;)

Thanks a lot ,

best regards,

Nixeus
[Windows Mobile] malatest:
I´m using 28230 rollup for 23152 lang pack (both are COM3)

I think, i don,t sure is this

http://www.mediafire.com/?ywohlzimzhc
[Windows Mobile] Nixeus:
thanks :)

Do you have a link please :)

Thanks
[Windows Mobile] malatest:
http://www.mediafire.com/?ywohlzimzhc

Edited
[Windows Mobile] Nixeus:
Thanks a lot :)

Hope we will get new build or....the famous Windows Embedded handeld 7 !
[Windows Mobile] Nixeus:
What about this ?

http://www.microsoft.com/windowsembedded/en-us/downloads/download-windows-embedded-compact-ce.aspx
[Windows Mobile] caliban2:
Somewhere I've read that embedded 7 will break backward compatibility with 6.5.

And about 6.5: it's a bit hard to understand, but from what I get it's compatible to winmo 6.5 app-wise, yet restricted when it comes to replacing the gui. The targets are industry-devices (scanner etc), not phones.

Someone can shed some light on this? :)
[Windows Mobile] sker100:
hi all, I'm trying make a rom with win 6.5 for my htc jade and i want know witch version is the most stable? a I prefer one with the buttoms in the inferior part of the screen, and one in portuguese.

tanks
[Windows Mobile] NinoFR:
Hello,

The most stable one is COM1 (21916).

The most recent one is 29022...

Regards,

Nino
[Windows Mobile] sker100:
thanks for answer butt in this thread i don't find this builds...

i search in the xda search i don't find it in the Portuguese language, anyone can help me find that two builds in Portuguese?
[Windows Mobile] NinoFR:
Look at the 1st post, there is a link to download build for WWE.

You need to download a rollup...

Look for WM 6.5.X Rollup all lang and all res

Hope it helps.

Nino
[Windows Mobile] bibiteri:
23563 roll up

http://www.mobileunderground.info/sys/

Download the builds you want and change the languaje with that roll up.
[Windows Mobile] sker100:
That website o indicate only have the english version,

you say to chage the language butt how i can do that?
[Windows Mobile] Farmer Ted:
Use one 't', lol.
[Windows Mobile] raving_nanza:
hi dudes,

looking for build 21056 for QVGA, can anyone supply me with a link please :)

EDIT:

nm i found it on Da_G's thread ;)

EDIT:

some files are corrupt in the .rar i found :eek:
[Windows Mobile] NinoFR:
Dear all,

I have some questions for chiefs:

- I am using 29022, could you, please, support me to find that files from build 23569 I should use to patch build 29022 for phoecanvas, incoming call, call history .. issues ? Is it cprog.exe ?

- 29022 does not support threaded-email ? If yes, should I use build 21690 to get this feature ?

- The mirror repository given in the 1st post is not reachable ... is there any others mirrors to download WM builds ?

Many thanks by advance for your help.

Kind regards,

Nino
[Windows Mobile] James72:
1) Here for E-Mail Attachements (Thanks to Sharkie405)

http://attachments.xda-developers.com/attachment.php?attachmentid=656630&d=1310830016

2) Then I've problem with Keyboard (SIP) on Touch Pro2.

I look SIP and appears larges letters, by 23569 don't happen, the Letters are perfects. Is there any cure for LARGE LETTERS on SIP?

3) In my Build 23569 appear Htc Volume Control, by cooking Build 29022 don't appear it.

4) What about phoecanvas, incoming call, call history issues?

Please, can anyone post us how "treate" thos "bugs"?

Thanks in advance!
[Windows Mobile] malatest:
PhoneCanvas fix for 6.5.x

Well, there are several variables for this, like type, version, etc of phonecanvas you are using. If you use phonecanvas 5 from Huasang you don´t need fix, but you can´t use videocall (if your physical phone supports that). I use rhodium phonecanvas version 4.2 for topaz (supports videocall) with all this archives. Some of them are from 23569 for incoming call like celltsp.dll, cfghost.exe, cprog.exe, pimstore.dll and tpcutil.dll and the others phcanrc.dll (WVGA only)(for sidebar and perhaps other things probably from Leo) and phcanhtc.dll with hex modifications (thanks to SergeyLAR, Lissek, and many others) from phonecanvas rhodium 4.2 for incoming call position and little bottom for dialpad.

In other hands, if you want to be able to use volumecontrol while calling, you may use phonecanvas, volumecontrol and Dshow packages from same dispositive.

This is the complete packages I use. If you want try it, you must change language (0C0A) on phonecanvas and volumecontrol.

For call history position I didn´t find any fix. From titanium you can see call history from softkey on phone
[Windows Mobile] James72:
Probe with those

P.S. What You said about the stability pf 29022 in my Pro2 in not true. I find more reactive and stable Build 23569, because 29022 is so slower, slower and slower. I've only substituite IE6 from 29022 and inserted in Build 23569.
[Windows Mobile] NinoFR:
Thanks you all for your post... about call history issue I have found a workaround: I am using AMEBA tools for position fix and i have resized the bottom button to avoid overlaping the task bar :-)

Otherwise, the best solution consists in dissambly phcanhtc.dll and modify some HEX part...

Regards,

Nino
[Windows Mobile] Stephen:
I am experiencing the same issue. If I use my fix from os 23569 when you first go into the phone canvas and look at the keypad button at the bottom the allignment is perfect. When you then go into the menus and then look at the keypad button the button is off centre.

Looking to see if there is a fix for that! I have everything else sorted as far as I can tell.
[Windows Mobile] Stephen:
Hey I was having a look at the twaks you uplaoded. Did you happen to take them out of my oskitchen build for the hd2? They look very similar to mine? If you did, I dont mind you uploading them but you should no that they are not a 100% stable for os 29022. They were orgionally for os 23569.

I have tried to modify them to work with 29022, but still not quite 100% there yet!!!
[Windows Mobile] James72:
I raccomended You to work with 23569, I don't have any problem except "Keyboard Info", it's not allineed! The same happen to 29022.
[Windows Mobile] James72:
Yes, It's cames from your OsKitchen. Sorry, I've forgotten my thank to You.

Otherwise, but why not substitute the 29022 modules with 23569 modules directly in the Kitchen, maybe It's worked stability.
[Windows Mobile] NinoFR:
Hello,

Do you mean that using 23569 instead of 29022 is better for phonecanvas issue ? Does it solves call history position ?

Since AKU of build 29022 is newer it should be more smooth than 23569... am I right ?

Thanks for your precisions.

Regards,

Nino
[Windows Mobile] Stephen:
Yes there still are a couple of phonecanvas issues, very minor the button for the dial pad sometimes seems to go out of allignment and the call history position as well. I will let you know when I get a fix.
[Windows Mobile] NinoFR:
I have already found this: http://xdaforums.com/showpost.php?p=6178217&postcount=14826

But have not succeed in find those hex data .. :(

I have another issue ... when I change the back light settings it does take into consideration dynamically I have to soft-reset to take the new setting into consideration.

EDIT: Found the back-light fix... use the correct HTCUtill.dll file :)

Regards,

Nino
[Windows Mobile] James72:
Can You Post It?
[Windows Mobile] NinoFR:
For sure ... in attachment :

1 - ZIP File: External package for ROM Cooker

2 - CAB File: To be installed directly

Regards,

Nino
[Windows Mobile] James72:
Thanks Nino.
[Windows Mobile] NinoFR:
Miror down

Dear all,

It seems that the mirror http://joojoobee666.ppckitchen.org/Kitchens/ is down ...:(

Is there any others ones ?

Regards,

Nino
[Windows Mobile] ct_moi:
Hello,

You can try here: http://fileserve.com/list/j69C7k3

Upload in progress of all I have on my hard disk.
[Windows Mobile] NinoFR:
Many thanks to you :-)
[Windows Mobile] Nixeus:
Hello my friends,

I knwo thaht Opera is better thaht Internet Explorer on Windows Mobile, nevertheless i would like to know which build has the better version of Internet Explorer.

21690, 29022 ?

Thanks in advance :)

Best regards,

Nixeus
[Windows Mobile] Farmer Ted:
Use PIE from 28245; that's the branch where PIE was being developed, supposedly. It should work fine in other builds.
[Windows Mobile] Nixeus:
Thanks :) I search the build of PIE with tha maximum of features ;)
[Windows Mobile] tobbbie:
Is there a way to tell apart the Windows Standard (Smartphone, no touchscreen) builds from the usual professional (with touchscreen)?

I know that most only care about the touchscreen devices, but is there a repository for the standard builds? Which is the latest - or probably the most stable?

I know I could use some already cooked smartphones as a base (also for porting/using packages in the OEM area except the HW dependent ones) - but as a start I want to go for a plain vanilla from a shipped ROM.

Would be great if German (0407) is already included.
[Windows Mobile] AndrewSh:
Build 23153_AKU5314_CHS/CHT/WWE

is available at DFT for download......