yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] m3cti:
well, the tool ist very nice, but it has a annoying problem left to solve:

if i get a call, answer it by pressing hard-phone button it works so far. But if i'm getting another incoming call while still talking it isn't possible to reject these because of the locked display :(

Pressing "end call"-hardbutton ends both calls, and the "phone"-button switches to new call.

I guess i have to use sensorlock again to have a option manually unlock screen if necessary.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Interesting scenario! I guess for now (untill v0.4 with Stylus support) you have to just let it ring untill it goes away. With stylus support, the screen will unlock once you pull the stylus out. Will that solve it?
[Touch Diamond, MDA Compact IV Themes and Apps] MJNewton:
I can confirm seeing the very same behaviour.

However, try this.... In AE Button Plus do you have 'Restore Volume Slider' enabled (under Options) for any of Today/Phone/Phonecalls options? If so, try unticking them...

I did this and have since found AEBPlus to be working fine, all the time. I suspect the problame may be down to Answerkeys making AEBPlus think the 'phone' is (still) in use and hence it reverts the keys back to normal operation. Of course, perhaps you may wish to have the volume function restored under such circumstances however it's not a problem for me hence I find this fix/workaround is acceptable.

Mathew
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Version 0.3.1 released

v0.3.1 (RS)

Changed locking behavior: If the device is on and a call comes in, it will not lock.

Fixed screen turnoff errors: if called directly after a missed call (within 40 seconds or so), the screen will now turn off once the second call is answered/rejected/missed.

Added screen turnoff: when during a call the device is turned off, the screen will turn off after the call is hung up.
[Touch Diamond, MDA Compact IV Themes and Apps] sabb0ur:
Actually, I have to disagree!

I just tried the following scenario:

1. Called the phone

2. Answerkeys Disabler kicked in, the phone locked

3. I answered using the hardware button and eventually the screen turned off

4. Just pressing the center button brought the screen back to action and it wasn't locked!

So, Answerkeys Disabler only locked the phone while it was ringing, without interfereing with the normal operations afterwards (which is GREAT!)

Can you check again using the above scenario?

Even pulling out the stylus did the normal thing!

Edit:

Actually, I miss understood the problem. You mean that when another phone call comes in while you are already having a call, Answerkeys Disabler will kick in. Isn't there a check in the windows mobile API to indicate whether another phone call is in progress that could be used as a flag to indicate whether Answerkeys Disabler should kick in or not?
[Touch Diamond, MDA Compact IV Themes and Apps] BerlinTop:
Wouldn't it be a solution to simply not lock the screen, when a second (parrallel) call comes in? I mean, the screen is unlocked during the existing call. If now a second call comes in, just don't let answerkeydisabler act...

The stylus-solution to unlock is not really handy, typically parrallel calls hit me, when I am driving, trying to make a left turn on a big intersection...I just do not have enough hands to handle this situation without fatalities...

I will stick with v. 0.2.1 for the time being, because I would hate my screen to go blank after unlocking...
[Touch Diamond, MDA Compact IV Themes and Apps] patbots:
Answerkeydisabler using bluetooth

Thank you for a great program. I will now enjoy using my new TD much more. I installed version 0.3 and it has been working as advertised. I did some testing via Bluetooth headset and experienced the following.

With the phone in standby mode (Screen off) I answer the incomming call via Bluetooth headset. Screen activates and is auto lock with your software and the screen goes off during conversation. I then end call via Bluetooth and the screen reactivates after a few seconds to Dialpad screen and then to Home screen. Please make it possible for the screen to revert to standby mode (Screen off) directly after hangup via Bluetooth.

Again, Thank you very much for all your efforts. It is much appreciated by many TD users.
[Touch Diamond, MDA Compact IV Themes and Apps] Matrix44:
Whan I want to uninstall app, will I get the original settings back ?

Does anybody have any screens what it looks like ?

Thx,

Matrix44
[Touch Diamond, MDA Compact IV Themes and Apps] m3cti:
Hmm, i guess not, at least not really ;)

The point is, i wish to decline another incoming call while talking already to send this caller to my mailbox. If i do not, it will ring without end. I have disabled automatic mailbox-forwarding. So the only way to send someone manually to mailbox is to press the "decline"-button on screen, which isn't possible if screen is locked. And: i turn always off my screen if a call is still active to save power.

So i'm waiting for 0.4. But it would be very nice, if you could disable screen-lock by pressing power on/off-key. I think if someone uses this button it is almost clear that he wants to use the phone and it's touchscreen ;)
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Try the new 0.3.1 version, it should disable the screen just as you asked :)
[Touch Diamond, MDA Compact IV Themes and Apps] knight14th:
Hey, thank you for the nice tool.

What about locking the screen if a call comes in and the the light sensor reports darkness (because the phone is in the dark pocket!). After taking the phone out of the pocket it should unlock, if there is light, lock otherwise (while it is near to ones ear).

This would make your tool really cool and useful.
[Touch Diamond, MDA Compact IV Themes and Apps] nushuth:
just one question:

i want to cook it directly into a rom, and i want to start it autimatically at boot.

is there something to do except add a link in autostart directory?
[Touch Diamond, MDA Compact IV Themes and Apps] patbots:
Thanks soooo much.:)
[Touch Diamond, MDA Compact IV Themes and Apps] Arkadash:
Agree with it and I will thank if You will do it. :)

Added: Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
? can you explain better what you mean?

...where action-button unlock solution would be great

hope it comes eventually (even with a small window to hide the two big buttons)
[Touch Diamond, MDA Compact IV Themes and Apps] Matthy_47:
Great work, keep it up, little donation is on the way.

M.
[Touch Diamond, MDA Compact IV Themes and Apps] tuem:
installed and tested v0.3 (on 1.93 rom)

simple and works like a charm.

good job, thanks mate! :cool:

the problem of the mistakenly rejected calls seems to have become history:D

now if i can only find a solution to accidental touch operation when the device wakes up on reminders or alarms... without the hassle of locking / unlocking the device manually each time... i'd be in heaven:rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] wpguser:
I don't see a touch.dll file and I see a coredll.dll.0409
[Touch Diamond, MDA Compact IV Themes and Apps] fBx:
Anyone experiencing higher energy drain with this tool enabled? In my opinion my phone lasts about 25% shorter than before installation.
[Touch Diamond, MDA Compact IV Themes and Apps] Django76:
Hi sausagegun :D,

i did not experience any higher energy consumption
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
I strongly believe in safer traffic by not calling at all in the car, and if we truly must to regulate it as we in the Netherlands do: just use a cheap (bluetooth) headset or get fined. You at least have both your hands free for the life-critical task you're doing: driving!

Therefore, I'm supporting bluetooth headsets more. That's why I want to lock the parallel call as well. If I don't, people driving and using headsets while keeping the phone in the pocket, will loose calls (possibly both) when a secundary call comes in.

Yep, the program does not change any setting at all.

Good idea. However for now, I'd like to K.I.S.S.

Nope :)

The device wakes up if you end a call as well, be it when you hang up yourself using the hardware key, or the other party hangs up. The device will wake up, being unlocked. Answerkeys Disabler v0.3.1 will turn off the device, if this happens.

Action-button unlock.. Maybe with a window.. I'm first investigating if I can read the touch screen in the center button (not the regular touch screen) while everything is locked and stuff.
[Touch Diamond, MDA Compact IV Themes and Apps] BerlinTop:
Don't get me wrong, of course I do use a bluetooth headset while driving. It sits on my ear all the time. I depend on doing lots of calls while driving - this is part of my job. I don't do that to talk about the wheather. Now, when I hear a "call waiting"- tone in the headset while in a conversation, I use the hardware-key on the Diamond to toggle between the calls. That's fine.

The trouble starts, when I want to reject the second incoming call. Then I would have to take the phone in my hand and somehow pull out the stylus to activate the screen (while holding the steering wheel with my knees or maybe nose). In this situation, the whole idea of using a headset becomes obsolete (if I still have to perform complicated manual operations on the phone itself like fingering for the stylus). The whole idea of using a headset is to have the hands free for driving, right? So, basically, NOT using the stylus strongly supports the all agreed usefulness of a headset :-) If the display wasn't locked upon the second incoming call, one touch with a finger would resolve the situation much easier. And traffic would be safer (and my life would be, too).

And, of course, there is nothing wrong with implementing this "stylus-feature", if you like the idea so much.

But what speaks against an additional tweak to not lock the screen upon a parrallel incoming call?

Just give it a thought.

Cheers :-)
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Good discussion, I like that :)

Calling in cars in inevitable, I understand. The stylus idea is nearly implemented. I will probably be releasing the v0.4 within the hour.

What speaks against not locking a second call? Scenario:

1. First call comes in. Device is locked, but on, in your pocket.

2. You pick it up with your BT while driving. The phone remains in your pocket. It turns off (the screen) directly after you pick it up.

3. Second call comes in. The screen turns on, unlocked.

4. You at the same time have to punch the brakes for that idiot in front of you.

5. By braking, you either accidentally pick up the second or reject it, because your pants hit the screen.

6. Back to square one..

I'm investigating the touch sensor on the action button. That seems to respond only to my finger, not the pouch.
[Touch Diamond, MDA Compact IV Themes and Apps] BerlinTop:
:) I am fine with any solution that can be executed with the tip of one finger.

And: If the phone is in the pouch, or even in the trunk, then neither the stylus, nor the screen, nor the action button will be of much help. Then to hell with the second caller. Life is a chain of missed opportunities, right :-)

But my next car will have a built-in bluetooth solution for the phone, that should be able to handle parrallel calls without the need to perform any actions on the phone itself. (And maybe, my next car will even have breaks :confused: )

But until then, I will be more than happy with the action button...

Thanks, I appreciate your efforts and responsiveness! Thats great!
[Touch Diamond, MDA Compact IV Themes and Apps] Krzysiec:
I experienced a little bit faster battery drain with AD ... But in compare with s2U2 its better anyway ... but if there is possibility to decrease battery drain why not ;)
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
I wouldn’t add AppToDate support. Why waste the resources in trying to do that? Once the program has been perfected, there is no need to modify it so no need to have AppToDate.

Also, by incorporating stylus unlock, are you notified that the registry entry has changed, or do you have to actively poll the registry? If it is the latter, then I can see that adding significant processing utilisation.

Finally as your app is running all the time, when in standby what is your app actually doing? You’re most significant optimisation and reduction of battery usage will be made by trying to reduce the amount of work your app is doing in the background, when in standby or just if the phone is on running another app.

However this can follow once you have finished coding all the functionality you require and all the bugs have been ironed out. Then you can look at making it more efficient without breaking it.

PS: I’m still resisting trying the app yet, will wait until you release V1.0, at the rate your going I expect that to be quite soon!
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Good points! :)

AppToDate support: it's only placing one XML file of exactly 319 bytes (321 bytes if I release a 0.4.1 version) on the device, as well as one registry key. I think I can do that for the people who really like that ;)

About stylus changes: I'm indeed notified on registry changes. No polling at all. Otherwise it wouldn't have been included.

If the phone goes to standby (e.g. by pressing the power button), HTC causes it to go to the 'unattended' state at first. During this state, everything is off, but applications may still run to clean up crap before going to true 'suspended' state. During this unattended state, Answerkeys Disabler does the same as when the device is on: wait until it's notified for one of the events (incoming call, power status change, stylus change). When the device then truly goes to 'suspended' state, no programs run. If it can do anything at all in that state, it again waits for one of the notifications. To illustrate my point of not running at all: I get the power change notification that the device was suspended only after it woke up again ;)

v1.0 .. I guess 0.4 is going to be the preliminary final version. Possibly a 0.5 version will emerge with action key unlocking support, but that's not expected for the near future (unfortunately).
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Great,

That means battery usage should be quite minimal as it is...

So improving the code will make it less resource hungry and maybe run faster and more efficiently.
[Touch Diamond, MDA Compact IV Themes and Apps] MJNewton:
Waste resources? There's really nothing to it as drvdijk says.

Besides which, when in the history of software development has a program ever been 'perfected'?! ;)

Mathew

P.S. Keep up the good work drvdijk - if it's not already obvious by now your tool is greatly appreciated!
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Version 0.4 released

Project home page including source code: http://code.google.com/p/answerkeysdisabler/

v0.4 (Windows installer, CAB file)

Stylus support: When Answerkeys Disabler locks your phone, you can unlock it by pulling out the stylus (or inserting it). After this, you can use all on-screen buttons, and the device will not turn off the screen.

AppToDate support

Other device turn-off mechanism: Answerkeys Disabler now simulates pressing the power button. This fixes the wake-up from talk-and-end key after Answerkeys Disabler turns the device off.

Answerkeys Disabler will now automatically run after installation. Uninstallation does not require shutting down Answerkeys Disabler anymore.

Created Windows installer for those unconformable with cab files

TODO

Add unlock by action key option (if possible)

Give me some input! :)

Coffee

If you like what I'm doing, buy me some coffee to keep me doing it ;)

Have fun with this one!

Download links

Windows installer

CAB file
[Touch Diamond, MDA Compact IV Themes and Apps] onesolo:
Do you mean like S2U2 ??
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Nope, the round button in the center of your phone has an additional touch screen. That one.
[Touch Diamond, MDA Compact IV Themes and Apps] Peio64:
That would be awesome!

Thanks a lot for your work
[Touch Diamond, MDA Compact IV Themes and Apps] Graphyboy:
Internet calling

Hi...

Your application is really great... but I have just one problem. It don't work with internet calling. I'm using the built-in VOIP and when somebody call me, the screen of my Diamond is'nt locked. I can accept or refuse the call by a touch on the screen. I don't know why...

Regards,

Didier
[Touch Diamond, MDA Compact IV Themes and Apps] Ikarus80:
I am owner of the xda Diamond for a few days now and I just installed Version 0.4. This tool is exactly what I was looking for, thanks a lot for this!

Directly after installation I got the message: "Unable to run Answerkeys Disabler" or something like that. But after a softreset everything works fine.

Again, thanks a lot!

P.S.: I like the icon very much :)
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Hmm, Answerkeys Disabler locks when it gets a TAPI message. Most likely, internet calling (SIP?) does not yield those tapi messages..

What message? "Unable to run Answerkeys Disabler"? I haven't incorporated that message in the program / installer.. Weird? Glad it's solved after a soft reset :)

I didn't make the icon, you should thank Birkov for that one ;)
[Touch Diamond, MDA Compact IV Themes and Apps] krheinwald:
Installing from CAB: 'Could not launch AnswerKeysDisabler. Run manually' (Or something like this).

Sorry, device is looked,but still on after call is ended with End-key.

But never mind, it's a great application anyway.

I hope one of HTC's d**b product managers sees this thread. It's not a bug, it's a feature. Pah!
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
It will turn off your phone ony if it was off before hanging up. I.e. pressing the red button, or the other party hanging up. Turning it on and pressing the on-screen button will not turn off the device.

@krheinwald & ikarus80: Are you using non-english ROMs?
[Touch Diamond, MDA Compact IV Themes and Apps] charly_mx:
Simply this is the best application for our Diamonds. :) Great Job my friend. This forum is really awesome!!
[Touch Diamond, MDA Compact IV Themes and Apps] Graphyboy:
Thank you for your answer...

Do you know if there is a possibility to give to the internet calling (yes... it's a SIP protocol) the ability to send this TAPI message ? I'm using the built-in WM6 VOIP.

Sorry if i look like a newbie... but I'm just a user...
[Touch Diamond, MDA Compact IV Themes and Apps] JollyDrifter:
hey just wanted to say i get the same error messages like the others, but it seems to work fine.

thx for a great app.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
If you're getting the error message during installation "Failed to start Answerkeys Disabler, please start manually", please post your ROM information! Thank you :)
[Touch Diamond, MDA Compact IV Themes and Apps] krheinwald:
That was the case. Phone was off. Call came in, was accepted using green key. Screen went off. Call was ended with red key. Screen went dark, but stayed on.

Screen turns off when other party ends the call.

I have set the registry key which delays turning off after the unit being locked by the backlight going off. Might that be the reason?

German in my case.
[Touch Diamond, MDA Compact IV Themes and Apps] grebbo:
Up to now it is a great application but I had to remove it because , I don't know if it's been pointed out yet (haven't seen it on any post so far) but when a new SMS, or I suppose MMS too, is received .... the phone wakes and it's unlocked ....

As an italian user , we here use a lot the messaging function , and I found my phone too many times unlocked in my pocket and into some weird menus ....

Can this be fixed/added in your program ?
[Touch Diamond, MDA Compact IV Themes and Apps] krheinwald:
But now I can't turn it on anmyore!

Trying softreset...
[Touch Diamond, MDA Compact IV Themes and Apps] krheinwald:
Softreset fixed that, but it still stays on after *I* end the call.

Re-setting 20. HKEY_CURRENT_USER\ControlPanel\BackLight\AutoDevic eLockTimeout to 0 didn't fix this.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Weird behaviour... Anyway, I'm trying to contact you a little more directly. I just sent you a PM =]
[Touch Diamond, MDA Compact IV Themes and Apps] NoBody20013:
hi,

i have installed version 3 and now i installed version 4. but i dont work. i deinstalled the programm and installed it again and restartet the diamond. but it dont work (i can use the screen to answer calls...)

what to do now please?
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
Did you get the change in v0.3.1? "Changed locking behavior: If the device is on and a call comes in, it will not lock." Is this the case?
[Touch Diamond, MDA Compact IV Themes and Apps] BerlinTop:
Hey, just gave v. 4.0 a quick run. On the first glance: seems to be doing what it should! Great! The only bug I could discover so far: It gives an error message right after installation is complete that it couldn't start automatically. But it runs fine after manual start.

Pulling out the stylus during a call not only unlocks the screen, it also opens the message-function...hmmm...:-) But that´s a default behaviour...so the idea with the action key option still is a good one :-)
[Touch Diamond, MDA Compact IV Themes and Apps] BerlinTop:
1.93.407.1 GER
[Touch Diamond, MDA Compact IV Themes and Apps] koppee1:
what happens if an SMS (text message) comes in? The screen unlocks as well right? Does this software help in that case? or is this only for calls?

thanks! :) lovely job you are doing!
[Touch Diamond, MDA Compact IV Themes and Apps] Vulpix:
What is this ApptoDate feature? Can someone explain?
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
This is for calling only indeed. Incoming SMS messages or event notifications are not locked.

v0.4.1 fixes the AppToDate support issues by the way.

Well, if you've got AppToDate installed, applications supporting it will be updated automagically if new updates become available.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
I just tested the app with my original Vodafone NLD ROM. I also get the installation notice. This is because the application is automatically installed in "\Programmabestanden\Answerkeys Disabler", while the installer tries to run "\Program Files\Answerkeys Disabler".

I had a choise to make. On one side not have this error and start the program correctly on non-WWE phones, or have the installer always install on the right storage device (not the 4GB drive). I chose the latter.

Not being able to turn it on again.. Nope, didn't notice this behaviour at all
[Touch Diamond, MDA Compact IV Themes and Apps] krheinwald:
There should be something like %PROGRAM_DIR% available in the installer, which expands to the localized directory.
[Touch Diamond, MDA Compact IV Themes and Apps] drvdijk:
I'm using a call to CreateProcess in a setup.dll file. Do you know how to use the %PROGRAM_DIR% or the CE1 variable in such a setting? Cheers
[Touch Diamond, MDA Compact IV Themes and Apps] krheinwald:
Sorry, not on this platform.
[Touch Diamond, MDA Compact IV Themes and Apps] putradbm:
the new version is ROCKS!!!

I think I like this version very much...

before testing this version v.0.4.1 I used the sensorlock v.0.3..but I think , from now on, I will use answerkey disabler v.0.4.1 ..!

You are the man....!!!

I combined it with the standart WM lock...i think this is the perfect combination....

answerkey diabler lock for incoming calls, and the standart lock, will always, lock the incoming messege.... PERFECT!

thank you

Still looking forward for next update...

cheers..!
[Touch Diamond, MDA Compact IV Themes and Apps] putradbm:
but please explain...what is the APPtoDATE feature? how it works? what is it suppose to do with the function of the disabler??

sorry, I just do not get it...

hope you will explain...thank you