Ditto to
MissionImprobable's suggestion, with a caveat (see below). For the record, SBF re-flash of the .622 Andriod 2.3.4 stock VZW build on my R2D2 produced interesting results, but not a full resolution for my buggy touchscreen... It works intermittently now, but usually just has a conniption (therefore the hardware is toast).
I've installed a workaround (I will explain how I did it
toward the end of this post) Android app called "
Argotronic Lock Screen / Disable Touch," which at least allows me to do just that: disable the touch input feature on R2D2's screen. I have it set to enable/disable this toggle upon shaking the phone. Unfortunately it also re-enables the touchscreen after the screen times out (once battery saver kicks in) and when calls are received, and since my screen begins "touching itself" (how icky does that sound?? oops, am I disturbing you, Artoo? Nobody wants to see that!!!), it means that when my phone buzzes or rings, it wakes up the screen, potentially unlocks itself by "touch" and begins performing unapproved actions, or if the screen is on at the point R2D2 is in my hip holster case, simply walking can "shake" the screen enough to re-enable the touchscreen to begin the whole circus again. I repeat: What fun!
The shorter story: YES I will be replacing my phone, but cannot afford to pay the Asurion deductible ($99) at the present. So instead, I'm seriously considering waiting until my upgrade discount from VZW (subsidized upgrade price) is available in October, weighing the cost of "discounted upgrade price" vs knowledge that I would lose my current unlimited data plan by gaining a lower price on a Droid 4 at that time, or just bypassing VZW to snag a replacement phone (new, used, or refurbished) on eBay. I'm trying to be sensible about this because after all, R2D2 was a FREE PHONE at the time I adopted him, but I've become so dependent on this battle-worn device for business, entertainment, etc. Just stuck for now with his bad behavior.
Latest frustrating example was taking photos of my son at the big Air Show yesterday, camera app decided to start applying effects, like solarizing just before I click the camera button, or tinting everything green (coincidentally the air field lawn and most of the Army National Guard vehicles were of course already green, so great sense of humor there, Artoo!). I could easily shake the phone each time I woke the screen from standby, using this new app to disable the touchscreen at that point, but some features are touchscreen dependent, so adjusting back to "normal" effect required wrestling the possessed touchscreen for control. Bah!
So, to install that app (or any other, really), log into Google Play from a computer, using your Google/Gmail credentials from the phone (which if you've wiped and reloaded R2D2, you probably have that username and password memorized, right?). From the web browser version of Google Play, you can use my link (above) or search for "touch screen disable" in the market, locate the app and choose INSTALL agreeing to the various permissions and prompts at your discretion. This is just one option, but if you choose to install this way, it will push the app to your device without you having to operate the phone's touchscreen. Now, once it's installed (or anything like it), you'll have to access the app from the device itself to first-time enable it or change its features. I found with gritted teeth and squinting one eye, I could manage to fight the screen just long enough to use the keyboard slider to arrow down to "shake to enable" and exit the settings screen, shake the phone, then go back into the app (arrows and OK button, physical keyboard again), then finally scroll the other settings and preferences. Your mileage will almost certainly vary.
I'm willing to be extra patient with this madness because it's not in my budget to buy a new phone, nor pay the deductible to get a refurbished version from Asurion (especially knowing that +$60 gets me a NEW unopened R2D2 on eBay right now, which
*ahem* nudge to MissionImprobable here, would also mean it has the ORIGINAL shipped Android 2.2 OS, completely corruptible for root and alterna-ROM goodness
, who wants a refurbished R2D2 already arriving with 622 locked down firmware & bootloader, really?:blink:STOP THE PRESSES, LOOKS LIKE
622 ROOT IS NOW POSSIBLE?? Thank you in advance to
jedifire11 if that tip works out!)...
Now I WOULD like to call Asurion and have a Droid 4 sent to me as replacement for this R2D2, whether the D4 is refurbished or not I probably wouldn't care, but realistically I know that won't happen. Most recent "replaced R2D2" post I read (on
Official R2-D2 Owner's Thread) said that owner
received a refurbished R2-D2 with 622 already loaded on it (no thank you!). I would also like to call GM and have them swap my Chevy 2006 HHR for any Chevy Traverse, Buick Enclave, Saturn Outlook, or GMC Acadia with 3-row seating and AWD, but that's equally unrealistic.
And so I digress and wait it out as long as I can manage this workaround and not throw artoo "accidentally" while shaking to disable the touchscreen. *sigh*
PS.
KelleyElston: if you DO get anything other than an R2-D2 from Asurion, please let us know!
K ... Also just realized I misspelled you when I said "Welcome" so I'll go edit that now :biggrin:
