Wasn't sure where to post this, so i'm starting here; confident someone will re-direct as appropriate.
I've got a stock My-Touch-3G (i.e. not rooted/jail-broken). Recently the response to standard buttons changed drastically: *Regardless of applicat state (awake, sleep, active application, ...) the Home button no longer as any visual affect. If the phone has gone to sleep, the home key will wake it up to the home activity. *Regardless of settings, the keyguard lock screen never appears. I believe the class is still partially functional because when tried things like turning it off then on, i do get the pattern input view and can succesfully stroke my key). I can press any key (including end) when the screen turns off and it just brings the screen right back up (whichever screen/application I was on last). This is the same whether it times out or I hit End. *The Search button is equally as ineffective as the Home button, only functioning to turn the screen back on. *Holding down the End button no longer gives me the options of Silent/ Sleep/Power. Only Power is available. WORST: there is no visual or other indication of an incoming phone call. Any incoming call is routed directly to voicemail. Notification of voice mail appears normally. Messaging works fine, all outgoing connectivity appears to be functional (phone calls included). (I borrowed most of that description from http://androidforums.com/t-mobile-mytouch-3g/12021-home-search-buttons-not-working-not-sleeping-locking-properly.html ) I'm a begginner at Java/Android but with the help of a little searching and browsing of platform source, looking at dumps from adb I found two things: 1) comment in source (WindowManagerPolicy.java): /** * inKeyguardRestrictedKeyInputMode * * if keyguard screen is showing or in restricted key input mode (i.e. in * keyguard password emergency screen). When in such mode, certain keys, * such as the Home key and the right soft keys, don't work. * * @return true if in keyguard restricted input mode. */ 2) in one of the dump logs from my phone: 02-03 10:05:55.222 I/CallNotifier( 121): CallNotifier: rejecting incoming call: device isn't provisioned Summary: somehow one or more key-value in the security table /data/ data/com.android.providers.settings/databases/settings.db were changed. This is obviously happening enough to appear on blogs, support forums, and similar venues. Really bad publicity, really bad that the most common suggested solution is to Factory Reset the phone. I tried accessing the table via adb tools and realized that I didn't have proper permissions. Figured it would be no big deal to write a 10-15 line piece of code to reset the value, but I don't know enough about signing APKs to give the code the necessary access permissions to do it. CAN ANYBODY PROVIDE CODE OR APK TO FIX THIS? Would really be nice if such a one-time-only apk was available via market for customer base!!!! (Not sure on the business/politics/release managment aspects of this?) WOULD ANYBODY BE WILLING TO HELP ME figure out which applications on my phone are candidates for further debugging to find the bug? If a level of trust can be established, I have no problem allowing SSH and other access to my development platform (currently ubuntu+eclipse) and my phone. thanks jeff knaggs I logged all of this info (and more!!) as comments to android/issue #4358 (it looked like the person that created 4358 was experiencing this, just didn't fully describe it). -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
