Related
Hi all
I have got a new sony x10 mini pro, and have an odd issue that seems a design floor.
When on a call my ear constantly presses the mute button and mutes people.
any one know of a way to remove the mute button on the interface or another app that can be used for in call functions.
any advice would be much apreiciated.
thank you
Mat
Place rthe phone closer to the ear so that the proximity sensor disables rthe screen
Sent from my U20i using XDA App
i have d same issue n keep muting calls
I have posted the same issue here
I use hands free but it is still easy to press with the side of your hand if you are holding the phone...
I notice on my phone the touch still works outside the screen border. and it sometimes goes on speaker or mute
+1
Really need a fix for this. Mostly the mute button is the problem, but i have had the loudspeaker activated a few times too.
+1
This is really annoying.
+1
I really nead a solution for this.
I was also annoyed with this, so I made an app that launches it self after accepting the call to avoid the issue. The app can be found at my site on paxanima DOT net (can't post URLs yet, apparently)
I just made it, so not too much real life testing, but seems to do the trick.
paxanima said:
I was also annoyed with this, so I made an app that launches it self after accepting the call to avoid the issue. The app can be found at my site on paxanima DOT net (can't post URLs yet, apparently)
I just made it, so not too much real life testing, but seems to do the trick.
Click to expand...
Click to collapse
Good work on that, thats a start.
But can someone just remove the goddamn mute button? UHHH!
It's too complicated for me. I think i installed like 4-5 apps but still couldnt get to the point where you can get the apk from the phone.
True, this is very annoying. SE has received plenty of complaints so I hope they're working on a solution. I am wondering if installing any of the new custom roms would sort out the issue for me since waiting for SE updates is a nightmare.
My problems started when I first updated to 2.1 where it happened in more than half of calls and got better with the last update and now happens only occasionally.
i never had that problem but i think that costum rom will help for these prob.
sory for bad english
Yeah, you have to be careful. Hold your phone from the back to avoid touching the front sides and slowly approach it to your head (the proximity sensor is at the top left of the phone). I'm pretty sure I look like a retard while doing so but hey, better than having the person on the other end saying "hello? is there anybody here? hello?".
Same here
This issue has also been annoying me from the beginning, and on every release of the SE standard ROMS. I don't understand why some people have the issue and others don't. Maybe it has something to do with the shape of one's ears??
No seriously, when i do some tests, like calling to my voicemail and then holding the phone in my hand, on some occasions the phone goes black after covering the proximity sensor with my finger, and sometimes the phone does not react at all when covering the sensor. So maybe some processes that are running prevent the proximity sensor from working correctly.
Would it be possible to adjust the semcphone.apk to have no mute button at all? I never use this option anyway.
Or is it only possible to change the shape and color of the icons/images.
As far as I know. When ever you made a call or answering call, the screen will turn off, right after you place the phone on your ear... So there's should be no pproblem answering or making call and suddenly pressed the mute button with own ear. Im using the same phone, and making almost 20 to 30 calls a day. And never even once encounter the problem as stated.
Sent from my U20i using XDA Premium App
I get this problem once in awhile too. I have to bring the phone to my ear slowly.
can't we just replace the dailer APK with something from HTC or something?
I also hate the current contact list, theres no smart search.
Yes you can. But it has to be ported with some mod for it to work.
Sent from my U20i using XDA Premium App
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Did you ever find the problem? My proximity sensor has stopped working also.
i am having an issue with mine too. at first i thought it was an issue with the screen not coming back on, but now i realize that the proximity sensor is not turning off the screen at all and my screen is just turning off when the screen timeout value is reached.
my phone is rooted, i have used titanium backup to freeze some of the apps associated with blur, and i have installed the hack to use webtop mode. can others that have this issue confirm if they are running stock or modified software?
***EDIT***
http://forum.xda-developers.com/showthread.php?p=12035170#post12035170
Any of you guys ever find a fix for this? I just noticed that mine is not working anymore either. It's rooted using aRoot but it was working for a while and now it doesn't anymore. I have another couple of days to exchange in store if I want to if it's a phone issue.
Crap, I'm having the same issue now too -- was working fine since I had it, but this occured just today, Day-2 of using 1.5.7 .... wonder if it's related ...
Crap, I'm having the same issue now too -- was working fine since I had it, but this occured just today, Day-2 of using 1.5.7 .... wonder if it's related ...
Reboot seems to fix this -- but annoying >_<
Is anyone that is having these issues using bluetooth? I have isolated mine to bluetooth and sent an issue report to Motorola.
same problem here but not using bluetooth
My wife's Atrix does the same thing. "dials or hangs up while in a call". She does not own a bluetooth headset and I have only connected a Motorola 305 one time to it. Reboot fixes the problem. Reboot seems to take forever when compared to my Dell Streak.
Ed Venture said:
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Click to expand...
Click to collapse
Had the problem with mine when I installed a different launcher had to delete it and restart the phone now it works ....for me anyways
Sent from my MB860 using XDA App
Hi I believe I traced the problem with the proximity sensor not working to Handcent SMS. On two separate Atrixes, as soon as I uninstalled Handcent and rebooted the phone the problem went away and stayed away. I have since installed GoSMS and now it happens just sometimes (usually after I install a new app) but a reboot after installing an app ususlly fixes it.
My Phone has a standard Telstra (Australia ROM) and is not unlocked or modified in any way.
Ed Venture said:
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Click to expand...
Click to collapse
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Seem that i have this problem on my atrix,when i calling someone,the screen turn off immediately and the led on proximity sensor just keep turn on when i stop calling,i cant imagine this atrix have a lot a lot hardware problem
Sent from my MB860 using Tapatalk 2
If you are using unlocked bootloader or if u have unlocked the dim using a code then u will have to disable the In Pocket detection and then try sounds crazy but worked for me.
Sent from my MB860 using xda premium
ranjithkumar1201 said:
If you are using unlocked bootloader or if u have unlocked the dim using a code then u will have to disable the In Pocket detection and then try sounds crazy but worked for me.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
care to share how?
Similar issue
Just installed latest stable build onto my Atrix 4G, everything seemed fine last night, although I was using phone with bluetooth, this morning get a call, answer, screen goes dark, red proximity light comes on, and I can hear no sound, [later on the caller said he could hear me fine].
Phone would not wake up right off, and when it did it I still could not hear caller.
Been screwing around with settings all morning to no avail, discovered that the phone will only work with bluetooth device connected. without bluetooth the device goes dark, cannot wake up, have to hard reboot, with bluetooth and volume button awaken enabled, it performs normally, so possible connection to issues in post with proximity but with a bluetooth twist...
12as2005 said:
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Click to expand...
Click to collapse
Did that...... Does nothing much....
12as2005 said:
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Click to expand...
Click to collapse
Worked for me!!!
Stock rom with, root, atrix tweaks installed.
Thank's a lot!!!
Anyone else having issues with the proximity sensor not working when on a call? Screen stays on for me when its against my ear. I'm also rooted with Alien rom and Knightwolf's themes.
Sent from my MB855 using XDA App
Yep and it is annoying as can be.........seemed to go away after I updated.....
unsane said:
Yep and it is annoying as can be.........seemed to go away after I updated.....
Click to expand...
Click to collapse
I have the newest update installed. I would rather not reinstall but it seems like it's my only choice. #Sadguy
I updated and still have the problem. sucks!
this was covered in another thread.. I can't recall where but the fix for this is related to the in pocket lock setting...
go into menu > settings > display
disable 'in pocket' detection..
reboot your phone..
after reboot, you may enable it again if you use that feature or leave it off.
PROFIT !!
I take no credit for this fix. I don't remember who discovered it but I'm sharing it because it bothered me after the update as well.
If this works/helps, remember to hit that magic thanks button
I've tried that and it doesn't work...only thing so far that works is a reboot
Sent from my MoPho using XDA Premium.
daddymikey1975 said:
this was covered in another thread.. I can't recall where but the fix for this is related to the in pocket lock setting...
go into menu > settings > display
disable 'in pocket' detection..
reboot your phone..
after reboot, you may enable it again if you use that feature or leave it off.
PROFIT !!
I take no credit for this fix. I don't remember who discovered it but I'm sharing it because it bothered me after the update as well.
If this works/helps, remember to hit that magic thanks button
Click to expand...
Click to collapse
I've tried this myself too. Did not fix the problem
I would like to see a thread that shows all the issues we have and potential fixes. This is one that needs attention.
Sent from my SPH-P100 using xda premium
yup mine doesnt work properly either. ALso the ear speaker doesnt work ( i think its broken cuz it makes a funny noise
You guys may have hardware issues too, go swap your devices and see if it helps.
Sent phrom my Mo-Pho
This may sound crazy but mine does this only at work??? When I'm at home its fine. So I'm not so sure its hardware as opposed to radio or software. IDK?
xxxicu812 said:
This may sound crazy but mine does this only at work??? When I'm at home its fine. So I'm not so sure its hardware as opposed to radio or software. IDK?
Click to expand...
Click to collapse
Thats a weird one... Try a factory reset
Sent phrom my Mo-Pho
This isn't a device/hardware issue either. Something causes the sensor to shut off or fail. I feel this is software related.
Sent from my MoPho using XDA Premium.
I downloaded androsensor from the market, and you're right the prox sensor just stops responding... Says waiting for event, and after a reboot it gives an output of 1.2 our 39.4 inches.... Not sure what the prob is. I read on another forum that out may have something to do with rooting the phone, but I don't adhere with this. Are you guys with the problem rooted?
Sent from my MB855 using xda premium
had the same problem. turning off "in-pocket detection" worked for me.
Just to confirm. Once I disabled the in pocket feature the proximity sensor works just fine.
Once you disable the in pocket feature you will need to power off your phone than re power it up and it should be fine.
anoroc44 said:
Just to confirm. Once I disabled the in pocket feature the proximity sensor works just fine.
Once you disable the in pocket feature you will need to power off your phone than re power it up and it should be fine.
Click to expand...
Click to collapse
I have tried multiple roms (Homebase, Star Wars, and stock) and it still malfunctions. definitely seems like a hardware issue.
flawlessbmxr said:
Anyone else having issues with the proximity sensor not working when on a call? Screen stays on for me when its against my ear. I'm also rooted with Alien rom and Knightwolf's themes.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
yea was really annoying.....but it went away after updating the phone
Anyone still having the problem? I am. Im on the latest OTA and did a hard reset via recovery. Moto forums seem to think it has something to do with Bluetooth. Is it a known hardware issue? Resetting the phone always fixes it.
Ya mine does that too....i never ever use blue tooth so that cant be the only issue..bluetooth is off
On the latest update. 6 or whatever was just released the other day ..i manually pushed it with rsdlite
We will see if that fixed it
Sent from my MB855 using XDA App
So I got my phone almost two weeks ago when It got released.. Basically it's amazing and everything works fine except that when I play Temple run or Magic Piano these two games that I tried out are so good and they run smoothly but the speaker gives me cracked sounds like I can't hear smooth sound coming out from the speaker without cracking up I tried to use a headphone and restart my phone, hard reset and it's still the same. I don't know why I get this issue I saw few people they were saying that temple run and magic piano works so fine with them. Not sure if it's a hardware issue.
---
My device also heats a lot when using it, like playing a game or just browsing and listening to songs nothing that uses lot's of graphics or anything but I get lot's of overheating issues. Could it also be a battery issue or that's normal?
I'll be taking it to service tonight to check it up It's so unusual and I don't like how it's really bad although it's a new phone and I don't use it a lot.
Thanks
Yes from what you have mentioned, it looks like you have a defective unit and they can replace the device. The behavior is not normal.
same problem
i recently bought the s3 and im having the same problem.. apart from this the phone screen tends to be a bit yellow when im using whats app.. what did the samsung guy say to when you took the phone to the service station??
Same again...
Snap. I've had my Galaxy S3 since last Saturday and have exactly the same issue. So far it seems to affect Temple Run, Mass Effect Infiltrator, Magic Piano and Real Racing 2. All of them have crackled, distorted sound that makes them near unplayable with the sound turned on.
Bizzarely this is the only thread I can find that even mentions the issue! Please can you let us know what Samsung's feedback is?
temple run with and without headphones gives perfect sound for me
solved... or not?
try doing a factory data reset.. it worked for me.. but someone i spoke to said that the problem came back after a while.. after he installed a launcher... i dont know if using a launcher causes this problem but as of now.. running stock touch wiz... both temple run and magic piano work fine..
Hey guys..I have a brand new s3 and it is also exhibiting the same issues with temple run. The sound shutters ( would appreciate if anyone found a fix to this.. I have a galaxy s3 white international version.
+1
3 weeks old S3. Cracking noises when I used the speaker during phone calls.
When other party speaks => clear
When I speak => crack, crack, crack especially the first few words
Tried setting call quality, no improvement. Not sure if this is a hardware issue?
I had the same issue, but aparently this had something to do with one of the updates. Yesterday's update solved this issue.
Temple run runs without any issue.smooth.will be checking other games too after downloading
Sent from my GT-I9300 using xda premium
No problems here! No heat, or crack in sound?, my phone stock no root
Sent from my GT-I9300 using xda premium
not facing a single problem what you had mentioned ..everything is working fine..battery gives me 7-8hours backup on the screen ... no heating problem.........no sound problem...hmmm...i think i'm lucky here lol
Cracking sound while playing game...
Guybrush86 said:
Snap. I've had my Galaxy S3 since last Saturday and have exactly the same issue. So far it seems to affect Temple Run, Mass Effect Infiltrator, Magic Piano and Real Racing 2. All of them have crackled, distorted sound that makes them near unplayable with the sound turned on.
Bizzarely this is the only thread I can find that even mentions the issue! Please can you let us know what Samsung's feedback is?
Click to expand...
Click to collapse
Well guyz even I was facing the same problem but I finally figured out whats the exact issue...All u need to do is go to settings ----> Sound ----> Disable Auto Heptic or click on auto heptic ----> Mark the application you want it to be disabled for.
Well one more thing...Its is turned off by default so if you will reset your phone it will work ....I happened to turn it on accidentally without knowing whats exactly it is and I am sure that most of you must have did the same thing....!!!!
Galaxy S3 ROCKZ
iZnoGouD.123 said:
Well guyz even I was facing the same problem but I finally figured out whats the exact issue...All u need to do is go to settings ----> Sound ----> Disable Auto Heptic or click on auto heptic ----> Mark the application you want it to be disabled for.
Well one more thing...Its is turned off by default so if you will reset your phone it will work ....I happened to turn it on accidentally without knowing whats exactly it is and I am sure that most of you must have did the same thing....!!!!
Galaxy S3 ROCKZ
Click to expand...
Click to collapse
Good for you. My heptic feedback is always off. Still have speaker cracking.
Just did a factory reset. Have to monitor and see if it solves the problem.
Guybrush86 said:
So far it seems to affect Temple Run, Mass Effect Infiltrator, Magic Piano and Real Racing 2. All of them have crackled, distorted sound that makes them near unplayable with the sound turned on.
Click to expand...
Click to collapse
I'm getting the exact same issue with the games above...haven't seen the issue arise with any other apps so I'm not too worried however it would be great if a fix was found
Edit: Just tried turning off auto haptic in sound settings and strangely enough this actually fixes this problem for me :s
It's a common fault, return the unit and get a new one.
Gob done.
Home buttom lag , Home button lag , Home button lag & again home button lag
Sent from my GT-I9300 using Tapatalk 2
princealitanha said:
Home buttom lag , Home button lag , Home button lag & again home button lag
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
To fix that, you have to open S-Voice> Settings> uncheck Launch S-Voice by double tapping home button
Thanks everybody. I had the problems with home button lag and temple run and the fixes described here worked perfectly.
iZnoGouD.123 said:
Well guyz even I was facing the same problem but I finally figured out whats the exact issue...All u need to do is go to settings ----> Sound ----> Disable Auto Heptic or click on auto heptic ----> Mark the application you want it to be disabled for.
Click to expand...
Click to collapse
This worked for me, thanks.
Hi everyone, i'm using CM9 ROM and i'm facing a problem with proximity sensor...
When in a call, the screen don't turn off and then it gets locked...
To end the call I have to unlock the screen and tap on end button...
Does anybody have the same issue?
I love CM9 ROM, but I always have to change to stock (since this is not the first or second time I see this), this bug really piss me off
Tried many kernels but the problem persist
If someone knows a way to fix that would be GREAT!
Thanks.
I dont have those problem.Currently im using cm9 fxp211 and kernel
Sent from my SK17i using xda app-developers app
Well, every time I flash CM9 i get this thing...
It's weird, cos I've never seen someone with this problem =/
I'll search for a fix... No succes till now...
Maybe there is a way to calibrate, I just need to learn how!
Thank you
*#*#SERVICE#*#* and service test your proximity to check whether it is working properly or not
Sent from my LT28h using xda premium
I dont have those problem too. Maybe sensor crash?
Tried to test everything and realized that even auto brightness is working...
Don't know what is happening here...
Tried to disable auto brightness to see if was some kind of conflict... Still the same