22 Apr, 2005
Version 1.7 Release Candidate has been released !
Fixed bug (overlapped text) for WinMobile 2003SE (O2 IIs, mini...)
Download: http://www.d25.cjb.net
What's new ?
1) Reading favourite-text file & vocabularies file very fast now.
2) Added Chinese lunar datetime style.
3) New style for Calendar (fixed width, not depended on Fonts size anymore).
4) Tap on a day on Calendar will shows full date.
5) Support Landscape mode of Windows Mobile 2003 SE.
[FIXED BUGS]
- Fixed: overlapped text on PPC with Win2003SE (O2 mini, O2 IIs...)
- Fixed: reading fav-text/vocabularies-text file that has only 1 line.
- Optimized performance.
- Tested with: WM2002/2003/2003SE, O2 XDA II, O2 mini, O2 IIs, SX56, iPAQ 2215, iPAQ 4150, iPAQ 4700, Siemens.
- If you get any bug, please visit the forum
great little today plugin !!!
The Magic can upgrade WM5/WM6 disappointment, so powerful configuration and even impossible Take WM6 disappointment. A strongman change this situation?
Eh? What do you mean?
Can we use WM5 and WM6 on the Magician (WM2003) hardware?
V
vijay555 said:
Eh? What do you mean?
Can we use WM5 and WM6 on the Magician (WM2003) hardware?
V
Click to expand...
Click to collapse
I think he meant he's disappointed that there is no WM6 for the magician Considering its a powerful device and is asking any strongman(sorry im not that buff Lolz) to take the challenge.
Why hasnt anyone made a wm5 rom for the magician? Its not like the device lacks the stats to run it.
bigcheekybird said:
Why hasnt anyone made a wm5 rom for the magician? Its not like the device lacks the stats to run it.
Click to expand...
Click to collapse
After reading the numerous WM5 threads here in the magician forum, there are three reasons for this:
1. The lack of drivers,
2.And the most significant of all, the memory is too small, i think you need atleast 128MB of ROM.
3. The device is already old to even be given a new rom by hackers, most of them got a kjam or hermes already.
Eikichi said:
After reading the numerous WM5 threads here in the magician forum, there are three reasons for this:
1. The lack of drivers,
2.And the most significant of all, the memory is too small, i think you need atleast 128MB of ROM.
3. The device is already old to even be given a new rom by hackers, most of them got a kjam or hermes already.
Click to expand...
Click to collapse
I dont know much about the drivers but in sure that some one could create them, a device called Pharos Traveler 525e runs on 64mb of rom and has windows 5.0 installed on it, there are a few others out there aswell that run on 64mb of rom, The main reason you need such a high level of ram is because of the way wm5 was made, if you install all your programs on a sd card then your problem is virtually gone. The device may be old but im sure that there is someone out there that has the know how to take on this project.
Not RAM, Its the ROM which is small. Theres no deal with RAM, some imate jams have 128MB of RAM,heck even my iPAQ is running WM5 on a relatively small 64mb of RAM (32mb of which is useable RAM), but it has 128mb of ROM. Magician has only 64mb of ROM. The only way i know to have WM5 but still maintain the classical,simple and elegant look of the magician is to trade it for a charmer. But you lose CPU power in the process (magician-xscale;Charmer-TiOmap)
My bad, i meant rom, ive changed the post.
The Pharos has 128MB of ROM and 64MB of RAM see the specs.
http://www.pharosgps.com/products/all-in-one/PTL525E.htm
* Microsoft® Windows Mobile™ version 5.0 software
* Pocket versions of Microsoft software are included (Outlook, Word, Excel,Windows Media Player and Internet Explorer for Pocket PC)
* Processor:SC32442 300 MHz processor
* Memory: 128MB ROM, 64MB SD RAM
* Dimensions:109.7mm (L) x 59.4mm (W) x 17.6mm (T)
* Resolution: 240 x 320 with65,536 colors
* Expansion: SDIO expansion slot
* Built-inBluetooth and WiFi
Yea your right, i got my data off this webiste http://accessories.us.dell.com/sna/productdetail.aspx?c=us&l=en&s=dhs&cs=19&sku=A0785811
It says 64 MB ROM and 128 MB SDRAM.
my bad
HP iPAQ hx2410 Pocket PC (FA298T). this device runs stock on wm2003 se but has an update to wm5, it runs slowly but it works. heres the link to check the stats. http://h10010.www1.hp.com/wwpc/uk/en/sm/WF06a/21675-21679-21679-21679-297609-10244635.html.
The thing i dont get is, if you can update this to wm5, why cant it be done for the magician, they have relatively the same stats.
Look mate im not trying to be difficult for you here, you were asking the reason why, and to save you time i gave you the reason which has been repeated for numerous occassions whenever some idiot who doesnt know how to search the forum pops up the WM5 question. If you want to satisfy your curiosity then i advise you to course through all the WM5 threads in the magician forum starting from buzz lightyears thread, and hopefully youll get the answer your looking for.
Why not?
We know how to add/remove files from the ROM, many components from the Magician are used in Himalaya, Universal and BlueAngel
ex:
PXA272 -> Universal
Bluetooth -> Himalaya (both uses BlueCore3)
GFX/SDIO/USB via PXA272 -> Universal
Touchscreen -> Himalaya, BlueAngel
maybe some others, I don't know how many drivers we have to identify, and if the compatibility will be possible with a different architecture/mapping...
And Himalaya and Blueangel have 64Mb ROM and works on WM5... I don't mean we can have a full featured WM5 for Magician, but a "as small as we can" ROM, just for the POC, and let ppl build some special ROMs for special use-cases
I'll try to gather more informations on the forums on how they did cook first releases, try to create a kitchen (Blueangel or himalaya kitchen should work without many changes), and a DEV folder with filtered registries...
And maybe, after WM5.... WM6? And long walk has to be done before first ROM
--------UPDATE-------
The biggest problem seem nk.exe... since there is no nk.exe (WM5) for magician, we can only expect to hack some nk.exe (from universal for processor compatibility), or find a magician-like (same processor and major components) device which already has WM5... It may be a long long and risky walk...
@Eikichi
I have read the forums, but still dont get why the magician cant run wm5 when there are other devices out there that can.
@b0ris747
vicott
Sep 28 2005, 11:41 PM
The minimum requirement of Windows Mobile 5.0 is 32MB RAM and 64MB ROM. For devices having only 64MB ROM, there is a high chance that the devices may only be using a reduced version of WM5.
For example, HTC Galaxy has 64MB ROM and about 33-37MB of it is for persistent storage. One of the models of the upcoming Fujitsu Siemens N500 series may also have only 64MB ROM. And WM5 upgrade is also provided for devices having only 64MB ROM, e.g. iPAQ hx2110/2410, FSC Pocket LOOX 700s and Acer n50.
Taking the HTC Galaxy as an example, a reduced version of the OS may be less than 32MB. Let's take a look at other WM5 devices and their config:
* HTC Universal: 128MB ROM and about 44MB persistent storage
* HTC Wizard: 128MB ROM and about 47MB persistent storage
* HTC Galaxy: 64MB ROM and about 33-37MB persistent storage
* Dell Axim X51V: 256MB ROM and about 195MB persistent storage
* Acer n311: 128MB ROM and about 84MB persistent storage
* FSC Pocket Loox N520 (engineering set): 64MB ROM and about 26MB persistent storage
* HP iPAQ rx1950: 64MB ROM and about 33MB persistent storage
* HP iPAQ hx2190/2490: 128MB ROM and about 80MB persistent storage
* HP iPAQ hx2790: 192MB ROM and about 144MB persistent storage
I got the above info above from the link below
http://www.ppcsg.com/lofiversion/index.php/t59946.html
here http://forum.xda-developers.com/showthread.php?t=312625&page=2 last post something that convinced me not to wait for WM5 (the english is not perfect but the point is there). But if you guys are up for the challenge, by all means my best of luck to you and thank you in advance.
The thing is though, wm5 has been put onto a device with the same rom and ram stats as the magician, so that guy is wrong in saying that it wouldnt work.
Since no visible WM5 for the magician is existing not even in experimental form, dnt u thnk d presumption that he is correct works for his favor? anyway you can rebutt all you want but the bottom line is... "There is no WM5 for the magician" in actual or experimental form.
upgrade my dopod 818 pro
wher can i update my dopod 818 pro from wm5 to wm6
Seem easier to finish the work on porting linux...
Eikichi said:
Since no visible WM5 for the magician is existing not even in experimental form, dnt u thnk d presumption that he is correct works for his favor? anyway you can rebutt all you want but the bottom line is... "There is no WM5 for the magician" in actual or experimental form.
Click to expand...
Click to collapse
Maybe should ppl investigate linux as a solution... Linux exists for magician (I tried it) but still some work to do to make it bootable under linux (but has been made successfully on other devices, including WM5 compatible devices like ipaq hx4700).
It's legal (not like cracking ROMs) and a lot of informations already exists, and you won't have restrictions on how you use your GSM modem...
Magician could handle WM5... But it would require too much work for what it would offer. Linux is for me a better alternative to focus on.
...............
b0ris747 said:
We know how to add/remove files from the ROM, many components from the Magician are used in Himalaya, Universal and BlueAngel
ex:
PXA272 -> Universal
Bluetooth -> Himalaya (both uses BlueCore3)
GFX/SDIO/USB via PXA272 -> Universal
Touchscreen -> Himalaya, BlueAngel
maybe some others, I don't know how many drivers we have to identify, and if the compatibility will be possible with a different architecture/mapping...
And Himalaya and Blueangel have 64Mb ROM and works on WM5... I don't mean we can have a full featured WM5 for Magician, but a "as small as we can" ROM, just for the POC, and let ppl build some special ROMs for special use-cases
I'll try to gather more informations on the forums on how they did cook first releases, try to create a kitchen (Blueangel or himalaya kitchen should work without many changes), and a DEV folder with filtered registries...
And maybe, after WM5.... WM6? And long walk has to be done before first ROM
--------UPDATE-------
The biggest problem seem nk.exe... since there is no nk.exe (WM5) for magician, we can only expect to hack some nk.exe (from universal for processor compatibility), or find a magician-like (same processor and major components) device which already has WM5... It may be a long long and risky walk...
Click to expand...
Click to collapse
The Htc Atom Uses the exact same processor as the htc magician, You could use the nk.exe from the atom to make the magicians one
Htc Atom
Specifications
Date Announced 2005, 3Q
Network Technology GSM 900 / 1800 / 1900
Hardware/Processor Intel PXA272 416MHz processor
Dimensions (mm) 102 x 58 x 18.5
Weight (g) 140
Display Screen Size : 2.7 inch, 240 x 320
Screen Color : TFT 262k Colours (65k effective)
Design Type : Blok
Navigation Key : 5 way Navigation Key
Other Keys : Volume up/down, Camera, Recorder
Antenna : Fixed Internal
Memory Phonebook : Advance
Internal(MB) : 64MB SDRAM, 128MB ROM
Expansion : miniSD, SDIO
Battery Battery Type : Li-ion 1500mAh
Stand-by (hrs) : 150
TalkTime(min) : 330
Entertainment
Ringtones Polyphonic : 64-chord polyphonics
Customization : MIDI, MP3, WMA, WAV
MP3 Yes
A2DP Yes
TV Receiver Null
FM Radio Yes
Video Record Yes
Video Support MPEG-4, H.263, WMV
Audio Support MIDI, MP3, WMA, WAV, AMR (Stereo Speakers, 10-band equalizer, 2.5mm Audio Jack)
Voice Support Recording, Dial
Games Solitaire and Jawbreaker
Messaging
SMS Yes
MMS Yes
EMS No
Email Pocket Outlook
Connectivity
HSDPA Null
EDGE Yes, Class 10
Bluetooth Yes
3G No
GPRS Class 10 (4+1/3+2 slots)
Infrared (IrDA) Yes
USB Port Yes
WIFI/WLAN 802.11b
Data Cable RS-232, mini USB
Software
Java (J2ME) Yes ,MIDP 2.0, CLDC 1.1
WAP Yes Ver 2.0
Platform / OS Windows Mobile 5.0
Browser Internet Explorer Mobile
Other Application Windows Media Player Mobile 10, Office Mobile (Word Mobile, Excel Mobile, Powerpoint Mobile), O2 MediaPlus, ActiveSync 4.0, PDF Viewer
Personals
Themes No Info.
Caller ID Photo
ProfileID Yes
Camera
Lens Type CMOS, 2.0 Megapixel
Digital zoom
Max. Resolution 1600 x 1200
Flash Yes
Night Mode Yes
Multi Shot Yes
Extra Features self-portrait mirror, self timer, landscape mode
Photo Format JPEG(1600x1200,1024x768, 640x480, 320x240,176x144)
Video Yes
Video Format MPEG-4 (352 x 288, 176 x 144, 128 x 96)
Its worth making the rom so that finally we can have wm5 on magician
The new German O2 ROM can be found here:
http://www.o2online.de/nw/support/downloads/software/xda/xdaorbit2/index.html
New (translated from page with some notes)
* Windows Mobile Professional 6.1 AKU 1.2.3
* Threaded SMS (Win 6.1 standard...)
* Improved stand-by time (...not yet tested)
* Improved support for MS Exchange 2007
* Pocket Internet Explorer with page overview
* Opera Browser (Old 8.65 Version...)
* Remote Desktop Client
* »First Steps« Wizard
- Runs pretty slow for me
- TomTom 6 is also included.
- One Note is included
- TouchFlo 2.0 ... plain and simple 4 tabs standard
I'm not to excited about
For me it is really exiting. I´m using my TC as a busines device and this rom is faster then the Original rom and have less Bugs than every other Rom here.
Does it have new album, camera, or music software?
The Audio Manager is still version 1.2
Tha Album looks like the Old one and the Camera is still "ein Haufen Grosses Ah Ah" (not good)
But more intersting is, that the Exchange is working better for me
I think it´s possible to update the Audio Manager and the Album software.
Weather of own city in HTC-Home
Hello all,
I also updated my orbit2 with the official O2 WM6.1. But the weather patch "N2A Pathed Home Plugin DLL.cab" I used before forced me to do a hard reset.
Have anyone a solution for this?
SOLVED!
I've edit the original htchome.dll with a hexeditor and change the webside in this file.
1st time I forgot to sign the file after my changes, but now everything works fine for me.
Hi I have the following issue when cooking both WM6.1 and WM6.5 ROM.
If I use a donor ROM with MS bluetooth stack, when I am trying the pair my WinXP netbook which is running Widcomm/Broadcom stack, my netbook can see the following service from my WM phone:
- ActiveSync
- Network Access Point (NAP)
- Dial-up Networking (DUN)
- OBEX Object Push
- Voice Gateway
If I use a donor ROM without MS bluetooth stack, but supplement the missing SYS part (SYS/Bluetooth and SYS/Bluetooth_0409) from another donor ROM which has MS bluetooth stack, then my netbook can only see the following service from my WM phone:
- ActiveSync
- OBEX object push
- Voice Gateway
The major show-stopper here is the missing of NAP. This is stopping me from moving to the latest shipped ROM I can get my hand on, as most recent WM shipped ROM all have been using Widcomm/Broadcom stack.
I am cooking for HTC Diamond. Due to the above issue, the best ROM I can get for HTC Diamond are:
- WM 6.1 build 21042 (donor from Topaz)
- WM 6.5 build 21887 (donor from Topaz) with native NK + OEMDrivers from pine ROM.
If someone has any solution to this issue, please help. Thanks.
I am impressed you have managed to get that far transplanting the MS BT Stack back into a device that natively has the Broadcom/Widcomm stack. I am keen to know what files/modules and registry entries you removed/added/changed from the OEMDrivers folder to get this far? I have a BT carkit and it simply doesn't get on well with the Broadcom stack on my custom-ROM'd LEO. With the same WM build and native drivers on my old Blackstone it works perfectly (with my BT carkit..).
Cheers
Andy
No, I am not. I am cooking for HTC Diamond, so my base ROM always has MS bluetooth stack. It's the donor ROMs that I am porting from that have Widcomm/Broadcom stack, because all the recent HTC WM builds always come with Widcomm/Broadcom stack.
Ah sorry, misunderstood. I thought the Diamond had the Broadcom stack natively.
If you have the MS BT stack natively then I'd have thought the MS BT components in the latest MS builds would work? I always use the 'full' MS Builds that are kindly packaged by DFT and not builds extracted from 'donor' ROMs.
Andy
I have always been sourcing donor ROMs from official ROMs releases. This way, I don't have to worry about beta OS, stability, time-bomb etc. Call me un-adventurous, but this is my preferred way of cooking and the source is legitimate, sort of ...
I would refrain from using unofficial/leaked MS build drops for the mean time if this issues can be resolved through other means.
Solved
I have found the answer to my own question.
It was caused by the DSM order in package.sof. For donor ROMs which don't have MS bluetooth stack, the package.sof will not contain the DSM UUID for SYS/Bluetooth and SYS/Bluetooth_0409. When the missing SYS are supplemented from another ROM, BuildOS will append their DSM UUIDs at the end, and so their RGUs will override the RGU from SYS/INTERNETSHARE and setup BT communication as PANU instead of NAP.
I analyzed packages.sof from Topaz ROM and SYS/INTERNETSHARE comes after SYS/Bluetooth.
As a result, I am now running my Diamond with WM6.5 Build 21913 ported from Leo 3.14.