I don't know where to really put this since this is happening to all of my devices i own thats 6.0 and higher. When ever i make a call on google hangouts. (actual phone call not hangouts audio call) soon as the screen shuts off the audio goes mute and the mic gets shut off as well( other arty cant hear me). thought it was my galaxy S6 until i updated my LG G4 to 6.0.1. both devices are 6.0.1 and do it. my note 4 on 5.1.1 doesnt do it nor does my S4 zoom or iphone 5s. All devices are running stock with no root. All are up to date as far as applications go as well. I honestly don't know whats going on, even logcats aren't helping. I've given the applications all the permissions they require, so im i'm baffled as to why this is happening. I cant just use the regular call function because im on TMOs 30 dollar plan.
I guess no one is going to answer?
Try and wipe cache and data on your hangouts application
Sent from my GT-I8190 using XDA-Developers mobile app
Related
So I installed nettalk voip app on my tablet it installs but it has the same issues with voice calling with fring. I mean this app would be great for us G tablet users cause we lack phone cababilities. What needs to be fixed so this app would work flawlessly? I would love to use this app cause its like the magicjack of android... Well until magicjack releases there android app which they stated it would be released in september of this year
I tried sipdroid and imsdroid. Neither work.
Also stremfurious doesn't work. It keeps reporting broken pipe and freezing.
It's like the network is going up and down, or the connection status is not being reported properly.
Voip Gtablet
I have Skype and IAXagent working, but unable to get audio to my bluetooth headset.
very possible @op. install sipdroid and let it make you a new pbxes automagically and have gv installed. i treated my viewsonic like a project and first testing requirement was "could i make and receive calls?" well i got swype plus mic and call and recieve working...but the software was still horrible. i couldnt beleive that a device like a giant epic(sgstabby) could massacre my tegra2tabby by way of speed and sheer quickness...working on phone call and receive now for my galaxy tab and i couldnt be happier....amazing what software can do...this tabby will be awesome if it gets enough dev but as it stands its going to be overlooked just because of the crap software...i used all custom roms and none had the performance of STOCK s g tabby....i hate samsung and i looked forward to this device for so long...rather disappointing...glad i purchased at staples with no restock fee
Humm, my sipdroid works just dandy... using sipgate, sipsorcery, Google voice..
Sidebar, in sipdroid you must hit menu>speaker to hear anything.. I've also found within sipdroid in landscape mode the keyboard "enter" button actually starts the call
rgiesbers said:
I have Skype and IAXagent working, but unable to get audio to my bluetooth headset.
Click to expand...
Click to collapse
+1 Skype works fine for me. I have a Skype number and the $2.99 unlimited US/Can calls. I can receive and make calls. I use my phone headset and it works perfectly.
Ok, so I got a Galaxy Tablet (Sprint) from BestBuy, and plan to use it only with WiFi.
I was searching around and discovered Sipdriod as a possible app to make calls over WiFi with my G Tab, but when I try to place a call I get the message "Cannot make or take a call using the Galaxy Tab."
Anyone know why this is?
I read above that Sipdroid won't work, but I am wondering why. I mean is this a limitation Sprint has put on their G Tabs? Is it some limitation Samsung built in?
It just doesn't make sense to me that I can have an Android app that should be able to make a call over WiFi, but the G Tab is restricted.
I am an onsite tech, and I've been using my Old Atrix for almost 1.5 years, I'm excited I get to upgrade in February, but since I got my Nexus, I am totally going to start using it to replace my phone, and here is what I did:
1. Convinced my boss that we need to find an alternative to WhatsApp. So now we are using Google Talk, with Party Chat that keeps a persistent group chat.
2. Setup a Google Voice number, and I use that app to text.
3. Then setup Talkatone for calls, I disabled it from notifying me of texts since GV also does that.
4. The only thing I still need to do is get a BT headset to make calls more efficient.
I still need to test this setup more, but it should work good for me.
So, has your Nexus 7 replaced your phone yet?
I don't remember hearing a echo before KitKat. Maybe the radio isn't as good? It doesn't happen all the time. Wife's HTC M7 goes in and out when she talks on her phone. Not sure if somehow the issues are tower related or something with both of our phones?
Guess I'm the only one. I might try a reset but probably won't help. Also having FC's on apps. Both after KitKat.
sweets55 said:
Guess I'm the only one. I might try a reset but probably won't help. Also having FC's on apps. Both after KitKat.
Click to expand...
Click to collapse
No your not. I get it also every so often. But very far apart.
Sent from my LG-D959 using XDA Free mobile app
My echo happens everyday. I told my mom that I was getting a echo and she's like I don't have one. LoL. I told her it's on my end and got off the phone.
I get echo with T-Mobile and wifi calling. My fix has been to turn the volume to about 1/4 and it stops.
Yup
Yup. I don't know if it happened on 4.2.2 or not, I got the phone, upgraded as soon as I opened it to 4.4.2 (v7 Sprint) and rooted, changed the audio to Dolby installed the viper audio app and made a call. It echoed bad. So, because I like to flash things (hubba hubba) I decided to flash back to stock 4.2.2, but like a retarded honey badger who doesn't give a ...., I forgot to test the call quality before I accepted the update back to 4.4.2.
So, most definitely happens on my phone, both with WiFi calling on or normal calling mode while using KK.
rsohne said:
I get echo with T-Mobile and wifi calling. My fix has been to turn the volume to about 1/4 and it stops.
Click to expand...
Click to collapse
My Volume is blasting loud also. Usually it sounds as if the other person has me on speaker phone and I'm hearing my self.
Sent from my LG-D959 using XDA Free mobile app
echo on Google Hangouts voip call
When I make a Google Hangouts voip call with my LG G Flex, or answer an incoming call with Google Hangouts on the LG G Flex, the other party says the echo is unbearable. I actually cannot hear it, but they say it is terrible. It's too bad. I like using Google Hangouts for calls when I'm outside of cell coverage, but Hangouts is a no go for me with the Flex.
Has anybody figured out a way to get this to answer calls from the Google Voice and/or Hangouts apps? I have the added complication of using it with a tablet that "can't" make voice calls. The "Phone" app is hidden and with everything I've tried (nothing tricky, just the standard options), my Neo tells me something like "your connected Android device is not capable of making calls."
I'm using a rooted AT&T Samsung Galaxy Tab S (SM-T807A), running Android 5.0.2. I'd like to be running basically anything other than TouchWiz but locked bootloader is a pretty big hindrance.
My Neo is running software version R381XXU0BOA2.
I'm able to get notifications from the Hangouts app (even missed call notifications, ironically) so I suspect that if I could somehow trick the Neo into thinking the T807 is (for example) a Galaxy S5, it might let me answer calls. But I have no idea how to do that or if that's even where the problem is.
"READ Tmobile acknowledge Native message app is corrupt. Don't update Says TMobile
It seems that if you read online on T-Mobile forms in other areas people are not receiving all their text messages if not 10 to 50% of them are missing people are finding this out by logging into T-Mobile digits and same messages they never got through the native messaging app after the 8.0 update.
I noticed this when I did not receive messages for a good while until I put my SIM card into a Galaxy S8 and 20 to 30 messages popped up that were pre conversation topics from the past days before after talking to T-Mobile and digits support team they are being told to replace the device one time and Advising customer to keep the Nougat software until a fix ia found or until further notice this issue seems to be tied to the Z2 only and Oreo update just wanted to throw this out there as a pre warning the alternative solution the tech told me is that you can use a different messaging app but who's to say you'll ever know if you're not getting all your messages .
It evidently seems to be affecting incoming messages alternatively at your own choice maybe Nougat could be flashed back "Not sure" but this is a real life issue for this phone . If you want to be certain and surprised login to T-Mobile digits activate it and see what messages that you have not got
Hope this information is appreciated.
Um check your wifi calling settings
Sent from my [device_name] using XDA-Developers Legacy app
androidddaaron said:
It seems that if you read online on T-Mobile forms in other areas people are not receiving all their text messages if not 10 to 50% of them are missing people are finding this out by logging into T-Mobile digits and same messages they never got through the native messaging app after the 8.0 update.
I noticed this when I did not receive messages for a good while until I put my SIM card into a Galaxy S8 and 20 to 30 messages popped up that were pre conversation topics from the past days before after talking to T-Mobile and digits support team they are being told to replace the device one time and Advising customer to keep the Nougat software until a fix ia found or until further notice this issue seems to be tied to the Z2 only and Oreo update just wanted to throw this out there as a pre warning the alternative solution the tech told me is that you can use a different messaging app but who's to say you'll ever know if you're not getting all your messages .
It evidently seems to be affecting incoming messages alternatively at your own choice maybe Nougat could be flashed back "Not sure" but this is a real life issue for this phone . If you want to be certain and surprised login to T-Mobile digits activate it and see what messages that you have not got
Hope this information is appreciated.
Click to expand...
Click to collapse
seemles said:
Um check your wifi calling settings
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
What about it ? Wether on wifi calling or not this is a message issue acknowledged and very pronounced In many ways . It's simple to see with a few trial and error tests regardless of wifi
Or LTE Data
Seeing all your messages show up on TMO digits comparing them to messages you've got or never got .....putting a SIM card in a different phone and seeing multiple messages pop up that have still been trying to push through that are tied to specific time line conversations. TMobile literally already acknowledges this it's just nobody is realizing it because they're not expecting messages that they're actually missing from people.
Feel free to test it if you would like have multiple people text you wait for it to come through not saying it affects everybody T-Mobile did tell me that they already have a ticket out for it and it's software related to this particular phone.
On top of the SMS of all things is one of the most critical uses of a phone .
Just trying to shed light on a rising issue that most would never be aware of .
Because all Android phones ship with settings set to wifi preferred wich leads to dropped calls and unsent messages after setting up a home wifi. And if you have no sim installed your obviously using wifi calling wich is most definitely not as dependable as volte.
Sent from my [device_name] using XDA-Developers Legacy app
seemles said:
Because all Android phones ship with settings set to wifi preferred wich leads to dropped calls and unsent messages after setting up a home wifi. And if you have no sim installed your obviously using wifi calling wich is most definitely not as dependable as volte.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'll look into that....but if your not on wifi calling "connected" to a wifi network you would still be using volte right ? This is happening to people conversating anywhere Mobily in a vehicle not on wifi. Messages for instance with my brother whereas I never got a reply in which I would have came through after I put my SIM in my s8.
People are seeing ungotten messages in TMobile digits.
I don't really care i was just looking out for the community here with a potential problem hindering, and T-Mobile tech support made acknowledgement about it . I highly doubt a community across United States all at once is screwing up by keeping WiFi preferred on.
You're only going to be using WiFi calling if you're connected to an actual at work under that settings menu otherwise you would be using cellular by default just like it says to choose below that
You're only going to use Wifi calling if you're connected to a WiFi network otherwise you're going to use cellular default which is the same as being on cellular by default correct me if I'm wrong
Can you post a link to the discussion? I can't find anything after searching for a while.
Sent from my [device_name] using XDA-Developers Legacy app
Z2 force sms MMS broken discussion link
http://support.t-mobile.com/thread/143284
Multiple replied posts from z2 users
How this has not made it to xda is beyond me but it is real situation
It's really not a good feeling to really not know all the messages you should be getting that you're not especially the ones that you're not expecting the scenario is playing out just like it shows in these support forums and with myself.
It's like not "Some messages are blocked in a limbo status never reaching the target device
Like myself you could stick a SIM card potentially in another phone and see stuff that pops up that was related to conversations long ago that you never got replied too.
I haven't had much of a problem with T-Mobile to T-Mobile network SMS but many other people I know that use other carriers I never got replied to until I stuck my SIM card into a different phone of mine.
It's a janky situation and if TMobile is already acknowledge this and told to replace phones one time then evidently the issue has gotten out to the people that needs to I just don't know how nobody here on XDA knows about this .
I have tried multiple text apps and nothing seems to be different I even thought about editing access point but usually that only solves MMS problems
This issue was already addressed with a fix to boot by xda. I had the issue my self. With no issues after I updated to oreo.
https://forum.xda-developers.com/z2-force/how-to/t-mobile-how-to-3rd-party-sms-apps-root-t3661703
seemles said:
This issue was already addressed with a fix to boot by xda. I had the issue my self. With no issues after I updated to oreo.
https://forum.xda-developers.com/z2-force/how-to/t-mobile-how-to-3rd-party-sms-apps-root-t3661703
Click to expand...
Click to collapse
I tried this method and it did not work, after the Oreo update I tried again but kept having issues. Decided to Force stop the CPS app and install the Google Carrier services app and this worked. Don't remember where I heard/read about Google carrier services. BTW using Googles messages app now and seem to be receiving all messages.
I discovered this a few weeks ago then installed google messages and everything works now
Missing messages FIXED
androidddaaron said:
It seems that if you read online on T-Mobile forms in other areas people are not receiving all their text messages if not 10 to 50% of them are missing people are finding this out by logging into T-Mobile digits and same messages they never got through the native messaging app after the 8.0 update.
I noticed this when I did not receive messages for a good while until I put my SIM card into a Galaxy S8 and 20 to 30 messages popped up that were pre conversation topics from the past days before after talking to T-Mobile and digits support team they are being told to replace the device one time and Advising customer to keep the Nougat software until a fix ia found or until further notice this issue seems to be tied to the Z2 only and Oreo update just wanted to throw this out there as a pre warning the alternative solution the tech told me is that you can use a different messaging app but who's to say you'll ever know if you're not getting all your messages .
It evidently seems to be affecting incoming messages alternatively at your own choice maybe Nougat could be flashed back "Not sure" but this is a real life issue for this phone . If you want to be certain and surprised login to T-Mobile digits activate it and see what messages that you have not got
Hope this information is appreciated.
Click to expand...
Click to collapse
I have already experienced this issue. It's NOT related to wifi calling at all. I tested it with wifi calling on and with it off, same results.
What worked for me to FIX it was to clear storage and clear cache on the "native" app. You won't lose messages already on the device but you should backup with Carbonite sms first to be safe. Once I wiped storage and cache for the app I started receiving messages again normally.
I found out I was missing messages by installing digits. It's all working now but I'm keeping digits temporarily just to be safe.
texasaggie1 said:
I have already experienced this issue. It's NOT related to wifi calling at all. I tested it with wifi calling on and with it off, same results.
What worked for me to FIX it was to clear storage and clear cache on the "native" app. You won't lose messages already on the device but you should backup with Carbonite sms first to be safe. Once I wiped storage and cache for the app I started receiving messages again normally.
I found out I was missing messages by installing digits. It's all working now but I'm keeping digits temporarily just to be safe.
Click to expand...
Click to collapse
Wait so your saying this is a fix wether on Oreo or nougat and digits is the whole reason why .
And the native message app just need to clear cache and data in settings app
Sent from my [device_name] using XDA-Developers Legacy app
I deleted and deactivated digits completely. After I had it completely removed from my account, I rebooted and changed to Android Messages and everything has been fine since October.
Are the issues with this phone sorted yet? I was looking to purchase the T-Mobile variant of this phone but have read about issues such as not receiving texts (huge problem), VoLTE not working with Galaxy S7s, and WiFi connection issues. If they are not fixed, can they at least be avoided by refusing the Oreo update? I would like to avoid rooting my phone just to fix a defect and would only consider using a 3rd party messaging app if it fixed the problem without introducing other problems.
I have my phone choices currently narrow down to the Z2 Force, LG G6, and Galaxy S7 (all are currently in the $400 range). I was leaning towards the Z2 since it's the most powerful, but the issues I'm reading about seem quite severe.
After a little more research I see 2 patches were released for the Z2F after the Android 8.0 update.
https://support.t-mobile.com/docs/DOC-35970
I found a Reddit thread (https://www.reddit.com/r/Moto_Z/comments/7zxcpo/tmobile_moto_z2_force_ocx271_update/) where some people mentioned it fixed the SMS notification and Galaxy S7 VoLTE issues. I didn't see anything anything discussing the Bluetooth/WiFi issues or more importanly, the SMS not being received issue (the topic of this thread). Can anyone comment if those were fixed?
cyborgLIS said:
Are the issues with this phone sorted yet? I was looking to purchase the T-Mobile variant of this phone but have read about issues such as not receiving texts (huge problem), VoLTE not working with Galaxy S7s, and WiFi connection issues. If they are not fixed, can they at least be avoided by refusing the Oreo update? I would like to avoid rooting my phone just to fix a defect and would only consider using a 3rd party messaging app if it fixed the problem without introducing other problems.
I have my phone choices currently narrow down to the Z2 Force, LG G6, and Galaxy S7 (all are currently in the $400 range). I was leaning towards the Z2 since it's the most powerful, but the issues I'm reading about seem quite severe.
Click to expand...
Click to collapse
The latest 2 Oreo updates have fixed those problems, and they didn't affect everyone.
Sent from my Moto Z (2) using XDA Labs