[Touch Diamond, MDA Compact IV Themes and Apps] AboveTheBULL:
Sounds *great*! :D I look forward to trying it!

At least for me, the zoombar "swipes" are really easy to accidentally do. It isn't like the Nav sensor was on my TP, where it was a smooth and predictable motion -- it is more like just another section of touch screen that doesn't really register consistently. In fact, I hate mine and never use it, lol. BUT when I am picking the phone out of my jacket pocket or from the belt pouch thing, even when I don't touch it with my hands, the action of the case rubbing against it must be activating it.

EDIT: Aha! I just tried it -- it does not need to actually be "swiped" to unlock. I took the first three fingers of my right hand and placed them at left, middle, and right sections of the zoom bar. Then I tapped each in quick succession, left - middle - right, and guess what? It unlocked. I did this a couple more times, and I can consistently get it unlocked in this way -- by just tapping on the zoombar. Something similar to this must be how it is being triggered accidentally... and maybe because of this, those points maybe are live at the very bottom of the touchscreen directly above where the zoom bar begins... ie. the lower section of the softkeys...

Interesting. I turned on the bluetooth headset during that log, so it should have shown up correctly.

I will do a new log file just to make sure. But just to be sure I understand, are you looking for bluetooth "enabled" or "active"? I say this because on my phone, bluetooth is always enabled, even when I do not have a bluetooth device connected. Perfect example is my headset. When I want to use the bluetooth headset (maybe for a trip in car or walking around in public), I just turn it on, let it automatically connect to the

already enabled phone

, and then use it for that time. Then when I am back at home, I turn headset off and stick it on its charger, then use my phone as if no headset is on it. But I leave bluetooth enabled on my phone. Maybe I will want to send files from my computer to it -- I don't want to have to go into settings, enable bluetooth, and then send file. So I leave bluetooth on always...

I give all that scenario, because when bluetooth is

enabled

(but not necessarily

active

) on my phone, HTCLockAPIWhenBluetoothActive=1 will enable the HTCLockAPI.

Aha! This is HUGE progress, I think! It never occurred to me that it would be important, but on this phone, there is some kind of built-in automatic profile system. I say this because when I connect to a call with my bluetooth headset, it automatically changes the volume to whatever it was set at in last bluetooth conversation. Then, after I hang up, it returns it to whatever it was before. Of course, I would never have known this, except when I connect to call with bluetooth headset, for a moment I see the volume screen with the slider moving to the automatically remembered position... although I am not doing this myself. (BTW, this is a stock Sprint Touch Pro2 with original ROM -- nothing special. It works like this even on hard reset.)

So maybe this is what has been confusing TLP. Maybe the volume up (or down) that is automatically done by system when answering with bluetooth headset is disrupting things. I am going to try unlocking the volume buttons in settings and see if that helps...

EDIT: It didn't help. In fact, unlocking the volume buttons (UnlockedKeys=118,117) just caused the volume screen to come up on-screen when I pushed a volume key and the phone was already locked by TLP -- but the volume slider never moved no matter how long I pressed or how many times. If I unlock it, volume keys work normally. I had the unlock sequence keys removed before I tried this (as well as a soft reset), so it wouldn't be looking for any unlock key sequence.

EDIT #2: Also, on this phone, there is only one volume slider by default, not two (System and Phone) like on other WinMo devices. I imagine it just makes volume same on both System and Phone when changing, eliminating need for two separate sliders (come to think of it, I miss the old 2 sliders, LOL). Now, there *is* a system setting to change that back to the old way, but it is not enabled by default. I do not know if this has any bearing on volume command readings, but I just thought I'd let you know...

EDIT #3: I also notice that when "unlock key sequence" is cleared of the volume up and down keys and they are instead placed into "unlocked keys", it is MUCH easier and more consistent to unlock with zoom bar. I wonder why this is? Maybe I am just sleepy -- I will try this one again in the morning...

This I will do for normal operation, because it will get the job done. But when I get home and can test, I will put it back to not use HTCLockAPI, so I can help figure out why the TP2 is being so stubborn. :) Hopefully you won't mind!

BTW, I have typed so much now, I have gotten very sleepy. LOL. I will update with a new debug log later today. If there are specific things you want me to do in the log, let me know so I can proceed in a manner that will best help...