I rooted my girlfriend's S3 with no problems. I can install a TW rom and everything works as expected. If I installed a ASOP rom, when a call is made or received the screen turns off. If you pull the phone away from your ear the screen stays off. I've browsed around the forums, but have not found anything to resolve the issue. Any ideas of what might cause this on ASOP roms ?
Thanks in advance,
Richard
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
You could test the proximity sensor response. It might be flaky?
I use this app,
https://play.google.com/store/apps/details?id=com.tbs.activity
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
audit13 said:
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
Click to expand...
Click to collapse
The only time it has been an issue is with ASOP roms. If I use a TW rom, there is an option to leave the screen on during a call. This is what I clicked to get the screen on during calls. However, with ASOP roms there is not an option for this. I don't think it's the proximity sensor since the screen stays on with calls on a TW rom. I forgot to mention that the ASOP was KK rom, but I have the same phone different cell provider and do not have this issue. I think I tried a JB rom with the same effect.
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
audit13 said:
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
Click to expand...
Click to collapse
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
riche1 said:
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
Click to expand...
Click to collapse
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
audit13 said:
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
Click to expand...
Click to collapse
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
riche1 said:
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
Click to expand...
Click to collapse
Without making any changes to the stock TW ROM dialer settings, does the screen go black when you place the phone next to your ear and come back on when you move it away from your ear?
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
riche1 said:
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
Click to expand...
Click to collapse
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
audit13 said:
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
Click to expand...
Click to collapse
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
riche1 said:
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
Click to expand...
Click to collapse
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
audit13 said:
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
Click to expand...
Click to collapse
she said it was not a problem until the phone was updated to 4.3 through ATT software update. This was way before I rooted the phone. The same thing started with her sister's phone. So.. I'm stumped as to what the problem could be. I rooted it because I thought CM11 might fix the issue and that was not the case. I don't know how I can go about fixing it. I don't want to take a chance in bricking the phone.
Related
my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.
chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?
From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.
networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.
i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.
thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.
well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.
There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.
actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.
Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.
Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.
Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?
we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.
It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent
I've had this issue for quite a while now.. at first I figured it was just a bug as my screen would no longer rotate but I've flashed and tried several different roms (Probam jelly bean, KitKat, and now on Temasek V28 KitKat) and have tried a few different Kernels such as Devil 2.3.2 and currently using the stock Temasek kernel.
I've downloaded some sensor apps and they list my sensors, but whenever I go to test them such as the accelerom3534, gyroscope, compass.. they don't work at all.. They just say "waiting for data"
The Proximity sensor still appears to be working though.
Anyone had this issue? My phone I don't think is damaged.. I've dropped it on some small falls in the past but it's been in a nice cover as well.
Small update:
Went back to a rooted stock 4.1.2 AT&T ROM, stock kernel, stock modem.. no change. Must be the hardware being broken
epix1718 said:
Small update:
Went back to a rooted stock 4.1.2 AT&T ROM, stock kernel, stock modem.. no change. Must be the hardware being broken
Click to expand...
Click to collapse
Is it your home screen that doesn't rotate or will no apps work.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
ShrekOpher said:
Is it your home screen that doesn't rotate or will no apps work.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
None of the apps will rotate, or say a picture in "gallery". Home screen I know was never designed to rotate.
Also just tried the 1-Click ODIN restore to unrooted stock rom, no difference Screen still does not rotate in any apps.
Sounding like a hardware issue...
Sorry to hear that ...g
epix1718 said:
None of the apps will rotate, or say a picture in "gallery". Home screen I know was never designed to rotate.
Also just tried the 1-Click ODIN restore to unrooted stock rom, no difference Screen still does not rotate in any apps.
Click to expand...
Click to collapse
the only other option I can suggest is to check and make sure all of your settings that effect screen rotation of cleared. Make sure you don't have smart stay on and you have screen rotation enabled in your settings. You may also want to turn them on if they are off and reboot your phone. Then turn them back off and reboot your phone again. If that doesn't fix it I would assume its a hardware issue.
Did you drop your phone recently or get it wet or damp. That's the only thing I have heard can cause the hardware issue.
bringing this thread back to life sense I couldn't do the same for my sensors
Hello there! So I have had a similar experience with the Note 2. It is not hardware related as far as I can determine because I swapped out the prox sensor on mine and it did not help. I feel that it is kernel related. On my previous Note 2, I flashed some kernel, prox sensor stopped working. I flashed back to stock AT&T and it worked for one call before quitting again. That's when I tried a new sensor and camera unit. The phone was under warranty so I triangled away and traded it. With the current Note 2, I flashed Sky note 9.3 and then after a while the prox sensor stopped working, I just thought okay with whatever maybe it's the kernel I'm using. I wanted to upgrade to Sky note Air, so I did. Got all settled in and decided to see if their provided kernel fixed my call sensor, no cigar. So I went into *#0*# and realized that none of my sensors were working. Tried using Devil Kernel, stock, stock ROM, all sorts of configurations and I can't revive any of them. Feeling very defeated.
New to running custom roms on phone, usually I just stick to stock but after a week of running COS I was about ready to return my phone. Found paranoid android, read the thread and got it running on my phone. I have to say it completely changed my opinion on the phone and I am loving the experience so far. 2 things though
1) Proximity sensor not working when in a call, not THAT big of a deal but I didn't know if it had already been reported for this rom yet as I read some of the other roms were experiencing a similar issue.
2) This maybe just me not being able to find stuff but is there a way to keep the notification/status bar from going into auto-hide? Although having full screen is nice, I am so used to seeing the status bar that I would like the option to display it.
Other than those two issues, I am loving this rom, even donated to the dev just because it turned a mediocre/almost bad experience into a positive one.
Running pa_find7-4.4-20140626 with micro mod gapps
Thanks for the help!
On PA, there are multiple settings to change notification and what not. As far as proximity sensor, it may be wise to wipe and reflash. I've installed PA on mine and don't remember having an issue with it at all.
One hint, most these apps automatically turn gesture while screen off. If you carry phone in pocket, it will turn torch on and start music without you ever touching the phone. This goes for most of the roms though!
best of luck
lambda231 said:
New to running custom roms on phone, usually I just stick to stock but after a week of running COS I was about ready to return my phone. Found paranoid android, read the thread and got it running on my phone. I have to say it completely changed my opinion on the phone and I am loving the experience so far. 2 things though
1) Proximity sensor not working when in a call, not THAT big of a deal but I didn't know if it had already been reported for this rom yet as I read some of the other roms were experiencing a similar issue.
2) This maybe just me not being able to find stuff but is there a way to keep the notification/status bar from going into auto-hide? Although having full screen is nice, I am so used to seeing the status bar that I would like the option to display it.
Other than those two issues, I am loving this rom, even donated to the dev just because it turned a mediocre/almost bad experience into a positive one.
Running pa_find7-4.4-20140626 with micro mod gapps
Thanks for the help!
Click to expand...
Click to collapse
i am having a strange issue. Running Virgin Rom Google Edition 4.4.4.
Every time I am on the phone, screen turns black as expected. Yet, when I hang up, the screen doesn't turn on. Very often I cannot wake up the phone by pressing any button. After about a minute or two, it becomes responsive again, and I am able to turn the phone on.
When looking at Better Battery Stats, ProximitySensor is the biggest battery hug. In fact it runs for as long as the accumulated time of the phone calls I have mad or received.
In other words, it doesn't turn itself off when I am on the phone.
I tried blowing the compressed air through the top speaker and headphone jack with no improvement.
Is this hardware related or software related?
i tried other roms on this phone and don't remember having this issue.
I like using the AOSP based rom. If this is software related, can someone recomend another AOSP rom that works well and stable, and is as quick as snappy as the virgin rom I am using?
Any help, suggestions would be highly appreciated.
Thanks
That's an issue with aosp/cm ROMs, only in touchwiz it works as it should. It's also normal for it to be on while you are in a call. You can try opening the phone and blowing in it instead of just from the outside
I am confused by what you write.
You are saying there is an issue with aosp/cm roms. . Yet, you are also saying that it is normal for the proximity sensor to be constantly on while on the phone. Then if it is normal, than what is the issue with aosp rom? Does the proximity sensor stay on as well in TW roms?
Please clarify what you mean.
Thanks.
serio22 said:
That's an issue with aosp/cm ROMs, only in touchwiz it works as it should. It's also normal for it to be on while you are in a call. You can try opening the phone and blowing in it instead of just from the outside
Click to expand...
Click to collapse
Sorry I meant the issue with it not waking the phone up is the problem with aosp/cm ROMs. Proximity sensor needs a wakelock to detect when you move the device away from your ear so it can wake the phone up.. Wakelocks are not always bad
serio22 said:
Sorry I meant the issue with it not waking the phone up is the problem with aosp/cm ROMs. Proximity sensor needs a wakelock to detect when you move the device away from your ear so it can wake the phone up.. Wakelocks are not always bad
Click to expand...
Click to collapse
I dont know about it being a wakelock problem. I used to have this problem with the google play edition rom on my s4, where the screen will not come back on during a phone call, I got a air duster can and blow out the speaker above the screen. Samsung put the proximity sensor right behind the speaker for when you hold the phone up to your head and it get dirty easily.
Could you recommend a good TW rom that is light on resources and quick in real use?
Those are the aspects that attracted me to aosp roms in the first place.
retfeg said:
Could you recommend a good TW rom that is light on resources and quick in real use?
Those are the aspects that attracted me to aosp roms in the first place.
Click to expand...
Click to collapse
I generally don't recommend ROMs but Warpdrive is the lightest tw ROM I have ever used, its super debloated and fast, but I found there was home button lag at first, but this is because s-voice was removed and you can't easily disable the 'open by double taping home button' feature which is what makes it lag, so I installed S-voice myself, disabled the feature and the lag was gone
I have the Chinese version of the Find 7 currently running MoKee 44.4 because I thought this issue was caused by AOSPA, which I flashed for the first time yesterday. Anyway when I make a call the screen turns off as it should and will not come back on no matter what I do. I have to reboot the phone every time. I looked through similar threads but they all seem to be unrelated to having a custom rom; this problem only started occurring after I flashed one & everything worked fine when I was running Color OS 2.0. I tried installing a new dialer but the same problem happened.
Does anyone know of a way not to have the screen turn off when making a call or better yet how to fix the issue?
Thanks very much!
I'm having a very similar situation with Paranoid Android 4.6 (both beta4 and latest beta6).
If I long-press home button, I'm sent back to the lock screen, but only after the call is finished.
Maybe there's a problem with AOSPA's proximity sensor during calls?
Sometimes, the screen will not turn off, but the screen will not react to any touch input during the call.
Power button will turn screen off but not back on again.
This is a problem coming from ColorOS 2.0.x.
I will try to flash back to and older version of ColorOS. After that try an AOSP rom.
Sent from my X9006 using Tapatalk
same problem
Whit all rom use CM11 based or similar, I have black screen when I call, and no input possible!
the only ROM stable is the Kakulay, bet it have several problem whit the contacts management! it confuse the name and numbers in the memory and SIM card!