Database Users

Can align screen shortcut be disabled?

I'm curious if its possible to disable the align screen shortcut on the Wizard (Enter Button in center plus Messages Button) Its really annoying when playing Doom or an emulator in landscape and having that popup all the time. Does anyone know a fix for this?

Unfortunately i dont have an answer for you. but i do have aquestion that i hope youcan answer. I got myself a doom launcher. It works well, but the control setup is terrible on the wizard. If i play in portrait mode, the fire button is the left soft key. So i ahve to fire with the same finger that i use to move. That makes the game unplayable. What launcher are you using and where did you get it?

I haven't done any testing or trying yet, but here is my idea...
what if you rename the align screen app, just so it stops it from launching?

Unfortunately i dont have an answer for you. but i do have aquestion that i hope youcan answer. I got myself a doom launcher. It works well, but the control setup is terrible on the wizard. If i play in portrait mode, the fire button is the left soft key. So i ahve to fire with the same finger that i use to move. That makes the game unplayable. What launcher are you using and where did you get it?
Click to expand...
Click to collapse
Its called GF Doom (I'm sorry but I don't remember where I got it or whom made it. Although if the creator see's this I would love for him/her to PM me as I also have some questions.) Anyway the launcher shouldn't control the Key Mapping, usually thats done in some sort of config file. With the program that I have the keys are mapped in the skin file's txt document.
Try this, unzip all contents into your storage card and run the launcher you should get Doom, Doom II, and Plutonia (sometimes called Ultimate Doom) as well as a 3rd party mod called Evilution. Keep the default skin, with that the keys I have mapped are:
The directional Buttons for Movement, Messages button for Fire and strafe(I would like to change strafe to volume up/down or Internet but have not been able to if you can figure this out let me know), and the softkeys for Select and Start.
The screen defaults to protrait with your choosen skin. To play in full landscape start the game in the options change the resolution to "low" and it will switch, Hope this helps
I can't seem to get the attachment to work here is the link ftp://[email protected]/Uploads/
the file is pocket doom.zip

A Flock of Seagulls are in my Wizard
It would be awesome to find a way to disable this. Is there maybe an entry in the registry that corresponds to what key combination turns on the align screen program. Maybe it could be changed to some combination of keys that is very unlikely to be executed simultaneously.
Until then, I'll continue to drink foo-foo drinks to calm myself while trying to play any action games.

GF Doom
Dragonedge:
What version of GF Doom do you have? Maybe I have an old version. When I enter full screen mode, the soft keys are shoot and strafe, while the message/IE buttons are menu and escape. I have to use the same hand to shoot as I do to move.
Thanks for the tip about full screen, I would never have figured that out. Now I'm not dissapointed with the program anymore.

Lol, funny posts. Is this still a problem? Does it need investigating?
V

I still have the problem........ working on some things now.

What version of GF Doom do you have? Maybe I have an old version. When I enter full screen mode, the soft keys are shoot and strafe, while the message/IE buttons are menu and escape. I have to use the same hand to shoot as I do to move.
Thanks for the tip about full screen, I would never have figured that out. Now I'm not dissapointed with the program anymore.
Click to expand...
Click to collapse
Not sure what version it is. Check out the ftp I uploaded a zip file with everything I use. Also you can edit the skin files to remap the softkeys as well as the messaging and internet keys. All the information about remapping the buttons is in the skins folder in a txt file names Skin Specs.
Lol, funny posts. Is this still a problem? Does it need investigating?
Click to expand...
Click to collapse
The only problem I had was being able to map the message and internet buttons as different keys. Also I would like to use the volume slider as a left and righ strafe but could not seem to get that mapped either. Any help there would be great.

I've made an app to disable this - VJCalibrula for Universal and Hermes.
Wizard requires a slightly different hack, and I don't have one to test on.
dragonedge: what hardware/ROM are you using? I'll try to get you to alpha test if you want.
V

dragonedge: what hardware/ROM are you using? I'll try to get you to alpha test if you want.
Click to expand...
Click to collapse
I wouldn't mind at all . I have the T-mobile MDA/Wizard with the 2.26 ROM
An app to disable this would be handy another idea that would be nice is an app that would let you specify another button combination for system shortcuts would be awesome.

VJCalibrula - disable align screen settings (alpha)
Guys, please give this a go.
I don't think it supports AKU 3.2 for now. Soon...
http://forum.xda-developers.com/showthread.php?t=282152
V

disable both action screen, and dialer when slide open

Hi, I usually slide open just to power on the phone.
So, I would like nothing to happen when I slide the phone open when on the today screen..
Does somebody have an idea how to do this?

Are you talking about the Keypad QuickTasks?
You can easily find the option on Start -> Settings -> System Tab -> Keypad QuickTasks

Yes, I mean the dialpad quicktasks.
When this is disabled I get the dialer instead.

As a "workaround", you could just press the red "hangup" button after opening the phone to return to the home screen...
Royan

Royan said:
As a "workaround", you could just press the red "hangup" button after opening the phone to return to the home screen...
Royan
Click to expand...
Click to collapse
this annoys me too, i may write a small program that looks for the keyboard opened event, and minimises the phone program

this annoys me too, i may write a small program that looks for the keyboard opened event, and minimises the phone program
Click to expand...
Click to collapse
That will be cool!

Oh.. I've been using a certain "Yet another lock app" v1.2 or something like that... and I always set mine to lock and suspend everytime I do a right to left sweep (via FTouchFo). And everytime I slide the keypad, it automatically unlocks and nothing comes up; no quicktasks nor phoneapp). I'm not kidding... I don't know if it's a good "side-effect", but that's how it works.

can you post a link or the cab?
I hate the search function!

lostsoul said:
can you post a link or the cab?
I hate the search function!
Click to expand...
Click to collapse
i second this vince!!!Please post the cab!

This is where I found it.
http://forum.xda-developers.com/showthread.php?t=261277
I actually prefer this than any other locking app out there since this app uses the same built-in Device Lock program with a few nice modifications.
Enjoy!

Optional Alternative
I wrote a mortscript file to disable both menus
1. Extract
2. Place "Kill" folder in Program Files
3. Place run.mscr in startup
4. Reset
Enjoy

Simple fix for this
Hi there,
I just got my Niki a couple of weeks ago (with T-mobile in the UK) and this has been bugging me too ever since.
I figured that there must be a registry setting to control this somewhere as the Keypad Quicktasks are able to adjust this behaviour. Last night , I finally found it.
The setting in question is:
HKLM/Software/HTC/Biotouch/ActionScreen/Check
With the Keypad Quicktasks on, it is set to 1. With them off it is set to 0 and will instead launch the phone app.
Simply set it to anything else (e.g. 2) and both the Quicktasks and the phone application are disabled upon sliding open the phone. The active slide event is still recognised and sliding the phone open will still answer an incoming call.
Sweet.

fenallen said:
Hi there,
I just got my Niki a couple of weeks ago (with T-mobile in the UK) and this has been bugging me too ever since.
I figured that there must be a registry setting to control this somewhere as the Keypad Quicktasks are able to adjust this behaviour. Last night , I finally found it.
The setting in question is:
HKLM/Software/HTC/Biotouch/ActionScreen/Check
With the Keypad Quicktasks on, it is set to 1. With them off it is set to 0 and will instead launch the phone app.
Simply set it to anything else (e.g. 2) and both the Quicktasks and the phone application are disabled upon sliding open the phone. The active slide event is still recognised and sliding the phone open will still answer an incoming call.
Sweet.
Click to expand...
Click to collapse
you are a genius, problem solved! 10/10

winwiz said:
you are a genius, problem solved! 10/10
Click to expand...
Click to collapse
Agreed Thanks fenallen

i've come accross a problem - a reset seems to wipe the settings and has reverted to showing the phone screen???

Well it seems to survive a soft reset as well as power cycles with the battery removed so I presume you mean a hard reset, in which case ... isn't that the point of a hard reset?
I would be amazed/worried if it wasn't set back to default by a hard reset.

nope, i am on about a soft reset! i'll try again to see if it keeps the settings this time

Im happy to say it works fine, after i made a soft reset.

power on/off
it´s posible to change the action of the power buton hardkey?
thanks

MobileMute - Mute/Unmute calls via hardware button

MobileMute is a little program that allows you to mute/unmute phone calls via a hardware button. It will also launch any other program of choice if a call is not in progress (that way your hardware button doesn't get wasted). I had searched for this functionality for while without much luck. So, I decided to write a quick little app to do it for me.
For those of you who had used the first version of this, you may have noticed the slight delay when running the program. This was because it was designed to start, do its thing, and then exit. That being said, it took a second for the program to initialize on startup which resulted in a delay.
I have changed this version to try to figure out what button you have it mapped to. If it can figure that out, it will stay active listening for future pushes to that button. If it can't figure out what button is mapped, it will act just like the first version (which is still functional, just with a slight delay).
I have also added a simple configuration utility for changing the settings (located in Program Files/itsallwright/MobileMute).
I originally developed this for my Kaiser, therefore it was originally posted in the Kaiser section. But, since it can work on other devices, I am posting the new version here. The only problem is that different devices have different button IDs. I will post some instructions for getting your button IDs on the devices that the default Kaiser button IDs don't work for.
I didn't test this version for as long as I tested the original. So if you have any weird problems with it, please let me know.
Original version is posted here http://forum.xda-developers.com/showthread.php?t=386810
Edit: Added MobileMute_v2.1 which adds support for more devices and Kaisers with non-standard ROMS.
Enjoy,
Jay

Button IDs
Here are some instructions to help find the button IDs.
If you do not have Visual Studio or another spy program, I saw a post here http://forum.xda-developers.com/showthread.php?t=251955 that might be able to help.
1) Open Spy Program and connect to device
2) Expand "Desktop Window"
3) Expand all child windows titled "Phone" (or whatever your "Phone" title is)
4) Locate the "Phone" window that has a child named "Mute" (or whatever your "Mute" text may be). If you can't find the correct Phone window, it is possible that is hasn't been started since the last reboot. To start it, make a quick call until you get the call status and hang up. Now you should be able to locate the window.
5) The next steps should be made while you are on a call, so make a call to Voicemail, yourself, or a patient friend . After the call is connected, make sure you are on the "Call Status" screen (the one that has the mute button on the screen).
6) Highlight the "Phone" window found previously and click the Messages button to view messages for that window. You will probably see messages continually being posted to the window.
7) Click "Menu" at the bottom and then click "Mute" (Note: do not click the "Mute" button on the screen as that will not give us the information we need.)
8) Click "Menu" at the bottom and then click "Unmute" (Same note as above applies)
9) Disconnect the call. The message window should stop getting messages.
10) In the message window, find all messages titled "WM_COMMAND" (there should only be 2)
11) The WPARAM value of the first WM_COMMAND message is the "Mute" button ID (Put it into a calculator to convert it to a decimal number)
12) The WPARAM value of the second WM_COMMAND message is the "Unmute" button ID​
If you do find your IDs and confirm they work, please post them here with your device and ROM info to save others with that device the trouble.
Thanks,
Jay

just use volume up/down to mute incoming calls...

zuNN said:
just use volume up/down to mute incoming calls...
Click to expand...
Click to collapse
If I'm not mistaken the purpose of this app is not to mute the ringer during an incoming call but to mute the mic during an active call. Also when not in a call it will launch your app of choice so when not in a call you're not occupying an otherwise usable button.

jhw549 said:
If I'm not mistaken the purpose of this app is not to mute the ringer during an incoming call but to mute the mic during an active call. Also when not in a call it will launch your app of choice so when not in a call you're not occupying an otherwise usable button.
Click to expand...
Click to collapse
That is exactly what it is for. It is very usefull if you have to attend a lot of conference calls where you are not required to participate 100% of the time.
Jay

zuNN said:
just use volume up/down to mute incoming calls...
Click to expand...
Click to collapse
This won´t work with my Kaiser with M-Diamond 1.4 ROM.

MobileMute_v2 with HTC Fuze
I have tried version MobileMute_v2 with the HTC Fuze and it does not appear to work. It will launch the program defined in the settings when not on a call, but will not mute the call, when launched while on a call.
I am launching this from the PTT button through the methods described in another thread. I created a shortcut short_ptt.lnk, which launches this application.
I have also navigated directly to the executable and run it while on a call and get identical results.
I am going to uninstall version 2 and try installing version 1.

HTC Fuze and MobileMute
I have now tested the original with the HTC Fuze with similar unsuccessful results.

sounds like a great app ill give it a go on my hermes tonight. thanks for sharing!

JVH3 said:
I have tried version MobileMute_v2 with the HTC Fuze and it does not appear to work. It will launch the program defined in the settings when not on a call, but will not mute the call, when launched while on a call.
I am launching this from the PTT button through the methods described in another thread. I created a shortcut short_ptt.lnk, which launches this application.
I have also navigated directly to the executable and run it while on a call and get identical results.
I am going to uninstall version 2 and try installing version 1.
Click to expand...
Click to collapse
This is most likely because the Fuze button ID for Mute/Unmute is different then the Kaiser.
Have you tried using the steps above to get your button IDs?
-Jay

Mobile Mute and Fuze
I had also tried running the executable directly, not through the remap of the PTT key.
I did that to elliminate the possibility of it being a mapping to a key issue.
This does assume it works when run directly and not from a key.
I suppose it is possible that an exeception is thrown when the program checks what key was pressed to launch it, if there was not key pressed to start it.
As is, with the Fuze, the touch screen has on screen buttons for Mute and Speaker Phone.
I have remapped the long_ptt to Voice Command and the short_ptt to {"\Windows\ctlpnl.exe" cplmain 1} which gives you the lock screen so I can quickly change the timeout. I like it to lock quickly when not running GPS, but not lock at all when running GPS, but this last paragraph is not related to Mobile Mute, other than I no lnger have an available button to map it to.

JVH3 said:
I had also tried running the executable directly, not through the remap of the PTT key.
I did that to elliminate the possibility of it being a mapping to a key issue.
This does assume it works when run directly and not from a key.
I suppose it is possible that an exeception is thrown when the program checks what key was pressed to launch it, if there was not key pressed to start it.
As is, with the Fuze, the touch screen has on screen buttons for Mute and Speaker Phone.
I have remapped the long_ptt to Voice Command and the short_ptt to {"\Windows\ctlpnl.exe" cplmain 1} which gives you the lock screen so I can quickly change the timeout. I like it to lock quickly when not running GPS, but not lock at all when running GPS, but this last paragraph is not related to Mobile Mute, other than I no lnger have an available button to map it to.
Click to expand...
Click to collapse
Check in "/Program Files/itsallwright/MobileMute" for an ErrorLog file. If that file exists and has info, post the contents and I will see if I can figure out what went wrong.
Since it does launch the program you have configured when not in a call, the program at least initializes. If it also launches the program when you are in a call then it can't find the "Phone" window or the "ConnectedText" value. If it appears to do nothing while you are in a call, then it is likely that the Button IDs are wrong.
-Jay

Fuze
A friend of mine with a Fuze let me check it out and I determined why it does not work.
The dialer on the Fuze has Mute/Unmute buttons on the screen, but the buttons do not have text (I suspect it uses seperate Mute/Unmute images instead). That being said, MobileMute determines the Mute State of a call based on the text value of the Mute/Unmute buttons. Therefore, it does not know what command to send.
I am trying to figure out a way to work around this, but in the meantime, I am sorry to say the Fuze is unsupported.
Just as a fyi... the Mute/Unmute button IDs for the Fuze are the same as the Kaiser (21408/21409)
I'll keep you posted on my progress with supporting this device.
-Jay

Trying to use this app on my Mogul/Titan without success. I set it up on the button that would normally be conn mgr, went into cfg and set it to \windows\connmgr.exe
When I go to use the button I get a wait icon, the program launches and hides (still visible in Task Mgr). Opening manually works equally well (not at all).
The tools in the 2nd post don't work ("Class not registered" error).
While in a call the application launches (with a massive delay I might add) then performs its functino properly and mutes the call, no delays after initial launch.
There is no error log in the program's folder.
Help?

jhw549 said:
Trying to use this app on my Mogul/Titan without success. I set it up on the button that would normally be conn mgr, went into cfg and set it to \windows\connmgr.exe
When I go to use the button I get a wait icon, the program launches and hides (still visible in Task Mgr). Opening manually works equally well (not at all).
The tools in the 2nd post don't work ("Class not registered" error).
While in a call the application launches (with a massive delay I might add) then performs its functino properly and mutes the call, no delays after initial launch.
There is no error log in the program's folder.
Help?
Click to expand...
Click to collapse
The initial start of MobileMute does have a delay. That is the reason I created v2 that will stay running. If MobileMute shows in task manager after you run it, then it found the hardware button you have it assigned to and is listening for future presses of that button. Since it does Mute/Unmute the calls, the program is functioning as designed.
As for running "\windows\connmgr.exe". I also cannot run that program (even manually). I don't think it is an app to be used that way. Are you sure you don't actually want to run "\windows\CommManager.exe"?
-Jay

Heh.... umm... oops >.<
That's rather embarassing lol... You're completely right, I picked the wrong exe. It works 100% perfectly now.
I just wish it would hide completely and not show up in my tasks list... I have a tendancy to hit that kill all button rather than pick them out one by one.

thanks. this is a good idea... i'll be using it.

v2.1 with Fuze support
itsallwright said:
A friend of mine with a Fuze let me check it out and I determined why it does not work.
The dialer on the Fuze has Mute/Unmute buttons on the screen, but the buttons do not have text (I suspect it uses seperate Mute/Unmute images instead). That being said, MobileMute determines the Mute State of a call based on the text value of the Mute/Unmute buttons. Therefore, it does not know what command to send.
I am trying to figure out a way to work around this, but in the meantime, I am sorry to say the Fuze is unsupported.
Just as a fyi... the Mute/Unmute button IDs for the Fuze are the same as the Kaiser (21408/21409)
I'll keep you posted on my progress with supporting this device.
-Jay
Click to expand...
Click to collapse
Well, it turns out that the Fuze isn't the only device with that dialer. I recently found a ROM (Phoenix v2) that has touch flo and a similar dialer to the Fuze. I put that ROM on my Kaiser to reproduce this issue on my own.
After quite a bit of research and learning, I found a way to detect the Mute state of a call via TAPI. The Mute/Unmute button text is no longer needed.
I have no way to test with an actual Fuze, but I am pretty confident it will work now. I have added the new version to the original post.
-Jay

I've got v2.1 loaded. Detection on Fuze works, the registry shows mute/unmute id's 21408/21409. I'm using the short_PTT.lnk method. When I press PTT, I can see the titlebar flash 'MoblieMute' text.... but the mic does not mute.

jpn621 said:
I've got v2.1 loaded. Detection on Fuze works, the registry shows mute/unmute id's 21408/21409. I'm using the short_PTT.lnk method. When I press PTT, I can see the titlebar flash 'MoblieMute' text.... but the mic does not mute.
Click to expand...
Click to collapse
When you are not in a call, does it open the configured program (BubbleBreaker by default). Also, if you look in task manager, is MobileMute listed?
-Jay

How to lock Ans/End key

Usually when a call comes and the phone is inside the pouch (good for protection), there are several ways of messing up by accepting or rejecting the call even b4 its completely out of the pouch as blelow:
On screen:
1) U can press the on screen message but which will send an auto sms to the caller and end the call
2) U can press the answer key
3) U can press the ignore key
Off screen (hardware)
4) U press the answer key
5) U can press the end key
Incredibly, all 5 options are simultaneously active. The screen can be locked by S2U2 etc. but I cannot find any option of locking the hardware keys.
Any help will be appreciated

Firstly thanks for Omnia i8000 support on XDA..
Now I feel secure..
Secondly even I'll lyk to disable my hardware keys for call ans/end..
is there a registry tweak or something we can do to disable it..

s2u2 has that option... go settings/phone and u have S2A Hard ans/end key...

Search 542482 - there's an app for that over in the Mobile Apps & Games forum

Solution found!!!!
The issue was really troubling me and I finally found a solution. Install a small program called Incall lock which locks the call & end key. But that will totally disable u from accepting calls under WM6.1. So install s2u2 and enable screen response and voila!! U have. Both these are available elsewhere in this lovely forum.
Note:- The whole process during inplementation is quite messy as u will first have to install .net compact & samsung SDK software (both freely available).
4 software to do a simple thing which should have been taken care of by the OS. That's life under our billy, the goat.
Hope this help. I would be glad to give something back to this site, i have greatly benefited from.

TouchLockPro works great.
(I can't post a link yet...search for it in the Omnia 2 section at Modaco).

ad720 said:
TouchLockPro works great.
(I can't post a link yet...search for it in the Omnia 2 section at Modaco).
Click to expand...
Click to collapse
I tried tpro but it did not work for me. I am using wm6.1 under samsung touchwiz. Cud it b because of that ?

TouchLockPro is the answer, however, if both touch screen and the keys are locked on all in-coming calls, how the hell do you answer the phone? First to unlock it then answer it? A bit troublesome.

captkkk said:
TouchLockPro is the answer, however, if both touch screen and the keys are locked on all in-coming calls, how the hell do you answer the phone? First to unlock it then answer it? A bit troublesome.
Click to expand...
Click to collapse
See, even if no software was there u wud have to press a key or tap something to answer anyway. With S2U2 and incall lock, the only point of access is the slider (in my case) with which i can either accept or reject calls. So if i swipe to ans, the lock opens and i can straight away start talking. So there really is no extra step involved. Whereas, if I do not lock the key, I will have to be careful not to press the keys accidentally which is difficult as I often put it in my pocket and more so inside the pouch. I think the swipe to answer is the killer option.

bimboybimboy said:
See, even if no software was there u wud have to press a key or tap something to answer anyway. With S2U2 and incall lock, the only point of access is the slider (in my case) with which i can either accept or reject calls. So if i swipe to ans, the lock opens and i can straight away start talking. So there really is no extra step involved. Whereas, if I do not lock the key, I will have to be careful not to press the keys accidentally which is difficult as I often put it in my pocket and more so inside the pouch. I think the swipe to answer is the killer option.
Click to expand...
Click to collapse
Slide to Answer is great option to traditional Click to Answer, that is very true, however, that option has been adopted in 6.5 and some 3rd parties phone app as well, so if in i8000 case, the phone interface can be omitted and use the 6.5 or simply use those better and more feature phone apps

captkkk said:
Slide to Answer is great option to traditional Click to Answer, that is very true, however, that option has been adopted in 6.5 and some 3rd parties phone app as well, so if in i8000 case, the phone interface can be omitted and use the 6.5 or simply use those better and more feature phone apps
Click to expand...
Click to collapse
Well, as I said I hv 6.1 & 6.5 not yet available in my country. so...

Hi,
I installed Throttle Lock.. Nice lock... it has slide to answer..
secondly it does not interfere with the touch player, lyk s2u2 does..

Are you using Omnia II with WM6.1 ?
Because throttle lock is not saving the settings on my phone. And yes, I am clicking the "ok" button at the top right and getting a message "changes saved". And my slide to answer is ON but no slide is displayed. All I can see is the default lock screen which opens when I click on a button on screen but that certainly does not solve my problem. Using ver .07 (latest).
I have even registered myself. Hell, the config.xml file shows Calllock is on but its not even locking when the call comes. That should be the very basic default function. Sorry, back to s2u2.

I am using WinMo 6.1 original Rom...
I installed it on Storage memory.. and its workign fine.. It does interfere with the Samsund dialer when the call comes in... but I will try disabling the samsung dialer and check... back to your issue.. Try re-installing it.. and it should work.. iam able to save all my settings..
And when the call comes in My hardware keys are lock as well and I get option to Slide to Answer or reject..

Aafi-rocks said:
I am using WinMo 6.1 original Rom...
I installed it on Storage memory.. and its workign fine.. It does interfere with the Samsund dialer when the call comes in... but I will try disabling the samsung dialer and check... back to your issue.. Try re-installing it.. and it should work.. iam able to save all my settings..
And when the call comes in My hardware keys are lock as well and I get option to Slide to Answer or reject..
Click to expand...
Click to collapse
Thanks. I unistalled S2u2 and installed again. Still no. Yet the program was working when I clicked on it. So, luckily having some working knowledge of windows, I found that the program is not putting a link in the start menu or start up folder. This I had to do manually. But thats unclean.
And what happens when a call comes is funny. There is a brief fight between the throttle default , the windows splash & the lock screen itself. Luckily, the lock screen is winning every time. But again unclean or is it the links I have placed.
Currenly, I have links to both thottlelock & throttlelockdemon in the startup & lockdemon in the start menu. How is it with u?
Also in the setting under samsung default setup, the options like lock mode & incoming are white on white. What are your current settings ?
Think this program was designed for HTC. But is definitly smaller and though not neat...working. Thanks

I have mapped it to a hardware key, so when I want to lock I press the hardware key..

Aafi-rocks said:
I have mapped it to a hardware key, so when I want to lock I press the hardware key..
Click to expand...
Click to collapse
Use incall lock for locking the keys when call comes. Works perfectly.
Tried the throttlelock for 2 days. Sometimes, the default wm screen was coming up and the look is messy. So more experiements......but till date s2u2+incall lock looks the cleanest. Will keep looking...

captkkk said:
TouchLockPro is the answer, however, if both touch screen and the keys are locked on all in-coming calls, how the hell do you answer the phone? First to unlock it then answer it? A bit troublesome.
Click to expand...
Click to collapse
I'm using TouchLockPro. It's much faster and less memory consuming than S2U2 and it has multiple ways to unlock your phone!
In the newest version, you can unlock your phone by using the proximity sensor (and our Omnia II has one )
So if your phone wakes up in your pocket our pouch, it won't unlock, but if it wakes up in your hand or on your desk, it will unlock immediately!
Consequently, if you have an incoming call and the phone is in your pocket: It will remain locked until it's out of your pocket so you don't have to manually unlock before answering
I love it!

maardiweb said:
I'm using TouchLockPro. It's much faster and less memory consuming than S2U2 and it has multiple ways to unlock your phone!
In the newest version, you can unlock your phone by using the proximity sensor (and our Omnia II has one )
So if your phone wakes up in your pocket our pouch, it won't unlock, but if it wakes up in your hand or on your desk, it will unlock immediately!
Consequently, if you have an incoming call and the phone is in your pocket: It will remain locked until it's out of your pocket so you don't have to manually unlock before answering
I love it!
Click to expand...
Click to collapse
I hv omnia 2 with wm6.1. Tried touchlockpro and was absolutely useless. How is it possible ?

Can u plz put in the download link.. Iam sure its somewhere on XDA itself, but I am kinda lazy to search today.... I'll download it once I reach home..

Ringer-off switch doesn't vibrate

When switching the phone from ring to vibrate using the manual switch on top of the phone, isn't there supposed to be a short vibration as feedback to let you know the phone is silenced? When I switch from ring to vibrate, I get no vibration feedback, but everything else works correctly (meaning that the ringer and sounds really are silenced and switched to vibrate-only mode).
None of the Treos I've had in the past have had this problem of the "vanishing feedback" when switching to vibrate.
Does anyone know if there is a setting or a registry hack to re-enable this feature?
It is very convenient to be able to reach in my pocket and switch the phone to vibrate and to receive a short vibration to let me know I got the switch in the right position. Thanks in advance for your help!

You should try getting into Start menu >Settings>Sounds & notifications, and then notifications !
There should be a check box where you select to enable or disable the feature
Fyi

I have a similar issue...
I'm using 6.5 23549 RealVGA Updated from imzkng in ppcGeeks with the 'no windows/ok/X button' tweak and sometimes in start menu when a push 'lock' (or anything in the bottom bar) the Treo give-me a vibrate-feedback, ok I like it! but 95% of the time it just does nothing...
I bought a LG Cookie for my girlfriend and I LOVED the feedback and would like to put in my Treo... does anyone know how?

well, I found a program that rumble the way I want...
TouchResponse
U can config it to rumble when U touch and when your finger leave the screen... and other things...

well, i have the same problem with my custom wm 6.5 rom... as for the screen, touch response is a great addition (then i know when stuff freezes too )