Go Back   Android Forums > Android Phones > Samsung i7500

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

test: Reply
 
LinkBack Thread Tools
Old December 24th, 2009, 11:49 PM   #1 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2009
Location: North Florida, USA
Posts: 75
 
Device(s): Nexus One
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 2 Posts
Default Proximity sensor while making calls

I have not seen this mentioned but I have trouble with it every day. When I make a call the proximity sensor does not always work. During the call my cheek will pull up the keypad and then start dialing. Sometimes this will happen even if I remember to hit the sleep/wake button as I start the call (to turn off the screen).

Very embarrassing to explain to the other party why your phone is touch-toning over their conversation.

Does this happen to everyone or just me? It did it with the I4 and now the K4 firmware.

James Bell is offline  
Reply With Quote
sponsored links
Old December 26th, 2009, 09:25 AM   #2 (permalink)
Senior Member
 
Rastaman-FB's Avatar
 
Join Date: Sep 2009
Location: UK
Posts: 6,113
 
Device(s): HTC Desire (depreciated) Blue Galaxy s3 (international)
Carrier: Not Provided

Thanks: 114
Thanked 1,016 Times in 838 Posts
Default

Quote:
Originally Posted by James Bell View Post
I have not seen this mentioned but I have trouble with it every day. When I make a call the proximity sensor does not always work. During the call my cheek will pull up the keypad and then start dialing. Sometimes this will happen even if I remember to hit the sleep/wake button as I start the call (to turn off the screen).

Very embarrassing to explain to the other party why your phone is touch-toning over their conversation.

Does this happen to everyone or just me? It did it with the I4 and now the K4 firmware.
other people have reported this
have you looked where the proximity sensor is?
the ones that reported this issue noticed a build up of dust in there from a bad seal on the phone.
no fix though
Rastaman-FB is offline  
Reply With Quote
Old December 26th, 2009, 10:23 AM   #3 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2009
Location: North Florida, USA
Posts: 75
 
Device(s): Nexus One
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 2 Posts
Default

I have only had the phone a month or so, and I don't see any dust. I removed my screen protector from the proximity sensor to see if that would help but no luck. It sure seems to be software. Sometimes when I make a call the screen darkens as it starts to place the call - before I bring it to my cheek. Most times it does not do this and no amount of bringing it to my face will make it go dark.
James Bell is offline  
Reply With Quote
Old December 26th, 2009, 04:19 PM   #4 (permalink)
Member
 
Join Date: Sep 2009
Location: Serbia
Posts: 161
 
Device(s): HTC Desire Z
Carrier: Not Provided

Thanks: 2
Thanked 7 Times in 7 Posts
Default

If it's software problem wouldnt there be more people around with problem like this. Hardware issue seems more likely to me....
Naruvam is offline  
Reply With Quote
Old December 27th, 2009, 08:27 AM   #5 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 14
 
Device(s): i7500
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

As far as I know K4 has diffirent sensor driver (samsong.sensor.so as I remember) so you shoud check with other firmwares first (I think II5 should be enought). For testing purpose there is app called "sensor test" in market. This tools shows state of proximity sensor (it should shows "1" if you hide sensor, and "0" if sensor is clear). If sensor won't work in II5 and K4 then it might be really broken.
crow6 is offline  
Reply With Quote
Old December 27th, 2009, 09:31 AM   #6 (permalink)
Junior Member
 
Join Date: Sep 2009
Posts: 36
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by James Bell View Post
Does this happen to everyone or just me? It did it with the I4 and now the K4 firmware.
Its happening to me as well now with K4, didn't happen with I5 or any of the other firmwares I've flashed.
hagi is offline  
Reply With Quote
Old December 27th, 2009, 11:49 AM   #7 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 14
 
Device(s): i7500
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

@hagi:
try to replace /system/lib/hw/sensors.samsung.so (I made mistake in my previous post ) file from II5 firmware to K4. You can use adb (with push/pull command) program to do it.
crow6 is offline  
Reply With Quote
Old December 27th, 2009, 04:50 PM   #8 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2009
Location: North Florida, USA
Posts: 75
 
Device(s): Nexus One
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 2 Posts
Default

The "sensor test" app shows nothing for my proximity sensor. Can another Galaxy user confirm it should work for us? I just wonder if the test is for specific chip(s) that the Galaxy might not use.
James Bell is offline  
Reply With Quote
Old December 28th, 2009, 02:25 AM   #9 (permalink)
Senior Member
 
KlaymenDK's Avatar
 
Join Date: May 2009
Location: Denmark
Posts: 1,221
 
Device(s): HTC Desire Z (rooted, CyanogenMod v7.1; Revoked ClockworkMod) HTC Desire (rooted, Oxygen rom; Revoke
Carrier: Not Provided

Thanks: 31
Thanked 132 Times in 100 Posts
Default

James, I had tons of proximity problems with I5, but none since I updated to K4. Have you tried to reflash back to I5 and then K4 again? I'm pretty confident that the K4 version should fix your problem.
__________________
Don't forget to hit the "Thanks" button when someone helps you!!!
How To Ask Questions The Smart Way
-- 010\001\111 --
KlaymenDK is offline  
Reply With Quote
Old December 28th, 2009, 08:48 AM   #10 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2009
Location: North Florida, USA
Posts: 75
 
Device(s): Nexus One
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 2 Posts
Default

Thanks for the advice but ugh, another reflash? I have 20 apps installed and all my accounts setup..I just put in K4 3 days ago. I had all these same problems with I5 too BTW.

Is there something other than (not free) MyBackup that will save everything and make re-flashing less painful?
James Bell is offline  
Reply With Quote
sponsored links
Old December 28th, 2009, 05:13 PM   #11 (permalink)
Senior Member
 
KlaymenDK's Avatar
 
Join Date: May 2009
Location: Denmark
Posts: 1,221
 
Device(s): HTC Desire Z (rooted, CyanogenMod v7.1; Revoked ClockworkMod) HTC Desire (rooted, Oxygen rom; Revoke
Carrier: Not Provided

Thanks: 31
Thanked 132 Times in 100 Posts
Default

Quote:
Originally Posted by James Bell View Post
... ugh, another reflash? I have 20 apps installed and all my accounts setup ... Is there something ... that will save everything and make re-flashing less painful?
I feel your pain. The reflash itself isn't so bad really, it's having to start from scratch. That's the downside of the Android security model: system-wide backups aren't really possible ... unless you hack it.

I recently followed the "Simple Rooting Guide (without galax0/galaxher0 roms)" to get the modified rescue system which enables a full system backup/restore function called "Nandroid". You can apply this to your existing device with no ill effects , but I think you will need to start afresh with every new firmware version. What I'm saying is, once you're on K4 (and find it working, and have it set up the way you want it) you can make a solid restore point to revert to when you want to experiment.
KlaymenDK is offline  
Last edited by KlaymenDK; December 28th, 2009 at 05:15 PM.
Reply With Quote
Old December 28th, 2009, 05:26 PM   #12 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 10
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I have this same problem with my phone, running a brand new IK4 install.
fabianobonin is offline  
Reply With Quote
Old December 28th, 2009, 09:07 PM   #13 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2009
Location: North Florida, USA
Posts: 75
 
Device(s): Nexus One
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 2 Posts
Default

Can someone please take 2 minutes to download the "sensor test" app from the Market (free) and see if they get data for their proximity sensor (last one on the list). A K4 firmware user would be even better.

I get all zeros but I don't know if that means my sensor is broken or the program doesn't work for the Galaxy.
James Bell is offline  
Reply With Quote
Old December 29th, 2009, 12:33 AM   #14 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 10
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by James Bell View Post
Can someone please take 2 minutes to download the "sensor test" app from the Market (free) and see if they get data for their proximity sensor (last one on the list). A K4 firmware user would be even better.

I get all zeros but I don't know if that means my sensor is broken or the program doesn't work for the Galaxy.
I downloaded the 'sensor test'.
My firmware is K4.

When i start it, the 'proximity' section has 3 lines:
0: 0.0
1: 0.0
2: 0.0

When i put it near my face, the first line changes:
0: 1.0
1: 0.0
2: 0.0
fabianobonin is offline  
Reply With Quote
Old December 29th, 2009, 12:52 AM   #15 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 14
 
Device(s): i7500
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I've Galaxo 1.1 (so it's II5) with sensor driver from IK4. Sensor test shows 1 when near face and 0 with clear. Before - with original driver it don't work (always 0). Moreover now it seems that dialpad works ok during calls (3 days tests without restarting!)
crow6 is offline  
Reply With Quote
Old December 29th, 2009, 02:06 AM   #16 (permalink)
Member
 
Join Date: Sep 2009
Location: London
Posts: 231
 
Device(s): Nexus 5, 4 & 7
Carrier: Three

Thanks: 0
Thanked 7 Times in 6 Posts
Default

Quote:
Originally Posted by fabianobonin View Post
I downloaded the 'sensor test'.
My firmware is K4.

When i start it, the 'proximity' section has 3 lines:
0: 0.0
1: 0.0
2: 0.0

When i put it near my face, the first line changes:
0: 1.0
1: 0.0
2: 0.0
Same here with K4.
chistery is offline  
Reply With Quote
Old December 29th, 2009, 03:01 AM   #17 (permalink)
Senior Member
 
KlaymenDK's Avatar
 
Join Date: May 2009
Location: Denmark
Posts: 1,221
 
Device(s): HTC Desire Z (rooted, CyanogenMod v7.1; Revoked ClockworkMod) HTC Desire (rooted, Oxygen rom; Revoke
Carrier: Not Provided

Thanks: 31
Thanked 132 Times in 100 Posts
Default

Quote:
Originally Posted by chistery View Post
Same here with K4.
Ditto.
But, I have had tons of sensor problems with every firmware up until that, I even sent it in for repair for it (and all they did was reinstall the same old firmware). It may be you really do have a defective unit.

Oh, and tip: You don't need an app, you can just dial *#*#0*#*#* to access a host of test programs.
KlaymenDK is offline  
Reply With Quote
Old December 30th, 2009, 12:03 AM   #18 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2009
Location: North Florida, USA
Posts: 75
 
Device(s): Nexus One
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 2 Posts
Default

Thanks to everyone for testing for me & the dial code sensor test screen.

Nothing I do seems to make my sensor change at all. I will try to pop open the cover to look for a loose connection. If no luck I'll try reflashing back to I5 then K4 again. If all THAT fails I'll see if Samsung will fix it.
James Bell is offline  
Reply With Quote
Old January 1st, 2010, 02:19 AM   #19 (permalink)
Member
 
Kouske's Avatar
 
Join Date: Oct 2009
Posts: 105
 
Device(s): ex i7500@ galaxo v1.6.3.3 | now on HTC Desire@ dGB v1.4 ManU1.4
Carrier: Not Provided

Thanks: 1
Thanked 6 Times in 6 Posts
Default

Quote:
Originally Posted by crow6 View Post
I've Galaxo 1.1 (so it's II5) with sensor driver from IK4. Sensor test shows 1 when near face and 0 with clear. Before - with original driver it don't work (always 0). Moreover now it seems that dialpad works ok during calls (3 days tests without restarting!)
Could you upload the IK4 sensor driver? I wanna try doing it as well.
Kouske is offline  
Reply With Quote
Old January 1st, 2010, 02:57 PM   #20 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 14
 
Device(s): i7500
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

@Kouske
up to II5: RapidShare: 1-CLICK Web hosting - Easy Filehosting
from IK4: RapidShare: 1-CLICK Web hosting - Easy Filehosting
crow6 is offline  
Reply With Quote
sponsored links
Old January 1st, 2010, 07:48 PM   #21 (permalink)
Member
 
Kouske's Avatar
 
Join Date: Oct 2009
Posts: 105
 
Device(s): ex i7500@ galaxo v1.6.3.3 | now on HTC Desire@ dGB v1.4 ManU1.4
Carrier: Not Provided

Thanks: 1
Thanked 6 Times in 6 Posts
Default

Works like a charm. Thank you very much.
Kouske is offline  
Reply With Quote
Old January 3rd, 2010, 09:19 AM   #22 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2009
Location: North Florida, USA
Posts: 75
 
Device(s): Nexus One
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 2 Posts
Default

Taking it apart and reconnecting the sensor did not help. @Kouske: Are you pushing those i5 and K4 sensor drivers to the phone without reflashing? If so, how exactly?
James Bell is offline  
Reply With Quote
Old January 19th, 2010, 07:16 AM   #23 (permalink)
Senior Member
 
informale's Avatar
 
Join Date: Oct 2009
Location: Scotland
Posts: 704
 
Device(s): Samsung GT-i7500 @ Galaxo 1.6.3.4 / JC6
Carrier: Not Provided

Thanks: 19
Thanked 34 Times in 26 Posts
Default

That problem hit me recently

I've done some testing too. I think the problem is with the sensor driver, or whatever there is interpreting data from the sensor and reporting it to the apps.

Notice when you launch Sensor Test, GP2AP reads 0. Cover the sensor - the reading will change to 1. Now when you remove the finger it is still 1. It is stuck in 1 forever, unless you kill the Sensor Test and restart it. So it works the same way with force stopping Dialer Storage from app manager.

So I suspect the driver does not report the sensor changing back to 0 to the apps. Which is why the Dialer locks up. The only question is then, why the screen even turns on - it should be receiving false sensor status as well.

When testing with built-it tester (dial *#*#0*#*#*), covering the sensor triggers the test app to turn on vibration and, again, it won't stop until the app is restarted.
informale is offline  
Reply With Quote
Old January 19th, 2010, 07:57 AM   #24 (permalink)
Senior Member
 
Rastaman-FB's Avatar
 
Join Date: Sep 2009
Location: UK
Posts: 6,113
 
Device(s): HTC Desire (depreciated) Blue Galaxy s3 (international)
Carrier: Not Provided

Thanks: 114
Thanked 1,016 Times in 838 Posts
Default

im on galaxo ii5 with ii5 sensor drivers and proximity sensor resets to 0 every time
Rastaman-FB is offline  
Reply With Quote
Old January 19th, 2010, 08:05 AM   #25 (permalink)
Senior Member
 
informale's Avatar
 
Join Date: Oct 2009
Location: Scotland
Posts: 704
 
Device(s): Samsung GT-i7500 @ Galaxo 1.6.3.4 / JC6
Carrier: Not Provided

Thanks: 19
Thanked 34 Times in 26 Posts
Default

I guess it would be rational to go back to Galaxo (II5) from IK5 then ) Snappiness of IK5 is immeasurable - may be it is just placebo, and I don't use the pouch, so the camera button battery drain should not be a problem. + no dialer bug + the compcache and swap.

seems like a no-brainer )
informale is offline  
Last edited by informale; January 19th, 2010 at 08:05 AM.
Reply With Quote
Old January 19th, 2010, 08:35 AM   #26 (permalink)
Junior Member
 
Join Date: Nov 2009
Posts: 15
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 1 Post
Default

I believe that the problem is in the sensor hardware itself or there is dust in front of it, not in the drivers.

Informale, have you tried to light the sensor with flashlight? My sensor returns to 0 when the sensor is in very bright light.
crester is offline  
Reply With Quote
Old January 19th, 2010, 08:41 AM   #27 (permalink)
Senior Member
 
informale's Avatar
 
Join Date: Oct 2009
Location: Scotland
Posts: 704
 
Device(s): Samsung GT-i7500 @ Galaxo 1.6.3.4 / JC6
Carrier: Not Provided

Thanks: 19
Thanked 34 Times in 26 Posts
Default

Surprisingly, it does reset under bright light, but not just any light. I tried mega powerful LED torch - did not work. I tried a regular light bulb - it reset. Weird...

I would not say mine has dust over the sensor - seems free of any particles.
informale is offline  
Last edited by informale; January 19th, 2010 at 08:42 AM.
Reply With Quote
Old January 19th, 2010, 09:57 AM   #28 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 14
 
Device(s): i7500
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

@informale:
try to hit top of yours Galaxy. I suggest coach or something soft. I tried some time ago and it works (dust inside mobile???) :]
crow6 is offline  
Reply With Quote
Old January 19th, 2010, 12:31 PM   #29 (permalink)
Senior Member
 
informale's Avatar
 
Join Date: Oct 2009
Location: Scotland
Posts: 704
 
Device(s): Samsung GT-i7500 @ Galaxo 1.6.3.4 / JC6
Carrier: Not Provided

Thanks: 19
Thanked 34 Times in 26 Posts
Default

Quote:
Originally Posted by crow6 View Post
@informale:
try to hit top of yours Galaxy. I suggest coach or something soft. I tried some time ago and it works (dust inside mobile???) :]
I do hope you meant couch I'm afraid my Galaxy would not survive coach in any one of its meanings
informale is offline  
Reply With Quote
Old January 19th, 2010, 12:47 PM   #30 (permalink)
Senior Member
 
informale's Avatar
 
Join Date: Oct 2009
Location: Scotland
Posts: 704
 
Device(s): Samsung GT-i7500 @ Galaxo 1.6.3.4 / JC6
Carrier: Not Provided

Thanks: 19
Thanked 34 Times in 26 Posts
Default

Guys! Solved. Just get a can of compressed air and spray it into the speaker, using angle of approx. 45 degrees. 3 or 4 sprays fixed the sensor for me. It really was dust

See attached image for spraying instruction Aim exactly where the arrow ends, not at the sensor but exactly there - this way it hits the sensor too.

Apparently it indeed has nothing to do with the firmware version. Shall we add that to the FAQ?
Attached Images
File Type: jpg galax_clean_sensor.jpg (8.3 KB, 167 views)
informale is offline  
Last edited by informale; January 19th, 2010 at 12:50 PM.
Reply With Quote
The Following User Says Thank You to informale For This Useful Post:
dryhte (March 18th, 2010)
sponsored links
Old January 19th, 2010, 03:20 PM   #31 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 5
 
Device(s): Samsung Galaxy i7500
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

That's the fix. I did it while I was calling my voicemail. Didn't work at the start of the call, a little compressed air and then it started working.
Thanks informale.
epicpajl is offline  
Reply With Quote
Old January 20th, 2010, 12:18 AM   #32 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 14
 
Device(s): i7500
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by informale View Post
Surprisingly, it does reset under bright light, but not just any light. I tried mega powerful LED torch - did not work. I tried a regular light bulb - it reset. Weird...
I thing it's OK - as far as i know proximity sensor is just IR receiver and LEDs doesn't emits (almost) any IR radiation...

@informale:
Yes - couch. I'm not native english speaker - sorrry :] And I'm happy You did the trick

About soft - I tried trick with changing driver and it helped me. So it can be also a fix for someone...
crow6 is offline  
Reply With Quote
Old January 20th, 2010, 05:23 AM   #33 (permalink)
Senior Member
 
informale's Avatar
 
Join Date: Oct 2009
Location: Scotland
Posts: 704
 
Device(s): Samsung GT-i7500 @ Galaxo 1.6.3.4 / JC6
Carrier: Not Provided

Thanks: 19
Thanked 34 Times in 26 Posts
Default

Quote:
About soft - I tried trick with changing driver and it helped me. So it can be also a fix for someone...
Well, maybe in some fw versions the driver is calibrated to react at lower thresholds - the trick with the light worked for me - which means that the sensor is somewhat functional even when covered with dust. But really, I now think the dust is the primary cause.
informale is offline  
Last edited by informale; January 20th, 2010 at 05:23 AM.
Reply With Quote
Old January 26th, 2010, 02:05 AM   #34 (permalink)
Junior Member
 
Join Date: Sep 2009
Posts: 62
 
Device(s): HTC Desire HD Samsung Galaxy i7500
Carrier: Not Provided

Thanks: 3
Thanked 5 Times in 5 Posts
Default

Quote:
Originally Posted by informale View Post
Guys! Solved. Just get a can of compressed air and spray it into the speaker, using angle of approx. 45 degrees. 3 or 4 sprays fixed the sensor for me. It really was dust

See attached image for spraying instruction Aim exactly where the arrow ends, not at the sensor but exactly there - this way it hits the sensor too.

Apparently it indeed has nothing to do with the firmware version. Shall we add that to the FAQ?
Works for me, used a hoover to gently suck around the speaker, usb, headphone and odd hole in the top (???).

I also had a screen protector fitted, after trimming this down a bit so you clearly expose the 3 sensor dots on the right of the speaker, this also seemed to help.


Something to add, the Sensor test never changed unless the dialer was active, (IH4 FW) but having now (finally) updated to the official UK O2 IK4 version this now works well all the time.


Thanks to all as this problem was really really annoying.
qwerty100 is offline  
Reply With Quote
Old January 26th, 2010, 03:15 AM   #35 (permalink)
Senior Member
 
mrqs's Avatar
 
Join Date: Sep 2009
Location: Suomi Finland Perkele
Posts: 1,448
 
Device(s): htc sensation nokia n8 samsung galaxy (broken - waterdamage)
Carrier: Not Provided

Thanks: 46
Thanked 92 Times in 78 Posts
Default

Quote:
Originally Posted by qwerty100 View Post
odd hole in the top (???).
assuming you mean the one on the corner, it's for a strap, doesn't go inside the phone
__________________
All the best bands are affiliated with Satan - Bart Simpson
mrqs is offline  
Reply With Quote
Old January 26th, 2010, 03:26 AM   #36 (permalink)
Senior Member
 
Rastaman-FB's Avatar
 
Join Date: Sep 2009
Location: UK
Posts: 6,113
 
Device(s): HTC Desire (depreciated) Blue Galaxy s3 (international)
Carrier: Not Provided

Thanks: 114
Thanked 1,016 Times in 838 Posts
Default

no theres a tiny pinhole to the right of the usb socket
Rastaman-FB is offline  
Reply With Quote
Old January 26th, 2010, 04:01 AM   #37 (permalink)
Senior Member
 
mrqs's Avatar
 
Join Date: Sep 2009
Location: Suomi Finland Perkele
Posts: 1,448
 
Device(s): htc sensation nokia n8 samsung galaxy (broken - waterdamage)
Carrier: Not Provided

Thanks: 46
Thanked 92 Times in 78 Posts
Default

oh, didn't notice that with my usb flap open (charging atm) - guess it's for some sensor?
mrqs is offline  
Reply With Quote
Old January 26th, 2010, 05:42 AM   #38 (permalink)
Senior Member
 
informale's Avatar
 
Join Date: Oct 2009
Location: Scotland
Posts: 704
 
Device(s): Samsung GT-i7500 @ Galaxo 1.6.3.4 / JC6
Carrier: Not Provided

Thanks: 19
Thanked 34 Times in 26 Posts
Default

Maybe it's a noise cancellation mic. But the position is weird for it to be one.
informale is offline  
Last edited by informale; January 26th, 2010 at 05:42 AM.
Reply With Quote
Old January 30th, 2010, 08:13 AM   #39 (permalink)
Junior Member
 
Join Date: Nov 2009
Posts: 15
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

that's the mic for video recording.. it has a separate mic.
trin is offline  
Reply With Quote
Old February 8th, 2010, 06:06 AM   #40 (permalink)
Senior Member
 
mrqs's Avatar
 
Join Date: Sep 2009
Location: Suomi Finland Perkele
Posts: 1,448
 
Device(s): htc sensation nokia n8 samsung galaxy (broken - waterdamage)
Carrier: Not Provided

Thanks: 46
Thanked 92 Times in 78 Posts
Default

this just made me think, couldn't that extra mic be used for noise cancellation?
mrqs is offline  
Last edited by mrqs; February 8th, 2010 at 06:07 AM.
Reply With Quote
sponsored links
Old February 8th, 2010, 07:18 AM   #41 (permalink)
Senior Member
 
informale's Avatar
 
Join Date: Oct 2009
Location: Scotland
Posts: 704
 
Device(s): Samsung GT-i7500 @ Galaxo 1.6.3.4 / JC6
Carrier: Not Provided

Thanks: 19
Thanked 34 Times in 26 Posts
Default

I thought about it too, but I suppose Samsung engineers didn't )

And (though I'm not a sound engineer) I guess the position is not the best for noise cancellation mic - it should be on the back of the phone, rather than on the top.
informale is offline  
Reply With Quote
Old February 8th, 2010, 07:27 AM   #42 (permalink)
Senior Member
 
KlaymenDK's Avatar
 
Join Date: May 2009
Location: Denmark
Posts: 1,221
 
Device(s): HTC Desire Z (rooted, CyanogenMod v7.1; Revoked ClockworkMod) HTC Desire (rooted, Oxygen rom; Revoke
Carrier: Not Provided

Thanks: 31
Thanked 132 Times in 100 Posts
Lightbulb

Quote:
Originally Posted by trin View Post
that's the mic for video recording.. it has a separate mic.
I just tested this, and it seems to be incorrect.
I recorded a video in a quiet room and supplied some "noise" (known to some as "80's music" ) through a set of earplugs. The video only contained audio when I held an earplug near the bottom phone mic; I heard no difference when I held an earplug near both holes, so I don't think that (in the Galaxy, at least) there's any active noise cancellation.

I could be wrong, though!
KlaymenDK is offline  
Last edited by KlaymenDK; February 8th, 2010 at 07:28 AM.
Reply With Quote
Old February 8th, 2010, 08:39 AM   #43 (permalink)
Senior Member
 
Rastaman-FB's Avatar
 
Join Date: Sep 2009
Location: UK
Posts: 6,113
 
Device(s): HTC Desire (depreciated) Blue Galaxy s3 (international)
Carrier: Not Provided

Thanks: 114
Thanked 1,016 Times in 838 Posts
Default

Quote:
Originally Posted by KlaymenDK View Post
I just tested this, and it seems to be incorrect.
I recorded a video in a quiet room and supplied some "noise" (known to some as "80's music" ) through a set of earplugs. The video only contained audio when I held an earplug near the bottom phone mic; I heard no difference when I held an earplug near both holes, so I don't think that (in the Galaxy, at least) there's any active noise cancellation.

I could be wrong, though!
could be for phone calls only
Rastaman-FB is offline  
Reply With Quote
Old February 8th, 2010, 08:53 AM   #44 (permalink)
Senior Member
 
KlaymenDK's Avatar
 
Join Date: May 2009
Location: Denmark
Posts: 1,221
 
Device(s): HTC Desire Z (rooted, CyanogenMod v7.1; Revoked ClockworkMod) HTC Desire (rooted, Oxygen rom; Revoke
Carrier: Not Provided

Thanks: 31
Thanked 132 Times in 100 Posts
Default

Nope, performed another test, replacing the video recording with a phone call.

I don't know what the top hole is for; but it seems to have nothing to do with audio input.

Anyway, I think I'm done hijacking this thread (wasn't really about that top hole).
KlaymenDK is offline  
Last edited by KlaymenDK; February 8th, 2010 at 08:55 AM.
Reply With Quote
Old March 12th, 2010, 06:39 AM   #45 (permalink)
New Member
 
Join Date: Mar 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default fixing the problem

reading through the different posts here is what i did.
i am new to the galaxy so didnt want to mess with K4/II5.
i did manage to figure the problem has to do with the proimity sensor that detects that i am geting near the phone but doesnt change when i get away again.
setting the galaxy next to a strong light when the sensor recognizes you as near to it, will change the sensor back to it normal stage. you can then use the dialped when in call.
benfuniv is offline  
Reply With Quote
Old March 17th, 2010, 08:40 PM   #46 (permalink)
New Member
 
Join Date: Mar 2010
Location: Canada
Posts: 1
 
Device(s): Samsung Galaxy
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by informale View Post
Guys! Solved. Just get a can of compressed air and spray it into the speaker, using angle of approx. 45 degrees. 3 or 4 sprays fixed the sensor for me. It really was dust

See attached image for spraying instruction Aim exactly where the arrow ends, not at the sensor but exactly there - this way it hits the sensor too.

Apparently it indeed has nothing to do with the firmware version. Shall we add that to the FAQ?
I've that keypad lockup problem during a call, and i want through 6 Samsung dealer stores but nobody could solve the problem. Searching the net and found your solution, I tried it which fixed my problem right the way, you're such a genius.
tsaltsrif is offline  
Reply With Quote
Old March 18th, 2010, 05:58 AM   #47 (permalink)
Member
 
Join Date: Mar 2010
Location: Belgium
Posts: 186
 
Device(s): Samsung Galaxy I7500 (Froyo - GAOSP nightlies since 09182010) & LG P500 Optimus One
Carrier: Not Provided

Thanks: 8
Thanked 31 Times in 15 Posts
Default

great isn't it I love him too. (for that solution )
dryhte is offline  
Reply With Quote
Old April 13th, 2010, 05:37 PM   #48 (permalink)
New Member
 
Join Date: Apr 2010
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default The air fix worked for me

I'm a new Galaxy user, about a week. I too could not use the dialpad on phone calls.

10 seconds with the vacuum cleaner, alternating between the USB port and the earpiece. Now it's working perfectly.


In regard to diagnostics, I could not get the "sensor test" app to detect the proximity detector, but the built-in *#*0*#*#* test does work. I get detection at about 1cm from the earpiece.

Thanks Informale
patbeirneottawa is offline  
Reply With Quote
Reply

Buy the Samsung i7500
Sign up for instant notification when the Samsung i7500 goes on sale!
Samsung i7500

When Samsung joined the Open Handset Alliance, excitement and anticipation engulfed the mobile world. With industry leading mobile phones such as the Samsung Instinct and Samsung Omnia already on the market, expectations soared. The speculation can f... Read More



Go Back   Android Forums > Android Phones > Samsung i7500
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 10:04 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.