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!
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.
Hi guys, im the developer of Kilsswitch, an app that turn off the screen of your device when the case is closed.
You can find the apps thread here:
http://forum.xda-developers.com/showthread.php?t=988126
Ive been meaning to get some feedback from people using the more obscure devices, so if anyone has the app or participated in the beta a few weeks back, id like to hear about the results!
This is fantastic. I didnt even know I was looking for this. It works exactly as its supposed to. Im using Vegan 5.1.1 and a SwissGear slip case from Walmart.
And as a bonus the Adam's light sensor is perfectly placed to be used a power "button" of sorts. GReat work!
Great! What sensors are you using?
Also, i will release a new version by weeks end which integrates a new function - you will be able to run Killswitch using a day/ night schedule. I know this doesnt sound important, but it is.
ATM Killswitch is a hack - i built it for myself knowing full well that low quality sensors on many devices will have problems registering events in high-sensitivity environments (at night, for example, when ambient light levels can be low in peoples homes) .
My galaxy tab is an engineering sample with an excellent light sensor which works perfectly even when light levels are low, but many consumer products have really weak sensors that cant differentiate between low light levels.
For this reason i always recommend an activation delay of 6+ seconds to ensure redundancy.
With the schedule feature, Killswitch will allow people with weak sensors to disable some functionality at times when they know their sensors are not up to psr.
Any way to provide apk? Market is always flaky on mine.
I'm using the ambient light sensor at 1% sensitivity. I don't think the Adam has a proximity sensor. I don't have a use for the accelerometer sensor as I don't place my device facedown but can confirm that it works, and well I might add.
Full disclosure, I pirated your app to test, but will be buying it tomorrow on payday, for my device and the 3 others that I manage in my family. Thanks for the hard work, this is extremely useful.
Edit: Bought 2 copies so far. 1 for myself and 1 for the wife.
Ah, so a pay for app, I checked and also no demo. I'll try it once there is one, thanks for the effort.
15 minutes is more than enough to try it out - just put your finger over the light sensor!
Ive been considering a demo, but it would have to be seriously restricted or time-limited... hardly a demo.
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
Hi All,
My proximity sensor isn't triggering during calls (Possilbly at all?) causing me to accidentally put people on hold.
(very annoying! at least make a tone so I know I hit the button)
Is there a switch for that?
What's weird is that I don't see a HW test for the proximity sensor in the diagnostics screen (tapping on kernel version)
Edit -> settings -> system apps -> phone -> incoming call settings -> proximity sensor is ON.
Can someone whose proximity sensor is working download a sensors test app like https://play.google.com/store/apps/details?id=com.wered.sensorsmultitool&hl=en
and tell me if that detects your proximity sensor distance correctly? (or whatever app you want, just tell me which one).
- Frank
Go to Settings - About phone and tap 5 times on Kernel tab. You will get into test menu. There you can to test and calibrate proximity sensor.
sergmarin said:
Go to Settings - About phone and tap 5 times on Kernel tab. You will get into test menu. There you can to test and calibrate proximity sensor.
Click to expand...
Click to collapse
I don't see it. What is the test called?
What Rom are you running? I'm on 8.0.10.0
See pictures below. Test menu works on any firmware.
sergmarin said:
See pictures below. Test menu works on any firmware.
Click to expand...
Click to collapse
Well,that's damned odd.
My proximity sensor item is missing.
https://drive.google.com/open?id=0B6qmkujf4DlWVVFWVXBxTkJoRTA
xx
ChodTheWacko said:
Well,that's damned odd.
My proximity sensor item is missing.
https://drive.google.com/open?id=0B6qmkujf4DlWVVFWVXBxTkJoRTA
Click to expand...
Click to collapse
Just looked at mine and I have prox sensor as number 9. Sounds like you may need to flash an updated build.
I updated to developer rom and proximity appeared and was working.
I then re-updated to stable rom (8.0.12.0 i.e latest) and it dissapeared again!
ChodTheWacko said:
I updated to developer rom and proximity appeared and was working.
I then re-updated to stable rom (8.0.12.0 i.e latest) and it dissapeared again!
Click to expand...
Click to collapse
You already have the answer you're looking for. Guess the sensor is broken in the stable build. In this case, you may have to wait for the next stable release or use an alternate ROM.
ChodTheWacko said:
I updated to developer rom and proximity appeared and was working.
I then re-updated to stable rom (8.0.12.0 i.e latest) and it dissapeared again!
Click to expand...
Click to collapse
Confirm proximity sensor missing in 8.0.12.0
Unfortunately, it is also missing in 8.2.1.0 stable
On Chinese 8.2.3.0 and the settings are missing from the CIT list also ... with that said I don't depend on it anyways lol. Just checking things.
for some thick case the proximity sensors might have problem... need to reboot phone with case on to "register" the case thickness...
hi mi mix fans , I came through lot of applications,proximity sensor tests, procedures, secret codes etc . to get solution for "screen off during call and not on automatically" but i found the real solution in this is .. remove back cover which almost users use . , tpu transparent also and see whether it work during call ..yes,finally got solution. check yourself all test works properly and screen on during call when device is away from ear..if not ?? pls consider to clean sensor ..
Wanted to test it. I can see the test, but not sure how to test it. I still don't.
So I tried to the front microphone test to learn how to use these tests...
But it scared the s**! out of me. It's such a haunting noise! Is that normal?!
I'm on global stable, CIT proximity option doesn't show too. I think my sensor is bugged by my cover since when the device isn't covered the sensor works fine.
jaekry said:
Wanted to test it. I can see the test, but not sure how to test it. I still don't.
So I tried to the front microphone test to learn how to use these tests...
But it scared the s**! out of me. It's such a haunting noise! Is that normal?!
Click to expand...
Click to collapse
Yes, such an annoying noise.
i have same problem i just updated phone after proximity sensor not work why xiaomi not try before update this f*cking fw.
What I observed is after resetting when I tested it I came to know that sensors sensi
What I observed is after resetting when I tested it I came to know that sensors sensitivity distance increase up to an inch but starts dropping again as I move object in front of sensor 8 to 10 times and is reduce to 1 cm finally which is very less if you hold mobile in left hand ear but it works on right hand ear as proximity sensor is placed left of mobiles front side.I think it is a software problem which xiaomi should look in to.Sensor keeps on calibrating till it reduces distance to 1cm from nearly 1 inch that is 3 cms.This is very shameful for xiaomi that after so many years of experience they have not yet resolved this for Mi A1.
My proximity sensor also isn't working. I've tried to do this test we find on kernel tab, but I couldn't test it, it shows no options for me to calibrate or sth. Help me please!!
Same issue here. Phone just turns black, when I am calling people - difficulties to restart the display afterwards. Using Lineageos 16 - no chance to tab the kernel there. Dialing * # * # 64663 # * # * shows no results. Wandering, if this is a hardware or a software issue.
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