How to get phone to shut screen off when taking calls? - Nextbit Robin

This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
So does anyone know? Is this simply not a feature of this phone?
Thank you.

bcsteeve said:
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
Click to expand...
Click to collapse
I thought it was just me! I haven't looked for a solution as yet, but if you find one please post back here and share.

Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.

bcsteeve said:
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
Click to expand...
Click to collapse
I had a same problem too, but did resolved after factory reset. But I don't know where is the problem located, maybe the proximity sensor is very sensitive even with dust.
Sorry, bad English.

Your English is fine
I think you might be right, because my problem now seems to come and go. The screen definitely shuts off, but there's some times when my face will put the call on mute or other strangeness. I've even accidentally sent an email to my Mom, all with my cheek while on the phone with someone else! I had to click the back button 6 or 7 times to get back to the phone screen.
This phone was good value, but I do regret the purchase.

The proximity sensor is very sensitive, even with a very small string. I just test this when I call my second phone. And moving around my finger, and boom! My screen is turned off, but did turned on again after I moving away my finger. This is surprising me when I call my mom, and I force to turn off my device, and it's rebooted. After my device is successfully booted, I tried to call my Dad, and surprisingly the screen is not turned off. So I'll try to find the problem, and I founded them:
The proximity sensor is very sensitive, so be sure to wipe the proximity sensor until it gets clean completely.
That's it, so no matter if you use a different dialer or default dialer for your device, just keep in mind that I mentioned there.
Thank you. As always, sorry for my bad English.?

Related

phone stops ringing after a split second

i've tried searching this forum with no luck for results, so maybe someone can point me in the right direction...
just wondering if there is a fix for this issue, that apparently is a bug:
when receiving an incoming call, and while the phone ringer is turned on, it will ring for a split second then it will stop ringing. the call will still be coming through and i can answer it and talk just fine, it's just the ringer that is the problem. this happens randomly, and i've found numerous posts on other forums by searching google, but haven't been able to find anything here.
can't post a url so here's some quotes:
My Dinc sometimes stops ringing after half a second with incoming calls. I'd hear a very short ring and then it just stops ringing or vibrating. I just noticed this today after missing several calls with my phone today.
This problems comes on randomly and goes away in a similar fashion. This seems to happen only when the phone is lying screen down on a flat surface. I called HTC and they said it might be due to the sensor in the front and advised me to not put phone face down and always carry it in a pouch. This is not an acceptable solution. I carry my phone in my pocket and it can very well be face down in there.
Has anyone noticed this problem? If not, I invite you to reproduce this problem. Put your phone screen down on a perfectly flat surface and try to call your cell. I'm wondering whether my phone is defective or it's a much wider issue.
Thanks.
Update: Apparently there is a feature on HTC devices when if you're holding the phone and if it rings, it will mute if you put it on a surface face down. While this is fine, the problem with my device is that if I leave it on a flat surface, it will do that for all subsequent calls too (ring for half a second and then mute). Maybe my phone has a bug in implementation of this 'feature'?
Click to expand...
Click to collapse
It's a well known issue that HTC has not fixed and will most likely never fix. I've been through 3 Dincs because of this problem and they all do the same thing. Quite irritating! Nice phone except for this BIG bug.
Click to expand...
Click to collapse
is there any fix for this bug? and does anyone know if this bug is software or hardware related. currently, i'm running stock 2.2 rooted with city id deleted. thinking about flashing CM7 or another custom rom, and just curious if it will do this with those roms as well.
thanks for any help
Must be an issue with the stock rom. I've never had a problem. But I've also never ran the stock 2.2 rom. I ran stock 2.1 until root was achieved. Custom Rom's from there on out.
Sent from my ADR6300
Also on my HTC Wildfire
This happens also on my htc wildfire android v2.2.1 (latest official rom), i think it is caused by the mute-on-pickup feature that is bugged in some way, even if i have turned it off.

Rhodium400 in-call problems with hearing either side (proximity sensor?)

I know the proximity sensor is not functional with the Rhodium400. My wife and I are both running the newest version FRX 7.1 on the .27 kernel.
She had issues with Windows Mobile getting a data connection, and it would carry over to Android. So I dd a hard reset on Windows Mobile and started her Android from scratch (as it was having other slowness and issues also). Ever since then she tells me (and I have heard this in call) that every time she puts her cheek or face to the phone it will sound as if the call dropped but it doesn't drop really. She can't hear me and I can't hear her, but as soon as she takes her head away she and I can both hear again. This doesn't happen all the time, and is likely only happening when XDAndroid has not been rebooted in a few days.
I have not been able to confirm it by sitting right beside her and calling and confirming the problem, but I plan to do so tonight. At first I thought she was just muting me because she was ticked at me...don't ask , but she isn't smart enough to come up with something like this, because technically it sounds like the proximity sensor is mucking up the phone call which I thought was not possible from everything I have read. I even had her turn the power button off at the top to turn the screen off, to make sure she wasn't bumping any buttons. The way it looks, it almost sounds as if the phone is inadvertently trying to place another phone call and putting the first phone call on hold.
Has anyone else had this issue? Doe anyone think this is likely a proximity sensor issue, or have any advice for when I get home tonight and start playing with the phone?
Supposedly also this issue was going on with her in the car and the phone plugged into a car charger. She called me back with it not on the charger and it is not messing up anymore. I don't know if it is coincidence or not, since it wasn't always doing it to begin with.
Never heard of this, almost sounds like a hardware failure.
Run WinMo for a few days, see if you can recreate the problem there. If so, there's something going haywire with the physical hardware.
I get a situation kind of like this in Android, but not WinMo. Basically if I recieve a call it's about a 50/50 chance that this happens. I can't hear them and they can't hear me. There is no sound at all, like the speaker and mic don't even turn on. However, mine doesn't seem to have anything to do with the proximity sensor as it does it as soon as I hit the answer button and moving the phone away doesn't fix it. Also, it's only when recieving calls, outgoing calls work all the time.
I've had similar problems, but quite a bit in the past, making me think mine was software or settings. So don't discouraged!
My thinking is, since auto-mute to rear speaker/mic system is a 'feature', that maybe that system gets triggered. Check those settings, and that level/bubble calibration stuff.

[Q] Proximity Sensor issue with Stock Dialer??

Hi all,
I absolutely love my Gnex. I got it on launch day, and for the most part I have not had a ton of issues. However, there is one thing that I am having a hard time dealing with, and I'm hoping someone will be able to help me with it. When I dial a number with the stock dialer I have no issues at all. After I connect and when I need to bring up the number pad to enter extensions, voicemail, or whatever else, my number pad "short circuits." I only can describe it like a flickering everytime my fingers come close to push a number. It disappears when I go to push them and reappears when I take my finger away. I almost have to time it right when trying to access my voicemail just to push the numbers I need. I have tried holding the phone in different locations because I am aware that there is a proximity sensor....but it seems to me that what is happening really shouldn't be. Is there a setting I can change? Any assistance that can be provided would be greatly appreciated.....I really would like to clear this issue up as its the only thing from making my GNex close to perfect.
Thanks!
Is there a screen protector blocking the sensor? Some of the cheap ones block then sensor and screw with it.
Nope. No screen protector as of yet. I purchased the XO Skin but have yet to put it on.
I have hung up a few calls as well.
I think the proximity sensor works but it seems to be slower than the average phone. Hopefully this is something that could be fixed with a software patch.
Punchup- Is it anything like this?
http://www.guytechie.com/articles/2012/1/22/galaxy-nexus-slow-proximity-sensor.html
OP- Mine did that once but i couldnt reproduce it on the next reboot.
Naddie that is exactly what is happening!
It is good to know so I can avoid doing it but I do hope they fix it in a patch. Thanks!

[Q] 4.2 Issue with proximity sensor/dialpad?

I'm not sure if I am the only one but searching hasn't really helped me find any answers. Basically, since updating (rather, doing a clean install of 4.2 tajku) to 4.2 Jellybean, I often have an issue where despite the fact that the proximity sensor blacks out the screen, the dial pad when pulled up still detects key hits. Hence, my cheek is randomly pressing buttons. Happens during voicemail since the dial pad is needed to get through menus and/or during calls which have a menu system.
Any else have this problem or have any ideas how I can resolve it?
Same here
Glad I'm not going crazy. Seems to also be happening without the dial pad, per say. I say that because it appears during a call, I was pressing something so I removed from proximity to be greeted by the lock screen (number pad). So I wonder if it has something to do with that. I am going to disable pin lock for awhile to see if that alleviates the problem.
Do you have something similar with SKype?
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.
MenaMAKS said:
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.
Click to expand...
Click to collapse
No Skype. And the screen goes off due to the proximity sensor - but the buttons and/or dial pad are still active. I'll try changing my power button back from "end call" to just screen off and see if that helps.
Anyway, a quick update. Seems like a couple of factory resets did the job. So something with Titanium Backup did not translate over well to 4.2 (from 4.1.2). On top of that, I can no longer seem to do a full restore, causes my device to go into boot loop. Don't know why it worked the first time. At any rate, just re-downloaded all my apps and so far so good. Just have to try and restore individual app data one by one and see if I can get it to stick without fudging up the dial pad again.
EDIT: Scratch that, it's going it again. What the hell... 4.2 is such a @#@#@ in the ass.
Still having same issue. Glad you came back with an update, bc I was about to re-flash and re-download all of my apps. I know you say that you experience it even without the keypad pulled up, but I have not. Usually happens when I call an automated system, and my call gets sent to every extension possible!
Sent from my Galaxy Nexus using xda app-developers app
Alright, I think I have it working. I did factory reset... made sure any phantom directories (i.e. storage(sdcard)/0/0/0/0 etc) were deleted.
1) By default, I tested by calling voice mail then rolling my cheek against the screen. So far so good.
2) I downloaded StickMount, Titanium Backup Pro, NTFS mounter (for ntfs driver) and ES File Explorer. Tested again as per above. OK.
3) Used Titanium Backup to restore missing apps + data. Did a test, still good.
4) Used Titanium Backup to restore only select system data (i.e. call logs, SMS log, alarm, etc). Still tests fine.
5) Enabled PGM free. Did test and BOOM, problem.
So it seems like with 4.2 there is something screwy with PGM which is essentially keeping the screen "awake" even though it's off due to sensor. Don't know why I didn't think of it earlier.
EDIT: Checked the PGM thread and it appears the author has already fixed it though only the paid version is updated atm. Says will update the free version soon if the paid version doesn't have any new bugs.
Awesome, nice work! Will see of it works for me too and report back.
Sent from my Galaxy Nexus using xda app-developers app
Edit Uninstalled PGM, reboot and its solved! Thanks for your hard work!
I was going crazy with this issue too .. it's good that it's not only me .. i will disable PGM and try
My brother's nexus has this issue without pgm installed on full stock 4.2.1 rom.
I have watched the serial code and production date is c9,or rather september 2012.
What I have to do to fix this very annoying issue?
edit: no one has this issue?It's a common problem of latest batch sold in Italy.

Person on other end of call can't hear me

Have AT&T Note 4 since launch. Stock, not rooted or anything like that. Not sure when this problem started because I don't regularly make calls, but I think within the last week or two, possibly after I got the update to COC6 (the update seemed to complete normally, though).
Every time I place or receive a phone call and attempt to use the phone normally (hold it to your head), the person on the other end cannot hear me at all. If I switch to speakerphone, they can hear me and it behaves normally, and if I connect to a Bluetooth device like my car, it also works fine, but if I try to use the phone normally, they cannot hear me. I can always hear them perfectly.
For what it's worth, Google won't pick up my "Ok Google" from the home screen anymore either. Also, I had previously had the option to wake the phone with "Ok Google" disabled, but when I try to enable it now, it hangs on listening to me say "OK Google" 3 times... as if it never hears me say it.
The microphone appears to be working completely normal for everything else I've tried, it's just acting like it's on mute when I'm in a call and not on speakerphone or Bluetooth, and the OK Google stuff isn't working either.
Any ideas? I'm trying not to factory reset... I've searched a lot and not found anything where anyone has solved the issue.
FWIW I had the same issue randomly with my rooted Note 2, and I believe I either fixed permissions or reinstalled the ROM to get it working (can't remember). I wish I could just reinstall the ROM or latest update (COC6) again so I don't have to factory reset. Is this an option at all?
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
pj_rage said:
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
Click to expand...
Click to collapse
Not gonna lie, I checked my mic hole as soon as I read this. XD
I tend to always put my pinky finger over that mic subconsciously. I don't mean to, but it's just how my hands want to hold the phone during a call. I constantly get people saying that they can't hear me though. Then I always notice that my stupid pinky is on the darn mic. Grrrrrr.
Sent from my SAMSUNG-SM-N910A using Tapatalk

Categories

Resources