yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Glad you like it again! About the SMS wakeup: please read the post above yours, my first reply.

Yeah.. Complete weirdness. It gets the call (the TAPI message) but fails to lock somehow. As if it does not want to lock the LCD screen with TAPI messages.

It shows how to press the keys, unfortunately not how to catch them. However, thank you very much for the effort, it greatly helps if people think along like this! :)

I thought I heard NoBody20013 say this as well, with respect to HomeZone calling.. It is a weird anomaly I guess, Answerkeys Disabler actually does not disable the answerkeys (hehe), it just disables the touch screen. It does not affect the phone program afaik.

I don't have a CDMA phone, could you please try and see if it works?
[Touch Diamond, MDA Compact IV Themes and Apps] triakom:
Everything works fine.

I need only one option more:

go back to the previous state

after

the call is ended.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
It does as far as I know..
[Touch Diamond, MDA Compact IV Themes and Apps] StarMonkee:
Had some problems since my morning sprite backup (which restarts the phone).

Even in standby, when a call came in, it didn't lock the screen. The app was running because when I selected it in the start menu it asked if I wanted to disable it.

The only way I could get it to work was to disable and re-enable it.

I've just tried a manual restart and it worked fine, so it doesn't look like it's a permanent problem. It just leaves me a bit worried that I can't trust it all the time.
[Touch Diamond, MDA Compact IV Themes and Apps] Lordsori:
has somebody had problems with panosha 2.0 or 2.1 roms?

basically it does not wokr altough it says is working. It works perfectly with panosha 1.8

thanks
[Touch Diamond, MDA Compact IV Themes and Apps] BerlinTop:
Just installed v 0.5. Works great.

One minor thing: When installing 0.5, the installation gives me an error message saying, it couldn't disable AKD to uninstall the old version (German ROM) - although after clicking ok, it does the job. So, its more of an optical, rather than a functional bug.

Cheers
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Yeah, that also has to do with the program file finding... Wait a minute.. Haha great, you just found a bug! :p I'll fix it right now, but won't release a new version for this just yet. You will get this message again when installing a future version, but after that, you won't anymore.

Thanks!
[Touch Diamond, MDA Compact IV Themes and Apps] BerlinTop:
I can live with that, no problem at all...great thing to be able to configure the behaviour of AKD - that does the job for me, and I can leave the stylus in place in most all thinkable scenarios...
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
why don't you ask Panos in his forum?

you will have more luck finding people using his ROM there
[Touch Diamond, MDA Compact IV Themes and Apps] metalbrother:
Works like a charm
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Really? Great, thanks for testing!
[Touch Diamond, MDA Compact IV Themes and Apps] Polluxus:
Great that we can change some options. Though, after a soft reset (not the first one after installation) the new AKD didn't run/work so it wasn't locking my screen. When I clicked the AKD program icon it said it was running and if I would like to stop it. After another soft reset it was functioning normal again.

Very odd, I'll see if it happens more often.
[Touch Diamond, MDA Compact IV Themes and Apps] StarMonkee:
It happened again for the first incoming call after the sprite backup reboot this morning :O
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
That's not too good. Could you remove answerkeys disabler tonight and see if it happens again tomorrow morning? If it does, it's not answerkeys disabler related. If it does, I don't know why but will investigate
[Touch Diamond, MDA Compact IV Themes and Apps] boltun:
did not work for me

sorry for the delay, was away few days.

i have installed answerkeys disabler v0.4.1, after installation and checking that its running, i still am able to answer calls through the touchscreen, mean to say the touchscreen is not disabled when i get a call.

i have now installed V0.5 and called from my other phone was not able to answer via touch screen, but when i called from my landline i was able to answer via touch screen.

will check out V0.2 and a few other versions

however i have updated the software through orange and now i do not get a ring tone when i get a call. In vibrate and ring, i get only a vibration when i get a call. i will check on xda for this

thanks for ur time
[Touch Diamond, MDA Compact IV Themes and Apps] lony:
Great idea and app! I had problems with heavy battery draining on 0.4.1 and will now try the 0.5.0 - thumbs up!
[Touch Diamond, MDA Compact IV Themes and Apps] triakom:
I found a bug and went back to sensorlock. I don't know if it happens only to me.

After two successful call pickups (the phone in standby mode), the third time the touch screen is no more locked and anserkeydisabler 0.5 is running in the background. It practically stops to work. After soft reset works fine.I have tested and it happens again.

1.93 official rom.

UnlockWithStylusEnabled = 0

LockCallsDuringCalls = 0

LockOnlyFromStandby = 1 (only lock when the phone was off)

TurnOffScreenMode = 0

TurnOffScreenMethod = 0
[Touch Diamond, MDA Compact IV Themes and Apps] ariminvm:
in Dib 1.4 Lite ITA they work together perfectly!

good work drvdijk !
[Touch Diamond, MDA Compact IV Themes and Apps] Windza:
Interestingly enough - I can't get 0.5 to run on the P3720 (Australian Version). I'm running SwiftBL 7.0 ROM but don't think this would be causing the issue.

I don't get any errors whatsoever... it installs fine from both PC and .CAB but doesn't appear to run (nothing in the task manager and yes - I've reset after each install).

I'm yet to try the older versions...
[Touch Diamond, MDA Compact IV Themes and Apps] metalbrother:
Same here, only my phone was off. Sometime it works, sometime doesn't.
[Touch Diamond, MDA Compact IV Themes and Apps] Shouma:
All is working perfect but there is a bug when a waiting call comes in...we can switch for the 2nd call but there is a problem specially if TurnOffScreenMode = 2 bec. the program thinks when i accept the 2nd call and hold the 1st one that i finished the 1st call and turns off screen..so if I want to go back to the 1st call I have to use power button put on screen then press answer button again to switch to the first call...

Thanks drvdijk mate for your hardwork anywayz...but no deny you solved a great issue in the mob :)..hope the update solve the bug also. Thanks bro.
[Touch Diamond, MDA Compact IV Themes and Apps] StarMonkee:
I haven't noticed my original problem happening any more, but I've got a more worrying one which seems to be completely at random.

Even when the app is running in the background, there are times when it doesn't block the screen when calls come in - I'm pretty sure when I was using v2.1 it worked reliably 100% of the time.
[Touch Diamond, MDA Compact IV Themes and Apps] mgear356:
2nd that seems liek sometimes it doesnt lock screen
[Touch Diamond, MDA Compact IV Themes and Apps] Polluxus:
Same here. Sometimes it locks sometimes it doesn't. Didn't happen to me in the previous version.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
How are you calling from a land-line? Are you using Homezone by any chance? There apparantly are some problems with that, allthough I really don't know why.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Trying right now with these settings. I was not able to reproduce this situation. My phone is NOW ringing for the forth time, with the on-screen buttons disabled.

How I tested: I disabled answerkeys disabler, changed the settings according to what you posted, and enabled answerkeys disabled. I then called while the phone was still on, I could answer using the touch panel. I then turned off the phone (power button), and called again. Locked. Answered with hard keys, said "hi", and hung up. Turned off the phone again with the power button, and called again. Same story: cannot answer using touch screen, but I can with the hard-keys. I just repeated this four times, and it still works. Let me try a fifth time: I can't use the touch panel. Let's wait for the device to turn off by itself after 40 seconds... ... ... (you can type a lot in 40 seconds!!) ... (have I told you about that time the bird went out of its cage and ...).. Ah, it's off now! Sixth call. Answerkeys disabled!

Sorry, I just cannot repoduce your situation!
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Answerkeys Disabler does not show in the default Windows Mobile task manager, since it does not have a window. You can check if it runs by using a complete task manager such as FdcSoft TaskMgr, or by checking if clicking the program from the start menu ONCE pops up a dialog box "Do you want to disable Answerkeys Disabler".

This is something for the todo-list, pop-up a dialog box if Answerkeys Disabler is clicked from the start-menu, indicatng it has started correctly.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
I could not reproduce this on my phone either... It always shows the dialer. Maybe that's ROM dependant? I'm using SwiftBlade 7.5 Full with the default HTC dialer.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
My settings right now:

LockCallsDuringCalls = 1

LockOnlyFromStandBy = 0

TurnOffScreenMethod = 1

TurnOffScreenMode = 2

UnlockWithStylusEnabled = 1

So it was on. I call with my other cell, and answer using the hard keys. The device stays on (TurnOffScreenMode = 2 after all). I manually power down the device in the call. Then I call using another phone (Skype, actually), and answer that using the green hard-key (touch screen is disabled). The device indeed powers off directly (it was powered down during the first call). However, I can switch from one call to the other with the hard keys, even though the device is powered down! It wakes up for an instant, switches over to the other line, and direcly goes back to sleep again. Hanging up is possible with the red hard-key as well.

In short: I think the current behavious of the program is (accidentally) correct: I can still switch over while the device is "turned off". Accidentally correct, since I didn't realize this was a possibility, but it does work :p
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
All right you guys, this is a nasty situation! First I want to know if you are absolutely certain you completely understand Answerkeys Disabler's working: it disables the touch panel ONLY if the device is off. There is one exception: if you changed the LockOnlyFromStandby setting to 0.

This is the non-random part for which I can explain why Answerkeys Disabler does not lock the touch panel. I think this is correct behaviour, and you can change this behavious by making changes to the settings in the registry.

Okay. I know at least one of you does quite well know the working of the program. WHY does Answerkeys Disabler omit to lock the touch panel? Is it other software running at the same time? The ROM running? Hmm.. Could you answer the following questions:

After Answerkeys Disabler omitted to lock an incoming call, does it lock other calls afterwards? i.e. is the program still running?

What are Answerkeys Disabler's settings in the registry? Did you change any?

Are you running other software that has anything to do with device locking? (sensorlock, styluslock, .... default windows mobile locking settings)

Which ROM are you running?
[Touch Diamond, MDA Compact IV Themes and Apps] StarMonkee:
1, I'm not 100% certain, but I think that it's not a permanent problem. ie if it doesnt lock a call, I don't believe that it will not lock any others until its restarted - I can't be sure though.

2,

LockCallsDuringCalls 0

LockOnlyFromStandby 1

TurnOffScreenMethod 1

TurnOffScreenMode 0

UnlockWithStylusEnabled 0

3, I have the standard windows mobile lock set to lock the device when it wakes up (done through batterystatus). The HTC dialler unlocks the WM lock automatically when a call comes in whereas answerkeys disabler keeps the touch screen locked.

4, Stock Orange UK 1.93 (which is just the HTC 1.93 modified to be accepted by the Orange SPL).

I've done a few tests, and I can't put my finger on anything conclusive. It's definitely not to do with a delay before AKD kicks in. It doesn't happen often (ie it hasn't happened while my phone was in my pocket) - maybe once every couple of days for me.

My phone does a sprite backup every night which reboots it. I don't know if this could cause any problems.

Ive just tried phoning my diamond from my work phone, and had the following - the device was in standby every time and it hadn't been rebooted since the sprite backup this morning. Also I haven't received any other calls today but have made a few:

1st call - AKD didn't work

2nd call - AKD didn't work

- Ran AKD from programs, it said it was already active so i told it not to close

3rd call - AKD didnt work

- Ran AKD from programs, disabled it, then ran again

4th call - AKD worked perfectly

- Rebooted phone

5th call - AKD worked perfectly

6th call - AKD worked perfectly

- I then ran a manual sprite backup (out of curiosity)

7th call - AKD worked perfectly, obviously not sprite

-I then wondered if making outgoing calls could make a difference

8th call was outgoing

9th call - AKD didn't work

10th call - AKD didn't work

:O

I hope that helps, it certainly does look like the outgoing call was the culprit.
[Touch Diamond, MDA Compact IV Themes and Apps] Polluxus:
1.) No it doesn't seem to lock calls after the first unsuccessful 'lock'. When I press the AKD icon it says it is running.

2.)

UnlockWithStylusEnabled = 1

LockCallsDuringCalls = 0 <---Changed

LockOnlyFromStandby = 1

TurnOffScreenMode = 2

TurnOffScreenMethod = 1

3.)Not running any other software in the background

4.) Official 1.93 Dutch ROM

Can't really see a pattern for the unreliable behavior. I am aware that the phone should be in sleep mode before AKD kicks in.

Just reinstalled the app. and will test some more.

Update:

After reinstall it looks good. I couldn't reproduce the 'outgoing call leads to unlock bug'. Toggled between flight mode and 3g/gsm mode without problems, soft reseted a couple of times, no problem. Can't think of anything else that can affect the AKD behavior. Will see if the new installation holds up.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
My guess for the both of you is tha AKD looses its connection on the TAPI line. Never happened here, but this might be caused for some reason.

What dou you 3 have in common? All British maybe?

Do you ever switch the phone off completely?
[Touch Diamond, MDA Compact IV Themes and Apps] StarMonkee:
I'm British, on Orange and I never turn the phone off completely, but it does get reset every morning after a sprite backup.

I wouldn't know if it was losing the TAPI connection. On my normal day I'll go through a lot of 2g/3g areas so the radio does switch quite a lot.

On my testing earlier though I was in one location for the whole test.

I'll do some more testing on the outgoing call thing now and report back - it did make a difference earlier but it could easily be a coincidence.
[Touch Diamond, MDA Compact IV Themes and Apps] StarMonkee:
OK, nothing has changed since my last test earlier today (i've received no calls and made no calls). The last thing that happened was AKD didn't block the screen.

1st call - AKD didn't block the screen

- I disabled and re-enabled AKD

2nd call - AKD worked perfectly

3rd call - AKD worked perfectly

- I made an outgoing call

4th call - AKD didn't block the screen

5th call - AKD didn't block the screen

- I then ran AKD (it said it was already enabled), disabled and then re-enabled it

6th call - AKD worked perfectly

7th call - AKD worked perfectly

8th call - AKD worked perfectly

- I made another outgoing call

9th call - AKD didn't block the screen

10th call - AKD didn't block the screen

My settings are the same as my last post and after each call I turned the screen off (with the power button - I've set AKD to not do it automatically), waited a few seconds, and then tried again.

My results are pretty conclusively that making an outgoing call somehow breaks AKD. Not sure what else I can do to find out exactly what the problem is, but I hope this helps.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Doh! Update on its way :)

Version 0.5.1 released (bugfix)

v0.5.1 (Windows installer, CAB file)

Fix for the situation when the LockCallsDuringCalls has the value 0 placing outgoing calls would prevent future incoming calls of being locked (thanks Polluxus and StarMonkee)

Fixed the shutdown when updating Answerkeys Disabler bug: Answerkeys Disabler will now quit faster during uninstallation and not show the warning message (thanks BerlinTop)

Now lets have lunch :)
[Touch Diamond, MDA Compact IV Themes and Apps] StarMonkee:
Fantastic, I'll report back if I notice any problems but I'm glad my testing was helpful :D
[Touch Diamond, MDA Compact IV Themes and Apps] Blazeitup123:
i just installed, thanks for the update. ill take it for a spin today and report any findings.
[Touch Diamond, MDA Compact IV Themes and Apps] eltsele:
I just installed this app to my Diamond and seems to work fine.

Congratulations, I had already some problems with unwanted accepting/rejecting calls!!
[Touch Diamond, MDA Compact IV Themes and Apps] Polluxus:
Ok have been running the 0.5.1 version for two days. Problems seem to be gone :) Thank you.
[Touch Diamond, MDA Compact IV Themes and Apps] NoBody20013:
does anybody knows if the new AKD version 5.1 works with "Homezone"?

i had to switch to sensor lock because of the disfunction with calls to my Homezone number (a landline number which goes directly to my mobile device - in germany this is a "normal" mobile option). And i want to change back to Answer Key Disabler
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
No changes for that unfortunately :(
[Touch Diamond, MDA Compact IV Themes and Apps] mastaduck:
I have two problems with Answerkeys Disabler 0.5.1.

1. I noticed that after a few calls no longer functions as may be required (touchscreen is working - I had the same problem with previous versions of Answerkeys Disabler)

2. And my main probe is that even when the program is working fine the phone pick up the incoming call after few rings (every time) till now i havent had this problem and is very annoying.

Anybody got any idea how to overcome. In particular, the problem of under 2.

Pleesssss i am desperate
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
For #1, what are your settings, is the issue reproducable? For #2, do you have problem #2 as well if you don't install Answerkeys Disabler?
[Touch Diamond, MDA Compact IV Themes and Apps] gamer007:
Just tried this on my CDMA Telus Diamond. Doesn't work while running Juicy's 2.5 ROM.
[Touch Diamond, MDA Compact IV Themes and Apps] mastaduck:
For #1 my setting are:

LockCallsDuringCalls 0

LockOnlyFromStandby 0

TurnOffScreenMethod 1

TurnOffScreenMode 2

UnlockWithStylusEnabled 1

Are my settings wrong, because every here and there the Answerkey Disabler does not block the touchscreen when i get incoming call?

#2

I unistall Answerkey Disabler and i still have the problem whit picking up the incoming calls, but the problem apper today when i install Answerkeys Disabler (i install last other program on my Diamond one approximately one week ago).

Thanks for trying to solve my problem
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
There are no "wrong" settings, they all should work, that's why they're called settings :) Anyway, you could try enabling the LockCallsDuringCalls setting once more. However, I don't think it'll solve problems.. It's not alike the problems others faced with v0.5, not locking calls after an outgoing call was made.. But you could try of course.

I don't have a solution for #2.. Answerkeys Disabler does only listen on the TAPI line, it does not accesss functions to reject/answer/... calls. Heck, I don't even know how those functions are called! :P

Good luck! Cheers, Daan
[Touch Diamond, MDA Compact IV Themes and Apps] daidey:
Suggestion

This is really a light weight and useful tool!! Very nice! :D

I have just an idea that if it could interface with the G-Sensor which able to disable the screen in the following condition during a call:

1) Disable the screen when the phone is placed vertical (placed near an ear)

2) Enable the screen when the phone is placed horizontal (hold on hand and use the dail pad)

In short, work like iphone. Diamond comes with a similar function but stupid, lock the screen when the phone placed vertical, but then NEVER enable back the screen.:mad:
[Touch Diamond, MDA Compact IV Themes and Apps] skduk:
it may be just me but it seems to disable also the PTT push-to-talk button on the hands-free - which is not good... any settings i've missed?
[Touch Diamond, MDA Compact IV Themes and Apps] halkis_13:
problem

i have a problem with htc diamond..if i have a miss call (very fast call) and the rigntone doesn't ring the diamond block..if i have one ring its all ok..

v.0.5.1
[Touch Diamond, MDA Compact IV Themes and Apps] rocajack:
No working on Telus CDMA STOCK

It also does not work with Telus Stock ROM. The on/off (prompt when press the icon) does not change the registry or it registered any differences. Tried numerous incoming call from standby and no locking of the screen (yes done reset also). What does work is the screenofmethod which shuts the display down right away when call is established.

any suggestions would be appreciated.

RJ
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Thanks rocajack, that pinpoints the probems with CDMA devices to the Touch Panel driver, definately. TAPI messages can be received (otherwise the device would not turn off after a call), but turning off the touch panel will not.

Hmmmmmm..... Wasn't there another way to turn it off? Using another kernel call? Let's look back in the history of device locking! Interesting....... Thanks :)
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Sorry, I was mistaken. The previous locking system would lock everything, including hardkeys. You woulnd't be able to pick up the call unless you retract the stylus. Not really useful...
[Touch Diamond, MDA Compact IV Themes and Apps] ricolee:
Samsung i780

Drvdijk,

Your program is exactly what I am looking for fixing another annoying Windows Mobile feature. I tried different configuration on my Samsung i780 but it still can't lock the softkey on the screen. Do you have any idea?

Thanks,

Ric
[Touch Diamond, MDA Compact IV Themes and Apps] ndrom:
Touchscreen lock

Hi,

What would you recommend better, AnswerkeysDisabler or S2U2?

Do they work if installed both?
[Touch Diamond, MDA Compact IV Themes and Apps] sepehr_sar2000:
is there any of this app for Wm 5 ( i-mate JAMin ) ?

it's very important for me ...... :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Nope, Answerkeys Disabler will prevent S2U2 from unlocking: you cannot slide the phone to unlock/answer since the touch panel is disabled. I've not tried this however...

Sorry guys, I don't have such phones. This is for the HTC Touch Diamond...
[Touch Diamond, MDA Compact IV Themes and Apps] Strish:
Answerkeys Disabler works fine for me. Thank you.

But may be you can add the same action (locking screen) for bluetooth connection (or disconnection) with car kit (additional for incoming calls)? During a connection establishment (or disconnection) phone unlocks in my pants...
[Touch Diamond, MDA Compact IV Themes and Apps] venom037:
this app works great on my Touch Pro.. thanks, best app
[Touch Diamond, MDA Compact IV Themes and Apps] master1706:
thanks a lot. works ok on touch pro
[Touch Diamond, MDA Compact IV Themes and Apps] venom037:
this works awsome on the touch Pro and I have tested this extensively. thank you for the recommendation.