Database Users

[Q] Defy Problem

Huge problem with Defy.
Had the phone for 7 months, and for the past month, every time i make or receive a call, when i try to end the call i cannot, because the screen is black and the red led is shining. Either i dial a number and the screen goes automatically black and i have to wait 2-3 minutes for it to get back or actually remove the battery, or i recieve a call and i can't end it because the screen is black whilst talking and afterwards.
I had this while running 2.2.2 CEE and CM7 which i'm running now. Any ideas?
Thanks.

I'll take a wild guess here, but since you had it in two ROMs and judging by the effects, could it be related to the proximity sensor?
Trimis de pe Defy CM9

Yes. I managed to find a videon in which some chinese guy unscrewed the right-sided bolt a little and it fixed his issue. It partly fixed mine too. In any case, way better than before, now i could actually try and close a call every once in a while.
But is there any way to permanently solve this?

^ Here's the video you're talking about: http://www.youtube.com/watch?v=uMk1S90MjbY&feature=youtu.be
BTW, same problem with my Defy. It used to work perfectly but then a few months ago I started noticing some problems with sensor (using Nordic 177-5 and CM7). Then I reflashed Nordic and used WajkIUI but the issue was still there. Luckily, WIUI has an option to completely disable proximity sensor which I did. Now, I have moved on to CEE 179-002 and CM9 and the issue comes back because now there's no option to disable proximity during call.
I still have to try out what that Chinese guy has shown. The very dim red light in sensor region is constantly glowing (if you look closely). Definitely a hardware issue.
Anybody else has permanent solution?

I have had the same problem.
A small time after i replaced my screwed front housing (broken screwholes ) inkl. Digitizer-toutch glass .
Im on quark's cm9 defy+ build march 30 at my normal defy.
A kernel change from 4.5.2-109 DHT22 to CM9 kernel solved the problem till now.
Now im looking for 4.5.1-134 DFP-231 kernel CWM update.zip
Sent from my MB526 using XDA App

So I followed the Chinese guy's video and found the my proximity sensor starts working, when I put a little pressure on the screw with a screw driver. Video tells us to rotate it, but mine works by pressure. it again stops working when pressure released. Now I don't know how to keep it constantly under pressure.
It's probably loose, coz sometimes it works on tapping the sensor.
bone101 said:
Im on quark's cm9 defy+ build march 30 at my normal defy.
A kernel change from 4.5.2-109 DHT22 to CM9 kernel solved the problem till now.
Click to expand...
Click to collapse
How are you able to run CM9 defy+ build on normal defy? Which is you base SBF ? are there any special steps required to install defy+ cm9 on defy? Please let me know, I'll try upgrading kernel, it might work!

bikerabhinav said:
So I followed the Chinese guy's video and found the my proximity sensor starts working, when I put a little pressure on the screw with a screw driver. Video tells us to rotate it, but mine works by pressure. it again stops working when pressure released. Now I don't know how to keep it constantly under pressure.
It's probably loose, coz sometimes it works on tapping the sensor.
How are you able to run CM9 defy+ build on normal defy? Which is you base SBF ? are there any special steps required to install defy+ cm9 on defy? Please let me know, I'll try upgrading kernel, it might work!
Click to expand...
Click to collapse
It is proximity sensor issue indeed. And dirt accumulation may be the problem! First try to check the working of proximity sensor by reading its raw values(Use Elixir2 or androsensor) And since it is still under warranty(7months) go see a service center... Unscrewing the torx screws may make it less water resistant and also loose your warranty!

pranks1989 said:
It is proximity sensor issue indeed. And dirt accumulation may be the problem! First try to check the working of proximity sensor by reading its raw values(Use Elixir2 or androsensor) And since it is still under warranty(7months) go see a service center... Unscrewing the torx screws may make it less water resistant and also loose your warranty!
Click to expand...
Click to collapse
Yes I tried Elixer2 and after tapping sensor a bit I can see the graph saying near/far as I move my hands over sensor. Dmesg logs an error too:
Code:
isl29030_get_avg_noise_floor: prox data sample 4 is 0x57
The 4 & 0x57 parts keep changing now and then to 0x58, 0x59.
I looked up the isl29030's driver for Defy and ended up with this.
This pastebin is the driver for same sensor used in Moto Atrix: http://pastebin.com/ur5LkA91 line 536 shows the error I get
Can someone please explain what's happening here?

bikerabhinav said:
Yes I tried Elixer2 and after tapping sensor a bit I can see the graph saying near/far as I move my hands over sensor. Dmesg logs an error too:
Code:
isl29030_get_avg_noise_floor: prox data sample 4 is 0x57
The 4 & 0x57 parts keep changing now and then to 0x58, 0x59.
I looked up the isl29030's driver for Defy and ended up with this.
This pastebin is the driver for same sensor used in Moto Atrix: http://pastebin.com/ur5LkA91 line 536 shows the error I get
Can someone please explain what's happening here?
Click to expand...
Click to collapse
Its because the sensor is not getting or not able to get enough samples or values to calculate.. Might be hardware issue!!

Cm9 + cm9 kernel dont solve the problem !!!
For more info about cm9 defy & defy+ look for the thread in XDA defy development sektion.
Sent from my MB526 using XDA App
---------- Post added at 04:39 PM ---------- Previous post was at 03:58 PM ----------
I opened the housing and cleaned the prox. sensor.
I tryed to fasten the screws not so hard as in the past.
Let´s have a look if its better now.
Maybe its a software bug

bone101 said:
I opened the housing and cleaned the prox. sensor. I tryed to fasten the screws not so hard as in the past.
Click to expand...
Click to collapse
Did this solve your problem?

No , I think Not......
Now i reflashed my Stock rom via RSD lite ans reenstalled my Backup
Now if i made a call the Display goes out for a moment, but a Bit longer than before, and comes again correctly.
Lets have a look.....how long
Sent from my MB526 using XDA App

Even I have this irritating problem after giving my phone for service due to water damage
Sent from my MB525 using XDA

Maybe its too hard screwed like in video
Sent from my MB526 using XDA App

This did not solve my problem...I have problem both with my led and sensor...may be its a bit complicated..should try giving it for service
Sent from my MB525 using XDA

Yes
Sent from my MB526 using XDA App

Smart Cover App

So I found out the hard way that the Tab 2 10.1 doesn't come with a proximity sensor (not sure how I missed this). Has anyone found an app that turns the screen on/off by opening and closing a case?
My assumption is that this isn't possible without a proximity sensor but thought I'd ask.
Sent from my Kanged Tab2

Shouldn't be impossible at all.. the device auto senses what the screen light should be I do not know if it uses the camera for this or if there is a second sensor to accomplish this.. but it sounds totally feasible to write a program that senses total darkness to tell the device to sleep Im not so sure how turning it back on would work..this would be am awesome app please post back if you find one
Sent from my GT-P3110 using xda app-developers app

Here there, sorry I don't think it is possible, even smart cover app relys on proximity sensor.
And no, light sensor wouldn't work in dark places or at night.
I believe proximity sensor is only present in cellular models. If so, on your dialpad/keypad, type *#0*# -> sensor -> and place an object near the top of the tablet where the speaker and light/prox sensors are located.
Screen should turn green, and PROXIMITY:0.0 -> PROXIMITY:1.0

Im not much on coding but you would see some light at night from the screen unless the sensor just sucks or the case lets too much light escape i dont see why it wouldnt.
Sent from my KFTT using xda app-developers app

mrkhigh said:
Im not much on coding but you would see some light at night from the screen unless the sensor just sucks or the case lets too much light escape i dont see why it wouldnt.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
The sensors are only effective if light in shinning directly above it. If light sensors were this sensitive (picking up light from screen), I adobt putting a smart cover on or putting it in your pocket isn't going to work since neither pockets or smart covers are completely light proof as sensors are near the top picking up reddish/faint light.
Cover isn't flat enough to stop screen backlight from traveling accorss the surface of tab and therefore sensors won't be triggered.
Common sense

do you try the Power Switch Pro?

Power Switch Pro works with my Tab 2 7.0 and I would think it would work with the 10.1. There is a lite version on Play that you can try. I liked it well enough to buy it.

chriscsh said:
do you try the Power Switch Pro?
Click to expand...
Click to collapse
Tel864 said:
Power Switch Pro works with my Tab 2 7.0 and I would think it would work with the 10.1. There is a lite version on Play that you can try. I liked it well enough to buy it.
Click to expand...
Click to collapse
I'll get it a shot and see if it works. Are you using the wireless or cellular version?
Sent from my NOTEworthy smartphone

Must be user error because power switch pro didn't work on my10.1
Sent from my Kanged Tab2

emeraldayotte said:
I'll get it a shot and see if it works. Are you using the wireless or cellular version?
Sent from my NOTEworthy smartphone
Click to expand...
Click to collapse
I'm using the wireless version. It works on my Samsung and also on the wife's rooted Nook tablet. It actually works the best when using the motion sensor and laying it upside down when you want it to turn off. A couple of times it didn't respond as quickly when lying on the back, but it works 100% of the time when laid upside down.

emeraldayotte said:
Must be user error because power switch pro didn't work on my10.1
Sent from my Kanged Tab2
Click to expand...
Click to collapse
i guess this only work on rooted device

emeraldayotte said:
So I found out the hard way that the Tab 2 10.1 doesn't come with a proximity sensor (not sure how I missed this). Has anyone found an app that turns the screen on/off by opening and closing a case?
My assumption is that this isn't possible without a proximity sensor but thought I'd ask.
Sent from my Kanged Tab2
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.sourcespark.app.casesensor&feature=related_apps#?t=W251bGwsMSwxLDEwOSwiY29tLnNvdXJjZXNwYXJrLmFwcC5jYXNlc2Vuc29yIl0.
Here you go its not free but 0.99 is not alot works off light sensor

My p3100 has a proximity
__________________
Sweet Devil >_<
GT-P3100 | Android 4.0.4 ICS | Sun Cellular
PM me if you need help

OptimusLove said:
My p3100 has a proximity
__________________
Sweet Devil >_<
GT-P3100 | Android 4.0.4 ICS | Sun Cellular
PM me if you need help
Click to expand...
Click to collapse
and...
perhaps we should buy your p3100....no comment

There is also a app at google play called Killswitch Lite.

power switch pro seems to do the job to a certain point. it works good outside, but when you are inside a room or place with a litle less light it starts to pop up that notification window and shut down the screen. maybe be it can be adjusted with the light sensor sensitivity but i found that so disturbing that i disable it.
for me it doesnt do the desired job. if someone has some idea how to make this useful will be thankful.

karaern said:
power switch pro seems to do the job to a certain point. it works good outside, but when you are inside a room or place with a litle less light it starts to pop up that notification window and shut down the screen. maybe be it can be adjusted with the light sensor sensitivity but i found that so disturbing that i disable it.
for me it doesnt do the desired job. if someone has some idea how to make this useful will be thankful.
Click to expand...
Click to collapse
Like I said earlier

searsh smart cover on google play best one is about 2 $

I use Case Sensor on my Tab 10.1" and it does it's job. It does use the light sensor so during night time or dark areas, it won't activate thinking the case is still covering the light sensor. This app is clever in that when you press the power button, it will override the app for a temporary amount of time. Good enough until someone else can think of a better way to execute or use a combination on different sensors to control the screen

Add another proximity sensor issue to the list

I read a few posts on here about the proximaty sensor not working on the Note 3. Well mine is a little different, My screen stays on even when I put the phone to my head. It started doing this just today, so well out of my 14 day return period.

Limeybastard said:
I read a few posts on here about the proximaty sensor not working on the Note 3. Well mine is a little different, My screen stays on even when I put the phone to my head. It started doing this just today, so well out of my 14 day return period.
Click to expand...
Click to collapse
Assumption that you have a clean screen and that you haven't flashed some ROM that could be the problem instead of the actual hardware.

Screen protector not covering sensor.......?

Bizzare rebooted, its all working now. Not rooted.

Proximity Sensor ADC Value - Please Weight In

My current Note has the proximity senor issue where it thinks my face is to the phone all the time and therefore gestures don't work and the screen goes black instantly when making a call. This has been outlined in a few threads. Here are two good ones:
This post has actual values for ADC:
http://forums.androidcentral.com/sa...-sensor-issue-during-calls-3.html#post3234634
Another with the same problem:
http://forum.xda-developers.com/showthread.php?t=2520118
I looked at a new note today that Bell is going to let me exchange my current note for. Its value with nothing close to it is about 30.
I would like to know what other peoples ADC values are. Simply enter *#0*# into your dialer, then choose sensors and you will see the ADC value with the proximity sensor. Could you please report that value with nothing close to the screen.
I'm trying to determine what the normal ADC value should be on a new working phone so I can figure out if the new phone (that has an ADC value of 30) is ok or not.
Thanks and hopefully this will help out other people.

Mine seems to stay at 33-35 until about 20cm away from the screen then starts increasing.

I don't have any problem what so ever with the screen turning off/on when calling. Not even once failed.
My values for ADC are 0, constantly 0, if nothing in front of the device. If i approximate my hand it starts increasing, and then the screen turns green and the phone vibrates when the proximity sensor goes from 0 to 1. If i put my finger on top of the sensor it stays at ADC 1003.
Is this how it is supposed to work?
N9005 with MJ7 firmware.

Mine is always below 10 if nothing is in front. Fluctuate between 5 and 9.
Sent from my SM-N9005 using XDA Premium 4 mobile app

My ADC values fluctuate between 30 - 34. @antt00, how come yours so low?

My first note idiled at around 29-30. My second replacement note idles between 0-1. I had proximity problems with my S4 so I check it religiously. While values around 30 would be okay for now, but you may run into problems later. The problems come when you have some dust that gets stuck inside on the sensor and causes a higher adc value. This is what causes the sensor to not work correctly. I have to take apart my S4 every 3 month or so just the clean it and then the number will drop back down to 6. Also keep in mind, the reading goes up a bit in direct sunlight. IMO I would get one that idles around 0, this will give you more headroom for dust.

Thanks for the feedback. I didn't get a chance to read all the posts before I went and got an exchange. For some reason their system let me exchange it even though I past 15 days so I kind of jumped on the chance. The new note at home reads around 20. Not as low as some but better then what I returned. I'll have to see how long it lasts and I'll keep and eye on it. It definitely sounds like its a combination of possibly bad/poor sensors. Dust build up inside which is a design flaw. And maybe poor calibration from samsung as it look like from a post I've see that you can re-calibrate the sensor, though I not sure if that may have some negative effects.
I didn't try and push them to let me cherry pick a phone, they were nice enough to let me check the ADC value and firmware version before the exchange. Hopefully this one works out or I'll have to try and get a better one. I'll see in time as my previous one definitely had the dust issue. It was pretty obvious because I could lower the ADC value if I blew compressed air in the ear piece.

i did notice the proximity sensor screwing around on phone calls, it would delay getting the screen back after distancing from it...
the procedure you gave me shows ADC values contentiously flipping from 9 to/through 13 (sometimes chronologically)
putting your hand over seems to green-out the window showing that proximity is working, nice, however, im having shadow greens, meaning, just leaving it on the table, once a minute it goes green, yet nothing moves over it...strange.
ps, no plastic cover used, dont see a reason to use protection with this quality

williamyi said:
My ADC values fluctuate between 30 - 34. @antt00, how come yours so low?
Click to expand...
Click to collapse
I have no idea.
Sent from my SM-N9005 using XDA Premium 4 mobile app

antt00 said:
I have no idea.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you applied the glass m sp gotten from Alex?
Sent from my SM-N9005 using XDA Premium 4 mobile app

williamyi said:
Have you applied the glass m sp gotten from Alex?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes but that does not obstruct the sensor. It only reaches below it.

Idling 0 with and without direct artificial light (no tested against sunlight). As my palm gets closer the number progressively increases. The screen turns green after reaching 120
I had no idea that a proper cleaning could fix the sensor. Thanks for the info
iiSo say we all!! From my Note 3 (N9005)

Well now I'm at about ADC 40. In two days the value has doubled. I can't win....

I have this problem with my AT&T N900A and the ADC value is between 82 and 85 at idle. If I wave my hand over the sensor it will go to 1000 but unfortunately its still not responding when I pull the phone from my face after a phone call.
I'm not rooted so I'm not going to manually adjust anything. Is the fix just to get another phone. This is sort of pissing me off. I've had 6 or so Samsung phones and never a problem so frustrating as this one.

And now I'm at ADC 90 and when I activate the sensor (screen goes green and vibrates) it won't stop when I move my hand away. There must be a serious design flaw that allows dust to get onto the sensor. Unfortunately I don't see any way to solve this....I don't know how many times I can return the phone and hope to get one that doesn't allow dust in. I guess the next step is to try and talk to Samsung.....

Has anyone gone as far as to replace the sensor? There is a part out there. Its listed as a 9000/9005 part, not sure if it works with US carrier models. I'm having a hard time finding it in stock anywhere though.
http://rounded.com/samsung-galaxy-note-3-n9005-front-camera-proximity-sensor.html?sl=EN
I have zero desire to send my device to a Samsung service center. I'd have to order a phone to use in the mean time until it came back. I'd rather just swap a new part in.

0/0/0
when i move one hand about 14-16cm above the device (and move it closer to it) the numbers start to increase

aygriffith said:
Has anyone gone as far as to replace the sensor? There is a part out there. Its listed as a 9000/9005 part, not sure if it works with US carrier models. I'm having a hard time finding it in stock anywhere though.
http://rounded.com/samsung-galaxy-note-3-n9005-front-camera-proximity-sensor.html?sl=EN
I have zero desire to send my device to a Samsung service center. I'd have to order a phone to use in the mean time until it came back. I'd rather just swap a new part in.
Click to expand...
Click to collapse
I have a strong feeling that its just dust getting in the way. I was at ADC 90, blew air at the ear piece and it dropped to ADC 60. Though I don't know how it looks like inside. I have a feeling some are sealing out the dust completely and some are not.
I do find it odd though that mine started out from factory at ADC 30

bnevets27 said:
I have a strong feeling that its just dust getting in the way. I was at ADC 90, blew air at the ear piece and it dropped to ADC 60. Though I don't know how it looks like inside. I have a feeling some are sealing out the dust completely and some are not.
I do find it odd though that mine started out from factory at ADC 30
Click to expand...
Click to collapse
I'm not really satisfied with the idea of periodically blowing into the ear piece of the phone with a can of air I don't regularly have otherwise. They need to accommodate the issue with a software fix for the sensor sensitivity if they can't fix the manufacturing process.
Sent from my Nexus 7 using Tapatalk 4

Now I'm ADC 99 and my screen doesn't turn on or off properly again. Haven't had a chance to call Samsung yet but this is really annoying. I also don't want return it and get a phone with the new bootloader. Ugh

[Q] Light sensor not working

Hi everyone
I have S4 i9505 I got it second hand
I noticed that the auto brightness not working
I make sensors test and her is screen shot for result
Another scresc shot from galaxy sensors app (3rd sensor says waiting)
Any idea how to solve this , is it SW or HW issue?

It is hardware issue
The hole whre you insert handsfree get some blower that blow air with pressure
Blow it properly hope this work
Sent from my SM-N910F using Tapatalk

dragonheart786 said:
It is hardware issue
The hole whre you insert handsfree get some blower that blow air with pressure
Blow it properly hope this work
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
I would try that , thanks

KOREAN!
(ALMOST 85% SURE)
Try comparing your phone with other S4's with smallest differences.
Regards,
hitman-xda