All was fine on Pie, no real call issues. Since I've upgraded to Android 10. I will hit the call button to make a call. it takes like 15 to 20 seconds or more to connect and I see the mute button, keypad, speaker button and so on. Very annoying! Anyone else experiencing this issue? Once connected, all is fine.
Hey, I ran into this issue yesterday, I cleared the phone app cache and data and the issue persisted. I ran a factory reset this morning and the phone calls connect immediately.
Android has come a long way with restoring from the cloud, give it a shot.
Ill let you know if the issue comes back.
Here's your answer, https://www.phonearena.com/news/Fix...xels-updated-to-Android-10-is-a-snap_id118768
That's the fix!!!
spotmark said:
Here's your answer, https://www.phonearena.com/news/Fix...xels-updated-to-Android-10-is-a-snap_id118768
Click to expand...
Click to collapse
That is EXACTLY what the issue was! Thanks for the quick reply!
spotmark said:
Here's your answer, https://www.phonearena.com/news/Fix...xels-updated-to-Android-10-is-a-snap_id118768
Click to expand...
Click to collapse
I can confirm that instantly fixed the problem for me. Thank you.
I just denied phone permission to the My Verizon app - fixed.
Related
As soon as i go to place a call in xdandroid, the call is immediately cancelled! I am on a T-Mobile Touch Pro 2 running the 8/26 build with the sound fix. Anyone know a way to fix or remedy this besides resetting the phone into windows mobile then back to xdandroid??? Thx!
jookdakang23 said:
As soon as i go to place a call in xdandroid, the call is immediately cancelled! I am on a T-Mobile Touch Pro 2 running the 8/26 build with the sound fix. Anyone know a way to fix or remedy this besides resetting the phone into windows mobile then back to xdandroid??? Thx!
Click to expand...
Click to collapse
Nope, you are the only one. Just reset your device
so there is no fix correct?
jookdakang23 said:
so there is no fix correct?
Click to expand...
Click to collapse
No. The only fix is to reset the phone
I've had the same problems before. I did as above, just reset device. Usually put me back in bootloader screen and have to put it on PC to get it out. But I can deal with it
Lord Craigus
Same I have this problem too, Hopefully the developers come up with a fix for this.
I am also having this issue, sometimes putting the phone into flight mode and then taking it back out works, but usually I have to reset the phone... it only happens maybe once a day or every cpl days so its livable for now
I have to add to the fact that I get this same exact issue but noticed that emergency calls will always work and not hang up... I can't call voicemail but I can call 911
starmena said:
I have to add to the fact that I get this same exact issue but noticed that emergency calls will always work and not hang up... I can't call voicemail but I can call 911
Click to expand...
Click to collapse
Hrm... Like the phone is in emergency-only mode... Odd. I've never experienced this issue.
yup, that's exactly what it looks like. I'm thinking that if I maybe put it in airplane mode and then back on it may start working... I haven't had the issue in a while since I make all my calls using WM but I'll report if it fixes the issue in my end..
After 30 minutes of going through posts in this forum trying to look for a solution, and apparently I couldn't find what I was looking for, I've decided to create this post.
Something really weird started happening to my arc recently. Whenever there's an incoming call (call waiting) while I'm talking on the phone, everything gets muted immediately. I cannot hear the other party, and vice versa. Even though I answer the call waiting call, we couldn't hear each other at all. I had to reject the call waiting call in order to be "connected" with the current call again. At first I thought it was some carrier, reception issues, but it's not. The bars were full and I've tried restarting the phone, but it didn't help. I was wondering if anyone has the same issue after upgrading to 2.3.3 and how did you fix this? I didn't notice anything like this before I upgraded. Any help is appreciated!
jerrytea said:
After 30 minutes of going through posts in this forum trying to look for a solution, and apparently I couldn't find what I was looking for, I've decided to create this post.
Something really weird started happening to my arc recently. Whenever there's an incoming call (call waiting) while I'm talking on the phone, everything gets muted immediately. I cannot hear the other party, and vice versa. Even though I answer the call waiting call, we couldn't hear each other at all. I had to reject the call waiting call in order to be "connected" with the current call again. At first I thought it was some carrier, reception issues, but it's not. The bars were full and I've tried restarting the phone, but it didn't help. I was wondering if anyone has the same issue after upgrading to 2.3.3 and how did you fix this? I didn't notice anything like this before I upgraded. Any help is appreciated!
Click to expand...
Click to collapse
I have the same problem. really annoying!
AmitPeri said:
I have the same problem. really annoying!
Click to expand...
Click to collapse
are we the only 2 that has this problem?!
Don't know if it helps but I just wanted to let you guys know I don't have the problem
( open bootloader, flashed prerooted global generic )
jerrytea said:
are we the only 2 that has this problem?!
Click to expand...
Click to collapse
Do you have the Viber app installed? I saw somewhere that some phones react like this because of Viber.
Sorry I don't seem to have noticed that either and I recieved a call waiting bleep while I was on a call just yesterday
I can confirm its the Viber app, I just uninstalled it and the problem is gone!
AmitPeri said:
I can confirm its the Viber app, I just uninstalled it and the problem is gone!
Click to expand...
Click to collapse
Yes, I can confirm this as well, but the problem is fixed on the latest version of Viber. Happy with regular call and Viber now. Thanks to everyone who tried to help
Hey all,
Just wondering if anybody is having a similar issue. Before I get started I did a quick search and havent found any recent threads stating the same issue.
What happens is often I will place a call and immediately switch to speakerphone so I can put the phone down and be handsfree, however for some reason I cannot hear ANYTHING the other line is saying, but they can hear me just fine. Switching back to earpiece does nothing either. This problem has been happening for about a week or so.
The only remedy I have found is to either call back, or reboot my phone but both of these options are unacceptable IMO.
Has anybody else experienced this? If so, what was your solution? I have gone through all the call settings and nothing seems to be out of the ordinary. I don't mute or hold calls and my call volume is almost at max.
Any help or input is appreciated.
Same problem since I went to lollipop. Met a lgcrep who had never seen this
Thanks for the response. It must be a pretty bad software bug then
The problem is with the 3/19 update of the Google search app. Either roll back the build on your phone or disable OK Google from any screen. Same problem exists on KitKat.
OMG thank you so much!
I was starting to think I would never be able to use speakerphone again
Yaminashi said:
OMG thank you so much!
I was starting to think I would never be able to use speakerphone again
Click to expand...
Click to collapse
You are welcome. I almost RMA'ed my phone. Apparently, lots of people have already only to have the same problem as soon as they apply updates.
Here's the apk for the older version. Make sure that you roll back updates to the installed version of Google (and turn off auto-updates) before installation:
http://www.apkmirror.com/apk/google...-app-4-1-29-1706998-arm-android-apk-download/
Same issue
datawrhsdoc said:
You are welcome. I almost RMA'ed my phone. Apparently, lots of people have already only to have the same problem as soon as they apply updates.
Here's the apk for the older version. Make sure that you roll back updates to the installed version of Google (and turn off auto-updates) before installation:
http://www.apkmirror.com/apk/google...-app-4-1-29-1706998-arm-android-apk-download/
Click to expand...
Click to collapse
I had this same issue and disabling the from any screen feature fixed it. I do like that feature however and would like to continue to use it. Do you know if the version in your link supports that function? If not do you know if there's a version that does that does not interfere with speakerphone function?
Thanks.
Anyone else having this problem. It's only just happened. I've unpaired, uninstalled software, done everything I can think of. My phone is connected to it but when I get a message etc it doesn't come up on my watch.
Update
Charlie3999 said:
Anyone else having this problem. It's only just happened. I've unpaired, uninstalled software, done everything I can think of. My phone is connected to it but when I get a message etc it doesn't come up on my watch.
Click to expand...
Click to collapse
I've factory reset my phone and watch. Still not working. A phone call comes up on my watch so it must be a setting I can't work out.
Mine was working yesterday on a stock rooted rom on my phone, but not today on a modified rom. What are you running?
Charlie3999 said:
Anyone else having this problem. It's only just happened. I've unpaired, uninstalled software, done everything I can think of. My phone is connected to it but when I get a message etc it doesn't come up on my watch.
Click to expand...
Click to collapse
Hi,
I also had issues and did not recieve messages on my watch... (see: https://forum.xda-developers.com/huawei-watch/help/messages-arriving-watch-t3510071)
Did your recently reset your phone to factory settings?
Because the new version of Android Wear is asking for permissions to recieve notifications.
I did everything but the solution was simple for me:
Open the Android Wear app and on startup page there should be a blue notification which says something like klick here to enable notifications...klick this button and allow the notification permission and everything should work fine now.
htcdesire-hd said:
Hi,
I also had issues and did not recieve messages on my watch... (see: https://forum.xda-developers.com/huawei-watch/help/messages-arriving-watch-t3510071)
Did your recently reset your phone to factory settings?
Because the new version of Android Wear is asking for permissions to recieve notifications.
I did everything but the solution was simple for me:
Open the Android Wear app and on startup page there should be a blue notification which says something like klick here to enable notifications...klick this button and allow the notification permission and everything should work fine now.
Click to expand...
Click to collapse
Can you post a picture of where you mean. I can't seem to see where you're talking about.
Charlie3999 said:
Can you post a picture of where you mean. I can't seem to see where you're talking about.
Click to expand...
Click to collapse
I meant this notification with the label "Turn on watch notifications". (see attachment)
Charlie3999 said:
Can you post a picture of where you mean. I can't seem to see where you're talking about.
Click to expand...
Click to collapse
htcdesire-hd said:
I meant this notification with the label "Turn on watch notifications". (see attachment)
Click to expand...
Click to collapse
You can also access that in Settings > Apps > Gear Icon (upper right) > Advanced / Special Access > Notification access, then toggle on the Android Wear if it is not on
Thanks a bunch... I went to the app and noticed it said not connected... Touch to reconnect... Had to do that 4x and it finally connected
htcdesire-hd said:
Hi,
I also had issues and did not recieve messages on my watch... (see: https://forum.xda-developers.com/huawei-watch/help/messages-arriving-watch-t3510071)
Did your recently reset your phone to factory settings?
Because the new version of Android Wear is asking for permissions to recieve notifications.
I did everything but the solution was simple for me:
Open the Android Wear app and on startup page there should be a blue notification which says something like klick here to enable notifications...klick this button and allow the notification permission and everything should work fine now.
Click to expand...
Click to collapse
I'm having the same problem only I've done all of the above and it's still not working.
Notifications work for everything except messages and gmail.
It's only been doing it since the watch updated to Android Wear 2.5.
I have reset both the phone and the watch to factory, deleted and reinstalled the apps and still nothing.
bjm374 said:
I'm having the same problem only I've done all of the above and it's still not working.
Notifications work for everything except messages and gmail.
It's only been doing it since the watch updated to Android Wear 2.5.
I have reset both the phone and the watch to factory, deleted and reinstalled the apps and still nothing.
Click to expand...
Click to collapse
Same here after OTA update to 2.5 I can't receive notifications on my watch anymore..had to reset my phone and watch but still not working.
I wonder if there's a way to roll back to 2.0???
bjm374 said:
I wonder if there's a way to roll back to 2.0???
Click to expand...
Click to collapse
I don't know but I wish there was an easy way to go back to 2.0.
Hopefully someone far smarter than me will see this and tell us how easy it is ?
try to "sync all apps" again with the android wear app.. then shut down and restart the watch. This works until I rebooted my phone, then I had to do it again
bjm374 said:
Hopefully someone far smarter than me will see this and tell us how easy it is
Click to expand...
Click to collapse
It's obvious now that the current Android Wear app on the phone needs to be updated to become compatible with the 2.5.
My workaround to this issue was, which I've tested many times and worked so far, finger crossed!:
1-Turn the watch off
2-Turn the Bluetooth off on the phone
3-Turn the watch on completely
4-Turn on the Bluetooth on the phone.
The first notification will take 3-4 seconds to arrive.
Excellent effort. So far that seems to be working for me. I haven't received any messages yet but I'm getting my email notifications (which I wasn't before).
Thank You
hagba said:
It's obvious now that the current Android Wear app on the phone needs to be updated to become compatible with the 2.5.
My workaround to this issue was, which I've tested many times and worked so far, finger crossed!:
1-Turn the watch off
2-Turn the Bluetooth off on the phone
3-Turn the watch on completely
4-Turn on the Bluetooth on the phone.
The first notification will take 3-4 seconds to arrive.
Click to expand...
Click to collapse
That worked for me, thanks.
Oddly enough though, I followed the instructions step by step and actually had a facebook notification pop up on the watch immediately after it powered up but before I'd turned bluetooth back on on the phone!
@hagba Thank you very much those step work. I also noticed that google assistant doesn't work when you send your first query. You have to ask it something, click on the little colored dots then ask it the same thing again and it works. You have to do this everytime you make any request. Annoying. I hope the knuckleheads at Google will fix these annoying issues soon.
snapperheadjoe said:
@hagba Thank you very much those step work. I also noticed that google assistant doesn't work when you send your first query. You have to ask it something, click on the little colored dots then ask it the same thing again and it works. You have to do this everytime you make any request. Annoying. I hope the knuckleheads at Google will fix these annoying issues soon.
Click to expand...
Click to collapse
Myself I have no such problem with the Google assistant, it works fine from the first voice command without touching the colored dots, even "Ok Google" works well.
hagba said:
It's obvious now that the current Android Wear app on the phone needs to be updated to become compatible with the 2.5.
My workaround to this issue was, which I've tested many times and worked so far, finger crossed!:
1-Turn the watch off
2-Turn the Bluetooth off on the phone
3-Turn the watch on completely
4-Turn on the Bluetooth on the phone.
The first notification will take 3-4 seconds to arrive.
Click to expand...
Click to collapse
Worked for me, too. Got a message notification before I turned the Bluetooth back on, lol:good:
Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Maybe give a factory reset a go.
moralesd66 said:
Maybe give a factory reset a go.
Click to expand...
Click to collapse
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
tdetroit said:
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
Click to expand...
Click to collapse
Hard reset....As in power off and on right? Try booting into recovery mode and deleting cache and data.
tdetroit said:
Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Click to expand...
Click to collapse
My TMO one did that today, heard it ringing but screen remained off.
Sent from my SM-N950U using Tapatalk
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
tdetroit said:
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
Click to expand...
Click to collapse
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Maybe the setting for proximity...in pocket...turn off
Limeybastard said:
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
I've tossed the screen protector after 1 day because it kept making a clicking sound on the top corner. No case on it.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
tdetroit said:
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
Click to expand...
Click to collapse
Factory reset , if no go , replacement.
Sent from my SM-N950U using Tapatalk
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
tdetroit said:
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
Click to expand...
Click to collapse
they know absolutely **** about anything
I never use retail store
Another way to fix this is to call yourself on another phone while your Note 8 screen is on. When the call comes in, don't answer but slide down the notification bar and you will see your call. Adjust notifications to not block/be silent.
tdetroit said:
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
Click to expand...
Click to collapse
I went into Settings, Display, but nothing about double tap to wake-up. Samsung runs on AMOLED and that function is on other screens like Sony Xperias.
I do notice another thing going into Notifications settings and I see that the Phone app is Muted. I don't know how to get out of it.
The solution is the person who posted above. You call yourself, and swipe to unblock Silence notifications for your phone app. It's weird how it was set that way, but that's the best solution!
How do I unmute phone call notifications?
Thanks! My incomimg calls now appear on my screen!
I tired the unblock silence notifications and that still has not fixed it as well as a hard reset. Anyone else got any suggestions?
Thanks
Ian
Fix to dark screen on incoming call
Step 1: call youself
Step 2: swipe down on notification bar to view the call(usually how you would answer while dealing with this issue)
Step 3: swipe the call to the right and click the setting wheel.
Step 4: select "do not hide notifications"
Step 5: test call after doing this with the screen off, its should work.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
I turned "block accidental touches" off.
That worked for me!
THANKS