Discussion in 'Android Devices' started by ajoh99, Dec 1, 2009.
thanks but is this any different than the moments built in sensor?
It makes it more sensitive and with a delay so that every time you move the phone away from your ear it does not turn on.
Yep...I've done this a few times too. Very annoying! I try to be aware that whenever i move my phone away from my ear/face it will light up. So I keep it fairly close to my ear and away from my face at all times lol. I guess a quick solution would be to get a bluetooth as someone has suggested.
Holy crap dude! Take a bath!! *gags at the thought of a mud-man running around town*
The accidental mute and speaker phone issues are resolved I believe with the CL14 update. I have noticed (can't confirm) that the new in call screen moves those buttons lower on the screen and makes them smaller, lessoning the risk.
Does it? My wife would love that. Every next sentance from her mouth is "Hello? Did I mute this thing again? Hello?"
Funny stuff right there! A little bit of phone engineer humor / easter egg to keep 'em guessing.
I have had this problem since day 1 and continue to have it after the update.By far my biggest complaint about the phone, but I am holding out for a fix at some point. I try very hard to be careful but find my screen doing all kinds of things. Lovely when I am talking to a client...
Someone suggested pressing the "Back" button when you receive a phone call. This locks the phone so you can't press anything accidentally. Same goes for when you make a phone call, it returns to the home screen. Just a temporary fix, but it eliminates the risk of putting the phone on mute or speaker unintentionally
I called to Sprint to see if they had a suggested work around since I figured this is a known problem. Big shock, Sprint says it 'hasn't been reported' so there is no known issue. If you believe there are issues with the proximity sensor, CALL SPRINT and report it. Until they get some magical number of report from users of the problem, it is not considered a problem. I don't know if they can do anything software wise to fix this, but I would like to think that they at least recognize it as a known issue. I have seen this on forums over and over and personally experience on a daily basis, so I know I am not alone...
I think there was a learning curve for me on how the face proximity worked, but I noticed now that when I am on a call and I get a text message that screen lights up and button mashing ensues-- mute, speaker, the works. My friend claims his screen does not light up when he gets a text while on a call.
Do you have the update? Your friend may have the "earlier" version of the phone, without the update. When I get a text when I'm on a call, my phone doesn't light up and I don't have the update. However, the screen will turn on briefly if i get a text and the phone is sleeping, but I'm using Handcent.
Now that you bring it up, he didn't buy the phone until after the update. I have not gotten the update yet. I switched to handcent but haven't really tested it since then. When it happens, it is highly annoying, but i hardly use my moment for voice, so I haven't pursued the issue.
The proximity sensor app does fix the issue BUT it only works with the phone set to auto back light, which is just as annoying as the mute problem. I've become so used to the problem now that as soon as I hear the caller say "hello?", I correct the problem without them even knowing what happened. I hope that the person writing the proximity app is able to remove the auto back light limitation, because I have no confidence in Samsung ever fixing this or any other issue beyond releasing a vanilla 2.1 update.
After update, still happens for me. Left ear. I should not have to constantly think about the proximity of the phone to my head, but I do for fear of muting or hitting speaker.
I don't worry about it any more. I have noticed a HIGH responsiveness of the phone recognizing when something is against the sensor. My phone will shut off usually (only happened once in like 2 weeks now) about an inch from my ear. Even then, it's an almost instant screen shut off. It's still slow responding from being removed from my ear, but that's fine with me.
Maybe I just have a decent sensor. No idea really... oh yea! I've been going 2 days consistently now without a charge (no car charging to school or anything) with Wi-Fi and GPS turned on. When I charge it the second day it's usually reporting '20%' to me. I kind of half believe it, though it may be right. No idea why....
5-7 calls a day
Constant texts (~20-50)
Streaming music in 4 out of 6 classes
Web browsing whilst jammin'
Screen brightness to auto, timeout=1min.
Never really kill stuff with task killer unless my phone starts to get REALLY boggy (usually when around 15-10mb of mem. left free). I just let it run and do it's own thing.
Memory free on average.... couldn't really tell you, because well.... I never check! I think it's around 35-40mb.
I will probably give the proximity app a try. It can't hurt I guess.
I was on the phone for an hour last night and I had the phone all over the side of my head. I know this because the volume level kept changing and I kept readjusting the phone to hear better. The screen never came on. Not once. So I am sure now that it is somehow related to the text notification waking the screen up. But I even turned notifications off and still had the screen wake up, so I am still at a loss.
this is super annoying and a huge problem for me. I can't have the speakerphone suddenly activate and start broadcasting my calls when I am on sensitive calls .... I wish when people review phones, they would check all of these issues as I did not know about this when I bought the phone.
For anyone having this issue, you may want to read up on rooting your phone. Click on the All Things Root section at the top. I replaced the dialer and removed the Speakerphone and Mute buttons all together. I can get to those options still by pressing menu.
Fantastic! Care to share screenshots or directions on how you did that? TIA.
Edit: Found the below link. Anybody tried this yet and can confirm it works?
Maybe I'm stupid, but are you all saying the only way to fix this problem is to basically wipe out my phone and start again? Because that's what it seems rooting is? I really didn't buy a phone so I'd have to program the whole thing. Also, I'm confused, because it is said above that when you remove the mute and speaker buttons you can access them from menu, but I don't see how. As it stands now if I hit menu from a call nothing helpful comes up. Also, when it leaves the call screen in a middle of a call I can't access ANYTHING helpful anymore, be it mute, speaker, whatever. I'm frustrated.
With the 2.1 update you have to slide a icon across the screen to either mute or turn speaker phone on. It pretty much solves that problem.
Yeah, 2.1 FTW on that matter. I got use to holding the phone at an angle from my face so I wouldn't touch it. My wife never caught on. She still has 1.5 on her phone as well LOL.
Are you sure about this? I'm running 2.1 on my Motorola Droid and to mute a call or turn speakerphone on just requires a simple button push. I don't have any issues with the proximity sensor on my droid but my gf just bought the moment and is having this issue. It would be great if 2.1 on the moment had the slide feature that you mention, but I don't see why it would be any different than 2.1 on my droid.
hehe, because the leaked version is out and people are using it. jump on sdx-developers to get some screenshots.
as for 1.5, you can remove the mute and speaker buttons as well with a rooted phone. basically, what was done was XML edits to the buttons to make the 0 x 0