Slashdot Mirror


Handspring Hides Flash ROM in Handspring Treo

miradu writes: "TreoCentral has just posted an intriguing article about how the Handspring Treo has Flash ROM - something that Handspring claims it doesn't. They've worked with Brayder Technology to create applications to utilize this newly discovered feature. It brings up the question, Why do developers lie about features in a device - especially if they are features that are wanted? Does anyone know any other examples?" Strange -- hardware manufacturers don't often underestimate their products' capabilities, do they?

18 of 191 comments (clear)

  1. That one is easy by fidget42 · · Score: 5, Informative

    It allows them to remove the Flash at some point in the future and replace it with a cheaper ROM. If they don't tell you that they have a Flash, then you won't complain when it is removed. I would expect the next version to be missing the Flash.

    --
    The dogcow says "Moof!"
    1. Re:That one is easy by Chanc_Gorkon · · Score: 3, Insightful

      Yes but if Handspring does not release a ROM update having it doesn't really do you any good does it?

      Joel

      --

      Gorkman

  2. And option B... by MosesJones · · Score: 3, Interesting

    This isn't _standard_ on all of the Treo's and is only used in certain manufacturing runs, so some of the things tried here could fail, or screw up the system you have. So in the specs they don't mention it as the use of FlashROM was down to a costing decision on a paticular run (maybe they bought in bulk to support other products, or had left over elements that could be incorporated).

    This is like assuming that just because one PC has a paticular motherboard with paticular tweeks that every PC has that.

    The Treo is still butt ugly mind.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
  3. Samsung i300 by The+Jake · · Score: 5, Informative

    Users of the Samsung i300 for the longest time were told that there was no flash rom, and that the operating sytem was not upgradable.

    Then FlashPro came out and proved that there was flash in the i300.

    Upgrading the OS is still not an option, considering that there are lots of propreitary extensions to the OS.

    However, the flash capabilities of the devices were hidden for quite a while.

    Jake

  4. long range vision by cr@ckwhore · · Score: 5, Interesting

    I think at least in Handspring's case, they've had a philosophy of planned obsolescense by building their products with hard ROMs.

    Obviously, they can't be upgraded that way, so in their all knowing marketing minds, they're hoping users will continue to upgrade to newer products from Handspring.

    Originally, they claimed that the lack of a flash ROM was a price saving measure, but I tend to think that in some cases, a flash rom would actually be cheaper.

    Now that the treo has a flash rom, and they're lying about it, what do they expect? Of course users are going to make use of that 'hidden feature' now!

    Handspring, you ought to 'embrace and extend' now that the gig's up.

    --
    Skiers and Riders -- http://www.snowjournal.com
  5. Just another customer support de-feature I suspect by Whispers_in_the_dark · · Score: 3, Interesting

    It has been my experience at least that companies regularly hide things I would consider features because they don't want to deal with customer support issues surrounding those features. This more often happens, so it seems, when the feature involved is either complicated or delicate (or both for that matter).

  6. Why? Support by Your_Mom · · Score: 5, Interesting
    It brings up the question, Why do developers lie about features in a device - especially if they are features that are wanted?
    Easy, one word: Support. I am quite sure that Handspring doesn't feel like supporting a million handsping Treo's where their users downloaded the lastest PalmOS upgrade that theire neighbor used on their m 505 and burnt out thier Treo. I am reminded of the PA cartoon where nintendo has to support GBAs when peoepl try to install the Portable Monopoly sytem.

    Maybe they planned to tell us later, maybe its a fluke and is only in certain models. Who cares?
    --
    Objects in the blog are closer then they ap
  7. VW does this with their cars by qurob · · Score: 4, Interesting


    Take a look at the cars with the 1.8 Turbo engine.

    By changing the ECU programming, they can add power by adjusting boost pressure, air/fuel/spark maps...

    The car can magically gain 10-20hp between model years, all with the click of a mouse.

    Aftermarket ECU tuners can get the same results out of the cars that are just a few years older.

    But, "15 more HP than last year" is a great selling point for a car.

  8. My favorite quote by mdahlman · · Score: 5, Funny

    My favorite quote from the article:
    I ask all these rhetorical questions for a reason: I want to know what you think.

    er... you keep using that word. I do not think it means what you think it means.

  9. Palm OS licensing issue perhaps? by topham · · Score: 4, Interesting

    Whats the chance they license Palm-OS on a reduced rate because it isn't 'upgradable'?

  10. Some Earlier Examples by twisty · · Score: 5, Interesting
    > Strange -- hardware manufacturers don't often underestimate their products' capabilities, do they?

    It's common for the aspirations of engineers to be lobotomized a little by the larger marketting beast. I've read several articles on the web where a Celeron motherboard could be greatly sped up by placing celophane tape over a single pin of the Celeron's card edge connector. But then we stray into the area of overclockers...

    THE EARLIEST EXAMPLE that springs to mind is on Radio Shack's TRS-80 Color Computers. There was some story about doubling the RAM by bending two pins on a socketted IC chip. The story was that the onboard capacity was crippled for the sake of easy in-store upgrades.

    1. Re:Some Earlier Examples by alienmole · · Score: 4, Informative
      That might be the earliest example in the "PC" industry, but IBM was much earlier - they used to (perhaps still do) charge big bucks to perform "upgrades" on customer mainframes by enabling hardware that was already in the machine.

      Mainframes would ship with various disabled features. Remember these were room-size devices (well, multiple large cabinets which would fill up a big room). When the customer wanted an upgrade, an IBM technician would be sent out, he would rearrange some jumpers, enabling a feature, and the customer would receive a bill for e.g. $100,000 for a memory upgrade.

      IBM made no apology for this: you were charged for the functionality you received, and the fact that the "upgrades" already existed inside the boxes in your computer room was irrelevant.

      So perhaps one can blame IBM for having started the ball rolling on the idea of strong control of "intellectual property" by the vendor... I wonder if anyone back then "hacked" their own mainframes?

  11. Hardly unheard off by SmallFurryCreature · · Score: 3, Interesting

    Happens all the time. CPU's are one extreme example. Early Intel celerons had the hidden capacity to be used in a multi processor setup. This was only changed when Intel noted that a lot of users where opting to buy two dirt cheap celerons rather then the overpriced PII(I) they wanted you to buy. Same with overclockin. It is easy enough to accomplish with an AMD chip, don't have Intel myself anymore so couldn't say, but AMD sure as hell ain't telling users about it. I started my IT career on the PROGRESS platform, RDMS and 4GL in one. Their monitoring tool had a "secret" section I only learned about when a rep visitid for some testing.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  12. Why do developers lie? by Bigfishbowl · · Score: 4, Insightful
    >Why do developers lie about features in a device
    The developers of the hardware usually aren't the ones who are lying. I work for a fairly large company and I can safely tell you that the engineers (that's me) don't sit around and plot to hide features. The way it usally goes down is that some guy in marketing gets a hold of technical documentation that is being developed along with the product. Once he gets it, he gives us a call and starts asking if feature so and so should really be documented. One thing is for certain though, marketing seems to get the final say as to what gets published and what doesn't.

    The corperate benifit of some of this stuff is fairly easy to see. For instance, say we make a chip called the Wizbang 3900. Now, this chip is going to be released in the 3901, 3903 and 3909 flavors each with different features. Since a run through the fab can cost upwards of $500k, it is much easier to just make one version, then just label them differently. The same thing is true with the development boards. A lot of times the board is only populated with the parts to allow that feature set. By populating more/different parts of the board, different features can be achived with out requiring a different board spin. All of this saves money and development costs, but does lead to some documentation holes.

    So in short, blame it not marketing not the engineers. We're the good guys.

    1. Re:Why do developers lie? by martyb · · Score: 3, Informative

      The developers of the hardware usually aren't the ones who are lying.

      Agreed! I've seen that happen more than a few times. Thought it might be useful to add another possible reason why some features are hidden.

      My expertise is with software (20+ years in QA), not hardware, but I've seen the hiding of features happen several times. In my experience, the develpment cycle starts off with marketing making its pitch for what needs to be in the product release, and development pushes back with what is feasible in the time frame, as well as what they would like to do. There's some negotiation, and then development goes off to "do their thing". And all is happy and good.

      Then QA appears and does its thing. Sometimes QA is called in right from the start; other times the product is almost ready for release and someone thinks it might be good to have QA look at it before it is shipped tomorrow. I actually have seen a few projects released on time, under budget, and with the promised capabilities. But, that is sadly the exception rather than the rule. Even with an early participation by QA, there are often far more developers at work than QA people. The number of possibilities goes up exponentially, and there's just not enough time to test everything as it is developed. Design errors and implementation errors are found. Rework is required. Deadlines loom. All is not as happy and good as it once seemed. And then it happens.

      Maybe it's a nasty memory leak that builds up over time. Maybe there's a variable that gets corrupted, eventually. And there's not enough time to isolate it and fix it. So, instead of yanking out all the questionable code (which would introduce its own bevy of problems), the common approach is to just remove access to it (e.g. removing a choice from a pull-down menu) and, of course, removing all reference to it in the documentation.

      So, there's quite possibly some hidden functionality in a program (or a piece of hardware), but it was hidden for a reason. If you're a bleeding-edge kind of person, go have fun. In light of your particular circumstances, it might well seem to work okay. But, if you need to be able to rely on the application or system, it might be a Really Good Idea(TM) to use only the documented features. You might miss out on some helpful features, but you might also save your butt.

    2. Re:Why do developers lie? by alienmole · · Score: 3, Funny
      But, if you need to be able to rely on the application or system, it might be a Really Good Idea(TM) to use only the documented features. You might miss out on some helpful features, but you might also save your butt.

      Darn! You mean I shouldn't be using the hidden "overclocking" option I found on my pacemaker? But I feel so alive with my heart going at a steady 180bpm all the time!

  13. And then amazingly in 2 years your engine fails! by sheldon · · Score: 4, Insightful

    Do you seriously thing that an automaker would advertise their engine as having only 140 hp if with a small software change they could get 160 hp? I mean come on.

    No, they spec the engines out based on a number of factors relating to emissions, fuel economy and reliability. So by tweaking you adjust the compromise. Automakers do refine engines over time to gain more power, but they try do so in ways that don't effect it negatively. By that I mean, decreasing reliability or not allowing the car to meet US regulations regarding emissions and fuel economy.

  14. Re:And then amazingly in 2 years your engine fails by Wolfier · · Score: 4, Interesting

    >Do you seriously thing that an automaker would
    >advertise their engine as having only 140 hp if
    >with a small software change they could get 160
    >hp? I mean come on.

    Single brand (Porsche, BMW) companies usually don't - but those who have luxury brands and ordinary brands (Toyota, Honda, VW, Nissan, Ford, GM...) do. They want to share parts to reduce cost, but have to intentionally downtune the cheaper brands to prevent it from competing with its own luxury brands.