yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] + Que PPC:
Yes GTx it was solved before and i can tell you is the same same trouble that this guys have... :D start to search that mui or dll duplicated

You dont need to download the newer one cause if you already knows where does that mui is you will give me the real question here....

And the real question here is....

Does the Newer "MUI or DLL" is in the sys as you comes posting a page before?

So I can answer Of course YES!! you know... ancient times :rolleyes: jejeje when i had this kitchen working with the old 21022 build uuuuu :rolleyes: hehehe i used to change the folder icon... and guess what... the folder icon was in that shelres dll... then that MUI has the links that calls for the right images inside the dlls or the images that are in the windows folder....

With this info you will be able now... to understand that::::::

OLD MUI's and OLD DLL's dont have the same icons... the same resources NEITHER the same links to call for that especific images...

thats why if you have that old muis or dlls you will have this xtrange behaviour.

hehehe ****!!! who wants to be suscripted to my classes???? :D Im joking im not so good to teach anybody.
[Windows Mobile] + Que PPC:
Nice question thats the dirty way to make it works but why to do it...or why to keep that old one?... if you will never cooks again for that old build... ;)

I bet you to do something... take a screenshot of your inside OEM folders i can tell you wich mui or dll is the one with troubles.
[Windows Mobile] Pisca:
I agree with you, if someone is asking about things that has no ideia what they are, or where they are placed, no possible answer can satisfy, even if they write a romance in each post or scream around
[Windows Mobile] + Que PPC:
Oh Pisca you make me laugh :p jajaj thanks...
[Windows Mobile] mike1986.:
Why are you making jokes if I asked serious question?

I want to know that because sometimes I put newer versions of some drivers or dll files and I never know If it's neccesary to check the mui files also.
[Windows Mobile] witschey:
As I said your answer was better than no answer, but far from ideal. You taught me the method by which I can theoretically solve it. I appreciate that. Thanks!

If I find the mui or dll that is causing the problem I will post the answer with before and after pictures and I will provide people with the 23047 dll or mui so that they can solve the problem in 2 minutes instead of many hours. That is the type of answer that I wanted to get with my original post, but instead I was given 'homework' to go do it on my own. That' s fine; except if we all were sent to do 'homework' instead of sharing solutions the value added of such a forum would be diminished. Its better if each of us solves a few things and shares ready to implement solutions so that we don't all waste time on the same things.
[Windows Mobile] + Que PPC:
Im not doing jokes with you!!!! :eek: my answer is God damn personaly help to you!!!!

ok... MUIS are the non part of an "update" process... cause there arent newer things than WM6.5.X to date...

Lets do this more comfortable ok? again... take a capture of your PC screen showing the OEMDRIVERS folder contains, then post it i can take a look of it... again, wich device you have???

I will never help anymore.... :mad:
[Windows Mobile] joshkoss:
Chill pills

Calm down guys... this place is a forum for everyone to learn.. Please be respectful.​
[Windows Mobile] S.V.I:
sorry to trouble you, but i am having a troublesome issue that i can not seem to find an answer to:

since updating to 23037 i have had my keyboard overlap what i am writing.

did anyone run into this problem since updating to a SYS with the large bottom bar?

is there a solution?
[Windows Mobile] mike1986.:
Sorry If I misunderstood but I simply don't know what will it give to you if I show you the screen of my OEMDrivers folder...

I have HTC Diamond

Screenshot attached...
[Windows Mobile] + Que PPC:
Ok sometime ago i published this

http://xdaforums.com/showpost.php?p=4504420&postcount=3669

As you can see... i had two windows flags instead a lock on two oks instead back arrow... so kane told me... you must to se if there is an OLD mui cause the muis has been change... Drkfng told me that it must be a dll (cause of course the dlls have been change too) so after so many research on my ext and oem folder i saw it here!!! in medkidcol (maybe other devices dont have this folder, cause the guy (joshkoss) who stripps the oem for us in hermes made this folder to !make! UI changes) see the pic (i dont have it any more jejeje but some guys needs a pic! (me I love pics! :p)

There i had that shellres.0409.mui old enough that this trouble jumps for me when the newer core ask for the codes or links that the muis has inside, of course this mui never works fine... even if i had the newer shelres.0409.mui in the sys at the cooking process if you pay attention the oen and the ext packages are the last to be eincluded so thats why the newer in sys has been overwrited by the old in oem...

So kane told me try this mui the same mui in the sys but recmoded of course... overwrite it in your working os... do a softreset... and what da heck!!! it works!!!! look this:

http://xdaforums.com/showpost.php?p=4504633&postcount=3674

Thats why you all need to see if there is a dll or mui duplicated... maybe the same mui works for you in other DPIs or ress but i can tell you that it dont wprks for you in other lang.
[Windows Mobile] TAEL:
To all dear raphael users,

My first ROM finally released.

TAEL ROM - WM6.5 Build 23049 [Manila][WWE]

http://xdaforums.com/showthread.php?p=4550213

Regards
[Windows Mobile] demeone:
Anyone notice in 23409 that there is no sound notification when you talk with someone and at the same time you've got another call (Call waiting). Only on screen it is. I wish to hear also that someone else is calling to me
[Windows Mobile] abc001:
What is "that TweaK"? Can you elaborate?
[Windows Mobile] player911:
The tweak cab file that was posted earlier in this thread to bump up certain app windows as needed. I can't remember the name as it was posted a while ago. Check the attachment window or search for "Manila Resco Fix"

Anyway has anyone had any luck bumping up the incoming call window from the Tachi Dialer?

Also I'm noticing that several of my apps have screwed up menu buttons. Not the graphics but for example in a program I use there are 2 buttons; Options and Menu. Well they both bring up the same window. The same goes with the Raph phone canvas... the Keypad button brings up the menu from the right button. So does the Tachi dialer for Contacts, brings up the right buttons menu.
[Windows Mobile] hasseye:
anyone thats wondering...i cooked both the 23049 and the 23412 and surprisingly but i felt the 23412 felt nicer....i might be wrong but thats the rom im using right now....if anyone is debating..give it a try. eager to see more COM4 builds.
[Windows Mobile] st4nd4l0n3:
Can i use these resource for porting my Samsung C6625???

thx.
[Windows Mobile] abc001:
Thanks. Unfortunately it is not working well for me (QVGA device).
[Windows Mobile] abc001:
May you update it to include QVGA devices also?
[Windows Mobile] Nagrom Nniuq:
+1. That would be nice.
[Windows Mobile] dijor69:
Hello, first of all wanted to thank you for your work, for giving us all this stuff.

On the other hand I have several questions I'd like you to help me solve:

When you click on a contact in the agenda should get a menu that you want to perform action: call, send SMS, email ... Well, my problem is that translating 0c0a not work for me, that is, if I click on a contact does nothing.

Would you know tell me that part of the sys is responsible for this, to find out where the problem?

EDIT:Eh already solved, a problem was poutlook.exe module, eh what replaced and fixed.

-Besides, I have the problem that LockScreen not work properly, ie, does not unlock the device, whereas if you press the keys decrease or increase volume, and press" ok "and if you can unlock. I've been reading that the problem may come from the native nk.exe, Is it true?, Is there any way to fix it?

-Finally, indicate missing packets VoiceCommand_Lang_0C0A, Transcriber_Lang_0C0A, to me are not necessary, but would have them.

Thanks for everything, and excuse my bad English, give thanks to google translator.
[Windows Mobile] ahmedfikry:
+ 1 ...QVGA fix pleaseeeeeeeeee
[Windows Mobile] svprm:
Yes,QVGA Fix please.
[Windows Mobile] rkumar8:
Hi, How can i install wm 6.5 for my htc touch viva? Where can i find the WM6.5 and do you have any single .exe or .cab file which will update WM6.1 to WM6.5 at a single execution.

Thanks,Rakesh
[Windows Mobile] Pisca:
Please look here:

http://xdaforums.com/forumdisplay.php?f=444

Follow carefully all instructions, there's no .exe or cab to do it, you must flash your device
[Windows Mobile] Röchelhilpert:
can somebody check on xbeta .. what is up with 21855 ?
[Windows Mobile] freeze5272:
It's from DFT.Someone said it's good .But I think the change is only the number there is not too many key points.
[Windows Mobile] freeze5272:
And it's Rombeta now.
[Windows Mobile] Farmer Ted:
Here's a little tip: read the first posts of the thread. Don't quote them. Thanks.
[Windows Mobile] Röchelhilpert:
i would try it .... can somebody upload the files ?
[Windows Mobile] b16b:
i have the same problem here no sound when 2nd call incoming..
[Windows Mobile] da_reeseboy:
ankit360 posted the common over on ppcgeeks - http://forum.ppcgeeks.com/showpost.php?p=1172952&postcount=7957
[Windows Mobile] Nixeus:
Possibilty to having some screenshot of this 21855 build ? Thanks a lot :)
[Windows Mobile] krazy_about_technology:
BTW, Ankit360 also posts these builds on XDA too, for 96 DPI phones :) The thread is here :

http://xdaforums.com/showthread.php?t=551470
[Windows Mobile] + Que PPC:
Ankit or Zelalat's link???? 21855 is an old com so it must be a pure 6.5 without any modifications... why to get a screenshot.
[Windows Mobile] ther-amm:
WM6.5 21855 CE OS 5.2.3791 Sep 4 2009 21:07:09 for vga and qvga as always with added missing stuff.

http://rapidshare.com/files/281497957/WM65-21855-CE-OS-5-2-3791-LANG-0409-VGA-QVGA.7z

Thanks to Sun_Dream@DFT and ankit360 for the sys common.

Update: Link above has been updated with the correct qvga dpis. Below qvga dpis only.

http://rapidshare.com/files/281461380/21855-lang-0409-dpi-96-resh-240-resv-320.7z
[Windows Mobile] JoeTheFro:
Both of you may have the age ol issue of the system using the wrong sound file for "Call Waiting"

In the phones registry, go here:

HKEY_CURRENT_USER\ControlPanel\Sounds\CallWaiting

The entry for "Sound" should be set to:

callwait.wav

That should do it, i know it does for me!
[Windows Mobile] krazy_about_technology:
Well, the thread was started by Zelalat and he maintains the first post, but if you look at the thread itself, Ankit360 shares his found treasures in it :)
[Windows Mobile] Montecristo:
What is the one closer to the release candidate?

230XX

234XX

218XX

:eek::rolleyes::confused:
[Windows Mobile] da_reeseboy:
231xx?? Did I miss something?
[Windows Mobile] + Que PPC:
None.... :p

but if we use the common sense... the candidate must be... the com4 cause is the latest division on development... but if you were trying with us the releases for com3 you can think that this branch is the most stable with th enew improvements...

But a question jumps up.... wm6.5 candidate??? or WM6.5.1????

Firts Q!!! i think it could be 218XX

Second Q!!! Must be com4 they has at least 1 1/2 month to merge the stability of the com3 in the new branch com4 and polish all the visual errors.
[Windows Mobile] TAEL:
I guess one of 230XX (COM3) builds will be an official release. BTW, Oct 6 is near and all of us waiting... :)
[Windows Mobile] FormerPalmOS:
Did anyone find the solution for this? Should be a Lock icon but is instead a copy of the Windows icon. Could be a simple reference to the wrong icon in the code, or the icon itself is bad.

And NO this is NOT a duplicated or old MUI dll - I have already checked. I have only one file with the word shell in the filename in my OEM and EXT packages - shellcelog.dll. It's also not the provxml in the base_dpi folder - the syntax is valid. It must be something else.
[Windows Mobile] kidoucorp:
One question : Why, when building a rom, the total space on storage isn't the same ? For example on my diamond, the space vary from ~91 to 99Mb (or a little more sometime) (Total) :confused:

What depend on this ? I guess it's the number of modules, but I'm not sure about that :rolleyes:

I'm using NK for diamond, LZX, and I noticed it some time ago, also with roms made by others, so if someone knows... :)
[Windows Mobile] + Que PPC:
wich device... dpi and resh resv you have? wich build?
[Windows Mobile] JoeTheFro:
I use to get that issue too. It happened when i applied my custom theme. (Each new build seems to add more ability to customize more elements than the previous.)

With all newer builds of the OS, i have learned to just take the Classic Blue.tsk and modify it from there to use any custom elements as well as color scheme... when i am done, i rename it to what i want, upload to phone and Waa Laa...
[Windows Mobile] twopumpchump:
the grey softkeybar comes from an image defined in theme registry...

[HKEY_CURRENT_USER\Software\Microsoft\Today\SoftKeyBar]
"SoftKeyBarThemeImage"="\\Windows\\classicblue_softkeybar.png"

just change that image to one that you want :)
[Windows Mobile] JoeTheFro:
Ohhh, LOL.... haha i was telling a story and not asking for help... thanks though!!

Yah, the orig post guy was having an issue, and i was replying to help him... and mine sounds like i was in need of help... thanks for the response, but its all good!!
[Windows Mobile] amarullz:
New Showcase for New WM6.5.x was released :D

Showcase Suite 1.1.0

Showcase for New WM6.5.x BUILD 23045+

Enhancement your new Windows Mobile​

e-Natives Showcase Suite is Free Finger Friendly and Resource Friendly Task Manager With Professional Skinning and Easy to Use for New Build(s) of Windows Mobile 6.5.x (BUILD 23045+).

ShowcaseSuite replace Showcase_X function and implemented into new usage for new Windows Mobile User Interface.

What's New?

FOR MORE INFO & DOWNLOAD:

http://xdaforums.com/showpost.php?p=4030903&postcount=3​

. :D
[Windows Mobile] + Que PPC:
Thanks a lot amarullz lets donate to this guy... i will test it when i get home cause i forgot my f/(%n usb cable.... :p
[Windows Mobile] aussiebum:
Woohoo! All hail amarullz :D
[Windows Mobile] + Que PPC:
Had a question does we need to install the smartoolkit in this showcase suite too?
[Windows Mobile] amarullz:
you mean Showcase (not SmartToolkit) isn't it?? :D

Showcase Suite was Showcase + New WM6.5.x Enhancements :D

So, no need to install Showcase, because Showcase was included in Showcase Suite.
[Windows Mobile] + Que PPC:
mmmm i had the feeling before that the old showcase needs to works the help of the smartollkit jejeje my mistake... lets try your new baby amarullz you ROCK!!
[Windows Mobile] Rob_Storm:
Look in base_dpi_96_240_resv_400, the mxipcold_wpc_2.provxml file is missing something in one of the commands which prevents the default theme from loading. Look for: <parm name="ToolbarIconBubbleButtonSelectedThemeImageTopMargin" value="16 datatype="integer"/>

There is a " missing after the #16. This should fix the missing theme and the icon.
[Windows Mobile] herg62123:
try this

in this cab contains the phcanrc.dll file fixed so all dialer screens are corrected like it should

this is only for the tachi dialer vga sized only
[Windows Mobile] hasseye:
Thanks for this, however on my wm6.5 COM4 build using the tachi phonecanvas i try to install this cab., but get an unsuccessful installation. Saying something about its not digitally signed or something like that. Any solutions.
[Windows Mobile] blazingwolf:
New Showcase Task Manager working great on my WQVGA device. Moves Resco window to the correct position with a setting of 17 for the new task bar position. :D

Thank you amarullz.
[Windows Mobile] herg62123:
put your device in airplane mode and kill cprog.exe

once this is done install my cab and reset if it doesnt ask you to
[Windows Mobile] player911:
Thanks, I started to think my request fell on deaf ears.
[Windows Mobile] DomSim:
mind sharing what you actually did to fix the incall screen as not all phoncanvas versions are the same. also, is it possible to remove the text that now shows up with the iconon the left softkey?
[Windows Mobile] d_train:
Was a posted earlier in the thread...

http://xdaforums.com/showpost.php?p=4424416&postcount=2594

I did this on two different dialers and it worked for both of them - thanks Alexx~

DT
[Windows Mobile] player911:
Somewhere I missed where the softkey fonts had changed. I see pictures of different fonts (non-bold) which fits more text in. Looks better too IMO. Was it COM4 or what because my 23049 still has the original bolded font.
[Windows Mobile] Da_G:
23052 in a few hours..

Anyone interested in 21857? (using the "old" 6.5 interface) - I can stick that in post 1 as well (but it doubles the work so I don't want to use it unless there's at least some interest)

:)
[Windows Mobile] svprm:
Very Thanks Da_G for hard work.

Wating for new Vesion.

QVGA Soon.:)
[Windows Mobile] d_train:
Brilliant - will 96dpi also be available?

Thanks for all your hard work Da_G

DT

PS: any luck finding the latest MEGA/touch2 packages - esp. M2D 2.0.1918??
[Windows Mobile] da_reeseboy:
23052? Sweeeeet!!!

I have a few people that like com 2 still... sys & xip are all I need tho. But take your time - your efforts are greatly appreciated!
[Windows Mobile] jmckeejr:
My 23049 had the small font :confused: I had to add some reg to EXT to make it bold(It actually looks terrible IMO, needs antialiasing or something. Very pixelated). Maybe you have some reg somewhere?

Thanks Da_G, looks like I'll be busy this weekend. I vote no on 21857. I see no point in doubling the work for an already outdated build(unless there are some stability changes or something).
[Windows Mobile] silentP:
Da_G, I for one, would be interested in 21857. If you have the time, it would be great if you could post it. Thanks for your work.
[Windows Mobile] aphey:
thks，waiting for your new versions

only support your versions
[Windows Mobile] asdahd:
GOOD Work! what about the sms send problem?
[Windows Mobile] ther-amm:
Waiting for both of them. Thanks Da_G :)
[Windows Mobile] hasseye:
hey da_g i see your about to upload build 23052 which is pretty sweet, any chances you have a COM4 build? I'm using build 23412 that came out with a build date sometime last week, just wondering if you any chance have an updated COM4 build. One must be out there since the build date of 23049 came out after it and theres already another version.

Thanks for all you do regardless tho. :)
[Windows Mobile] Da_G:
At this time no COM4 build, the features from both should be merged again at some point soon though :)

Here's a teaser shot while I work:
[Windows Mobile] da_reeseboy:
SWEEEEET!!!! Are those default icons for the enlarged taskbar?
[Windows Mobile] JoeTheFro:
Nice screenshot..... here is one i just took of a minor glitch in solitaire... Looking forward to the new build, and i also hope they cut out the hijacking of the hardware buttons... i miss my PTT mapping...
[Windows Mobile] d_train:
Can I ask a stupid question - what is that additional toolbar for and how do you access it?

Looks fantastic by the way :)

DT
[Windows Mobile] da_reeseboy:
I think thats the enlarged taskbar that pops down when you click on the taskbar.
[Windows Mobile] hasseye:
da_g can you elborate a little on what you mean by at some point both builds should be merged together sometime???
[Windows Mobile] ams1576:
he means tht the changes from com3 would b brought in the com4 branch and we would get the best of both the worlds:cool:
[Windows Mobile] + Que PPC:
Mmmm the important thing here is... that the titlebar now can be shown on other screens not only in the today. :eek:

Edit: I think is not needed to be sarcastic...

Merge... jejejej the same that happends with the drag and drop... and pivot features huh?

so... again we gonna spec changes in the dll's :( hope the releases ends as betas not the 6th... tomorrow! jejeje
[Windows Mobile] Da_G:
23052 + 0409 all dpi up in first post, rest to follow shortly.
[Windows Mobile] d_train:
That would be why I probably don't see it, I have the notification enhancement from the MEGA installed and when I click on the topbar it opens that instead of showing that enlarged taskbar.

Anyone on QVGA devices having the issue with the memory page not showing correctly?? see attached image.

DT
[Windows Mobile] d_train:
You da man Da_G - thanks!!
[Windows Mobile] silentP:
Awesome, thanks man.
[Windows Mobile] watzone69:
Thanks Da_G.

Sleep is overrated anyway!:p
[Windows Mobile] JoeTheFro:
Da_G.... the link took me to some page that said "Dont Share this Link With Anyone"... good thing we all love eachother here... so i just snagged the real link for the DL...

Cant do much with the page since there is no login done... but it does add an extra step for the forum users that are use to click and go...
[Windows Mobile] yardi4life:
Thanks again.
[Windows Mobile] Da_G:
Whoops, thanks for the heads up JoeTheFro, it's fixed now :) I'm sure no one would have deleted anything even if they could though :)

All languages are done uploading, 23052 is complete.
[Windows Mobile] adwinp:
23414 will be up shortly by monkeybape:
[Windows Mobile] bga7x:
Thanks Brother!!!!!
[Windows Mobile] winderp:
21857 I want it because I still like the classical interface rom thank you very much！！！
[Windows Mobile] svprm:
Thanks Da_G.

I want MSXIPKernel for new SYS 23052.

Sorry,nob question.

Anyway to use previous build MSXIPKernel?

Request:

You uploaded SYS_Common and XIP in DPI192.

SO,DPI 96 User download both Common DPI and SYS_common with DPI192.

So,i request you to upload SYS_common separate.

If you don't like this request,Sorry.
[Windows Mobile] mike1986.:
but 21857 seems to be older tree than 23017 which was last build with old interface...
[Windows Mobile] drkfngthdragnlrd:
Actually, this is a Dialer issue. The alignment is based on the style/exstyle values already mentioned by Alexx a while back for the scroll bar issue. The text is because the dialer has textin a dll/mui somewhere for the softkey. You may be able to just delete those string resources to get rid of the unwanted text. The middle, Icon, I have no clue. As the dialer is not designed for these builds, all we can do is hack it best we can. I don't know what dll's/mui's you'd need to edit other than the phcanrc.dll(was it?!?!?).
[Windows Mobile] ams1576:
Thanx Bro:D:D:D
[Windows Mobile] Da_G:
@svprm:

I have included MSXIPKernel in the archive in first post.

@michal_banszel:

You are trying to compare the build numbers as indication of age, but this is not a correct thing to do :)
[Windows Mobile] indagroove:
I would like 21857 too please. I prefer the com2 tree builds myself.
[Windows Mobile] ams1576:
hey bro can we get patched shell32.exe?
[Windows Mobile] mike1986.:
Well, all I know that 21857 is 6.5.0.50 and 23017 is 6.5.0.60. If it's not the main thing to follow then I also want 21857 and looking forward for it :):):)
[Windows Mobile] svprm:
Thasnk Da_G for your hard work.

Request:http://xdaforums.com/showpost.php?p=4559029&postcount=4321
[Windows Mobile] Da_G:
uploaded patched shell32 in first post.

@svprm:

Due to the way things are laid out this would introduce further work to the process, I don't think it is worth the small savings in download time for that one file :)

@michal_banszel:

The underlying codebase can be determined by looking at the CE OS Version, the AKU (6.5.0.50/6.5.0.60) indicates the feature level of the build (.60 will have feature(s) that .50 did not)

So, there is some feature introduced in .60 that you will not find in the .50 build, but if you do not use this feature (I think it may be SEMC Bluetooth Watch support), no reason to want that AKU :)
[Windows Mobile] svprm:
No problem.

Thanks for uploaded patched shell32.
[Windows Mobile] Mars.C:
patched shell32.exe to avoid timebomb,

:) patched shell32.exe to avoid timebomb,

23052 shell32.exe