I've recently migrated an m8 to Lineage from stock. It is currently running lineage-14.1-20171109 (initially lineage-14.1-20171102).
Call answering performs normally when Bluetooth is off or Bluetooth is active with no connected devices. It also works as expected when connected to a Bluetooth headset which can provide phone services. It does not work if any audio is playing when an incoming call arrives (only tested to the same headset).
On call presentation an incoming call alert appears at the top of the screen, which if the answer option is selected then the full incoming call screen is opened. From this screen the selector can be moved to answer or reject, both options having no affect. If Text is selected, then the pre-set text list is displayed but no text is sent if selected. At this point the phone is still displaying that there is an incoming call. This can't be cleared down and opening apps/settings is non-functional. Opening settings presents a blank screen with a white background. The only way to get back to a functioning phone is to reboot. After a reboot some of the app groups and icons on the Home Screen may have disappeared.
I've found some Bluetooth issues reported that look very similar to this problem. In those cases the remedy reported was to turn off Privacy Guard for the Bluetooth apps. I've tried this and have turned off Privacy Guard for all apps, though this does not resolve the issue.
Any help appreciated.
Thanks
Alan
Update:
Having been able to do some further testing with another m8 on the same build and a different Bluetooth device, this problem looks to be app specific. Since un-installing TuneIn Radio Pro I've been unable to reproduce the problem.
Alan
Related
Hi All,
Just the other day my speaker phone stopped working. I can hear the people I am calling, but the microphone doesn't seem to work. They cant' hear me. Not at all, it is like I have the phone muted-- but it is not.
Any body else with this? Any ideas, besides hard reset to try?
Thanks
cameraddict said:
Hi All,
Just the other day my speaker phone stopped working. I can hear the people I am calling, but the microphone doesn't seem to work. They cant' hear me. Not at all, it is like I have the phone muted-- but it is not.
Any body else with this? Any ideas, besides hard reset to try?
Thanks
Click to expand...
Click to collapse
There are loads of software apps that could interfere with sound, have you installed anything recently that you can remember?
have you applied any "tweaks" that you can remember.
Does it only happen when on speaker-phone or during normal calls.
It may be worth removing the back cover to make sure that nothing has interfered with the Mic Mute button on the rear of the device.
Give us some more info an I'll try to help further.
Cheers,
Beasty
Hi Beast0898
Here is a list of software that I have installed in the last 2 weeks:
CarlosP ToneManager
cRaCKwHoRe's Snooze options
merlot mToolbox
Shubaroo Contact Fix
tarkim Keyboard controller.
I had not used the speaker phone for a while. Not since I installed any of the above, so if it is a software interference, it could be any of the above. Ideas?
The mute button is not blocked. And it happens when I enter speaker phone by turning it upside down, and when enabling it with the button on the dialer.
Any ideas?
Did you get it to work? I've encountered a weird problem recently myself where suddenly all system sounds seem to stop, including dialing tones etc.. but if I let the phone go into speaker phone mode, that does work. I hang up the call and suddenly sounds are back.
It seems to only happen when I use Groovefish and/or Nitrogen, so I wonder if one of those is causing some weirdness, just haven't pinned it down yet.
if this is the same bug I had on mine, you can either toggle the speaker phone button twice or do this:-
There is an easy workaround for this problem. On your Touch Pro 2 go to the home screen. Slide to the "Settings" tab. Tap the "Menu" softkey and choose "All Settings". Tap "Personal" then "Phone". Open the "Advanced" tab and change "Reduce noise in phone calls" to "Never".
Reference:-
http://www.chazco.co.uk/post.php?po=38
Here is a fix without turning off noise cancellation.
http://forum.xda-developers.com/showthread.php?t=826396
Hi,
I am having problems with the HTC One X and my car kit. It connects ok and allows outgoing calls no problem. However incoming calls were automatically answered (worked out it is the stock installed car mode),and a message played to the caller "the person you are calling is currently driving". After that, it is not possible to connect to the caller.
I have now disabled the car mode app and done a hard reset. The phone now still works for outgoing calls. It works for incoming calls, provided it is not plugged into the charger.
If plugged into the charger (cig lighter with non-HTC usb cable),hitting answer (whether on phone or car kit) picks up the call and then the audio goes silent after about 2 seconds. The call can then only be recovered by selecting the audio out as handset, and then re-selecting the car kit. After doing that, everything works fine (provided the caller hasn't hung up in the meantime!).
Has anyone else had similar issues? Any ideas are welcome.
I have tried installing no dock and a tonne of similar apps to no avail.
I have tried enabling the car mode app and answering calls through it (but does the same as above - 2 seconds of audio then audio goes until carkit disconnected and then reconnected during call).
I am running a stock phone, not rooted, with 1.26. I am not encrypting the storage or anything else (I notice there have been threads about enryption and bluetooth problems prior to 1.28).
Thanks
TS
You may have solved this by now but I had a similar problem with my One S. It turned out not to be the phone at fault.
In my case the phone would ring once then fall silent and the car audio would go silent while the incoming caller received the message that I was driving. I had not changed any of the settings on my car so assumed that the phone was at fault.
After trying to change phone settings I had a look at the settings for the Bluetooth on the car, where I found a setting for placing calls on hold. I found that this was set on automatic so I changed it to manual and everything worked properly.
What had been happening was that all incoming calls were being put on hold, which is why the incoming caller received the "driving" message. The caller was actually connected but on hold and if I had pressed the button to swap between callers on hold I would have been connected.
It appears that the setting had always been on automatic but my old phone didn't use the automatic call hold function, which is why I only had the issue when I changed to the One S.
Hope this helps.
Posting here since I'm a newb. I recently rooted and flashed a 4.2 ROM to my phone for the first time and I'm having some issues.
First, as many people have reported, I can not receive MMS. I have successfully sent one using ChompSMS, but when I receive one, I get a notification that I have an MMS, and Chomp displays the message size, but it never downloads. I have tried this using WiFi and mobile networks.
Then, a music app (dSub) that used to transmit track information over bluetooth to my car's stereo has stopped doing so. I no longer get the artist, track and album name on my head unit like I used to.
Last, the app automatically reduces volume on music if another sound takes focus (notification, for example). It is supposed to return the volume back to the initial level afterwards, but with this ROM, the phone volume stays very low. Even if I manually change the volume down and back up, or use different apps, or manually kill the music app, the volume is not restored to normal levels until I reboot the phone.
Any ideas on fixing these issues? The ROM has been great and very smooth otherwise.
EDIT - Fixed my MMS issue, I had forgotten to check "auto-retrieve" in the MMS settings of the stock messanger. Still looking for info about the bluetooth and volume issues.
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.
Ok, so found a really annoying issue when the watch is set to play phone audio. Basically when you answer a call or make a call from your phone, the functionality of the screen turning off when you put your phone to your ear no longer works, which means you end up controlling your handset with your ear if you ear touches the screen.
Very annoying!
This only happens if the watch is basically setup as bluetooth audio for the phone (as in you can take calls on your watch).
This was already discussed here:
http://forum.xda-developers.com/huawei-watch/help/phone-audio-proximity-sensor-t3330372
It seems to be a problem in the Google Dialer App. The problem is not present with Samsung phones.
For the moment you'll have to press the power button, to disable the screen. Hopefully a future update of the phone dialer app will fix this, you may support this here:
https://code.google.com/p/android/issues/detail?id=202776
There is an update MHC19J mentioned for the Nexus 5X, which may improve the situation.