[Q] Proximity Sensor - Motorola Atrix 2

Hi,
I need to know if it's possible disable or recalibrate the proximity sensor of the Atrix 2 because when I make a phone call my screen turn off and I need to push power button to activate de screen and hang up :/.
I'm using JB 4.2.2/CM 10.1
Thanks!

alrojas said:
Hi,
I need to know if it's possible disable or recalibrate the proximity sensor of the Atrix 2 because when I make a phone call my screen turn off and I need to push power button to activate de screen and hang up :/.
I'm using JB 4.2.2/CM 10.1
Thanks!
Click to expand...
Click to collapse
I've noticed this too before, but not since the latest release (4/3/13), could be a coincidence, but if you are on an older build, try updating.

lkrasner said:
I've noticed this too before, but not since the latest release (4/3/13), could be a coincidence, but if you are on an older build, try updating.
Click to expand...
Click to collapse
mmmm, I am using CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com.zip. It is the latest release from this thread: http://forum.xda-developers.com/showthread.php?t=2121029. I'm not sure if it's the same.
Thanks!

alrojas said:
mmmm, I am using CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com.zip. It is the latest release from this thread: http://forum.xda-developers.com/showthread.php?t=2121029. I'm not sure if it's the same.
Thanks!
Click to expand...
Click to collapse
yeah, that is the latest. I'm not sure what the problem is. try a fix permissions in recovery, I haven't been having a problem. also try in different light conditions, as that could be related, as well as any crap that has built up over the sensor (just left of the notification light, you can see it at the right angle)

lkrasner said:
yeah, that is the latest. I'm not sure what the problem is. try a fix permissions in recovery, I haven't been having a problem. also try in different light conditions, as that could be related, as well as any crap that has built up over the sensor (just left of the notification light, you can see it at the right angle)
Click to expand...
Click to collapse
I have this doubt. What it's "more latest" CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com.zip(previously mentioned) or CM10-nightly-NONE_CN-20130412-2102-signed.zip from this thread http://forum.xda-developers.com/showthread.php?t=1869692
I'm sorry if my question is too trivial.
Thanks!

alrojas said:
I have this doubt. What it's "more latest" CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com.zip(previously mentioned) or CM10-nightly-NONE_CN-20130412-2102-signed.zip from this thread http://forum.xda-developers.com/showthread.php?t=1869692
I'm sorry if my question is too trivial.
Thanks!
Click to expand...
Click to collapse
The first one is cm10.1 latest build and second one is cm10 with camera fix

lkrasner said:
yeah, that is the latest. I'm not sure what the problem is. try a fix permissions in recovery, I haven't been having a problem. also try in different light conditions, as that could be related, as well as any crap that has built up over the sensor (just left of the notification light, you can see it at the right angle)
Click to expand...
Click to collapse
mmm and What exactly do Fix Permissions in Recovery?... I just wanna know XD. Anyway It doesn't solve my issue

I would also like info on this because my proximity sensor is broke and always thinks there is an object by the phone, which makes in-call operations impossible...

Related

[Q] Auto-rotate function fail - G-sensor calibration aborted

Hi All. The Screen Auto-rotation has failed on my Sensation. Everything is set to allow it in Settings but no joy.I've tried everything [almost] inc Battery Removal, Disabling Flip-over Speakerphone & Live Wallpapers, and calibrating G-sensor but it always says Calibration Aborted. Anyone got any other ideas?
and116 said:
Hi All. The Screen Auto-rotation has failed on my Sensation. Everything is set to allow it in Settings but no joy.I've tried everything [almost] inc Battery Removal, Disabling Flip-over Speakerphone & Live Wallpapers, and calibrating G-sensor but it always says Calibration Aborted. Anyone got any other ideas?
Click to expand...
Click to collapse
hmm.. maybe there is a hardware fault.. grab the Bubble level app from the market to test: https://market.android.com/details?id=bz.ktk.bubble&feature=search_result
pakraider said:
hmm.. maybe there is a hardware fault.. grab the Bubble level app from the market to test
Click to expand...
Click to collapse
Oh dear. Bubbles not working. That's a hardware fault then?
And how about Elixir2 and its sensor diagnostic utility?
AlexFlexy said:
And how about Elixir2 and its sensor diagnostic utility?
Click to expand...
Click to collapse
Installed it. Nothing is working, except the microphone.
Hardware then?
and116 said:
Hardware then?
Click to expand...
Click to collapse
Hmm... try to re-flash stock ROM (if you have not done this yet). If this does not solve the problem, then the problem is hardware.
AlexFlexy said:
Hmm... try to re-flash stock ROM (if you have not done this yet). If this does not solve the problem, then the problem is hardware.
Click to expand...
Click to collapse
Okay. I'm running Bulletproof at the mo.
Where would I find the stock ROM please?
[I got it in August from Vodafone. Don't remember any branding but it did have all the 360.com bloatware.]
Where would I find the stock ROM please?
Click to expand...
Click to collapse
Ok, try to find it here:
http://forum.xda-developers.com/showthread.php?t=1074559
Thanks. Will report back tomorrow
installed original ROM and it still does not work, so sending it back. Glad it wasn't the Bulletproof ROM's fault! Thanks for your help
G-sensor
Hi. I installed ARHD 5.0.2 on my Sensation 4G. Now auto-rotate doesn't work. It sets screen to horizontal, but it doesn't set screen back to vertical. In other apps sensor works perfect. Calibration didn't help. What should I do?
Help
Hey guys I also got a same problem.
My phone slipped off my hand and fell off and the last time i use it(not rooted), i swear that the g sensor still worked.After that fall, it didn't work, sensor tools didn't detect it help me.

power button broken

hi! after a fall my Desire S have some problems with the power button. Now is still working but I have to push harder every day to unlock the phone!
I thought to remove the original ROM and use something like ICE DS to remap the power button to one of the volume keys. New motherboards for this phone are not cheap and I think this is the better solution. Do you have any suggestions? Is this the better way to solve the problem?
10q
S2w is something I used and it is optional on most if not all current dev ROM. U can basically switch the the phone on or off by swiping from the home softkey to the search key. Install it and experience it for yourself.
FromA100
rain987 said:
S2w is something I used and it is optional on most if not all current dev ROM. U can basically switch the the phone on or off by swiping from the home softkey to the search key. Install it and experience it for yourself.
FromA100
Click to expand...
Click to collapse
thank you, S2w could be interesting. Is it too bad for battery life? I tested a week ago a few programs that unlock the phone using the proximity sensor and they didn't work very well.
neonum6 said:
thank you, S2w could be interesting. Is it too bad for battery life? I tested a week ago a few programs that unlock the phone using the proximity sensor and they didn't work very well.
Click to expand...
Click to collapse
Alternatively you could try screen off and lock from the playstore
"Some things Man was never meant to know. For everything else, there's Google."
jugg1es said:
Alternatively you could try screen off and lock from the playstore
"Some things Man was never meant to know. For everything else, there's Google."
Click to expand...
Click to collapse
Yes I was talking about screen off and lock from the playstore when I've said that I don't like it.
neonum6 said:
Yes I was talking about screen off and lock from the playstore when I've said that I don't like it.
Click to expand...
Click to collapse
Ok, I'm using it instead of s2w, had no problems whatsoever
"Some things Man was never meant to know. For everything else, there's Google."
Try s2w, It's great
jugg1es said:
Alternatively you could try screen off and lock from the playstore
"Some things Man was never meant to know. For everything else, there's Google."
Click to expand...
Click to collapse
totalnoob34 said:
Try s2w, It's great
Click to expand...
Click to collapse
Yesterday I have installed ICE DS 6.5 and it's amazing. This ROM comes with s2w already installed, and you can also unlock your phone using the volume keys!
So my problem is solved and I suggest to all people that have similar troubles to think about this solution!
I thought that S2W is just kernel related and not ROM related? So it would be enough to use the kernel from amidabuddha, right?
StormShadowBK said:
I thought that S2W is just kernel related and not ROM related? So it would be enough to use the kernel from amidabuddha, right?
Click to expand...
Click to collapse
If your using a sense rom, then yes
Just remember, if the world didn't suck, we'd all fall off.

[Q] CM10 Nav buttons flashing on and off??

Hi all I have a Galaxy Blaze 4G on the t-mobile network.
I flashed CM 10 cm-10.0.0-t769.zip and the gapps from this thread.
Every thing seems to work very well but when the phone screen times out and goes black or I hit the power button to turn off the screen the hardware buttons ( Menu Home Back Search ) will flash on and off in 2 second intervals.
Any ideas? have I just not found a setting?
Thanks for reading.
Settings / display / notification light. It is probably flashing because of a notification that needs answering.
Romman0 said:
Settings / display / notification light. It is probably flashing because of a notification that needs answering.
Click to expand...
Click to collapse
Thank you for the reply. Yes it was an e-mail doing it.
area1509 said:
Thank you for the reply. Yes it was an e-mail doing it.
Click to expand...
Click to collapse
You need to flash the newest nightly, the stable isn't stable check the date. 3-10-13 is the latest. Plus the stable is missing a few things like the kill all apps button at the top of the recent apps switch.
I'd also really recommend flashing the updated radio located here:
http://forum.xda-developers.com/showthread.php?t=2171664
I was having some issues with not being able to answer/make calls but this seems to have fixed it. It's an updated radio from what you probably have.
Cirkustanz said:
I'd also really recommend flashing the updated radio located here:
http://forum.xda-developers.com/showthread.php?t=2171664
I was having some issues with not being able to answer/make calls but this seems to have fixed it. It's an updated radio from what you probably have.
Click to expand...
Click to collapse
I feel like a car salesman, been trying to tell you guys for a week now.lol
jbats said:
I feel like a car salesman, been trying to tell you guys for a week now.lol
Click to expand...
Click to collapse
Hah, now that's funny. Truth is I stopped checking on XDA for a while, and never even saw that radio update. That's because I felt like I didn't really have a reason to, CM10 seems to be everything I wanted.
So, that's a kudos, all around?

LED Notification malfunction

I suppose this has already been discussed but I still need an answer.
When I receive a notification, like SMS, sometimes the LED lights up and behaves as it should, and other times it simply doesn't blink. This seems to be random... Is there any way to fix this?
Also, is this a software issue, or hardware issue that needs RMA?
Thanks.
ColdFire InOx said:
I suppose this has already been discussed but I still need an answer.
When I receive a notification, like SMS, sometimes the LED lights up and behaves as it should, and other times it simply doesn't blink. This seems to be random... Is there any way to fix this?
Also, is this a software issue, or hardware issue that needs RMA?
Thanks.
Click to expand...
Click to collapse
I've had a similar issue with using the custom stock notification, but I switched over to Light Flow and you you can choose your color led notification and it works fine you try it out.
Anth0789 said:
I've had a similar issue with using the custom stock notification, but I switched over to Light Flow and you you can choose your color led notification and it works fine you try it out.
Click to expand...
Click to collapse
I already tried Light Flow and the problem persisted... So does that mean it's a hardware defect?
ColdFire InOx said:
I already tried Light Flow and the problem persisted... So does that mean it's a hardware defect?
Click to expand...
Click to collapse
Generally I've found it to be software related. Which custom ROM are you on? Could you possible test on another to see if the problem persists?
JuGGerbad said:
Generally I've found it to be software related. Which custom ROM are you on? Could you possible test on another to see if the problem persists?
Click to expand...
Click to collapse
My Nexus is completely stock, and unrooted... The problem hasn't happened in the last couple of days but I'm concerned it will return...
The LED itself functions well, but sometimes it just isn't triggered by notifications as it should.
ColdFire InOx said:
My Nexus is completely stock, and unrooted... The problem hasn't happened in the last couple of days but I'm concerned it will return...
The LED itself functions well, but sometimes it just isn't triggered by notifications as it should.
Click to expand...
Click to collapse
Every once in awhile something similar happens to mine. If I power the screen on and off without actually unlocking the phone, the LED begins flashing normally as it should. Not sure if sometimes it just doesn't get triggered.
JuGGerbad said:
Every once in awhile something similar happens to mine. If I power the screen on and off without actually unlocking the phone, the LED begins flashing normally as it should. Not sure if sometimes it just doesn't get triggered.
Click to expand...
Click to collapse
So that means it is software related? A bug in KitKat?
ColdFire InOx said:
My Nexus is completely stock, and unrooted... The problem hasn't happened in the last couple of days but I'm concerned it will return...
The LED itself functions well, but sometimes it just isn't triggered by notifications as it should.
Click to expand...
Click to collapse
I thought mine had a similar problem initially on stock, but I think it was just me being picky ..... I'm running the CM11 nightlies now and it's working fine... Generally though the light will only turn on for notifications when the screen is off... Perhaps that's what you're noticing...
rwilpstra said:
I thought mine had a similar problem initially on stock, but I think it was just me being picky ..... I'm running the CM11 nightlies now and it's working fine... Generally though the light will only turn on for notifications when the screen is off... Perhaps that's what you're noticing...
Click to expand...
Click to collapse
Not really, sometimes I light up the screen and I have a notification and there was no LED blinking...
ColdFire InOx said:
Not really, sometimes I light up the screen and I have a notification and there was no LED blinking...
Click to expand...
Click to collapse
Is that for an sms? I'm not sure how many different notifications it actually lights up for on stock.
rwilpstra said:
Is that for an sms? I'm not sure how many different notifications it actually lights up for on stock.
Click to expand...
Click to collapse
Not just for SMS. You see, right now I received an email through the Gmail app and the LED blinked once and stopped. And I turned the screen on and off and then it blinked once again and stopped. Really weird!
But now I got a text message and it's working fine. It's really random!
ColdFire InOx said:
Not just for SMS. You see, right now I received an email through the Gmail app and the LED blinked once and stopped. And I turned the screen on and off and then it blinked once again and stopped. Really weird!
But now I got a text message and it's working fine. It's really random!
Click to expand...
Click to collapse
That sounds pretty similar to what mine was doing. I don't think lightflow even helped too much... I would recommend CM11.... It has customization for the notification light built in and it all seems to work very well.
rwilpstra said:
That sounds pretty similar to what mine was doing. I don't think lightflow even helped too much... I would recommend CM11.... It has customization for the notification light built in and it all seems to work very well.
Click to expand...
Click to collapse
It should be a KitKat bug then. How can I report bugs to google?
ColdFire InOx said:
It should be a KitKat bug then. How can I report bugs to google?
Click to expand...
Click to collapse
Check here
rwilpstra said:
Check here
Click to expand...
Click to collapse
Actually, that wasn't very helpful. I found it on my own nonetheless.
I wonder how this kind of bug has gone unnoticed or unfixed for so long.
I will try to use another ROM and then report back. I suppose this is a KitKat bug.
ColdFire InOx said:
I will try to use another ROM and then report back. I suppose this is a KitKat bug.
Click to expand...
Click to collapse
I m on droidkang and its ok

Touch Problem

Q few months afo i replaced my G3 Screen as old one was broken and after updating it to M.M stock rom or even flashing some other M.M + roms touch is not working from staring after ph boot up.
But when i go down to L.P it work perfectly....
Any one can help....
PlZzz...
Thx....
Yup... need a Moto OEM touchscreen, half of the third party ones, typically the cheaper ones, don't work on Marshmallow. We still don't understand why, but it's been a thing for quite a while.
Piyush Garg said:
Q few months afo i replaced my G3 Screen as old one was broken and after updating it to M.M stock rom or even flashing some other M.M + roms touch is not working from staring after ph boot up.
But when i go down to L.P it work perfectly....
Any one can help....
PlZzz...
Thx....
Click to expand...
Click to collapse
Try nougat roms
Prashant324 said:
Try nougat roms
Click to expand...
Click to collapse
same with that...
Piyush Garg said:
same with that...
Click to expand...
Click to collapse
This is a known issue... we don't know why for sure, but some non-OEM replacement touchscreens do not work with anything but Lollipop... And we don't know how to make it work other than replacing it with an Moto OEM touchscreen or one that is of high quality.
acejavelin said:
This is a known issue... we don't know why for sure, but some non-OEM replacement touchscreens do not work with anything but Lollipop... And we don't know how to make it work other than replacing it with an Moto OEM touchscreen or one that is of high quality.
Click to expand...
Click to collapse
I am interesting why devs dont wanna implement l.mretus synaptics driver in all newer android or custom distributions than lollipop knowing this!
Its really strange , Lenovo is doing nothing in this case but devs could do..but they have conviced that its working(newer driver) for them but its not heh if something is good for everyone..why we can't use it?
pio80 said:
I am interesting why devs dont wanna implement l.mretus synaptics driver in all newer android or custom distributions than lollipop knowing this!
Its really strange , Lenovo is doing nothing in this case but devs could do..but they have conviced that its working(newer driver) for them but its not heh if something is good for everyone..why we can't use it?
Click to expand...
Click to collapse
Because it creates other potential issues for minimal gain I assume. I can't really answer that question definitively.
I have ghost touch issue only while calling........i tried Marshmallow Stock ROM CM 13 and LineageOS14........i couldn't fix this........
NOTE: I didn't remove or replace my display......the phone is intact
Sachin ET said:
I have ghost touch issue only while calling........i tried Marshmallow Stock ROM CM 13 and LineageOS14........i couldn't fix this........
NOTE: I didn't remove or replace my display......the phone is intact
Click to expand...
Click to collapse
Does the screen blank (turn off) when you hold it up to your ear? If so, I do that know, if it doesn't you have a proximity sensor issue and the device needs to be repaired/replaced.
acejavelin said:
Does the screen blank (turn off) when you hold it up to your ear? If so, I do that know, if it doesn't you have a proximity sensor issue and the device needs to be repaired/replaced.
Click to expand...
Click to collapse
Yes the proximity sensor works perfectly fine (Screen Turns off when it's covered while calling)
Sachin ET said:
Yes the proximity sensor works perfectly fine (Screen Turns off when it's covered while calling)
Click to expand...
Click to collapse
So what is the issue then? If the screen is off it shouldn't be recognizing any touches... or am I misunderstanding the problem?
acejavelin said:
So what is the issue then? If the screen is off it shouldn't be recognizing any touches... or am I misunderstanding the problem?
Click to expand...
Click to collapse
I'll explain........the problem is when i am making a call and not holding it to my ear (Or it hapens in the time gap between dialing and holding it to my ear)........same thing happens in the case of incoming call, that is i cant pick the incoming call(either the screen freazes or the ghost touch automatically" Decline" my call).
I am attaching a link down here........please have a look at it........ it is a screen recoded video during an incoming call.
https://drive.google.com/file/d/0B_yXW_DztkJ7Nkt2NlBLQmpQR2M/view?usp=drivesdk
NOTE ( i didn't touch the screen while recording........the whole thing happens automatically)
Thanks

Categories

Resources