I have installed gingerbread xxjvk on my i9000,everything is ultimate,no hang problem,BUT one problem that is sensor problem.
when i play any sensor game,sensor did not work properly.
if i handle device in my hand in portrait position,it shows horizontal view.
Mean to say sensor is not working in proper manner.
please tell me what i do
Related
I remember (but not for sure) a settings page that gave you the ability to test different sensors and what-not. the reason for my question is because when i make a call the proximity sensor doesnt work, and i wanna know is it because of the rom or anything software related, or is it the sensor itself, since i recently had repair done on the screen.
thanks.
Nobody knows? i got a 30-day warrenty, so if my proximity sensor really isnt working i need to know soon.
I've used an app previously that would display raw readouts from the various sensors in the device, including the proximity and ambient light sensors. Stand by while I try to find what app that was...
In the meantime, you can at least verify that half of the sensor is working by looking at the screen through a digital camera or other phone's camera. The proximity sensors works off of a flashing IR LED that you should be able to see through a digital imaging sensor. The sensor is located to the left and below the speaker.
Also, I believe the application I was using is called "Elixir", and is free on the Market.
Thanks man, great app. everything is working ok now.
Hey guys. I have looked around and can find no info on some of the tabs sensors. From what i understand the chipset is straight out of the galaxy s phones, which is the reason i see the existence of a proximity sensor but dont see any data from it.
Anyone have a clue whether it actually exists?
chipset and sensors are different things....even if the chipset supports a certain type of sensor doesn't mean it should be there if there is no need to be there.
galaxy tab doesn't need a proxy sensor cause you are not going to put it beside your face when calling...
triplex76 said:
chipset and sensors are different things....even if the chipset supports a certain type of sensor doesn't mean it should be there if there is no need to be there.
galaxy tab doesn't need a proxy sensor cause you are not going to put it beside your face when calling...
Click to expand...
Click to collapse
Doesn't need and doesn't have are different things. Point is, if it was stated that the tab has a proximity sensor, where is it?
I'm pretty sure it has one, in the unofficial CM build Technomancer says he fakes i at 10CM
There is no proximity sensor in Galaxy Tab.
My CM7 sensors driver pretends there is one and reports 10CM distance so the Phone app behaves better.
Thanks mate, that's what you said in the last thread back in October, but why do all the sensor pingers see it? Are they checking code rather than hardware?
Also, is there a working, sensitive light meter anywhere for the tabs ambient light sensor? The couple I've tried refuse to work...
There is working light sensor in the Tab. Both my CM7 and Samsung ROMs support it just fine. It has range from 0 to 6000 Lux snapped to one of several levels in the kernel driver. You can actually read it from sys interface.
The proximity sensor in my CM7 sensors driver is just software reporting constant 10cm to the system. The sensors test apps in my CM7 (I uses Sensor Test and Plot http://www.appbrain.com/app/sensor-test-and-plot/com.golborne.android.SensorTest) just reports 10cm from my fake sensor.
I think there is some leftover code in Samsungs sensors driver that may report presence of proximity sensor.
Yep, i use it as well, but my issue is with the three avaliable states the driver seems to report.
I get 5, 22 and 75. Are there only three levels then? And no way to modify them outside the kernel?
I can get up to 6000lux using strong LED flashlight directly on the sensor.
There is another sys device that can read unprocessed data that has values not snapped to 5,22,75 etc... but Samsung's driver uses the snapped device (and so is mine).
This is very annoying... im trying to make an app that needs a proximity sensor to work as intended so the light sensor as well as the sleep mode implementation are really no substitute.
In any case, im sure it will be quite usefull for all tablet owners running 2.2 and up and using a case. I will have a closed beta for xda members by the end of the day, so people can test it over the weekend.
Would you like a shot, mancer?
I don't know what would you do but if I understand why not to use the g-sensor ... just like in samsung omnia...put backwards enable silent courtesy mode.
the proximity sensor will be useful if you use the leather case to close the screen when touches the screen , like ipad 2 and galaxy tab 10.1 V they have proximity sensors , but i noticed that the sensor exists using sensor applications they see it exists but not giving readings
Hi - there is no sensor, the sensor list showing it is just a glitch from the galaxy s motherboards. And the functionality youre describing is already available in my app Killswitch - you can get both the lite and full version from my signature...
ftgg99 said:
Hi - there is no sensor, the sensor list showing it is just a glitch from the galaxy s motherboards. And the functionality youre describing is already available in my app Killswitch - you can get both the lite and full version from my signature...
Click to expand...
Click to collapse
Thanks I already bought it from market and it's great
Sent from my GT-P1000 using XDA App
Great! Im working on an update that will help improve the accuracy of the light sensor functions... been getting some flack for not updating it
Watch this space!
Hello i found out my N1 Proximity sensor have issue wen a install 2.3.3 my screen shutoff when i do call and stuck blank screen i have to remove the battery and put the back.
i download Elixir App and doing some test and Sensor only Say "NEAR" I put my hand on the screen still say Near...
/etc/permissions
android.hardware.sensor.proximity.xml
android.hardware.sensor.light.xml
/system/lib
libssensorservice.so
Factory Code Nexus One
#*#0588#*#* Proximity sensor test (no work in my N1)
can i restart the sensor?
can i disable Proximity in DIAL ?
do i need to take tHTC Support N1?
where is the CM3602 on N1?
can i fix my self?
and I have the same problem but no answer :-(
___
http://forum.xda-developers.com/showthread.php?t=707234&highlight=nexus+proximity
Hi,
Have the same issue, too !
hmm, looks like a android 2.3 issue on that one....
The same here. Is there any way to do a downgrade to 2.2? The phone is unusable, I'll have to go back to my old Nokia!!
Also, at the same time, when I plug the earphones on the Nexus, it doesn't detect them and continues playing through internal speaker!! And I suspect that the light sensor doesn't work.
Hasta luego.
Nexus one proximity sensor problem
Hi guys i had the same problem with my phone
and I manage to fix it
I open the phone and check where the proximity sensor was
and clean it with the a spray duster they sell in computer store
I clean the entire phone
put i back together and it was fix
thanks me if it works for you like that
You are lucky,, just opened my phone and cleaned the proximity sensor and light sensor with specialized electronics solutions i borrowed from work and nothing happened,,dont know what to do about it
RE: how to disable proximity sensor
hey there, this is my second post, THIS PLACE IS AWESOME!!! I was able to disable my nexus one proximity sensor using the hex edit method (after granting the app root access) and now a brick to be is no more. thank you to the poster who made the original post and the one who mentioned the way to give hexedit root access. my sensor definition was exactly where he said it would be. the name of course was cm3602 (lowercase, looking for uppercase found nothing) I was able to change hex position 0000323d from 32 to 00 , and poof, no more black screen after dialing or when receiving a call. a temporary solution I was using was to use a bluetooth headset.
Thank you all.
Anyone seen their light sensor get 'stuck' or just badly calibrated?
Mine reports super low values unless you hold it right up to a light bulb, then it says 'dim room' or something similar lol.
'
This all started happening after I tested out killswitch application (which uses the light sensor) which I think killed it. I've uninstalled and rebooted but now my light sensor is stuck in above state.
Anyone know how to recalibrate?
Bump and even more confusingly, I'm now on overcome 2.0 rc1 and even full restock and flash to new rom didn't fix it. What the...
Sent from my GT-P1000 using Tapatalk
Its a known Issue to samsung light sensor auto brightness is screwed. They fixed it with Galaxy S2 upgrade. I wish someone would port it for our tabs
oh snap it was working OK before that app broke it, no joking.
And the broken-ness carried across a full restock and upgrade from Overcome 1.45 to Overcome 2.0 (froyo --> gingerbread). So something is very weird, I hope you're right and that its a SW problem not hardware.
Also lightsensor problem with brand new Tab 7.7
I also have a problem and nSamsung doesn't even answer to my cries for help (Samsung Belgium redirected me to Samsung the Neteherlands and they do not reply at all).
I downloaded different luxmeter apps and general sensor apps they give as measurement result 12, 120 or 1200 lux (seems they output the range or lower or upper limit of the range the sensor is on, not the actual value). The sensor datasheet says it has a resolution of 1 lux.
Any solution would be much appreciated, I intende to use the sensor as a luxmeter and write an app for it taht needs the luxvalue ! But as it is now, the tablet is completey useless for this because the OS/driver software not working properly
I have Note8. It has a very strange sensors error, as below:
- All sensors, from proximity sensor, light sensor, to GPS, iris scanner, and all the other sensors do not work at all.
- In the app like Phone INFO Samsung, CPU-Z or AIDA64, in the Sensors section, all sensors do not work.
- The Auto Brightness function does not work (due to the light sensor), the brightness of the AOD screen is also not adjustable.
- When making a phone call and move the phone close to the ear, the screen does not turn off due to proximity sensor.
- Auto Rotation function is not working (due to rotation sensor).
- Google Maps shows inaccurate location. Other apps that rely on GPS (such as the speedometer app) are completely not working.
- The iris scanner function does not work either.
It was about two weeks ago. I've Wiped the cache, restart the phone but does not make sense.
Yesterday it suddenly returned to normal, I don't know why.
But today - while I'm typing this post - all sensors suddenly do not work again.
Any idea about the error and how to fix it?
Thank you guys
Best advice I can think of is to factory reset and see if that alleviates the problem.
If you did not do anything firmware-related, or you did not drop or submeged your device, the best you can do is to make a warranty claim, pure and simple, if you have no way to make such claim, well, next time you should consider getting a device from an official source
I've read other users have had same problem. Ones I read said it was motherboard issue had to have sammy replace it.
Thank you guys
There is also built-in sensor test. Open dialer and dial *#0*#
I noticed a problem when I was playing Asphalt (racing game on me Note 8). I am unable to use the Tilt controls to move the scar.
Testing out the Sensors using *#0*# at the dialer revealed that all the SENSORS was faulty.
I reset the whole phone just now. The issue is still there with the sensor. As expected Auto rotation doesn't work.
Running the latest version 8.0.
I recently changed my motherboard (under warranty) 3 months back cos something was faulty. Seems it may be another motherboard issue.
Anyone else in this thread solved the issue?
Hey everyone I'm facing the same problem. All sensors stoped working but they were working before on 7.1.1 and i updated my device to oreo and realized all sensors stoped
Then i got another updated for about 900mb i thought maybe this update will fix them and also that update said tha after updating the user cannot downgrade to nougat but after updating the problem still exsist. Please if anyone can help i also try to flash same oreo firmware with odin but doesn't fixed the sensors