HP iPAQ hw6515 and the Windows Mobile 5 Upgrade That Never Came

Some product histories are about what shipped. This one is mostly about what didn't. The HP iPAQ hw6515 landed in 2005 as a genuinely capable converged device — touchscreen Pocket PC, slide-out QWERTY keyboard, phone radio, and built-in GPS in one body. What it never got, despite real interest from owners, was the Windows Mobile 5 upgrade that started showing up on newer devices within months of its own debut. HP said no, on the record, in September 2005, and the details are worth getting right rather than repeating the shorthand version that's circulated since.

What Was the HP iPAQ hw6515?

The HP iPAQ hw6515 was a converged PDA-phone — HP called it a "Mobile Messenger" — announced in mid-2005 and reviewed by outlets including The Register that September. It packed a touchscreen Pocket PC, an integrated GSM/GPRS/EDGE phone radio, a slide-out QWERTY keyboard, a camera, and built-in GPS into one handheld, at a time when most of those still lived in separate devices. It reached the US market in part through Cingular, and it wasn't cheap: owner comments on Mobility Today from late 2005 describe paying upward of $700 for one, in line with its positioning as a premium business device.

The hw6515's Original Operating System

Worth stating precisely, since it's easy to get backwards: the hw6515 shipped with Microsoft Windows Mobile 2003 Second Edition, Pocket PC Phone Edition — not Windows Mobile 5. WM2003 SE had released in early 2004, more than a year before the hw6515 reached shelves, and Windows Mobile 5 itself didn't arrive until May 2005, right around when the hw6515 was announced. That timing is exactly why the OS became a live issue almost immediately: reviewers, including The Register, were already describing the hw6515's OS as the "older" platform practically on arrival, simply because a newer one had appeared on the calendar at nearly the same moment.

Hardware, Keyboard, and Touchscreen

Under the hood, the hw6515 ran an Intel PXA270 processor at 312 MHz with 64MB RAM and 64MB ROM, expandable through dual card slots — a full-size SD slot and a separate miniSD slot. The display was a 3-inch square TFT touchscreen at 240x240 resolution, run with a stylus in traditional Pocket PC fashion, and the unit weighed around 165 grams with its 1200 mAh battery installed. Below the screen sat a full physical QWERTY keyboard rather than a numeric keypad. Reviewers compared the key feel unfavorably to the Palm Treo 650, but noted the wider hw6515 body actually made typing more comfortable in practice.

Built-In GPS and Bundled Navigation Software

The hw6515's GPS receiver was genuinely built in, rather than added through an external sled or Bluetooth puck, which was still a common way to bolt GPS onto a Pocket PC at the time — contemporary coverage specifically noted there was no awkward external antenna. HP paired the device with TomTom Navigator for turn-by-turn navigation, and a separate "TomTom/HP Navigation Pack" bundle added an SD card, car power cable, and suction-cup mount. Maps weren't pre-loaded — regional maps had to be downloaded separately — and voice guidance shipped with a single voice option. Whether the receiver used network-assisted positioning isn't confirmed in surviving sources; what's documented is a standard, standalone onboard chipset.

Integrated GSM, GPRS, and EDGE

For cellular connectivity, the hw6515 used quad-band GSM (850/900/1800/1900 MHz) with GPRS Class 10 and EDGE Class 10 data — solid, broadly compatible radio hardware for 2005. What it didn't have was 3G or Wi-Fi. The 3G gap specifically got tied to the operating-system question in contemporary reviews: 3G support on Pocket PC Phone Edition devices was arriving alongside Windows Mobile 5, which only sharpened the sense the hw6515 had launched a step behind.

The HP hw6500 Mobile Messenger Family

The hw6515 was part of a broader hw6500 series, and it's a mistake to assume every model was identical. The best-documented variant is the hw6510, which shared the hw6515's hardware platform spec-for-spec but shipped without the built-in camera, aimed at buyers in camera-restricted environments. Owner discussion from the period also references additional regional and carrier-specific hw6515 model numbers, a reasonable signal HP customized the line further for different markets — though the exact differences across every regional SKU aren't well documented today.

Why hw6515 Owners Wanted Windows Mobile 5

None of this happened in a vacuum. HP's earlier h6300 converged devices had already shipped with Windows Mobile 2003 and never got an update path either, so some buyers were already wary by the time the hw6515 launched. Paying several hundred dollars for a converged phone-PDA and then watching a materially newer OS ship on competing and follow-up devices within the same year is a reasonable thing to be frustrated about, especially for a device marketed at professionals. That frustration shows up repeatedly in owner comments from the period, most pointing to the missing upgrade path as the core issue.

What Windows Mobile 5 Actually Changed

WM5 introduced one genuinely architectural change: persistent storage. On earlier Pocket PCs, including the hw6515, user-installed apps and data lived in volatile RAM, so a fully drained or removed battery could wipe out everything a user had added. WM5 moved that data into flash memory that survived a power loss while running active applications out of RAM — a real structural shift, and the single most-cited reason people wanted it. Alongside that, WM5 shipped with an updated Office Mobile suite, Windows Media Player 10 Mobile, and a somewhat faster ActiveSync 4.x sync stack. Windows Mobile Device Center, the sync tool most associated with later releases, arrived with Windows Vista and Windows Mobile 6, not WM5 itself.

The No-Upgrade Announcement

Mobility Today published the news under the headline "Official: HP iPAQ hw6500 no Windows Mobile 5 Upgrade," bylined David Ciccone and posted Monday, September 26, 2005. The piece answered a direct question about whether HP would support Windows Mobile 5.0 on its currently shipping converged products, and it named both the h6300 and hw6500 lines explicitly — not the hw6515 in isolation. It also didn't come out of nowhere; industry coverage in the weeks before had already been running "will it or won't it" speculation about a WM5 path for the hw6500 series, so HP's answer landed with an audience already primed for it.

HP's Stated Reasoning, and What Wasn't Confirmed

HP's own explanation, as published, centered on network stability rather than product strategy. In substance, HP said the h6300 and hw6500 lines were more complex than simpler Pocket PCs because they ran on live carrier networks, that maintaining stable performance there under a new OS could require hardware changes, and that since it had no plans to modify hardware on models already shipping, it wouldn't provide Windows Mobile 5 for either line. Not every reader accepted that — comment threads include owners questioning why devices with comparable specs reportedly got WM5 while the hw6500 line didn't, though this piece can't independently verify those comparisons. Also unconfirmed: exactly how Mobility Today obtained HP's answer, and any engineering-level detail behind what hardware changes HP believed were necessary. Where the record runs out, this piece stops rather than filling gaps with something that merely sounds plausible.

hw6515 vs. hw6900: The Comparison That Stung

The contrast that made the decision sting wasn't abstract — it showed up within months, in HP's own next product. HP confirmed the iPAQ hw6900 series in January 2006, its first smartphone built around Windows Mobile 5 from the start. The hw6900 kept the same basic cellular foundation as the hw6515 — quad-band GSM with GPRS and EDGE — while adding Wi-Fi, a faster 416 MHz version of the same PXA270 processor family, and roughly double the flash storage. The specific radio hardware HP had pointed to in its reasoning was still present, largely unchanged, in the very next device that did run Windows Mobile 5.

Forum discussion from right around the September 2005 announcement already referenced an anticipated "hw6700" as HP's next WM5-capable device — a codename that, based on how the timeline played out, appears to be what eventually shipped as the hw6900.

Unpredictable Updates, Then and Now

Step back and the underlying problem was bigger than one HP product line. In the mid-2000s, Microsoft licensed Windows Mobile to hardware manufacturers, who decided — on their own schedule, for their own commercial reasons — whether to build and certify a new-OS ROM for an already-shipping model. There was no industry norm for how long a device should keep getting OS updates, and for phone-radio devices, carrier certification could add another layer of approval outside the manufacturer's control. An owner in 2005 had no reliable way to predict whether a device would get a major OS update six months later. Today's phone makers, by contrast, routinely publish multi-year OS update commitments up front as a stated product feature — a genuinely different relationship between buyer and manufacturer than the one that produced the hw6515 situation.

Unofficial ROM Efforts: What Actually Happened

Given how active enthusiast ROM-cooking communities were around other Windows Mobile devices of this era, it's a fair question whether anyone built an unofficial WM5 ROM for the hw6515 or the broader hw6500 family. Interest was real and long-running — threads asking about exactly this turned up on enthusiast forums for years after HP's 2005 announcement. But based on the surviving discussion, that interest doesn't appear to have produced a working result: the consensus in those communities is that no functioning unofficial WM5 ROM was ever successfully built for the hw6500 line, unlike a number of other contemporary Windows Mobile devices that did get community-built upgrades. This isn't treating forum chatter as evidence of an actual unofficial upgrade path — only as evidence people kept asking, and that as far as the record shows, nobody ever delivered one.

Using an HP iPAQ hw6515 Today

Realistically, an original hw6515 is a collector's piece rather than a usable daily device now. It runs a Pocket PC OS from before smartphone-era app ecosystems existed, its original battery is almost certainly degraded after two decades, and in a growing number of regions carriers have shut down the 2G and EDGE networks the device depends on, meaning the phone radio may have nothing left to connect to. None of that makes it worthless — for collectors of early converged devices and Windows Mobile history, a working hw6515 with its original navigation accessories intact is a genuinely interesting artifact. It's just not a phone anyone should plan to rely on.

FAQ

What OS did the HP iPAQ hw6515 use?

Windows Mobile 2003 Second Edition, Pocket PC Phone Edition — not Windows Mobile 5.

Did HP release WM5 for the hw6515?

No. HP confirmed in a statement published September 26, 2005 that neither the hw6500 line, including the hw6515, nor the earlier h6300 line would receive Windows Mobile 5.

Why did owners want WM5?

Mainly for persistent storage, which stopped a drained battery from wiping user data and apps, plus an updated Office Mobile suite and newer media software — and because they'd paid a premium price for a device that already trailed the newest platform at launch.

What changed in WM5?

The headline change was persistent flash-based storage instead of volatile RAM-only storage. WM5 also shipped with an updated Office Mobile suite, Windows Media Player 10 Mobile, and a faster ActiveSync 4.x sync stack.

Did the hw6515 have GPS?

Yes, a built-in GPS receiver was standard, typically paired with TomTom Navigator software and, optionally, a bundled car mounting and charging kit.

Did it support EDGE?

Yes — quad-band GSM with GPRS Class 10 and EDGE Class 10 data, though it did not support 3G.

What was the HP hw6500 Mobile Messenger series?

HP's family of converged Pocket PC phones launched in 2005, including at minimum the camera-equipped hw6515 and the camera-free hw6510, both sharing the same core hardware platform.

Did the hw6900 series run WM5?

Yes. The hw6900, confirmed by HP in January 2006, was HP's first smartphone built around Windows Mobile 5 from the start, while retaining the same quad-band GSM/GPRS/EDGE cellular hardware as the hw6515.

Were unofficial WM5 ROMs available?

Enthusiast interest was long-running, but based on surviving forum discussion, no working unofficial Windows Mobile 5 ROM was ever successfully produced for the hw6500 family.

Can an iPAQ hw6515 still be used today?

Only in a limited, mostly collector sense — the software is decades obsolete, batteries are likely degraded, and EDGE/GSM networks the phone depends on have been shut down in many regions.

The HP iPAQ hw6515 wasn't a bad device when it launched — reviewers generally liked its combination of a real keyboard, a built-in GPS receiver, and solid cellular hardware in one body. What it became, within a year of release, was a case study in how unpredictable OS support could be during this stretch of Pocket PC history: an expensive, well-specced device that HP itself effectively left behind, while shipping a near-identical radio stack in a follow-up phone that got the update the hw6515 never did.