HTC Prophet
mobile phone and digital assistant
The HTC Prophet is a combined Personal Digital Assistant (PDA) and mobile telephone manufactured by HTC.
It was released onto the UK market by Orange UK in April 2006 under the name Orange SPV M600. In Asia, it is marketed under the name Dopod 818 pro. It is also available on other networks as the Qtek S200 or the i-mate JAMin.
Features
Closely resembling the HTC Magician, the device is a 2.75G phone with a 2.8" 240x320 touchscreen, a 2.0-megapixel digital camera, Bluetooth 2.0 without EDR (equivalent to version 1.2 with additional bug fixes), WiFi 802.11b/g, Infrared Technology, Microsoft Push email access, 128 MB internal memory and a full sized SD card slot (no SDHC support). It is based on the Microsoft Windows Mobile 5.0 Professional platform, and was among the first Pocket PC phones to use the operating system. It has Microsoft Word, Excel and PowerPoint. The phone also includes Pocket Internet Explorer and Windows Media Player 10 Mobile as well as some carrier or provider specific software.
Specifications
Texas Instruments OMAP 850 200 MHz CPU
128 MB ROM, 64 RAM;
Talk time 5.0 hours
Standby 200 hours
Weight: 150g
2.0-megapixel camera, Macro Mode.
Bluetooth
Infrared connection
MP3 player
Polyphonic ring tones
True Tones
MP3 Ringtones
Video Messaging
Wap
WiFi
Windows Mobile 6 (Crossbow)
There were several "unofficial" builds of Windows Mobile 6 (Crossbow), WM6.1 and even some Windows Mobile 6.5 builds which ran on this device. Some tools allowed users to create their own custom WM6 ROM images (a process most commonly known by the term "cooking ROM's").
The public source identifies “HTC Prophet” as mobile phone and digital assistant. This brief keeps that definition visible, then builds a research path around Prophet, mobile and phone.
Why this record matters
A short description can identify a subject without explaining its stakes. For “HTC Prophet”, the useful work is to connect “mobile phone and digital assistant” to the records capable of establishing context and consequence.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Feb 9, 2026. The linked authority identifier is Q702946. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2006.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “HTC Prophet”, its source revision and the description used here.
- Expand the search: follow HTC Prophet primary sources, HTC Prophet archive and Prophet research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “HTC Prophet”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “HTC Prophet” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.