Database Develop

Is there anyway to test hardware functions?

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.

[Q] Proximity sensor

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!

[Q] Proximity sensor issue???

Wondering if someone (hopefully more than one) can check something to see if this is an issue with my particular phone or something related to the software/hardware. It seems that when a call is placed or received, the proximity sensor goes to "far" and won't reset until it is uncovered and then re-covered. I have searched through the Verizon HTC One forums and have not found anything related to this issue.
If the proximity sensor is covered, and I make a call (via bluetooth headset (double click for last dialed)) or receive a call, the proximity sensor goes to the uncovered state. It then stays in that state until I uncover and then re-cover it. How I checked this was using Elixir 2 and checking the sensor data. I also set up variables in Tasker and Automagic.
So, this was my test procedure:
I start the sensor data in Elixir 2 for the proximity sensor. I cover the sensor with my finger (it now shows "near"). I use my bluetooth headset to place a call. The screen comes on with the current call. I back out of the current screen (the phone screen) and get back to Elixir 2 sensor data. The sensor now shows "far". From that point on, until I uncover the proximity sensor and then cover it, it shows far. I set up variables in Tasker and Automagic that show the same results.
I am running the stock debloated ROM. Rooted and S-Off.
EDITED:
So, this is the latest for my issue. I went from stock ROM to ViperOne 5.8.0. I am still getting the same results. So, I think I have eliminated the software side of it. Would that be right? So, it could be the firmware or the hardware? I'm still wondering if it's my phone only or if it is an issue with the HTC One in general. Is there anyone that can check this? Or give me another route to take?
I'm on ViperOne 5.8.0
Android 4.4.2
Senses 5.5
Any other info you might need, please just ask.

Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101

alex.foto said:
Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101
Click to expand...
Click to collapse
Well, seems to be the same here. I have this posted under the Verizon HTC One > One Q&A, Help & Troubleshooting as well as here and at the Android forums. It seems that either no one else is having this issue, no on cares or no one can run this test with free programs. I dunno. The problems I have is that I use by bluetooth headset most of the time. I am a blue collar worker and try not to pull my phone out of my pocket when my hands get filthy. But, when I take or make a call using the headset, the display kicks on and then stays on because I can't use the proximity sensor to turn the screen back off. Guess I'll have to try other routes. This sucks. LOL
I haven't heard of the other issue you are referring to. I can tell you that I have not had that issue with my One. Doesn't mean that it's not a problem. Have you checked the Sounds settings for pocket mode and quiet ring on pickup? If so, I think I would try to either get with Verizon about it or maybe even HTC. It definitely sounds like it could be a phone issue. But I'm kind of new to all of this.

Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"

I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.

psicobelico said:
Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"
Click to expand...
Click to collapse
It's not a calibration issue. When the phone rings or you make a call via a headset and the proximity sensor is covered (ie. in your pocket or screen face down), the display kicks on and the prox sensor seems to default to "far" or "uncovered" (whatever term you like). It will remain at that value until you ACTUALLY uncover the sensor and then cover it back again.
alex.foto said:
I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.
Click to expand...
Click to collapse
The problem I have is that while the display is ON and sitting in my pocket, I have a chance of butt dialing someone or starting programs that drain the battery in addition to the dsplay being on. Not to mention, with the display on in my pocket, the heat builds up in the phone. I guess I have a $700 butt warmer? LOL

[Q] Galaxy S problems:(

Hello guys ...sorry if a similar question was already asked.
I have a problem with my phone. When i want to make a phone call the screen goes off. At first I thought that the phone switched itself off, but later I noticed that the credit was gone...:/ I happens even after the factory reset. It also happens with another dialer from google play...however, people can still call me and there is no problem...no problems with sms either.
I have 2.3.6 Gingerbread
Please help

I think that's normal. There's a sensor which causes this.

Lars124 said:
I think that's normal. There's a sensor which causes this.
Click to expand...
Click to collapse
so its not software problem? is it worth to replace it? how much may it cost?

i also checked another thing...its not only the screen there's no signal and a phone call is not made...:/

Every phone has this sensor. The intention is that you don't touch any button on your screen during the phone call.
You can try to reflash the stock rom.

Lars124 said:
Every phone has this sensor. The intention is that you don't touch any button on your screen during the phone call.
You can try to reflash the stock rom.
Click to expand...
Click to collapse
I reflashed it...the problam's still there...but my friend call me back i called him but i didn't here any signal and the screen went off...:/

Lars which sensor did You mean? Proximity sensor? Would that cause the phone to go silent (no dial signal)?

zombie1977 said:
Lars which sensor did You mean? Proximity sensor? Would that cause the phone to go silent (no dial signal)?
Click to expand...
Click to collapse
I run the proximity sensor test using *#*#0588#*#* and looks like it's broken...the screen is blue and displays "proximity x 1" covering the sensor has no effect, looks like the sensor is activated all the time...
I noticed some dust, maybe moisture in there so i think it will be a good idea to take the phone apart and clean the sensor...

zombie1977 said:
I run the proximity sensor test using *#*#0588#*#* and looks like it's broken...the screen is blue and displays "proximity x 1" covering the sensor has no effect, looks like the sensor is activated all the time...
I noticed some dust, maybe moisture in there so i think it will be a good idea to take the phone apart and clean the sensor...
Click to expand...
Click to collapse
I feel like a crazy person answering my own posts...
I took it apart, cleaned it, but the problem's still there. I bought a new assembly jack-speaker-proximity sensor on ebay for 7 euro...hope it will work after replacing this part...
The way it's all together explains why there was no dial signal.
When I replace the part i will let You know Thanks for Your help

No problem.
Tell me when you're done.

Lars124 said:
No problem.
Tell me when you're done.
Click to expand...
Click to collapse
Hello Replaced the part, tested, everything working beautifully Sweet I love this phone :cyclops:

Note8 Sensors error - Any of you faced with?

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