Database Develop

Locking phone after certain duration

Hi guys,
I've tried looking thru the settings of my phone for locking my phone after certain duration but i couldn't seem to find it. is there a way in the phone? cause sometimes i get too busy to even hold on to the 'end key' for 3 secs and and just dump it into my pocket. ended up it goes to other programs or something else.
hope you guys can point me in the right direction. i also found 3rd party software to do this but is there a need to?
anyway i'm not refering to getting timeout to the password screen.

Personally, I didn't find this kind of feature too,
but there is a nice app, that will do this for you
http://forum.xda-developers.com/showthread.php?t=412418

Automatically lock your Diamond --> HKEY_CURRENT_USER\ControlPanel\BackLight\AutoDevic eLockEnable from 0 to 1 and everytime your backlight goes off the device is locked
Delay device autolock: HKEY_CURRENT_USER\ControlPanel\BackLight\AutoDevic eLockTimeout -> Change the Dword value (30 = 30 seconds, etc)
http://forum.xda-developers.com/showthread.php?t=398265

ah... apparently i didnt look hard enough for the possible tweaks.
i was trying out maniac's auto keylock. didnt quite suit me.
thanks a lot guys

SurfHost said:
Automatically lock your Diamond --> HKEY_CURRENT_USER\ControlPanel\BackLight\AutoDevic eLockEnable from 0 to 1 and everytime your backlight goes off the device is locked
Delay device autolock: HKEY_CURRENT_USER\ControlPanel\BackLight\AutoDevic eLockTimeout -> Change the Dword value (30 = 30 seconds, etc)
http://forum.xda-developers.com/showthread.php?t=398265
Click to expand...
Click to collapse
ok for the first tweak i understand what it meant.
but what does the second tweak do exactly?

Its suppost to delay the autolock for the specified amount of seconds after the backlight turns off.

Backlight problem

I'm having this problem with backlight. No matter what I do, the screen automatically dim after 10-12 seconds. I've turned off the all "Turn off screen after so many minutes" (on battery or on AC). I've changed the backlight settings and it still revert.
I've even watch the backlight setting moved back to minimum from max after that 10-12 seconds.
I can't figured out what is overriding the setting. I don't have much installed:
WM 6.1 with
HTC Home
HHC
BatteryStatus
TouchPal
Wizard_reTOUCHed_Dialer2
Any thoughts?

Settings->System->Backlight & Settings->System->Power
To control BACKLIGHT settings, i.e. Backlight Brightness, Backlight timeout, etc, go to:
Settings->System->Backlight
...and check OFF the checkbox in the "Battery power" tab...or leave it checked ON and adjust the timeout
To control SCREEN settings, i.e. when does the screen turn OFF COMPLETELY, etc, go to:
Settings->System->Power
...and check OFF or adjust the timeout for the timeout that takes the device into standby mode
note that the above two settings applets are linked to each other from within via the Menu softkey
if you have already done BOTH of the above, i've no idea why your backlight dims so quickly

You have batterystatus installed and if you go to the preferences in it you have backlight as an option adjust your settings in there.

msg1285 said:
You have batterystatus installed and if you go to the preferences in it you have backlight as an option adjust your settings in there.
Click to expand...
Click to collapse
Sweet! That was it. Thanks for the tip.

I don't have batterystatus installed. I do have pockettoolman but it uses regular power and backlight settings.
My issue is even without any reset, the backlight setting automatically resets to default 10s. I change it to 2min, but at some point it will reset itself to 10s. This is without reset or turning phone off. I don't know y it does this but its very annoying!
Any ideas? Thanks.

I am having the same problem as well here... the backlight timeout will automatically reset to 10sec everytime you switch on the phone (not soft/hard reset, just normal power on). I am using ATT Tilt with the offical WM6.1 ROM.
Tried to change the setting directly in Registry using Resco, still the same problem. The value got reset to 10 on the next power on.
Wondering if anyone got a solution to this?
(maybe it's a problem for ATT tilt only....some users posted the same problem in the official ATT forum
http://forums.wireless.att.com/cng/...thread.id=99891&view=by_date_ascending&page=8 )

I'm having similar problem with back light and also it is very annoying when screen goes black and kills wifi and gps. is there way to keep wifi and gps on when backlight goes off? thanks.
WM6.1 dutty's WWE rom, Att Tilt

ATT Tilt Backlight Fix {Maybe}
I have to put this here
"Making registry changes incorrectly can cause system-wide problems that may require you to re-install WM6.1 to correct them. Making changes at your own risk."
=======================================================
Well here some settings to try:
HKCU\ControlPanel\BackLight
There are several settings here with the word "Timeout" in them:
Assuming External Power
===================
ACTimeout
ACTimeoutTemp
ACTimeoutTempUnchecked
Assuming In Battery
=================
BatteryTimeout
BatteryTimeoutTemp
BatteryTimeoutUnchecked
Make them all 300 for 5 minutes
Now one interesting one...
AutoSensor try changing 1 to 0
Test run....
==================
Power on/off using switch etc..
Performed soft-reset using stylus...
Display did not timeout after 10 seconds... But is did appear to power off after 5 minutes...
To soon to say how long this will last, but it definately appears to have made a difference and now seems to last longer. Something like 2 or minutes. Go figure

I was pretty happy with the new AT&T 6.1 Rom until this problem came up. The ROM is fast, the battery life with the 1.65xxx14 radio is good.
After a couple of days trying to fix it based on some solutions I found on the internet, I have given up.
No matter what I did, it always came back even with just having exchange push mail and total commander installed only.
Reverted back to WM 6.0 just because of this problem that was very annoying...
Now I am having a problem flashing a different hard spl instead of the 3.56 on my phone for WM 6.0.
Anyway, so, has the problem come back yet?
Thx
Oz

Still no solution to this problem? I'm a little afraid to try registry hack but am getting desperate.
I also now notice volume resetting issues...volume will change on its own accord to different settings...

The registry tweak fixed problem.
Only changed the first batterytimeout to 96 (2 min).
It now timeouts after 2min and survives a soft reset.
Thank you!
tkellytpa said:
I have to put this here
"Making registry changes incorrectly can cause system-wide problems that may require you to re-install WM6.1 to correct them. Making changes at your own risk."
=======================================================
Well here some settings to try:
HKCU\ControlPanel\BackLight
There are several settings here with the word "Timeout" in them:
Assuming External Power
===================
ACTimeout
ACTimeoutTemp
ACTimeoutTempUnchecked
Assuming In Battery
=================
BatteryTimeout
BatteryTimeoutTemp
BatteryTimeoutUnchecked
Make them all 300 for 5 minutes
Now one interesting one...
AutoSensor try changing 1 to 0
Test run....
==================
Power on/off using switch etc..
Performed soft-reset using stylus...
Display did not timeout after 10 seconds... But is did appear to power off after 5 minutes...
To soon to say how long this will last, but it definately appears to have made a difference and now seems to last longer. Something like 2 or minutes. Go figure
Click to expand...
Click to collapse

Back light issues Mobile 6.1
I have the TILT with 6.1 installed.... My backlight with default to 10 seconds also.. alog with that when I Turn the phone ff using the power button, if I sit there and watch it the backlight will come on with a black screen. Just backlight for no ryme or reason... I also have the issue of the screen brightness going full bright on me. All of these issues have really taken a toll on my battery life. Any thoughts from anyone...

I found that for some reason (probably Battery Status?) my backlight would always revert to 7-seconds when on battery. Every time I changed it via the control panel applet I could then go and see the value in the registry getting changed to 7. If I manually changed the value in the registry it would always revert to 7 after a short while.
I found that removing the 'BatteryTimeout' entry from the registry (HKCU\ControlPanel\BackLight) and not touching the Backlight control panel applet (or changing Battery Status) prevents it being automatically updated to 7-seconds and applies the default of 30-seconds.
I am not sure if this will work for you as there seem to be variable results, however for me this works perfectly. I have all my defaults set in my custom ROM so I never need to change Battery Status or open the Backlight applet and the default 30-seconds for the backlight is set.
Andy

Here is a link to a cab to address this issue
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=1&dl_id=269

jgatlin1 said:
Here is a link to a cab to address this issue
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=1&dl_id=269
Click to expand...
Click to collapse
Just to confirm I have just extracted the 'backlight.dll' file from the update posted on HTC's website and cooked it into a ROM, replacing the original 'backlight.dll' and it does indeed solve the problem.
I have played around with the backlight control panel applet and opened and closed Battery Status and the delay remains at what is configured - 30-seconds in my case.
Andy

ADB100 said:
Just to confirm I have just extracted the 'backlight.dll' file from the update posted on HTC's website and cooked it into a ROM, replacing the original 'backlight.dll' and it does indeed solve the problem.
I have played around with the backlight control panel applet and opened and closed Battery Status and the delay remains at what is configured - 30-seconds in my case.
Andy
Click to expand...
Click to collapse
Scratch what I said in my previous post. With this updated .dll file the behaviour of the backlight is worse. I have done some testing today with the updated 'backlight.dll' file cooked into a ROM and it's painful. No matter what I try the registry values 'ACTimeout', 'BatterTimeout' & 'timeoutsaved' are ALWAYS reverted to a value of 8 once the keylock has been applied. In my case either by Battery Status (keylock on resume) or pressing the today screen icon. This results in the backlight dimming after 8-seconds when on either battery or AC, the only way to resolve is to either go to the backlight control panel applet or edit the registry directly. Hit the keylock though and your back at square one
I have now re-cooked my ROM and replaced the 'backlight.dll' for the previous one and the behaviour returns to normal. So my advice is don't install this patch or cook it into your custom ROM.
Andy

ASCIIker said:
To control BACKLIGHT settings, i.e. Backlight Brightness, Backlight timeout, etc, go to:
Settings->System->Backlight
...and check OFF the checkbox in the "Battery power" tab...or leave it checked ON and adjust the timeout
To control SCREEN settings, i.e. when does the screen turn OFF COMPLETELY, etc, go to:
Settings->System->Power
...and check OFF or adjust the timeout for the timeout that takes the device into standby mode
note that the above two settings applets are linked to each other from within via the Menu softkey
if you have already done BOTH of the above, i've no idea why your backlight dims so quickly
Click to expand...
Click to collapse
Thanks so much for this post. I have been trying for days to get my back light to stay on and nothing worked. As it turned out I was only doing the setting in the backlight tab, not the in the power tab.

Finally!
Click Here for the .cab that fixed my unit. I got it off the ATT forum.
NOTE to all... Even this fix did not solve my problem until I checked the boxes to time the backlight. I like the backlight feature on all the time. If I don't want to see the screen, I turn it off.

[APP] LevelSight 1.1.0.2 2009.09.16 - backlight enhancement for Acer 900s and HTC

Seriously consider donating something like $1 if you want software from me to continue, as johnpatcher had suggested.
This was originally built to flatten the brightness levels between AC and BATT on the Kaiser, but since lacking a workable front-camera API access, this works out better on devices with a light sensor.
/// new Acer m900 support
Since this device has only 3 auto-brightness settings, a full sensor-to-backlight curve is used -- configurable in HKCU/SOFTWARE/Creative 'Ware/LevelSight/0-a -- to map the 11 brightness settings actually available.
Brightness levels to about 4 have been hand-tuned and then it's a linear scale to max brightness.
Currently, the settings are loaded only on service startup, restart the service (through dotfred TaskMgr) if you want it to reload the registry settings
///
1.0.3.x: <HTC>Remember to CLICK OFF your auto-backlight setting.<HTC>
Uses HKCU\SOFTWARE\Creative 'Ware\LevelSight\offset to adjust the native backlight setting. It defaults to -1 so it'll pick a setting 1 less than what the system would've automatically set. If you set it to 0, it'll pick the same as auto, and so on. Behavior is the same as pre-1.0.3.x when backlevels fall below low_wm, but switches to offset mode when levels rise above high_wm.
More gui ability to adjust these settings is coming.
/// pre-1.0.3.x
<HTC>All this does is TURNS OFF the auto-backlight whenever reported light levels drop below low_wm using a custom 1st order low-pass algorithm. When turned off, the backlight falls back to whatever you have your AC/BATT light levels set to in your control panel. This solves the issue of the auto-backlight not dimming below backlight level 3.
When light levels rise above what the light sensor API thinks should be backlight level high_wm, it uses the auto-backlight settings again, and lets it auto-adjust as was usual.<HTC>
///
It is however not perfect due to the low accuracy of the sensor at low light levels, but does try to ignore the random unexplainable surges in the sensor readings when light levels are constant. It's probably a reason why ODMs don't bother to try to make auto-backlight work any lower.
Thanks originally to Koush for his LightSensor SDK reference as well as Scott Seligman for the C++ reference.
Advantages:
works with native OEM backlight without extra .NET layer
history-less sensor-data filtering
Native C++ and assembly, floating-point-less DSP/SIMD-accelerated math, and extra optimization analysis in Ida Pro.
No CPU/power-sucking .NET, nor the standard/default software floating-point emulation used.
takes 1K of ram, 22K of storage
0 process slots (runs as a service)
no notable power-draw (same amount of power ~53mA with service on/off on Fuze)
polls every ~2000 milliseconds
no HTCSensorSDK sensor-data lag (~200-300 ms) nor cpu load -- directly accesses the sensor driver
dll and supporting code are compressed independently of .cab and use cpu's smaller Thumb (16-bit) code when advantageous
mostly lockless multi-threading
HKCU/Software/Creative 'Ware/LevelSight:
offset: adjusts backlight levels positive or negative of oem-pick
low_wm: fuzzy point where it low-light auto-backlight (2 is default recommendation)
high_wm: fuzzy point where offset auto-backlight will turn on (5 is recommendation)
Tested with stock Fuze rom, and Acer m900 160-lite rom.
Release Notes:
-current(1.1.0.x series)
1.1.0.2: fix bug where max backlight was clamped to level 5. It now uses the full 1-10 (10 levels) range. Level 0 disabled because not useful.
1.1.0.1 2009.09.04: full-backlight enhancement for Acer m900 ONLY!! Backport to FUZE whenever.
Acer 900s version abandoned because of Clove Technology.
-stable(1.0.3.x series)
1.0.3.2 2008.02.19: full-backlight replacement
-obsolete(1.0.2.x series)
1.0.2.1 2008.12.03: reset hysteresis on backlight power-state edge
1.0.2.0 2008.12.03: hysteresis now using first-order low-pass filter with a medium α; math and power-state optimizations
obsolete (1.0.1.x series) LevelSightSvc.1.0.1.1.CAB (11.8 KB, 132 views)
1.0.1.1 2008.11.24: work-around for service not starting up when device is rebooted; tweaked hysteresis
1.0.1.0 2008.11.21: converted into a service with registry configurable water marks
1.0.0.3: better hysterisis
1.0.0.2 2008/11/16: Previous version tended to like it dark and resisted turning it up.
Adjusted dark/light sensitivity so it switches auto-off at light sensor 3::3, and switches it back on at 3::5. Still playing with this to get a better hysteresis.

Thank you Sir! That's exactly the kind of app I was waiting for. From what it sounds like I much prefer your solution over G-Light! I will test it right away!

NuShrike, the app doesn't seem to work for me. I've installed it and did a soft reset afterwards (just to make sure) but the backlight still never falls below level 3. In my AC/Batt settings I have the backlight auto configuration enabled and did also try to disable this with the same result.
Am I making some mistake?
I'm really looking forward to get this sorted out because I love the idea of your app!

same here! tried it with duttys rom

Same issue with stock fuze rom. Definitely looking forward to this app.

I just analyzed the running processes after soft reset and the app is not running even tough it is placed in startup. so I just tryed starting the process manually but even when it's running it is not working

Great idea, but does not work consistently. I've tried to narrow it down to a repeatable scenario, but have not been successful. I can see the LevelSight.exe process running (BTW, it takes approx 2.4% of my cpu every three seconds, then idle for three seconds.) LevelSight initially appears to work as designed, but after a few light cycles, it stops enabling the auto adjust setting.

Just did some more testing. If I go in and manually enable auto adjust (in Power settings) it will work as long as the light level is high. Then when light level is low, LevelSight will disable auto adjust (setting backlight level to what I have it set to) but never reenable auto adjust (no matter how bright the ambient light.) So it seems to half way work, it does consistently disable auto adjust but it never enables it.

More testing. Seems that if I let the phone dim the backlight all the way to dark setting (30 seconds) and hit it with bright light before it goes to sleep, LevelSight will enable the auto setting and the light will come up. This might cause a problem with the auto dim. Hmm, still playing.

Okay, I've tried playing with the turn-on trigger a bit to see if that helps. It was programmed in the dark with a flash-light and now just tested in the sun today.
Version 1.0.0.2 is a little better at turning auto-back on, but may be still be not quite "right" in my experience.
Here's an interm version to get it more usable while I try to find the better "fuzzy" logic for the trigger.
TheMostToys: How are you measuring CPU usage? I'm using TaskManager and it's showing cpu in the range I described.
DeepThought: do you have HTCSensorSDK.dll in your \Windows? I assume a Raphael rom is built mostly the same as a Fuze's so I'm not sure why else it's not running for you. It will refuse to run more than one at a time also, and soft-reset may clear up the self-lock if that's the problem. If not, I'll post up a debug app to see what's going on.
My Fuze did get all app security turned off so I may not be properly triggering the needed security dialogs.

NuShrike said:
TheMostToys: How are you measuring CPU usage? I'm using TaskManager and it's showing cpu in the range I described.
Click to expand...
Click to collapse
I'm using Memmaid. Also tried SKTools with similar results.
BTW, I'm not overly concerned with the current CPU usage, just noticed a difference and thought I'd let you know, in case it helped narrow down the problem.

Much better hysteresis with 3-point history.
Resists going dim, but will still do so in ~9 seconds if ambient stays dark.

Does not work
Hi, NuShrike, nice app, but does not work for me.
The problem is that in the full darkness the signal level from light sensor on my TP is falling under 7, but then slightly increasing till 7.26 (according to G-Light measurement) and stay constantly at 7.26 forever!
Since screen is dimmed and then lighting up to the level 3 again!
Is it possible to change the bound from 7 to 8 or make an ability to adjust it personally through some config file or command line parameter?
I suppose it might be useful to the people who have very little sensor signal in the darkness, too.

Vladimyr said:
Hi, NuShrike, nice app, but does not work for me.
The problem is that in the full darkness the signal level from light sensor on my TP is falling under 7, but then slightly increasing till 7.26 (according to G-Light measurement) and stay constantly at 7.26 forever!
Since screen is dimmed and then lighting up to the level 3 again!
Is it possible to change the bound from 7 to 8 or make an ability to adjust it personally through some config file or command line parameter?
I suppose it might be useful to the people who have very little sensor signal in the darkness, too.
Click to expand...
Click to collapse
I think your 7.26 is the calculated lumen value that G-Light may be using out of the .net SDK.
I'm not using that SDK, but basing off the raw values coming from the light sensor almost directly. I can add build some registry entries to allow some tweaking because maybe each TP reads differently.
So holding your thumb over the light-sensor and the backlight still goes back up to 3?

NuShrike said:
So holding your thumb over the light-sensor and the backlight still goes back up to 3?
Click to expand...
Click to collapse
Yes, right. Right now after my thumb covered light sensor it is dimming to 1, then after a few seconds it's back again on 3!
G-Light is deactivated this time, but when I start it showing 4.52 immediately after covering sensor, and 7.26 a few seconds later.
NuShrike said:
I can add build some registry entries to allow some tweaking...
Click to expand...
Click to collapse
Yep!!! Please! Do it!

download it and will try .

Okay, I've verified that LevelSight stops running after a full-night's sleep. I'll see if the conversion to a service will keep it running.

Vladimyr said:
Right now after my thumb covered light sensor it is dimming to 1, then after a few seconds it's back again on 3!
Click to expand...
Click to collapse
Exactly the same for me.
NuShrike said:
Okay, I've verified that LevelSight stops running after a full-night's sleep. I'll see if the conversion to a service will keep it running.
Click to expand...
Click to collapse
I look forward to the next version, thank you for your efforts!

Now converted into a Service and runs under service.exe.
Registry configuration for fuzzy low and high water marks for turning auto-backlight on/off in
HKCU/Software/Creative 'Ware/LevelSight:
low_wm: ambient level where auto-backlight turns off
high_wm: ambient level that triggers auto-backlight on
Also, light sensor I2C device driver is now directly accessed so HTCSensorSDK is no longer used nor required removing a battery/cpu sucking layer.

The problem did not exist in fact
It seems i understood the reason of program "malfunction".
It was caused that i did not read decription carefully:
NuShrike said:
When turned off, the backlight falls back to whatever you have your AC/BATT light levels set to in your control panel.
Click to expand...
Click to collapse
But i had default backlight level set on 4! Thus, when ambient illumination was dropping under level 3, auto-backligh was turned off and backlight was increased to 4
Not i set default level to 2 and all is working well!

Auto Disable LockScreen with trusted Wifi

Can somebody please inform me how to use Tasker on my Galaxy S8 so the pincode lockscreen will be automatic disabled when I'm connected to a trusted wifi and will be abled when I'm not connected to this trusted wifi.

you could check AutoTools
http://forum.joaoapps.com/index.php...-enable-your-lock-screen-at-will-no-root.237/

Thanks, but in your example Lockscreen disabled is set in time (7200 sec). I want Lockscreen disabled as long as I am connected with a "trusted wifi", this can be 10 sec, 2 hours or even 3 days.

Lockscreen is a challenge on the newer Android releases. I handle it the same way that Auto tools does by changing the lock screen timeout to a ridiculous value (10 days). Then on the exit task, I return the value to a more sane number. The worst case is one every 10 days I have to enter my screen lock code. Though I have to do that every day anyway since I reboot my phone over night. I describe my approach in this post.

Display Dimming / Timeout

Anyone know of a way (perhaps via Tasker) to prevent the phone's display from dimming after several seconds when connected to a vehicle's USB port? Thanks in advance!

second this.. i already detect that the phone is connected to the bluetooth in the car and used tasker to set the screen timeout to 30 minutes. but when AA finally starts, it overrides my tasker change and sets the timeout to 15 seconds. i tried using the "Docked" event detection to detect that the phone was placed in "docked car" state. but, the AA application needs to get this event to start, so tasker never gets it. i'm looking into having tasker be the default app that gets the docked car event and then have tasker launch AA... we'll see if that works.
but it would be great if someone else has already figured this out and can post...
schleprock