[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Hi ZR, this is me again. :)

Since i've upgraded to 2.1 i always have the same problem.

I have AutoLockOnPowerOn=0 in TLA & in Registry entry also of course ( UseTAPI=1 & LockIncomingCalls=1) but my device always ( always means always for me) locks my TP when turning it on, not only in incoming calls.

In 2.03, it worked fine, but there was the "can't turn on Device because it is locked while screen is off" that you fixed it due my old logs i sent you some days ago.

I've tried everything, including to unistall it, delete TLP related registry entries and reinstalling it again & configuring it from scratch. Nothing works.

I attach the new logs for you, to see if you can figure it out what's hapenning.

Another problem i have is that sometimes ( 10-20 times per day at least ) the capacitive middle area (CapacitivesTouches Sequence=22) doesn't detects my finger taps & I have to take stylus out to have my TP unlocked. BTW i also have running Gscroll, so maybe it could negatively affect TLP's behaviour. TLP 2.03 used to be a bit better but also used to occur this from time to time.

For the AutoLockOnPowerOn=0 locks problem, i don't give you exact time details becasue it occurs always, each time you see in my log a lock when turning device on, then there is where the problem occurs becasue i always have AutoLockOnPowerOn=0.

For the "not always responding capacitive area, i give you these concrete times:

at 11:40 it happens once, to unlock i have to take stylus out

at 12:27 the problem happens twice consecutively, to unlock i have to take stylus out in both cases.

at 12:27 TLP detects one tap but not the second one (CapacitivesTouches Sequence=22), to unlock i have to take stylus out

at 12:28 TLP detects one tap but not the second one (CapacitivesTouches Sequence=22), to unlock i have to take stylus out

at 12:29 TLP detects my 2 taps and then it unlocks my device ( Well done this time!)

thanks as always!

edit 1:

this is really weird, since i've disabled TLP to copy the log for you, once i've enabled it again, for first time, TLP starts to work as it should,

AutoLockOnPowerOn=0 and now TLP doesn't lock my device when turning it on.

let me test it during some time more and also do some soft resets to see if this correct TLP behaviour continues overtime or it jumps back again to the before commented bad behaviour. So at least for now, it seems that to disable and to re-enable TLP fixes this "AutoLockOnPowerOn=0 but locking device" bug.

edit 2:

after some more testing the problem comes back again without doing any softreset between it worked fine some minutes ago and now that it starts to work bad.:

12:52 the "AutoLockOnPowerOn=0 but locking when turning device on" comes back again by itself, i unlock it sliding keyboard

12:56 incoming call. device locked but i can't unlock with "22 tap sequence". stylus out to unlock device

12:58 incoming call. device locked but i can't unlock with "22 tap sequence". stylus out to unlock device

13:01 the "AutoLockOnPowerOn=0 but locking when turning device on" continues occuring and only one tap of the "22 sequence" is detected

13:02 the "AutoLockOnPowerOn=0 but locking when turning device on" continues occuring and only one tap of the "22 sequence" is detected

13:04 the "AutoLockOnPowerOn=0 but locking when turning device on" continues occuring and only one tap of the "22 sequence" is detected

edit 3:

the weirdness occurs again, since i've disabled again TLP to copy again the log for you, once i've enabled it again, TLP starts to work as it should,

AutoLockOnPowerOn=0 and now TLP doesn't lock my device when turning it on. Let's see how it lasts! this is crazy!

i leave attached the last tlp.log file that includes everything i comment in this post. the old one is substituted by the new one.

edit 4:

after a while tlp comes back to behave badly as since 2.1 release use to do for me: "AutoLockOnPowerOn=0 but locking when turning device on"

(i use Proven Rom 1.11)