Related
Hi, does anyone have same problem as I? Almost everyone I call is telling me they can hear me very low. I can hear them perfectly and all of the rest regarding sound volume is perfect.
chimas16 said:
Hi, does anyone have same problem as I? Almost everyone I call is telling me they can hear me very low. I can hear them perfectly and all of the rest regarding sound volume is perfect.
Click to expand...
Click to collapse
Check to see if you have any gunk in the mic hole. I highly doubt that your mic is the issue.
chimas16 said:
Hi, does anyone have same problem as I? Almost everyone I call is telling me they can hear me very low. I can hear them perfectly and all of the rest regarding sound volume is perfect.
Click to expand...
Click to collapse
I've got exactly the same problem. The phone is brand new, the mic hole is not blocked at all. I dont want to send it to service beacause it takes like 2 weeks to get it solved. Are there any service codes for sm-g900f to solve such issues? Any suggestions?
riddle13 said:
I've got exactly the same problem. The phone is brand new, the mic hole is not blocked at all. I dont want to send it to service beacause it takes like 2 weeks to get it solved. Are there any service codes for sm-g900f to solve such issues? Any suggestions?
Click to expand...
Click to collapse
it happens to me sometimes. I am not sure if it is a fault in the handset or something else. normally it works fine, but yes I started getting complaints that my voice is far away after buying the S5 (happened to me 3 or 4 times within one month)
chimas16 said:
Hi, does anyone have same problem as I? Almost everyone I call is telling me they can hear me very low. I can hear them perfectly and all of the rest regarding sound volume is perfect.
Click to expand...
Click to collapse
Try turning off Noise Reduction in the dialer settings menu. This will cause this type of problem for some people. The other TW builds that have it, also have a touchscreen button so it can be easily disabled while in-call but ours is buried in the menu.
tdunham said:
Try turning off Noise Reduction in the dialer settings menu. This will cause this type of problem for some people. The other TW builds that have it, also have a touchscreen button so it can be easily disabled while in-call but ours is buried in the menu.
Click to expand...
Click to collapse
Thanks! I think that solved it!
chimas16 said:
Thanks! I think that solved it!
Click to expand...
Click to collapse
Good deal.
I used to have a lot of problems with that feature on my Galaxy SIII.
But it didn't seem to affect everyone.
tdunham said:
Try turning off Noise Reduction in the dialer settings menu. This will cause this type of problem for some people. The other TW builds that have it, also have a touchscreen button so it can be easily disabled while in-call but ours is buried in the menu.
Click to expand...
Click to collapse
It has not solved mine, though. I noticed that if there is an app running in the bacground it worsens the case. Do not know why. Perhaps I will debrand my phone and change it to xeo.
I am stuck with an annoying problem. The other parties can NOT hear my voice. I have tried recording voice using voice recorder and it works. What it could be a hardware or software issue.
The phone is an official kitkat, not rooted.
ahsanshah said:
I am stuck with an annoying problem. The other parties can NOT hear my voice. I have tried recording voice using voice recorder and it works. What it could be a hardware or software issue.
The phone is an official kitkat, not rooted.
Click to expand...
Click to collapse
I dont know the exact location of the mute/unmute button but there is one in the lg app i believe so its not an hardware issue and probably also not an software one cause you have maybe clicked the button accidently. Can you go through the dialer app to find some settings where that might be located? But i guess you need to call someone first again to enable your mic
wulsic said:
I dont know the exact location of the mute/unmute button but there is one in the lg app i believe so its not an hardware issue and probably also not an software one cause you have maybe clicked the button accidently. Can you go through the dialer app to find some settings where that might be located? But i guess you need to call someone first again to enable your mic
Click to expand...
Click to collapse
No that can't be the cause , the problem goes after rebooting the phone sometimes and sometimes do not even after restart. It is quite random.
ahsanshah said:
No that can't be the cause , the problem goes after rebooting the phone sometimes and sometimes do not even after restart. It is quite random.
Click to expand...
Click to collapse
Well you can might consider to reflash stock or do factory reset if it just goes like that but i dont think its an hardware issue if you dont have mic during call but recording you have but the g2 has 2 microphones i thought so maybe one of them is failing or what. I could be wrong since i am thinking bout lots of phones atm.
I was thinking same. but factory reset is very bothering, all installed applications and data will be gone. . I am also much confident that it is not an hardware issue
Well the onky thing i can say is to look again in the dialer and incall ui to see the mute button and press unmute, try to logcat, look in the settings app and or google more about the second mic how you can test it cause i dnt know how out of my head.
software problem
ahsanshah said:
I am stuck with an annoying problem. The other parties can NOT hear my voice. I have tried recording voice using voice recorder and it works. What it could be a hardware or software issue.
The phone is an official kitkat, not rooted.
Click to expand...
Click to collapse
is software problem. Root and install a custom rom , wait an firmware upgrade or go to service guys.
Using stock dialer, on Oreo. (Had the same problem on Nougat.)
When a call comes in, it does not allow me to answer the call. If I drag up on the ball for "answer", it simply bounces back. It won't "answer".
However, this only happens when the phone is "cold". After answering a call the phone answers normally for future calls
Any ideas?
This doesn't seem to be a dead spot in the touch screen, as I can suspend the ball at the apex for an indefinite time.
The problem seems to be that it doesn't trigger the "call answer". It isn't accepting it as an input.
This is repeatable, but once it has "answered" a call, it will generally answer the next few calls accurately.
I have the same thing on Nougat and Oreo too can be pretty annoying at times
Sent from my PH-1 using Tapatalk
Pucksr said:
Using stock dialer, on Oreo. (Had the same problem on Nougat.)
When a call comes in, it does not allow me to answer the call. If I drag up on the ball for "answer", it simply bounces back. It won't "answer".
However, this only happens when the phone is "cold". After answering a call the phone answers normally for future calls
Any ideas?
This doesn't seem to be a dead spot in the touch screen, as I can suspend the ball at the apex for an indefinite time.
The problem seems to be that it doesn't trigger the "call answer". It isn't accepting it as an input.
This is repeatable, but once it has "answered" a call, it will generally answer the next few calls accurately.
Click to expand...
Click to collapse
me too. very frustrating....thinking of buying a different phone.
Pucksr said:
Using stock dialer, on Oreo. (Had the same problem on Nougat.)
When a call comes in, it does not allow me to answer the call. If I drag up on the ball for "answer", it simply bounces back. It won't "answer".
However, this only happens when the phone is "cold". After answering a call the phone answers normally for future calls
Any ideas?
This doesn't seem to be a dead spot in the touch screen, as I can suspend the ball at the apex for an indefinite time.
The problem seems to be that it doesn't trigger the "call answer". It isn't accepting it as an input.
This is repeatable, but once it has "answered" a call, it will generally answer the next few calls accurately.
Click to expand...
Click to collapse
dandan2980 said:
I have the same thing on Nougat and Oreo too can be pretty annoying at times
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I am on T-Mobile and have not seen this happen. Any of you using WiFi Calling, if not try and see if it makes a difference.
Don't swipe up from the icon.
Swipe up from higher up, near the contact picture.
Just like the rest of the google apps, google doesn't use a proper viewport and the coordinates are messed up the essential phone.
Charkatak said:
I am on T-Mobile and have not seen this happen. Any of you using WiFi Calling, if not try and see if it makes a difference.
Click to expand...
Click to collapse
I'm on Metro Pcs which is on the same network as T-Mobile. Some times it takes like 3-4 swipes to get it answer sometimes on the first one and I've actually missed phone calls because it wouldn't answer
I'm not using WiFi calling either
Sent from my PH-1 using Tapatalk
dandan2980 said:
I'm on Metro Pcs which is on the same network as T-Mobile. Some times it takes like 3-4 swipes to get it answer sometimes on the first one and I've actually missed phone calls because it wouldn't answer
I'm not using WiFi calling either
Click to expand...
Click to collapse
This is my second headset and the first one was without this issue. If you have any one with another carrier, try their sim card. This is what I have done with another phone brand when there was an unrelated to your issue.
JCBomb said:
Don't swipe up from the icon.
Swipe up from higher up, near the contact picture.
Just like the rest of the google apps, google doesn't use a proper viewport and the coordinates are messed up the essential phone.
Click to expand...
Click to collapse
It works!! swipe up from near the contact picture.
thanks for the advice.
Pointmaine said:
It works!! swipe up from near the contact picture.
thanks for the advice.
Click to expand...
Click to collapse
Or anywhere in the middle of the screen: swipe up to answer or down to reject a call.
can't answer calls on oreo now
anyone got a fix or workaround ??
This happens to me too. Does the same thing to ignore. I also have problems where I can't hear the person for a good 30 seconds, even though it gives me the ringtone when the call is placed. Sprint says it's not on their end... I've pretty much decided to sell this.
Before this I had Moto G5 Plus which was highly rated as the best budget and it had a ton of issues too. I may buy an iPhone for the first time. I'm just tired of always having an issue with something on an Android device. I just want a product that works 100% of the time.
Pointmaine said:
anyone got a fix or workaround ??
Click to expand...
Click to collapse
I go home and the phone call should appear on the top, then I click answer to get the call
work around from essential
Pointmaine said:
anyone got a fix or workaround ??
Click to expand...
Click to collapse
If you start in the middle of the screen and swipe UP in short strokes, doe this resolve your issue.
I've seen this come up a few times on here and the subreddit and haven't had an issue answering or declining calls :S
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.
Hi guys I'm on Jan update , and the only problem that I have is some times when I call people or someone calls me , the other side can't hear my voice , I wanna know that it's a known bug or it's something wrong with my phone ?! It's so annoying
That sounds like a problem with the phone. We have two A1s and call volume and sound quality are very good. I have not seen many reports of intermittent voice, so would think it may be local to your phone. I may be wrong, and if so, I am sure someone else will correct me.
--KB
KB_Thailand said:
That sounds like a problem with the phone. We have two A1s and call volume and sound quality are very good. I have not seen many reports of intermittent voice, so would think it may be local to your phone. I may be wrong, and if so, I am sure someone else will correct me.
--KB
Click to expand...
Click to collapse
Nothing is wrong with my phones hardware because I can talk with it but sometimes it's not working , I think it happens when I connect it to my gear s3 smart watch! And my phone is always connected to my watch , it has to be a bug nothing is wrong with my phone , hopefully ?
Ah, you did not say anything about the watch in the original post. I don't use smart watches, so cannot offer anything further except to disconnect the watch and see if the problem disappears. If it does, then you will know it is not the phone, but a problem between the phone and watch.
Good luck.
--KB
ho3yn89 said:
Hi guys I'm on Jan update , and the only problem that I have is some times when I call people or someone calls me , the other side can't hear my voice , I wanna know that it's a known bug or it's something wrong with my phone ?! It's so annoying
Click to expand...
Click to collapse
Even I'm facing the same issue and even i have a gear S3. This makes me wonder if the problem is to do with my phone's update or the watch's update??
shubh.pansare said:
Even I'm facing the same issue and even i have a gear S3. This makes me wonder if the problem is to do with my phone's update or the watch's update??
Click to expand...
Click to collapse
It's not a problem with watch I think it's a problem with phone app, when the watch is connected it goes to Bluetooth and then goes back to phone's speaker quickly and there is no voice ! Incoming or outgoing!
Same issue here, often when i make a call the phone seems not Connect and i have to retray the call one o two times to be connected and can talk.
I have the phone connected with Huawei watch 2.
When i receive a call no issue, the bug only in outgoing calls
manuel_fantoni said:
Same issue here, often when i make a call the phone seems not Connect and i have to retray the call one o two times to be connected and can talk.
I have the phone connected with Huawei watch 2.
When i receive a call no issue, the bug only in outgoing calls
Click to expand...
Click to collapse
Absolutely ! And it confirms that the problem is not with gear s3! It's a big bug for this phone with Google's support! Hopefully they know about it and fix it in the next update
Are you sure it's a phone issue and not network related? Have you tried replicating the issue by inserting your SIM in a different device?
Some issue with 2 different operator sim on A1, the same Sim on other device have not this issue
joeyhuab said:
Are you sure it's a phone issue and not network related? Have you tried replicating the issue by inserting your SIM in a different device?
Click to expand...
Click to collapse
Yes absolutely not network problem
Having also problems to make bleutooth call there can't here me. I.m currently on 8.1
Sent from my Mi A1 using XDA Labs