yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] + Que PPC:
You miss the lockscreenNONea or EA and the lockscreen in the sys... thats why you got the WM5 lockscreen

Thanks for the 21872 build monkeybape, Utaker, Alex and many more for sharing... so...

If com2 are where MS tooks stock roms for carriers where does this comes from i mean device... :confused:
[Windows Mobile] utak3r:
;)

look at the top of it:

<parm name="Skin" value="\Windows\Classic Blue.tsk" datatype="string"/>

Just change it to some theme not supporting graphic buttons ;)

Or... on a running system just apply such a theme.
[Windows Mobile] + Que PPC:
why the topic is now how to break the gui if the guis the newer and prettier since MS didnt change it since wm6
[Windows Mobile] Xannytech:
initflashfiles... :D
[Windows Mobile] + Que PPC:
how does the initflash can disable the lockscreen?? :rolleyes:
[Windows Mobile] Xannytech:
cause many people try to cook now... ;)

and if he doesn't have these lines in the initflashfiles he could have that issue ... it's clear enough? :cool:

;+++++++++++ Files for HTC Lockscreen ++++++++++++++++++++++++++++++++++++

Directory("\Windows\LockScreen"):-File("LS_LockScene_480x800.cpr","\Windows\htc_LS_LockScene_480x800.cpr")
Directory("\Windows\LockScreen"):-File("LS_LockScene_800x480.cpr","\Windows\htc_LS_LockScene_800x480.cpr")
Directory("\Windows\LockScreen"):-File("LS_PhoneCallScene_480x800.cpr","\Windows\htc_LS_PhoneCallScene_480x800.cpr")
Directory("\Windows\LockScreen"):-File("LS_PhoneCallScene_800x480.cpr","\Windows\htc_LS_PhoneCallScene_800x480.cpr")
Directory("\Windows\LockScreen"):-File("LS_SimplePinScene_480x800.cpr","\Windows\htc_LS_SimplePinScene_480x800.cpr")
Directory("\Windows\LockScreen"):-File("LS_SimplePinScene_800x480.cpr","\Windows\htc_LS_SimplePinScene_800x480.cpr")

;----------- Files for HTC Lockscreen -----------------------------------

:eek: now it works......!!! so it's not my sys!!! :D:D:D:D
[Windows Mobile] Emrulez:
How can i get this to be enabled?

"Enable"=dword:00000000

should I change it to?

"Enable"=dword:00000001

Thanx In advance
[Windows Mobile] Dr.Gonz0:
Minor issue

The 23081 that utak3r posted works awesome on my Wing, only downside is I am unable to change SIPs... I tried installing fingerkb from a cab and it installs and configures just fine but I am stuck with the basic keyboard, even using SIP Change doesn't allow me to switch. I also tried the fingerkb package posted on utak3r's 4shared and cooking it in but still no dice. Am I doing something wrong?
[Windows Mobile] RyanMogul:
Exactly.

Depending on what type of switch you are dealing with.

"Enable" = 0 (00000000) would mean disabled.

"Enable" = 1 (00000001) would mean enabled.

Now say it said "Disable" instead of "Enable" then...

"Disable" = 0 (00000000) would mean enabled.

"Disable" = 1 (00000001) would mean disabled.
[Windows Mobile] RyanMogul:
I remember reading something about that and I believe you press and hold on the keyboard icon for it to come up to switch.

Could always change the default SIP (input method) from Input options in settings.
[Windows Mobile] Dr.Gonz0:
hehe forgot to mention that I tried those as well, my bad
[Windows Mobile] mike1986.:
I don't have those entries and lockscreen is working :) Or maybe it's about this tapping first on the clock issue?
[Windows Mobile] Xannytech:
it depends also on your packets if you cook in, htc leo lockscreen, like the man who asked before could have that problem if you do not have that in you initflashfiles

Maybe one of your packages contains something like a .provxml that do the same thing that these strings do in initflashfiles...

But that issue is tipical.

as i wrote before ...thanks to ervius and other people providing kitchen almost ready, many are approaching to cook, and many are asking why their manila or other packages does not start... simply look the initiflashfiles if the ringtones, the wallpaper, the xml etc are not in the right directory it's normal ... :D
[Windows Mobile] mike1986.:
a...sorry. I didn't know it's something new :D I was sure you are talking about WM6.5.1 lockscreen so that's why I was so surprised. When you started talking about provxml then I was sure that there is some misunderstood :p btw where can I get this htc lock screen? and as I was reading before the stock wm6.5 lockscreen sys packages are necessary?

PS. I'm cooking since almost a year ;)
[Windows Mobile] Xannytech:
no no,sorry you misunderstood me, i'm not talking about you, i'm talking about strange issues like Barbapappa has...

The packages is htc leo Lockscreen... it's in the leo dump normally :D but if i remember well there is one also in the latest topaz or rodhium wm6.5 upgrade.

I started speaking about his problem... i know what he is using, so i know where is the problem... :)
[Windows Mobile] mike1986.:
ok, thanks. I will search for it and see if it's working better then stock wm6.5.1 lockscreen.

BTW as you mentioned before it's better to add it into provxml and put into htc lockscreen package because those entries would be useless if he will decide to make rom without htc lockscreen.
[Windows Mobile] utak3r:
awesome?... it's the best build I've seen in two years at least! It beats any wm6.1 build, that's for sure... It's super-fast and rock-stable. Man, I'm so excited...

Well, to use my package you should have both FingerKeyboard and SIPChange packages from my repositury. And... that's not all yet - my SIPChange depends on a small application called delayedExec.exe, go and search for it.

It works for me flawlessly, I've tried both FingerKeyboard and EzInput 2.1.
[Windows Mobile] benko286:
23075 build:

when i send device to suspend music also stopps playing??

registry above doesnent help!
[Windows Mobile] Dr.Gonz0:
Heck yea it's an awesome build!

Hmmm.... delayedExec... definitely gotta try that one when I get the chance. But I believe the issue is beyond that given that even installing the app fresh from a cab still don't let me use it at all. It installs, configures, but when I try to change it using various methods (SIP Change, Start>Settings>Personal>Input, or changing it by holding down the button and selecting it on the poop-up) still doesn't actually change the SIP to the finger keyboard.

If I cook a rom using a previous build (23071 using Ivan's SuperJustKitchen) I don't have this issue.

My next idea would be to manually install NETCF after cooking to see if maybe perhaps it's that.
[Windows Mobile] utak3r:
Do you use NetCF3.5? Or 2.0 provided?... Use only 3.5 (and not 3.7, which is not official release).
[Windows Mobile] barbapappa_86:
You where right there Xannytech :) I checked my initflashfiles and it pointed to the wrong crp files. Now everyting looks great. And yes, i use the latest 6.5 rhodium packages :D lol
[Windows Mobile] acidhax:
Anyone here having trouble 'RecModCommon'ing 21872 SYS/SHARED/COMMON?
[Windows Mobile] Dr.Gonz0:
I went with 3.5 since that's the official release from m$. In cooking I've tried every version available in the kitchen, 2.0, 2.5, 2.5 & 3.5 hybrid, 3.5 and 3.7, as well as the one packaged with the release. So this time around I cooked something up without any NetCF. Manually installed it, then manually installed that SIP I'm lightly obsessing over and I still get the same issue. So uh where to go from here???
[Windows Mobile] + Que PPC:
Mmmm why to install netCF 3.5 instead of the default in every build...??? it seems to be better the default than 3.5 and is not the buggy beta 3.7

Utak3r: why your fingerkey works fine and if i install another dont works??? and i had install the sipchange in all cases.
[Windows Mobile] Dr.Gonz0:
Yea, I normally use 3.5 and when the SIP didn't take I figured "try something else" now I'm just out of ideas
[Windows Mobile] Xannytech:
happy to help you good cooking!
[Windows Mobile] player911:
This is because HTC WM6.5 builds are starting to put the lockscreen files in a folder within Windows. There is a registry key that redirects Windows to look for the lockscreen files in this folder.

If you just cook in the stock Lockscreen files in the \Windows folder (like they normally are)... it won't find them because the registry is now pointed to \Windows\Lockscreen.

Delete the registry entry from one of the RGU files... or just cook in your own redirect that points it back to Windows. I pulled that crap out of my initflashfiles.dat and deleted that reg entry in the OEM .rgu file. This way I can cook my new SYS builds like normal and have the lockscreen cpr files in the Windows Directory like we originally had them.

If you don't have all the connection correct (using the \Windows\lockscreen folder or the default \Windows location) you'll be presented with the old lockscreen.
[Windows Mobile] player911:
You will be unable to switch SIP keyboard using EzInput when using the stock WM Sip menu. All that is displayed is "EzInput". When I used my Fuze, I had this issue. Even newer HTC builds don't have it working.

The only way you can get it working is by using a biotouch.dll that turns the SIP menu into one of the HTC menu kind. Only the HTC Sip menu will allow you to change your SIP Keyboard.

Myself and others have actually started using a Manual SIP changer app that will open this "HTC Sip Menu" and allow you to switch... but you have to run the app to do it. You can't do it on the fly.

I've created a thread about this already in the Dev forums where I've been dissecting a few of the EzInput packages and was getting pretty far when I had my Fuze replaced with a Pure.

Even my Pure (topaz), running WM6.5.1... the SIP menu is one of HTC's designs. If I disable this menu... all I get is "EzInput". I really wanted to get a stock SIP menu that would work but eventually stopped working on it since the HTC SIP menu works.
[Windows Mobile] Dr.Gonz0:
Just so I've got this straight... I would need to use "EzInput" and HTC Sip Menu to allow me to switch. So the issue is with the stock SIP and it's friends. It makes perfect sense... So I would need to head over to the dev forums to get edumicated on biotouch and friends...

Thanks for the info!
[Windows Mobile] Rim1Flex:
If anyone who knows wm 6.5/6.5.1 really well and wants to make a rom for samsung i760. These people are welling to pay lots of $$$$$
[Windows Mobile] hideto1128:
Can anyone please share 23502(or 23081)&21872 for Bepe's kitchen(Old Style)?

I tried many times to port it and failed alsoT_T

It's too hard work to me.....
[Windows Mobile] dreamtheater39:
I have a really weird bug....in my network adapter settings.....i cant enter 3 digit numbers for my IP address. So, 192.168.1.1 is not possible...as i'm able to only input 19.16.1.1 :(

Any idea what could be wrong?

thanks!
[Windows Mobile] programatix:
If everything is set up properly, you can try this little app. What it does is to change a registry value and the HTC Sip Menu will be shown.

Someone has this problem before and if I'm not mistaken, you can actually enter all 3 digits but you can only see the first 2 digits. Might be font size or resource problem?
[Windows Mobile] md_bluelily:
I have this problem from the early builds of WM6.5.

It refuses to accept the third digit.

There is no problem with font size or any resources. The control that they are using for IP Address has some bugs in it.

Best Wishes.
[Windows Mobile] uhery:
bug digits in wifi settings

yes some bugs in it! ... but if you want to solve in someway you can make a provxml file like this ... but using your own values:

<wap-provisioningdoc>
<characteristic type="CM_WiFiEntries">
<characteristic type="My_SSID"> (do not change this value and delete this comment)
<parm name="DestID" value="{A1182988-0D73-439e-87AD-2A5B369F808B}"/>
</characteristic>
</characteristic>

<characteristic type="Wi-Fi">
<characteristic type="access-point">
<characteristic type="YourSSID to insert">
<parm name="DestId" value="{A1182988-0D73-439e-87AD-2A5B369F808B}"/>
<parm name="Encryption" value="0"/>
<parm name="Authentication" value="0"/>
<parm name="hidden" value="1"/>
<parm name="KeyProvided" value="0"/>
<parm name="NetworkKey" value="yourPWD to insert"/>
<parm name="KeyIndex" value="1"/>
<parm name="Use8021x" value="0"/>
</characteristic>
</characteristic>
</characteristic>

<characteristic type="Registry">
<characteristic type="HKLM\Comm\TIACXWLN1\Parms\TCPIP">
<parm name="EnableDHCP" value="0" datatype="integer"/>
<parm name="AutoCfg" value="1" datatype="integer"/>
<parm name="WINS" value="" datatype="multiplestring"/>
<parm name="DNS" value="Your one" datatype="multiplestring"/>
<parm name="DefaultGateway" value="Your one" datatype="multiplestring"/>
<parm name="Subnetmask" value="Your one" datatype="multiplestring"/>
<parm name="IpAddress" value="Your one" datatype="multiplestring"/>
</characteristic>
</characteristic>

</wap-provisioningdoc>

you also can make a cab file .... put it in your rom/device ... the wifi works even if you can read only two digits! ... I use it! :)

provxml code from : xda 3d
[Windows Mobile] bajok!:
...xtract and copy the attachment using Resco Explorer or Total Commander to your \windows directory to overwrite the existing file, then soft reset... you can now input 3 digits...cheers!:)

BTW: if you want to include this to your kitchen, copy the file to SHARED\0409\Base_Lang_0409... but delete first the module before you copy...
[Windows Mobile] Emrulez:
I have this weird problem at the moment.

I cant get my WWE rom to work.

My NLD rom works fine. Same as build 23071 in WWE.

The problem is that the NLD version boots fine WWE only has a white screen and text no images.

What I tried, using an unedited initflashfiles.dat.

I already have recmodded stuff.

NLD has 0 in slot 0 264 in slot1 WWE has 0 in slot 0 and 265 in slot 1 thats the only difference.

What else can I do?
[Windows Mobile] citysu:
骚猴 怎么不见更新了os了啊 喜欢你的资源 加油 祝你天天发布最新资源 哈哈

MOD EDIT: THIS IS EN ENGLISH FORUM PLEASE ADD TRANSLATION
[Windows Mobile] AndrewSh:
Generally speaking it's only QVGA problem. For the future:

1. Recmode tshres.dll.0XXX.mui

2. Open it with Restorator

3. Find Dialog 12044

4. Edit field length (default 64 - make minimum 70). Do that for all three fields (IP address, Subnet mask and Default Gateway)

5. Save mui and reversmode it back. That's it.
[Windows Mobile] Amir167:
23081 and can not find 480 800???
[Windows Mobile] DeadOne:
Microsoft best be joking.
[Windows Mobile] silentP:
Seriously? This has to be another false alarm. Someone sending out false notices again.
[Windows Mobile] RyanMogul:
Hate to tell them (Microsoft). Everyone and their immediate friends and family already have all of their new buggy builds. And once they are uploaded onto the internet there is no stopping it.. They shouldnt even of released such untested junk to begin with. But thats neither here nor there.. Maybe thats why they are so upset. Because those builds arent included on any New Phones yet. They are still using COM2 and earlier because those builds are official releases on some New Phones. These new COM3, 4, and 5 builds are most likely still in Beta Testing and someone is leaking them early..

I dont use these new builds because I am aware of the problems they have.

http://xdaforums.com/showpost.php?p=4747451&postcount=319
[Windows Mobile] agh1701:
It looks fake. I wonder if it was sent from a microsoft domain?
[Windows Mobile] spikegotti:
i agree, i thought the smart thing to do was to release a finished product then release updates after, even tho i use 6.5, there are still too many bugs in the builds, these leaked builds including the builds on the new 6.5 devices certainly aint a finished product...maybe M$ will release a finished WM when apple responds to windows mobile in terms of hardware and multitasking
[Windows Mobile] secc123:
Re: MS
[Windows Mobile] acidhax:
These builds are just taken from QA. AKA the successful builds that pass certain testing. These are BUILDS, not releases.
[Windows Mobile] + Que PPC:
:rolleyes: AGAIN???? OMG!!! this is getting old... c'mon Flar why not to investigate first the source... then publish it...?

Any kindly guy that discover the source?

Post 5 and some more in the thead has builds... this is (stupid)
[Windows Mobile] makeveral:
it must be a fake like always!
[Windows Mobile] silentP:
Ok guys, I've screwed up somewhere and can't figure out where. I'm currently running 21872, works great. But I have this one issue. See pics below. My message screen is missing the "send' option. I have to tap the far bottom-left corner to send my messages. What package did I screw up? I hoped switching builds would help, but it's obviously in my EXT. But I don't recall adding/switching anything. Anyone with an answer? Thanks guys, for everything you do.
[Windows Mobile] CRACING:
Looks like its normal mode, change it to threaded mode. But not sure though :D
[Windows Mobile] burtcom:
Nope -- the links in post 5 go to non-working Rapidshare pages -- they got to rapidshare too :(
[Windows Mobile] biscuits1978:
This same notice with the exact same verbiage has been sent to other people that had in no way violated any copyright.

Here's the thing -- these words:

This is implying XDA is hosting these files for download, when in fact it is linking to another site that is hosting these files. If anything, the douchebag that sent this notice should have sent it to the file hosting provider.

The same thing happened to this group that was talking about Windows 7 beta, and lo-and-behold its the same takedown notice with the same lame verbiage.

http://www.cultofmac.com/microsoft-...-takedown-notice-for-a-link-to-windows-7-beta
[Windows Mobile] WoZZeR999:
"Offending" forums posts give me 404 not found now.
[Windows Mobile] XirXes:
Are we still going to get new builds here or did MS ruin our fun? I really like the COM3 builds and I would be very upset if I couldn't update.
[Windows Mobile] AndrewSh:
Dunno who the hell sent the note to xda - they removed the name from the note but if it's the same smart ass as that one who sent the note to cultofmac.com - he is Lithuanian guy

Petras Sigitas Vyšniauskas - the lawyer from Vilnius....

his number +370 5 2622720 - who wants to call? :)

other info about the guy
[Windows Mobile] daguerrotipo:
Hi

how can I "repair" this?

Thanks
[Windows Mobile] dreamtheater39:
I cant believe MS can be so shortsighted. This was what kept the WinMo community active and going. We all love WinMo because our devices are moddable beyond recognition unlike all other OS-based devices out there. Throwing the towel on this will only kill the community and make things worse for MS. They sure dont want people switching to Android, do they?

bah....feels terrible, sucks. Please take this back MS....for everyones good
[Windows Mobile] dijor69:
WOW, if MS would have to be grateful, we investigate and remove the bugs and faults that tend to have them in SYS, except that each of us have acquired a license with our WM devices whether or not other versions, and the reason an attempt is made to research and develop on this platform is none other than the need for software that we sell work properly and had no faults with which we sell as final versions.

In short, this is still one more time the suspicion of a company that is increasingly declining.

THANKS XDA FOR YOUR PLATAFORM AND WORKS
[Windows Mobile] silentP:
After a few days when it's a proven hoax, yes, they'll come back. They seem to target XDA every 4-6 months since the builds for 6.5 began to leak.
[Windows Mobile] silentP:
You have to remember, this is most likely another hoax, not by MS. Flar and the other admins are just covering their a$$es just in case this is the real deal. By the verbage and the places it was sent, this is a shotgun hoax. Look how many places were hit. Even those who had nothing to do with it. Give it a few days and everything will be back to normal.
[Windows Mobile] barbapappa_86:
What i have read previus in this thred, theres no fix for that. Its a "grafic bug"

What did you do to not get scrolling in youre phone canvas btw? :)
[Windows Mobile] WoZZeR999:
Even IF it is real, it's probably not from MS anyway. It would most likely be from some company that MS hired to find windows "warez". They see a download link to Windows, and assume that it's a pirated copy for people to download. The end even says "internet investigator", and he probably get's a fee for finding "offending" sites that offer pirated MS products .
[Windows Mobile] daguerrotipo:
Hi

In this theard the are a manual for fix the scroll I made a lot of time ago ....but i don't remembar how it was... was editin a file with restorator.

Byes
[Windows Mobile] acidhax:
Well, let's see.

No request to pull the 6.1 rom's down as well?

If they know how to use forums to find the 6.5 rom's, then they know fully well that 6.1 is right here too.

hoax.
[Windows Mobile] + Que PPC:
So...... Shut up!!!!!!

More vacations people!!!! is true they comes and take it down in a repetitive period of days... lets wait...

mmmm 6.1 is not windows property... is carrier's property so... lets wait for at&t orange dopod and some more to come and bann them.
[Windows Mobile] Farmer Ted:
The letter was probably sent by Da_G, anyway, just to try to stem all the "When are you going to upload the next build for me!!!" pm's that he gets. He needs a vacation.
[Windows Mobile] acidhax:
Not well versed in Software copyrights, are we? :P
[Windows Mobile] abusalza:
as far as i know since an old era, g'reloc wouldn't work for resource modules, mui modules, and executable modules. but i don't know about cpl modules if it's realoc during cooking progres.

so if you care for slot 0 just recmod for modules like htmlview.dll etc (sorry i don't know what we called this type lol)

please correct me if i'm wrong...
[Windows Mobile] vagal_br:
I am Brazilian and I am using a ROM WM 6.5 build 23025 in English on my omnia, I would move to Brazilian Portuguese. I do not understand how it does. Could someone help me?
[Windows Mobile] megapinky:
help!!

i have this erros? i need to install a diferent net cf? which one? help please
[Windows Mobile] Da_G:
23028:

http://rapidshare.com/files/2671669...-4075-LANG-0409-DPI-192-RESH-480-RESV-640.rar

Note that this build is timebombed! You must remove the timebomb from shell32, following the SOP.

For your convenience, i've attached a patched shell32.exe :)

A few more things are renamed from Pocket PC to Windows Phone, among other changes in this build. The "Enlarge Titlebar" function looks a heck of alot nicer in this build :)

Ooh, fancy compositing effects! :)

@ Abusalza:

If I recall correctly, the VM handler automatically remaps modules assigned to slot 0 that are resource only to slot 63 "on the fly" - the only specific allocations required are slot 60/61/1/0
[Windows Mobile] Cal-El:
Thank you soooooo much, I am all over this, I will let you know what I find out! :)
[Windows Mobile] + Que PPC:
So the other ress user (as me) use the 23025 dpi and lang?

The timebomb isnt disabled by default with ervius VK?

Thanks for sharing Da_G

If both question's ask is YES i will try it!!!! hahaha thanks a lot man!
[Windows Mobile] the.decoy:
No, you just need to copy all of the BaseApps\GAC_****_v1_0_0_0_cneutral_1.dll files from 23022 (under SYS-SHARED-COMMON) and use them to replace those that are in 23025.

They are corrupt or something (and have been since 23024) ... not sure if 23028 ones are fixed.

You can also copy these files into the Windows dir on your running rom but use TotalCommander and do a soft reset straight after.
[Windows Mobile] Da_G:
@+ Que PPC:

Yes, Ervius VK will automatically patch the timebomb. However not everyone uses it, so I have also provided it for them :)

For other langs.. same as before.. if u have a problem tell me and I will try and get them out. It's alot of work to do every time, if its not needed :)
[Windows Mobile] + Que PPC:
Yup i knew it, thats why im asking, you know the change of 23022 to updated 23025... hehehe, thanks man...! ;)
[Windows Mobile] Cal-El:
Does anyone know where to find the files and resources for the titlebar? :)

BTW this build is very nice, thanks G!
[Windows Mobile] Da_G:
I only checked briefly, but I think the resources are in shellres.%dpi%.dll

:)

Checked closer, yes, in RCDATA section, stored as .png with transparency mask, very nice resource for modding the UI :)

all dpi 0409 posted in first post