[Q] Secret / Dialer Codes for Galaxy Tab 7.7 - Galaxy Tab 7.7 Q&A, Help & Troubleshooting

Hello,
I've noticed that most of the well knwon Samsung Secret and Dialer Codes are not working on the new Galaxy Tab 7.7 P6800. Are there known solutions for this? Other codes that are working?

I noticed the same thing.

RiverSource said:
Hello,
I've noticed that most of the well knwon Samsung Secret and Dialer Codes are not working on the new Galaxy Tab 7.7 P6800. Are there known solutions for this? Other codes that are working?
Click to expand...
Click to collapse
Yes all known USSD/MMI Codes are working on GINGERBREAD on my SGSII but not on SGT7.7 with HONEYCOMB. I think its cause HONEYCOMB

I have found, that some of the codes can be used with the App "SGS Secret Codes".
Since the codes are working, I think, they are filtered by the Dialer App.

RiverSource said:
I have found, that some of the codes can be used with the App "SGS Secret Codes".
Since the codes are working, I think, they are filtered by the Dialer App.
Click to expand...
Click to collapse
Only 2 of those codes work, the one to check the imei and another one which I font remember, the others nothing. Im looking for the one that shows the frequencies and you are able to enable/disable then. I wan to check what frequentcy my tab picks up while running T-Mobile sim
Sent from my SGH-T959 using XDA App

adinis78 said:
Only 2 of those codes work, the one to check the imei and another one which I font remember, the others nothing. Im looking for the one that shows the frequencies and you are able to enable/disable then. I wan to check what frequentcy my tab picks up while running T-Mobile sim
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
You mean this one? *#*#197328640#*#*
It works.
I'm still trying to find the *#*#9900#*#* one the works. Something to find and disable Fast Dormancy...

Jade Eyed Wolf said:
You mean this one? *#*#197328640#*#*
It works.
I'm still trying to find the *#*#9900#*#* one the works. Something to find and disable Fast Dormancy...
Click to expand...
Click to collapse
Yea thats the one i was refering to
Sent from my GT-P6800 using xda premium

Funny thing, i tried downloading the sgs codes app and now i have access to the frequency selector i have set up the tab to work on 1900mhz now i have to try and see if i can get full 3g+voice on tmobile. Will report back.
Sent from my GT-P6800 using xda premium

Maybe we can get in touch with the lidroid developer. I would like to have some other codes, like *#272*IMEI#. I will try it next week.

How about the lcd test menu?

Ok so while taking my dog out i took my tsb and wanted to see if it would pick up 3g with tmobile. and the result is, no. See the following and you will notice that 1900mhz is selected:
View attachment 888880
View attachment 888881
View attachment 888889
View attachment 888890
The first pic shows the tab connected at 1900mhz but if you look at the bottom right hand corner it shows as running on Edge. So maybe its picking up Sprints signal and Tmobile has not rolled out the 1900mhz over on the east coast?
EDIT: please let me know if you are able to see the pics. Everytime I go into the thread the pics are not coming up
Sent from my GT-P6800 using xda premium

No, the pics aren't displayed. I get the message, "Invalid attachment specified".

redb33s said:
No, the pics aren't displayed. I get the message, "Invalid attachment specified".
Click to expand...
Click to collapse
K thanks, ill repost by tomorrow
Sent from my SGH-T959 using XDA App

test menu code
EarlZ said:
How about the lcd test menu?
Click to expand...
Click to collapse
Please try this code, *#*#0*#*#*

Some codes that work
Did a lot of searching and found out a few that work
*#*#1234#*#* (To get the PDA/Phone/CSC versions)
*#*#0011#*#* (ServiceMode)
*#*#4636#*#* (Diagnostic and general settings mode)
You can see a pattern here...

adinis78 said:
So maybe its picking up Sprints signal and Tmobile has not rolled out the 1900mhz over on the east coast?
Click to expand...
Click to collapse
Nah, you're not going to be able to pick up Sprint anything, even if they use the same frequency bands; totally different technologies CDMA vs GSM/UMTS. Actually, believe it or not, UMTS has a lot in common with CDMA, but it's still not compatible. CDMA, specifically EV-DO, uses 1.25mhz spectrum channeling for it's available bandwidth. Also, it's simply a data stack, hence the "DO" in EV-DO (stands for Data Optimized). Modern CDMA networks still rely on a 1xRTT network for their voice stack. Because both stacks are separated by two different technology standards, the phone device can only really use one at a time. It is theoretically possible to do both, but that would require essentially two modems, one dedicated for voice, and one dedicated for data, but cost and complexity likely make that prohibitive. Instead, it's cheaper for CDMA devices to incorporate a modem that switches between the two stacks (voice/data) on demand, while keeping the idle stack on hot standby. That's why CDMA phones can't do data and voice simultaneously (easily).
UMTS (AKA WCDMA, or Wideband CDMA) on the other hand, is a whole different ball game. Because UMTS is technically a CDMA based technology, it also utilizes code division multiplexing as opposed to the time division multiplexing scheme used by legacy GSM. However, that's about where the similarities end. UMTS uses 5mhz spectrum channeling (4x the channel bandwidth of traditional CDMA/EV-DO!). Also, both voice and data are separated logically, instead of physically, by using dedicated slices of that 5mhz for their respective tasks. Essentially, part of that 5mhz channel will be dedicated to circuit switched voice access, and the remaining channel bandwidth is dedicated to packet switched data. In this way, a single modem can be easily used to perform both voice and data simultaneously because both protocol stacks are rolled into one nice neat package.
To draw an analogy, think of CDMA like having two plates of some Mexican food. One plate has your veggies (like your beans and rice), and the other plate has your meat (like your beef, chicken, or pork). By protocol standards, you're only allowed to eat from one plate at a time.
With UMTS, you're basically taking all those same ingredients, and rolling it all together into a burrito!
P.S. I've tried enabling the 1700mhz band via the service menu, and attempted to get 3G signal on a T-Mobile SIM, but no luck. No 1900mhz T-Mo 3G in the Washington DC area either btw.

Ok here are pics that didnt load on my original post
Sent from my GT-P6800 using xda premium

Jade Eyed Wolf said:
Nah, you're not going to be able to pick up Sprint anything, even if they use the same frequency bands; totally different technologies CDMA vs GSM/UMTS. Actually, believe it or not, UMTS has a lot in common with CDMA, but it's still not compatible. CDMA, specifically EV-DO, uses 1.25mhz spectrum channeling for it's available bandwidth. Also, it's simply a data stack, hence the "DO" in EV-DO (stands for Data Optimized). Modern CDMA networks still rely on a 1xRTT network for their voice stack. Because both stacks are separated by two different technology standards, the phone device can only really use one at a time. It is theoretically possible to do both, but that would require essentially two modems, one dedicated for voice, and one dedicated for data, but cost and complexity likely make that prohibitive. Instead, it's cheaper for CDMA devices to incorporate a modem that switches between the two stacks (voice/data) on demand, while keeping the idle stack on hot standby. That's why CDMA phones can't do data and voice simultaneously (easily).
UMTS (AKA WCDMA, or Wideband CDMA) on the other hand, is a whole different ball game. Because UMTS is technically a CDMA based technology, it also utilizes code division multiplexing as opposed to the time division multiplexing scheme used by legacy GSM. However, that's about where the similarities end. UMTS uses 5mhz spectrum channeling (4x the channel bandwidth of traditional CDMA/EV-DO!). Also, both voice and data are separated logically, instead of physically, by using dedicated slices of that 5mhz for their respective tasks. Essentially, part of that 5mhz channel will be dedicated to circuit switched voice access, and the remaining channel bandwidth is dedicated to packet switched data. In this way, a single modem can be easily used to perform both voice and data simultaneously because both protocol stacks are rolled into one nice neat package.
To draw an analogy, think of CDMA like having two plates of some Mexican food. One plate has your veggies (like your beans and rice), and the other plate has your meat (like your beef, chicken, or pork). By protocol standards, you're only allowed to eat from one plate at a time.
With UMTS, you're basically taking all those same ingredients, and rolling it all together into a burrito!
P.S. I've tried enabling the 1700mhz band via the service menu, and attempted to get 3G signal on a T-Mobile SIM, but no luck. No 1900mhz T-Mo 3G in the Washington DC area either btw.
Click to expand...
Click to collapse
We all know that we cant get 3g on 1700mhz with tmobile only edge thats why i wanted to see if enabling 1900mhz would work. But i wonder how i am picking it up if tmobile has not implemented it here on the east coast, guess ill just have to keep waiting until they do. No point in calling tmobile and ask them as i am sure they would not have any clue.
Sent from my GT-P6800 using xda premium

phseet said:
Did a lot of searching and found out a few that work
*#*#1234#*#* (To get the PDA/Phone/CSC versions)
*#*#0011#*#* (ServiceMode)
*#*#4636#*#* (Diagnostic and general settings mode)
You can see a pattern here...
Click to expand...
Click to collapse
Go to the market and download the sgs secret codes app it will give you a bunch of codes
Sent from my GT-P6800 using xda premium

adinis78 said:
Ok here are pics that didnt load on my original post
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Having looked at your pictures there, it looks like you're connecting on GSM 1900 (which T-Moblie does support). This is 2G, not 3G/4G. If it were, GSM would be replaced by UMTS or something. See my pic in the attachment.
Also, see how it says WCDMA 1900 Band 2? It'll tell you if it's using UMTS/WCDMA or not.

Related

G2x In Europe

Hey guys!
Going to the States tomorrow, I saw this beast is quite cheap unlocked in Amazon, so I'm currently thinking of buying it.
But just to be 100% sure, is there anything is should take note on? I'm from Denmark which also use GSM and same frequencies (I think).
Thanks in advance!
If it uses the same frequencies, then you should be fine. But take note, the G2x doesn't include the FM Radio.
Sent from my LG-P999 using xda premium
I've never in my life used FM radio, so I can live with that
Prozel said:
I've never in my life used FM radio, so I can live with that
Click to expand...
Click to collapse
Never used FM radio? Its a new age indeed. Lol
So i bought one, but how come 3G don't work? I have typed in the right APN.
Prozel said:
So i bought one, but how come 3G don't work? I have typed in the right APN.
Click to expand...
Click to collapse
Does the g2x support your network 3G frequencies?
Sent from my LG-P999 using XDA App
Several web sites say Denmark uses 2100 MHz for 3G. Could check the phone settings under "Wireless and networks/Mobile network settings/Data enabled" and make sure data is enabled. Alos check "Network Mode" to make sure it is not on GSM only.
Both things are as you say, and i'm pretty sure MIUI (a backup) was on it for a short time, but it's doesn't connect, weird.
I'm using mine in Thailand on 2100 so that is not the problem. Almost all European carriers use 2100. Make sure you go to APNs in the Networks settings and enter the correct APN for your carrier, give it a name and save it. Then press the radio button to make the selection green. Are you using Network Enabler? That will screw you up if active the first time you are trying to connect to a new network. If you are using that uninstall it or disable it. Also get a program from the Market called Networks. Use it to make sure the phone internally is not set to 2G only. I had that happen once on a phone and it did not show in the settings menu. With that program you can set it to WCDMA Only or WCDMA Preferred. Here is a link to the program.
https://market.android.com/details?id=de.mangelow.network
Prozel said:
So i bought one, but how come 3G don't work? I have typed in the right APN.
Click to expand...
Click to collapse
Did you end up using this in Europe? I'm going in fall for school & plan to travel all over. Are you using a local sim card to use it on their towers? I was thinking of just getting a pre-paid sim card there on my buddies unlocked blackberry, but I'd love to use my G2X if possible!
Thanks!

PRL

I've heard this phone runs a different PRL series...55xxx. Anyone pulled it yet? I'd like to get a copy to run an analysis on it.
I'm on 55006
Sent from my XT897 using xda app-developers app
gtownswagga said:
I'm on 55006
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Same here
Sent from my XT897 using xda premium
digiblur, if no one can pull it, give me some instructions and I can pull it tomorrow night from my mom's phone
jefbal99 said:
digiblur, if no one can pull it, give me some instructions and I can pull it tomorrow night from my mom's phone
Click to expand...
Click to collapse
I don't have this phone so I am not sure how to do it. You might do some other searches on loading prls with qpst on similar Motorola phones. To pull it is simple if you can get qpst working with it. You just hit read instead of write.
Sent from my C64 w/Epyx FastLoad cartridge
Looks like it's a bit more intensive. I'll have access to the phone all weekend on a family camping trip. If I can get wifey and mom to watch the kids, I'll dig it out of there
I don't mean to sound overly noobish... I understand what PRLs are, but how could changing them be beneficial? Is there some way to just simply have you phone lock to the tower with highest signal strength?
I live in an apartment where I get next to no sprint signal which drops calls like crazy, if I stand in certain spots in the building I can get it to roam which gives me 3 bars... and calls are clear and never drop... I assume the PRL has something to do with this?
wolfie359 said:
I don't mean to sound overly noobish... I understand what PRLs are, but how could changing them be beneficial? Is there some way to just simply have you phone lock to the tower with highest signal strength?
I live in an apartment where I get next to no sprint signal which drops calls like crazy, if I stand in certain spots in the building I can get it to roam which gives me 3 bars... and calls are clear and never drop... I assume the PRL has something to do with this?
Click to expand...
Click to collapse
With Sprint introducing 800Mhz 1xA for voice, PRLs can be used to search for that signal over 1900Mhz PCS. Also, it can be used to force roaming
jefbal99 said:
With Sprint introducing 800Mhz 1xA for voice, PRLs can be used to search for that signal over 1900Mhz PCS. Also, it can be used to force roaming
Click to expand...
Click to collapse
Is this something that can be selected on demand similar to the wifi selections? I remember seeing somewhere on the phone to select a network, but it only has Auto and Sprint.
No, a PRL has to either be pushed/updated by the carrier via OTA or flashed by a user.
wolfie359 said:
I don't mean to sound overly noobish... I understand what PRLs are, but how could changing them be beneficial? Is there some way to just simply have you phone lock to the tower with highest signal strength?
I live in an apartment where I get next to no sprint signal which drops calls like crazy, if I stand in certain spots in the building I can get it to roam which gives me 3 bars... and calls are clear and never drop... I assume the PRL has something to do with this?
Click to expand...
Click to collapse
Try Roam Control have to Google it.
Sent from my MB855 using xda premium
I second the Roam Control suggestion, have used it for a year and a half now on my Epic....I force into roaming every day in my home office at work. Even then the signal fluctuates some roaming Verizon, but its almost always crappy with Sprint while at work...our building sucks for cell penetration.
wolfie359 said:
I don't mean to sound overly noobish... I understand what PRLs are, but how could changing them be beneficial? Is there some way to just simply have you phone lock to the tower with highest signal strength?
I live in an apartment where I get next to no sprint signal which drops calls like crazy, if I stand in certain spots in the building I can get it to roam which gives me 3 bars... and calls are clear and never drop... I assume the PRL has something to do with this?
Click to expand...
Click to collapse
I called and complained about that very same thing and they offered me an Airave for free. Might be worth trying considering they can terminate your service if you roam too much.
http://support.sprint.com/support/device/Sprint/AIRAVE_by_Sprint-dvc1230001prd
Here's a zipped folder with some of Sprint's current LTE PRLs. The xx006 PRLs contain information pertaining to the future LTE developments that are rolling out. Below's the contents of what's in the zip and what they are, to my knowledge these are the ones that allow 3G roaming:
16006: LTE PRL (don't have much information on this one)
24006: CL LTE PRL (recommended)
54006: Advanced World Mode CL LTE PRL (CL and designed for international travel)
56006: LTE PRL (found on demo devices at the stores)
I'm not going to do a write up for how to flash PRLs or pull them from the Photon Q. Mostly because I'm lazy and can't be bothered, and there's plenty of well written tutorials floating around XDA as is.
QPST?
I tried to pull this guy up in QPST as soon as I got it to flash the 1119 PRL, but I wasn't able to get QPST to see the phone. Anyone else had this issue? Or resolve it?
haveigonemental said:
I tried to pull this guy up in QPST as soon as I got it to flash the 1119 PRL, but I wasn't able to get QPST to see the phone. Anyone else had this issue? Or resolve it?
Click to expand...
Click to collapse
Trying to get my PRL updated as well and QPST is not having any of it. I tried similar steps to the previous photon without success, anyone know what needs to be done here?
I have tried many different ways to get a custom PRL on this thing without success. I can get it into dev mode using ##3424# and then I also check developers mode in the Development menu and still can not do it. QPST just does not see it. One thing that does happen with the above steps is that windows tries to install drivers for various motorola stuff. QC interface and the like. I can not locate those drivers anywhere. Anyone?
are you sure it has a qualcomm radio? the galaxy nexus and sgs3 all have VIA chipsets
shabbypenguin said:
are you sure it has a qualcomm radio? the galaxy nexus and sgs3 all have VIA chipsets
Click to expand...
Click to collapse
The S3 is qualcomm from what I heard. Thought it was the same as the Evo Lte.
Hope it doesn't have those garbage Via licensed cdma chipset.
On another note, if you do load a different prl on this device, like 12124, let me know if LTE still works.
Sent from my C64 w/Epyx FastLoad cartridge
US GS3s are Qualcomm. We have a few of the newer QPST build links on our site.
We're able to push/pull from VIA chipsets as well. The Galaxy Nexus was fully flashed to Cricket and that involves more than just a PRL.
I came to this thread looking for a method of obtaining the MSL/SPC for the Photon Q. I am not a Sprint customer.

Will the Nexus 5 support VoLTE?

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?

Which band is missing on the N920T from the N920A?

I'm having a hard time finding a definitive answer about which LTE band I'll lose using the tmobile variant on att.
I don't think any, I think both are identical. I am using the N920T with AT&t. I would suggest you consider using DarthStalkers ROM, he was able to pull the AT&T carrier files.
The N920T & A are the same. If you had bought the N920I you might lose bands.
Does anyone know where I can get a band 12 coverage map? I can only find the LTE coverage map which doesn't specify if band 12 is used there
wdkingery said:
I'm having a hard time finding a definitive answer about which LTE band I'll lose using the tmobile variant on att.
Click to expand...
Click to collapse
17 and 30 (I don't think the 920t's band 12 will work with AT&T's B17 - even though 12 is a subset of 17 (or do I have that backwards?) Possibly 29 (downlink only for AT&T) - but there's very little documentation on B29, so I'm not sure if the N920A supports it or not.
garyd9 said:
17 and 30 (I don't think the 920t's band 12 will work with AT&T's B17 - even though 12 is a subset of 17 (or do I have that backwards?) Possibly 29 (downlink only for AT&T) - but there's very little documentation on B29, so I'm not sure if the N920A supports it or not.
Click to expand...
Click to collapse
Could you be so kind as to translate what that will mean to me? I have a t-mobile note 4 here on att and it seems to do fine.. Do you think I'll be so lucky with the note 5?
wdkingery said:
Could you be so kind as to translate what that will mean to me? I have a t-mobile note 4 here on att and it seems to do fine.. Do you think I'll be so lucky with the note 5?
Click to expand...
Click to collapse
Band 29 is rarely used by AT&T (only as a downlink in heavily congested areas.) This shouldn't be a problem.
Band 30 (WCS band) is something AT&T _just_ started deploying, but I've never seen it in actual use. In fact, until very recently, none of AT&T's own phones supported it. B30 is really of limited value for general use due to it's propagation (or lack thereof.) Like 29, its probably only used as a supplement to other bands. I wouldn't worry about B30.
B17, however, is a Big Deal for AT&T. That's AT&T's primary "lower frequency" LTE band. Because of the low frequency, it has excellent propagation (meaning it moves farther and through trees, buildings, etc.) They use this band to cover large geographical areas with minimal towers. If you will be using your phone in a non-urban area, B17 is almost essential for AT&T. (My phone spends the majority of the time at my home on B17.)
I haven't heard of anyone with a TMO Note 5 device (without explicit B17 support) attaching to AT&T's B17, but that doesn't mean it won't work. However, Unless someone confirms B17 functionality on the n290T from actual use (and not just what they think), I'd suggest assuming that it won't work.
garyd9 said:
Band 29 is rarely used by AT&T (only as a downlink in heavily congested areas.) This shouldn't be a problem.
Band 30 (WCS band) is something AT&T _just_ started deploying, but I've never seen it in actual use. In fact, until very recently, none of AT&T's own phones supported it. B30 is really of limited value for general use due to it's propagation (or lack thereof.) Like 29, its probably only used as a supplement to other bands. I wouldn't worry about B30.
B17, however, is a Big Deal for AT&T. That's AT&T's primary "lower frequency" LTE band. Because of the low frequency, it has excellent propagation (meaning it moves farther and through trees, buildings, etc.) They use this band to cover large geographical areas with minimal towers. If you will be using your phone in a non-urban area, B17 is almost essential for AT&T. (My phone spends the majority of the time at my home on B17.)
I haven't heard of anyone with a TMO Note 5 device (without explicit B17 support) attaching to AT&T's B17, but that doesn't mean it won't work. However, Unless someone confirms B17 functionality on the n290T from actual use (and not just what they think), I'd suggest assuming that it won't work.
Click to expand...
Click to collapse
An informative post if ever there was one indeed.
What app do you use to determine which hand your phone is connected thru? I have found this app "LTE discovery", and it seems my att note 3 stays connected to 5 mostly, or 4 for lte. But then for GSM is doesn't list a band, but appears connected. On her t-mobile note 4 connected to att, she stays on 5, but the GSM doesn't appear to be connected to anything..
We will be almost exclusively in the middle of a city, but as with anything that could change or in the event of a road trip..
Is there a place I can sit and study this information? Perhaps a website with all of this data? Or do you happen to work in the field?
In a sea of noobs, an informed person is a real diamond in the rough - I appreciate your time.
wdkingery said:
What app do you use to determine which hand your phone is connected thru? I have found this app "LTE discovery", and it seems my att note 3 stays connected to 5 mostly, or 4 for lte.
Click to expand...
Click to collapse
That's a good app to use. I also use my phone's diagnostic menu's, but I doubt AT&T left those enabled on the 'a' variant.[/QUOTE]
wdkingery said:
But then for GSM is doesn't list a band, but appears connected. On her t-mobile note 4 connected to att, she stays on 5, but the GSM doesn't appear to be connected to anything..
Click to expand...
Click to collapse
Is that with "lte discovery" that she doesn't appear to have any GSM side connection? She most likely does, as that's where voice calls will take place...
wdkingery said:
Is there a place I can sit and study this information? Perhaps a website with all of this data?
Click to expand...
Click to collapse
Google. Then google some more. If you run out of pages from google, use another search engine. All the information is readily available - it just takes time to find it all.
garyd9 said:
That's a good app to use. I also use my phone's diagnostic menu's, but I doubt AT&T left those enabled on the 'a' variant.
Click to expand...
Click to collapse
Is that with "lte discovery" that she doesn't appear to have any GSM side connection? She most likely does, as that's where voice calls will take place...
Google. Then google some more. If you run out of pages from google, use another search engine. All the information is readily available - it just takes time to find it all.[/QUOTE]
so i got through all the hoops.. don't have LTE ;-(
it connects to band 4 or 5 when i first come out of airplane mode, but it jumps right back off. stuck on 4g. called at&t for an hour, they said initially it wasn't provisioned on my sim card, but then afterwards they determined it was a problem on my end, walked my thru APN settings and then ended the call.. still no LTE.
do you have an opinion of what i could do?
wdkingery said:
do you have an opinion of what i could do?
Click to expand...
Click to collapse
Quoting me in a thread was enough... didn't have to also PM me...
@TEKHD has a firmware that might work for you. Check it out over here: http://forum.xda-developers.com/tmo...h6-tekxodus-n5-urv1-00-00-lollipop-5-t3201869
He has apparently provided a mechanism that is working for other AT&T users... (probably via loading the AT&T RIL libs.)
I haven't tried this (and I don't even have a 't' variant myself.) On the other hand, a quick search of that thread seems to show that other people are having successes with AT&T sim's on 't' variant devices.
Good luck!
Gary
sorry about the double.
after a precursory examination, idon't see exactly what you are talking about in his thread..
is it a download?
garyd9 said:
Quoting me in a thread was enough... didn't have to also PM me...
He has apparently provided a mechanism that is working for other AT&T users... (probably via loading the AT&T RIL libs.)
Good luck!
Gary
Click to expand...
Click to collapse
the search feature doesn't appear to work for me; shows 0 results on att or at&t.. i'm having to sift thru all 114 pages by hand.
garyd9 said:
He has apparently provided a mechanism that is working for other AT&T users... (probably via loading the AT&T RIL libs.)
Gary
Click to expand...
Click to collapse
i searched all 114 pages and didn't find reference to any of that.. now i know why search provided no results; there weren't any!
so i need to find the att ril libraries. how will i ever find that.
wdkingery said:
i searched all 114 pages and didn't find reference to any of that.. now i know why search provided no results; there weren't any!
so i need to find the att ril libraries. how will i ever find that.
Click to expand...
Click to collapse
Maybe that was the wrong firmware... it's something in the TMO dev section. Please search.
garyd9 said:
Maybe that was the wrong firmware... it's something in the TMO dev section. Please search.
Click to expand...
Click to collapse
i've searched the entire tmo dev section for term "at&t" and there are sparse hits; there is some conversation about CSC for a guy in canada getting his VoLTE working, but nothing on att.
wdkingery said:
i've searched the entire tmo dev section for term "at&t" and there are sparse hits; there is some conversation about CSC for a guy in canada getting his VoLTE working, but nothing on att.
Click to expand...
Click to collapse
Apparently, you already found it: http://forum.xda-developers.com/tmo...on-1-aroma-t3212091/post63516726#post63516726
This has AT&T RIL's in the update.zip, and from a quick look at the first post in that thread, they are installed based on an aroma installer. Others in that thread claim it works for them. You're using a TMO device on ATT, so you have to expect some level of incompatibility. There are AT&T LTE bands that the TMO device simply doesn't support. It doesn't matter what happens with your Note 4. Different device and different modem.
So, if you want to use a TMO device on ATT, you'll have to make some sacrifices. Most people will find the sacrifices are less drastic using an international version of the phone. For some reason, US carriers go out of their way to ensure their devices are incompatible with each other.
garyd9 said:
Apparently, you already found it: http://forum.xda-developers.com/tmo...on-1-aroma-t3212091/post63516726#post63516726
This has AT&T RIL's in the update.zip, and from a quick look at the first post in that thread, they are installed based on an aroma installer. Others in that thread claim it works for them. .
Click to expand...
Click to collapse
ok this is where i started, by flashing the ATT option for this rom. but that doesn't solve the problem. i'm in the process of clean flashing the tmobile choice like he suggested.
thanks for all your help.
i'm afraid this isn't going to work either. i realize the wife's note 4 may have different hardware, and isn't a good reference.
i can see the thing connect to band 5, then band 4, lte .. but it's in "emergency calls only" mode, then it gives up on that, connects to HSUPA or HSPA+ and that's the last of an LTE connection.
i feel like it would connect if it could, and that i'm having a software issue.
problem solved guys sorry for the large headache..
Solution:
AT&T did not recognize my IMEI as being LTE capable. Because of that, they decline to allow my phone to connect to LTE. My phone would connect to an LTE tower (as in the screen shots a few pages back), but wouldn't receive anything back from AT&T, so it would say "emergency calls only" and then give up after about 10 seconds, and then never go back. Crap data all around at this time.
What you'll need to do is walk into an AT&T store, take a picture of the IMEI off an LTE phone, and then call in and change your IMEI to the phone you found. This will cause the system to recognize your phone as LTE capable, and like magic, you'll have LTE.
I can confirm that I have a tmobile branded unit that attaches to band 17. It isn't as frequently as on my note 4, I'm generally on band 2. With that said I've had virtually no trouble with service. I was initially worried about the b17 issue, but it hasn't seemed to make any difference.
intifadamericana said:
I can confirm that I have a tmobile branded unit that attaches to band 17. It isn't as frequently as on my note 4, I'm generally on band 2. With that said I've had virtually no trouble with service. I was initially worried about the b17 issue, but it hasn't seemed to make any difference.
Click to expand...
Click to collapse
Does it attach to band 17 on AT&T or t-mobile?

? How to get LTE speed on US LTE tablet running ROW LTE Image?

Hi folks,
I've got the US LTE original Shield tablet, which is the replacement that NVidia sent me for my original "pyro edition" tablet. Since ATT haven't released the Nougat (Android 7, software package 5.0 or 5.1) builds for this tablet, but the ROW tablets are able to get this update, I flashed my tablet using adb/fastboot with the full ROW 5.0 package downloaded from the NVidia site. I then connected to WIFI, and let it pull down the 5.1 update. Factory reset, flash TWRP, rooted with SuperSU. Easy peasy. Then I set up the tablet with my accounts and such.
Based on good info from user @Son-j I made two build.prop edits, changing ro.build.flavor to wx_na_do-user (was wx_un_do-user) and ro.product.name to wx_na_do (was wx_un_do). This changed the reported signal type from H+ to 4G. Unfortunately I'm having trouble finding the thread where he suggested doing this. I think it was on the geforce web forum.
The only problem I've found so far is that I'm not getting LTE speeds. I was in Chicago for a couple days, in an area with strong LTE signal, and my other devices were reporting LTE and getting ~20Mbps down / 10+ Mbps up. My Shield was pulling maybe 8 Mbps down at best , and 1-2 Mbps up. At home in my suburban location, the difference is negligible (most devices here do 5 Mbps down / 1 Mbps up, LTE or 4G).
Still, I'd like to fix this if possible. Are there further edits or flashings that will let my US device running the ROW build get LTE? I have gone in and verified that my APN settings are the recommended ones from ATT. These showed up automatically, and matched the ATT recommendations.
Thanks in advance!
Hi I'm not sure but I there was a thread here in XDA that says it's still difficult to change the LTE (RoW to US, and vice versa) bands because developers couldn't find yet which part of the code to modify... It's not also confirmed if it is indeed possible to change the LTE bands to support.
So basically, flashing RoW LTE on US LTE device will still result in US-LTE supported bands. That's what I understood.
But what you did is quite a revelation. Can anyone else confirm that modifying the build prop will work? Boy I'm excited!
Son-j said:
Hi I'm not sure but I there was a thread here in XDA that says it's still difficult to change the LTE (RoW to US, and vice versa) bands because developers couldn't find yet which part of the code to modify... It's not also confirmed if it is indeed possible to change the LTE bands to support.
So basically, flashing RoW LTE on US LTE device will still result in US-LTE supported bands. That's what I understood.
But what you did is quite a revelation. Can anyone else confirm that modifying the build prop will work? Boy I'm excited!
Click to expand...
Click to collapse
Hi @Son-j -
Thanks! Do you happen to remember which thread had those two buildprop edits? I found them after seeing a post from you a few days ago, but now I can't find it at all. My google mojo has fled me.
I'd like to have a link there so others can see the original source.
It would be nice to get LTE speed, if someone knows how, but most places where I use the tablet don't have super fast LTE, so the difference for me isn't enough to make me downgrade to the marshmallow US LTE build. I'll stick with nougat for now, and hope eventually to get full speed. Who knows, maybe ATT will eventually release the 5.1 US LTE build...
For clarity here is the set of APN settings I'm using. I'm going with the column in the center at the bottom for Tablets:
https://www.att.com/esupport/article.html#!/wireless/KM1062162
All of this was correctly entered by default except I did need to edit two keys:
APN was listed as broadband instead of Broadband (yes, I'm picky, but wanted to match case)
APN type was listed as just default. I edited it to match the listed setting of: default,mms,supl,hipri,fota
Also I'm set to LTE for "Preferred network type"
Ok I think there's a misunderstanding. Uhm, I'm trying to look for the related posts here at the Nvidia threads but it seems to have disappeared.
Just to set something straight, LTE speed is influenced by:
1. LTE device with specific supported LTE bands
2. LTE sim
3. Location with LTE signals
I take it that for your specific device - US LTE Shield Tablet (just like mine) - you satisfy all 3.
For the record, flashing RoW LTE on our US device won't change the supported LTE bands (check baseband code in About Tablet section of settings). So if you used to have AT&T LTE speeds/signals using US LTE ROMs, it shouldn't change if you flashed RoW LTE ROM on the same device.
We are speculating though that there might be a way, software/firmware speaking. We are hoping it's not hardware-baked.
Son-j said:
Ok I think there's a misunderstanding. Uhm, I'm trying to look for the related posts here at the Nvidia threads but it seems to have disappeared.
Just to set something straight, LTE speed is influenced by:
1. LTE device with specific supported LTE bands
2. LTE sim
3. Location with LTE signals
I take it that for your specific device - US LTE Shield Tablet (just like mine) - you satisfy all 3.
For the record, flashing RoW LTE on our US device won't change the supported LTE bands (check baseband code in About Tablet section of settings). So if you used to have AT&T LTE speeds/signals using US LTE ROMs, it shouldn't change if you flashed RoW LTE ROM on the same device.
We are speculating though that there might be a way, software/firmware speaking. We are hoping it's not hardware-baked.
Click to expand...
Click to collapse
Thanks Son-j. It kind of freaks me out that just a week ago I found the thread that recommended those two changes in buildprop, but now I can't find it, and apparently neither can you! So maybe I'm not crazy, since it's more than just me having problems finding it.
Anyway, yes, I used to get the LTE indicator on the tablet, when in an area that has decent reception of those bands. At my workplace, which is a building built like a Faraday cage, we can get only ATT service, via repeaters spread throughout the building (I switched from Verizon in part due to this). Phones almost always report ~3 bars of LTE in places I usually find myself within the building. However, speeds tend to be <10 Mbps (tested using Speedtest.net from either my phone or tablet). So, despite getting "LTE service" there (prior to my software update), the speeds were nothing so great. For this reason, I'm not TOO worked up that my US tablet running ROW software isn't reporting LTE... most places where I use the tablet don't have blazing fast LTE, and the difference between the 4G service it actually gets and the LTE it "used to get" is not that great.
I would like to fix the problem if possible, but it's not a critical thing, and I may just put it on the back burner until the US LTE 5.1 image comes out, then flash back to that. I've got lots of other fish to fry these days.
Always interesting discussion. Thanks Son-j!
Marc
If it's just a speed issue, that will be the provider's end. If it's a signal issue, that's device problem.
It's possible to get an LTE signal but with HSPA speed in some areas.
There is an app called LTE Discovery. It will tell you which band it is currently connected to. I've got it on my tablet on T-Mobile. I am having problems with it connecting to anything other than 3G. But I have read others with the Shield tablet having similar problems with T-Mobile.
Sent from the Delta Quadrant using Tapatalk
caseyatbt said:
There is an app called LTE Discovery. It will tell you which band it is currently connected to. I've got it on my tablet on T-Mobile. I am having problems with it connecting to anything other than 3G. But I have read others with the Shield tablet having similar problems with T-Mobile.
Sent from the Delta Quadrant using Tapatalk
Click to expand...
Click to collapse
Thanks @caseyatbt,
I was unaware of that app. I downloaded it on my phone (which gets LTE just fine at my house, most of the time) and it reports all kinds of fun stuff about the LTE signal it's connected to. On the US Shield tablet running ROW stock, this is what I get, which frankly makes me think the tablet is connecting via CDMA of all things, despite having chosen all the correct options in the Settings / Mobile section:
The fact that my radio seems to be connecting to WCDMA instead of GSM is kinda freaking me out, folks.
I'm tempted to try flashing the US LTE device Marshmallow recovery image, and see if that fixes it. I understand the flashes don't change the baseband, but since I flashed 5.0 and the the device did an OTA update to 5.1, that might have changed the baseband, eh?
So, if me flashing the marshmallow files doesn't fix it, I might reflash an earlier edition and let it OTA to latest edition, which presumably would install correct "latest" baseband for the model.
We'll see ... I'm still not committed to one direction or another.
Marc
OK, I just flashed the 4.4.0 version of Marshmallow. (full flash of all Nvidia recovery image files). After letting it reboot the first time, it checked for update and found none, as expected.
NO LTE. Downloded the LTE Discovery app, and it still only sees WCDMA signals. Uggh.
Now I'm going to install the 4.3, and let it OTA to 4.4, and hope that refreshes the modem/radio. If anybody is following this, wish me luck!
EDIT: OK, I'm in idiot mode. I downloaded what I thought was the 4.3 US LTE image and it was actually the 4.3 ROW image. I didn't notice this until after flashing, and seeing the H+ icon, and noticing lack of ATT usage tracking app. Oops.
I don't see the 4.3 US LTE image on the site; I'm now downloading the 4.1 image, and will do OTA updates from there, checking as I go how which signal my radio is getting.
No Joy.
I flashed US LTE 4.1 image. AFter the flash, LTE Discovery still reports just HSPA+ signal from WCDMA towers. I then let it take the OTA for 4.4... the latest available for the US LTE tablet, and after it ran through its update process, I'm still on WCDMA.
Uggh. I doubt there's any WCDMA signal where I work so I may have killed my tablet, at least as far as using it at work is concerned.
I'm sure there IS a path back, I just can't imagine what it might be, at the moment. I'll start a new thread to be more specific to this current problem.
Sigh.
Frankenscript said:
Thanks Son-j. It kind of freaks me out that just a week ago I found the thread that recommended those two changes in buildprop, but now I can't find it, and apparently neither can you! So maybe I'm not crazy, since it's more than just me having problems finding it.
Click to expand...
Click to collapse
Eventually found that thread with the buildprop changes, see here if interested or if you ever need to find it.
I just checked my Shield on T-Mobile. In the same area on LTE Discovery that yours says W-CDMA mine says the same thing (under Neighbor Cells). When you scroll to the bottom, what does it say for carrier?
Carrier: AT&T (310410)
caseyatbt said:
I just checked my Shield on T-Mobile. In the same area on LTE Discovery that yours says W-CDMA mine says the same thing (under Neighbor Cells). When you scroll to the bottom, what does it say for carrier?
Click to expand...
Click to collapse
Here are screen shots of my sim status (personal details redacted) and the LTE discovery window:
I am thinking that it is possible that W-CDMA doesn't mean what we think it means. It shows you connected to AT&T so you are not on someone elses network.
caseyatbt said:
I am thinking that it is possible that W-CDMA doesn't mean what we think it means. It shows you connected to AT&T so you are not on someone elses network.
Click to expand...
Click to collapse
I talked to ATT. It's sort of their backup network, not available everywhere. My other devices definitely show LTE. Will post a screen so from my phone a bit later which shows that.
Sent from my LG-D851 using Tapatalk
caseyatbt said:
I am thinking that it is possible that W-CDMA doesn't mean what we think it means. It shows you connected to AT&T so you are not on someone elses network.
Click to expand...
Click to collapse
Here are some pictures taken from my phone, which is working properly. In settings, you can see the LTE network type and in the LTE Discovery app screen capture, all the LTE towers.
ATT maintains a "vestigial" WCDMA to allow some level of connectivity by devices that don't have GSM/LTE, but it's not everywhere and it's pretty slow.
The Shield used to show LTE in the Settings Cellular network type, as well as giving the LTE icon, when appropriate. Now it's just HSPA. Sigh.
Frankenscript said:
Here are some pictures taken from my phone, which is working properly. In settings, you can see the LTE network type and in the LTE Discovery app screen capture, all the LTE towers.
ATT maintains a "vestigial" WCDMA to allow some level of connectivity by devices that don't have GSM/LTE, but it's not everywhere and it's pretty slow.
The Shield used to show LTE in the Settings Cellular network type, as well as giving the LTE icon, when appropriate. Now it's just HSPA. Sigh.
Click to expand...
Click to collapse
My T-Mobile phone shows similar to your phone with LTE. T-Mobile must have a similar vestigial WCDMA that is showing up on my tablet. I still haven't found anyone that was able to get T-Mobile LTE working after it was only giving them 3G and HSPA. I have heard it either worked or it didn't.

Categories

Resources