Good Day, I'm hoping someone can help me, I've tried searching but I can't seem to find anything(mainly because I don't know the best way to describe it) sometimes, randomly the screen will turn off, as it should but then it wont come back on, I've installed the wake on volume mod and that doesn't seem to help.
Happened with CM7 and now with The darkside rom.
It's sporatic, it wont do it for like 10 hours then will do it 3 times in an hour.
Any help would be greatly appreciated
Thanks
Adam
Gweilo said:
Good Day, I'm hoping someone can help me, I've tried searching but I can't seem to find anything(mainly because I don't know the best way to describe it) sometimes, randomly the screen will turn off, as it should but then it wont come back on, I've installed the wake on volume mod and that doesn't seem to help.
Happened with CM7 and now with The darkside rom.
It's sporatic, it wont do it for like 10 hours then will do it 3 times in an hour.
Any help would be greatly appreciated
Thanks
Adam
Click to expand...
Click to collapse
I have a similar problem. But mine only happens when i make or recieve a call, doesn't do it everytime. I actually found a thread where it said it was possibly a broken proximity sensor. So the solution was to download 2 things from the app store and install them, and disable the proximity sensor. I am going to try that, cause when i make or recieve a call I actually turn my screen off so i won't hang up on anyone or hit several buttons. The solution they gave was to have a rooted phone, and download "android sensor box" so you can see the name of your proximity sensor, and then download "hardware disabler". Find the name of your proximity sensor and disable it. I have tried everything else, so what do I have to lose on trying this, lol.
Update, after several days i've found the culprit. There was an issue with my sd card, once I swapped it out haven't had a problem since
Sent from my MB860 using xda app-developers app
Related
Hey guys I searched, but couldn't find anyone with the same issue, so hopefully someone could help me. My touch pro is Sprint (Don't know if it makes a difference), but I can not answer any of my calls being hardware buttons or screen, nothing works. I've been using s2u2 and never had a problem, but I uninstalled it thinking there may have been an issue, but no, still happening. Sometimes if i hit either the hardware or software key a bunch of time it will answer, but only like every 1 out of every 10 times. Also I've been calling myself to check and the call will only come through 1 out of 10 times. Any ideas what could be causing this?
officer629 said:
Hey guys I searched, but couldn't find anyone with the same issue, so hopefully someone could help me. My touch pro is Sprint (Don't know if it makes a difference), but I can not answer any of my calls being hardware buttons or screen, nothing works. I've been using s2u2 and never had a problem, but I uninstalled it thinking there may have been an issue, but no, still happening. Sometimes if i hit either the hardware or software key a bunch of time it will answer, but only like every 1 out of every 10 times. Also I've been calling myself to check and the call will only come through 1 out of 10 times. Any ideas what could be causing this?
Click to expand...
Click to collapse
If your out of options try a hard reset. That should fix it.
hello
cforster said:
If your out of options try a hard reset. That should fix it.
Click to expand...
Click to collapse
I agree. go to settings, clear storage and type in 1234
phone will reset to factory
Can't Answer Calls
Before you do a hard reset, I recommend that you read this thread on ppcgeeks http://forum.ppcgeeks.com/showthread.php?t=40427 , it took a a couple of weeks to figure this out, but it worked for me.
Good Luck.
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!!!
I am running AOKP ver 35.1 I have noticed that my phone doesn't vibrate anymore. and I'm not sure when I lost it. I have been all over in the settings it is set to vibrate. somewhere I think I seen that it was broken in ICS any ideas for me?
Thanks
bthelin said:
I am running AOKP ver 35.1 I have noticed that my phone doesn't vibrate anymore. and I'm not sure when I lost it. I have been all over in the settings it is set to vibrate. somewhere I think I seen that it was broken in ICS any ideas for me?
Thanks
Click to expand...
Click to collapse
My vibrate is working on 35.1. It could possibly be a bad download or maybe your vibrate motor just wore out. ( it is one of the few moving parts in our phone)
You could try redownloading/ reflash and if that doesn't work, I would return to stock eh03 to see if it functions at all.
Sent from my SCH-I500 using XDA
so i thought i was having that issue till i hit the call button, went into dialer settings and enabled vibrate from there. try it out
I honestly had sort of the dame issue twice. I would get a weak weird vibrate instead and when I reset the phone it was fine again. It us probably due to the age of the phones is my best guess.
Sent from my SCH-I500 using Tapatalk
Hello Everyone.
Wonder if anyone can help me as I think I am going mad!
I use my headset all day (listening to podcasts) and whenever i answer a call, I have to remain very still for fear i will hang up (which happens regularly).
I have had the same problem on many roms - Omega, Temasek, Cyanogenmod, Foxhound and many more, its driving me crazy.
I have also installed proximity service and an app which I cant remember the name of at the moment, but will update when i find out. Needless to say, nothing has worked, the screen always comes on when a call comes in.
Does anyone have any idea what i can do to sort this, i never need my screen on when my phone is in my pocket.
PS I have tasker, maybe i can use that to sort it?
Thanks for any input
JimmyMagic said:
Hello Everyone.
Wonder if anyone can help me as I think I am going mad!
I use my headset all day (listening to podcasts) and whenever i answer a call, I have to remain very still for fear i will hang up (which happens regularly).
I have had the same problem on many roms - Omega, Temasek, Cyanogenmod, Foxhound and many more, its driving me crazy.
I have also installed proximity service and an app which I cant remember the name of at the moment, but will update when i find out. Needless to say, nothing has worked, the screen always comes on when a call comes in.
Does anyone have any idea what i can do to sort this, i never need my screen on when my phone is in my pocket.
PS I have tasker, maybe i can use that to sort it?
Thanks for any input
Click to expand...
Click to collapse
Try Gravity box-power settings-the last two options
Anyone else experiencing this? Less than 10 seconds after I fingerprint unlock, sometimes the screen will go black while I'm reading a message or whatever. Other times it seems to be triggered by a touch action, like pressing on an icon or clearing a notification.
I found no setting that explains it. Screen timeout is set to 1 minute. I don't have any third party lockscreen or display related apps. It's been happening for as long as I can remember with this phone, and I thought the January update might fix it but it persisted through. Faulty proximity sensor maybe? I'm starting to contemplate warranty servicing.
Glaux said:
Anyone else experiencing this? Less than 10 seconds after I fingerprint unlock, sometimes the screen will go black while I'm reading a message or whatever. Other times it seems to be triggered by a touch action, like pressing on an icon or clearing a notification.
I found no setting that explains it. Screen timeout is set to 1 minute. I don't have any third party lockscreen or display related apps. It's been happening for as long as I can remember with this phone, and I thought the January update might fix it but it persisted through. Faulty proximity sensor maybe? I'm starting to contemplate warranty servicing.
Click to expand...
Click to collapse
I think it's A12. On the P5 you could look at the device and it would stay on when doing something. The feature, although there is a setting on/off, does not work any longer. I never had it on the P6 shipped with A12 but on the P5 my wife has the same problems since updating. So perhaps a proximity update will fix it but if all else is working the replacement will almost guaranteed be worse.
Glaux said:
Anyone else experiencing this? Less than 10 seconds after I fingerprint unlock, sometimes the screen will go black while I'm reading a message or whatever. Other times it seems to be triggered by a touch action, like pressing on an icon or clearing a notification.
I found no setting that explains it. Screen timeout is set to 1 minute. I don't have any third party lockscreen or display related apps. It's been happening for as long as I can remember with this phone, and I thought the January update might fix it but it persisted through. Faulty proximity sensor maybe? I'm starting to contemplate warranty servicing.
Click to expand...
Click to collapse
Are you using a custom kernel or have had a custom kernel installed in the past?
If so, you will need to try a factory reset and complete full stock image.
bobby janow said:
I think it's A12. On the P5 you could look at the device and it would stay on when doing something. The feature, although there is a setting on/off, does not work any longer. I never had it on the P6 shipped with A12 but on the P5 my wife has the same problems since updating. So perhaps a proximity update will fix it but if all else is working the replacement will almost guaranteed be worse.
Click to expand...
Click to collapse
I saw that setting but I don't see how it's relevant. Even without that setting, the display should not turn off on its own before 1 minute of inactivity.
vandyman said:
Are you using a custom kernel or have had a custom kernel installed in the past?
If so, you will need to try a factory reset and complete full stock image.
Click to expand...
Click to collapse
No. I didn't do any modding beyond bootloader unlock and root with Magisk. I flashed the January factory image a few days ago and rerooted, but as I said the problem started long before that.
Glaux said:
I saw that setting but I don't see how it's relevant. Even without that setting, the display should not turn off on its own before 1 minute of inactivity.
No. I didn't do any modding beyond bootloader unlock and root with Magisk. I flashed the January factory image a few days ago and rerooted, but as I said the problem started long before that.
Click to expand...
Click to collapse
I didn't realize you were rooted, I usually don't read signatures. Have you unrooted and tested? Other than that I'm not rooted so perhaps someone can help you out. Maybe change the title of the thread so rooted folks will jump in with suggestions. Good luck.
Looks like the issue might have come from the launcher I use, Smart Launcher. Specifically a setting called "Smart Screen Off" that's not working as intended. I turned that off and so far I can't reproduce the issue.