Related
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!
Hi all,
troubleshooting for a girl with a Bionic; replaced cracked glass/digitizer for her and updated to JB via the OTA update, but her proximity sensor is flaking out.
I've installed a few Prox. Sensor reporting apps to see what values it's putting out: it reads 3cm most of the time, and 100cm when swiping down the notification bar. (100cm is max range, which I assume is a placeholder for a no-report state in the phone, not sure what it has to do with the notification bar.)
Problematic behaviour is that the screen turns off almost instantly after placing a call, and won't come back on except by swiping down (on the blank screen) to pull down the notifications, which temporarily disables the sensor. (it lasts long enough to get ~1 keypress on the keypad, which is *not* a usable workaround even for checking voicemail.)
I'll take the phone apart again and make sure there's nothing in the way of the prox. sensor, as that seems the most likely cause... but any guesses or similar reports from anyone about possible bugs in the firmware update? Any proximity sensor calibration apps for this hardware I'm not seeing in the marketplace, or ROMs that expose that functionality? (I wasn't planning to root the phone, but she won't know the difference if I need to. Was hoping to avoid safestrap to simplify the boot procedure and not interfere with future OTA updates, but warranty is gone already so it's not a big deal if I need to install something new.)
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
so in short this problem has plagued the phone since day one and i suspected a HW issue since nothing fixed it. for those who dont know whats im talking about, you are lucky. the issue is basically that the proximity sensor is missed up so the screen will light up when you are in a call or listening to Whatsapp/Telegram voice messages.
The Solution:
The problem, turned out, was caused by the factory screen protector that came already applied to the phone. i removed it after it was damaged and also removed the case (Spigen Rugged Armor Case), cleaned the phone and VIOLA its working perfectly fine now...
i hope it works for everyone else.
So, what you are saying is:
Since when this phone got launched in May 2019, not a single user facing the proximity sensor issue had the ingenious idea to remove their factory applied screen protector and you are the first one to come up with this "fix"?
I am really sorry to be this discouraging but: This ain't it chief.
Good that it fixed your perception of the issue though
Comrade, the issue is far graver than that. OnePlus 7Pro does not have a proximity sensor per se. It uses software (an ai I think) to "guess" whether to turn on the screen or not which is why listening to voice notes gets crazy...
amirage said:
Comrade, the issue is far graver than that. OnePlus 7Pro does not have a proximity sensor per se. It uses software (an ai I think) to "guess" whether to turn on the screen or not which is why listening to voice notes gets crazy...
Click to expand...
Click to collapse
Even though it does have an infrared sensor under the screen (that has been proven), i agree with you that it seems to be using something like that.. Curiously, the proximity sensor once fired when i flicked off my lights in my room.. This indeed leads me to believe there is more going on than just a simple infrared proximity sensor..
But yeah, i don't think removing the stock screen protector "fixes" the thing.. It may improve things but i doubt it's a fix.. As i said, this phone has been out for a while and people would have noticed if removing the screen protector fixes the proximity sensor for good..So yeah, cheers mate.
I took the screen protector off before I turned the phone on for the first time. I still get the screen lighting up while I'm on a call, often muting it with my cheek.
I must be lucky but at the moment I have no such issue with my new OP7P (MFD: 2019/05). RR Rom. Still have the screen protector on it. What's the MFD of your unit ?
i have problem with my oneplus since i rooted this phone
after root i have installed pixel expereince rom
when i called i found proximity sensor not working
now almost 6 months no fixed i'm stock oos
please help me there is no guard on my phone also no cover
The simplest solution for me has been to use a Bluetooth headset. I rarely use it without it.