So I have a brand-new att s5. Rooted.
Phone locks after answering and ending bluetooth phone call. I didnt have this problem w the s4. Annoying when driving. Lock timeout is 10 min but it still locks as soon as the call ends via bluetooth (gear)
Anyone else have this happen? Any fix?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Related
This is not a Nexus 4 specific issue, but rather a general CM10.1 issue.
The stock CM10.1 phone app normally does a good job of blacklisting numbers - but when you have the phone connected to a Bluetooth handsfree, and the blacklisted number attempts to call you, then the Bluetooth handsfree will start ringing and it's impossible to stop the ringing unless the caller gives up or you disconnect the Bluetooth.
The handsfree device in question is the Ford Sync system built into my car. Earlier today, I blacklisted the number 6474964196 (for others who live in Toronto, blacklist it too!) after realizing it was a scam to impersonate the bank TD. Later, when I was driving out of the office with the phone connected via Bluetooth, my car started ringing and displayed that very number on my GPS screen as an incoming call. I kept rejecting the call using my steering wheel button, but the caller didn't relent.
The whole time, my phone screen itself did not show any signs on an incoming call. Normally when I drive I keep my phone in the cupholder, and if it gets an incoming call from a non-blacklisted number, the screen turns on and shows me the number along with a big red button to reject the call. But with the incoming call being from a blacklisted number, the screen remained off.
After failing repeatedly to silence that call, I had to wait till I got to a red light so I could manually turn off the Bluetooth. At the same time, I noticed the phone app showed nothing from the blacklisted number in my missed-calls log.
I'll report this on Jira later. In the meantime, does anyone know of an alternative call blacklist app that doesn't allow a Bluetooth handsfree to ring when a blacklisted number calls me?
I previously used root call blocker pro to block calls. I don't use Bluetooth so I can't say if it'll help you out.
You can also add the number to your contacts, then go into the contracts app and have all calls go to voicemail. CM's method is better because it doesn't let them go to voicemail.
Yes, there is a bug in there. I now use root call blocker.
Sent from my Nexus 4 using Tapatalk 4 Beta
I use true caller to block calls. It even has option to block numbers marked as spam by other users
Sent from my Nexus 4 using Tapatalk 4 Beta
Thanks for the suggestions guys. I'll use root call blocker and see.
I just create a contact names no answer and add the number there, with the option to send calls to voicemail. Now my phone won't ring when they call, and when I wipe and flash a new ROM, the blacklist numbers all carry over with my Google contacts. I have about 15 blacklisted numbers there.
Sent from my Nexus 4 using Tapatalk 4 Beta
I'm having an issue where sometimes people cannot hear me on phone calls. It's complete random but does happen 1-2x a day. It's regardless of whether or not I'm on Wi-Fi or carrier data. Or even if I'm dialing or receiving the call. If i disconnect the call and try a second time, it works fine. I've tried searching but the only solutions i found are related to a screen protector blocking the mic (which isn't the issue in my case). Also regardless of whether I'm using the phone, speakerphone, or even Bluetooth, Can anyone help?
Sent from my XT1058 using XDA Premium 4 mobile app
You are not alone. I have been having the same issue on my VZW version. Ppl say that my voice cuts in and out. I can't find a solution anywhere. I'm about to flash the stock firmware(I'm still running stock) and see if that does anything.
As per title, anyone else had this? I tried ringing and receiving calls from both a Nexus 7 (2013), a Moto G and a HTC Evo 3D. Each time i either get a crash (doesn't even say it stopped working just jumps back to my home screen) as soon as it connects or 2-3 seconds after connection.
Yes, i have with the current version the same problem
Sent from my XT890 using xda app-developers app
Phone keep switching between active call & on-hold call? Anyone else? Possible fix?
I have had this problem since I had the phone, I thought with Sense 6 it could be solved somehow. The proximity sensor works just fine, but when I'm having an active call and one on-hold the phone keep switching between the two calls and I find myself talking to the other person and both callers become the wrong person hearing the wrong things.
Anyone else having the same problem? Any possible fix -other than using a headset?
Thanks in advance!
Hello... Anyone?
Sent from my HTC One using XDA Premium 4 mobile app
Hi, I've noticed recently that sometimes when I try to call a number, it does not call; instead the dialpad goes blank. This occurs especially trying to dial numbers from Google maps or from contacts. Does anyone know a solution to this?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
incisivekeith said:
Hi, I've noticed recently that sometimes when I try to call a number, it does not call; instead the dialpad goes blank. This occurs especially trying to dial numbers from Google maps or from contacts. Does anyone know a solution to this?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
No one with that issue?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
I have an issue like that, but the dial pad doesn't go blank. the call just sits there in silence and never connects. I have to toggle Airplane mode to fix it.
I have a similar issue! WHen calling someone it says dialing for like 10 seconds. Sometimes i miss calls because when someone calls me it says the netwrk is busy or something like that,
Not sure why this is happening. The only "system" change I've made is installing themes.
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Has anyone come across a fix for this?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Yes and unfortunately it is that the 3 or 4 of us have defective phones. We need new ones
stu5797 said:
Yes and unfortunately it is that the 3 or 4 of us have defective phones. We need new ones
Click to expand...
Click to collapse
Not sure that's the solution. The issue wasn't present since the day I bought the phone.
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
if i recall, i having this problem on galaxy s5 or note4 edge, cant remember.
when i make a call, i always turn off wifi, it fixed the problem for me.
Did you swap the SIM from your previous phone to this phone without activating the new one? I did this and had issues. I called AT&T, and they said my IMEI from my old phone was showing and not the new one. You might try giving them a call and make sure the IMEI showing on their side is that of your new phone.
I notice that this frequently occurs if I start a call while connected to Wifi and then walk/drive outside the Wifi range. Toggling Airplane mode always fixes it for me.
eventer289 said:
I have an issue like that, but the dial pad doesn't go blank. the call just sits there in silence and never connects. I have to toggle Airplane mode to fix it.
Click to expand...
Click to collapse
I have this exact issue and the airplane mode toggle fixes it. I would like to know what is going on , whether my device is defective or if there is a better fix.
Same issue (not connecting calls, not the screen blank issue)