Database Users

"Cannot complete the call. The Signal ma be unavailable

I sometimes get on my exec the following message when I'm hyst trying to make a REGULAR NORMAL ORDINARY phone call to any of my contacts:
"Cannot complete the call. The signal may be unavailable or the phone number may not be valid. Verify the number and try again later."
This bull**** also happened to me before ocassionaly on my old i-mate PDA2K. Driving me nuts, can't make a phone call till a soft reset is made. Making the phone flight mode on/off doesn't fix it.
WTF is wrong? Why does the machine gets confused. Today I had to make an urgent phone call and this **** happened and I lost some business. This machine is simply not as reliable as a phone.

same thing here....Imate sucks.
Ya, I'm getting the same thing here too. I miss calls and have to frequently press redial, as to redial the same number, since it incomprehensibly couldn't dial it. I've got the latest update.
Unfortunately for me, my unit is an Imate and their support "services" SUCK big time.
Paid $1000.00 dollars for this unit and get even get $2.00 service.
IMATE Sucks!

hmm
has similar problems..
using vodafone i noticed it was trying to connect to 3G et.. so i changed Band settings..
select network type to GSM instead of Auto.. i now see a nice G instead of a U next to my vodoafone connection signal thingy..
and all seems to work great again!!
let me know if that solved your problem :lol:

not so sure whether it's relevant or not, but since I removed all "hooking" applications like Smart Filter, ReDial, and calls time monitors ... etc and this issue didn't happen except once during a full month ...
I think those applications suppliers have to do more than just re-compliling their S/W to claim it's WM5 compatible!

Voice dialing

I'm wondering if anyone is working on improved voice dialing capabilities for the G1? I see in the 1.5 update that it says something about improved voice recognition, but I can't tell if that applies to the voice dial problem. That problem being that the way it is now, you have to touch the phone to place any call other than redial. Is this an android issue or a T-mobile issue?

Just a bump... really? Nothing?

Voice dialing on the G1, in my opinion, is still pants. I am using JF 1.5 and voice dialing works sometimes, but not enough that you can rely on it. Since it is in the 1.5 developers release I would have to say it is a Goggle, not carrier, problem.
- The voice recognition is spotty at best. "Call voice mail" Gave me voice mail as an option but I had to click on the screen to choose it. Worse yet the first choice in 1 out of 3 attempts was "call Oscar on Mobile".
- As far as I know you can not set up voice dial to start by hitting the call button on your BT headset. So you have to pull out the phone to initiate a call.
- Even if you could initiate a call via your headset Android does not give you any audio cues as to whom it decided you are trying to call. i.e. machine generated "call voicemail?" then you say yes to dial them.
On the other hand voice search capabilities did improve quite a bit and it is actually useful now. It is often easier for me to initiate a search by simply saying it then whipping out the keyboard.

Maybe I'm just not up on the lingo, but I'm not sure what "is still pants" means, unless it's a typo.
The voice recognition is okay, the times I've used it it hasn't made any mistakes, unless I'm trying in a very noisy area. For the numbers I call often, I find that putting a shortcut on the homescreen helps, but voice prompts are necessary and this should be addressed. If it is a google issue, do you have any thoughts on how to voice this issue to the proper place?

[Q] Fingerprint Lock + Bluetooth Dialing

Since I have enabled the fingerprint lock I can no longer do voice dialing from my bluetooth device (until I unlock it first). Has anyone else encountered this?

Yes. It's been fairly common on smartphones over the past decade or so to not allow voice dialing when pin locked (or in this case, fingerprint). Not sure why.
So far I haven't looked into alternatives...I just don't voice dial when it's locked (or unlock it first).

yea i figure this too that sucks TBH perhaps if you can dial would be a "bypass" of security so maybe thats why, you should have a option to enable this as feature

Yes, especially frustrating when you live where it is not legal to talk on the phone without a hands free device!

It worked fine on my BlackBerry Tour... bummer. Any workarounds for it?

A little googleing reveals that on some Androids it apparently works, as it does on iPhone. Hmmm... starting to wonder if I chose the right phone.

Voice Dialing without unlocking phone
Has anybody found a workaround for this yet?
This has been getting particularly annoying as of late - both in the car and on foot. What's the point of voice dialing if you have to pull out the phone first? BT headsets must be pre-synced with the phone, so allowing this isn't even that significant of a security breach, unless you lose your BT headset along with the phone.
Do we even know what component prevents us from voice dialing when the phone locks? Is it part of the lock screen? Of the android kernel's security? Or is it a hidden setting/permission that perhaps a more experienced developer can help us find? I don't know enough about Android yet to even begin to know where to look . . .

It annoys me the most when double click my bluetooth for redial but it doesn't respond...
Sent from my MB860 using XDA Premium App

AlonFW said:
It worked fine on my BlackBerry Tour... bummer. Any workarounds for it?
Click to expand...
Click to collapse
I use the 'delayedlock' app to unlock the phone when it detects my BlueAnt S4 is connected. Works fine. The phone relocks itself once the S4 is disconnected.

cmccabb,
Thanks, I will check that out. I assume you use the Bluetooth plugin for "Delayed Lock?"
Maybe once our phones go to Gingerbread we this will be fixed. Maybe.
Alon

AlonFW said:
cmccabb,
Thanks, I will check that out. I assume you use the Bluetooth plugin for "Delayed Lock?"
Maybe once our phones go to Gingerbread we this will be fixed. Maybe.
Alon
Click to expand...
Click to collapse
Yes. I also use the wireless plug in to keep it unlocked at home.
Sent from my MB860 using XDA Premium App

i have the same problem. ive always used the fingerprint, but it wasnt until i got new BT headset when it started. so it could be the headset also. My old one would do voice commands when locked. im gonna search for that app too see how it works.

Just off the top of my head:
If you have Tasker, you can set it to deactivate the screen lock when a bluetooth device is connected.
Create a new profile
Select state > Bluetooth connected
New Task > Display > Keyguard > Set Off
Then you can set an exit task to turn the keyguard back on

This is now fixed in gingerbread.
Sent from my MB860 using XDA Premium App

Actually mine went from working in 2.2.2 to now not working in 2.3.4... screen flashes a bunch of times but wont unlock... cant bluetooth call unless I unlock the phone first. This is very annoying!

It should be a bug at some custom ROMs. You may try to flash the Custom ROM "CherryBlur 1.4d", the bluetooth dialer is still alive. However, it has battery drain issue. The battery may support around 12~14 hours even you switched to the maximum battery saver mode.
p.s. assumed that you have to enable the "Allow Bluetooth bypass" option in the system setting.
http://forum.xda-developers.com/showthread.php?t=1160649

Running stock Gingerbread. I frequently use Bluetooth with no problems at all. I use fingerprint sensor all the time. Never need to unlock to receive an incoming call.

On Alien #4 - and in Stock too, I think - I've got the option to "Bypass over Bluetooth" as last menu entry in the lock settings. Do you have that menu point and have you tried that?

Problem at Bluetooth Voice Dialer - Solution Found
Dave__C said:
Running stock Gingerbread. I frequently use Bluetooth with no problems at all. I use fingerprint sensor all the time. Never need to unlock to receive an incoming call.
Click to expand...
Click to collapse
Yes! The bluetooth headset may redial the last outgoing call and receive the incoming call without any problem. But it cannot wake up the phone when you activate the bluetooth voice dialer in some Custom ROMs.
Finally, I identify that the issue was caused by the overclock kernel. Because "CherryBlur 1.4d" includes the standard kernel without any overclock / under voltage setting, the bluetooth voice dialer can operate perfectly.

[GSM User] Call audio quality poor on other person's side

Hi guys,
First of all, I'm a GSM user running the latest OTA stock ROM and Baseband.
So I've been making more calls lately, and I keep getting complaints from people saying my voice is unclear and breaking up on them. I decided to do some experimenting, and have come to the conclusion that it is not my SIM, phone's mic, ROM, or the other person's problem.
I've noticed, when calling from my Razr M to another phone (let's call it Phone2), if I set Phone2 to mute, then my voice is heard perfectly fine on Phone2. If it's not muted, then Phone2 can barely hear what I am saying from my Razr M. The whole time, anything the person says into Phone2 is heard crystal-clear on my Razr M
I know it's not my SIM card is because I just went to the AT&T store today and replaced it
I know it's not the mic is because if I use GrooVe IP to place the call via VoIP, everything is heard fine on both ends
I know it's not the other person is because I've had at least 4 different people tell me they can barely hear me on their phones, and I've tested it myself by calling the other phones in my AT&T family plan, and my landline, and the issue still occurs.
I found that changing
Code:
persist.audio.mic=digital
to "analog" instead, helps a little because it makes the voice louder, but it doesn't help with the audio breaking up.
Reverting back to the older baseband (the one that is included in Matt's Utility 1.20) doesn't make a difference.
Does anyone else have similar experiences? Ideas for me to try? I'm especially curious to hear from other GSM users.

Google Voice not working

I'm not sure what is happening here but i can't get my phone to place calls via Google Voice. Anyone else use Google Voice on their stock G6 successfully? If I dial a number the stock phone dialer calls the GV relay number but I never hear it ring on my end. If they answer I can't hear them either.
I'm on software version h87211g on T-Mobile. Completely stock phome. Did the BOGO deal and the problem happens on both of these phones.
I've been using GV for years and never experienced this. It works as it should on any other phone I test it on. LG Stylo 3, Galaxy S9, S9+ Note5, erc...
I can factory reset this phone, install Google Voice and no bueno. Can't make calls with GV.

Just tried again. Reset and wiped the phone to factory stock and did default setup. I let Google and LG do whatever updates it needed to do. Everything works perfectly. I went to the play store and downloaded Google Voice and setup normally and have it set to use my GV number to make all calls as I always have. Try to make a call and it never rings. The receiving line will ring but when they answer no audio is passed through.
I just grabbed my old Note 5, reset it back to stock and did the same process. Installed Google Voice and it works perfectly. Also grabbed an old LG F3 I had in a drawer and it worked on it also. Seems to be some combo issue with this dialer, maybe VOLTE and who knows what. It doesn't seem to make a difference if I have VOLTE on or off or if WiFi is on or off. It just doesn't work for me on this phone.

cahiatt said:
Just tried again. Reset and wiped the phone to factory stock and did default setup. I let Google and LG do whatever updates it needed to do. Everything works perfectly. I went to the play store and downloaded Google Voice and setup normally and have it set to use my GV number to make all calls as I always have. Try to make a call and it never rings. The receiving line will ring but when they answer no audio is passed through.
I just grabbed my old Note 5, reset it back to stock and did the same process. Installed Google Voice and it works perfectly. Also grabbed an old LG F3 I had in a drawer and it worked on it also. Seems to be some combo issue with this dialer, maybe VOLTE and who knows what. It doesn't seem to make a difference if I have VOLTE on or off or if WiFi is on or off. It just doesn't work for me on this phone.
Click to expand...
Click to collapse
That is very odd. I also have the h87211g and Google voice works flawlessly. Can you try calling once from the dialer within the Google Voice app and see if that works?

nikhilrathi10 said:
That is very odd. I also have the h87211g and Google voice works flawlessly. Can you try calling once from the dialer within the Google Voice app and see if that works?
Click to expand...
Click to collapse
Didn't work. It brings up the stock dialer, calls the relay number then no audio. Person called does receive the call but they can't hear anything and it never tells me the call connected on my end.
I found an older version of GV from January and get the same issue. Just installed Hangouts and the Hangouts dialer and it will make calls fine.
I can receive calls fine on GV also. Just cant make them. Two brand new and identical G6 doing this.
I'm going to stop by the TMO store and get a new SIM just to try anything at this point.

I had to use hangouts dialer

Spookymyo said:
I had to use hangouts dialer
Click to expand...
Click to collapse
Google voice not working on your phone either?

Got new SIM. Same issue.

cahiatt said:
Google voice not working on your phone either?
Click to expand...
Click to collapse
Yes it's working. I could always send texts but to be able to make calls I had to download the Google Hangouts dialer.

Finally got it to work. Ended up giving the G6 to my wife who doesn't use Google Voice and took her S9 which she complained would drop calls
Now both our problems are solved. I have a properly working Goole Voice and she says the call quality is better. Bigger battery is a plus for her too. Not sure how but she can put in a good four or five hours talking to ONE person.

cahiatt said:
Finally got it to work.
Click to expand...
Click to collapse
Sounds like you didn't actually get it to work, you just worked around the problem
I'm on AT&T and GV calling works fine for me. So I can't provide any direct data here and I don't have any need for a solution. But I would still prefer to see an explanation for why this wasn't working (and preferably a fix) since it could help others who are affected.
What I would have suggested is: manually call into your own GV number and hit the button when it answers (* or #, I forget which) that lets you get in and listen to messages and make calls. Try dialing out from that menu and see how it works. Also, you didn't mention whether you had the same problem regardless of who you called, or whether you were able to test from different locations (and thus using a different cell tower).
It seems most likely that there is some issue with the G6's implementation of VoLTE (and possibly only in your area). The only place I know I have made GV calls, I often won't have an LTE signal so I can't confirm whether it works over AT&T's VoLTE, but it would be even more interesting if it did not.

jdock said:
But I would still prefer to see an explanation for why this wasn't working (and preferably a fix) since it could help others who are affected.
Click to expand...
Click to collapse
I'd love to get to the bottom of it. I'll test it again when and if another system update comes out for this thing. I've added a few more things I've done to see if I could figure it out. The only thing I haven't done is try a SIM for a different carrier such as ATT or Cricket. The results of any test were the same. Outbound calling through Google Voice would never ring on my end and I could never hear anything. Two different G6 phones, brand new, stock, etc...
I tested on Wifi, regular LTE, VOLTE on or off. Same results. The other party may or may not be able to hear me or it may or may not even ring on their end. No particular setting with regard to being on wifi, LTE, VOLTE on or off made any consistent difference. Inbound calling always worked fine.
I also downloaded and installed a modified Pixel phone dialer to replace the LG version. I was hoping it was some bug in their dialer doing this. The dialer worked on my Note5 and S9 and worked on the G6 when installed also. Once setup and working I put Google Voice back on and tried to make a call. Same issue. It will not ring on outbound and if someone did answer, I couldn't hear them.