Ever since I updated to the latest 13 beta 2, I'm unable to see voicemails in the Google phone app. Worked fine before. P6, T-Mobile. In phone settings it's stuck on activating voicemail. Wondering if anyone else is experiencing the same..
A13 Beta 2 as well with the same issue on AT&T. I'm also enrolled in the beta phone app, so I'm hoping it gets an update pushed at some point that will fix the activation getting stuck.
Beta 2 is extremely buggy.
Related
So this afternoon my Incredible suddenly stopped being able to text. It just keeps getting "Message not sent." Also I cant place any calls or receive them. I dont think this is a Verizon issue because my brother has my old LG Dare and he can text, he even called me and got my voicemail. The phone's 3G is working fine still. Also it says I have service, a couple bars. Anyone else have this issue or know what's up?
I've of course power-cycled a couple times.
I haven't installed anything new today, last thing being Google+ earlier this week.
The phone has been running CyanogenMod 7.1.0-RC1-Inc since it was released, with the regular Cyanogen kernel that comes with it.
Did you pull the battery?
Sent from my ADR6300 using XDA App
Anyone else using Skype and seeing this?
I have a unlocked, none carrier branded Samsung Galaxy Nexus running 4.1.1. Recently when returning to the Skype app home screen from either a message chat, voice or video call my screen started looking like the attachment. There is a ghosting affect going on but it doesn't happen all the time. I also have a few issues where the program just stops working and needs to be restarted and I’m forced to reenter my password. After the restart the app does run normally for a while until I try to chat or make a call. This issue did not happen when I first got the phone running 4.0.4 but has started only a few days ago. It did not start right away when I updated my phone to the 4.1.1 about a week ago. I haven’t installed any programs since this started either, only a few updates for maps, locations services, etc.
I know that this must be an issue with this phone and android build as I do not have this problem on any of my other Android devices running various versions of Android.
No I haven't tried uninstalling and reinstalling the app yet but will if the problem persists.
Okay so i have a T-Mobile S4 it is now running 4.3, The phone was rooted and running the Google Edition custom rom on 4.2.2 when this issues started.
When i first rooted the phone and installed the Google Rom it worked fine, i could send pix to iphone and receive them from iphone (yes ive tested it with many iphone users and its always the same outcome) however a few weeks ago they stopped receiving any pic text i would send and i would receive theirs as well. I have tried this on wi-fi and just on my cellular network and it still doesnt work.
So last night i thought it might be due to the face i need to update to 4.3, so i un-root my phone, factory reset it so its back to 100% stock, update to 4.3 and im still having the same issue. It works fine with anyone using a Android device, but 90% of my friends and my GF have iphone so this is starting to piss me off...
any info would really help me out. and i didnt a search but nothing to the effect of my problem came up...
The problem is not with your phone, its because apple sucks.
Sent from my GT-I9295
When I "Decline" a call, it takes exactly 17 seconds for my "voicemail" greeting to start....So, there's 17 seconds of dead air.
If I let the call ring out and go to voicemail, it picks up immediately.
I've tried At&t Visual Voicemail and Google Voice with the exact same results. I'm on ViperOne 3.1.0, but it also did this on Eragon 8.6 (and ViperOne 3.0.0)
Does anyone else have this issue or is there a setting I need to change somewhere to speed up my declined calls?
tele_jas said:
When I "Decline" a call, it takes exactly 17 seconds for my "voicemail" greeting to start....So, there's 17 seconds of dead air.
If I let the call ring out and go to voicemail, it picks up immediately.
I've tried At&t Visual Voicemail and Google Voice with the exact same results. I'm on ViperOne 3.1.0, but it also did this on Eragon 8.6 (and ViperOne 3.0.0)
Does anyone else have this issue or is there a setting I need to change somewhere to speed up my declined calls?
Click to expand...
Click to collapse
I used to have a lot of problems with AT&T voicemail. Not this exact issue but similar ones.
What I did is returned to stock and the issue was still there so I got with AT&T support and they fixed it on their end.
jollywhitefoot said:
I used to have a lot of problems with AT&T voicemail. Not this exact issue but similar ones.
What I did is returned to stock and the issue was still there so I got with AT&T support and they fixed it on their end.
Click to expand...
Click to collapse
Got any good tech's names?!!?
I was on the phone with them for almost 2 hours Friday, an hour Saturday and about 2.5 hours today and they still couldn't get it fixed.
I thought they fixed it Friday, but it never was 100% fixed.
I just wiped and doing a completely CLEAN install with no restore of any kind... I'll see if that fixes it?
tele_jas said:
Got any good tech's names?!!?
I was on the phone with them for almost 2 hours Friday, an hour Saturday and about 2.5 hours today and they still couldn't get it fixed.
I thought they fixed it Friday, but it never was 100% fixed.
I just wiped and doing a completely CLEAN install with no restore of any kind... I'll see if that fixes it?
Click to expand...
Click to collapse
Haha. Good one. They don't have any good techs (OK, too be fair maybe 1 in 5 are good). I went thru the same crap as you. One of the techs actually made it to where I couldn't even receive any calls at all. That was fun.
They suck, but at least they're super fast too push updated out. Oh wait, no they're not. They suck at that too.
[UPDATE] after another 3 hours of support calls!
So, after another 3 hours of being on support calls...... I finally got At&t Visual Voicemail working on International (Android 5.1) ROM's. They had to completely disable HD Voice (VoLTE) on their end and everything *seems* to be working for now. They said "you should be able to use Google Voice now if you want", but I'm not going to push my luck after finally getting a working voicemail after 7 days of trying.
tele_jas said:
So, after another 3 hours of being on support calls...... I finally got At&t Visual Voicemail working on International (Android 5.1) ROM's. They had to completely disable HD Voice (VoLTE) on their end and everything *seems* to be working for now. They said "you should be able to use Google Voice now if you want", but I'm not going to push my luck after finally getting a working voicemail after 7 days of trying.
Click to expand...
Click to collapse
Yeah, that's exactly how I felt. My issues were about two months ago, so I'm starting to think about trying to get GV working again.
tele_jas said:
So, after another 3 hours of being on support calls...... I finally got At&t Visual Voicemail working on International (Android 5.1) ROM's. They had to completely disable HD Voice (VoLTE) on their end and everything *seems* to be working for now. They said "you should be able to use Google Voice now if you want", but I'm not going to push my luck after finally getting a working voicemail after 7 days of trying.
Click to expand...
Click to collapse
I've been testing the latest version of ICE for the past few days and volte is working again with it and it also included AT&T visual voice mail. Also, I've gotten google voice to work with it as well.
I've had the phone for over a month now, and I've been noticing some weird issues with phone calls across different versions.
I have two issues at the moment:
A call is always starting with the speakerphone on. Even when the speakerphone button indicates it is off. Turning speakerphone "on" and off again will send the audio to the earphone piece.
Conference calling does not work. I get a message about the conferencing failing.
I don't use conferencing a lot, but I was surprised to find such a basic feature broken. This happened on both 8.1 DP2 and 8.1 final. 8.1 DP2 did not have the issue with the speakerphone being on when placing a call.
I actually did a full wipe of the phone after being on DP2 (by removing the phone from the beta program) and then sideloaded the 8.1 update from 8.0 .
This on top of ALL calls coming up as 'HD' when calling non-Tmobile numbers.
Maybe I should be running a T-Mobile specific version of software. This is a Verizon Pixel 2 XL.
Anyone else have issues?
havanahjoe said:
I've had the phone for over a month now, and I've been noticing some weird issues with phone calls across different versions.
I have two issues at the moment:
A call is always starting with the speakerphone on. Even when the speakerphone button indicates it is off. Turning speakerphone "on" and off again will send the audio to the earphone piece.
Conference calling does not work. I get a message about the conferencing failing.
I don't use conferencing a lot, but I was surprised to find such a basic feature broken. This happened on both 8.1 DP2 and 8.1 final. 8.1 DP2 did not have the issue with the speakerphone being on when placing a call.
I actually did a full wipe of the phone after being on DP2 (by removing the phone from the beta program) and then sideloaded the 8.1 update from 8.0 .
This on top of ALL calls coming up as 'HD' when calling non-Tmobile numbers.
Maybe I should be running a T-Mobile specific version of software. This is a Verizon Pixel 2 XL.
Anyone else have issues?
Click to expand...
Click to collapse
I'm on Project Fi and the few times I've used conference calls it has worked. I haven't paid attention to which network I was using at the time though. I tried it just now while I'm connected to US Cellular and it worked. I can try it on T-Mobile when I get home. Don't have service with them here at work. I had the speakerphone issue that you described happen once. I just wrote it off as a fluke. I was on DP2 at the time. I've been on 8.1 stable for about 24 hours now and haven't had any issues with it.
murphyjasonc said:
I'm on Project Fi and the few times I've used conference calls it has worked. I haven't paid attention to which network I was using at the time though. I tried it just now while I'm connected to US Cellular and it worked. I can try it on T-Mobile when I get home. Don't have service with them here at work. I had the speakerphone issue that you described happen once. I just wrote it off as a fluke. I was on DP2 at the time. I've been on 8.1 stable for about 24 hours now and haven't had any issues with it.
Click to expand...
Click to collapse
Is your Pixel a Verizon version?
I rebooted my phone and the Speakerphone issue went away. So it might be a bug that gets triggered by something but cleared with a reboot.
The conferencing does not work after rebooting, unfortunately.
havanahjoe said:
Is your Pixel a Verizon version?
I rebooted my phone and the Speakerphone issue went away. So it might be a bug that gets triggered by something but cleared with a reboot.
The conferencing does not work after rebooting, unfortunately.
Click to expand...
Click to collapse
I have the Google Version.
murphyjasonc said:
I have the Google Version.
Click to expand...
Click to collapse
Thanks. I ended up with a Verizon version, because I wanted the Panda sooner than when Google would ship
Most likely, my issue is related to this, but it shouldn't be. Even though it's a Verizon version, it has never been used on Verizon and has been factory reset several times.
A Phone app update was just installed, but no changes to my issues.
Do you get the HD icon on all your calls?
havanahjoe said:
Thanks. I ended up with a Verizon version, because I wanted the Panda sooner than when Google would ship
Most likely, my issue is related to this, but it shouldn't be. Even though it's a Verizon version, it has never been used on Verizon and has been factory reset several times.
A Phone app update was just installed, but no changes to my issues.
Do you get the HD icon on all your calls?
Click to expand...
Click to collapse
The HD icon is a feature. It only means that you are using VOLTE. This will be enabled when you and whoever you call are both using it regardless if they are on The Mobile or not. Sprint and US Cellular doesn't support this but when I'm on T Mobile it is enabled for me also.
murphyjasonc said:
The HD icon is a feature. It only means that you are using VOLTE. This will be enabled when you and whoever you call are both using it regardless if they are on The Mobile or not. Sprint and US Cellular doesn't support this but when I'm on T Mobile it is enabled for me also.
Click to expand...
Click to collapse
This is not the way things worked on any of my other phones. HD is supposed to indicate the use of the wideband codec in a phone call. Usually this only happens between two T-Mobile customers (other carriers that support this and offer the feature to the subscriber will do the same), and is not restricted to VoLTE in all implementations. Calls to land lines or 800 numbers have never been marked as HD on phones I've used on T-Mobile over the past 8 years.
If you are seeing the HD icon on all your calls when on T-Mobile, but not the other carriers, then the 2 XL is not labeling calls properly. This sounds like a hardware/firmware bug (most likely radio firmware) since my previous Pixel XL behaved properly.
In the end, it's cosmetic, because when I call other T-Mobile users with HD Capable phones, I can tell the call is using wideband vs the more compressed codec.