yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] cajunflavoredbob:
Motorola ES400

The first Windows Embedded Handheld device, the Motorola ES400, uses the 23121 SYS build. Since we've moved WAY past this build already, I would say that the SYS branch does not determine the device's platform name. If that is the case, then any current branch we're seeing come out could become a WEH branch or build. It seems to be up to the OEM.

Build info was provided by Rapid81.
[Windows Mobile] Nixeus:
Thanks for this useful post !

It's sad to know that if WEH use an other Core, we couldn't continue to upgrade our phone like HD2,etc..... :\
[Windows Mobile] rtomakov:
Did anyone noticed that some parts of 29009 package are missing?

I cant find 29009_WVGA_0409 part, those with theme .tsk files, phone redist ...

And, yes, I noticed that AFTER I made 29009 rom for hd2.

I am surprised that rom works without all that stuff.
[Windows Mobile] Rapid81:
I wouldn't be so sure about this. We'll see.
[Windows Mobile] Nixeus:
HTC release the kernel soruce for the Android Phone.

HTC HD2 is not an Android Phone, but a great and great phone.

Why HTC doesn't release the BSP for the public :)

We could build a new kernel for the future of Windows Mobile :)
[Windows Mobile] Monfro:
29011

Build 29011 is out!!!

Thanks to AndrewSh:

http://www.mobileunderground.info/showthread.php?t=444&p=78088#post78088
[Windows Mobile] cajunflavoredbob:
You're comparing apples to oranges. Android is an open operating system. Carriers have no choice but to release the code. They are not allowed in the General Public License to keep the operating system a secret or to profit from it. Android is a Linux based system.

Windows Mobile does not fall into this category. No one is expected to release codes or customizations. The operating system is also not free.
[Windows Mobile] Nixeus:
Nice for your answer but i know this ;)

Just wondering to having the BSP ! :)
[Windows Mobile] Farmer Ted:
It's not going to happen, so there's not much point in discussing it. I have no idea, but it's certainly possible (if not probable) that HTC would be in a major violation of the terms of their agreement with microsoft if they released their kernel sources. Let's just get back to discussing the new releases. Tx.
[Windows Mobile] pupakota:
Funny post about "terms" here, while this site's free developement and knife-methods of MANY led HTC to be one of most popular tradeMARKS....killing other PPC trademarks in advanCE...congratz on viral market.

i am sure, that mods will forgive me my post this time.

ehh..(EOT)...
[Windows Mobile] dotcompt:
But you like to be a part of it, don´t you?
[Windows Mobile] AndrewSh:
29013 AKU 5311
[Windows Mobile] EVEALEX62:
hi AndrewSh,

What is the difference between 29009, 29011 and 29013 please ??

Thanks in advance.

Best regards
[Windows Mobile] Rapid81:
29009 and 29011 is AKU 5.3.10

29013 is AKU 5.3.11
[Windows Mobile] EVEALEX62:
Thanks for the reply but I know that.

I just want to kwnow what is the difference ? (MAJ IE, etc ???)

PS: I hope you understand my bad english ... :)
[Windows Mobile] Rapid81:
I cooked a 29011, but I'm not experiencing any major differences between this and the 29007. Maybe 20911 is faster a bit.
[Windows Mobile] soroush0313:
Could someone please tell me what's the difference between AKU 5.3.9, AKU 5.3.10 and AKU 5.3.11?
[Windows Mobile] krazy_about_technology:
Hey guys, has the development stopped in 231xx branch? This was the branch having highest AKU version all the time. For ex, right now i am using 23152 having AKU 5.3.12. I like this branch.
[Windows Mobile] AndrewSh:
28245 AKU 5310

http://dl.dbank.com/c0l6yypniy

Password: JVpEPqcf

Thnx to Boomer (uploading), zjw831 (re-uploading)
[Windows Mobile] cajunflavoredbob:
I can't seem to get anything other than the COMMON_409 to download. Can someone who can get this build downloaded please upload it to multiupload or hotfile or something?
[Windows Mobile] AndrewSh:
28245_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409_FROM_DFT

Thnx to rewwps for re-uploading
[Windows Mobile] _Madmatt:
Is build 28245 (see quote) newer/faster than 23152? :) Can you post the release date?

And a last question: is there a HVGA device with newer packages (HTC Sense and other HTC stuff)?
[Windows Mobile] Farmer Ted:
Thanks, all! I love me some 28245 action. It's good to know that line is still alive, since it's the development branch. Yay!

Yes, it's exactly 4,362.3 times faster.
[Windows Mobile] CRACING:
Build 5224

Date Oct 24 2010

Time 15:57:09
[Windows Mobile] _Madmatt:
Very exact! Thanks! :)

Thanks! Will try it out soon
[Windows Mobile] mudhi:
There is not much difference between 23152, 28245 and 29013, by using SPB benchmark, very little.

I also test how fast it drains the battery, by full charged putting it over a night period, 3 AM ~ 9 AM.

23152: 10%

28244: 2%

29013: 6%

28245 have not tested yet

28244 has the best stability, 28245 has the fastest GPS locating speed.

And I'm trying to test 29014.
[Windows Mobile] prabhat:
Nice compare mudhi,

Can you please post the results of 28245 as well, if you are done :).

Thanks.
[Windows Mobile] pupakota:
That's interesting chart. And interesting comment about results indifference.

Thanks for tests, now i want to cook(6.5.x) again.

I can see VERY specific task-oriented differences(100% jpeg decoding diff, i.e. or ddb results(!)), it may be quite fun in searching of best of these.

TBH, after all these years i think that there's no thing like "best build", it is matter of finding specific build for specific needs, nothing more. And some builds are more suitable for specific needs than other ones. SO it is talk about: what do i need and do i need anything more(of the same)?

On the other hand i wonder, if all of these tested roms had SAME, exactly same reg settings related to tested elements.

Personally doubt it.

And finally - SPB bench sucks ass as real device value bench, but it can help finding interesting output....maybe.

k, taking 29013. seems suitable.

I lol'ed there, good one Ted, good one :)

Of course. Near, not a "part".
[Windows Mobile] szefu:
can someone share a mirror of 29014?
[Windows Mobile] AndrewSh:
21689

Thnx to DFT for sharing & to rewwps for re-uploading

Build (3599) (Jan 6 2011 15:44:02) AKU 5312
[Windows Mobile] kristofpetho:
Excellent tests!

I did my own benchmarks with SPB Benchmark, but I found this order:

Fastest to slowest:

29013 - 21916 - 28244 - 23152

2% 5% 5% difference

Firsat COM3 that is faster than COM2!!!

So overall, I am keeping the 29xxx branch on my HD2... :)
[Windows Mobile] kristofpetho:
Removed post due to ignorance on my part... :)
[Windows Mobile] AndrewSh:
The benchmark ****-measuring prevented you from seeing the link in my previous post :)

To mods:

Maybe the benchmarking and opinions "who's fastest" should be moved to separate topic? For those who is interested in the matter?
[Windows Mobile] kristofpetho:
LOL... Yes, you're right...
[Windows Mobile] CRACING:
Build 3599

Date Jan 6 2011

Time 15:44:02

Looks like newer build then others. :eek:

haha, same topic issue we had earlier. :D
[Windows Mobile] mudhi:
The 29014 is actually 29013 XIP, with mixed 29014 in some packages, just wait for 29015.
[Windows Mobile] prabhat:
Ohhh Good Info... so I will wait for 29015 :).

Thanks.
[Windows Mobile] prabhat:
Looks like the first build of 2011 :).

Any one have internal info/compare of this build with 28245 ?

Thanks.
[Windows Mobile] Rapid81:
21689 compared with 29013 on Omnia 2:
[Windows Mobile] mudhi:
I never succeeded reading internal database on HD2, here is the benchmark of new sys, I don't know how to calculate overall performance, but I sum it up, with the 21689 being the best.
[Windows Mobile] prabhat:
Thanks mudhi for the report :).

Thanks.
[Windows Mobile] cajunflavoredbob:
29009 Start Menu

Has anyone else had problems with 29009? I'm able to cook it just fine, but the start menu does not load. When I tap the start button, the device freezes for a few seconds while the button is shown to be depressed and then the button returns to normal and unfreezes without ever loading the start menu.
[Windows Mobile] Farmer Ted:
It sounds like you're missing the start menu .cpr's, or maybe have the wrong dpi's. My guess is that you left out a dpi package (can't remember which one is the start menu off the top of my head).
[Windows Mobile] cajunflavoredbob:
I guess something must be wrong or corrupted with the ones I'm using then. I'll try swapping between 29011 until I get it working. Thanks.
[Windows Mobile] AndrewSh:
29017_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409_FROM_DFT

Windows CE: 5.2 Build 6211 (Jan 26 2011. 9:44:01)
[Windows Mobile] Nixeus:
Yeah!Thanks a lot AndrewSh !!

Looks like a recent build :)
[Windows Mobile] Nixeus:
No skyBox ( MicrosoftMyPhone) in this build.

Is Microsoft abandon MicrosoftMyPhone ?
[Windows Mobile] AndrewSh:
Nixeus, MyPhone should be anyway updated to 1.6.2718 online so the default package is useless...

Wanna have my self-made 1.6.2718? :)
[Windows Mobile] Nixeus:
On my selfcooked 21916 rom i have the 01.06.2718.0001, is it the latest? Thanks :)
[Windows Mobile] AndrewSh:
Looks like that if it was really in the build but not online-updated while first start
[Windows Mobile] steff195:
Also in 21689. :D Anyway, I took the files from another build already...
[Windows Mobile] timolol:
Great! Thanks very much for 29017. I've been waiting for this build for a while. Time to cook! :)
[Windows Mobile] Nixeus:
Please give us a feedback about this new build :) :)
[Windows Mobile] Rapid81:
Sense 2.5 is running faster on it on Omnia 2 than on the previous 290xx builds. :)
[Windows Mobile] Nixeus:
Great :)

Else, is there any new features ?
[Windows Mobile] Rapid81:
GPS fix is halved for me (now a cold fix is about 1-2 minutes. With the stock ROM had more than 10 mins, with 29011 5-6 mins). :D

Office Mobile 2010 Version 14.0000.29017
[Windows Mobile] Nixeus:
Thanks a lot. ;) :)
[Windows Mobile] Nixeus:
I have a question about the future of Windows Mobile.

It will become Windows Embedded Handeld. Ok fot this.

Actually, the Windows Phone 7 don't use MarketPlace and MicrosoftMyPhone.

Microsoft don't want to kill Windows Mobile, in order to continu a Mobile OS for the professionnal.

Do you think that we can imagine ( and dreaming....) about a compatibilty of the WindowsPhone 7 Marketplace, and maybe the Windows Phone 7Apps on Windows Embedded Handeld ?
[Windows Mobile] NRGZ28:
Thanks for posting that man :)
[Windows Mobile] leonore:
@AndrewSH

Thanks a lot for sharing-it`s very nice Build-just cooking a rom

Best regards
[Windows Mobile] cajunflavoredbob:
Nope. If you want WP7 apps, you'll need a WP7 device.
[Windows Mobile] pupakota:
29017 seems to be nice, really nice build, but guys, i have weird problem with toaster skinning - it is white on white, just block of white space no gfx(despite of having gfxes related to that element and reg in theme), could someone pm me with solution? Had something changed since first 6.5.x'es in theming matter?

And some more ot - i had theme that had NOT menu scroll arrows, now, when i am trying with 6.5.x again(after year of skipping 6.5'es) i do not remember how it was done.

I remember that menu was scrollable, BUT there was NO menu tap-scroll-arrows, i need info on this badly. Is this possible at all with 6.5.x now?
[Windows Mobile] fubo73:
I flashed 29017 on my Omnia2 in two fashions, but with both I'm having issues. 29013 worked better. I will give a try to 28245.
[Windows Mobile] thunder141:
flashed 29017 on omnia qwerty. What issues do you have?
[Windows Mobile] fubo73:
1. Bluetooth does not work anymore with Parrot. It worked with 29013 and works with 28245

2. Phone app occasionally locks and I need a reset. 29013 was fine.
[Windows Mobile] Rapid81:
Then maybe you did something wrong.

I cooked some 29017 ROMs to i8000 too, and all working just fine.
[Windows Mobile] variosteph:
had some problems with 29017 too. random freezes, auto-hardreset and stuck on bootscreen. flashed different roms to my rhodium and always the same problems.

don´t know if it´s just a problem of my kitchen, flashed a new rom 2 hours ago an till now no freeze... so let´s see:-)
[Windows Mobile] AndrewSh:
C'mon guys, latest 21689 and 29017 are good builds with absolutely NO issues.

No need to post "cooked rom and now it has issues". The problems are not in the build but in cooked roms. Let's keep the topic clean of complains 'bout "bad roms' - let's talk only about builds.

Whenever some common SYS issues detected - welcome to post. But not the private problems with roms, kitchens etc.
[Windows Mobile] HD2Owner:
yeah. you're right. both builds (21689 and 29017) are working very well. :D
[Windows Mobile] fubo73:
I'm sorry AndrewSh. I agree it could also depend on specific unit software. I will avoid complaining anymore.

Thanks again for sharing new builds!
[Windows Mobile] c_shekhar:
Yes you are absolutely right. Ihave no issues on my hd2
[Windows Mobile] mwalt2:
These are all signs that you need to use Task29 or flash a shipped ROM for your device before you continue flashing new custom ROM builds.
[Windows Mobile] Farmer Ted:
28245 is awesome. I'd say that it is every bit as good as 28244.
[Windows Mobile] variosteph:
thanks for your asistance mwalt2, thats exactly what i did before flashing 29017:-)

but no freeze till this morning, so it must have been my bad cooking skills, corrupted kitchen, whatever

so sorry guys for wasting your time and yes, 29017 is great

steph
[Windows Mobile] mwalt2:
Just curious, but is pimstore.dll from 21864 still needed or is the pimstore.dll from 21689 compatible with our devices?
[Windows Mobile] AndrewSh:
New pimstore should work
[Windows Mobile] 5318008:
This is pretty standard practice isn't it? I don't flash often (or at all anymore, sold my Rhodiums) but when I do (did) I'd do a task29 with a radio to blank out the old ROM, then flash over the new ROM. Doesn't really take much more time.
[Windows Mobile] xlightwaverx:
290xx

So 290xx seems to be the most recent build. For what exact system is it for?

Example:

212xx = AKU1, all builds leading up to and including WM 6.5

213xx = MOT motorola

214xx = ???

215xx = SAM samsung

*216xx = HTC htc

217xx = COM1, continuing dev of 6.5.0.1 - 6.5.0.40

218xx - 21919 = COM2, continuing dev of 6.5.0.50

21920 - 21999 = MD, feature test branch, pretty much dead now. (unstable features are added here, this tree is based on COM1, so older base OS code, but the UI/UX code is newer)

*22xxx = SEMC sony ericsson

*230xx - 231xx = COM3, continuing development. Now an HTC branch.

*234xx = COM4, appears to be abandoned.

*235xx = COM5, more GUI changes here.

*236xx = LG Electronics Branch

*24xxx = Possible HTC branch

*25xxx = SEMC - Sony Ericsson

*280xx, 282xx = WMD. This is a continuation of com3 from 23090. Most of the changes appear to be with IE

It would be nice to associate a system with this. Though I read where Rapid used it on i8000, so in turn it must be compatible with i920 Omnia II, correct?

X
[Windows Mobile] cajunflavoredbob:
We don't know where it came from. It's listed as Unknown on the Mobile Underground thread.
[Windows Mobile] xlightwaverx:
How long has it been out? Does it work with all devices? Maybe its the Universal OS. ;)
[Windows Mobile] Farmer Ted:
I know I'm going out on a limb here, but I'm thinking 29017 is the 18th build (at most) in the series.
[Windows Mobile] + Que PPC:
Universal OS??? :p sounds nice, but who wants to know from wich branch is it... almost all are dead, im happy to have a newer build wherever it cames i will try it, and i think all are Universal OS, just the OEM Changes :p and 29017 is... a good build.
[Windows Mobile] illi:
Just curious:D

Is it possible to change the home layout of COM3 to COM2? What I mean is can the Taskbar be at the top instead of at the bottom. I really dont like the Start Menu, etc., to be at the bottom.:confused:

TIA
[Windows Mobile] AndrewSh:
Absolutely not. Different gwes.
[Windows Mobile] illi:
Thanks AndrewSH:D
[Windows Mobile] Nixeus:
@Illy,

I would like too this ! I don't like the come2 Home.....grrrr

It's possible to hack gwes....
[Windows Mobile] AndrewSh:
Just curious - what do you plan to hack? Gwes is the Graphical Windowing and Event Subsystem. It’s program that draws all the controls on the device like scrollbars, buttons, and checkboxes. It also handles passing window messages back and forth between applications and manages the window callback function of all of the programs on the device that are displaying UI.

So first you should "hack" all the resource libs and muis, draw new bitmaps (all of them in Windows), then Windows API, then font engine and so on, and so on...

When you finish this work - let us know - we will help you to "hack" gwes.
[Windows Mobile] sharkie405:
Just to put this out there for anyone who might want to give this a go...

I use the entire OS directory from the 23563 SYS in my other build packages. The latest builds I've used this with are 21689, 28245, 29017 and I've been using it on 29007 for a long time now with absolutely no issues. I did try changing out just the gwes.exe, but as Andrewsh stated, it didn't work. Replacing the whole SYS\OS package does work though. I also use the 23563 lockscreen packages with all my other builds.
[Windows Mobile] Nixeus:
Hey my friends,

If we use a com3 XIP ( like 29017) with the latest com2 buils (21917), maybe we could have a better system than a Com2 XIP and a Com2 SYS.

What do you think about ?

Thanks a lot,

regards,

Nixeus
[Windows Mobile] bgcngm:
You're talking about 21917... Was it really released?
[Windows Mobile] Nixeus:
Sorry it's an error ! I'm talking about 21916 !
[Windows Mobile] bobzero:
do any of these latest builds come with a newer version of voice command?

I'm using 1.6.23568 from build 23568, Anyone know what the latest voice command package is?
[Windows Mobile] krazy_about_technology:
Hmm... Cooked 29017 Yesterday. Good build, more respnsive than 23152 practically on my Samsung B7610 Omnia Pro. File system speed seems good as on LZX compression, app startup time is considerably better. Also, GWES seems to be tweaked a bit, loads and operates heavy graphics/image based apps better. Gonna live with it for some time.
[Windows Mobile] ai6908:
Probably that is the latest!
[Windows Mobile] Farmer Ted:
I'm pretty sure MSVC only comes with builds leaked out of the US. Da_G's builds had it, but I don't think any of DFT's do. So, I wouldn't expect any new versions any time soon.
[Windows Mobile] rickou26:
Hi,

I cooked the build 29017 and I find it rather well except that its consumption of the battery seems a bit larger than the Successives versions.

however, if someone calls me when the phone is at sleep mode and locked (WM lockscreen), the caller IDs are not shown on the screen, only the caller's number is shown. The name, the pictures are not avaliable.

Have you any idea to deal with this problem ?

Thank you
[Windows Mobile] derliebewolf:
thats a common issue in most of the 29xxx and probably 28xxx builds, together with a few other glitches. It's caused by the cprog.exe acting different than it used to do before. The fix supplied here should help you out, though.
[Windows Mobile] illi:
Date not shown in Quick links page

I'm cooking for Topaz using the latest Sense Core 2021/Home 2022. The Home screen, when I scroll down to the Quick Links page, the date is not displayed. I cant remember if the stock ROM shows the date or not. Can someone confirm that it is the natural behaviour or the actual date should be displayed. If that is the default, how can I get the date to be displayed?

Please see my screen capture.

TIA

illi
[Windows Mobile] rtomakov:
It still has it!

Seems that some manila files are missing in your build.
[Windows Mobile] NIKOSXRI:
Just curious, why Microsoft doesnt fix this problem?What are they waiting for?
[Windows Mobile] illi:
Thanks rtomakov. Will take another look at my manila files;)
[Windows Mobile] derliebewolf:
I don't think this a "bug" at all. I guess they are modifying some of the stuff for newer Builds as the intend to use that for Windows Embedded Handheld (e.g. Moto ES400). The problem only occurs afaik with pacages from HTC, so mixing old (HTC's stuff) and new (WinMo build) takes you to the place where you are now. But as that never was inteded to be mixed it's not a "real-life bug" ;)

Can confirm, it works with my ROM (using the same Manila core and Home builds as you are)
[Windows Mobile] illi:
Looking at the Manila files now. Thanks for the heads-up:)
[Windows Mobile] rickou26:
Thank you very much the fix works perfectly. :D
[Windows Mobile] Nokser:
Anyone have a Polish package for WM 6.5.x??
[Windows Mobile] StefanV3:
Hi,

i have a self cooked ROM with Build 29017 on my HTC Touch2, but the consumption of battery is very strange i think. It feels like the battery life is only half as long with other builds. Can anyone confirm this or even fix this?

StefanV3
[Windows Mobile] Shady313:
My battery drain is also worse on HD2. I couldnt fix this yet.
[Windows Mobile] derliebewolf:
I cannot complain about batery drainage of 29017. It's better than 29007. At least it feels like its better :D
[Windows Mobile] ai6908:
You probably will need to go through the charge cycle twice. Usually that fixes it. I am running 29017 and batter life is just fine.
[Windows Mobile] Farmer Ted:
I would recommend using tBattery to figure out if there's a major current draw.
[Windows Mobile] AndrewSh:
100% agree.

Normally battery driver is OEM :) All the builds I've ever tested have absolutely identical battery drain (and believe me - I've tested much more builds than published here as links)
[Windows Mobile] krazy_about_technology:
I am also using 29017 since 3 days on my Omnia Pro B7610 with LZX compression, No extra battery drainage. Its exacly like it was before. My phone still lasts 2 days, 2nights on a single charge with average usage.
[Windows Mobile] prabhat:
I have 29017 and its battery life is pretty good on my Touch Diamond 2/Topaz (~2 days in a 2G network with normal usage and couple of time WiFi).

@ai6908,

What is that "go through the charge cycle twice"? - I just wanted to know... and how that solves issue that StefanV3 has? That should be the solution as AndrewSh and have confirmed, but just curious to know :confused:.

Thanks.
[Windows Mobile] + Que PPC:
Yeah my batt drains fast too compared to others... i has an old device i know but batt is ok, i guess they are trying to say that we need to change the batt OEM pkgs to a newer version ;) i will try with my latest i can use HTC Mega's :p
[Windows Mobile] ai6908:
Sometimes, after flash, battery seems to drain too fast. In that case, let the battery drain completely, then put it in the charger, and let it charge complete. Repeat this again, and it usually stabilizes the battery drain.

This can be fixed if the drain is caused by new flash. If the drain is the same after going through battery charge cycle, then you have some program that is draining it, or you need a new battery!
[Windows Mobile] pupakota:
Your device needs to learn about battery again.

Also, it is good idea to flash with fully loaded battery, as it can shorten that "learn" time a bit, or even eliminate drain. Usually it is good idea to do 2 cycles of charge-discharge before making opinion on "drain".

It was like that, it is like that and it probably will.
[Windows Mobile] Shady313:
My battery lasts 5% in 10 hours (standby) with build 23152.

With 29017 it was 8% in 10 hours (standby).

Now looks like it normalized to 5-6% in 10 hours (Im using now some oboe packages, maybe i had a module problem). So it isnt too much but i've experienced. :)
[Windows Mobile] StefanV3:
Hi,

it seems that i was able to to reduce the battery drain by deactivating w-lan on my HTC Touch2.

StefanV3
[Windows Mobile] ai6908:
So does this mean that I dont have to use pimstore from 23563 to fix the caller id issue?
[Windows Mobile] StefanV3:
Hi,

i have another problem. I could not save any new contacts to sim card. When i tap the button to save the contact, it brings this error message:

SIM error. The informations could not be saved to sim card.

(translated from German)

But this problem is not new to build 29017. It's there since some newer builds. Hot to fix this?

StefanV3