73 replies to this topic

[JohKarJes]

Hi Omnia users,

As you know the default phone application from the omnia always locks while in a call.
You can press the mouse cursor key, but after (hard to change)period of time it will popup again.
I found a request from somebody some time ago who suggested to create a automatic unlocking feature that triggers on the accelerometer(position detector?)
or the build in light sensor. I thought this was a rather good idea (credits to that guy!).

Well, I just finished a small application which works as requested...AutoCallLocker.
The name does not cover it all, because it also does unlocking when appropriate.

Brief instructions:

Just install the added .cab file.
Then start the application. Now it should start with a settings screen (as you see in the capture).

Now, you can select which sensor you'd like to use for detecting when to lock/unlock.
Note that locking/unlocking is only influenced while in a call.
For the accelerator you may select a value between 0 (horizontal) and 90 degrees (vertical).
Above the device will lock the screen (when you have your omnia pressed to your head), below it will unlock.
When using the light sensor, you can set a value between 0 (no light) and 100 (max intensity of light).
Again the screen will lock below the threshold (if it is dark), above it will unlock.

Another nice goodie, is the always unlock feature. When set, the device will always be be unlocked in a call.
This is nice when you have placed the device for example in a cradle.

The last feature is an obvious one: Load on system start.
Note with this one set, the application is send to the background immediately after startup, although noticable for a short moment.
Note also that when this option is set, and you close and restart AutoCallLocker, it will also go to the background.
If you restart again, AutoCallLocker will stay maximized, so you can change its settings.

After you've changed its settings, you shoud press the Hide button, that will send the application to the background as well.
If you want to fully close the application, press Close.

Oh, as a last thing, I added a Haptic feedback option, that gives you a vibrating response when AutoCallLocker toggles its state.
Nice while trying to find the optimal settings, but a bit annoying on the long term, so you can switch it off.

Some notes:

• You need to install the Samsung redistributable smi_wm_sdk_redist_1_0_0.cab if you haven't done this before.
  I thought this one could be found elsewhere on this forum, but to make shure, here it is:
   smi_wm_sdk_redist_1_1_0.cab   219.29K   948 downloads
  
  
• I am using this application in combination with the PhoneEx phone replacement application (and that works too).
  So I haven't been testing much lately with the 'original' from samsung...so there could be some bugs remaining, although not likely. Please report.

Let me know if you have some more ideas or improvements for this application.

Regards and Enjoy,

JohKarJes

PS:

If you like this application you may sponsor my coffee needs: Donation

V1.0.0.5:
 AutoCallLocker1005.CAB   270.21K   542 downloads
 Screen01_1005.png   30.64K   151 downloads  Screen02_1005.png   15K   97 downloads

Older versions:
V1.0.0.4:
 AutoCallLocker1004.CAB   162.78K   248 downloads

V1.0.0.3:
 AutoCallLocker1003.CAB   162.28K   343 downloads

V1.0.0.2:
 AutoCallLocker.CAB   173.88K   282 downloads

Installation notes:

In case of trouble on installation try the following procedure:

• Uninstall the previous AutoCalllocker version:
      Stop a running instance before uninstalling it, by entering the configuration menu and press the 'Close'  button to stop the application completely.
  
• Then check your installation location (most of the time somewhere in \programfiles\AutoCallLocker).
  
• Delete any existing remaining files (settings.xml) before installing the new version.

Status history:
V1.0.0.5:
This version has a different architecture now. It is composed out of 2 executables instead of one.
The main part is now a kind of service which cannot be closed easily by the OS.
The second part acts as a settings starter to show the settings screen.

Bugfixes:

• This new architecture should definitely solve the closing problem when the OS has little memory left.
  
• The rattling when holding the device just over 90 degrees should be fixed now.
  
• Minor bugs and issues have been fixed during code changes (like for example usage of blanked screen and speaker output at the sae time).

V1.0.0.4:
Bugfixes:

• When the system has little memory left, the application could be closed unexpectedly.
  A fix is made to prevent closing. Please note that in (hopefully) rare circumstances,
  when the system has run out of resources completely, the appication might still be closed by the OS.
  
• When holding the phone upright, just over a 90 degrees angle, the phone unlocks again.
  This bug was introduced in the previous version, and has been fixed.
  
• Some internal fixes for minor (technical) problems.

V1.0.0.3:

Added a few new (requested) functions:

• Sensitivity setting - The previous version reacted a bit 'itchy' on accelerometer changes, so a filter is added to let it react more smoothly.
  
• A test button - Now you can check if you like the settings without making an actual call.
  The right square in the top of the screen shows when it is unlocked (green) or locked (red).
  
• Speakerphone toggling - When the phone is in an unlocked state, the speakerphone is activated, and de-activated again when the phone is locked.
  WARNING: Please check your settings carefully, before using this option.
  When the phone is held in such a way that the phone is going from locked to unlocked state, the phone starts very loud before lowering its volume.* Cosmetic update - Well, not absolutely needed, but (my humble opinion) the screen is much nicer now by using transparent controls and using a 'blue' theme.
  
• Replaced about button - Using a question mark now in the top left corner. Just press on it, and you'll be directed to the ' about' screen.
  
• Bugfixes? - Did not find major bugs, but some minors have been fixed.

V1.0.0.2:

• Sometimes even I am in a rush...last version contained a nasty bug,
  Setting the screen blanking option did not work properly (was not saved in the settings).
  
• Also, the blanking option is disabled by default now.

V1.0.0.1 :

• Added an option to blank the screen while in a call.
  
• accelerator is now accelerometer

V1.0.0.0 :

• The very first version

Edited by JohKarJes, 08 November 2009 - 08:04 PM.

[finaldestiny]

Hey! Nice work on the application. Tested it and it works fine on my omnia, thought I had to install the smi_wm_sdk cab file before it could work. I didn't realize it was working at first though because I expected the backlight to go off (screen go black) as well when the screen is locked through the light sensor or accelerometer Any chance of adding that? It would be the only feature I would say is missing.

Also, the user interface is fine and useable, it could do with a bit more spice to it though (just my humble opinion) <==Mainly irrelevant & unnecessary though!

Thanks for the great app

[Witu]

Many thanks, all work perfectly! Me has very much pleased that now there is a vibration on connection. Successes in new workings out.

[JohKarJes]

finaldestiny, on Jul 19 2009, 21:47, said:

Hey! Nice work on the application. Tested it and it works fine on my omnia, thought I had to install the smi_wm_sdk cab file before it could work. I didn't realize it was working at first though because I expected the backlight to go off (screen go black) as well when the screen is locked through the light sensor or accelerometer Any chance of adding that? It would be the only feature I would say is missing.

Also, the user interface is fine and useable, it could do with a bit more spice to it though (just my humble opinion) <==Mainly irrelevant & unnecessary though!

Thanks for the great app

About the backlight, I was already thinking about this, I'll give it a try asap.
About the spice...I don't think it has a high priority, but with someone having better GUI designing skills then me I maybe going to work on that one too.

And...yeah right...been sleeping I guess... ...accelerator...accelerometer...whatever...

Edited by JohKarJes, 20 July 2009 - 10:41 PM.

[Alberto Abarca]

Hi nice app, i try on blazingwolf Night v1 and works perfect

+1 backlight

[blazingwolf]

This looks very nice. I'll give it a try. Any issues with cooking it in to my ROM? Credit to you of course.

[JohKarJes]

blazingwolf, on Jul 20 2009, 18:23, said:

This looks very nice. I'll give it a try. Any issues with cooking it in to my ROM? Credit to you of course.

No problem, go ahead. Maybe you can wait a few days, I'm still busy with the backlight option. That would be a real finishing touch I guess....

[blazingwolf]

JohKarJes, on Jul 20 2009, 15:56, said:

No problem, go ahead. Maybe you can wait a few days, I'm still busy with the backlight option. That would be a real finishing touch I guess....

I'll wait.

I ran in to a couple of issue while trying this with the Samsung dialer.

1. When running your program and after I answer a call the program crashes and gives the error in the images.

2. The program errored while trying to uninstall it.

So at the moment it is unuasble on my phone.

Attached Files

•  Screen01.png   7.89K   63 downloads
•  Screen02.png   13.7K   58 downloads
•  Screen03.png   12.53K   49 downloads

[JohKarJes]

blazingwolf, on Jul 20 2009, 21:21, said:

I'll wait.

I ran in to a couple of issue while trying this with the Samsung dialer.

1. When running your program and after I answer a call the program crashes and gives the error in the images.

2. The program errored while trying to uninstall it.

So at the moment it is unuasble on my phone.

Well it seems you did not install the redistributable (properly) from Samsung ( smi_wm_sdk_redist_1_1_0.cab).
This one contains the missing dll (SamsungMobileSDK_1.dll). That should solve your problem, if not let me know, I'll might have to check with the original Samsung dialer (i'm currently using Spam alert ).

Edited by JohKarJes, 21 July 2009 - 11:27 AM.

[Rob V]

Great app!

I have only one suggestion, but don't know if it's possible:  The #1 use for this, at least for me, is when I'm interacting with voicemail.  The problem is that you hold the phone to your ear, and then need to immediately use the keypad to save or delete the message.  Is there any way that your app could be configured to override locking when I call a specific number?  It would always be the same number, dialed from a stored contact entry.  I think this one additional capability, in addition to turning off the backlight, would make this perfect.

[JohKarJes]

V1.0.0.1 - added the backlight option...

Guys, it's updated now, not exactly changing the backlight, but toggling the screen on/off (blank).

  Go ahead, give it a try and let me know how it works.
  
About the second 'overriding' request...I'll look into it, but do not  have too high expectations. This could be complicated (lets say a  challenge... ).
If I have something new or a fix, I'll let you know.
I only have limited options of testing, so I imagine there will be some bugs left when used on other configurations.

[Lyncexx]

i dont know whats wrong but it keeps locking/unlocking every half second, the screen is blinking
it only works with light sensor, but after few seconds being locked its not unlocking anymore by light
im usint Sector's DXID1_23004_Y1LiteBlack and samsung dialer

[JohKarJes]

Lyncexx, on Jul 21 2009, 23:23, said:

i dont know whats wrong but it keeps locking/unlocking every half second, the screen is blinking
it only works with light sensor, but after few seconds being locked its not unlocking anymore by light
im usint Sector's DXID1_23004_Y1LiteBlack and samsung dialer

Hmmm...not shure what's happening. Seems we're having a fight between AutoCallLocker (ACL) and another application. Seems ACL is locking when the other tries to lock...might be the ROM you are using. Can you find out if another application does a similar job while in a call ?

Other readers/users....do you have similar problems ?

OK, maybe found a problem that seems to resemble yours a bit.
I tested with the original dialer, and found out that the omnia can be set to blank the screen as well. Although it does not lead exactly to the described problems, it might be confusing.

Advice: disable omnia screen blanking switch while in a call. (settings/battery, tab page 'calling'...i've got a dutch device so don't know if this exactly matches a english device )

Edited by JohKarJes, 22 July 2009 - 06:10 PM.

[Rob V]

JohKarJes, on Jul 22 2009, 13:40, said:

Seems we're having a fight between AutoCallLocker (ACL) and another application. Seems ACL is locking when the other tries to lock...

I think that's exactly what's happening:  Lyncexx said that he was using the Samsung Dialer, which has a built-in lock (can be set via control panel to lock at 2, 5, or 10 seconds).  There is no way to turn off this lock while using the Samsung dialer.  But if you deactivate Samsung's dialer skin (ie, return to the defauilt WM dialer), then you also deactivate the lock.

There are two ways to do this.  One is to fire up your favorite registry editor and navigate to the following key:
[HKEY_LOCAL_MACHINE\Security\Phone\Skin]
"Enabled"=dword:1

Change the value of "Enabled" from 1 to 0, and then soft-reset your phone.

The other (and easier) way is via the Advanced Configuration 3.3 tool -- you'll find this parameter in the 'Phone' group.  (AC 3.3 has been cooked into some custom ROMs, but it you don't already have it, download from http://forum.xda-dev...ad.php?t=418151.)

I'm using the default dialer and have no problems with AutoCallLocker, so hopefully this will also solve Lyncexx's issue.

[JohKarJes]

Thanks Rob for the explanation. This was new to me too. Great Work !

BTW. The last version contained a (minor but nasty) bug that prevented toggling the blank screen option.
Repaired that one.

[pacman9889]

I really love this app, I do have one suggestion though, if it's possible.  

I think another option that would be amazing would be enabling speakerphone based on the above conditions.  That way when you pull the phone away from your face, not only does it unlock, it puts speakerphone on as well.  

Just an idea from wishful thinking.

[Rob V]

pacman9889, on Jul 24 2009, 16:09, said:

I think another option that would be amazing would be enabling speakerphone based on the above conditions. That way when you pull the phone away from your face, not only does it unlock, it puts speakerphone on as well.

+1 on this suggestion!  In fact, if this was possible, it would serve as a pretty decent workaround for the "don't lock when I'm calling voicemail" issue I had raised.

[JohKarJes]

Rob V, on Jul 25 2009, 01:08, said:

+1 on this suggestion!  In fact, if this was possible, it would serve as a pretty decent workaround for the "don't lock when I'm calling voicemail" issue I had raised.

Yes, sounds like a nice option, and easier to implement then the other you've mentioned.
I'll put it on my list, probably will be part of the next release.

[lhahehal]

cool app and working great on sector roms..

[Veggie-man]

So far so good on Adrynalyne's ROM... I'll post back if there are any problems!  Thanks so much for this!