I have been using my S2 since the beginning of February 2012 and have not noticed at any time other than when making calls that the proximity sensor was activated (dull red glow). Just last night I noticed that the sensor seems to be activated all the time now, screen on, calling, whatever...
It of course turns off when the S2 is turned off. When booting back up it does not get enabled again until the end of media scanning.
Any ideas how to check which app or process is enabling this when it is not necessary nor wanted?
Shameless bump. Surely somebody has an idea what variable is involved or what program I can use to change the behavior?
Try after a fresh install with full wipe if it happens
Sent from my GT-I9100 using Tapatalk 2 Beta-5
Well I don't know why, but the sensor has stopped running continuously without any intervention. Thanks for the reply.
I had a similar problem and I found out it was an app causing that - viber.
Probably it was the same with you.
NunxPT said:
I had a similar problem and I found out it was an app causing that - viber.
Probably it was the same with you.
Click to expand...
Click to collapse
Thanks! I had the same problem , and it was indeed Viber.
Btw , did you managed to fix it ?
ZVictor said:
Thanks! I had the same problem , and it was indeed Viber.
Btw , did you managed to fix it ?
Click to expand...
Click to collapse
New viber update today and the issue is fixed
Viber was the problem for me too
Related
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
Hello,
I bought recently the new SGS3 and after a week or two of using I noticed the phone loses all the sounds despite all of them are turned on and not being on minimum. After a while the sounds get back and everything works fine. At first I thought it might be from the settings because I set up silent mode for all notifications and I thought it may turn all the sounds off, despite it normally shouldn't. After playing for a while with the phone I realized the issue appears randomly without any reasons while I was playing game or simply navigating through the phone. If anyone had experienced the same issue or have an idea what could be the problem (software, hardware, settings, OS, etc) or how it can be solved, please respond. Any answer is appreciated as the problem is quite annoying as I'm missing calls because of it.
Thank you.
Phone details:
Samsung Galaxy S III
Android version - 4.0.4
Baseband version - I9300BOLF1
Kernel version - 3.0.15-782020
Build number - IMM76D.I9300XXBLFB
P.S. Restart of the phone doesn't help as I already tried it. The issues is related to all the sounds not to the vibration, the last works fine.
Backup data and factory reset.
Sent from my GT-I9300 using xda premium
JJEgan said:
Backup data and factory reset.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thank you for your advise JJEgan, unfortunately it didn't help neither. Yesterday I did the factory reset and left it as it is, didn't restore any of my previous settings or apps, didn't install anything additional, just wanted to see if the problem will appear again, and unfortunately it did.
Anything else I can try or I should take it to a service?
Thank you
I have the same problem with notification sounds. The problem appears when i turn off notifications on apk like im+ or Yahoo messenger. Is there any other solution rather than factory rest?
Sent from my GT-I9300
mausxda said:
I have the same problem with notification sounds. The problem appears when i turn off notifications on apk like im+ or Yahoo messenger. Is there any other solution rather than factory rest?
Sent from my GT-I9300
Click to expand...
Click to collapse
maybe there is some loose..should send back to samsung
It happened to last night. I restored the phone using CWM and now is back to normal.
I've had this problem with my Xperia Z2 since I've owned it. I've had firmware 402 and now 314 and it's still the same.
The problem is that when I'm in a call, the proximity sensor works and turns the screen off but the digitizer does not turn off! So while I'm talking and pressing my face against the phone it detects input and sometimes I even hangup on people.
Anyone else experience this issue or have any suggestions on how to troubleshoot this?
Hi. I had the same problem. So I installed an app called "call screen lock". That solved it for me.
gork1975 said:
Hi. I had the same problem. So I installed an app called "call screen lock". That solved it for me.
Click to expand...
Click to collapse
Thanks but I don't think I should have to download another app to fix a bug.
ZPaul2Fresh8 said:
Thanks but I don't think I should have to download another app to fix a bug.
Click to expand...
Click to collapse
You can use the work around until it is fixed or suffer the bug. Why not complain to Sony?
Hi, I got my Mi 3 this week. I noticed some weird behavior from my magnetometer and Accelerometer, wondering if anybody else is experiencing the same. After a day of use, sensors go haywire and suddenly stop reporting data. Can't use compass and my auto rotate stops working. I tried different apps to see if it's a global problem or just a not compatible app, so far when sensors go blank, the effect is global. Even the Mi self test is not reading anything from the sensors. Pedometer is on the other hand operational tho.
Things come back to normal after a restart. I suspect it must be a software bug maybe?
sherlock.holmes said:
Hi, I got my Mi 3 this week. I noticed some weird behavior from my magnetometer and Accelerometer, wondering if anybody else is experiencing the same. After a day of use, sensors go haywire and suddenly stop reporting data. Can't use compass and my auto rotate stops working. I tried different apps to see if it's a global problem or just a not compatible app, so far when sensors go blank, the effect is global. Even the Mi self test is not reading anything from the sensors. Pedometer is on the other hand operational tho.
Click to expand...
Click to collapse
My sensors are working but they are wrongly calibrated :/ and pedometer isn't working! I thought the pedometer was disactivated by default...
greenpays said:
My sensors are working but they are wrongly calibrated :/ and pedometer isn't working! I thought the pedometer was disactivated by default...
Click to expand...
Click to collapse
Dial *#*#6484#*#* it's the built-in test. U can recalibrate your accelerometer there and also test the device. Use power button to exit. And for +-45 test's of the accelerometer tilt your device on it's corners.
sherlock.holmes said:
Dial *#*#6484#*#* it's the built-in test. U can recalibrate your accelerometer there and also test the device. Use power button to exit. And for +-45 test's of the accelerometer tilt your device on it's corners.
Click to expand...
Click to collapse
Thanks for the tip it works perfectly!
By the way, you are using European firmware or Global, because for me the pedometer isn't counting the steps :/
greenpays said:
Thanks for the tip it works perfectly!
By the way, you are using European firmware or Global, because for me the pedometer isn't counting the steps :/
Click to expand...
Click to collapse
I'm glad to hear it worked for you. My pedometer comes and goes... Not reliable unfortunately. btw how can I check my ROM region? Got the October patch, It doesn't solve the bug...
I also have problems with my vibrator. It doesn't react to short vibrations (that much I can make out of it).
sherlock.holmes said:
I'm glad to hear it worked for you. My pedometer comes and goes... Not reliable unfortunately. btw how can I check my ROM region? Got the October patch, It doesn't solve the bug...
I also have problems with my vibrator. It doesn't react to short vibrations (that much I can make out of it).
Click to expand...
Click to collapse
Well I seem to have the global version. MIXM
I hope they get problems solved fast.
If anybody else with the device is reading this post, can you please check your sensors with an appropriate app and see if yours is also malfunctioning randomly?
I had this problem, but I just restarted the device and everything came back normal
braulio_holtz said:
I had this problem, but I just restarted the device and everything came back normal
Click to expand...
Click to collapse
Yes! It goes away with restarting (and sometimes doesn't!!!)
But it's just a temporary fix, in matter of hours, you r back to the square one.
sherlock.holmes said:
I'm glad to hear it worked for you. My pedometer comes and goes... Not reliable unfortunately. btw how can I check my ROM region? Got the October patch, It doesn't solve the bug...
I also have problems with my vibrator. It doesn't react to short vibrations (that much I can make out of it).
Click to expand...
Click to collapse
Go to Accessibility settings and turn on Touch Vibration. Keeping it off also hinders the in call volume function. Hope it helps
Arkapravoarka said:
Go to Accessibility settings and turn on Touch Vibration. Keeping it off also hinders the in call volume function. Hope it helps
Click to expand...
Click to collapse
Well yeah, it did work actually. But the thing is, I don't like to have the touch vibrations on always, I just want it to work with G-board and some other apps that use short vibrations as a feedback...
It's like the touch vibrations setting, controls everything lol.
It's definitely a bug they have to get fixed.
So it turns out the sensor problem that I reported is being caused by the G-cam port I had installed. The solution is to close the app (in the multitasking menu !?) Whenever you are done using it.
Flash the stock rom again and your problem will be solved for sure, also faced the same issue.
I have same issue and flash stock rom but still not working how can i fix it ?
I also have a problem with compass apps. north and south are correct shown, west and east are not correct.
Stefan_1 said:
I also have a problem with compass apps. north and south are correct shown, west and east are not correct.
Click to expand...
Click to collapse
I use this solution and it worked.
https://forum.xda-developers.com/showpost.php?p=82161897&postcount=4
My Mi A3 has just got an system update of android 10. Just after that, my camera isn't working. Please help me out of this problem.
Chaitanya123 said:
My Mi A3 has just got an system update of android 10. Just after that, my camera isn't working. Please help me out of this problem.
Click to expand...
Click to collapse
Did you try wiping data and cache for camera app?