Automatically lock whenever the N810 light sensor is covered - Page 5 - maemo.org

Active Topics

Porting apps to Leste (32)
to Maemo 7 / Leste by Arno_11 - 4 days, 20 hrs ago
[ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900 (2,264)
to Maemo 5 / Fremantle by panjgoori - 6 days, 14 hrs ago
more...

Page 5 of 8

Thread Tools

	qwerty12	2008-05-24 , 08:16
	Posts: 4,274 \| Thanked: 5,358 times \| Joined on Sep 2007 @ Looking at y'all and sighing	#41

Reminds me a bit of my W810 turning off the keypad light in bright sunlight (not great for me anymore as I patched it to stay off in dark light anyway

)

Quote & Reply |

	maillaxa	2008-05-24 , 12:45
	Posts: 149 \| Thanked: 13 times \| Joined on May 2008	#42

Great app. Thank you.

Quote & Reply |

	PinCushionQueen	2008-05-24 , 14:27
	Posts: 538 \| Thanked: 168 times \| Joined on Dec 2007 @ Seattle	#43

Originally Posted by twaelti

I thought about a derivative software of this application:
Once the sensor "senses" bright sunlight, the app could completely reduce the backlight of the N810. This would help conserve energy that would otherwise be wasted (in bright sunlight, the backlight is irrelevant).
Would that make sense or be practical?

Yes that makes sense and would be very practical

When I'm reading on the bus and it's sunny outside, I usually cover the light sensor with my thumb to dim the screen and save power. The sunlight and the N810's transreflective screen provide all the light I need. Never understood why the screen got brighter in bright sunlight.

As an aside I've had to remove this app due to a memory leak. With this autolock removed the memory leak is gone. I've switched to using the Keyboard Autolock instead. It works without leaking.

__________________
When you wish upon a star, your dreams really can come true... Unless it's an asteroid hurtling towards earth that will destroy all life.

Quote & Reply |

sparkling	2008-05-25 , 22:13
Posts: 95 \| Thanked: 27 times \| Joined on Oct 2007 @ Miami & London	#44

Originally Posted by PinCushionQueen

... switched to using the Keyboard Autolock...

Is this a built-in feature, or another application? I know I can unlock the screen by opening the keyboard, but closing the keyboard does not relock except in the special case where i have not touched the display.

Quote & Reply |

	PinCushionQueen	2008-05-26 , 12:59
	Posts: 538 \| Thanked: 168 times \| Joined on Dec 2007 @ Seattle	#45

Originally Posted by sparkling

Is this a built-in feature, or another application? I know I can unlock the screen by opening the keyboard, but closing the keyboard does not relock except in the special case where i have not touched the display.

It's a separate app called Slidelock It just adds the ability to lock the N810 by closing the keyboard and you just use the existing unlock by opening keyboard. If you want the keyboard shut and yet have the tablet unlocked you can still use the little slidy switch on top.

I've been using Slidelock for about a month now and have had no problems.

__________________
When you wish upon a star, your dreams really can come true... Unless it's an asteroid hurtling towards earth that will destroy all life.

Quote & Reply |

The Following 3 Users Say Thank You to PinCushionQueen For This Useful Post:
Borgel, Faz, sparkling

Dusty	2008-06-28 , 23:22
Posts: 16 \| Thanked: 25 times \| Joined on Dec 2005	#46

I've released a new version of autolock (0.3). It now works with Diablo. It also displays the enable/disable notifications longer, and should be harder to accidently disable. I have no clue what is causing memory leaks for some people - It doesn't seem to happen on my tablet. I would appreciate if someone with more experience with DBUS could look at my code to see if they can spot a leak. Anyways, it is Works on My Machine certified

Quote & Reply |

The Following User Says Thank You to Dusty For This Useful Post:
Faz

Dusty	2008-06-29 , 14:36
Posts: 16 \| Thanked: 25 times \| Joined on Dec 2005	#47

If anyone downloaded Autolock 0.3 before now, please re-download it; I accidently uploaded an old version last night. The new version is now uploaded. To check your version, run /usr/sbin/autolock -v. (Previous versions will ignore the -v option, so press Ctrl-C to stop it.)

Quote & Reply |

The Following 3 Users Say Thank You to Dusty For This Useful Post:
brontide, Faz, phutterman

	brontide	2008-07-01 , 17:27
	Posts: 868 \| Thanked: 474 times \| Joined on Oct 2007 @ Capital District, NY, USA	#48

Diablo install. Worked until I rebooted it. Also... was there supposed to be a control panel item to control the timeout?

I see it's supposed to start in /etc/rc2.d/ and restarting it manually /etc/init.d/autolock start seems to have fixed the problem.

Last edited by brontide; 2008-07-01 at 18:12.

Quote & Reply |

Dusty	2008-07-01 , 19:29
Posts: 16 \| Thanked: 25 times \| Joined on Dec 2005	#49

Thanks - I will fix this shortly.

Meanwhile, run as root:

Code:

update-rc.d -f autolock remove
update-rc.d autolock defaults 99

That should fix it.

I have no interest in adding a timeout (more complexity, little or no benefit). When I am somewhere that is so dark that I keep accidentally triggering Autolock, I either slide the keyboard out (which temporarily disables it) or disable it with the lock slider.