Hello everyone, as my title states. I am having a problem with my proximity sensor when in a call. I have a sprint galaxy note 2 (L900) and am currently running CarbonROM's nightlies (4.4.2). Before I was using the 4/10/14 nightlie and when I was in a call the sensor was stuck and kept my phone dark until the call ended. But now with the 4/17/14 nightlie, the phone is constantly on while in a call. Has anyone else have this issue using CarbonROM? If there's a fix please let me know. Much appreciated.
thaittnguyen said:
Hello everyone, as my title states. I am having a problem with my proximity sensor when in a call. I have a sprint galaxy note 2 (L900) and am currently running CarbonROM's nightlies (4.4.2). Before I was using the 4/10/14 nightlie and when I was in a call the sensor was stuck and kept my phone dark until the call ended. But now with the 4/17/14 nightlie, the phone is constantly on while in a call. Has anyone else have this issue using CarbonROM? If there's a fix please let me know. Much appreciated.
Click to expand...
Click to collapse
I'm currently on Carbon ROM nightly version 4-17 and I have the same issue. Did you find any info on this bug in the Carbon ROM forum? I think this needs to be looked into because I don't like face dialing while talking on the phone. lol
tx_dbs_tx said:
I'm currently on Carbon ROM nightly version 4-17 and I have the same issue. Did you find any info on this bug in the Carbon ROM forum? I think this needs to be looked into because I don't like face dialing while talking on the phone. lol
Click to expand...
Click to collapse
No I didn't find any fixes for it. I talked to one of the developers and they are looking into it BC when I entered the live chat I asked the same question and they responded with "let me guess, note 2?"they're not sure what's going on with the notes that is causing the bug. But I've been looking at the change logs hoping they fix it and my phone volume is really low when I'm talking to someone as well. Sometimes I can't even hear the caller so I have to switch to speaker :/
Thanks for the reply. As for the low volume during calls. You may already know this but try lowering the volume then raise it back up and that should increase the volume a lot. It's a bug in some AOSP ROMS.
I have tried that and sometimes it works and sometimes it doesn't, unfortunately.
Sent from my SPH-L900 using xda app-developers app
The proximity sensor issue has been fixed in the latest nightly build 4-23. Although now I can't sync my browser in Google account sync settings. All others seem to sync except browser. Could be another bug...
Related
sorted it out. For some reason removing the dialler application from the phone group within profiles caused it to start working again. very strange.
---
Hi guys,
For the last few nightlies using the Cyanogenmod 7 my desire hd won't ring.
When a call is received then it just vibrates even though the ring volume to set high and the ringer is also turned on.
Can anyone help please as I could really do with this back.
I would have posted this in the development forum but login still prevents this.
Thanks
Paul
u r a hero <3
Something similar happened to my friend's SE Xperia Mini Pro, using CMmini nightly builds. Strange thing here is that it doesn't even vibrate. We've tried changing the default calling app, but it keeps coming through the one what shipped with the ROM.
How weird is that
jonahjones said:
sorted it out. For some reason removing the dialler application from the phone group within profiles caused it to start working again. very strange.
---
Hi guys,
For the last few nightlies using the Cyanogenmod 7 my desire hd won't ring.
When a call is received then it just vibrates even though the ring volume to set high and the ringer is also turned on.
Can anyone help please as I could really do with this back.
I would have posted this in the development forum but login still prevents this.
Thanks
Paul
Click to expand...
Click to collapse
You just solved my problem too i have an lg p350 flashed t his new rom and didn't know how to make my phone ring thank you!
How did you find his solution out? Experimentation?
Was a while ago but just experimenting i think.
Glad you sorted it.
Sent from my GT-N7100 using Tapatalk 2
Hi guys,
I have this program called WeChat and you can do video calls on it. When I enter a video call, it works fine for the first 15-20 seconds then the phone just blacks out and restarts. This program was fine when I was on stock ROM but I am currently on CM10 9/19 nightly and this has been an ongoing issue since I started flashing CM10 on my S3.
Yes.. I could go back to stock ROM but I will miss CM10 if I do... Is this a known issue? I did a quick search and I didn't find anyone with similar issue.
Thanks in advance.
"Known issues" are typically of and for the ROM itself not third party apps.
Just guessing but it could be related to the fact we don't have a JB kernel source yet.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Is there a place to find known issues? I would like to add that I just flashed to 9/20 nightly and same problem...
On this particular Rom, has anyone had any issues with proximity sensor not recognizing the phone to your ear, therefore pressing buttons with your face instead of shutting off? I don't use phone for calls often, but seems every call I've taken I've run across that issue. Thanks!
I am on the latest MMuzzy Toro plus 4.2 and haven't noticed anything like this so far. I don't do a lot of calling but when I take a call it seems to work normally.
I'm running the 11/21 build and have no issue. I have made a few calls and no problems.
OP may try a fresh flash
Thanks I'll try fresh flash see what happens. Just wanted to see if anyone else had similar issues.
Sent from my Galaxy Nexus using xda app-developers app
I've problems with the Proximity sensor too.
Ok.. I am noob. But here is what I've.
I got the new 4.2 takju image from google and followed a very good thread here about how to install it and it worked perfectly. The only thing that is not working is Proximity sensor during Skype calls and Google Talk calls. I really can't understand this but this is the problem I've.
I flashed it twice with takju and it didn't work and installed yajku too and still not working. I am noticing minimal amount of reports about this but over the internet. But no solutions yet.
Hope someone would help us
I have been on his ROM from the day 4.2 dropped and it has been great. Few problems (googles not mmuzy's)but they have been fixed berry quickly
Sent from my Galaxy Nexus using Tapatalk 2
Yes, please check out my thread: http://forum.xda-developers.com/showthread.php?t=2006783
Fresh install, factory resets, the works. Still have the problem. Proximity sensor turns the screen off but the dial pad or even the end call button are active and are pressed by my cheek. It pretty much kills 4.2 for me and I am just about to go back to 4.1.2.
EDIT: Just to clarify, I am running completely stock 4.2 tajku
Just an FYI, appears to be a PGM issue in relation to 4.2. Even checked the PGM app thread and author released an update for the paid version, with the free version being updated soon.
[email protected]
Have my galaxy nexus a few months now, very satisfied, but I had a galaxy s
And when I made a phone call, moved the phone away from my ear the display goes on.
But not on my galaxy nexus the display doesn't turn on.
Is this a bug, or do I've to change an option.
Thanks
-Chris
are you using stock?
because some custom roms have the options to turn that feature on and off, perhaps it's off?
Yesterday I switched from carbon to paranoid and on paranoid it seems to function properly.
Never had an option on carbon to change this particular behavior, so I think it's a bug
Thanks for the answer
I write a comment on the thread and report the issue
Take care
-Chris
chiwou said:
[email protected]
Have my galaxy nexus a few months now, very satisfied, but I had a galaxy s
And when I made a phone call, moved the phone away from my ear the display goes on.
But not on my galaxy nexus the display doesn't turn on.
Is this a bug, or do I've to change an option.
Thanks
-Chris
Click to expand...
Click to collapse
Yeah dude it's a bug on some roms or some time in stock roms also
you have to flash a new rom.................my advise is cm 10.1 or latest aosp if u like stock........
chiwou said:
Yesterday I switched from carbon to paranoid and on paranoid it seems to function properly.
Never had an option on carbon to change this particular behavior, so I think it's a bug
Thanks for the answer
I write a comment on the thread and report the issue
Take care
-Chris
Click to expand...
Click to collapse
okay, glad the switch worked out, I never have used carbon so I wouldn't know :laugh:
cheers.
I am using find7s with the latest CM13 nightly.
Something strange that happens ever since I've moved to CM13, is that whenever I'm not using a wired headphone, voice calls are being dropped.
Anyone else has experienced it? Knows what to do?
munky-head said:
I am using find7s with the latest CM13 nightly.
Something strange that happens ever since I've moved to CM13, is that whenever I'm not using a wired headphone, voice calls are being dropped.
Anyone else has experienced it? Knows what to do?
Click to expand...
Click to collapse
No, but I face weak signals on Custom ROMs in few occasions.
deemee1988 said:
No, but I face weak signals on Custom ROMs in few occasions.
Click to expand...
Click to collapse
Thanks for answering.
Signal is 100%. And I've been using custom roms forever.
It's definitely something new...
calls dropped - you're lucky! I just updated to cm13 nightly and it can't find my SIM card. Hmmmmm....
I've got the same trouble.
Sometimes around 3-4 minutes, my call is dropped, quite annoying, because people think you are hung up on them.
Hello,
Have you enable "End Call" by press power button on Button Actions settings ?
Thread closed.
Please use:
http://forum.xda-developers.com/fin...-cm-13-0-official-nightlies-find7a-s-t3263643