Hey guys I did a search and found nothing. Any time I'm connected to Wi-Fi, I can't receive calls or texts. I'm on Sprint. Anyone else have this issue?
nein7three said:
Hey guys I did a search and found nothing. Any time I'm connected to Wi-Fi, I can't receive calls or texts. I'm on Sprint. Anyone else have this issue?
Click to expand...
Click to collapse
Yes, have done tons of research and am having a similar issue. It's believed to be software related. If LTE or Global are set as the "Preferred Network Type" under Mobile Network AND wifi is turned on, then the mobile signal cuts out when it goes to sleep. With 3G set, the phone works fine with wifi turned on. I've tried wiping the phone and also loaded the factory 4.4.2 image via fastboot this morning and still have the problem. Some people have RMA-ed their phones and still report the issue, so it must be a certain combination of settings. It's also being reported from Sprint and T-Mobile user, so it's not restricted to just one network. As for me, I'm on Sprint in NYC, have an AC router and using an Airave. My Galaxy S4 didn't have any problems.
Here are a few threads that I've found:
XDA - Signal Problem
XDA - Signal issues with new baseband solved by flashing older baseband
On Google's forums:
Nexus 5 sometimes doesn't ring when people are calling
Thanks man, I had read the Google thread but hadn't find the XDA ones. I'll try forcing 3g while on Wi-Fi.
No problem! If you're on Sprint, there is also this:
Circuit Switched Fallback Issues on Sprint
I'm in an area that is reported as not having the issue, so it's not that for me. Plus, I'm on 3G with the Airave. I remember having the HTC Mogul on Sprint and for a while it would just die if the signal was roaming. An update fixed it, but it wasn't fun. At least in this case the phone still works, not as advertised, but it works. Here's to hoping that it's fixed soon!
I'm the Tmobile user in the Google discussion. It's an annoying problem and hope it's fixed with 4.4.3. However the issue just happened to me in the last week before I got the 4.4.2 update. So I'm not sure what could have happened from a month ago when I got the phone until a week ago. Haven't installed any new apps since then.
This does seem to be working now that I am forcing 3g
Weird, right?
4.4.1 and 4.4.2 both have the same baseband and kernel. That's about the timeframe when the updates both came out, so I assume that maybe 4.4.1 is when the majority of users started seeing issues pop up?
From what I've read, this phone handles cell signals much differently because of the newer LTE TDD. It could be any number of things really, but I don't have the expertise to examine the code to see what was changed between the 4.4 and 4.4.1/4.4.2 baseband. I do believe that all of the Wifi and cell signal issue posts that are popping up now are related though.
I'm also noticing my wifi speeds bouncing all over the place (from ~180Mbps -- ~500Mbps) and I'm only a few feet away from my router. I have a Netgear r6300v2 AC router.
12/14/13 Update: I just got off of the phone with Sprint. They show that there is an internal memo on the issue and LG is aware of it. They will be pushing an update as soon as it's ready. Sprint will also be pushing an update for the Airave to help with the issue, starting on 12/19/13.
The support rep told me that it is an issue where the wifi and LTE radios aren't playing nicely together and it's causing this conflict. That's why everything seems to work fine when 3G is set as a preferred network.
PynkFloydd said:
Weird, right?
4.4.1 and 4.4.2 both have the same baseband and kernel. That's about the timeframe when the updates both came out, so I assume that maybe 4.4.1 is when the majority of users started seeing issues pop up?
From what I've read, this phone handles cell signals much differently because of the newer LTE TDD. It could be any number of things really, but I don't have the expertise to examine the code to see what was changed between the 4.4 and 4.4.1/4.4.2 baseband. I do believe that all of the Wifi and cell signal issue posts that are popping up now are related though.
I'm also noticing my wifi speeds bouncing all over the place (from ~180Mbps -- ~500Mbps) and I'm only a few feet away from my router. I have a Netgear r6300v2 AC router.
12/14/13 Update: I just got off of the phone with Sprint. They show that there is an internal memo on the issue and LG is aware of it. They will be pushing an update as soon as it's ready. Sprint will also be pushing an update for the Airave to help with the issue, starting on 12/19/13.
The support rep told me that it is an issue where the wifi and LTE radios aren't playing nicely together and it's causing this conflict. That's why everything seems to work fine when 3G is set as a preferred network.
Click to expand...
Click to collapse
thanks man!
do we have any update on the situation?
Yeah I wish there was an update soon because this problem is starting to become very annoying. Twice this week I had to check my Google Voice because my Text didn't go through on my phone
Anyone have a fix for this yet?
Does anyone know if any custom roms fix this?
I've read Google is aware of the issue and speculation says they will fix it with the 4.4.3 release.
questions:
(the 1st is stupid, but i'll ask anyways) - when this issue occurs, is the phone set to **wifi only** with 3g / lte in airplane mode?
or does it occur when just setting up wifi in ADDITION to 3g / lte?
&, when you typed Receiving no calls out texts while on WiFi , is your application for texting, hangouts?
if it's hangouts, then google neutered it to only allow text thru the cellular network,
but if you're simply joining a wifi hotspot at work or home, with your cellular network enabled, it SHOULD go thru, ive never had an issue like that with wifi toggled.. even with 4.4.1
---------- Post added at 03:54 PM ---------- Previous post was at 03:48 PM ----------
j'vai said:
questions:
(the 1st is stupid, but i'll ask anyways) - when this issue occurs, is the phone set to **wifi only** with 3g / lte in airplane mode?
or does it occur when just setting up wifi in ADDITION to 3g / lte?
&, when you typed Receiving no calls out texts while on WiFi , is your application for texting, hangouts?
if it's hangouts, then google neutered it to only allow text thru the cellular network,
but if you're simply joining a wifi hotspot at work or home, with your cellular network enabled, it SHOULD go thru, ive never had an issue like that with wifi toggled.. even with 4.4.1
Click to expand...
Click to collapse
~hint~
maybe it's simpler than one would expect (shot in the dark)
to sum it up;
on our new triband spark capable phones, does *automatic vs home only* in (change the cdma roaming mode) mean what we THINK it means in relation to it's single chip, single path architect??
back when, in dual pathed phones it MEANT roaming in another provider, when ecsfb, carrier aggregation, spark wasn't a thought..
but these newer triband phone are different beasts, & the effect of the patched worked, fit n finished network of cell sites of upgraded , non upgraded network vision, does toggling automate for smoother performance between these sites on these triband devices, with single paths....?
something as simple as a network toggle, to aid service (on the mobile client side) in this -
"In a CSFB environment, 2 important concepts are employed viz., Mobile Terminating Roaming Retry, Mobile terminating roaming forward. We will discuss MTRR in this blog. In a typical operator environment, voice coverage for the entire geographical area is achieved by employing many MSC’s. These MSC’s may be a mix of Legacy MSC (where upgrading is difficult/impossible) and next generation Softswitch MSC’s. In order to support CSFB, the MSC needs to be upgraded to support SGs interface, so the issue is how do we support CSFB when the UE is in Legacy MSC coverage. This is where MTRR helps in call delivery to Legacy MSC that does not support SGs"
from being parked on an lte channel, being called & successfully *inter-roaming* to 1xtt voice, evdo data (if used), then back to lte parking & usage when applicable..
~shrugz shoulderz~
for those with this issue, what are your setting like, in relation?
---------- Post added at 04:11 PM ---------- Previous post was at 03:54 PM ----------
j'vai said:
questions:
(the 1st is stupid, but i'll ask anyways) - when this issue occurs, is the phone set to **wifi only** with 3g / lte in airplane mode?
or does it occur when just setting up wifi in ADDITION to 3g / lte?
&, when you typed Receiving no calls out texts while on WiFi , is your application for texting, hangouts?
if it's hangouts, then google neutered it to only allow text thru the cellular network,
but if you're simply joining a wifi hotspot at work or home, with your cellular network enabled, it SHOULD go thru, ive never had an issue like that with wifi toggled.. even with 4.4.1
---------- Post added at 03:54 PM ---------- Previous post was at 03:48 PM ----------
~hint~
maybe it's simpler than one would expect (shot in the dark)
to sum it up;
on our new triband spark capable phones, does *automatic vs home only* in (change the cdma roaming mode) mean what we THINK it means in relation to it's single chip, single path architect??
back when, in dual pathed phones it MEANT roaming in another provider, when ecsfb, carrier aggregation, spark wasn't a thought..
but these newer triband phone are different beasts, & the effect of the patched worked, fit n finished network of cell sites of upgraded , non upgraded network vision, does toggling automate for smoother performance between these sites on these triband devices, with single paths....?
something as simple as a network toggle, to aid service (on the mobile client side) in this -
"In a CSFB environment, 2 important concepts are employed viz., Mobile Terminating Roaming Retry, Mobile terminating roaming forward. We will discuss MTRR in this blog. In a typical operator environment, voice coverage for the entire geographical area is achieved by employing many MSC’s. These MSC’s may be a mix of Legacy MSC (where upgrading is difficult/impossible) and next generation Softswitch MSC’s. In order to support CSFB, the MSC needs to be upgraded to support SGs interface, so the issue is how do we support CSFB when the UE is in Legacy MSC coverage. This is where MTRR helps in call delivery to Legacy MSC that does not support SGs"
from being parked on an lte channel, being called & successfully *inter-roaming* to 1xtt voice, evdo data (if used), then back to lte parking & usage when applicable..
~shrugz shoulderz~
for those with this issue, what are your setting like, in relation?
Click to expand...
Click to collapse
just a note -
if you look at slide 7 on the qualcomm snapdragon 800's chipset (you all already know this)
http://www.slideshare.net/jjwu6266/qualcomm-snapdragon-800-mobile-device
there's only ONE chip to handle wifi, 4g, 3g, bt, etc..
with lesser BoM (bill of materials) just maybe, top level s/w userspace toggles, handle more than what meets the eye, the point i was making in another thread..
which not only effects our nexus 5s, but even other phones in various ways depending on the implementation of sw/hd, of the same chipset family..
& sprint has mentioned for the forseeable future, of providing phones, with these types of chips from qualcomm..
~go figure~
nein7three said:
Hey guys I did a search and found nothing. Any time I'm connected to Wi-Fi, I can't receive calls or texts. I'm on Sprint. Anyone else have this issue?
Click to expand...
Click to collapse
the ONLY reason i pointed to the network settings *home vs automatic* in this situation, is because,
the qualcomm sd 800 is an asymmetric multiprocessor, (as will future chipsets be) & you're losing other core networking functions, while gaining another, when you SHOULD have available ALL facilities -
**ASMP vs SMP**
&
Symmetric Multiprocessing Vs. Asymmetric Processing
It actually occurs when the phone is connected to LTE and WiFi together. If my settings were to connect to 3G along with WiFi, SMS works fine.
I have to manually change my Mobile Network settings when I get to home or work, where I will be connecting to WiFi (note cellular service is always ,on, I didn't mean to make it sound as if I am trying to send SMS over WiFi). So when home I turn on WiFi along with 3G connectivity and when I leave I turn off Wifi and switch to LTE.
This issue has been happened while unrooted and running stock ROM and it still happens while rooted running Cataclysm.
Also note, the SMS we miss never will come through, it's not as if later on the message comes through...It's gone forever. It also prevents calls from coming through, it's not just limited to SMS.
nein7three said:
It actually occurs when the phone is connected to LTE and WiFi together. If my settings were to connect to 3G along with WiFi, SMS works fine.
I have to manually change my Mobile Network settings when I get to home or work, where I will be connecting to WiFi (note cellular service is always ,on, I didn't mean to make it sound as if I am trying to send SMS over WiFi). So when home I turn on WiFi along with 3G connectivity and when I leave I turn off Wifi and switch to LTE.
This issue has been happened while unrooted and running stock ROM and it still happens while rooted running Cataclysm.
Also note, the SMS we miss never will come through, it's not as if later on the message comes through...It's gone forever. It also prevents calls from coming through, it's not just limited to SMS.
Click to expand...
Click to collapse
try my suggestion; it won't hurt..
let us know if it rectified anything..
What worked for me was forcing 2G instead of 3G, hope it helps!
Related
Hello All,
I just updated to 4.4.3 last night and in the process have lost my ability to send or receive calls/SMS/MMS when connected to 3G.
When in range of LTE my phone operates fine, however when out of range (in my office) I am not able to connect to LTE and instead my phone drops to 3G which has typically been fine. Now however, my phone connects to 3G and has data access but cannot send or receive calls/SMS/MMS. When I pull down on the notification shade it says "Searching for Service."
I have enabled Band 41 and have set it at priority 1. I have tried disabling it to no avail. I have tried placing the phone on Global & LTE (recommended) and still do not have Phone functionality.
I went so far as to wipe data/cache/dalivk and it still is not working.
Any thoughts?
shahnyl said:
Hello All,
I just updated to 4.4.3 last night and in the process have lost my ability to send or receive calls/SMS/MMS when connected to 3G.
When in range of LTE my phone operates fine, however when out of range (in my office) I am not able to connect to LTE and instead my phone drops to 3G which has typically been fine. Now however, my phone connects to 3G and has data access but cannot send or receive calls/SMS/MMS. When I pull down on the notification shade it says "Searching for Service."
I have enabled Band 41 and have set it at priority 1. I have tried disabling it to no avail. I have tried placing the phone on Global & LTE (recommended) and still do not have Phone functionality.
I went so far as to wipe data/cache/dalivk and it still is not working.
Any thoughts?
Click to expand...
Click to collapse
Not to sound like a A$$ but started a thread for sprint and the update. There is a lot of useful info from many people in there.
Seriously it's so bad for me and my wife I put us back on 4.4.2
It got worse.your issue it sounds like is what we dealt with. It is the 3g/LTE handoff.it gets hung. You can try toggle airplane.
I reread your post.Yeah your suffering like us.try what I said. 4.4.3,crippled us in our area.
habitformer said:
Not to sound like a A$$ but started a thread for sprint and the update. There is a lot of useful info from many people in there.
Seriously it's so bad for me and my wife I put us back on 4.4.2
It got worse.your issue it sounds like is what we dealt with. It is the 3g/LTE handoff.it gets hung. You can try toggle airplane.
I reread your post.Yeah your suffering like us.try what I said. 4.4.3,crippled us in our area.
Click to expand...
Click to collapse
Can you direct me to this thread you created. I have the exact same issue above and can not find a solution anywhere.
http://www.androidcentral.com/t-mobile-add-wi-fi-calling-support-its-nexus-6-model-early-2015
Shipping with Android 5.0, the new Nexus 6 gives customers the latest and greatest Google mobile experience, and seamless integration with the apps they love. Plus, this hot new smartphone is expected to support Wi-Fi Un-leashed beginning in early 2015 with an over-the-air update– making it the first-ever Nexus device that will support Wi-Fi Calling thanks to enhancements in Android 5.0. And only with the Un-carrier can customers use the latest, super-sized devices the way they were meant to be used – with no annual service contract, no domestic overages and unlimited music streaming all on the nation's fastest LTE network, plus unlimited data and texting in 120+ countries and destinations − and now, Wi-Fi Un-leashed.
Click to expand...
Click to collapse
Will this be exclusive to the Nexus 6? If it is, surely it will be possible to port it to the Nexus 5?
Here's to hoping we get this included in our 5.0 update.
my first thought, which is nothing more than a guess, is that this will be hardware based on the N6 and "unlocked" with a T-Mo OTA and will not be able to be ported to the N5.
Lucke said:
my first thought, which is nothing more than a guess, is that this will be hardware based on the N6 and "unlocked" with a T-Mo OTA and will not be able to be ported to the N5.
Click to expand...
Click to collapse
considering Tmobile is making this feature available in early 2015 with an OTA I think you are right in guess that this will be something Tmobile bakes into the OS and not functionality native in Android L
Edit: Unless Google has a planned update for L in early 2015 that Tmobile knows about (I highly doubt it)
Improved network handoffs resulting in limited interruption in connectivity. For example, continue your video chat or VoIP calls without interruption as you leave the house and switch from your home Wi-Fi back to cellular
thats from here https://www.android.com/versions/lollipop-5-0/
I think wifi calling and voLTE are going to be baked into 5.0 no matter the carrier
david279 said:
Improved network handoffs resulting in limited interruption in connectivity. For example, continue your video chat or VoIP calls without interruption as you leave the house and switch from your home Wi-Fi back to cellular
thats from here https://www.android.com/versions/lollipop-5-0/
I think wifi calling and voLTE are going to be baked into 5.0 no matter the carrier
Click to expand...
Click to collapse
that's my suspicion as well..
google may bake hangouts code (or the hangouts dialer code) into the native dialer, making them one & the same -
http://forums.androidcentral.com/google-nexus-5/436152-nexus-5-likely-see-wi-fi-calling-over-t-mobile-soon-4.html#post3918556
david279 said:
Improved network handoffs resulting in limited interruption in connectivity. For example, continue your video chat or VoIP calls without interruption as you leave the house and switch from your home Wi-Fi back to cellular
thats from here https://www.android.com/versions/lollipop-5-0/
I think wifi calling and voLTE are going to be baked into 5.0 no matter the carrier
Click to expand...
Click to collapse
but that doesn't necessarily mean that t-mobiles wi-fi calling feature, or VoLTE compatibility is baked into 5.0. VoLTE is too new to test fully, and while that may work, you can't use VoLTE on wi-fi. the features you're talking about is the issue of dropping signal for that split second when you leave your house (the time where wi-fi drops off and cell doesn't re-establish itself instantly) for the purpose of hangouts (voice or video).
i still think that since the N5 isn't compatible with t-mo's wi-fi calling, it's not just a software thing.
that is talking about network handoff in general, nothing about hangouts. And the ota to enable this feature will be released next year so its probably being tweaked now to be ready for next year.
---------- Post added at 03:02 PM ---------- Previous post was at 02:58 PM ----------
also wifi calling has never been a hardware feature, its all software. back in the day of early CM(7 or 8) wifi calling was added to all the T-mo htc phones and it was the same as its being done today. A apps and a couple of libs in /system.
in other words, the feature doesn't need a carrier add -on (ims core registration), if it's OS software based..
even right now, we *have it* on the nexus 5, with gv / hangouts / number integration, on wifi & lte & I can stream a youtube vid & be on a call at the same time, so right now, it's a given in the userspace via apps, as an over the top solution (works dam well too)
a revision of android L may deeply provide a seemless solution with it's update; I suspect this much.. (the carrier's ims' Ok on data voice is only complementary) but, can be worked around..
j'vai said:
even right now, we *have it* on the nexus 5, with gv / hangouts / number integration, on wifi & lte & I can stream a youtube vid & be on a call at the same time, so right now, it's a given in the userspace via apps, as an over the top solution (works dam well too)
Click to expand...
Click to collapse
its not the same thing. you go from cell signal call to a wifi call with the same number. it is not VoIP.
Zepius said:
its not the same thing. you go from cell signal call to a wifi call with the same number. it is not VoIP.
Click to expand...
Click to collapse
even currently, hand-offs isn't reliable, votle / wifi calling is more, stationary than anything, from what I've been reading from the experiences of users on tmobile & Verizon..
with the over the top solution now on the nexus 5 (or many adroid devices), same difference;
one better, technically the nexus 5 isn't even supported on Verizon, but yet, can have voice over lte on Verizon (AWS) with a lte data only connection ..
on other networks, it matters not what the data air interface is, the call can be made, with one solution..
j'vai said:
even currently, hand-offs isn't reliable, votle / wifi calling is more, stationary than anything, from what I've been reading from the experiences of users on tmobile & Verizon..
Click to expand...
Click to collapse
this is impossible. Verizon does not have wifi calling at this time.
you cannot compare VoLTE to tmobile's WIFI calling as they are not the same.
VoLTE is only VoIP over LTE. nothing more.
tmobile's wifi calling is a regular cell signal call that can become a VoIP call but still use the original tmobile number.
Zepius said:
this is impossible. Verizon does not have wifi calling at this time.
you cannot compare VoLTE to tmobile's WIFI calling as they are not the same.
VoLTE is only VoIP over LTE. nothing more.
tmobile's wifi calling is a regular cell signal call that can become a VoIP call but still use the original tmobile number.
Click to expand...
Click to collapse
look at what you've typed, & go back & re-read what you quoted from me...
......
"Keyan X
3 hours ago
The nexus 5 can access and use Verizon LTE its been proven and confirmed"
"iavaj jj
3 hours ago (edited)
+Keyan X I'm not disagreeing with you that it DOESN'T work; just expanding that, from my prior post, one can have unfettered data & voice on Verizon's LTE band 4, where coverage is..
Google gave the nexus 5 a backdoor with the new hangouts dialer.."
---------- Post added at 09:12 PM ---------- Previous post was at 09:08 PM ----------
Zepius said:
this is impossible. Verizon does not have wifi calling at this time.
you cannot compare VoLTE to tmobile's WIFI calling as they are not the same.
VoLTE is only VoIP over LTE. nothing more.
tmobile's wifi calling is a regular cell signal call that can become a VoIP call but still use the original tmobile number.
Click to expand...
Click to collapse
"on other networks, it matters not what the data air interface is, the call can be made, with one solution.. "
I'm on sprint, with gv integration, all I'd need is data -
http://forums.androidcentral.com/google-nexus-5/436152-nexus-5-likely-see-wi-fi-calling-over-t-mobile-soon-5.html
anywhere in the world, I'd have the same 202 (wash dc) area code calling out..
j'vai said:
even currently, hand-offs isn't reliable, votle / wifi calling is more, stationary than anything, from what I've been reading from the experiences of users on tmobile & Verizon..
with the over the top solution now on the nexus 5 (or many adroid devices), same difference;
one better, technically the nexus 5 isn't even supported on Verizon, but yet, can have voice over lte on Verizon (AWS) with a lte data only connection ..
on other networks, it matters not what the data air interface is, the call can be made, with one solution..
Click to expand...
Click to collapse
nexus 5 does not work on voice over lte(volte) that verizon has. yes, verizons volte just began. no, the nexus 5 does not work on it. only thing that the n5 can do on verizon is get data.
simms22 said:
nexus 5 does not work on voice over lte(volte) that verizon has.
Click to expand...
Click to collapse
if it can ALREADY obtain the lte data service ( as in the youtube video) what would hinder gv from making & receiving calls with an over the top solution, with just Verizon acting as a dumb pipe?
it hasn't stopped me on sprint, nor tmobile, I guess it wouldn't stop me on att..
what would stop it on Verizon?
j'vai said:
look at what you've typed, & go back & re-read what you quoted from me...
......
"Keyan X
3 hours ago
The nexus 5 can access and use Verizon LTE its been proven and confirmed"
"iavaj jj
3 hours ago (edited)
+Keyan X I'm not disagreeing with you that it DOESN'T work; just expanding that, from my prior post, one can have unfettered data & voice on Verizon's LTE band 4, where coverage is..
Google gave the nexus 5 a backdoor with the new hangouts dialer.."
---------- Post added at 09:12 PM ---------- Previous post was at 09:08 PM ----------
"on other networks, it matters not what the data air interface is, the call can be made, with one solution.. "
I'm on sprint, with gv integration, all I'd need is data -
http://forums.androidcentral.com/google-nexus-5/436152-nexus-5-likely-see-wi-fi-calling-over-t-mobile-soon-5.html
anywhere in the world, I'd have the same 202 (wash dc) area code calling out..
Click to expand...
Click to collapse
you still do not understand the difference between VoIP, VoLTE, and wifi callling
I guess the majority are stuck on the schematics of volte, as only being ims based implemented by the carrier, also wifi calling or it ain't real -
"VoLTE, Voice over LTE is an IMS-based specification. Adopting this approach, it enables the system to be integrated with the suite of applications that will become available on LTE."
http://www.radio-electronics.com/info/cellulartelecomms/lte-long-term-evolution/voice-over-lte-volte.php
I'm not swayed by market speak, when the solution is at hand already, market speak sways many to purchases not needed, wen what they had in hand already could have done the job perfectly..
j'vai said:
if it can ALREADY obtain the lte data service ( as in the youtube video) what would hinder gv from making & receiving calls with an over the top solution, with just Verizon acting as a dumb pipe?
it hasn't stopped me on sprint, nor tmobile, I guess it wouldn't stop me on att..
what would stop it on Verizon?
Click to expand...
Click to collapse
thats fine, use your google voice number on the data only connection. you said that voice calls work over volte. when in fact they do not. older lte tech did not allow voice calls over lte, so when you made calls, you switched to H or 3G. this new tech allows calls over lte now, which needs a device that can call over lte. the nexus 5 can not call over lte, but most new phones will be able to now.
Zepius said:
you still do not understand the difference between VoIP, VoLTE, and wifi callling
Click to expand...
Click to collapse
market speak aside the division of wifi, lte, voip calling, is calls over data - which I expressed my sentiment here (posted for the second time)-
http://forums.androidcentral.com/google-nexus-5/436152-nexus-5-likely-see-wi-fi-calling-over-t-mobile-soon-5.html#post3929214
guess I need to copy & paste w/o the pics -
"have a hacker mindset, & push things to work how you want them;
forget simply wifi calling, I want it all, *data calling* irrelevant of the air interface used;
I have a truphone sim, that was collecting dust in my wallet for the longest, last night I decided to try something,
*use it*, lol
it had like $39 odd on it in credit, as stated, I'm a current sprint sub, with google voice integration, I've gave the truphone number to no one, it's basically dormant, minus test calls to keep the account alive, but it's no contact number for me..
what I'm did last night was swap my sprint sim, for the truphone sim, to utilize it's data, while still having my main sprint number via google voice, which I can receive & make, calls, videochat, mms, sms via hangouts, I've set hangouts to *receive incoming calls* since the native dialer isn't tied to the sprint sim anymore (so no double rings from hangouts & the native dialer)...
I want to see how far that $39 will take me..
at home & at work, I'm connect to wifi, so only in between, out & about am I utilizing truphone AKA tmobile's hspa data service-
all calls via the hangouts / gv / sprint number are nothing but data calls, ither on tmobile's hspa or wifi, likewise with sms, mms, & of course video chat.."
I won't have to upgrade from the nexus 5, for the same feature set..
j'vai said:
market speak aside the division of wifi, lte, voip calling, is calls over data - which I expressed my sentiment here (posted for the second time)-
[SNIP]
I won't have to upgrade from the nexus 5, for the same feature set..
Click to expand...
Click to collapse
congrats. you discovered VoIP.
VoIP is not the same as VoLTE
VoIP is not the same as WIFI calling.
i'm correcting you because you are spreading mis-information.
simms22 said:
thats fine, use your google voice number on the data only connection. you said that voice calls work over volte. when in fact they do not. older lte tech did not allow voice calls over lte, so when you made calls, you switched to H or 3G. this new tech allows calls over lte now, which needs a device that can call over lte. the nexus 5 can not call over lte, but most new phones will be able to now.
Click to expand...
Click to collapse
*my voice calls over lte with google voice on the nexus 5 works wOnders*
& I can use the browser, stream from youtube while on a call.. I don't have to wait for the carriers to *OK* the phone from their IMS core.. I simply go over the top of it, for the same functionality..
[Not Fixed] see bottom of this post.
It is fairly easy to install a new D6603 to work completly on the AT&T network. It is not so easy to find the answer of how to do it in the threads and posts. I tried many suggestions and wasted a lot of time. Hopefully this will save you from that fate.
First you must know that you can't use the IMEI number of your new phone if you want it to work completly as it should. If you use the Z3 IMEI you will have trouble with data of various sorts and the phone will go off line when on LTE after 20 or 30 minutes and you will not receive calls or SMS messages. I do not know why but it has been suggested that the AT&T network does not recognise this phone so it causes trouble.
If you have an AT&T nano-sim from your old phone then just put it in the phone. (Cut downs work but can cause other problems some say.) When the SIM is inserted for the first time into a new phone there is a prompt that asks if you want to download the APN. Hit 'yes' and the phone downloads the APN itself.
If it does not ask then go to Settings>More>Mobile Networks>Prefered Network Type and be sure LTE (Preferred) is selected. Then connect your phone to the internet and then go to Settings>More>Internet Settings and select AT&T. You should be good to go.
If you need to get a nano-sim then go to the AT&T store or call and they will give you one or send you one for free. You will need to use the IMEI number from a LTE phone that is already on the AT&T system. You can use your old phone or borrow the number from someone. If the rep installs the sim in the Z3 with the 6603 IMEI don't worry. Just call support later and tell them you sent your new phone back and want to go back to your old IMEI or have a new IMEI (from an existing AT&T phone). They will enter it and off you go. The phone from the IMEI will show in the picture on your account page. Big deal!
Update: This worked for hours last night but this morning it is back to not receiving calls. Simply turning wifi off and it began to receive calls as GPRS was switched back on. My wifi was on which has been said to cause problems. I will test with wifi off and report back. Had "no service" instead of AT&T on upper left of lock screen. A full shut down for several minutes than re-boot solved that.
YMMV. I've been on ATT with a Z3 purchased from Sony store for several months and it was registered in an ATT store by scanning the IMEI off the box followed by updating Internet settings in Setup. ATT online shows unknown model but everything works including LTE and MMS. There is something else involved when problems like this occur probably some setting not getting reset. I registered the Z3 on a new line with a new Sim card because I wanted to take my time moving stuff off my old phone--this may have avoided the problems.
JudH said:
YMMV. I've been on ATT with a Z3 purchased from Sony store for several months and it was registered in an ATT store by scanning the IMEI off the box followed by updating Internet settings in Setup. ATT online shows unknown model but everything works including LTE and MMS. There is something else involved when problems like this occur probably some setting not getting reset. I registered the Z3 on a new line with a new Sim card because I wanted to take my time moving stuff off my old phone--this may have avoided the problems.
Click to expand...
Click to collapse
I've also had no problems with my Z3 on AT&T. Works great, receives sms/mms immediately, etc..
esheesle said:
I've also had no problems with my Z3 on AT&T. Works great, receives sms/mms immediately, etc..
Click to expand...
Click to collapse
AT&T's system sometimes takes a while to get updated with new IMEIs that trigger LTE provisioning for a users' account.
Once your account is provisioned for LTE you never have to worry about it again, but sometimes if you have a phone the system doesn't recognize, it is a pain to get AT&T to properly provision your account. Supposedly properly trained in-store reps can do it - the key being "properly trained" - Never try to do anything "unusual" by calling AT&T customer service, and NEVER use a franchise/kiosk in-person for service - make sure you're at a corporate-owned store! Even then, some stores might have incompetent staff. I've been lucky that all of my local corporate stores are pretty well staffed.
So you are saying that your Z3's with wifi and LTE on with AT&T are working as they should?
With LTE off my phone responds normally with wifi on. With LTE and wifi on it will not respond to calls after a 30 minute sleep. It does not show missed calls. Calls go straight to voice mail after 2 rings. Could you tell me what level your LTE dBm's are? Thanks!
I was told not to give them my imie# but, after recvng the minisim I had to call them in order to 'provision' it to work at all and they needed that #. I have never had any problems personally and am assuming this may be because you gave them the wrong #. Again I am only guessing. Oth, if I had had a different imie to give, I would have done so myself.
It is very strange and I am feeling it is more signal strength related than how you provision your phone. (Once it is provisioned correctly.) It seems that more people have less problems when they already have a nano-sim and just plunk it in the new phone. This might indicate that they already had a strong signal from the get go. My old HTC One + get's a better signal than the Sony in the same locations with the same (new) SIM. With the Devilcase bumper on it gets 5% less. My very limited tests yesterday seemed to indicate that it was signal strength related. I am not enough of a conspiracy theorist to imagine that AT&T would program their system to not function correctly with sims that are provisioned with these Sony phones which they are obviously ignoring for some reason. Or am I?
I had all kinds of problems with the Z3 on AT&T. The IMEI caused an issue since AT&T linked it to a flip phone and therefore couldn't provision LTE. I changed it to an old AT&T LTE device and then I was able to get LTE but was having the same issue with calls going directly to voicemail and texts showing up hours later in bunches. I found the solution was to switch off LTE in the quick settings menu. All calls and texts came through and on time while LTE was off. If I needed a data boost to stream, I turned it back on until I was finished streaming. This was while on KitKat. After upgrading to Lollipop, I was able to keep LTE turned on and calls and texts still arrived on time.
I use data rarely. Mostly wifi. If I don't leave LTE on, my phone reverts to wcdma preferred. And why can't LTE just work without me having to constantly turn it back on? What bugs me is having the APN settings greyed out. I want to be able to turn it off. If anything it seems the phone itself is preventing me from accessing the sim. It feels like I'm borrowing something which contains lots of MY private data. I know my phonebook is stored locally but I also noticed there is no option of specifying the sim or not. Anybody know how to switch APN on and off? In fact, overall even rooted, I still feel like I have almost no power over it. I can't even disable the cellular connection without going full on airplane mode and I do not trust that. I don't even fly so that needs work for sure. Dumb question but could I buy a working nanosim from say 7-eleven that my apn switch will work with?
"Anybody know how to switch APN on and off?"
On my Z3 on OTA stock Lollypop I have an icon in quick settings to turn LTE on and off. Drag two fingers down from the top of the screen. If no LTE icon then select the pencil icon at the top and select the LTE icon. There is also a mobile data icon switch there.
To turn off your radio completly you can get the Advanced Signal Status app and select additional info at the bottom and click phone information and turn off radio. Probably a number of ways to do it but that is one.
Sim contact storage was a way to move information from phone to phone. You can still do it but not really necessary with cloud backup and storage. Google does it for me without me having to do anything which I like. I still save contacts to the sim just because I can. Export and import in your contacts app menu.
johnboatcat said:
So you are saying that your Z3's with wifi and LTE on with AT&T are working as they should?
With LTE off my phone responds normally with wifi on. With LTE and wifi on it will not respond to calls after a 30 minute sleep. It does not show missed calls. Calls go straight to voice mail after 2 rings. Could you tell me what level your LTE dBm's are? Thanks!
Click to expand...
Click to collapse
Works fine here. I don't pay attention to the dBm estimates since these aren't measured with calibrated test equipment and vary widely. Those numbers are basically worthless.
The only valid comparison is data performance in a given environment (ideally a difficult weak-signal one) - and at my desk with very weak signal, every phone I've ever used performs similarly to the Z3.
"Those numbers are basically worthless."
True, but we have narrowed this down to the possibility that it might be signal related so it is worth a shot. If people whose phones are working fine would measure the LTE dBm on Advanced Signal Status at the location where their phone sits and works well the most we might possibly see some measure of difference in the phones that are not working. Most of the non-working phones seem to work sometimes so signal strength is the next best parameter to rule out. Thanks!
Here are the screen shots of my phone with LTE on, LTE and wi-fi and LTE off and wi-fi.
How do the working phones compare? Does your CDMA (voice) also go to 0% when LTE is on and GSM = n/a?
Thanks. I think adv sig nfo actually works. I'm amazed actually. I can't find the phone's native greyed out apn switch anyways which really makes no sense.
Does anyone know how to activate wi-fi calling on the Z5? I figured it'd be a menu setting, but I can't find it. I'm using the Taiwan version of the Compact and am using MetroPCS here in the States.
Thanks.
To answer my own question. It appears that wi-fi calling is only available with some carrier phones. So for instance, EE in England says on their setup page,
"WiFi Calling is only available on the EE version of the Sony Xperia Z5 Compact, bought directly from us in one of our stores, online at EE.co.uk, through our telesales team, or through corporate sales if you are a corporate customer."
So, I guess my question now is, is there a way to flash the phone so that I can get this feature on my non-EE phone? My carrier, MetroPCS, does allow wi-fi calling, but they don't sell the Z5 (and likely won't ever sell it).
You can try flashing the EE ROM with flashtool and see if you have that option. You will get carrier specific bloatware as well.
Would I be able to delete the bloatware? And I'm new to Android. When I flash, does it delete all of my settings and downloads and whatnot? I'm assuming I can back them up someplace in case it does, but like I say, I'm new to this. Also, where would I get the EE Rom from?
Look for Xperifirm. Download and install. You can get the firmware there. Next download flashtool version 0.9.19.10. You can bundle the firmware files into a ftf and flash, both with flashtool. Read the respective guides. To keep data, look at options when flashing and choose not to wipe user data. I would type it up but the instructions are on XDA, just search.
Neither WiFi calling or VoLTE will not work on the Sony Z5 unless your carrier/network offers the Sony Z5 for sale directly.
Note, WiFi Calling and VoLTE are two separate features but similar network functions on the operators side.
Note, MetroPCS is a sub-brand of the T-Mobile USA network so Metro is pretty much TMo USA.
Since T-Mobile USA does not offer the Z5 you will not be able to get WiFi calling working. In order for WiFi Calling or VoLTE to be supported the network operator must customize the ROM to include the WiFi calling and/or VoLTE network configurations. Unlike the typical SIM card and APN settings which are industry standard and can be adjusted manually. WiFi calling and VoLTE are somewhat more complex and include carrier/network specific security certificates to work. Apple can get away with supporting WiFi calling and VoLTE simply by swapping SIMs because the T-Mobile configs are loaded into their core iOS software which goes out to everyone around the world. (Probaly one of the reasons the iOS eats up so much storage...but i digress) Android runs much leaner and does not carry all the extra configs for all global networks...hence a carrier (i.e. T-Mo US) tweaked version of the Z5 ROM would be required for this all to work.
If T-Mobile USA offers the Z5 in the future you may be able to unlock the boot-loader and flash the T-Mobile specific ROM onto your phone and get WiFi Calling and VoLTE to work. But if T-Mo USA never offers the Z5 then you will never have WiFi calling supported.
Hope that helps....
WiFi calling and VoLTE are pretty much the same thing...just VoIP. And in most operators case WiFi Calling and VoLTE are the same back end network call processing systems. VoLTE is easier for the operator to secure as the customer is using the operators LTE and IP network. WiFi calling is seen on fewer operators as it requires more security since you can access the operators network from any public or private IP network.
---------- Post added at 10:28 PM ---------- Previous post was at 10:20 PM ----------
and in theory you could extract the WiFi calling stack form the EE network's Z5 ROM and load it into a custom ROM. That would give you the software capability to support WiFi calling....But you will still need the T-Mobile USA WiFi calling fqdn for the WiFi border controller and their security certificates which are typically specific to a handset model. And again since TMo does not offer the Z5 there are no Z5 certificates.
Ah, well that sucks.
Yeah I feel ya, I love WiFi calling too
Some network providers have their own apps to allow it. Like in the UK, O2 network has an app called TU go
All hope isn't lost - Android M is supposed to have a provision for wifi calling. I've read posts of people with Nexus 6's on M (google play editions, so no carrier specific models) that have been able to use wifi calling. The current loss of band 12 (hoping this will change too) as well as the loss of wifi calling as a fallback has been the only drawback to this otherwise excellent handset. I absolutely love the thing. It just works, no fuss.
I know this isn't helpful, especially for those outside of the US, but this is why I ported my number to google voice a long time ago. VOIP works great over Wifi for me most of the time and when I have LTE reception, I can still use Voip albeit with increased data consumption.
shizenyasuya said:
I know this isn't helpful, especially for those outside of the US, but this is why I ported my number to google voice a long time ago. VOIP works great over Wifi for me most of the time and when I have LTE reception, I can still use Voip albeit with increased data consumption.
Click to expand...
Click to collapse
Do you know of any guides for how this is supposed to work? I have Google Voice, and I have Hangouts, but I'm not sure how they're supposed to work in tandem for wi-fi calling. Would I be forced to actually open up the Google Voice app in order to make wi-fi calls? How is that any different from something like Talkatone?
Adrift98 said:
Do you know of any guides for how this is supposed to work? I have Google Voice, and I have Hangouts, but I'm not sure how they're supposed to work in tandem for wi-fi calling. Would I be forced to actually open up the Google Voice app in order to make wi-fi calls? How is that any different from something like Talkatone?
Click to expand...
Click to collapse
Yeah, that's a bit of a pain in the ar$3. I install google voice and hangouts on any phone/tablet I get, Google voice is necessary to route all outgoing calls through GV so that my GV number shows up on my call partner's caller ID. (even though you can dial directly from the native phone dialer) I install Hangouts to manage sms and google talk (now just google hangouts but specified to avoid... or contribute to, (as the case may be) confusion) messages. You can also dial directly from Google Hangouts (this is the only option when you're only using Wifi, without cellular signal) So my thought flow kinda goes like this.
To make a call:
1)check for cell signal, if there is signal, use the native dialer to place a call
2) if there is only WiFi, use hangouts (or hangouts dialer) to place a call
Receiving calls: (If you need help I can tell you the specific settings)
1)when the phone rings, determine if it's ringing via Hangouts or the native phone app
2) check for cellular signal and wifi signal
3) if cell signal is 2g only, only answer with the native phone app (sometimes hangouts will ring first) and I have to wait for the native phone app to realize there is a call coming in (forwarded of course to my cellular provider number from GV)
4)if connected to WiFi, or I have LTE coverage (sometimes even on 3g) pick up the hangouts ring.
Sometimes I do miss calls because I'm waiting for the native phone app to ring when I'm on 2g, but hangouts rings first and the native phone app doesn't ring, but those instances are fairly infrequent and I can just call them back.
---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------
Adrift98 said:
Do you know of any guides for how this is supposed to work? I have Google Voice, and I have Hangouts, but I'm not sure how they're supposed to work in tandem for wi-fi calling. Would I be forced to actually open up the Google Voice app in order to make wi-fi calls? How is that any different from something like Talkatone?
Click to expand...
Click to collapse
Also, sorry I've never used Talkatone, so I don't know if it works any differently. You don't have to have google voice installed to make / receive wifi calls via hangouts. you just have to have opted in to hangouts on your google voice account. The ONLY reason I still install GV is to make sure that when I make outgoing calls from the native phone app, my GV number shows up on the recipient's caller ID. They should really just bake this into hangouts and completely depreciate the GV app.
You could port the t-mobile wifi calling apps from the z3. I ported wifi calling to my att g2 from the t-mobile rom. It's not really that hard if you know how to read logcats
Many retail mobiles have "Wifi Calling" function but not any menu entry to enable , The APP can check the hidden function and enable it if can use.
https://play.google.com/store/apps/details?id=com.widget7.wifi.calling
Hello XDA Community!
When my new phone (Huawei P9 Lite Mini) is on 3G/2G auto network mode, it consumes more battery than LTE/3G/2G auto mode even mobile data off.
I do not understand how this happens? For example, while 3G consumption at overnight is %10-15; LTE is only %2-3. This problem is the same in daytime too. Mobile data is off, unneccesary services/apps disabled, and no extra application installed while this happens. I tried all "wipe/factory reset/update firmware/factory reset/wipe/no app install" procedures, enabling all battery saving options, but it did not work. This is a problem for me when I'm in non-LTE areas.
This problem occurs the same result in different locations. There was no problem with my previous phone and I use same nano sim card.
I tried the following but it did not work:
- Wipe cache, factory reset, wipe cache,
- Wipe data/factory reset over recovery menu,
- Update latest firmware, wipe data etc. again.
How this happens and where am I doing wrong? Thank you for your help, best regards!
EDIT: PROBLEM SOLVED!
I changed my mobile carrier (provider) and the problem is gone. This is very interesting! I worked for hours and days to solve the problem, but this problem is neither caused by the phone nor by the software...
WCDMA (aka 3G with support for 2G/Edge) is in always-on mode on most phones, because that's how you receive and emit phone calls and, for most phones, SMS (in some more recent phones, LTE takes care of sending and receiving SMS/MMS), so if you're in an area where 3G/2G reception is poor, your phone has trouble locking on a cell with enough power to maintain contact, hence the battery drain.
4G/LTE only works for data, and voice if you have VoLTE (Voice over LTE) enabled, but works on a on-demand mode, even with cellular data constantly enabled. In other words, the 4G modem on your phone will memorize the latest position and IP address the nearest 4G tower/cell allocated it, and connect to it using the memorized settings when you need it to.
Not so with 3G, where DHCP doesn't exist, at least not the way it does in 4G: it uses PPP (Point-to-Point Protocol), where an ad-hoc IP address is attributed to each new connection, based on a pool of existing addresses allocated to the tower and its owner (carrier) by the authorities.
UglyStuff said:
WCDMA (aka 3G with support for 2G/Edge) is in always-on mode on most phones, because that's how you receive and emit phone calls and, for most phones, SMS (in some more recent phones, LTE takes care of sending and receiving SMS/MMS), so if you're in an area where 3G/2G reception is poor, your phone has trouble locking on a cell with enough power to maintain contact, hence the battery drain.
4G/LTE only works for data, and voice if you have VoLTE (Voice over LTE) enabled, but works on a on-demand mode, even with cellular data constantly enabled. In other words, the 4G modem on your phone will memorize the latest position and IP address the nearest 4G tower/cell allocated it, and connect to it using the memorized settings when you need it to.
Not so with 3G, where DHCP doesn't exist, at least not the way it does in 4G: it uses PPP (Point-to-Point Protocol), where an ad-hoc IP address is attributed to each new connection, based on a pool of existing addresses allocated to the tower and its owner (carrier) by the authorities.
Click to expand...
Click to collapse
Thank you for your reply!
When I googled about 3G vs. LTE battery consumption, everyone says that LTE will consume more batteries. That's make sense on first thought. So what I've been through is very interesting to me.
I think about is there a problem with my phone's 3G antenna. (footnote: I don't know about that 3g and LTE antennas are same or seperate?)
But I understand that you say this is normal, right?
Edit: I found a forum that this problem may be due to the operator (carrier). I'm still investigating...
3G and 4G operate on basically the same principle: receiving and sending "information" via radio waves.
The difference lies in the frequencies each standard uses, the way the data sent over them is modulated and demodulated, and how handsets make and maintain connection, so if you stay in the same location, and set your phone to 3G-only, then switch Airplane mode on then off, it'll take your phone longer to reconnect to the 3G cell/tower with the strongest signal (not necessarily the closest to you), because it'll have to go through the whole getting-acquainted process again, whereas in 4G, it'll go straight to the "Hey, how do you do? Long time, no see".
Now, if your phone antenna has a problem, you could be standing a few feet from the tower, in line of sight, and still get a crappy to non-existent signal. How many bars are showing on your screen is just an indication of how well your phone is receiving the signal from the tower; it doesn't mean that this signal is consistent and steady, hence the bars coming and going in real time.
If I were you, I'd download and install the Hidden Settings app from the Play Store, and run it; there, you go to RadioInfo, and you'll get a lot of information about how your phone modem actually works. It's a bit technical, but it would give you an indication.
I will try and looking for a new carrier. Thank you again. See you.
I changed my mobile carrier (provider) and the problem is gone. This is very interesting! I worked for hours and days to solve the problem, but this problem is neither caused by the phone nor by the software...