I have been noticing lately when using Wi-Fi calling my calls have been dropping and just a general overall overall inconsistency when using Wi-Fi calling. I haven't had any other issues with the kernel than that one. If someone can help me or give me suggestions for the problem I would appreciate it.
Did you check the support thread for that kernel to see if anyone else was having issues? If not, did you post there to let the developer know about it? Did you search the forum to see if anyone using that kernel has found a workaround?
Apart from the above, you have to decide to live with the fault for now or change kernels.
.
Related
I'm currently running Trigger 3.2 with Bullet kernel but I've had this problem with every kernel I've tried (stock Trigger kernel, Overstock, Bali etc) and with other roms (Bionix) and with or without Voodoo lagfix enabled. When I have wifi calling enabled, the caller on the other end hears an echo of their voice. This is true whether they call or I call and no matter where I'm using wifi. I've tried at home, work, coffee shops. No matter what, they hear themselves when they talk. Anyone else experience this issue? I really want to take advantage of the free unlimited wifi calling but if the people I'm talking to have this issue, it's not going to fly.
Anyone?
No one else is experiencing this problem? I just tried stock Froyo and I'm having the same issue. Hardware problem? Wifi settings? I tried changing my wifi security to open to test it and still experienced the problem.
Yes same problem on team whiskey roms... about to try a different rom... ugh, will post if it fixes
echo echo echo......
yes i have the same problem ive tried trigger and sgs 2 clone still same problem
I've got the same issue myself. The caller hears themselves with a delay. I thought it was due to bandwidth problems, so I made sure I had NO transfers going on my PC and reconnected the call. Same echo throughout - and THEN wifi calling force closed and dropped the call. I've been having these problems throughout. I certainly hope they improve WIFI calling and release app updates over the market (like My Account) rather than leaving it as is and/or waiting for an entire firmware update.
Same problem here on EDT Project V. I've had to stop using wifi calling because of it.
We need to bump this thread to get more people aware and to find a solution.... It is REALLY annoying!
I'm having the same issue.
Using Wi-Fi Calling version 1.0 on Bionix Next Gen 1
Same issue here also...ive tryed many roms and apps..but no change...ive givin up on the wifi calling months ago...it would b great to see it get fixed...that is if it can be...im starting to think that the echo ia just how it is...who know!!
simply galaxy 2.8 vibrant
Im having the same problem. It happens with every rom/ kernel I try. Only thing I have found that helps is to turn down the in call volume. It still echos, but not as bad.
this is probably with the t-mobile app itself
I know this thread is a bit old, but I'm also having this problem. I'm currently running Bionix-V 1.3.1 Fishman Mod V3 (Bali kernel). I don't think I had the wifi calling echo problem when I was using the regular Bionix-V 1.3.1 with the regular froyo kernel.
I'm working on a new rom for the captivate based on the kh3 leak and everything works great other than wifi.
So far I've gone through countless posts on how to fix issues with wifi, changing some files related to wifi, removed files that were said to fix it, checked router settings, did all wipes and factory reset, tried non modified kernel and a ton of other things and the only thing that works is connecting using a static ip and that isn't something that i think is ok in a rom I'd like to release as a 'daily driver' especially to the public.
If anyone could point me to some information to get this working right that'd be awesome I've been going crazy trying to find a fix for this for almost a week and its the only thing holding me back from releasing the beta of my rom.
If you need any info or logcat output i can provide it, just let me know, would already uploaded the logs and post the links but I've had a very busy day and its time for some sleep.
bump for the day, really need some help here guys, I've gone through everything I've found about issues with android wifi issues and nothing will work.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have just re-installed Wolfbreak's most up-to-date ROM and DoomLord's medium overclock custom kernel and noticed an option I've not seen in my Advanced WIFI settings before:
Regulatory Domain
and the sub-options are:
11 channels
13 channels
I've searched online and on the forum but can't find out what this really means. However ever since I moved to Stock 2.3.3 back in July last year, I have had so many problems with my wi-fi cutting out completely. Disabling and re-enabling Wifi does not fix it, and nor does a reboot. The only way to get my wifi back is to go downstairs and reset my wireless router. I don't think the router is a problem as it's the same one I used to have when on Stock 1.6/2.1 and I never had problems at all, but it will often just randomly cut out and I was wondering if these options could be any use to me?
Thanks,
Alex
I think those options just decide how many channels should the phone use.
Thanks for the response
I notice the option has only appeared since using a custom kernel (Doomlord's OC)
I suppose whilst I am here it is a good time for me to ask if anybody knows why my wifi does sometimes cut out and not return until I reset my router? I do remember reading somewhere that it is an issue with 2.3.3 and was wondering if there was a fix.
Thanks,
Alex
alex_ncfc said:
Thanks for the response
I notice the option has only appeared since using a custom kernel (Doomlord's OC)
I suppose whilst I am here it is a good time for me to ask if anybody knows why my wifi does sometimes cut out and not return until I reset my router? I do remember reading somewhere that it is an issue with 2.3.3 and was wondering if there was a fix.
Thanks,
Alex
Click to expand...
Click to collapse
Well, I'm always using a custom ROM and never had that problem
I installed the CM10.1 kernel 3.1 on my Atrix 4G, but it is giving me some trouble with the network.
I'm not talking about the data connection, I'm talking about the fact that I can't make a phone call and people can't call me.
The phone says "No Network" and the only chance to have it back is to restart the phone.
Is there any solution to this problem?
Is it seriously so hard to use search?
Thread reported.
ravilov said:
Is it seriously so hard to use search?
Thread reported.
Click to expand...
Click to collapse
No, it is not and I did, but I only find threads where people talk about losing of data connection, that's why I specified "no data" in the title.
If you have a link where is possible to read a solution I'll thank you, but I couldn't find any.
It's the same thing. There is no solution. You are running an ALPHA stage ROM which you should have known before flashing. If you didn't know that, then you did a crappy job at reading up before flashing.
ravilov said:
It's the same thing. There is no solution. You are running an ALPHA stage ROM which you should have known before flashing. If you didn't know that, then you did a crappy job at reading up before flashing.
Click to expand...
Click to collapse
Well, that's not exactly the same thing, I some time I also have data connection loss, but when that happen I'm still able to make and receive phone calls.
To get the data connection back, it is enough to put the phone in Aereo mode and back to normal, so it is not a big problem.
In addition I read about the ROM I was going to flash and on the official site (linuxmobile) I read:
Known to be working:
Calls
...
(so I expect that also network is ok)
Known bugs
MTP don't show files
HDMI
BT audio
Voice Dialer
Sound Recorder
Camera flas
(no bugs listed about network connection)
Features not supported
No fingerprint navigation or unlock
Wifi Direct
Gesture typing don't work...
Facelock
(no advice about network not supported)
So, as you can see, there are no advice about network connection loss and who reads that expect that connection loss will not happen.
Kumidan said:
Well, that's not exactly the same thing, I some time I also have data connection loss, but when that happen I'm still able to make and receive phone calls.
To get the data connection back, it is enough to put the phone in Aereo mode and back to normal, so it is not a big problem.
In addition I read about the ROM I was going to flash and on the official site (linuxmobile) I read:
Known to be working:
Calls
...
(so I expect that also network is ok)
Known bugs
MTP don't show files
HDMI
BT audio
Voice Dialer
Sound Recorder
Camera flas
(no bugs listed about network connection)
Features not supported
No fingerprint navigation or unlock
Wifi Direct
Gesture typing don't work...
Facelock
(no advice about network not supported)
So, as you can see, there are no advice about network connection loss and who reads that expect that connection loss will not happen.
Click to expand...
Click to collapse
True I guess. The working/not working lists are quite outdated though. Also, this ROM still uses the experimental kernel which is in alpha stage. This means what is labeled as "working" actually means "seems to work". It also means literally anything is possible, including something that is considered working to stop working all of a sudden. In short, this ROM was never meant to be a daily driver ROM.
Got it.
Well, I like this ROM and I want to go on using it, so I will follow the new releases.
I would also like to contribute to correct this and other bugs if possible.
Is there anything I can do to help? Maybe reporting logs about the connection loss? How?
Appreciated but there's not much you can do right now. This is a well known bug and it's being worked on. If you want you can follow the relevant threads in the Development section, every so often a new kernel build comes out which might fix this bug. But only try them out if you are confident enough in your technical knowledge, more specifically if you have sufficient technical background in doing basic adb/shell/recovery operations. Otherwise, if you feel you can't do this or you'd prefer a fully working ROM, you would probably be better of flashing a GB/CM7 ROM.
Kumidan said:
Got it.
Well, I like this ROM and I want to go on using it, so I will follow the new releases.
I would also like to contribute to correct this and other bugs if possible.
Is there anything I can do to help? Maybe reporting logs about the connection loss? How?
Click to expand...
Click to collapse
All future releases are kernel based. CM10.1 has reached the EOL as far as development goes. Please refer to the CM10.1, the CM9, and the kernel development thread for updates.
Kumidan said:
Got it.
Well, I like this ROM and I want to go on using it, so I will follow the new releases.
I would also like to contribute to correct this and other bugs if possible.
Is there anything I can do to help? Maybe reporting logs about the connection loss? How?
Click to expand...
Click to collapse
Now you can help by testing, go to cm10.1 and kernel threads, the ibfo on how to help is there
Enviado desde mi MB860 usando Tapatalk 2
Nice! If you can, fullfill the spreadsheet, so krystianp can squash that bug once and for all
Enviado desde mi MB860 usando Tapatalk 2
Should I reply to the official thread in this forum? Because at the moment I can't yet write there, the system says that I have not enough posts.
You should fill out the spreadsheet like andresrivas said.
Where do I find it?
Kumidan said:
Where do I find it?
Click to expand...
Click to collapse
I would tell you to use the search bar. You will find it very very quickly
Enviado desde mi MB860 usando Tapatalk 2
Kumidan said:
Where do I find it?
Click to expand...
Click to collapse
And learn to use the thanks button instead of spamming threads with your posts just to say thanks...
Does anyone know of a way within Tasker to toggle Wi-Fi Calling on/off? I'm looking to setup a profile to turn it on when I connect to my setup networks and off otherwise (it seems to drain battery if left on and not in use for me?).
I found someone else on the Note 3 T-Mobile side of things that developed the equivalent (haven't tried it yet, may have to take a backup and give it a go to see if it works) which shows as incompatible with my device unfortunately.
Not sure, but I'm also interested in this.
I joined up and asked over in the beta group, to see about any possibility of having the dev take a look at it...
Thanks for doing that, I was planning on doing the same this evening. I'll add a comment as well. Here's hoping for an easy solution
Sent from my SM-N900P using xda app-developers app
You ever find a solution?