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 bought a Streak 5 off eBay and it reboots constantly whenever I try using the GPS. It doesn't take it more than a few seconds before it does. At first I thought it would be just a ROM issue, and since I was not using GPS I didn't bother. Now I upgraded to DSC and the problem remains. Could somebody please help?
Thanks!
its just because the dell streak 5 you have does not have the correct baseband flashed....
i had same problem
well in the beginning i dint like my landscape lock-screen so i updated to portrait and after that the navigation keep shutting off and some times if navigation is running then it wont show GPS signal on the stat. bar...so i wiped everything out(factory reset) fix permissions and IT FIXED THE PROBLEM...
BTW i m running 2.3.3 longhorn 2.2v4 ROM....let us kno
many sfsf
This may sound strange... but... I "fixed" it by having the battery removed since I posted the question. It's working without issues *now*.
Could somebody please try to explain what has happened here?
BTW... I took the "idea" from:
(Can't provide a link due to stooooopid limitations for "new" users. The link pointed to mydellmini dot com)
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?
Hey guys!
I've already posted my problem in the Nexus 4 Q/A-Forum.. till now without help. Well i thought that maybe here is a good place to get help, too!
So whats my problem.. Yesterday i flashed a new update of Xylon-Rom (clean flash) on my Nexus 4. Installed and restored all Apps. Usually I use Swiftkey 4 as keyboard, so I set up everything like all the times before. The last times everything works fine, but this time not. I set up SK as my standard keyboard and began to write. After a while I wanted to write again, but suddenly there was the AOSP keyboard. Changed back to SK. But after some moments it happend again. So everytime when there is a text input AOSP appears.. I change back to SK then, but after turning screen on some minutes later AOSP again.
As it would be not enough, the same thing is happening since yesterday on my gf phone (HTC One S, also rooted with Carbon Rom). Like on my phone, it never happenend before.
What I've done till now? Erased App-Data of both keyboards, disabled AOSP keyboard. Everything without success.
Dont know why it happens now... I often flash other Roms, Updates etc and I use Swiftkey for a long time. Restoring with Titanium works everytime. And this time i haven't done any other thing on Restoring.
I hope u understand my problem (my english isn't the best ) and anyone could help me!?
Thanks so far.
Cls
Tried to freeze the AOSP in Titanium -> no effect
Set Swiftkey as System-App -> no effect
:X
I was encountering this with swipe keyboard previously, and my solution was to use swiftkey.
Sent from my Nexus 7 using Tapatalk 4 Beta
same thing
im suffering from this problem too.. no solution yet :3
Hey everyone-I need some help. I am not new to android or even this forum (I forgot my user name from a previous account so I created a new one). Anyways, I can't post in ChameleonOs's topic so I figured i'd try my luck here. I had put v .8 on my phone and played with it for a while. Very nice rom and layout but when I try to turn Bluetooth on via just hitting the button in the drop down or even in settings it just will not turn on. I watch it turn itself back off. The Bluetooth icon won't even show up at the top, I'll flick it on, it'll flick itself right off almost instantly.
Anyone know of any solution. I know it's a work in progress rom but I thought it had worked the last time I flashed it but I was trying other roms out too (CM 10.2 nightlies for example) but it just doesn't work on my phone at least. I switched back to the nightlies because I stream music to my car and Bluetooth is very important to me because I love music.
Reason I like ChameleonOS is because of the theme manager they have within the rom, well and the messaging app is pretty slick too. Hope someone can help me out..I seen Trekken was stopping development for the time being (hate to hear but totally understand). Thanks in advance!
He's still working on it as of 2 minutes ago when I was talking to him in hangouts. :good:
Dubbsy said:
He's still working on it as of 2 minutes ago when I was talking to him in hangouts. :good:
Click to expand...
Click to collapse
Ok cool, I didn't know if it had worked or not but thank you so very much for the update. I'll keep an eye on that thread for further updates or if you hear of anything first I'll check this one out too.
So I noticed he had uploaded an updated rom on his thread. I flashed that and I still have bluetooth shutting itself off. I noticed someone had said their Wifi don't work but mine does. I don't know if it is my phone personally. I am running baseband MDK and everything seems to be correct in the about phone section...just driving me nuts that bluetooth acting weird. Maybe I missed something? I love this rom just can't figure out what is going on