27 replies to this topic

[jasonrabbit]

Can we put our heads together and come up with a way to remove the Action Key in a Phone call.

Just a simple answer phone message i have to press that key 3 times

I have been throw RegEdit and changed setting values under HKCL/ControlPanel/Phone with no luck

We have some great minds on this site and im sure we can remove this

[Reuben (MY)]

the one that only allows you to send/center/end button during a call?

[jasonrabbit]

No the one that unlocks the keypad during a call

[msjfb]

jasonrabbit, on Sep 28 2008, 16:24, said:

No the one that unlocks the keypad during a call

One way to do it could be to have an application watch for the window or message, and press (programmatically) the key automatically. I have done some windows programming, and if Windows mobile is similar then it should not be difficult to intercept these events, and act on them. We need to get a windows mobile programmer involved in this.

[ptrbee]

msjfb, on Sep 28 2008, 17:29, said:

One way to do it could be to have an application watch for the window or message, and press (programmatically) the key automatically. I have done some windows programming, and if Windows mobile is similar then it should not be difficult to intercept these events, and act on them. We need to get a windows mobile programmer involved in this.

Yippie,    Can anyone tell that I'm happy about this?? thanks guys, hope we can get this sorted, after speaking to some muppet at Samsung Tech Support today, I will do anything I can to help get rid of this annoying popup.

[Juicey]

Well, I'm neither a 'great mind' or a windows mobile programmer, but I did a little research

Seems the registry key involved is HKLM\System\State\Touchlock . Set to 0 -> screen enabled, set to 1 -> screen locked.

Obviously the Phone program sets this value to 1 whem you're making a call, and sets it back to 0 (briefly) when you press the Action key. There's not a lot to be done about this, unless someone rewrites the phone program or Samsung is nice enough to drop this 'feature'.

As a workaround (nothing more) I've made a little Mortscript that checks wether the Phone prgram is running, and then resets the registry value to 0 after the Phone sets it to 1 at a given interval.

BTW, my first attempt at a Mortscript. May not be pretty, but seems to work.

# No_screenlock.mscr
# Script to prevent i900 from locking display while using Phone - (c) 2008 Juicey
#

# Set this to desired delay value in millisecs
delay=500  

While ( 1 )

If wndActive "Phone"
 regReadDword HKLM,"System\State","Touchlock",tlock
  If equals %tlock%,1
   regWriteDword HKLM,"System\State","Touchlock",0
  EndIf
EndIf

Sleep %delay%

EndWhile

Note - Once launched, the script will remain running till the next soft-reset. No idea  how that will effect the i900 performance or battery usage, but would like to know if anyone is brave enough to try

Note 2 - This script should in no way be able to damage or brick your phone, but you use it at your own risk!

Note 3 - Obviously you need Mortscript on your phone for this to work.

Enjoy!

Attached Files

•  No_screenlock.zip   385bytes   102 downloads

Edited by Juicey, 28 September 2008 - 08:09 PM.

[Reuben (MY)]

why not author the MakeACall script in WM not to set touchlock to 1? then you probable save lots of resource running backend program as process

[ptrbee]

Juicey, on Sep 28 2008, 21:08, said:

Well, I'm neither a 'great mind' or a windows mobile programmer, but I did a little research

Seems the registry key involved is HKLM\System\State\Touchlock . Set to 0 -> screen enabled, set to 1 -> screen locked.

Obviously the Phone program sets this value to 1 whem you're making a call, and sets it back to 0 (briefly) when you press the Action key. There's not a lot to be done about this, unless someone rewrites the phone program or Samsung is nice enough to drop this 'feature'.

As a workaround (nothing more) I've made a little Mortscript that checks wether the Phone prgram is running, and then resets the registry value to 0 after the Phone sets it to 1 at a given interval.

BTW, my first attempt at a Mortscript. May not be pretty, but seems to work.

# No_screenlock.mscr
# Script to prevent i900 from locking display while using Phone - (c) 2008 Juicey
#

# Set this to desired delay value in millisecs
delay=500  

While ( 1 )

If wndActive "Phone"
 regReadDword HKLM,"System\State","Touchlock",tlock
  If equals %tlock%,1
   regWriteDword HKLM,"System\State","Touchlock",0
  EndIf
EndIf

Sleep %delay%

EndWhile

Note - Once launched, the script will remain running till the next soft-reset. No idea  how that will effect the i900 performance or battery usage, but would like to know if anyone is brave enough to try

Note 2 - This script should in no way be able to damage or brick your phone, but you use it at your own risk!

Note 3 - Obviously you need Mortscript on your phone for this to work.

Enjoy!

Thankz thank-you  thankyou, hey can I post this in other forum, it works perfectly so far, i found the touch lock reg key disabled it but couldn't find where it keeps resetting itself...

[Juicey]

Guess it's just the Phone application that keeps setting the registry back to 1...

Feel free to post it anywhere you want!

Also, please report back here if you see any problems with performance or battery drain, curious about that.

[respider]

wow infinite loop with 500ms interval? thats almost a busy wait
anyone know about batt life with this script running? should drain really fast

[msjfb]

respider, on Sep 28 2008, 22:04, said:

wow infinite loop with 500ms interval? thats almost a busy wait
anyone know about batt life with this script running? should drain really fast

I'm digging a little bit into this... Mortscript does not do 'event watching' very well, from what I read (CPU intensive and battery drain). It seems that a product called SKSchema (http://s-k-tools.com...m_skschema.html ) is better at waiting for events.
I think we could get SKSChema to trigger on the phone app as it starts, and have it call the Mortscript (minus the waiting loop) so that Mortscript handles resetting the Registry key. When the phone apps stops, Skschema will trigger and kill the Mortscript. This way the tight loop is only active during a phone call.

Tha's the game plan, but a C# programmer with Compact .Net Framework experience could wrap this into one nice little application. For now, I will try to get something working with SKSchema and Mortscript.

[pidsw]

I used advancedConfig 3.2 and disabled the PhoneCanvas.  That did it.  I like the default as it is the fastest to load (I hate latency when it comes to answering calls)
However it may be missing some special support (?)  you can always re-inable it when needed.

[gregchurch]

pidsw, on Sep 29 2008, 10:01, said:

I used advancedConfig 3.2 and disabled the PhoneCanvas. That did it. I like the default as it is the fastest to load (I hate latency when it comes to answering calls)
However it may be missing some special support (?) you can always re-inable it when needed.

Hi,
Have installed advancedconfig.3.2 but can't find an option called Phonecanvas under the Phone section.
Grateful for help.

Cheers, Greg

[ptrbee]

gregchurch, on Sep 29 2008, 13:52, said:

Hi,
Have installed advancedconfig.3.2 but can't find an option called Phonecanvas under the Phone section.
Grateful for help.

Cheers, Greg

I think he means thephone-> phone skin option, set to disabled, Disabling this will give you the windows default phone pad.

[msjfb]

ptrbee, on Sep 29 2008, 12:56, said:

I think he means thephone-> phone skin option, set to disabled, Disabling this will give you the windows default phone pad.

Mmmm, this is a HTC centric application. Will have a look at what can be done with it, but I actually LIKE the feature of an quick screen lock on an incoming/outgoing  call. What I want is to be able to disable it on an outgoing call, when I need it to be off for the duration of the call.

[ptrbee]

msjfb, on Sep 29 2008, 14:25, said:

Mmmm, this is a HTC centric application. Will have a look at what can be done with it, but I actually LIKE the feature of an quick screen lock on an incoming/outgoing  call. What I want is to be able to disable it on an outgoing call, when I need it to be off for the duration of the call.

carefull with the performance tweaks "glyph cache etc" most of them are definately HTC & will cause the omnid to become very unstable & hang in some cases.

[PaulOBrien]

Just a heads up that I am already working on a fix for the in call lock...

P

[gregchurch]

Paul (MVP), on Sep 29 2008, 20:17, said:

Just a heads up that I am already working on a fix for the in call lock...

P

Cheers, Greg

[ptrbee]

Paul (MVP), on Sep 29 2008, 19:17, said:

Just a heads up that I am already working on a fix for the in call lock...

P

wicked, if you need a beta tester I'm happy to

[PaulOBrien]

OK, so I have successfully written an app that disables the screen lock every time it comes on, feels like a bit of a kludge tho, as when you turn the lock off (either programatically or by pressing the action key), it turns itself back on again shortly after.

My app basically watches that reg key, then sets it to 0 whenever it becomes 1. It's also using the WinMo's built in state notification broker, so there's no impact on performance / battery etc.

Thoughts? Altho not perfect, is this still useful?

P