Hey guys this thing thats been happening to me is absulotely mind boggling and if anyone can resolve this it would be greatly appreciated. it bugs me like theres no tomorrow.
so heres the issue.
i have a samsung galaxy s4 with all the latest updates provided Android Version 4.2.2
when im travelling along in the car or even randomly seated i would receive a call or even make a call and place my phone on loudspeaker now the funny thing here is that the phone after maybe 10-20 seconds will automatically switch back to normal speaker and it annoys me so i have to put it back on loudspeaker mode
ive had the occasional scene where it still showed that loudspeaker was activated but the caller was coming through the normal speaker so it forces me to tap loudspeaker to de-activate it and then tap it again to activate only to realise not long after it automatically switched back to the normal speaker all over again.
NOTE: the phone is laying flat on my lap or standing infront of me.
has anyone had this issue before and is there some sort of fix for it
PLEASE HELPPP !!!
Micky-90 said:
Hey guys this thing thats been happening to me is absulotely mind boggling and if anyone can resolve this it would be greatly appreciated. it bugs me like theres no tomorrow.
so heres the issue.
i have a samsung galaxy s4 with all the latest updates provided Android Version 4.2.2
when im travelling along in the car or even randomly seated i would receive a call or even make a call and place my phone on loudspeaker now the funny thing here is that the phone after maybe 10-20 seconds will automatically switch back to normal speaker and it annoys me so i have to put it back on loudspeaker mode
ive had the occasional scene where it still showed that loudspeaker was activated but the caller was coming through the normal speaker so it forces me to tap loudspeaker to de-activate it and then tap it again to activate only to realise not long after it automatically switched back to the normal speaker all over again.
NOTE: the phone is laying flat on my lap or standing infront of me.
has anyone had this issue before and is there some sort of fix for it
PLEASE HELPPP !!!
Click to expand...
Click to collapse
Two thinks u can try if u have had a OTA update and that time if u did not do reset do it now hopefully all issues will be sorted out
2nd try to enable / disable driving mode as and when u use or not in use
Sent from my GT-I9500 using xda premium
So I definitely checked to see if driving mode was on or not and I tried it still same issue so my next question how do I do the ota update what necessary
Sent from my GT-I9505 using xda app-developers app
So I have found that the only way I can get the loudspeaker to stay on is too keep the screen on after a few fiddling here in there I need to know how to force screen on when it on loudspeaker
Sent from my GT-I9505 using xda app-developers app
I recently got the galaxy s5 and for some reason when my phone is sitting by itself it will make a noise as if I was calling someone. It's the tone you hear when you call a person and wait for them to answer and it will sound only once and do it again in about 5 to 10 minutes. I read around forums but they found that it was the NFC making their phone make strange noises. I turned NFC off and to no avail. Any ideas??:crying:
That's strange did you try a factory reset? I had my motion settings ticked, so that it would make a call if rotated, that kept screwing me being in my pocket. Try shutting all your air gestures and motions off
Sent from my SM-G900V using XDA Free mobile app
Okay, since i flashed Alliancerom v3.0 on NB1, Everything works charmingly but this phone app causes my blood pressure to spike up. It's just a minor issue but it is very annoying for me.
whenever i run my phone app, it crashes with 'Unfortunately the contact has stopped'. my contacts work fine and i can recieve and call people through adding their number to the contacts and also can use voicemail. but the problem is that i cannot check my missed calls, and everytime i have to add a number to call. Because i cannot check my missed phonecall, this little 'missed calls counter' on the phone icon will never go away. I tried factory resets and force stopped and cleared everything but this problem will never go away. Can someone help me or at least tell me how to make this little counter thing to disappear?
Not sure why but after the last system update the phone will only come out of black screen sleep mode if I use the fingerprint sensor when theres an incoming call.
Any Ideas ?
This happened to me today too.
Hello, me too! Oreo Beta 2
Anyone ?
going_home said:
Anyone ?
Click to expand...
Click to collapse
Not me, I've never experienced this issue since I got the phone from N then updated to OB2, and now OB3.
Sounds like the proximity sensor may have an issue.
Do you have a screen protector or case?
I don't have that issue with a screen protector and Tudia case and B3.
It's a bug in the latest Google Dialer app. I fixed it be deinstalling the new version/updates then clearing cache and data in the dialer app. It's affecting the Pixel2 XL running 8.1 also. Fixed my issue and I won't let it install the newer dialer version from the play store
In Beta 3, I haven't experienced that problem. I did heavily on 7.1.1
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
going_home said:
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
Click to expand...
Click to collapse
happened to me last week too.. it only happened after I locked the phone, 5-10 minutes later incoming call or when unlocking the phone the phone shows back screen only for a few seconds then it went back to normal.
the problem went away after I turned off the bluetooth radio.
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
DrvLikHell said:
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
Click to expand...
Click to collapse
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
I tried two other dialers and it didn't make a difference on my phone. Drupe did work to make the screen show who's calling again, but wow, Drupe has too much.... just, everything. All I want in a dialer is basic functions in a standard format. Drupe is like a carnival of a dialer. I'll keep trying dialers though, since that one did work, maybe another one will too. Thanks for the suggestion.
Yeah, if you just take the Drupe dialer phone icon and put that on your home screen, whenever you select it you'll go right to the normal looking dialer. :good:You may want to try ExDialer. That used to be one I'd use a lot.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Sent from my PH-1 using Tapatalk
rignfool said:
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Click to expand...
Click to collapse
10 million downloads...good enough for me. I've used it for a long time and it's been better for me than the stock dialer. Just my opinion, no one has to use it but it sure beats a black screen when the phone rings.
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Sent from my Pixel 2 XL using Tapatalk
I read about some people being able to fix it by uninstalling dialer updates. Unfortunately, the Essential doesn't have any to uninstall. I'm working around it by using Drupe as my default dialer, but setting the stock dialer as the default app for dialing, if that makes any sense (When an event pops up that requires the dialer, it asks which dialer to use, I selected the stock dialer and told it always use that.) This way incoming calls trigger Drupe, which acts the way it's supposed to on Bluetooth, but I can still use the stock app for making calls and missed calls and such.
bricky23 said:
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Click to expand...
Click to collapse
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Jank4AU said:
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Click to expand...
Click to collapse
My volume buttons always work fine, BT or otherwise. Stock 7.1.1. Your issue could very well be related to OB3. I had a little bit of an issue connecting/reconnecting to some BT devices at first, but not lately, so it must have been fixed in the last few patches.
So whenever I am getting a call on my phone I am not getting the caller screen. Its just staying in the notification bar. So in order to accept or decline the call I have to pull down the notification bar and then do the following.
I don't know why is this happening.
If somebody knows the solution ,let me know, please asap.
+1 and this is irritating. Is there a fix?
Don't get it quite don't you have notification head's up on incoming call so you wouldn't have to swipe notification bar. Or you are talking when the phone is locked ?
Are you using bluetooth?
anyway: https://forum.xda-developers.com/mi-a1/help/black-screen-incoming-calls-t3741578
Just try to force stop phone app in settings and clear data. It should fix it. Clearing data won't clear your contacts. Happened to me. I did this.
Erasing the app data is work for me ,thanks.
Xiomi note 5 pro
I have been using my note 5pro for almost one year. Since yesterday my all app calls such as what's app, vonage, imo are not showing on my locked screen. I can hear phone ringing but can't see who is calling untill i turnon my screen. I can get chat notifications on locked screen but not call. But normal network simcard calls are working fine. Tried almost everything. But just not winning. Can i have possiblle solution please?