Develop Bugs

[Q] Caller ID Call Waiting doesn't work!

I have noticed since upgrading to Froyo that my caller ID is broken if I'm already on another call. It's very strange because it only shows the phone number, but after I complete both the calls and go into my call log, the phone is able to resolve the number to the contact.
I've been reading around the net and there's spotty coverage of other people having this issue but no resolution.
Is anyone else having this problem? Anyone else figure out a solution?

No problem with it here, mine has been working fine.

mine does it intermittently

Just as importantly, there seems to be no way to hang up on one call while keeping the other. You can flash between the two, and even merge them, but switching to one and then hitting end hangs up on both. As it stands, I have to let the one call sit until I decide to hang up both.my old g1 had a "switch and hang up" button that you could use to select the caller you wanted to disconnect.

pinetreehater said:
Just as importantly, there seems to be no way to hang up on one call while keeping the other. You can flash between the two, and even merge them, but switching to one and then hitting end hangs up on both. As it stands, I have to let the one call sit until I decide to hang up both.my old g1 had a "switch and hang up" button that you could use to select the caller you wanted to disconnect.
Click to expand...
Click to collapse
I haven't figured this one out either

[Q] Messaging crashes

Hey gents,
After some searching with no answers, I decided to ask the question myself. I apologize if this has been addressed before. I'm currently running a stock r800x with the 2.3.3 ota update. I've had the phone for about six months, but shortly after the update my leading had been acting up. It's almost impossible to send messages now. When the icon is tapped, the window opens but is completely empty for at least 40 seconds. when the keyboard is pressed, it takes another 30 seconds our so and words lag five seconds after key presses (swype and android keyboard). finally, after tapping enter, the message won't appear in the window for some time and I get the "force close or wait" option. After 2 or 3 times touching "wait" and a good 45 seconds to a minute each time, the message will send. I'm at a complete loss here, because I have plenty of space on both my phone and sd card. Does anyone know wtf is going on? Any help would be greatly appreciated and I thank you in advance.

nom nom apple said:
Hey gents,
After some searching with no answers, I decided to ask the question myself. I apologize if this has been addressed before. I'm currently running a stock r800x with the 2.3.3 ota update. I've had the phone for about six months, but shortly after the update my leading had been acting up. It's almost impossible to send messages now. When the icon is tapped, the window opens but is completely empty for at least 40 seconds. when the keyboard is pressed, it takes another 30 seconds our so and words lag five seconds after key presses (swype and android keyboard). finally, after tapping enter, the message won't appear in the window for some time and I get the "force close or wait" option. After 2 or 3 times touching "wait" and a good 45 seconds to a minute each time, the message will send. I'm at a complete loss here, because I have plenty of space on both my phone and sd card. Does anyone know wtf is going on? Any help would be greatly appreciated and I thank you in advance.
Click to expand...
Click to collapse
Do you have a lot of messages in there? The next time you go in try deleting all threads, then make sure to set you limits to 50 messages per thread and 10 MMS per thread. If you have too many messages/threads it takes a long time of the phone to load them, and unfortunately unless you set those options properly the phone has no way to communicate this other than crashing.

My settings were all good, so I decided to bump it down 20 per conversation. It may have had something to do with 58 different threads open and almost 50 messages each :/ . Turns out you even androids need some good old fashioned house keeping. A quick wipe of all threads did the trick. Thanks for helping me out
-jason

nom nom apple said:
My settings were all good, so I decided to bump it down 20 per conversation. It may have had something to do with 58 different threads open and almost 50 messages each :/ . Turns out you even androids need some good old fashioned house keeping. A quick wipe of all threads did the trick. Thanks for helping me out
-jason
Click to expand...
Click to collapse
No prob glad it worked out and that my folly (I battled with this over a week before I figured it out) can help others!

[Q] Dialing takes 2 clicks

Hi! I've noticed, that dialling from caller history or contact details take two clicks. The first click shows the usual optical feedback but does not trigger any action. The second click then starts dialing. In caller history, the first click even resets the contact looked up by vanity dial to the last called contact. Looking it up again, the next click starts dialling. Weird behavior that is!
Any one else got that too?
Using carrier unlocked stock rom 1.32.x base. The only app that might have sth. to do with it is Avast security. But no settings there. Any help is highly appreciated!

Call transfer problem

Greetings!
I'm wondering if anyone has the same problem as me, and maybe someone already has a solution for it.
When there is an incoming call, my phone rings and my watch too. I take up the phone and slide to answer the call, the phone stops to ring but the watch continous to buzz, and the phone won't take the call just hangs there and shows there is a call , 5-10 seconds after I pressed the anwser on the phone, THAN it picks it up, and now I can talk.
If I slide to answer on the watch it transfers to it.
I don't why it does this...
I have an LTE version, with the same phone number as in my phone ( I have a Note 9).

sortilego said:
Greetings!
I'm wondering if anyone has the same problem as me, and maybe someone already has a solution for it.
When there is an incoming call, my phone rings and my watch too. I take up the phone and slide to answer the call, the phone stops to ring but the watch continous to buzz, and the phone won't take the call just hangs there and shows there is a call , 5-10 seconds after I pressed the anwser on the phone, THAN it picks it up, and now I can talk.
If I slide to answer on the watch it transfers to it.
I don't why it does this...
I have an LTE version, with the same phone number as in my phone ( I have a Note 9).
Click to expand...
Click to collapse
I have the same problem and I only have the 42mm BT model. It's annoying

cwb1231 said:
I have the same problem and I only have the 42mm BT model. It's annoying
Click to expand...
Click to collapse
And do you have a clue of why it does it? Or have you considered to send in to repair?

sortilego said:
And do you have a clue of why it does it? Or have you considered to send in to repair?
Click to expand...
Click to collapse
I am very careful to not answer on my watch and hope the call goes though! I have turned phone off and watch off and that seems to clear it for a bit

sortilego said:
Greetings!
I'm wondering if anyone has the same problem as me, and maybe someone already has a solution for it.
When there is an incoming call, my phone rings and my watch too. I take up the phone and slide to answer the call, the phone stops to ring but the watch continous to buzz, and the phone won't take the call just hangs there and shows there is a call , 5-10 seconds after I pressed the anwser on the phone, THAN it picks it up, and now I can talk.
If I slide to answer on the watch it transfers to it.
I don't why it does this...
I have an LTE version, with the same phone number as in my phone ( I have a Note 9).
Click to expand...
Click to collapse
carrier issue id say.
do you remember if your carrier assigned a dummy phone number to your watch? because the watch can receive and make calls with the same number that ure phone has but its basicaly like a call forward. from the description of your problem, it would seem the carried might have activated the esim and put the phone's actual number instead of an other number. When i consult my online profile from my provider and see my plan and data usage, the phone has the original phone number as supposed and the watch has a random phone number that is just a dummy one and isint really usable.

Question Incoming calls take seconds to show

Has anyone else had this issue where you can hear the phone ring but it takes 5 to 10 second to see the display in order to answer?

Yes, had the same, no idea

Had this before,
Do you have more than two Google accounts on the phone? Try to remove one and see if it solves it.

No only one G-account

I have seen this issue. I think for me turning off adaptive battery for apps solved this for me. What annoys me the most is trying to hang up calls, where it takes over 3-5 seconds for the phone to respond to hang up, and multiple presses on hang up before it does, 9 times out of 10 the other end hangs up

danw_oz said:
What annoys me the most is trying to hang up calls, where it takes over 3-5 seconds for the phone to respond to hang up, and multiple presses on hang up before it does, 9 times out of 10 the other end hangs up
Click to expand...
Click to collapse
Have this as well, I've got my power button set to end calls and even that doesn't work

I've had this problem with my Note 4 a few times but I believe I had Power Saving mode turned on.

Is the call screening feature enabled?

I have the same issue ONLY when I have more than one Business Google accounts on the phone.
If I have multiple simple Google accounts and one Business G account then No Issues.
Adding one more Business G account triggers the delay.

Actually to be honest, you should try enabling the VoLTE on your phone. Pixel phone needs internet to be working for all services and apps to run smoothly. When an incoming call appears, it usually tries to grab the info from internet if the caller is a known profile. It used to happen with me, until I rooted and enabled VoLTE using magisk module because unfortunately my country is not supported for voice over LTE services on Google Pixel handsets.