I noticed today even if i keep phone flipped upside down the sensor its still closed . Only if i cover the whole display with hands i can make the sensor opens , this is a real problem . Only indoor the sensor works fine . Now it's not a lagging problem , it's sensivity at light .

this is the list of packages


Nokia-N900:~# maemo-list-user-packages
1up 1.1.0-2 user/utilities 148
accelemymote-gui 0.1.1 user/system 96
account-plugin-haze 0.10 user/network 132
advanced-power 0.4.2-4 user/desktop 188
advanced-power-monitor 0.5.3-3 user/utilities 216
aircrack-ng 1.0-3 user/network 1048
apmefo 0.11-1 user/system 200
ati85 1.4.1-1 user/science 2059
batterygraph 0.3.2 user/utilities 356
blessn900 0.43-1 user/graphics 1740
bootscreen 0.3.4 user/system 216
bounce 1.0.1 user/hidden 22036
chledclk 0.0.2-1 user/system 56
conky-n900 1.9.6-1.2 user/desktop 920
cpumem-applet 0.0.3 user/utilities 64
cutetube 0.9.10-4 user/multimedia 2132
d-theme-aero-blue 1.2-2 user/desktop 10168
dtg-installer 1.0-4.2+0m5 user/other 92
extmou 1.0.6 user/system 96
facebook-installer 1.0-4.1.1+0m5 user/other 88
fapman 0.7.1-1 user/system 864
flashlight-applet 0.4-5 user/desktop 284
fm-boost 0.2-2fremantle1 user/system 120
gonvert 1.1.4-0 user/science 468
healthcheck 2.9.10 user/utilities 696
irwi 0.2-9 user/desktop 360
jspeed 0.1-9 user/navigation 1040
kernel-power-flasher 2.6.28-maemo46 user/system 240
kernel-power-settings 0.11 user/system 140
keyboard-leds 0.1-2 user/system 148
kmplayer 0.10.5.901-1 user/multimedia 828
led-pattern-editor 0.0.5-1 user/system 228
lfocus 0.914-1 user/graphics 616
libqtm-bearer 1:1.0.2-maemo4+0m5 user/libs 300
libqtm-contacts 1:1.0.2-maemo4+0m5 user/libs 1012
libqtm-location 1:1.0.2-maemo4+0m5 user/libs 256
libqtm-messaging 1:1.0.2-maemo4+0m5 user/libs 848
libqtm-multimedia 1:1.0.2-maemo4+0m5 user/libs 1544
libqtm-publishsubscribe 1:1.0.2-maemo4+0m5 user/libs 244
libqtm-sensors 1:1.0.2-maemo4+0m5 user/libs 336
libqtm-serviceframework 1:1.0.2-maemo4+0m5 user/libs 392
libqtm-systeminfo 1:1.0.2-maemo4+0m5 user/libs 420
libqtm-versit 1:1.0.2-maemo4+0m5 user/libs 468
liqflow 0.1.9 user/multimedia 1156
mbarcode 1.0.0-3 user/utilities 520
mbarcode-plugin-qrcode 0.0.7-1 user/utilities 164
mbarcode-plugin-webrequest 0.1.15-7 user/utilities 156
mbarcode-plugin-wifi 0.1.0-9 user/utilities 76
mbarcode-plugins-all 0.0.2-1 user/utilities 36
mobile-maps 8.1.2 user/hidden 142597
mobilehotspot 0.3.5 user/network 204
mp-fremantle-generic-pr 20.2010.36-2 user/system
mplayer 1.0svn20091221-4 user/multimedia 18612
mycontacts 0.9.27 user/desktop 1136
mypaint 0.8.2-2maemo0 user/graphics 10476
n900-fmrx-enabler 1.5-4+0m5 user/libs 92
openssh 1:5.1p1-6.maemo5 user/network 8
openssh-client 1:5.1p1-6.maemo5 user/network 1192
openssh-server 1:5.1p1-6.maemo5 user/network 456
osso-applet-screencalibration-fix 1.12-6 user/system88
pidgin 2.7.7-0nix2 user/network 4392
pidgin-maemo-docklet 0.0.3-1 user/network 96
proximityclock 0.3 user/desktop 148
proximityd 0.2.2 user/system 88
purple-extra-protocols 2.7.7-0nix2 user/network 180
qcpufreq 0.4.3-1 user/system 324
qtirreco 0.3.1-1 user/utilities 1820
rdesktop 1.7-maemo3 user/misc 1820
rdesktop-cli 1.6.3-maemo3 user/tools 536
rootsh 1.8 user/system 32
shortcutd 0.1.4-1 user/system 240
someplayer 1.5.3-3 user/multimedia 1972
stellarium-mobile 1.0.3 user/hidden 21908
symfonie 0.2.5-6 user/multimedia 420
tar-gnu 1.22-2maemo5 user/system 2360
tracker-cfg 0.3.2-1 user/system 136
tutorial-home-applet 0.6.16+0m5 user/support 1292
vncviewer 0.6.6-fremantle8 user/network 252
vumeter 0.11.2 user/multimedia 192
wgames 0.6.8 user/games 7092
wifieye 1.0-3

I tried a reflash , still same problem .

Please tell me if I got you right. If the script responded "open" when you cover the sensor, that means you should see the phone app's screen unlocked as nothing is blocking the sensor. Isn't the test told you exactly the opposite of what you observed with your phone apps?

Also, if you've reflashed your N900 to the stock kernel and update nothing thereafter and still got the same problem, that means the problem is not related to recent update right? Then you'd like to look at the hardware problem.

P.S. you don't need to cover the whole display area to test the proximity sensor. This video can show you the exact location of the sensor: http://www.youtube.com/watch?v=QXgqp...layer_embedded

Totally understand and agree to the pain! It's a real pathetic implementation of that proximity sensor in the phone application!

Can anyone please help us disabling that stupid proximity sensor while actually on a phone call. Generally/personally, my phone calls don't last more than a few minutes (at max). So, even if the screen is continuously ON during that time, I won't have an issue. But to wait for the screen to appear back when I move the phone away from the ear is an extremely painful thing.

<bit away from the topic>
"Phone" app is the WORST app ever written on N900. Same holds true for the "Application Manager" too.

Those guys/teams should be fired immediately without notice actually!

There is also this issue with the placement of multi-app-menu-icon (left-hand top corner). The time I finish the call and when I see the phone screen, some random apps would have been opened!

I hope the MeeGo DE would take into considerations these usability issues seriously.

@9000 - I watched that video before . It seems it's a hardware bug and can't be fixed . What I have to do now ? this bothers me a lot because I can't use properly the main function of this device (phone) .

I actually like the proximity sensor, it keeps me from hanging up or starting all sorts of stray apps with my cheek. However, yes it is way too sensitive to ambient light and has lead to many games of peek-a-boo with the phone blinking in and out while I try to stab the Accept or End buttons.

What I have resorted to doing is when I want to answer or hang up the phone I slide the keyboard open. This disables the proximity sensor and leaves the screen active. Then when I bring the phone up to talk I slide the keyboard closed again to reactivate the sensor. Because there is another delay as the orientation changes I leave the phone locked in landscape mode; it's easy enough to operate sideways that this doesn't bother me that much. Still, this is a Micky mouse way to have to deal with badly designed hardware.

Isn't it where you can control it by settings ---> display ---> power saving mode ?

The problem is actually more complicated then it seems, because people would immediately assume that the phone app responds directly to the proximity sensor, actually it is also affected by accelerometer and something else. Therefore other non-proximity related apps would greatly affect the response of the phone app. Most of these issues have been discussed before and solved or worked around.

The script I gave you is to isolate the problem. You're patient enough to perform the test yourself and confirmed that this is a hardware problem. Hardware defect is actually rarely seen, as most people like the post above probably having software issues.

The sensors could be damaged by human mishandling. They could be damaged by slight misplaced or exposing to strong magnetic field (say by the magnets in the pouch).

afaik, no.

@9000 - I've done your test in x-terminal outdoor and indoor , and yes , sensor was closed while outdoor . Phone didn't suffer physical damage and I don't use a pouch .