***READ: Windows Mobile 2005 and XDAIIs/MDAIII/PDA2K/etc ***

[HappyGoat]

Please read this before asking questions!

As of this time, there is no Blue Angel-compatible CE ROM of Windows Mobile 5 to date, in beta or final form, in circulation nor available for examination or experimentation to us.

As of this time, there are no official or unofficial plans or announcements by any manufacturer, distributor, or wireless carrier.

Please do not create new threads or post off-topic in current threads that are in regards to this UNLESS you have witnessed firsthand that one does exist or that you are or can be in possession of a Blue Angel device that has actual Windows Mobile 5 code on it.

As soon as we can get our hands on a test ROM, we will let you know as soon as possible. :D

Thank you.

Thanks to BeyondtheTech for the idea and text. :)

[HDuser]

Well its a thought

http://forum.xda-developers.com/viewtopic.php?t=22111

If you have comments post to that thread

[MarcValme]

Some dutch company interviewed the head of Imate (in English), He said it himself, that the reason was because of memory issues, and the he was afraid that everytime, the phone died or there was a hard reset, we would lose part of the operating system. heres the link to the dutch webite

Here is a link to the Web Site (http://www.gogadget.net)


Here is a Direct Link to the streaming Audio interview (http://www.gogadget.net/pocketinfo/PocketinfoPodcast180505.mp3)

[darkjedi]

i'm guessing u didn't see the thread about WM5 actually on a BA device did u? well it's true, WM5 CAN be put on a Blue Angel.

by the way, i listened to the podcast, and he was talking about the magician. now if it was the SuperJAM, then i think it would be ok. but devices with 64MB RAM, then you will have the problem. but since the BA has 128MB RAM it's ok.

[jglev]

Dale Coffing on his site mentions something interesting. At the end of his review on the Samsung i730, he posts a response to a reader in the comments section who was asking about WM5 on the Samsung. Here is his reply:

"I have been running Windows Mobile 5 as a development platform on a BlueAngel device (the MDA3) so it kind of spoiling me to not have some of the advanced features on the i730."

So, it seems that not only is WM5 for the BA possible, but it already exists.

Here is the link to his site: http://dalecoffing.typepad.com/my_weblog/2005/06/first_look_sams.html#more

[Bubisch]

Youre right, i also read this, but we all knew this before. We know that it exists and we were very very close to getting a hand on it, severel times.

[szamot]

Well if Dale was as big of a bible thumper as he claims he is, he would have shared the device with us by now, after all isn't that what Christians supposed to do, share with the needy? But I suspect that his bigger passion is wth MS so I am pretty sure he won't share with us.

[vbguru613]

I emailed Dale hes a putts and eveyone on the world who has a BA with 5 and doesnt share it. There all putt's

[efjay]

Well if Dale was as big of a bible thumper as he claims he is, he would have shared the device with us by now, after all isn't that what Christians supposed to do, share with the needy? But I suspect that his bigger passion is wth MS so I am pretty sure he won't share with us.

If hes such a "bible thumper" as you say that's the very reason he wont give out what doesn't belong to him.

[rdaprix]

I’m having the problem you’ve already solved on the PDA2K with the GPRS re-connection on T-mobile. I ran "The last ones" cab file for changing the ‘flags2’ file to 16. So far so good.

The other issue of course is the need to downgrade my caller id version to 1.20 build 17957. I have the cab file for that: IA_CallerID_1.20_WWE.CAB but when I copy it from my desktop to the device and double tap it I get the same error message: “The file “\windows\iacontacts.dll” is in use or is in ROM. If the file is not in ROM, please close the application using the file.”

So, the second part of the fix is a no go. This device is my goodlink and to be honest I desperately need a work around for this bug in the 1.40 ROM. I would be EXTEMELY grateful if you could stem me through the process of downgrading the caller id .dll file to 1.20 build 17957 and somehow getting around the fact that it’s in ROM.

Thanks very much for your help. I’m afraid I’m supposed to be leaving town tomorrow late afternoon and this IMATE PDA2K was supposed to be my lifeline. Now I’m ready to throw this brick out the window and buy a treo. I’m depressed. L

I would really be grateful for any assistance. Thanks so much.

[joey jojo]

I’m having the problem you’ve already solved on the PDA2K with the GPRS re-connection on T-mobile. I ran "The last ones" cab file for changing the ‘flags2’ file to 16. So far so good.

The other issue of course is the need to downgrade my caller id version to 1.20 build 17957. I have the cab file for that: IA_CallerID_1.20_WWE.CAB but when I copy it from my desktop to the device and double tap it I get the same error message: “The file “\windows\iacontacts.dll” is in use or is in ROM. If the file is not in ROM, please close the application using the file.”

So, the second part of the fix is a no go. This device is my goodlink and to be honest I desperately need a work around for this bug in the 1.40 ROM. I would be EXTEMELY grateful if you could stem me through the process of downgrading the caller id .dll file to 1.20 build 17957 and somehow getting around the fact that it’s in ROM.

Thanks very much for your help. I’m afraid I’m supposed to be leaving town tomorrow late afternoon and this IMATE PDA2K was supposed to be my lifeline. Now I’m ready to throw this brick out the window and buy a treo. I’m depressed. L

I would really be grateful for any assistance. Thanks so much.


im assuming you meant to click new topic rather than reply at the top of the thread!!!, lol

[Kalash]

Can we post in here now?

PLEASE!!??!?!?! :P

Or at least change the sticky to the one that says WM5 is up and running? :D