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!
I'm increasingly convinced that the compass may be at least partly to blame for poor gps tracking. I'd like to experiment with disabling and/or tweaking the compass but don’t know where to start fiddling with compass settings.
Suggestions?
Sent from my GT-I9000 using XDA App
There has been some work on what causes the gps problems with captivate, notably by developers CLShortFuse and Da_G. Some of the discussions are quite technical. I don't recall the compass being implicated, however. If you are interested in pursuing gps info, search out threads by the above two developers. For starters, try this one.
I know this is an old thread, but I think there is something to it...
@creepyncrawly: I came to the same conclusion last night. The Captivate gets brilliant SNo while sitting on my desk. If I turn it while still on the desk, I lose all satellite locks. I think that is what introduces the error.
Open up GPS Test and watch the compass output. It's all over the place, while for me at least, the lat/long stay pretty steady. For example, completely still it wobbles, a lot. When I rotate the phone, the bearing wildly fluctuates. Turning it 180 degrees doesn't give a 180 degree shift in bearing either.
I think the phone is being mislead into thinking its moving by either the accelerometers or the compass. I think my next test will be a good strong magnet in close proximity while the phone is stationary.
I tried killing the compass daemon, but it comes back. I've tried removing it from the init script, but it must be a protected file. Next trick will be to just delete the binary I think.
My second idea is decreasing the port speed of the GPS module, not sure that would do anything constructive though.
I've only now discovered that the issues I've been having with certain apps are because the One has no magnetic compass sensor, only a digital compass. Is there any way to enhance the compass accuracy or otherwise calibrate it?
I ask, because when playing Ingress, my orientation is never even close to correct. I have to manually adjust the screen (while driving, ACK!??!) if I want to follow along with the route I'm driving, and of course the arrow is never pointed in the right direction which can make deploying resonators a little more confusing.
I'm also starting to get into geocaching, and without a working compass app, I have to carry another phone or an actual compass along with me. So spur of the moment geocaching can only happen if I happen to have one at the time.
And of course I'm sure everyone's heard about Sky Maps not working properly either, which is just a bummer.
Bumperoonie, Surely someone out there has similar problems or the knowledge to tackle this... anybody?
I think this happened at around the time that I installed the latest update. I checked the sensors through the *#0*# menu and found that my gyroscope's value isn't moving and my magnetic sensor is spinning. I calibrated the magnetic sensor using Google Maps and also the Edge screen, but still it happens. I tried playing a racing game which relies on my gyroscope to steer and to my surprise, it works fine. I also tried to test my magnetic senor by downloading a compass app, and it properly displays my current bearing. I'm also not entirely sure but my accelerometer data aren't properly telling that it's on a flat surface although it actually is.
Is anyone also having this issue?
I did just remember that when I downloaded the update, I had an intermittent connection, would a part of the update be corrupted so that the drivers for the gyro and compass be mismatched?
I also have a youtube video showing what my screen displays when I do a sensor test.