February 01, 2006
Minority OS Report

How long can it take to build an updater that executes on Mac OSX?

On 18 January, PalmOne released an updater for the unlocked Treo 650, but in the Windows build only - users of the OSX platform were advised that

Mac users: The Treo 650 Update is not yet available for Macintosh but should be shortly. Please check back for your update. When available, the Mac system requirement will be Mac OS X 10.2.6 to 10.4.x.

which is helpful, but... not very useful.

As my Treo has become increasingly unstable with frequent resets that appear to be (from various online reading) potentially hardware related ("Chunk Overlocked" errors on built-in as well as third party applications when the device goes to sleep), but just as likely poor NVRAM management related, I'm anxious to work through solutions -- this weekend will be a hard-reset and naked operation (e.g. no applications and contacts) execution, which will be a decent test I hope. If that doesn't point to a culprit, maybe the update will (time to boot the PC...), or maybe I'll have to negotiate with PalmOne for a repair. Lord knows what it'll cost - I'm out of warranty coverage, if my math is correct.

The real pity is that not 6 weeks ago I felt comfortable enough with the 650 to advise a friend it was a good purchase. It may still be - hopefully I'm an isolated case. But if not, whither? Back to the stability but poor PIM functionality of S60?

No wonder I seem to be running a phone purchase a year.

Technorati Tags: , ,

Posted by esinclai at February 01, 2006 10:04 PM |

what sort of enbuggery have you belabored the device with? I ceased such shenanigans around month 3.

Posted by: mike on February 1, 2006 11:51 PM

Ah, enbuggery. I have reset to a limited set of enbuggery a while back.... Currently the only 3rd party applications I run are Chattermail Agendus, and Verichat. There doesn't seem to be a correlation with the operation of these, though they were my first culprit.

The fact that the Chunk Overlocked errors will come from Phone, Applications, and SMSStub as well as any other apps makes me suspicious that these are players, particularly as I don't always run them in any background mode.

I do wonder if there is some flaw in the NVRAM implementation - long ago I had heard that there were some absurdly high numbers for read/write cycles on these, but if the PalmOS (particularly with the appswitching) is doing a lot of read/write cycling (open mail, delete mail, open SMS, lookup number, delete SMS, load and close a buncha apps alladamntime), maybe there's a threshold of statistics that has been crossed.

Freaking technology. Boon and bane I tell you.

Posted by: Eric Sinclair on February 2, 2006 06:44 AM

My 650 went into a crash-loop recently that wasn't cured until I found a patch for DocsToGo v8 -- the upgrade from v7 screwed up everything (esp. graphics handling). No hardware issues here, though perhaps the CDMA radio stack is more stable than the unlocked GSM (?).

Posted by: Sean on February 2, 2006 10:31 PM
Post a comment

Email Address:



Remember info?