Are you actually even in possession of a HERO??? Flaw, flaw... FLAW... flaw, flaw... blah, FLAW...
Believe me, you're not the only one laughing.
What's your deal? First you jump on me for not knowing an app was part of the problem. If I didn't know an app was capable of altering that behavior, how would I know that info was pertinent? If I knew that was the problem I obviously wouldn't have asked for an answer, would I? Should I fully list all apps, number of pics, contacts list, and wallpaper pics every time I have a question about a problem to make sure I included all info that might possibly be pertinent? Yet despite your assertion, I received a "proper" answer on the third reply to this thread even with my egregious oversight. I suppose you didn't read that part.
Second, you accuse me of not owning a Hero. wtf? Do I need to include, in addition to the full disclosure off apps, pics, ringtones, contacts, browsing history, and emails that might possibly be pertinent, a notarized picture of my Hero on top of a picture of me, my social security card, and perhaps a birth certificate?
Third, what's your infatuation with the word "flaw" and your need to emphasize it and define it for me? I never used the word. Again, I think it would help if you read before posting your knee-jerk fanboy responses. I called the problem a combination of bad hardware design and bad software design. A flaw is when something does not work the way it was intended, i.e. broke. Bad design can work just as intended... even if that intention was not well thought through. Buttons that can be depressed in pocket are a bad design, even if the button is working perfectly well and does exactly what was programmed when depressed. Software that allows inadvertent button presses to unlock the phone and do weird things is also designed poorly, even if no bugs are present.
I'm glad to know that lock2.0 was causing the battery drain problem with the trackball. Thanks to the helpful poster who brought that possibility to my attention. Again, it looks like my options are to deal with inadvertent unlocks from double menu presses, use the pattern unlock, or get a case. I'm leaning towards the latter. I've tried the pattern unlock and just hated it. I couldn't get it to recognize a quick natural swipe... it required a slow deliberate motion. I'm often in a situation where I need to pull up a piece of information now
, and the phone is slow enough already. Yes, just a few more seconds is going to make me look bad and raise serious eyebrows. The double menu press with the stock lockscreen had already caused me problems, which is why I had lock2.0 installed, which at least required an on-screen tap after the menu press instead of two menu presses successively (which seemed to happen way more often).
A case isn't a bad suggestion. I hadn't seen any in stores that I really cared for, but I'm going to check out some of the suggestions in this and other threads now that I have exhausted other acceptable alternatives. Oh, and wait for apps to be upgraded or new ones written that give more selectable control over what buttons and how unlock the phone. Or give up and figure out how to write one myself - for now, I don't have the time to learn the development environment.