hello everyone
after much debugging of this problem, I think it has to do with battery saving option in the ROM/Kernel.
while having a voip call using sipdroid or magicjack, the proximity sensor turns off the screen and causes the sound to cut off completely. i think the mic still works because i was able to record a voice message while the screen is turned off by the sensor. this also means the wifi signal was still on.
sipdroid has the option to keep screen on during a call. this options works very well. the screen dims but does not turn off completely. on the other hand, magicjack does not have such an option.
why i think it is a battery saving issue is because while the phone is plugged in to wall or laptop, proximity sensor does turn off the screen but the audio is not cut off and everything works just fine.
anybody knows a fix or a workaround for this issue?
the problem is the same on cyanogenmod, MIUI, and Team DIRT. i think i had the same problem when i was using ICS before i switched to jellybean.
thanks
Have you tried the "keep proximity sensor on" setting in the call menu? make sure it's unchecked. Was just asking because you didn't mention it in your post.
Roxxas049 said:
Have you tried the "keep proximity sensor on" setting in the call menu? make sure it's unchecked. Was just asking because you didn't mention it in your post.
Click to expand...
Click to collapse
yes. it is unchecked. however, magicjack uses its own dialing app. sipdroid is fine because it has the option to disable proximity sensor.
but more importantly, is this a normal behavior? shouldn't i be able to turn off the screen via proximity sensor and still be able to chat? maybe graphics and audio processes are in conflict when the proximity sensor is activated.
hmnxyz said:
yes. it is unchecked. however, magicjack uses its own dialing app. sipdroid is fine because it has the option to disable proximity sensor.
but more importantly, is this a normal behavior? shouldn't i be able to turn off the screen via proximity sensor and still be able to chat? maybe graphics and audio processes are in conflict when the proximity sensor is activated.
Click to expand...
Click to collapse
i should say, this only happens when the phone is unplugged. i.e. running on battery. i dont know what it is trying to do. maybe save battery. how can i access such settings?
also, i use sipdroid with another voip number. magicjack has its own number and its own dialing app.
I am back to ICS and everything works fine. maybe this problem will go away when htc releases an official jeally bean rom.
hmnxyz said:
I am back to ICS and everything works fine. maybe this problem will go away when htc releases an official jeally bean rom.
Click to expand...
Click to collapse
actually, the only ICS rom that worked flawlessly is the stock rom. i ended up flashing a rooted stock rom. the problem is gone. finally.
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!!!
Hi guys. I have a peculiar problem in my new Galaxy S3. Whenever I make a call, the screen remains on even though I have ticked the 'Auto screen off during calls' option in call settings. Also, whenever I input any numbers while in a call, the keypad does not hide. I mean I get the 'Hide' option but it doesn't do anything and the keypad stays on the display. Can anyone tell me if this is a known issue or am I the only one facing it? Is there any workaround this? I am on stock firmware (XXLF2) and haven't even rooted my phone yet. Please help me guys!
I have exactly the same problem. I know the proximity sensor works, because I tried the proximity sensor test app. But my phone does not turn off screen when in call.
i have same problem any one help us ?
I also have this problem.. and to make it worse, I can't seem to call out occasionally. I swipe to call, but nothing happens. I can't even dial out at times.. rebooting usually solves the issue, but the problem quickly comes back.
I'm not rooted, on stock rom. Anyone know what the issue is?
OK, it looks like for me, it was a conflict between Google Voice and the phone. Turning it off/disabling it fixes the problems I've been having. I'll have to see what exactly is causing the conflict, but at least everything works with it off.
BlueG2 said:
OK, it looks like for me, it was a conflict between Google Voice and the phone. Turning it off/disabling it fixes the problems I've been having. I'll have to see what exactly is causing the conflict, but at least everything works with it off.
Click to expand...
Click to collapse
Where exactly is the option for turning off Google Voice?
I looked in Applications All but couldn't find it.
Beards said:
Where exactly is the option for turning off Google Voice?
I looked in Applications All but couldn't find it.
Click to expand...
Click to collapse
Check under 'Voice', not Google voice. It's also an option on the Voice widget.
If that doesn't fix it, try rebooting and doing it again.
BlueG2 said:
Check under 'Voice', not Google voice. It's also an option on the Voice widget.
If that doesn't fix it, try rebooting and doing it again.
Click to expand...
Click to collapse
'Voice' was my search pattern. It's got to be there I'll find it.
Hi guys,
Did you find a solution to this problem yet? I have the same problem, and no matter what I do, I can not make it work. The screen is always on during a call. I am using the stock rom, without root, as it is.
------------
Nevermind. I fixed it by removing FSC ID, apparently it was interfering.
i had the same problem but it was fixed after i made a phone restart.
I have the same problem...
Hey guys,
I know this thread already exists in this forum but has come to an end with no solution and since its kinda very important to sort this issue to be able to use my phone I thought ill start fresh for some input from the experts.
I have a Galaxy S2 I9100 rooted with a custom ROM(slim ICS 4.1 when the issue started) and it started randomly freezing when unlocking the screen and normal use .but since last week it wouldnt let me make or receive calls as the phone freezes and reboots 10-20 secs into the call..i updated to 4.2 with the hope of resolving this but tht didnt work..I have changed kernels and ROMS(resurrection, cm9 release build)..though the dialer did work for calls on resurrection ROM the proxomity sensor wouldnt work..
so i tried going back to stock sammy ICS (XXLPH) and then the dialer would work but again without the proximity sensor and the samsung tests also confirmed that the sensor wasnt registering...
am rooted now and back to slim 4.2(dont like the look of sammy) with siyah kernel 3.2.2...the dialer and proximity sensor don work..the rest of it is all fine..
Ive done all the wipes each time ive installed a new ROM...also done kernel wipes before installing Kernels..
I think its not a ROM/hardware problem but well it could be but hope to get it sorted through the normal techniques..I cant return my phone for repairs as it was in mint condition bot second hand in UK without warranty papers..
Any help would be highly appreciated..thanks
EDIT: It seems the proximity sensor is to blame for this problem as i found out through other posts..and also i can make and receive calls with the headset/headphones plugged (in which case i assume the phone doesnt try to activate the proximity sensor)..
For now i would like to know how to disable the proximity sensor on the phone..I have tried inserting the gsm.proximity.enable=false in the build.prop editor using the ROM Toolbox lite app n rebooted...but that din seem to work...is there any other way to do this??pls help
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
proximity sensor and screen brightness sensor
3dawg said:
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
Click to expand...
Click to collapse
I havent managed to find a solution as yet..it seems the proximity sensor and the screen brightness sensor(which are on the same PCB i think as per the unassembling video) have a hardware fault and might need repairing..
Some kernels i think maybe bypass using the proximity sensor if its not working..for now I am back to the SLIM 3.2 ICS rom..It doesnt switch off my screen on call and also no auto brightness adjustment but rest all works ok so am using it for now before i get the hardware repaired..
also the resurrection rom v 2.5.1 works fine in the same manner(havent tested many others..CM7 release build doesnt work)..or you can try that script in build.prop to disable the proximity sensor..
check how it goes..
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
proximity sensor and screen brightness sensor
3dawg said:
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
Click to expand...
Click to collapse
I tried checking with the testers for the Slim ROMS..regarding differences in kernel or anything for slim 3.2 and 4.2(3.2 works while 4.2 doesnt) but they couldn't tell me what was the exact problem or the differences that should affect in this case..I haven't tried a CM9 ROM yet but it could work..The kernel for the resurrection ROM is siyah kernel but when i tried that kernel with the slim 4.2 ROM that still didn't work for calls as the phone rebooted.
Have you managed to find a replacement cost for the proximity sensor? also does your screen brightness sensor work?
Hi!
I am having a difficult time in disabling the proximity sensor in Galaxy S II. A few days ago I discovered that it was damaged, but it is probably gonna take a while till I am able to send it to Samsung for repair.
so When I receive a call or someone calls me the screen never comes back and I have to reset it or remove the battery which is pretty annoying.
So I have tried several methods using the Internet.
First there is this option in the caller application which basically disables the proximity sensor when calling. But this is not available in Jelly Bean 4.1. It has been removed...I am not sure why....
Second I tried adding manually in the biuld.prop file the entry
Code:
gsm.proximity.enable=false
After rebooting the phone that did not work either...
Finally I downloaded hardware disabled from the market, ticked the proximity sensor driver, rebooted and that worked fine. However when I do that the CPU remains in very high levels causing the phone to warm up a lot and the battery drain is amazing! So this is not really an option and I disabled that...
So I am wondering if any of u Jelly Bean users have any other ideas to offer cause I am kinda stuck here...
Thank you!
Paladin13 said:
Hi!
I am having a difficult time in disabling the proximity sensor in Galaxy S II. A few days ago I discovered that it was damaged, but it is probably gonna take a while till I am able to send it to Samsung for repair.
so When I receive a call or someone calls me the screen never comes back and I have to reset it or remove the battery which is pretty annoying.
So I have tried several methods using the Internet.
First there is this option in the caller application which basically disables the proximity sensor when calling. But this is not available in Jelly Bean 4.1. It has been removed...I am not sure why....
Second I tried adding manually in the biuld.prop file the entry
Code:
gsm.proximity.enable=false
After rebooting the phone that did not work either...
Finally I downloaded hardware disabled from the market, ticked the proximity sensor driver, rebooted and that worked fine. However when I do that the CPU remains in very high levels causing the phone to warm up a lot and the battery drain is amazing! So this is not really an option and I disabled that...
So I am wondering if any of u Jelly Bean users have any other ideas to offer cause I am kinda stuck here...
Click to expand...
Click to collapse
Wow, thank you, I didn't know this option exists. I am running NeatRom v4 Lite and that option you mentioned is still there. (it is also JellyBean)
Lol got same problem as OP and tried similar things including chmod 0000 to cm3663 folder but no success.
Any ideas?
I have this issue with my S3, that is infuriating! Whenever I get a call and answer it, my screen turns off after a short while and during the call I can't turn it back on. The power and home buttons do nothing, and the proximity sensor isn't working either, so I can't turn off a call.
Anyone know how I can fix this? I have Lollipop, CyanogenMod 12.1 custom ROM installed.
Thank you for your time.
This bug partially exists in stock roms too. It's just magnified in custom roms.
You should be able to set it to keep the screen on during calls. It's the only way i know of.
I fixed this problem by opening up the phone, unplugging the proximity sensor, and throwing it in the bin. (the trash to you Americans)
Screen stays on during calls now, but I've not had problems with accidentally ending calls with my face, so I'm happy.
You also lose your front camera because it's part of the same tiny PCB. But I've never used the front camera on a phone in my life. So my solution is perfect for me, but maybe not for you.
The other option is a software fix. There's an app, or a method that you can do yourself to disable the proximity sensor, but I had problems with it, so did it my way.
Edit: I forgot to mention that the reason my proximity sensor wasn't working was because whoever had this phone before me did a screen repair and had half severed the ribbon cable for the proximity sensor by accident. Not just because of the bug that sometimes exists.
Sent from my GT-I9300 using Tapatalk
Proximity sensor problem. Manually calibrating it solved the issue for me.
http://forum.xda-developers.com/showthread.php?t=2569141
Go to that thread and follow instructions. The code for sensors might be different for s3, Google it.
sashankps said:
Proximity sensor problem. Manually calibrating it solved the issue for me.
http://forum.xda-developers.com/showthread.php?t=2569141
Go to that thread and follow instructions. The code for sensors might be different for s3, Google it.
Click to expand...
Click to collapse
Bah, that's the boring way to fix it.
(didn't work for me. maybe work for OP though)
Sent from my GT-I9300 using Tapatalk
I remember that I saw a MOD or xposed module to keep screen on during call.
It's better than throwing the sensor to the bin (trash ) .