For anyone having problems with doing Wi-Fi calling I have found a permanent solution that seems to work, at least for the Pure Nexus rom. The build dated 8-07-2015 for some reason will not work with Wi-Fi calling. The fix is to apply the radio from factory image from the latest build from Google for T-Mobile which is LYZ28J.
I have a link here to my google drive with the file below:
https://drive.google.com/open?id=0Bw_st8EHY1jVOEh1bG5NYnFGb2s
to apply the radio, you must open up a command prompt and put the phone into the bootloader.
the command to apply the file will be: fastboot flash radio "[location]radioname.img"
Example: fastboot flash radio c:\android\sdk\platform-tools\radio.img
I have confirmed this working on two devices running Pure Nexus rom build 8-07-2015. As for other builds this may be a viable option!
jwleonhart said:
For anyone having problems with doing Wi-Fi calling I have found a permanent solution that seems to work, at least for the Pure Nexus rom. The build dated 8-07-2015 for some reason will not work with Wi-Fi calling. The fix is to apply the radio from factory image from the latest build from Google for T-Mobile which is LYZ28J.
I have a link here to my google drive with the file below:
https://drive.google.com/open?id=0Bw_st8EHY1jVOEh1bG5NYnFGb2s
to apply the radio, you must open up a command prompt and put the phone into the bootloader.
the command to apply the file will be: fastboot flash radio "[location]radioname.img"
Example: fastboot flash radio c:\android\sdk\platform-tools\radio.img
I have confirmed this working on two devices running Pure Nexus rom build 8-07-2015. As for other builds this may be a viable option!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
They have flashable radios here. Twrp no computer needed
Sent from my Nexus 6 using Tapatalk
I'm just including this here so people know how to fix it. I got no responses regarding it so I don't want anyone else to possibly go through the problems I did. Not that hard to open a command prompt and just go through fastboot flash... I actually prefer that myself
jwleonhart said:
I'm just including this here so people know how to fix it. I got no responses regarding it so I don't want anyone else to possibly go through the problems I did. Not that hard to open a command prompt and just go through fastboot flash... I actually prefer that myself
Click to expand...
Click to collapse
Based on what I've seen, the modem included with the J build was 14R, the same as that included with the E build.
Sent from my Nexus 6 using Tapatalk
Well this is the only thing that fixes it. So take it or leave it. If your Wi-Fi calling doesn't work on T-Mobile on that build this is your fix.
jwleonhart said:
Well this is the only thing that fixes it. So take it or leave it. If your Wi-Fi calling doesn't work on T-Mobile on that build this is your fix.
Click to expand...
Click to collapse
Oh, I'm not doubting you, and I appreciate the effort you've herein invested, but I ultimately would like to attain clarity on the situation, and I'm wondering if flashing the 14R modem, one would just as swiftly attain the same ends as you've provided in your OP...
https://www.dropbox.com/s/qfw2um8luur694x/shamu-n6-5.1-LYZ28E-radio.zip?dl=0
Sent from my Nexus 6 using Tapatalk
I had tried that radio, it did not work. Wi-Fi calling and T-Mobile with that radio doesn't work. For whatever reason this J revision is the only one I have found that works.
jwleonhart said:
I had tried that radio, it did not work. Wi-Fi calling and T-Mobile with that radio doesn't work. For whatever reason this J revision is the only one I have found that works.
Click to expand...
Click to collapse
Cool, thanks.
Sent from my Nexus 6 using Tapatalk
As a side note I have Wifi calling with the M radio, also I never knew Wifi calling wasn't working on Pure Nexus and I've been on it since day one hah
Hoping more clarity to come
just wondering. would this work with CM ROM if I flash it, since CM ROM does not have WiFi calling? just a thought.
herach said:
just wondering. would this work with CM ROM if I flash it, since CM ROM does not have WiFi calling? just a thought.
Click to expand...
Click to collapse
Nope
Sent from my Nexus 6 using Tapatalk
This doesn't work with Hydra kernel, but does work with Hells, BenzoCore and the pure nexus kernel.
Sent from my Nexus 6 using Tapatalk
This might be a stupid question. So If WiFi calling is enabled and call long distance do I get charge for it?
binqker said:
This might be a stupid question. So If WiFi calling is enabled and call long distance do I get charge for it?
Click to expand...
Click to collapse
Huh? Who gets charged long distance? Is it 1982?
Sent from my Nexus 6 using Tapatalk
Smallsmx3 said:
Huh? Who gets charged long distance? Is it 1982?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Actually everyone in Canada does if their plan doesn't include it, which is quite a few plans...
DespairFactor said:
Actually everyone in Canada does if there plan doesn't include it, which is quite a few plans...
Click to expand...
Click to collapse
Wow. Interesting!
Sent from my Nexus 6 using Tapatalk
binqker said:
This might be a stupid question. So If WiFi calling is enabled and call long distance do I get charge for it?
Click to expand...
Click to collapse
You would have to ask your carrier regarding that. I would call them and ask them if you use Wi-Fi calling will you be charged long distance? They may say yes or no. You aren't running off their cell tower, although it does go through their network. The answer could be 50/50... but it is worth asking at least.
I can't believe they charge you for long distance.... thats insane. They haven't done that in the US now for almost 15 years.
herach said:
just wondering. would this work with CM ROM if I flash it, since CM ROM does not have WiFi calling? just a thought.
Click to expand...
Click to collapse
No, the rom itself needs to support the option. If the rom doesn't support it, then switching to this radio will not make it magically work. Ontop of the rom, the kernel needs to support it as well.
SeVIIn said:
As a side note I have Wifi calling with the M radio, also I never knew Wifi calling wasn't working on Pure Nexus and I've been on it since day one hah
Click to expand...
Click to collapse
If you have Wi-Fi calling enabled, and you have Wi-Fi as the preferred calling method, you will see that while making a call it will say Wi-Fi call, then when you pull down your notification drawer, where it gives you your signal strength and says "T-Mobile" it will instead say "T-Mobile Wi-Fi Calling". That's how you can ensure it's working.
Related
For all of you who wanted tethering to be easy and clean on the Amaze I present to you the Android Wifi Tethering app in working order:
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-pre106.apk
This is still somewhat beta but I have tested it and confirmed it works. Couple of key things to note though. You MUST choose Amaze in Device Profile and you must select "Routing Fix".
For more info on the development of this version check out the bug report that got it started:
http://code.google.com/p/android-wifi-tether/issues/detail?id=1189&q=amaze
My heart felt thanks go out to the team and Android Wifi Tether for throwing us a bone here and getting this up and running!!!
For rooted users only it seems
F033x said:
For rooted users only it seems
Click to expand...
Click to collapse
Yes of course! Im sorry I just assumed that everyone knew that. But yes you must be rooted which is quite a simple process!
2sh0rt said:
Yes of course! Im sorry I just assumed that everyone knew that. But yes you must be rooted which is quite a simple process!
Click to expand...
Click to collapse
Very simple, if I can do it, anyone can. And I did.
Didn't work for me, just sent me to T-Mobiles page for ordering wi-fi tethering.
E-MAC said:
Didn't work for me, just sent me to T-Mobiles page for ordering wi-fi tethering.
Click to expand...
Click to collapse
What is your setup? Are you stock or running a custom rom?
It seems to fc in sense 3.5. Let me see if other versions work.
Edit: 3.1 beta7 works
Thanks!!! It's working for me. I'm rooted and using the stock Rom.
how to put it on?
I have tried 4 different roms on my amaze. Quiksense 3, beastmod, bulletproof, and something else. I wasn’t successful with any to get the wifi, tethering or Bluetooth to work. How do I use your download and make it work on any one of these roms. Kinda new to all this so if u can describe in simple English whether I need to go from the recovery mode from sd or rom manager, it’d be appreciated. Thanks
civiliancone41 said:
I have tried 4 different roms on my amaze. Quiksense 3, beastmod, bulletproof, and something else. I wasn’t successful with any to get the wifi, tethering or Bluetooth to work. How do I use your download and make it work on any one of these roms. Kinda new to all this so if u can describe in simple English whether I need to go from the recovery mode from sd or rom manager, it’d be appreciated. Thanks
Click to expand...
Click to collapse
You have to manually flash a kernel with custom ROMs
Sent from my HTC Amaze 4G using xda premium
Im confused? If we are talking bout wireless thering for another wifi device to connect to your phone. I use my amaze all the time and I haven't rooted mine yet because im waiting for Ice Cream Sandwich .
no go for me. Just rooted, using stock ROM.
tried both the newest beta (v3_1_beta11) and pre106. I see the hotspot from my PC and the log on the phone looks good, but the attempted connection times out.
read this, http://forum.xda-developers.com/showthread.php?p=21476900
no need to ROOT. Just delete all the tethering APNs.
I love the CM 10.1 build of 4.2.2. It is my dream phone right now. The problem is that no WIFI tethering works on it as of yet. If anyone has anything working I'd love to be proven wrong. This is a show-stopper for me. I can't use bluetooth because my laptop doesn't have bluetooth.
I tried every tethering app out there. Barnacle was the best in that it reported the errors it was seeing instead of just refusing to work.
Anyway, I am thinking of working around the problem by keeping a ROM stored as a TWRP backup that I can restore when I need tethering. I don't need tethering on a moment's notice.
I would like the tethering ROM as slim as possible. I haven't tried any yet. Would a restore be any faster with a slim ROM?
Can someone suggest what ROM I should use that has a small footprint and can restore quickly? I'm thinking that I won't have any apps and no account logged in. If I'm tethering I will be using the other device for email etc. And I'm sure the phone will work no matter what I'm running.
Can anyone suggest a better workaround than this?
I pretty much tether all day with my jellybam install. It has been a rock solid performer on my note and has kept me from having the itch to try any of the 4.2.1 ROMs.
There is supposed to be a new version released tomorrow, but quite frankly , I don't know whether I'll bother as the current version is exceptionally stable ( with flaps kernel )...
I'm sure with cm 10.1 going nightly, they'll have tethering fixed shortly. Its a pretty important feature for many of us.
crutzulee said:
I pretty much tether all day with my jellybam install. It has been a rock solid performer on my note and has kept me from having the itch to try any of the 4.2.1 ROMs.
There is supposed to be a new version released tomorrow, but quite frankly , I don't know whether I'll bother as the current version is exceptionally stable ( with flaps kernel )...
I'm sure with cm 10.1 going nightly, they'll have tethering fixed shortly. Its a pretty important feature for many of us.
Click to expand...
Click to collapse
I tried jellyblam for quincyatt and I got a boot loop. I went back to recovery and wiped everything again, reinstalled, and I still got a boot loop. Oh well. Thanks for the suggestion.
mchahn said:
I tried jellyblam for quincyatt and I got a boot loop. I went back to recovery and wiped everything again, reinstalled, and I still got a boot loop. Oh well. Thanks for the suggestion.
Click to expand...
Click to collapse
Sounds like a bad download...Did you download straight to your phone? While I've never had this issue, I have heard that some prefer to download to their computers and transfer the zip to their phones..
You might be right. I did download it to my PC and copy over the zip. However, I had trouble copying and I had to copy a second time. So, I'll try again.
I did a fresh download, copied, wiped, flashed, and it didn't work. Apparently bam won't run on my phone.
...and your using the latest version of twrp?
Yes. I checked. I might be doing something wrong but I doubt it. I'm guessing there is a bug somewhere that rarely shows up. Until the source code is available these custom roms are somewhat a shot in the dark.
I'm just going to go back to my ICS backup when i need tethering. I guess I started this thread with the hope that someone would have a workaround. I really like 4.2.2 and I've decided to live with this. Maybe it will be fixed soon?
Thanks for your help.
The only tethering app that seems to work is "Open Garden." It's in the Play Store but you'll have to side-load it if on AT&T.
Sent from my SAMSUNG-SGH-I717 using xda premium
thx -- I couldn't find apk anywhere, I'll look again. Is that bluetooth only? I need wifi.
apk is not on their home page. Any idea where to find it?
How do you keep AT&T from seeing that you're tethering?
knoshann said:
How do you keep AT&T from seeing that you're tethering?
Click to expand...
Click to collapse
I don't know who you are replying to, but I tethered all the time with ATT when using ICS. I didn't know they were trying to block it.
For a while they were changing people's plans to a tethering plan if AT&T caught them tethering. I got a warning email myself.
knoshann said:
For a while they were changing people's plans to a tethering plan if AT&T caught them tethering. I got a warning email myself.
Click to expand...
Click to collapse
I know that Verizon has folded tethering into the normal data plans. They make it sound like a benefit but they're raising the overall price so they are really forcing you to buy tethering. I thought ATT and the others were going the same way.
I assume they realized they couldn't enforce it any other way.
mchahn said:
thx -- I couldn't find apk anywhere, I'll look again. Is that bluetooth only? I need wifi.
apk is not on their home page. Any idea where to find it?
Click to expand...
Click to collapse
Assuming you're looking for Open Garden, go to http://www.open garden.com and tap the big orange Get APK button to download.
Sent from my SAMSUNG-SGH-I717 using xda premium
chp said:
Assuming you're looking for Open Garden, go to http://www.open garden.com and tap the big orange Get APK button to download.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I've been to their home page a million times because everyone said you could get the apk there. I was going crazy because all I ever saw was a big orange button to download a version for windows. I had just now typed a reply to you that said you were crazy and then it hit me. You meant to go there on the phone! I'd only been there from my laptop.
Thanks, I'll give it a try now.
-- later --
As I feared, open garden is bluetooth only.
I was researching the hotspot issue that only a few users have been having and found that it is inherent to android 4.1.2 and newer. What I found out:
"Throughout the previous iterations of Android (<4.1.2), Android has not identified for the carriers which data is for tethering, and which is not.
Android 4.1.2 introduced that ability (and requirement) for Android devices to properly flag when data is for tethering purposes. This is the first time this has been used in a vanilla release of Android...
For everyone frustrated by this update to Android: Android respecting a carrier's request to know if data is for a tethered device IS NOT A BUG. IT IS A FEATURE. It's not a feature for users like you and me, it's a feature for manufacturers like Samsung and HTC, so they can in turn build devices that carriers can have more control over.
So, to be clear, THIS IS NOT A BUG. Google INTENDED to respect carrier tethering rules. The only way to circumvent this is to either get a plan from your carrier that allows tethering, revert to a build of Android of 4.1.1 or earlier (I used wugfresh NRT tools, google it, they're amazing and simple: FOR NEXUS DEVICES ONLY, SORRY), or for a developer to find and KILL THE ****ING ABILITY FOR ANDROID TO TAG DATA AS TETHERING DATA and release that to the public; either by providing an modded Android image, or as an app (much less likely to work unless you're rooted)."
Copied from a past on another forum, and apparently I can't post a link to it.
Even though I clicked on Thanks, I'd like to thank you again for that clear explanation. I'm sure it won't take long for that to be hacked.
i think the next nightly may fix it
Next to fix on next Nightly
msm8660: Add Wi-Fi AP module args (i wonder if this is it?)
rkpsym ftewed
I sent JamieD a message about it a few days ago. I'm not sure if all developers were aware with source of the problem. Its especially hard when only some users report having an issue. Hopefully they get it working soon.
Just wondering if these could run tmobile roms would love to bring back wifi calling natively rather than using apps and things of that nature. Tried a few searches on here couldn't come up with anything that was solid.
You can make ROMs for other carrier work, but not without some extra work to replace certain files. However, wifi calling requires carrier support. It's not a feature that's going to work on Verizon. The phone system has to know how to route your number, and it can't do that without carrier support.
shrike1978 said:
You can make ROMs for other carrier work, but not without some extra work to replace certain files. However, wifi calling requires carrier support. It's not a feature that's going to work on Verizon. The phone system has to know how to route your number, and it can't do that without carrier support.
Click to expand...
Click to collapse
Ahh ok because I know on the I317 I can put a tmobile rom on it and I am able to use the wifi calling feature I thought maybe it would be a similar process.
blazin6969 said:
Ahh ok because I know on the I317 I can put a tmobile rom on it and I am able to use the wifi calling feature I thought maybe it would be a similar process.
Click to expand...
Click to collapse
If it is a TW ROM you can flash Scotts patch afterwards and will be fine. AOSP will require some modifying but its honestly fairly easy to get it up and running. If there are bugs you'll have difficulty figuring them out but with help from the community you would most likely be able to debug and fix any issues.
Sent from my SCH-I605 using XDA Premium HD app
i have a problem and i seem to be the only one with this problems its so strange. no matter what rom i flash or who its made by if its 4.3 or 4.4 i get the same problems. when i try to make a phone call i cant hear a thing no dial tone nothing UNLESS the phone is on speaker phone then i hear normal but if i switch back to normal phone its silent again. the second problem is when i use speech to text in a text, when i hit the mic symbol the phone reboots itself, sometimes i have to hit the mic then keyboard then mic but eventually it will always reboot its self. any help will be greatly appreciated.
You have done a full wipe, correct?
What radio are you using?
Have you had this problem ever since you first rooted our did this issue develop later?
Sent from my LG Optimus G using XDA Premium 4 mobile app
What Radio are you using? What Carrier?
I've used the ATT Hybrid radio on ATT for the longest time, and I haven't had any of the issues you describe.
DraginMagik said:
You have done a full wipe, correct?
What radio are you using?
Have you had this problem ever since you first rooted our did this issue develop later?
Sent from my LG Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes ive done a full wipe everytime im using stock jellybean modem i got from houstonn i believe and i never had this problem before ive had the phone over a year rooted since day one and never had this problem until i tried to install pcexpresses 4.4 and now every 4.4 and 4.3 rom i try to install has the same issues.
OMGMatrix said:
What Radio are you using? What Carrier?
I've used the ATT Hybrid radio on ATT for the longest time, and I haven't had any of the issues you describe.
Click to expand...
Click to collapse
can you give me a link to your radio so i can try it? and my carrier is simplemobile
dragonash86 said:
can you give me a link to your radio so i can try it? and my carrier is simplemobile
Click to expand...
Click to collapse
You'll want the third one from this link.
If that doesn't work, try the other one labeled "Hybrid" in that folder.
3622 23529369
The radio worked thank god but im still having the same problem with the MIC as soon as i push it the phone restarts.
dragonash86 said:
The radio worked thank god but im still having the same problem with the MIC as soon as i push it the phone restarts.
Click to expand...
Click to collapse
Have you tried the other hybrid radio from that link?
reply
Not yet but I don't think the radio is the problem cause when I install cyanogenmod it works perfectly fine with the hybrid modem where pcexpresses 4.4 the calling issue is fixed but not the reboot issue also I didn't notice this till yesterday but I lost root as well only with pcexpresses.
dragonash86 said:
Not yet but I don't think the radio is the problem cause when I install cyanogenmod it works perfectly fine with the hybrid modem where pcexpresses 4.4 the calling issue is fixed but not the reboot issue also I didn't notice this till yesterday but I lost root as well only with pcexpresses.
Click to expand...
Click to collapse
If you read the thread,you would have known that root is disabled by default in SlimKat.
You have to go in Developer Settings and allow root.
However, Slim's root implementation is kind of ****ty, so I always end up having to flash supersu when using that rom.
sdgf
yeah i noticed it says that at the begining i dont know how i missed that but its good to know how to fix that but that doesnt fix my rebooting problem. any ideas on that?
Well sort of. Its based of slimkat which is aosp. I'm just sharing the link, I'm downloading it now but a few sprint users claim it works.
http://forum.xda-developers.com/galaxy-note-3/development/rom-miui-v5-galaxy-note-3-t2816410
Saw the release
Yeah, I saw that, does anyone know if the sprint version is based on the N9000 and N9005 version on MIUI's site?
RigorousNinja said:
Yeah, I saw that, does anyone know if the sprint version is based on the N9000 and N9005 version on MIUI's site?
Click to expand...
Click to collapse
Not positive, but I think 9005. Anyway I could not get a signal at all. Have you tried it?
Modem
drunkensunday said:
Not positive, but I think 9005. Anyway I could not get a signal at all. Have you tried it?
Click to expand...
Click to collapse
I believe that if it will flash that you will have to flash a modem since it would contain the international modem pre installed, but I haven't tried the install yet, I may soon though.
It should work out the box. But it's not detecting our sim cards. It's based on the slim rom hlte device tree, which will work on our phones
Sent from my SM-N900P using Tapatalk
I am looking forward to a port of the tw version of MIUI.
Tried it
I tried it on our device, and it seems to work ok. It is definitely not a daily driver, but runs smooth. The mobile data doesn't work, but calls and texts come through. The rest of the bugs are true, where vibration on touch doesn't work. other than that it seems to work.
Is anyone having problems with their phone service? I can't text or call D;
kittyfantastic said:
Is anyone having problems with their phone service? I can't text or call D;
Click to expand...
Click to collapse
After setting network o can make calls but not disconnect from them. The dev seems to say it works but its not. Whish more devs would get active in porting it. It seems so close to actually working finally.