[Touch Diamond, MDA Compact IV Themes and Apps] AboveTheBULL:
Thank you so much for the quick response! I love this!

Interesting. So, when I look at the debug log, I should see the key(s)/command(s) sent when I pressed the bluetooth headset button as the phone rang? I am looking thru the one I sent in my last message, but I don't see where it gives this information. :( Can you help me know what to look for?

I also want to understand fully -- so when an incoming call rings the phone and I press the button to answer on my bluetooth, a command is actually sent somewhere on the TP2 to answer the call? But this is being blocked by the TLP? But then why is the audio redirecting to the headset instead when pressing button? Could it be that *part* of the command is working (the audio re-routing) but the other part is being blocked (the answering the phone part)? And why can the still unanswered call be successfully hung up by pressing the bluetooth headset button again (it's like the phone is thinking the call is actually answered and in-progress, and I am pressing the button to hang up... So it does.)

Is there a way I can help you know which command(s)/key(s) is being blocked? I want your program to continue to grow, because it is AWESOME!

Could it be related to whatever is allowing the screen to be unlocked in the upper RIGHT corner (task manager area)? Because the softkey areas ARE locked securely EXCEPT that one small section on the left bottom. It is actually hard to get it to press when locked, but a very small section (maybe a pixel or two) has sensitivity... and camera starts up!

Do let me know how I can help. I will do everything I can!

EDIT: Oh! I also remember this -- the left bottom softkey area is EXTREMELY close to the zoom slider. In fact, sometimes I press it by accident. Something I realized a couple weeks ago was that the zoom slider does NOT seem to function right with the "Nav Sensor" controls -- instead, it acts like volume up and down to TLP. I disabled "Nav Sensor" settings in TLP because they never would work right on TP2. But then, with just 118,117 in Keyboard options "UnlockKeySequence", a swipe from right to left on the zoom bar would unlock the phone. Just thinking it was a fluke or bug in the Nav Sensor controls, I changed it to 118,117,118 and then a continuous swipe from right to left to right on the zoom bar would unlock.

So... maybe the soft key issue isn't really the soft key. Maybe the zoom bar is unlocked and a small portion maybe overlaps the bottom left section of the screen, exposing a small unlocked area of the softkey. If this is the case, then maybe the other softkey also has same problem but I just didn't see this yet.

EDIT #2: Aha! It does! Both of them are unlocked at the very bottom (or with multiple presses to the area)....

EDIT# 3: Odd. I take out 118,117,118, save, and soft reset... and it does not matter. Swiping back and forth on zoom bar unlocks. So there was no correlation between unlocked volume keys and zoom bar... It's just the zoom bar remains unlocked even when no Nav Sensor settings are checked........ I really think this is why the extreme bottom of our TP2 screens has sensitivity when locked..........