Related
Randomly when I make calls or receive calls I have no sound. I can't hear them and they can't hear me. Rebooting the phone will fix the issue for a short while. I have been able to reproduce this by connecting to my cars blue tooth and making a call. The 1st call works however all calls after the first call I have no sound again. When the phone in the no sound state (Phone Call) Bluetooth media still works just no sound while in a call. The speakers work because I can play music and the mic still works because I can still record sound. This issue seams to be related to the phone app its self???
My phone is a Samsung S4 (AT&T) with Android 4.4.2 (Rooted via Towelroot) with SuperSU by chain-fire installed.
Here is some of the trouble shooting I have already done.
1. Factory Rest the Phone via Stock Recovery (Still can reproduce the issue)
2. Played around with various settings i.e. Google Now Bluetooth options. Un-paired all Bluetooth devices and then re-paired one to try (Still having same issue)
3. Cleaned out all app cache (Still having same issue)
4. Re-installed pre-installed apps that I removed once rooted.
Long story short, this one has be baffled. The only thing that fixes the issue is re-starting the phone.
Thanks in advance for any assistance
AG007
Same Problem Here, I may have figured it out:
After I rooted I used some apps to auto kill some running, supposedly non-essential apps. This caused my phone call problems, same exact issue as you're having. A reboot fixed it for me as well. I will let you know if it happens again without closing any apps.......
[Q] Viber speaker phone always on -[ROM]【5.0】Google Play Edition【LRX219】-12-24-2014
@Danvdh and team
Simply thank you for this gift. I have on issue with Viber app that I like to share:
I am using the ROM from this page:
http://forum.xda-developers.com/showthread.php?t=2557353
Clean installed with TWRP with phone setup as new.
1. When I call someone through viber app and or receive a call through viber, speaker phone is always on and I cannot turn it off. Has anyone else have this issue and resolved it or is it some settings that I may have mistakenly ticked off?
See the attached screen shot of the viber call and you will notice that the speaker icon it greyed out and it is always greyed out. I cannot turn it off as it is greyed out.
Please help????
Apologies to bump my post here.. this is an issue here and I am hoping some one can help me. Any viber call is always on the speaker phone. How can I make viber call normally please.
Mobile phone calls work perfectly,
quick workaround
hannah187 said:
Apologies to bump my post here.. this is an issue here and I am hoping some one can help me. Any viber call is always on the speaker phone. How can I make viber call normally please.
Mobile phone calls work perfectly,
Click to expand...
Click to collapse
Hello, hannah187. I had the same issue. Just reinstall Viber and the problem will be gone. I just don't know for how long.
I'm a bit worried because I've never had such problem with the stock ROM. It's important to keep this topic alive until we have a real fix.
Thanks.
rlauritzen said:
Hello, hannah187. I had the same issue. Just reinstall Viber and the problem will be gone. I just don't know for how long.
I'm a bit worried because I've never had such problem with the stock ROM. It's important to keep this topic alive until we have a real fix.
Thanks.
Click to expand...
Click to collapse
First of all, my issue is fixed now but strange fact is I did not reinstall viber. It's just fixed now. I understand that code does not lie so perhaps I have changed some settings which may have fixed it but honestly I do not know.
I know that when I did a clean install of this ROM, viber was working correctly and I have checked it. After couple of days, I can no longer make viber call through ear piece. I only can use speaker phone.
I do not think I have changed any settings, but viber now seems to work as expected and I can make viber phone calls normally as well as through speaker phone. I do not know how this has happened.
Well it seems that I have spoken too soon. From last night, viber speaker phone icon is again greyed out, in other words, I can only make the Viber phone calls through the speaker phone and no ways to disable it. Back to square one.
Happy New Year, @Viber Team!
???????????????
funny that ...is that going to fix it
Hi.
I have similar issue with the latest version of viber at my samsung galaxy s4 i9505 android 5.0.1
When i receive or make a call with phone NOT viber the speaker turns on itself until i press the speaker two times so i hear the call not from the speaker.
I understand that it was viber fault because when i completely uninstall the viber never had this issue again.
So is there any solution so we can have viber installed without that kind of issues?
Whenever I connect to one of my Bluetooth devices it shows that it's "Connected to xxxxx" in the secondary screen.
However, after I disconnect from the Bluetooth device it still says its connected in the secondary screen and the secondary screen just hangs there frozen saying its connected. I can only get rid of it by restarting the device.
Anyone else having this issue?
I'm experiencing this issue. I think it started happening after applying the latest update.
to fix it w/o restarting the device, you can go to settings - display - second screen and turn off 'show when main screen on' and back on.
I have this and all kinds of BT issues with my car.
Bluetooth has given me a lot of problems. Secondary screen stuck displaying the "connected" message, Bluetooth crashing, and high CPU usage when not connected. I've had better experience by toggling Bluetooth off and on with Tasker after disconnecting from my car. Figure it gives it a kick causing it to play nice.
McNutnut said:
Bluetooth has given me a lot of problems. Secondary screen stuck displaying the "connected" message, Bluetooth crashing, and high CPU usage when not connected. I've had better experience by toggling Bluetooth off and on with Tasker after disconnecting from my car. Figure it gives it a kick causing it to play nice.
Click to expand...
Click to collapse
So it's not just me having bluetooth issues lately. I was getting ready to drop by AT&T because of all the problems it''s been giving me lately connecting to things on bluetooth...
Mine has recently started doing the same thing with second screen stuck on connected to vehicle Bluetooth. I do remember updating recently so I am unsure what cause this issue. I am using stock with ATT
peekeesh said:
to fix it w/o restarting the device, you can go to settings - display - second screen and turn off 'show when main screen on' and back on.
Click to expand...
Click to collapse
I tried this trick and it only works temporarily. After an hour or so the same connection message will appear even though I'm not connected. So annoying. Come on LG! I like their devices but there is always some annoying issues with their phones.
Are you guys also experiencing general notification issues?
Example, I click on a Twitter or Kijiji notification and the app won't open or I can't respond within the notification shade any more.
See https://forum.xda-developers.com/showpost.php?p=72734315&postcount=10
I'm wondering if this is the cause of everyone else's bluetooth/notification issues. Worth a shot.
Ever since I upgraded to 10K from 10J on T-Mobile it has started doing this. Once I am connected I never have a problem with Bluetooth but connecting has been inconsistent ever since upgrading. My car stereo for example used to connect automatically now to get it to reconnect I have to turn off the stereo and the Bluetooth radio on my phone and then both back on @ same time otherwise I have to manually connect through the phone BT menu
Been having issues with bluetooth too. I've gotten into the habit of just turning it off after I get out of the car, then turning it on right before I get back in the car. If I leave it on all the time it fails to connect about half the time I turn on the car, if not more. Strangely I don't have the same issue with my Anker speakers, so I sort of assumed the car was the problem, but it seems not from these comments
McNutnut said:
See https://forum.xda-developers.com/showpost.php?p=72734315&postcount=10
I'm wondering if this is the cause of everyone else's bluetooth/notification issues. Worth a shot.
Click to expand...
Click to collapse
This seems to have fixed it for me! I had the same issue after updating my phone to the latest build.
thisisjason said:
Been having issues with bluetooth too. I've gotten into the habit of just turning it off after I get out of the car, then turning it on right before I get back in the car. If I leave it on all the time it fails to connect about half the time I turn on the car, if not more. Strangely I don't have the same issue with my Anker speakers, so I sort of assumed the car was the problem, but it seems not from these comments
Click to expand...
Click to collapse
Same exact issue. It only seems to happen to my car stereo since I upgraded to 10K. But my other speakers and headsets 99% of the time it will connect by itself.
Same issue here. Super annoying. Appears to have shown up around the same time that all my notifications stopped working.
I've been having the same issue. I use Car Home Ultra, and noticed that it was very delayed starting, and would start randomly even after leaving my car/disconnecting bluetooth. I thought it was a problem with that app, but now it appears it's that the phone is delayed in notifying of bluetooth connect/disconnect.
I constantly have the "connected" notification taking up the second screen until I reboot.
I am experiencing this aswell, and , when connecting to my SYNC 3 in my Ford Focus, it says connected, but it isn't. If someone rings me, the hand set rings.
It seems to be the initial handshake, if the phone's bluetooth is off when i turn car on, then i turn blutooth on and select "sync 3" it's all good, but if bluetooth is already on , and i switch car on , i get the message on the radio it's connected to my phone... but i cant access contacts or messages ( even though they are ticked in bluetooth menu )...
lucky for the 2 year warranty...
Disabling the Google app has fixed this issue and fixed my push notifications. Not ideal but doesn't appear any other answer exists.
Anybody have any updates on this issue? I have been having the connected message showing more frequently to my vehicles. I have been turning off second display and back on to remove. Thanks for the suggestion Adam about disabling Google app but like you said it is not ideal.
So on Verizon they just pushed a system update. Post update, I enabled Google app, and everything appears to be working great thus far.
I don't remember when but the issue just kind of went away without any action on my part. Maybe it was an update?
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 folks,
I'm kinda new to the Mod community. A few days ago I successfully flashed to LineageOS 17.1 to receive security patches and get rid of the google services. Phone runs smoothly and nicely. Now there is just one annoying issue: Whenever I activate the loudspeaker in a voice call the call receiver doesn't understand me anymore. It seems like the microphone gets super silent. This happens in apps like Threema and WhatsApp.
Regular calls and voice recording work without any issues.
What have I tried so far to solve the issue:
Editing build.prop with commands I found on the internet
Activating different sound fixes using Magisk modules
Re-installing chat apps
Am I the only one with this problem? Do you have any other suggestions?
Greetings,
O.
Owei1337 said:
Hi folks,
I'm kinda new to the Mod community. A few days ago I successfully flashed to LineageOS 17.1 to receive security patches and get rid of the google services. Phone runs smoothly and nicely. Now there is just one annoying issue: Whenever I activate the loudspeaker in a voice call the call receiver doesn't understand me anymore. It seems like the microphone gets super silent. This happens in apps like Threema and WhatsApp.
Regular calls and voice recording work without any issues.
What have I tried so far to solve the issue:
Editing build.prop with commands I found on the internet
Activating different sound fixes using Magisk modules
Re-installing chat apps
Am I the only one with this problem? Do you have any other suggestions?
Greetings,
O.
Click to expand...
Click to collapse
I've noticed this issue when downloading or using the google dialer app. If I use the android default dialer there is no issue.. Let me know if you found a fix in the end.
Sent from my PH-1 using Tapatalk
same issue in Lineageos 17.1
Hi,
I have same microphone issues in phone calls and voice calls in whatsapp. This also happens during a video recording in Essential camera or Gcam app.
But the sound of the microphone is good in the tape recorder application included with lineageos.
This is a bug that the essential team had fixed but which is present in lineageos since android 10.
Please report issue on https://gitlab.com/LineageOS/issues/android/-/issues/2209#note_378544829 , this will allow the information to be passed to lineageos developers.
Thanks
Still no fix? Microphone on loudspeaker still doesn't work at all in voice chat apps like WhatsApp. Also the microphone quality without loudspeaker is very underwhelming. Call partner are complaining constantly
Do we know how the Essential devs fixed the problem after android 10 update?
bump...
still with problems :C
I've tweaked around with several XML-files. Still no fix for me. Voice calls (WhatsApp, Telegram, ...) with loudspeaker on are still not working.
In the meantime several other people out there confirmed the error on GitLab:
https://gitlab.com/LineageOS/issues/android/-/issues/2209
But it seems like the critical mass is not yet reached
I've loudspeaker but work weird, microphone don't work or work very low, my problem is mainly can't lower the volume on videocall.
Could this problem be something out of lineageos? Like something missing of base ph1 system?