yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] boggsie:
Tael, if you want to update the OP, you can find working links over at the mobileunderground thread, here:

http://www.mobileunderground.info/showthread.php?t=444

Latest builds:

216xx - HTC

21685_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409_FROM_DFT (39.57MB) Windows CE: 5.2 Build 3597 (Thursday, September 16, 2010 3:43:53 PM)

218xx - COM2, continuing dev of 6.5.0.50

21916_XIP.BIN_MSXIPKernel_SYS_QVGA_VGA_WVGA_0409_FROM_DFT Windows CE: 5.2 Build 3833 (Friday, August 06, 2010 4:49:39 PM)

22xxx - SEMC Sony Ericsson

22047_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409_FROM_DFT Windows CE: 5.2 Build 4921 (Sunday, September 26, 2010 5:16:11 PM)

230xx - COM3, continuing development

23149_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409_FROM_DFT Windows CE: 5.2 Build 4173 (Thursday, September 23, 2010 3:54:05 PM)

235xx - COM5, presumed abandoned

23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409.7z (35.39MB) Windows CE: 5.2 Build 4536 (Tuesday, April 27, 2010 3:55:46 PM)

236xx - LG Electronics

23699_XIP.BIN_MSXIPKernel_SYS_QVGA_HVGA_VGA_WVGA_0409_FROM_DFT Windows CE: 5.2 Build 4600 (Thursday, November 04, 2010 3:44:02 PM)

24xxx - Possibly additional HTC Branch

24635_MSXIPKernel_SYS_QVGA_WQV_FROM_DFT Windows CE: 5.2 Build 5421 (Sunday, August 15, 2010 3:45:25 PM)

25xxx - Possibly additional SEMC Branch

25028_XIP.BIN_MSXIPKernel_SYS_QVGA_HVGA_VGA_WVGA_0 409_FROM_DFT Windows CE: 5.2 Build 5919 (Sunday, August 15, 2010 3:44:21 PM)

282xx - WMD

28244_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409_FROM_DFT Windows CE: 5.2 Build 5224 (Sunday, October 24, 2010 3:57:09 PM)

29xxx - Unknown

29002_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409_FROM_DFT Windows CE: 5.2 Build 6202 (Tuesday, August 17, 2010 4:35:34 PM)

Best regards,

-boggsie
[Windows Mobile] crazyC:
Just cooked with 21685.

Normally when I sync over the air with our exchange server it takes 3 or 4 attempts to get all the contacts, but I only know this because some of my favourites are missing at first.

This time there was the same behaviour but ActiveSync listed and error (requires attention) each time, and individually listed the contacts that had not synced. Never seen that before.

Maybe there have been changes to Activesync now - not sure. Its a fresh flash so I will see what else shows up.
[Windows Mobile] mark-m:
Errors in 21685

I also cooked with 21685.

I Sync with USB-Cable. First try i get an error.

Second try run's.

Then i have an error by my contacts.

The sign plus (+) before my numbers is gone, but only by the first entry (Mobile).

49 172 xxxxxxxx instead of +49 172 xxxxxx.

Provider say's number isn't avaiable.

Every one else have the same error ?

Mark.....
[Windows Mobile] NRGZ28:
21685 is a piece of crap, IMO. All sorts of errors on my device here.. took it off after a few hours.
[Windows Mobile] mwalt2:
Yeah, same for me with 21685. Contacts do not fully sync. I guess I won't leave it on the phone long enough to find out much else though.
[Windows Mobile] crazyC:
Yes - I have serious contacts issues as well.

Reverting back to 21683 - dissappointed.
[Windows Mobile] HD2Owner:
that's exactly the reason why i try to avoid experimental branches...

they can be very fast.... but as you can see, can cause issues too.

i hope that htc is trying to add new sync features like backup sms...
[Windows Mobile] crazyC:
21683 has been pretty solid for me I have to say.

I dabbled with 21684 but think I had some issues I could not pin down and was not sure if it was the build or something I installed but had to drop back to something stable as I needed it to work for a few days. Everyone seemed to then be saying that 21683 was better so I didn't bother with 21684 again.

Just thought I would try 21685 after seeing Boggsie's comment (I think it was his reference in passing to it)
[Windows Mobile] boggsie:
I've been running 21685 for a bit and I am a bit embarassed to say that I haven't had a single issue. It's the best build I've run in the past two months.

I can't account for my different experience, but I have my full kitchen (a continuation of work started by indagroove) posted at DFT and mobileunderground, but it is for CDMA devices, only.

Best regards,

-boggsie
[Windows Mobile] crazyC:
Do you sync with an exchange server ? That was really all I got to try. I had odd messages as I posted earlier but simply could nopt get it to bring over all my contacts. After trying that for a bit I read the other negative comments and reverted back to 21683.

Have you noticed any other changes in 21685?
[Windows Mobile] boggsie:
I do sync, but over the air with google mail and Windows Live mail, both set to "as items arrive". Obviously the google mail backend is not a "real" exchange server and I'm not exactly certain what comprises the mail backend of Windows Live. I sync my calendar events and contacts (>300) from gmail.

I can't give you the comparison that makes sense, because I did not go from 21683/4 to 21685. Immediately prior to 21685, I had been running 23149 and immediately before that, 29002. Everything else in my kitchen is exactly the same except for the SYS/XIP builds and my biggest impression with 21685 is increased speed and battery life. 21685 also seems more stable with SENSE (2019) ... on 23149, sense would sporadically restart for me at least twice per day and that hasn't happend to me once since I flashed 21685.

Best regards,

-boggsie
[Windows Mobile] mwalt2:
Mail syncs fine for me, but contacts fail using MS Outlook and activesync and also with MS MyPhone. Are you using PIMBackup or some other way to restore contacts? Texts I receive do not show the correct contact either, even if the contact is added.
[Windows Mobile] boggsie:
All my contact, calendar and email information is synchronized (restored) via activesync, either to google mail microsoft live mail. I do not perform any other type of backup/restore activity. I haven't experienced the issue you mentioned with text messages, either. I wish I could offer some help or advice other than to simply respond that it works for me.

You are USA / Michigan and I am in Ohio (some game last week, eh? :p ) so I presume you are SPCS or VZW, which means CDMA. Just for the sake of comparison, if you are at all interested, you can go to the kitchen thread over at mobileunderground and download the kitchen, or if you like, I'll post the ROM I am running now and you can try it ... as part of the process to narrow down where the issue might reside.

Best regards,

-boggsie
[Windows Mobile] AndrewSh:
I'm on 21685 for more than a week for now - already made three roms in different configurations - absolutely zero issues and my device is very stable and fast....

Guys would you be so kind to define the Outlook versions on your computers?

Actually I don't have any issues syncing the contacts on my Leo TMOUS (21685) with Outlook 2007, but already two guys on Russian forums complained that they fail to sync contacts containing birthday.

Also please try to remove birthday from the problem contact and sync again and define the Outlook version on your computers.

I will try to figure out the issue....

Thanx in advance for feedbacks.
[Windows Mobile] cajunflavoredbob:
I haven't had any problems. I'm kind of like boggsie here. I like the speed of 21685. I've had it in my personal ROM for a few days with no issues. I use Google for my exchange server, and I sync on my PC with Thunderbird/BirdieSync on Windows 7 Professional x64.
[Windows Mobile] mwalt2:
I'm using Outlook 2007 as well. I think you are right about the birthdays. I think the ones that did not sync did contain birthdays. I've moved on to 23149 at the moment, so I can't test further.
[Windows Mobile] ::indie:::
Same for me,

I made 16 roms with 21685 and for 3 days now my device is very stable and very fast...

The only problem I found with 216xx builds is that they connect to GPRS internet without reason (this is confirmed from many users)

With the 236xx builds and exactly the same kitchen I do not have this problem,

GPRS internet do not connect without a reason.

Anyone knows why and is there a fix for this?
[Windows Mobile] crazyC:
I am syncing with Exchnage Server 2003 I think - it is my office server and I do not sync locally.

As I do not have the rom on my phone anymore, I cannnot be certain, but:

A number of those it would not sync did have birthday, but I am sure some did not (ie favourite chinese restaurant!)

A couple of my favourites did sync, but did not show up in the people tab of sense. The HTC added in info was there in the contact.
[Windows Mobile] Nehomar_C:
Greetings friends sorry but anyone could help coseguir for my language languages 0C0A the latest build? and I have the 236xx and 280xx but I like to cook with other COM! Thanks and sorry if this was not to post it here! Greetings from Venezuela
[Windows Mobile] AndrewSh:
Those guys who have problems with sync on 21685 -

try to use pimstore.dll (BaseApps) from 21684

please leave feedbacks
[Windows Mobile] crazyC:
OK - Cannot remember if I used pimstore from 21683 or 21684 but it appears to have resolved my initial contacts issue.

Cannot feed back any more yet as only just flashed.

EDIT : Just made a call and had to soft reset as phone unresponsive at end of call (screen remained blank and buttons did nothing)
[Windows Mobile] boggsie:
Hey there, AndrewSH; thanks for the tip and let us know how those of us from north America who are inclined would go about donating to (PayPal?)AsusMobile.ru? Do you, Alex~~ or Barin have a PayPal address that goes to support the site?

Best regards,

-boggsie
[Windows Mobile] utak3r:
Aren't we expected to replace pimstore.dll in all current builds? Just like tpcutil.dll and cprog.exe? That's the first thing I always do to the new build...
[Windows Mobile] crazyC:
Really?? - this is the first time I have had to replace pimstore.dll. - I dont replace the others either. Whats the advantage?
[Windows Mobile] boggsie:
29003 up over at mobile underground

http://www.mobileunderground.info/showthread.php?t=444

**Thanks to the good people of the community like Da_G (XDA), Conflipper (conflipper.com),

Tom Codon (HTC Pedia), MWang and Boomer (DarkForcesTeam) for the leaked builds,

AndrewSH (AsusMobile) for downloading, extracting and repackaging.**

Best regards,

-boggsie
[Windows Mobile] mwalt2:
Incoming caller ID picture works with HTC dialers (I believe that's why people do it). Personally, I don't like replacing modules from another build, so I just use a different dialer like PhonEx and amarullz's 'no_htc_phonecanvas' hack to get it to interface with sense. Maybe that's why 21685 worked well for some and not others...
[Windows Mobile] crazyC:
OK - everything works fine for me using the Huashan dialer on the builds I use so I dont have to solve the problem I guess.

Cheers
[Windows Mobile] OndraSter:
Huashan has strange issues on HD2, so we have to use the stock one... and hope for 6.5.3 update for HD2 from HTC meanwhile.
[Windows Mobile] animelover:
WM6.5 is pretty dead now since WP7 and Android will be at higher priority for HTC, I think! So there will be never an official nor unofficial patch/update for the Huashan dialer to get it working on our HD2! :-/
[Windows Mobile] crazyC:
See this is what I would have thought, but then there are this stream of constantly updated builds that keep appearing - why? Presumably for those markets that WP7 does not cater to yet? But surely there is hope for the HD2 at least there?
[Windows Mobile] boggsie:
23150 up over at mobile underground

23150_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_040 9_FROM_DFT (39.82MB) Windows CE: 5.2.23150.5312 Build 4174 (Thursday, November 18, 2010 4:52:47 PM)

http://www.mobileunderground.info/showthread.php?t=444

Best regards,

-boggsie

**Thanks to the good people of the community like Da_G (XDA), Conflipper (conflipper.com),

Tom Codon (HTC Pedia), MWang and Boomer (DarkForcesTeam) for the leaked builds,

AndrewSH (AsusMobile) for downloading, extracting and repackaging.**​
[Windows Mobile] sharkie405:
Nevermind :)
[Windows Mobile] krazy_about_technology:
Hmm.. AKU number changed again in 23150... But what really suspicious is that build date has jumped from September to November in just one build. Anybody tried it yet??
[Windows Mobile] AndrewSh:
Windows® Embedded Handheld :)
[Windows Mobile] boggsie:
If you look at the office.dll in 23149 (hex 0x000006ee) you can see the date of the build is November 3, 2010, but for some reason, the DSM wasn't updated to reflect that date. If you do the same for 23150, you see November 18, 2010.

So, one of two things has occured: The original source had updated the DSM to reflect the true date of the build or, sometime after the build was leaked, the DSM was updated to reflect the true date of the build. Either way, 23149 and 23150 were both built in the early and middle part of Noember, 2010.

Best regards,

-boggsie
[Windows Mobile] krazy_about_technology:
@Andrew : :)

@boggsie: Hmm. could be. What i am really concerned about right now is that how is it in terms of speed compared to 23148. I am currently using 23699, switched over from 23148 because of its pathetic speed.

Anyways, downloading it now. lets see.

@everyone : guys if one of you test this before me, please let me know here. I specially want to know about speed and responsiveness, specially on an Omnia II.
[Windows Mobile] pkoper:
I might be wrong here, but the question may be who updates the builds constantly.

It just does not make sense to invest on development into a product you are not going to sell.
[Windows Mobile] CRACING:
Cooked ROM with build 23150 and bench marked but haven't got so nice results as 21685 nor as 28244.

Check my spread sheet report here.

I think I will stay with 21685. :)

Thanks...

Best Regards

Edit; The ROM I had cooked was using Dynamic Page Pool which I wasn't noticed and the BM report went wrong. I have updated and posted BM reports of Default Page Pool based ROM. Check my post here

The above statement is wrong. 23150 is faster then others. :)
[Windows Mobile] boggsie:
I can't say how much I appreciate the effort you put into these benchmarks. There is nothing like objective benchmarks, when attempting to compare one OS/SYS/XIP build to another.

Looking at these facts really forces to question my perceptions! :D

Best regards,

-boggsie
[Windows Mobile] light_n_roses:
for my experience as for now the best build that I have ever tried is the 21681 ...very stable and fast and it's 6.5.X
[Windows Mobile] AndrewSh:
krazy, buddy, I'm not really kidding! :)

Changes in langs: shellres.dll.0409.mui & shellresapps.dll.0409.mui

lines added in shellres.dll.0409.mui:

14696, "Windows® Embedded Handheld 6.5 Professional\0x00"

14697, "Windows® Embedded Handheld 6.5 Classic\0x00"

shellresapps.dll.0409.mui

RCML_DLGDATA - added 11090.res

Dialogue - added 11090.rc

CRACING, I told you - it's useless. Benchmarking works good as internal private thing - the main constant is YOUR device and YOUR way of cooking rom. Too many factors that are valid only for you - not for the others.... To tell the truth - I forbade publishing benchmarks at the builds developer topic at asusmobile.ru - because it's like a **** measuring between bears and dogs.... :)
[Windows Mobile] Tribulattifather:
Will you do a test between 21685 (WM6.5.3) and 23563 (WM6.5.5). Both seem fast and the most stable i.m.o. I'd like to see how one does against the other.

Thank you very much in advance,

Cheers.
[Windows Mobile] mudhi:
I had experienced build 23150, 2314x, 2369x drains battery twice or thrice faster than 28244, for HD2 ROM, as fast as 1% per minute, when using 3G, the battery even drops 2% per minute.

Anyone had this experience?
[Windows Mobile] CRACING:
Thanks. Its just some craze for me to do benchmarks. ;)

Best Regards

Sure, I would be glad to do that but may be tomorrow.

Today I'm very busy releasing ROM for Topaz. :)

Thanks...

Best Regards
[Windows Mobile] fubo73:
Hmmm, so what about other languages? We don't have for other than 0409, right? Could we still use rollups from 23139?
[Windows Mobile] Tribulattifather:
I am very much looking forward to your testing. Thank you very very much ^>^

I don't have the time as well right now to do anything like that; Christmas craziness has begun here, lol.
[Windows Mobile] boggsie:
**Thanks to the good people of the community like Da_G (XDA), Conflipper (conflipper.com),

Tom Codon (HTC Pedia), MWang and Boomer (DarkForcesTeam) for the leaked builds,

AndrewSH (AsusMobile) for downloading, extracting and repackaging.**​

21686 up over at mobile underground (thanks indagroove)

http://www.mobileunderground.info/showthread.php?t=444

Best regards,

-boggsie
[Windows Mobile] CRACING:
You're welcome. I know how ppl will be busy in Christmas days.

Have fun, Merry Christmas. :)

Thanks...

Best Regards

Thanks for sharing. :)

It was my bad that the benchmark I took was mistake. Not the benchmark but the ROMs I had cooked was using Dynamic Page Pool so the benchmark wasn't right.

Later I came to know the mistake. Re cooked with default page pool and taken benchmark.

Now I would say 23150 is truly fast compared to other builds (Atleast in benchmark reports). Both on HD2 and Topaz. :)

My Topaz ROM :

https://spreadsheets.google.com/ccc...BdUYwU1k3cTFpb2c&hl=en&authkey=CPGwjawD#gid=0

My HD2 ROM :

https://spreadsheets.google.com/ccc?key=0AqXPpi2-Pn0PdC0zUTI4eERsQ3ZUcU9BQk5lVWtxcXc&hl=en#gid=2

Thanks...

Best Regards
[Windows Mobile] AndrewSh:
Hmmm, I pointed on changes. So what about other languages? Are you able to add new lines to your native shellres.dll.XXXX.mui and shellresapps.dll.XXXX.mui by yourself? Or anyone should do that for you?

It's a matter of 5 minutes and it's not necessary to translate the expression Windows® Embedded Handheld 6.5 Professional to your native tongue.
[Windows Mobile] fubo73:
I can change the mui as well. But are the changes you pointed the only ones over the language package?

Regards.

EDIT: I can't find 14696 and 14697 in shellres.0409
[Windows Mobile] AndrewSh:
Yes. Only shellres.dll.0409.mui & shellresapps.dll.0409.mui
[Windows Mobile] fubo73:
I use resource hacker to change them. I can't export-and-import 11090 in shellresapps as binary. What am I doing wrong?

About shellres, I can't find the resource in the mui in package posted in this thread...
[Windows Mobile] AndrewSh:
Have no idea 'bout rez hacker - I use Restorator. Normally I open two dlls (mui), copy resource in one file and paste it to target file

What should I answer? Sorry for you.... I pointed to the line numbers in English string:

14696	Windows® Embedded Handheld 6.5 Professional

14697	Windows® Embedded Handheld 6.5 Classic

Pretty easy to find.

About - what is posted here - I did not check the link - but I am sure - it's a proper link. Besides - you can look for alternative links at asusmobile.ru

And... :) I hope we are talking 'bout 23150 - not 21686? :)
[Windows Mobile] fubo73:
Thanks AndrewSh. I downloaded the 23150 with uncorrect file name, 23149_... The shellres.dll.0409.mui does not have any 14696 or 14697 inside. Could you share yours?
[Windows Mobile] AndrewSh:
Sure. I also left recmodded mui inside modules to save your time.
[Windows Mobile] fubo73:
Thank you very much! I was able to find the strings with Restorator, ResHacker is not capable, it seems...

But, I tried trial of Restorator, and I read that when saving it puts some tags inside the resource. So, could you please merge the change for me? Attached are the files.

Regards.
[Windows Mobile] AndrewSh:
Both your problems are solved in archive - trial and mui.
[Windows Mobile] fubo73:
The no mui problem solution is recognized as virus.
[Windows Mobile] AndrewSh:
Switch off your antivirus and use the tool - it's safe - I promise :)
[Windows Mobile] fubo73:
Currently I can't, I do not have the rights... I should do it from a virtual machine...
[Windows Mobile] AndrewSh:
fubo73, than check your PM
[Windows Mobile] fubo73:
Thx AndrewSh for all your kind support.

I just build 23150 using standard 23139 0410 package, and I got no issue at all. First time I tried changes shellres*.*, instead, I got a broken image loading but corrupted... I will try again with your files.
[Windows Mobile] mwalt2:
Has anyone who had problems with contacts in 21685 tried 21686 to see if the same problems exists? Thanks.
[Windows Mobile] AndrewSh:
Just use pimstore.dll from 21684 - that's it. Some people have problems... Me - not with Leo, but - yes with Asus.
[Windows Mobile] iggord:
29004_aku 5309 dft
[Windows Mobile] kaywchan:
I did have problems with 21685 not showing the saved favorites in the People tab after restoring using PIMBackup. And I couldn't assign contacts to the blank placeholders either.

21686 seems to work fine for me. My saved favorites in people tab showed up after restoring from PIM backup.

best regards.
[Windows Mobile] boggsie:
Boomer must have started the thread and went to eat lunch, before uploading to the FTP site!

If you are reading, relax and eat your lunch, Boomer! We'll be ready when you are. :D

Best regards,

-boggsie
[Windows Mobile] Tribulattifather:
When you do the benchmark test between build 23563 and (as it where today) Build 23150, could you please use a 3MB pagepool. As it where, I am using this test based on an older phone with a small amount of RAM. And 3MB is what I usually use.

According to this picture:

Isn't 230XX considered to be WM 6.5.4?

Also, is this currently @ 23148 now in this branch?
[Windows Mobile] CRACING:
Sorry, didn't had time in cooking yesterday. Kinda busy with my site. :p

3MB page pool for which device? I have topaz and hd2 and both had 15mb pp as default which is good AFAIK.

Doesn't 3MB pp is less or may be its enough for your device. Well I don't know which device you have but I see its QVGA. :rolleyes:

Thanks...

Best Regards

Edit: Could you please share the 23563 build? (XIP, SYS, 0409, DPI 192, WVGA) Coz I'm unable to download from filefactory shared in mobileunderground. :(
[Windows Mobile] Tribulattifather:
Yes, I believe if you tested with 3MB pagepool, I'd be able to see it correlate to my device better. I have a QVGA Tmo Wing, which Natively has 49MB or so of program memory and I push it to about 53MB with 3MB pagepool.

Also, here is what I used for my 23563 build (Click Here).

I wouldn't be able to give you my files as some are recmodded and I changed a lot of the GUI, not to mention I delete the other DPI's; I use 96-dpi..

But thank you very much again.
[Windows Mobile] CRACING:
Thanks. Will download now. I had forgot to check joojoobee666 ftp. :p

If I change the page pool to 3mb in my devices, the report will different much.

I always take benchmarks with default pp which is 15mb. Lets see...

Edit:

Check out the benchmark : https://spreadsheets.google.com/ccc?key=0AqXPpi2-Pn0PdC0zUTI4eERsQ3ZUcU9BQk5lVWtxcXc&hl=en

Just now taken benchmark reports from the ROM I cooked with build 23563 and it has got the lowest outputs. Amazed to see that but wish it had supported some of new HTC packages (i.e HTC Lock screen).

Anyways, with the curiosity now I'm gonna try the latest build from com 5. :D

Edit 2:

Cooked ROM with 23569 but benchmarks weren't so good as expected. Results on spread sheet.

Thanks...

Best Regards
[Windows Mobile] Tribulattifather:
Thanks for confirming my opinions; I'm glad to see that cooking with 23563 came to fruition with just gut instincts.

Also, do you have a link to the new HTC packages (EXT) or .cabs?

Thank you again,

Cheers.
[Windows Mobile] CRACING:
Here but they are WVGA. :rolleyes:
[Windows Mobile] illi:
And is there for COM2, please? I'm cooking for Topaz. Been googling but couldnt find any specifically for COM2.

TIA
[Windows Mobile] Nixeus:
These packages are old, do you think thaht htc will release new packages ? Or new ooboe rom ?

Thanks,

Nixeus
[Windows Mobile] CRACING:
Old? If they are old, they should have worked on com 5 builds without any issues but they aren't.

i.e if you use HTC lockscreen, you will get windows lockscreen instead in com 5.

However, I have no idea about very new oboe ROM or packages either. :o

Thanks...

Best Regards