So will the Nexus 5 support VoLTE?
AT&T has said VoLTE starts deployment by the end of this year. Does anyone think the Nexus 5 will work on AT&T's VoLTE?
This thread doesn't have to be about speculation. This is XDA and I expect more technically from this forum. Let's think about this systematically. What is required for a phone to work on VoLTE? Is the LTE hardware enough? Probably not. I think we can all agree that the software has to support it. I've read that the LG Connect 4G on MetroPCS supports VoLTE since they have already deployed VoLTE and it is supported using that phone. So that means Android has had VoLTE since Android 2.3 Gingerbread. Was that custom software for the LG Connect or is there still code in Android supporting VoLTE? Is anyone knowledgeable to look at Android 4.3 source files to see evidence of VoLTE living there, in comparison to the Android source in the LG Connect? Maybe there are system files in Android that have VoLTE in their name. That would be a good clue.
Was there anything in the LG Connect's FCC documentation that specified VoLTE testing or specifications? Is this needed for VoLTE? Or is LTE testing alone enough since it is all the same from a physical frequency perspective?
I brought this topic up in another forum and I got some good responses. I just want to take it to the next level here with all the gear heads and XDA wizardry that lives here.
Sent from my Nexus 10 using Tapatalk 4
galfert said:
So will the Nexus 5 support VoLTE?
AT&T has said VoLTE starts deployment by the end of this year. Does anyone think the Nexus 5 will work on AT&T's VoLTE?
This thread doesn't have to be about speculation. This is XDA and I expect more technically from this forum. Let's think about this systematically. What is required for a phone to work on VoLTE? Is the LTE hardware enough? Probably not. I think we can all agree that the software has to support it. I've read that the LG Connect 4G on MetroPCS supports VoLTE since they have already deployed VoLTE and it is supported using that phone. So that means Android has had VoLTE since Android 2.3 Gingerbread. Was that custom software for the LG Connect or is there still code in Android supporting VoLTE? Is anyone knowledgeable to look at Android 4.3 source files to see evidence of VoLTE living there, in comparison to the Android source in the LG Connect? Maybe there are system files in Android that have VoLTE in their name. That would be a good clue.
Was there anything in the LG Connect's FCC documentation that specified VoLTE testing or specifications? Is this needed for VoLTE? Or is LTE testing alone enough since it is all the same from a physical frequency perspective?
I brought this topic up in another forum and I got some good responses. I just want to take it to the next level here with all the gear heads and XDA wizardry that lives here.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
i love your inquiry!
as we all know, tmobile's launching VOlte in seattle, via s/w upgrade to various phones, but why that way?
wouldn't it had been easier via an updated volte capable sim card with the needed provisioning?
what governs any phone's baseband code on certain networks; is it HARD coded, or SOFT coded, to change on the fly, depending on the network? -
iPhone can support VoLTE
that link also addresses how volte is implemented on tmobile's network..
or if one prefer - How it works: Voice over LTE (VoLTE)
one thing for sure, qualcomm & erricsson trialed volte on an earlier snapdragon chipset (Qualcomm's Snapdragon S4 MSM-8960)
the nexus 5's snapdrag, is a newer **Qualcomm MSM8974 snapdragon 800** .. i would doubt it DOESN'T
support volte, why add the feature to an older chipset, & not include it by default in a newer.. -
Qualcomm's Snapdragon almost ready for Voice over LTE (VoLTE) (February 2, 2012)
~edit~
i'm so glad i'm not mentally lazy (that's why i use linux dammit) the nexus 5 CAN DO VOLTE! -
Doug M.
Chief Operating Officer (COO) and Chief Sales & Marketing Officer (CSMO) at D2 Technologies, Inc.
We (www.d2tech.com) are trying to break the "chicken/egg" cycle by providing a commercial-ready reference implementation for native IR.92 VoLTE, IR.94 and RCS 5.1 / joyn for mobile devices. At MWC, we demo'd it on a Nexus 5, Huawei Ascend G716-L070, Nvidia’s Tegra 4i reference platform and an Intel® Atom™ based commercial handset. We're also providing several LTE modem IC vendors with an embedded IR.92 VoLTE solution that has APIs in the LTE modem IC to the mobile AP that allow the RCS/IR.94/WiFi calling capabilities embedded in the mobile OS to leverage the IMS registration and SIP signaling stack, and DSP voice engine that now reside in the modem IC. This makes it very easy for device OEMs to provide native RCS and/or VoLTE and IR.94 video calling.
from - http://www.linkedin.com/groups/China-Set-Lead-RCS-Integration-1890406.S.5849549644362706944
the nexus 5 can do volte on china mobile now, from china mobile's volte white paper - http://www.lte-tdd.org/upload/accessory/20138/20138271114319913691.pdf
3.4 Terminal Aspects
3.4.1 Multi-Mode and Multi-band
To meet the requirements for domestic frequency access and international roaming,
five radio modes including FDD LTE, TD-LTE, TD-SCDMA, WCDMA, GSM
should be supported by China Mobile TD-LTE terminals, which are divided into the
basic type and the enhanced type: the basic type terminal should support 5 modes and
10 bands, the enhanced type terminal should support 5 modes and 12 bands.
Furthermore, terminals with other multi-mode and multi-band capabilities can be
introduced to meet the market needs.
Supporting the Band41（2496-2690MHz）is mandatory for TD-LTE terminals in
2014. If the terminal support Band 41 without Band 38, it must comply with the
3GPP TS36.331 R8.H.0 and later versions, while for the terminal with both
Band41 and Band38, it is not needed to support the 3GPP TS36.331 R8.H.0
version.
qualcomm msm8974ab bring up kernel log ( that the nexus 5 has)
<6>[ 11.666645] pil-q6v5-mss fc880000.qcom,mss: modem: loading from 0x08000000 to 0x0d100000
<6>[ 11.667153] asoc: snd-soc-dummy-dai <-> SLIMBUS4_HOSTLESS mapping ok
<6>[ 11.668196] asoc: snd-soc-dummy-dai <-> VoLTE mapping ok
<3>[ 11.669309] init: cannot expand '${sys.sysctl.extra_free_kbytes}' while writing to '/proc/sys/vm/extra_free_kbytes'
& this is an interesting read, (not for the lazy) -
The State of Qualcomm's Modems - WTR1605 and MDM9x25
**comment from the article** -
iwod - Sunday, January 06, 2013 - link
"Interesting, i was late to the article and there is only 10 comments, compared to 3 page on ARM vs Atom. People not interested in LTE / Baseband at all??
Anyway, so do LTE UE 4 offer better bandwidth efficiency then UE 3? Since both only required 20Mhz, but UE 4 gives up to 150Mbps.
Apart from Beidou and TDS-CDMA, WTR1605 seems like a small step, no size reduction?
Are there any power improvement with 9x25? LTE seems to be draining battery a lot.
So i gathered all current Qualcomm already support VoLTE, we are only waiting for carrier to support it, right? And may be off topic, why aren't carrier doing it / Faster?
I am not sure if i am right, the more port there are, the more supported band / wireless spec there will be. It seems to be one of the reason iPhone 5 could not come with world wide LTE supported. So wouldn't ditching GSM help? ( 4G is here.... time to ditch 2G right? )
How do WiFi and Bluetooth fits into the scenario? They are all wireless tech, why do they requires another chip? Couldn't Qualcomm fits those in?
I remembered there was a article about Intel Digital Radio. I admit i still do not understand much of it. Any relation to this? Or is Digital Radio more on the antenna side of things."
**reply to that**-
DanNeely - Sunday, January 06, 2013 - link
"VoLTE increases the load on their 4g networks by reducing the load on 2g/3g; since 4g is only going to get more crowded with time while 2g is becoming a ghost town and 3g will become one in the next few years as LTE deployments are completed, VoLTE does nothing beneficial for the carriers in the short term.
Long term it's needed to let them shut down their legacy networks; but that's at least 4-5 years out according to occasional talking points they make (and if Sprint/iDEN is any indication even farther out in the real world) which makes it not worth enabling for handsets that will probably be junked well before it happens."
...........
we can deduct, that all current qualcomm chipsets have the VOlte feature baked in (but dormant for some odd reason);
tmobile, enables it on selected handsets via a pushed software update, not via an updated **VOlte sim** = Generic Bootstrapping Architecture
&
Subscriber Authentication in the IP Multimedia Subsystem
..
~shrugz shoulderz~
Probably to tie you into T-Mobile branded handsets where they make huge margins. Same as Wi-Fi calling.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Probably to tie you into T-Mobile branded handsets where they make huge margins. Same as Wi-Fi calling.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know how it works now;
the tmobile update *FULLY* enables the sip protocol on it's IMS ( IP Multimedia Subsystem) to match what's dormant in the phone ALREADY..
it's basically SIP ( with heightened QoS) -
read that - http://www.howardforums.com/showthread.php/1833821-Tmobile-launches-VoLTE-in-Seattle/page6
then
this - http://lteuniversity.com/get_trained/expert_opinion1/b/bbest/archive/2012/12/17/the-volte-conversation-between-ims-and-lte.aspx
...voLTE basically , speaks in SIP (session initiated protocol) -
http://www.sharetechnote.com/html/Handbook_LTE_VoLTE.html - the picture in this link with the raw network traffic can be mimicked with a tmobile sanctioned volte device, tethered wirelessly to a laptop in promicous mode, with wireshark or tcpdump, with the right arguments, or both, & with the said tmobile phone in a call session, the packets can be dumped & analyzed afterwards..
j'vai said:
i know how it works now;
the tmobile update *FULLY* enables the sip protocol on it's IMS ( IP Multimedia Subsystem) to match what's dormant in the phone ALREADY..
it's basically SIP ( with heightened QoS) -
read that - http://www.howardforums.com/showthread.php/1833821-Tmobile-launches-VoLTE-in-Seattle/page6
then
this - http://lteuniversity.com/get_trained/expert_opinion1/b/bbest/archive/2012/12/17/the-volte-conversation-between-ims-and-lte.aspx
...voLTE basically , speaks in SIP (session initiated protocol) -
http://www.sharetechnote.com/html/Handbook_LTE_VoLTE.html - the picture in this link with the raw network traffic can be mimicked with a tmobile sanctioned volte device, tethered wirelessly to a laptop in promicous mode, with wireshark or tcpdump, with the right arguments, or both, & with the said tmobile phone in a call session, the packets can be dumped & analyzed afterwards..
Click to expand...
Click to collapse
@galfert.. now that we KNOW at it's heart, VOlte speaks sip, it would be work to mimc the sip settings from another tmobile VOlte phone to a nexus 5 on the tmobile network..
it'll be lengthy, adding the bearer info, secondary bearer info, number + proper sip addy, & parking it on lte..
*BUT* it wouldn't work STILL, unless the UE (user equiptment) gets the OK'd update on tmobile's IMS gateway, *TO* set up & tear down the voice bearer connection with properly enhanced Q0S offered by the IMS..
the sip setting for the nexus 5 are in the phone setting for internet calls, & actually, i'll plug a thread started in here from 13 on this very subject -
Nexus 5 - Internet Calling Experience/SIP Thread by BinkXDA ..
the tools are in the device, but aren't complete from the network perspective..
& yet, i know NOT if tmobile could fashion this update for phone(s) a lil bit more heavier, where those un-known fields needed, are automatically populated.. maybe they're working on that for the future..
Here is something else to consider. T-Mobile has WiFi calling. Google Voice users for a long time have used apps to do VoIP over Google Talk XMPP and still can despite it being past the date. So who is to say an app couldn't just do it or they couldn't use just the SIP part of the phone app? Get the right codec and it is golden.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
Here is something else to consider. T-Mobile has WiFi calling. Google Voice users for a long time have used apps to do VoIP over Google Talk XMPP and still can despite it being past the date. So who is to say an app couldn't just do it or they couldn't use just the SIP part of the phone app? Get the right codec and it is golden.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
you're so right...
i use groove IP to call over lte, evdo, & wifi at times, after tinkering with the echo settings, it's as clear as any voice call..
only with the tmobile volte set up, the plus is you're using your same mobile number still (google snatched that away when breaking xxmp protocol in gv) ..
but with adjusting, the QoS can be just as good as your connection allows the call to be.. mine's is with groove IP / ring.to
galfert said:
So will the Nexus 5 support VoLTE?
AT&T has said VoLTE starts deployment by the end of this year. Does anyone think the Nexus 5 will work on AT&T's VoLTE?
This thread doesn't have to be about speculation. This is XDA and I expect more technically from this forum. Let's think about this systematically. What is required for a phone to work on VoLTE? Is the LTE hardware enough? Probably not. I think we can all agree that the software has to support it. I've read that the LG Connect 4G on MetroPCS supports VoLTE since they have already deployed VoLTE and it is supported using that phone. So that means Android has had VoLTE since Android 2.3 Gingerbread. Was that custom software for the LG Connect or is there still code in Android supporting VoLTE? Is anyone knowledgeable to look at Android 4.3 source files to see evidence of VoLTE living there, in comparison to the Android source in the LG Connect? Maybe there are system files in Android that have VoLTE in their name. That would be a good clue.
Was there anything in the LG Connect's FCC documentation that specified VoLTE testing or specifications? Is this needed for VoLTE? Or is LTE testing alone enough since it is all the same from a physical frequency perspective?
I brought this topic up in another forum and I got some good responses. I just want to take it to the next level here with all the gear heads and XDA wizardry that lives here.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
One thing you've forgotten to mention is Qualcomm's proprietary baseband firmware that has to have VoLTE support enabled. It's all closed source and signed.
We know that N5's baseband processor itself is capable, but if the firmware isn't there to enable and drive VoLTE, no matter which software you create over-the-top, it won't magically turn on VoLTE.
The main and most important difference between VoLTE and third party VoIP solutions like Skype, FaceTime, etc, is that VoLTE processing happens at the very baseband level, which handles phone call continuity between LTE and UMTS/GSM, and also makes it more efficient.
On the other hand, OTT processing is all OS/SoC.
I asked T-Mobile's technical guru about it a while back, here's what I got:
https://twitter.com/askdes/status/469582255191388160
Hilbe said:
I asked T-Mobile's technical guru about it a while back, here's what I got:
https://twitter.com/askdes/status/469582255191388160
Click to expand...
Click to collapse
https://twitter.com/TMobileHelp/status/479798004627427328
from 20 days ago.
Sorry for digging up this old thread, but after reading the how-does-VoLTE-work article, there's a point that nobody has mentioned yet...
While engaged in a voice call, a user might pass outside of an LTE coverage area, so that call needs to be able to fall back onto legacy networks. The VoLTE standard accomplishes this with Single Radio Voice Call Continuity (SR-VCC).
[...]
SR-VCC requires the network provider to have the IMS framework in place, but it also impacts device design. To support SR-VCC, devices must not only be able to connect to both the LTE and the legacy networks, but be able to connect to both at the same time. This is governed by the antenna architecture in the device. In order to conserve space, some devices, like the iPhone 5, will have 3G and 4G traffic sharing the same physical antennae, toggling between the two standards as needed. SR-VCC requires devices to have dedicated antennae for both 3G and 4G connections.
Click to expand...
Click to collapse
I may be mistaken about this, but the antenna is shared on the Nexus 5, isn't it? So it cannot support the LTE-to-3G handoff and as a result may never support VoLTE...
I've read it cannot, but by the time this technology is rolled out in a major way the phone will be verging on obsolete, I'm still happy with mine though
code65536 said:
Sorry for digging up this old thread, but after reading the how-does-VoLTE-work article, there's a point that nobody has mentioned yet...
I may be mistaken about this, but the antenna is shared on the Nexus 5, isn't it? So it cannot support the LTE-to-3G handoff and as a result may never support VoLTE...
Click to expand...
Click to collapse
Just watched a disassembly video on YT and he showed the Nexus 5 has two antennas. One for 2/3G and one for LTE.
Gesendet von meinem C5502 mit Tapatalk
Any confirmation on this?
I also only saw two antennas as I replaced my screen.
Ifixit.com says its MIMO and GPS antenna:
https://www.ifixit.com/Teardown/Nexus+5+Teardown/19016/[URL]
Any confirmation? Any help?
I bought a nexus 5 to replace my galaxy s4 which died a couple of days ago.
My home router is a Netgear D6300 and everything (pc, tv and phones such as iphone, samsung and nokia can connect just fine).
My nexus 5 was delivered today and i spent the last 5 hours to get it working with my wifi but NOTHING worked (and, i'm not joking, i got to the point of almost throwing it out of the window).
I tried enabling SSID broadcasting, changing "security options", changing channels, disabling 5ghz network, i also enabled the guest network with no protection but nothing worked.
The only thing i noticed was the when using particular channels (5-6-7) the phone would say "connecting" for a few seconds but then it would go back to "saved,protected with wpa/wpa2".
I also changed some wifi settings on my phone (i disabled wifi optimization and i forced the phone to use the 2.4 ghz network only)
Sometimes it stays on "saved....." and doesn't even seem to try to connect.
After a while i tried creating an hotspot with an iphone 5s and my nexus connected in a second and everything was working.
So the problem should be in my router settings but i already tried everything (and besides everything else but the nexus works just fine).
I'm really desperate because i use this phone for work and i need to get this working asap.
I also managed to update to android 4.4.4 using my mobile network but i can't update to lolipop because it would use all my remaining 3g network data.
Btw i did some heavy modding on my galaxy s4 so i'm not a newbie to android.
I'm also willing to pay for support but to be honest i'm really disappointed that such and "acclaimed" phone has problems connecting to a wifi network that works with basically everything.
Sorry if I missed it in the post, but did you reboot the router.
rootSU said:
Sorry if I missed it in the post, but did you reboot the router.
Click to expand...
Click to collapse
Yes but it didn't help.
I've had 4 N5's in my possession over the past year or so, and not a single one had any issues connecting to any WiFi network, including Netgear routers. Your problem is either specific to your particular device or your router and not with the N5 in general. I assure you, the N5 deserves all the praise (and criticisms) that it has received.ave you tried a different router? I know you used it with your iPhone's hotspot but I mean an actual router? Also, have you tried resetting your router to defaults?
Are you using MAC filtering on the router?
_MetalHead_ said:
I've had 4 N5's in my possession over the past year or so, and not a single one had any issues connecting to any WiFi network, including Netgear routers. Your problem is either specific to your particular device or your router and not with the N5 in general. I assure you, the N5 deserves all the praise (and criticisms) that it has received.ave you tried a different router? I know you used it with your iPhone's hotspot but I mean an actual router? Also, have you tried resetting your router to defaults?
Click to expand...
Click to collapse
I just tried a dlink router on my home network and everything works!!!!!
But i want to understand why my D6300 doesn't work with the nexus (its configured the same way as the dlink).
Any suggestions???
In the meantime i'll reset the D6300.
stevemw said:
Are you using MAC filtering on the router?
Click to expand...
Click to collapse
Nope, i've disabled it.
And btw i read on some forums of people using my netgear with the nexus 5 and everything was working just fine.
riki66 said:
Nope, i've disabled it.
And btw i read on some forums of people using my netgear with the nexus 5 and everything was working just fine.
Click to expand...
Click to collapse
If your router is handing out DHCP addresses it may have run out of addresses if you have many wireless devices connecting infrequently. But I would thing a reboot would have cleared that up.
Using a verizon note 5, marsmallow,with metropcs. ALL works as should. Excellent service, sms, mms even the my metro app. Hotspot works but with a weird problem... so I can connect every device in my house to my hotspot, except one connects and then says no internet. I can connect an Xbox 360, multiple laptops, 2 smart tvs, wiiu,tablets, and then the problem child, Amazon fire stick. It says connected, shows full bars for coverage, then it shows not connected to the internet. I've tried the old lollipop dhcp, I've tried 2.4ghz and 5ghz. To no avail, I cannot get it working for the life of me. I've tried tmobile apn and metro apn... now the weird thing is I can use my wife's note 5 from Verizon with verizon service and it connects and streams just fine. Just my Verizon note 5 with metropcs service, won't connect to that one device. Any input would be greatly appreciated. Thanks in advance
Any help or insight would be appreciated thanks
verizon hotspot app is limited to 10 devices.
Are you connecting more than 10 devices?
javamaan said:
verizon hotspot app is limited to 10 devices.
Are you connecting more than 10 devices?
Click to expand...
Click to collapse
No it was only the fire stick by itself. I came to the conclusion that even though metropcs works on a Verizon unlocked note 5, it doesn't have all the LTE bands so therefore my LTE speed wasnt fast enough to run the fire stick. Needless to say the note 5 has found another owner and I've moved on to the Nexus 6p. And now I have full LTE speeds and the fire stick works again. Thanks for your insight