Related
Hi i installed the rom and all is well but i installed that wififofum application and found it wasn't too great and so uninstalled it, Once i'd done this i went to the comm manager and the font had changed and its annoyin me a bit. Just wondering if ic an change it and if this has happened to anyone else? Thanks
Also another thing is that when i leave it for a while for example go to sleep, when i wake up the charge light is flashing green and no button will turn the screen back on, ive disabled the battery options that would normally turn it off but still does it. I all so have average battery when i turn it back on so its not that. I have slide2unlock could that be causing it?
Thanks again lol
Raggers,
First, take S2U2 off. It will be contributing to your problem. Secondly, simply reinstall the comm manager and you should be ok.
If you are sure that the rom you are using has the fake server tweak setup correctly (stops activesync from continuously getting in the way and locking up your phone; google on here for a more detailed explanation) and you are sure you don't have software being polled off an external SD card (will also cause lockups) then you can reinstall S2U2 with the following settings:
On battery power:
- Lock when backlight turns off: set to on
-But blank screen; set to off
- Blank screen on talk: set to off
On external power - have all settings set to off.
In the Avanced section:
- Dont suspend power: set to on
- Safe mode: set to on
- Directdraw: set to off.
These settings will stop S2U2 locking up your phone provided all the other things I referred to are sorted (just sharing my hard earned experience with you).
Let us know how you get on.
Cheers
WB
that is fantastic thankyou very much. One thing i was wondering, is there any good applications i could use to replace s2u2 as an automatic keylock? i wiull have to leave it a while to test but thankyou very very much for the suggestions
01/26/09 - This is just a minor update to fix some issues and add a couple small features.
Feel free to give comments or ask questions.
Thanks!
This program is a touch driver to handle the touchscreen presses and vibration. A settings program exists to configure how the vibration works.
Since this is a touch driver, there is no program you need to run to start it.
It has been tested on an HTC Touch and HTC Touch Pro for several days with several stability issues corrected. I am only releasing this now that I feel comfortable that you will experience no major issues. However, I cannot guarantee that it will work flawless for you. I cannot be held responsible for any loss of data or time you may experience while using this.
If you are experiencing problems after installation, please let me know so I can fix these issues.
Features
Global enable/disable option
Vibrate on touch/release
Variable duration of vibrate
Disable during Phone Call option
Disable when device is silent
Disable when device is locked
Disable when stylus is out (for devices that support this option)
Enabled for On-Screen Keyboard only (Temporary option until full include/exclude list is incorporated)
Settings Program->Settings->System->TouchResponse Settings
AppToDate support
Coming Soon
Include/Exclude list for vibration
Different vibration patterns
Resolve any software conflicts
Vibration tweaks
Sound on touch
Vibrate on hardware button press
Multi-language support in Settings program
I'm open to suggestions...
Known Issues
May or may not play well with touchflo/ftouchsl. If TouchResponse isn't working for you, try disabling those if they are enabled.
Disable when device is silent may not work on some devices. Let me know what kind of device you have if this is the case for you.
Donate
This is a free program and I plan on keeping it that way. If you enjoy using it and would like to support its development, please consider donating by clicking here:
Donate $ | Donate €
Change Log
.3.2 (01/26/09) - Minor update
- Option to disable vibration when device is locked
- AppToDate now supported - Download AppToDate to be informed of the latest updates
- Fixed issue when SIP Only didn't work as expected in landscape mode
- Fixed issue when Stylus Out still resulted in vibration when that option was set.
.3.1 (01/14/09) - Minor update
- Should properly upgrade when built into a custom rom
.3 (01/13/09) - More features
- Option to vibrate on release of touch
- Option to disable vibration when stylus is out
- Option for vibration to only be enabled for on-screen keyboard
- Better auto-detection of device model/vibrate id
.2.2 (11/27/08) - More Minor Updates
- Can increment the duration by one instead of five now
- The chance for a longer than usual vibration should be reduced if not eliminated altogether
- Disable while silent option should work a little better now
- Settings program allows for more Vibrate IDs in the Advanced tab
.2.1 (11/26/08) - Minor Update
- Windows Mobile 5 is now supported
.2 (11/26/08)
- Attempt to resolve suspend issues with certain phones - Let me know
- Disable while silent option added - may not work perfect
.1 (11/24/08)
- Initial Release
Questions and Answers
Q. How to I change the settings?
A. Start->Settings->System->TouchResponse Settings
Q. Why do I not see the settings program?
A. For some phones, the settings program does not appear in the control panel. Until I figure out a fix, you can run the program by going to \windows\TouchResponseSettings.cpl
Q. Why is it not vibrating when I touch the screen?
A. Go to the Device tab in TouchResponse Settings. It will display information about your device. If it says to select your vibrate id then find the one that causes the vibrate to work. Send me a PM with the name of your device model along with the vibrate id that works for you and I will incorporate that into future releases.
Q. Will this drain my battery life?
A. I don't have any statistics to show the before and after battery usage. However, I personally have not experienced any significant increase in battery usage. It all depends on how long the vibrate duration is and how often you touch the screen.
Q. Why does the vibrate last longer than it's supposed to sometimes?
A. This should hopefully be resolved as of version .02.2. If you experience this after this version, please let me know when it happens and how often.
Q. Why is the vibration always the same duration no matter what the settings are set at?
A. Use a registry editor to go to HKEY_LOCAL_MACHINE>Software>OEM>VIB and set STRENGTH_LOW to 0. Thanks to agdaniels for pointing this out.
Please don't post this cab on any other site. Let's keep all discussion here. I appreciate your cooperation.
Thank you for your support!
Ill try it and let ya know how it compares
Nice idea, thanks for sharing.
I read about a phone (I think it was LG Incite?) where some people complained about vibrating even when entering text with the soft-keyboard.
Could you give us an option to dis-/enable vibrating when entering text ? Maybe there´s an event you can use when the soft-keyboard flips up...dunno
regards,
Martin
m.schmidler said:
Could you give us an option to dis-/enable vibrating when entering text ? Maybe there´s an event you can use when the soft-keyboard flips up...dunno
Click to expand...
Click to collapse
Since the driver has first crack at the touch event, I should be able to determine which window is being touched and either vibrate/not-vibrate depending on how it's configured. For example, I can see that the SIP is being touched and not vibrate. I'll add that to the list, Thanks!
Just as Martin said.
When typng on the on screen keyboard. Vibrate on every button of the keyboard we pressing. That would be awesome.
Gonna test this on the X1i
It works great on my HTC touch PRO.
Yea Man !!
I love this Apps !!!
Thanks so much
all feature Works like a charm in my Kaiser (HTC TyTN II)
Well I guess I will put my suggestion here as I did with the other 2 programs like it. Would you consider creating a setting to were it is only active on SIP Keyboard AND when SIP keyboard is active I have choice between a vibration or a sound or both?
I know I can get a sound by going to the general settings of winmo but when it is on it makes a noise for all screen taps...annoying!!
CuriousG
curious george said:
Would you consider creating a setting to were it is only active on SIP Keyboard AND when SIP keyboard is active I have choice between a vibration or a sound or both?
Click to expand...
Click to collapse
Since this is a similar comment among everyone I will focus on this next. Thanks everyone for your feedback!
how about different types and lengths of viberations like the old motos used to have? dash-dash-dash-buzzz haha
maybe different intensities if possible?
I've always wanted 'heptic feedback' on my KS20 but non works for me. I've tried Heptick Feedback, Vibration Feedback and now TouchResponse, none work for KS20. Duh....
Can these options be added?
1. Not to vibrate when on silent?
2. Change buzz length (make it shorter/less intense)
3. An "use only when SIP activated" option.
richabi said:
how about different types and lengths of viberations like the old motos used to have? dash-dash-dash-buzzz haha
maybe different intensities if possible?
Click to expand...
Click to collapse
This is something I've been wanting to experiment with. I'll add that to my list, Thanks!
stutzedward said:
I've always wanted 'heptic feedback' on my KS20 but non works for me. I've tried Heptick Feedback, Vibration Feedback and now TouchResponse, none work for KS20. Duh....
Click to expand...
Click to collapse
You may have tried something similar with the other programs you have tried, but you can try changing the Led Id in the Settings program under the Advanced tab. Be sure to press ok to make the settings to into effect. Hopefully it is just a case where the KS20 doesn't use the default Led Id for vibrate.
derekwilkinson said:
Can these options be added?
1. Not to vibrate when on silent?
2. Change buzz length (make it shorter/less intense)
3. An "use only when SIP activated" option.
Click to expand...
Click to collapse
1. Yes, this is something I want to add! It's sometimes hard to go unnoticed when I use my phone in meetings at work when the vibration is loud.
2. Did you see the Settings program in the System tab of the "Control Panel"? Or do you mean a something like a longer buzz but less intense?
2. I'm going to be focusing on that with an include/exclude option next.
Thanks for your feedback!
Snailslug said:
You may have tried something similar with the other programs you have tried, but you can try changing the Led Id in the Settings program under the Advanced tab. Be sure to press ok to make the settings to into effect. Hopefully it is just a case where the KS20 doesn't use the default Led Id for vibrate.
Click to expand...
Click to collapse
Hey hey, it works for KS20 for the first time!!!!
I set the LED from 0 to 3 and hey, 3 works.
0 - LED displays green
1 - LED displays red
2 - LED displays blue
3 - it worked!
Thank you soo much! I gotta spread this on the KS20 thread because a lot of KS20 users are wanting this like me. I'll link them here.
very good work.
i have mine set to 25ms and the vibrate is a perfect length and silentness.
i agree on only sip active and/or blacklist
Just want to echo what's already said. What most ideally want is for vibration to be active ONLY on keyboard when text entering and to be as brief a buzz as possible. Some owners type very fast and we want the buzz to keep up and not still lag on the previous tap while tapping on the next key. It has to be super quick and not miss a key press when typing quickly. Thanks!
Ok, found the settings app, my bad
The other two requests would be awesome if they were to be fulfilled!
whats the difference between this program and this one : http://forum.xda-developers.com/showthread.php?t=425063 ??
My new HTC S740 is excellent except for one thing - the keypad backlight goes out after only 15 seconds. Very irritating in the dark.
I've looked for kb_light_timeout in hklm/software/htc/keypad but this does not exist.
I've found keylight timeout and qkeyledtimeout in hkcu/control panel/backlight which looks like the right place but altering values and rebooting makes no difference.
I've also looked in hklm/drivers/builtin/keylight and keypad.
I feel I'm very close. Can anyone help?
Yes Its most annoying as well as fact that only numbers or keys round circular button light seperately. Look forward to someone cracking it. Otherwise an excellent phone.
I agree, this is very annoying.
So theres no fix for this issue? To bad no ACT for this phone. An awesome phone, just wm standard gets so little love it seems.
I did some research today and he're the results:
1. This is far of to be a new issue. First complaints about the keyboard backlight timeout you can find under Qtek models...
2. Apparently, they were just few (2-3?) HTC models supporting a registry entry included in WM hkcu/control panel/backlight/QKeyLedTimeout - Rose definitely doesn't
3. The issue could be a case of WM 6.1 limitation - Rose has in fact three keyboard backlight arrays with separate light managements (soft keys, numeric, QWERTY - try to use them simultaneusly and you will see - their timing is independent on each other) and I've found some extra HTC registry entries concerning power management confirming a bit non-standard settings. Unluckily, nothing useful there for the kb backlights.
Sorry, based on my experiments, I can advice you only one very strange way how to overcome it for now: Limit the display timeout to the same 10 seconds as the keyboard has. At least, first press of any key will become inactive and just light-up both display and keyboard. Until display works, all keys are still active even the keybord backlight is off.
Nevertheless, any opposite finding will be appreciated...
Thank you for your investigation
I have a new s743 and this is the exact problem I came searching for fix for!
Too bad - it really is a sweet phone.
-John
To me this is a winmo thing. I don't understand why this option isn't included from the factory. It is a plain "NO BRAINER"! It's been this way on all my previous devices whether pro or standard. The diff being the pro os has wonderful tweaks and various cabs one can install to set the time out. What we need is to get some tweaking guru to set up something like ACT for standard. Problem is so little love for the standard os. The screens are to small anyway for my taste. I'll just stick to pro, the tweaks are better.
Well, i set the display timeout on my device to 5 seconds. Backlight of the qwerty and numeric keypads went off after 5 seconds.
The softkeys remained lit till 10 seconds was up.
TouchLockPro is not exactly new (currently at version 1.9), but it was posted in the Diamond thread, because there things started. But because other phones are also supported, maybe the TouchLockPro thread could move to here. If this cross posting is not wanted, I hope the moderators let me know how to continue. At the Diamond thread or in this one?
But Windows Mobile has an OEM screen locker!
Yes, Windows Mobile locks the screen, but unlocks the Answer and Ignore buttons as soon as a call rings, so it is useless. The same happens when any notification pops up, the Snooze and Dismiss buttons are enabled even when screen is locked, leaving them vulnerable to any accidental touch.
Supported phones (known)
Touch Diamond
Touch Pro
Sprint CDMA Diamond
Touch HD (only triple touch capacitive sensor for unlock does not work)
Summary
There are already a lot of applications to disable touchpanel and/or hardware keys for the Touch Diamond and Pro. I added yet another one:
* lock using the Power button, BattClock and/or Stylus Sensor
* auto-unlock by the Light Sensor
* unlock using triple touch of the Capacitive Sensor
* unlock using Stylus Sensor
* unlock when on AC/USB power
Why is TouchLockPro better than other locking solutions
TouchLockPro is designed not to interfere with running applications and is a multipurpose locking application. Other locking solutions are often specific for locking only incoming calls/SMS. A lot of locking solutions also place a (transparant looking) Window on top of the running application (e.g. slide 2 unlock), so the information of the background application is no longer visible. This is not the case for TouchLockPro, so it can be kept lean and mean. Also the used resources is very very low.
Does TouchLockPro use much battery, RAM, CPU
Not at all, TouchLockPro is designed to be lean and mean!
TouchLockPro does not have noticeable effect on battery life. It only uses 33 Kb RAM in memory, whereas other solutions often use much more. For example S2U2 uses 4 Mb (125 times more) and PocketShield 1.7Mb (50 times more) memory. TouchLockPro uses 0% CPU (check it with a task manager!) and is totally event driven. Polling is kept to a minimum (currently only for polling once per second the light sensor when LOCKED and the screen is on). Requested features which would violate the "lean and mean" principle are rejected. Note that larger UI related stuff is done in a separate TouchLockAction.exe (e.g. editing settings), so the memory is only used when that program is active for a small moment.
Which other solutions exist
This is a list of other solutions, which may suit you better:
* Built in locking of Windows Mobile
* Stylus(BattC)lock
* Get A Reward! Create A "answer Only With Hw Buttons" Option!
* S2U2
* PDAVIET's dialer
* CSDEVCTRL
* SensorLock
* Answerkeys Disabler
* PocketShield
* ThrottleLock
Interested in *FREE* TouchLockPro?
I just posted TouchLockPro version 1.8.
I also posted the source code belonging to version 1.8. Hope you will learn something from it and you are inspired to make great programs too. At the end programming Windows Mobile is not so difficult if you have programming experience. Prerequisites for programming:
* Visual Studio, Express editions are free!
* Windows Mobile 6 Professional SDK (also free)
Note that others pointed out, that Express editions are not suitable for Windows Mobile development. See Smart Development for what is supported by which version. I used myself Visual Studio 2008 Professional SP1.
Note that TouchLockPro is written in C++ and TouchLockAction in C# (and deployed using .NET Framework 2.0).
Enjoy the software and source code
you can lock specific programs? waaahhh? this is what I've been waiting for for a very long time. downloading right now.
lennie said:
you can lock specific programs? waaahhh? this is what I've been waiting for for a very long time. downloading right now.
Click to expand...
Click to collapse
I do not know if HTC x7501 has the same sensor like capabilities. Does it work for you? Or do you have another phone too?
anybody tried with tytan II ?
shuren said:
anybody tried with tytan II ?
Click to expand...
Click to collapse
TouchLockPro uses the unique sensors since Touch Diamond was brought out:
* auto-unlock by the Light Sensor
* unlock using triple touch of the Capacitive Sensor
So probably those functions will not work on your phone. BUT I continue without those functions when the loading of the needed HTC libraries fails.
There is also a stylus sensor, but TouchLockPro just observes a registry key for detecting if the stylus is in or out. So you can check if that registry key also exists on your phone, before you try to install:
HKCU\ControlPanel\Keybd\StylusOutStatus
1 = out
0 = in
If this registry key does not exists, probably TouchLockPro will not work for your phone.
For the rest it is standard Windows Mobile programming, although the locking of the hardware keys may also not work. But the locking of only the TouchPanel should work (setting "LockTouchPanelOnly = 1". TouchLockAction is written in C# and needs .NET Compact Framework 2.0.
Note that controlling the locking only with the stylus is also doable, actually my first version only supported this:
StylusLock
So you could use TouchLockPro with only the Stylus (if that registry key is written) and/or LockTouchPanelOnly, you miss only some of the unlocking features. Actually if you only lock the touchpanel, you can assign the command "\Windows\TouchLockAction.exe unlock" to a hardware key for unlocking.
Hope this helps......
So you say it won't lock some hardware buttons...this won't get around the problem with Samsung i730 and the power off key?
No program I have found yet can lock that hardware key to prevent it from powering off while in my pocket
EDIT: Nevermind...it isn't supported on the i730 anyway
First of all:
Congratulations for your post. Didn't see a long time an informative post like this - your own program is introduced, the reason for doing it AND other existing solutions!!! Hat off to you.
ZuinigeRijder said:
I also posted the source code belonging to version 1.8. Hope you will learn something from it and you are inspired to make great programs too. At the end programming Windows Mobile is not so difficult if you have programming experience.
Click to expand...
Click to collapse
Thank you very much for sharing the source code. It is for sure helpful in both ways - to learn and to get inspired. I already took my hat off otherwise I would do it again.
StrykerC3 said:
So you say it won't lock some hardware buttons...this won't get around the problem with Samsung i730 and the power off key?
No program I have found yet can lock that hardware key to prevent it from powering off while in my pocket
EDIT: Nevermind...it isn't supported on the i730 anyway
Click to expand...
Click to collapse
Actually it does lock ALL hardware keys, even "Power Off" key.
But maybe you meant the "Power On" key (actually, the same key).
That is why TouchLockPro does also lock immediately at Power On or Screen On (due to an external event, incoming call, or via pressing the power on key).
Code:
// --------------------------------------------------------------------------
// HTC Touch Panel
//
// Reverse engineered from HTC's TPEnable.exe and TPDisable.exe
// --------------------------------------------------------------------------
#define IOCTL_HTC_HAL_ENABLE_TOUCHPANEL CTL_CODE(FILE_DEVICE_HAL, 2698, METHOD_BUFFERED, FILE_ANY_ACCESS)
struct STouchPanel {
BYTE n1;
BOOL bEnable;
};
DWORD nBytesReturned;
STouchPanel s = { 0, !disable };
KernelIoControl(IOCTL_HTC_HAL_ENABLE_TOUCHPANEL, &s, sizeof(s), NULL, 0, &nBytesReturned);
But indeed, it will not work on your phone
ZuinigeRijder said:
Actually it does lock ALL hardware keys, even "Power Off" key.
But maybe you meant the "Power On" key (actually, the same key).
That is why TouchLockPro does also lock immediately at Power On or Screen On (due to an external event, incoming call, or via pressing the power on key).
Code:
// --------------------------------------------------------------------------
// HTC Touch Panel
//
// Reverse engineered from HTC's TPEnable.exe and TPDisable.exe
// --------------------------------------------------------------------------
#define IOCTL_HTC_HAL_ENABLE_TOUCHPANEL CTL_CODE(FILE_DEVICE_HAL, 2698, METHOD_BUFFERED, FILE_ANY_ACCESS)
struct STouchPanel {
BYTE n1;
BOOL bEnable;
};
DWORD nBytesReturned;
STouchPanel s = { 0, !disable };
KernelIoControl(IOCTL_HTC_HAL_ENABLE_TOUCHPANEL, &s, sizeof(s), NULL, 0, &nBytesReturned);
But indeed, it will not work on your phone
Click to expand...
Click to collapse
Well right, power off/power on, but when the phone is powered off, I am not worried about it being power on by accident, only the other way around
Why can't any one make a program for WM5 that can disable the Power On/Off key?!?! Ugh!
Finally!
So far, this seems to be the best solution to accidentally pressing hardware buttons or screen buttons while the phone is in my pocket. When using bluetooth I was constantly hanging up on people. Also, I would accidentally call people with the phone in my pocket when an SMS or e-mail would "wake up" the phone and then 2 unknown presses of the hardware "answer" button would first bring up call history and then call the first person on the list. I'll wait a few more days and, if all is well, I'll make a donation. Thank you so much for your effort. (tried Sensorlock, S2U2 and Answerkeydisabler but none did the trick)
mspingeld said:
So far, this seems to be the best solution to accidentally pressing hardware buttons or screen buttons while the phone is in my pocket. When using bluetooth I was constantly hanging up on people. Also, I would accidentally call people with the phone in my pocket when an SMS or e-mail would "wake up" the phone and then 2 unknown presses of the hardware "answer" button would first bring up call history and then call the first person on the list. I'll wait a few more days and, if all is well, I'll make a donation. Thank you so much for your effort. (tried Sensorlock, S2U2 and Answerkeydisabler but none did the trick)
Click to expand...
Click to collapse
I am a bit surprised the other locking solutions do not work well together with bluetooth. Others reported indeed that TouchLockPro does not interfere with bluetooth and you can pick up the phone with bluetooth, although the keys are locked.
Enjoy the software
The other solutions worked with bluetooth but the bluetooth call connection would wake up the phone and activate either the screen, the hardware buttons, or both causing the accidental hang ups or calls. TouchLockPro locks both the screen and the hardware buttons. btw I have the touches set to 2 and the light sensor set to 500. Very convenient!
mspingeld said:
The other solutions worked with bluetooth but the bluetooth call connection would wake up the phone and activate either the screen, the hardware buttons, or both causing the accidental hang ups or calls. TouchLockPro locks both the screen and the hardware buttons. btw I have the touches set to 2 and the light sensor set to 500. Very convenient!
Click to expand...
Click to collapse
Good to know.
In the upcoming version TouchLockPro 1.9 I will introduce the ScreenOffWhenCallConnected option, so you cannot accidently press stuff with your ears. Also I will introduce the option UnlockWhenCallConnected, so you can still use the hardware keys, when the screen is off (e.g. for ending the call) and it is not locked when the call is ended from the other side.
Dependent of the bluetooth usage, if you have the phone in your pocket, you may want to disable these settings.
TouchLockPro version 1.9
I just uploaded version 1.9.2 on my new website.
See TouchLockPro thread for more details.
Many thanks to Dennis van de Sande, alias Mr_Q from XDA-Developers, for sponsoring/donating the website and domain.
I wish you a merry christmas and a happy new year!
Version 2.0
I uploaded version 2.0, which fixes some (small) issues and added some features, like unlocking when sliding the keyboard out (if available). See Version 2.0
[APP][Updated 11-01-2009] TouchLockPro version 2.1
I just uploaded TouchLockPro version 2.1. Hope this version is again more perfect.
TouchLockPro 2.2.1 with GSENSOR support for unlocking
I just uploaded TouchLockPro 2.2.1 with GSENSOR support for unlocking.
TouchLockPro version 2.3
TouchLockPro version 2.3 is available.
How to unlock using touchprolock?
Im using xperia (no gsensor, no light, etc) ??
royalbloodvi said:
How to unlock using touchprolock?
Im using xperia (no gsensor, no light, etc) ??
Click to expand...
Click to collapse
Then you must unlock with a key sequence, using TouchLockPro 2.8.2.
See http://www.zuinigerijder.com
I found the following problem with most cooked ROMs (also including the last official one from HTC) /I tried that on fresh installations in every case/
I like AutoLock feature. So I made a small .reg file to modify one small entry in registry.
The moment this feature is on - if the device becomes locked, the screen goes dim. Problem is - it stays dimmed forever. I tried thousand different solutions - many combinations of registry values, power options, etc. nothing helps. If I lock the device manually - no problem. only with autolock. Anybody knows how to make it work?
Regards,
Vojtek
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Try using SmartLock, found on this site.
jmckeejr said:
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Click to expand...
Click to collapse
The official HTC ROM that I used to have before recent official update from HTC - worked very fine with this little registry mod.
The modification is as follows:
HKCU->ControlPanel->Backlight->AutoDeviceLockEnable
default value = 0
I change it to 1. This is all I do after totally fresh ROM update. that causes the dim to go permanently on from the next lock (doesn't matter if it was caused by auto or manual). even If I get back with the value to 0 in registry - problem stays. soft reset (and value set to 0) eliminate the problem.
one more thing - I never use auto-light sensor. My backlight level is always set to 2. with auto-light sensor - autolock works OK. however I loose a lot of battery life since auto-light sensor never allows backlight levels lower than 4.
Regards,
Vojtek
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
GldRush98 said:
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
Click to expand...
Click to collapse
Thank You for the tip. The tool itself is great. However it is affected same way by the autolock. Autolock causes device to stay dimmed permanently - even with Lumos running.
Regards,
Vojtek
First off... I'm new around here & still a little flabbergasted by everything WinMo, but this site has already helped me tremendously.
Secondly, I can confirm the AutoLock bug. I updated my Touch Pro to the latest official rom last night. While running through AdvancedConfig (i think...) I noticed the AutoLock option & enabled it. 10 minutes later I was freaking out that I had stuffed up my expensive new toy...
Disabled, rebooted & all is OK again.
First of all - Advanced Config has nothing to do with it (to defend the author).
Second - thank You for support. I could not find a solution for this problem anywhere and I spent hours googling. For the moment I thought that my TP is failed. Seems that nobody uses AutoLock these days. I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time...
Vojtek
vojtek11 said:
I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time.
Click to expand...
Click to collapse
I require a password/passcode level of security on my device - which the Lock/Unlock feature doesn't provide. Unfortunately, the current security implementation in WinMO 6.x doesn't allow the Today screen to be seen like the Lock/Unlock feature.
As a result of these shortcomings, most folks tend to use a 3rd Party lock application such as: S2U2, mLock, etc. as they provide the desired flexibility.
HTH,
very familiar with this issue. I'm working on it too. It affects the WM6.5 lockscreen for sure and I thought it was a problem with only that. Bugger that it affects official ROMs as well. Good info though, I can stop concentrating on the lockscreen and start looking at power mgmt.
mindfrost82 said:
Try using SmartLock, found on this site.
Click to expand...
Click to collapse
SmartLock all the Way!!