|
#1
|
|||
|
|||
|
Hello, can someone tell me how to disable the sensor on the N810. thank you.
|
|
#2
|
|||
|
|
|||
|
Which sensor are you talking about?
Do you mean the ambient light sensor? There's no "easy" way to just disable it. Although I'm sure you could by deleting a few key libraries somewhere. However, you can go into Control Panel --> Display and set the "Brightness Period" to 1440 minutes. This should keep the ambient light sensor from checking to adjust the screen brightness for 24 hours.
__________________
Promises are like babies. Fun to make, but hard to deliver. Warning: dates on calendar are closer than they appear. |
|
#3
|
||||
|
|
||||
|
AS ROOT
Edit the /etc/mce/mce.ini file The top of the file will look like this Code:
# Configuration file for MCE [Modules] # Path to modules # # Do not modify unless you're sure that you know what you're doing! ModulePath=/usr/lib/mce/modules # Modules # # List of modules to load # Note: the name should not include the "lib"-prefix Modules=homekey;battery;filter-brightness-als;inactivity;camera;alarm Code:
# Modules # # List of modules to load # Note: the name should not include the "lib"-prefix #Modules=homekey;battery;filter-brightness-als;inactivity;camera;alarm Modules=homekey;battery;inactivity;camera;alarm I'll leave the "getting root" and "edit file" as an exercise for the user. |
| The Following 7 Users Say Thank You to brontide For This Useful Post: | ||
|
#4
|
||||
|
||||
|
I think fanoush posted method, something about removing the sensor module from /etc/mce/mce.ini
or even better, look above. |
|
#5
|
||||
|
||||
|
does "OMG how do I quit VI " rings a bell ? :P
|
|
#6
|
|||
|
|||
|
Quote:
|
|
#7
|
|||
|
|
|||
|
hmmmm try changing the "Switch Screen Off" value to a higher value.
Then try changing it again. Are you running Diablo?
__________________
Promises are like babies. Fun to make, but hard to deliver. Warning: dates on calendar are closer than they appear. |
|
#8
|
|||
|
|||
|
Yeah, I am running Diablo. Tried everything. Strange that my only options are 10 and 30 seconds and 1 and 2 minutes. Won't lose sleep over it, but it's weird never the less. Did a full chinook backup restore, rather than start Diablo from scratch. Don't know if that has anything to do with it. Still, if that's the only issue I've got to worry about with an upgrade to Diablo, and so far it is, then I've got no reason to complain
|
|
#9
|
||||
|
|
||||
|
It's something that can be changed via gconf, they probably had made the tewak at some point and restored the backup. There are a number of neat tweaks that can be done including, but not limited to..
backlight timout > defaults lock timeouts > defaults networking scanning < 5 minutes I'l dig them up. |
|
#10
|
||||
|
|
||||
|
Here are the defaults from gconftool-2
Code:
~ $ gconftool-2 -R /system/osso/dsm/display display_on_with_charger = true display_brightness_level_step = 1 display_blank_timeout = 300 display_brightness = 1 display_dim_timeout = 120 max_display_brightness_levels = 5 possible_display_dim_timeouts = [10,30,60,120] possible_display_blank_timeouts = [30,60,120,300] Code:
~ $ gconftool-2 -s --type list --list-type int /system/osso/dsm/display/possible_display_dim_timeouts [10,30,60,120,600,3600,86400] ~ $ gconftool-2 -s --type list --list-type int /system/osso/dsm/display/possible_display_blank_timeouts [30,60,120,300,600,900,3600,86400] ~ $ gconftool-2 -R /system/osso/dsm/display display_on_with_charger = true display_brightness_level_step = 1 display_blank_timeout = 300 display_brightness = 1 display_dim_timeout = 120 max_display_brightness_levels = 5 possible_display_dim_timeouts = [10,30,60,120,600,3600,86400] possible_display_blank_timeouts = [30,60,120,300,600,900,3600,86400] |
| The Following 3 Users Say Thank You to brontide For This Useful Post: | ||
![]() |
|
|