Bluetooth reporting - Sprint LG G2

Heeeeeeeey Sprint G2 folk. You guys finally got Kit Kat! *High-five*
Question: Does your device report bluetooth being used in battery usage? The TMo and AT&T (AT&T here) shows it. I'm just wondering if they ironed out the false reporting percentage on your ota

Yeah mine reports bluetooth use 3%

Related

Radio problems? Try this

I know there is a lot of talk about the radio issues the Nexus has been experiencing. My experience is a lot like many others. I would go do use my phone (data or text) which showed I had two or three bars of service. As soon as I tried to use maps or send a text I would loose all service and have to wait about two minutes before everything connected again and only then would I be able to data or voice. I had people telling me that they would try to call and get a fast busy signal.
For some reason my Nexus was dropping its signal entirely but I would still show bars, only after trying to use a signal would the phone realize that it was disconnected and reconnect to the network. Very very very frustrating.
For ****s and giggles I disabled LTE and switched to CDMA only. For two straight days I didn't have a single problem (except no 4g of course). Soon as I turn LTE back on I start dropping signal again. I think the phone has a problem with either keeping LTE active while sleeping or it can't gracefully do handoffs with LTE and CDMA.
On the other hand, If I run pandora and have LTE active I won't loose connection. I've tried this in a two hour car ride all around So Cal which supports the phone sleeping theory.
Anyway, if you're having the same issues try running CDMA only for a couple days and see if that helps.
I'm in. Switching now
I can't say anything to confirm or reject your findings because I have a GSM Galaxy Nexus. Is there no way to switch to CDMA when the screen is off/sleep mode and when the screen is active switch LTE on. That way background data and voice still work albeit at a slower connection but you never lose connectivity.
Just a theory, I assume that LTE switching off would be to save on battery life. I personally use Tasker to switch data off when screen is off and when it's on I set it to turn the data on too. I have seen a massive increase on battery when phone is idle and my standby is just short of around 1 week (tested when I had forgotten my charger and USB cable and deliberately didn't turn screen on to conserve battery life, had 8-9 phone calls during that period no issues)
Sent from my Galaxy Nexus using xda premium
I switched LTE off purely to stop my data from dropping.
First of all, thank you OP for posting this info
And this is exactly what VZW customer service people want us to do as one of the "solutions" to LTE drop. And I've been using this phone with 4G off due to the drop this entire time, but this is more like a remedy..
On the advertisements for Verizon GNex : "The fastest, most reliable network and the latest 4G LTE Galaxy Nexus Device comes to life!"
On the phone with VZW customer service after you purchase this phone eager to use 4G : The representative tells you... "Why don't you turn the LTE off, and just use it as CDMA?"
And we are thinking 1) where is the supposed update that was to come since 3 months ago?
2) We feel like we bought a Ferrari and the maker is telling us we shouldn't drive faster than 80mph.......If we go pass that speed, our engine is going to be shut off.
LOL...sad..
This works. My signal has been pretty stable since turning off LTE ... Battery life has increased as well ...
Now I'll try rooting my phone and installing a 4.0.4 radio and see how it goes...
This issue sounds like it may be addressed in the update rumored for next month. (Problems with data when the device sleeps.) Here's a quote from Droid Life.
Our friend, the Mobile Panda aka @black_man_x tossed out a quick, but important Tweet this afternoon that has to do with your Galaxy Nexus. As someone that has a well known insider track record when it comes to Verizon and LTE devices, we usually listen when he has something to spit out. Android “4.0.5″ and “April” is what he dropped today. According to Sir Panda, 4.0.5 is in testing and fixes “audio reboot issue as well as data falling asleep.” That should make you smile, right? April is a bit late seeing as the device was released in December, but what can you do?
sdmf91 said:
This issue sounds like it may be addressed in the update rumored for next month. (Problems with data when the device sleeps.) Here's a quote from Droid Life.
Our friend, the Mobile Panda aka @black_man_x tossed out a quick, but important Tweet this afternoon that has to do with your Galaxy Nexus. As someone that has a well known insider track record when it comes to Verizon and LTE devices, we usually listen when he has something to spit out. Android “4.0.5″ and “April” is what he dropped today. According to Sir Panda, 4.0.5 is in testing and fixes “audio reboot issue as well as data falling asleep.” That should make you smile, right? April is a bit late seeing as the device was released in December, but what can you do?
Click to expand...
Click to collapse
I remember going through the same thing when I got the Thunderbolt. There were all kinds of issues but eventually they all got worked out
bazzawhite said:
I can't say anything to confirm or reject your findings because I have a GSM Galaxy Nexus. Is there no way to switch to CDMA when the screen is off/sleep mode and when the screen is active switch LTE on. That way background data and voice still work albeit at a slower connection but you never lose connectivity.
Just a theory, I assume that LTE switching off would be to save on battery life. I personally use Tasker to switch data off when screen is off and when it's on I set it to turn the data on too. I have seen a massive increase on battery when phone is idle and my standby is just short of around 1 week (tested when I had forgotten my charger and USB cable and deliberately didn't turn screen on to conserve battery life, had 8-9 phone calls during that period no issues)
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This particular issue isn't about saving battery life. It's about the cellular connection dropping out completely. Many users (myself included) have this happen several times a day. I can be in an area with a strong, full signal, and then all of a sudden my phone is searching for service. This happens far too often, and it happens both when I'm using the phone and when it's idle. Having LTE switch off when the phone is asleep isn't particularly useful for this issue because the connection drops when I'm trying to use the phone. I don't notice the connection dropping when the phone is idle unless I miss a call and get a voicemail later.
For me, I still randomly lose connectivity in CDMA only mode, although not nearly as frequently as when I have LTE on.
Prevent maps app from running all the time if you want to save battery. I use Gemini app manager from the market. I block maps from starting at boot and have seen significant battery life increases. App functions normally when ran too.

[Q] Roaming more often lately and battery draining

Ive been using this phone for a while now - with no issues. Recently had to get a replacement due to a lost phone and installed blazer 4.1. The first couple weeks i had no problems that caught my attention, but in the last week or two, it has been roaming almost all the time. The battery seems to go down much quicker too.
any suggestions on what I should check?
my personal reccomendation would be to call cc and see if their currently in your city working on your towers (3g capacity upgrades and lte installation) bc if thats the case you will suffer from poor service for the next few months until their finished
also what modem are you currently running>
thanks - i'll definitely do that. as for modem, i'm thinking that is the EL.29 number? (sorry i cant quite recall how to tell).. but it was a stock phone where i flashed to blazer rom without any other changes, so it should be the same modem that came with the install.

[CDMA/LTE] Who DOESN'T have signal drop issues?

Ok, so I am on my 4th replacement Galaxy Nexus (CDMA/LTE) All of them are dropping 4G signal every 3 to 5 minutes, but sometimes will go as long as 30 minutes or an hour. Either way, there's WAY too many signal drops. And, for clarification, I don't mean low bars...I mean going from 3 or 4 bars to no connection with the "x".
My original one was I515.09. All of the replacements have been I515.10's. I know the .09 / .10 are the hardware versions (.09 make in Korea and .10 made in China I believe). My wife's does not have the problem (.09 version), my brother in law does not have the problem (.09 version) and the one in my local Verizon store does not have the problem (oddly, a .10 version).
Regardless of what Verizon and Samsung say, this is NOT a coverage issue; it is either a hardware issue or something in the software causing interference with the 4G radios (it doesn't affect 3G signals, only 4G).
The problem seems so prevalent that I decided to do a poll...who among you DO NOT suffer from the signal drop issue? And, if you don't mind, provide a little information if you don't care. I am doing this in hopes of figuring out if this affects all .10 versions (obviously it does not). And if you have a .10 and do not have the issue, I am trying to figure out what combination of roms, kernels, and radios are working for you. I know that none of the variables should affect the signal drop issue, but for some reason some kernels and radio combinations seem to do better than others..
Do you have the issue?
What is your baseband version (.09 / .10)
What rom are you using?
What kernel are you using?
What radios are you using?
Fellow GNex users,
I have been having this same exact problem, too. My original phone was a I515.09, purchased back in early May 2012. Unfortunately, that phone had separate issues with it and I had to send for a replacement. Here I am, two replacements later, and I am experiencing the same issues the OP has. However, with the second phone, I decided to try and isolate the problem, and in an effort to save people some time, I thought I would post what steps I have already taken to try and resolve this issue. The bottom line: I believe it is in fact a hardware-related issue with the newer phones released and/or some firmware issue that is impossible for a user to manipulate.
:::None of these solutions resolved the problem:::
Replaced both the battery and the sim card
Rooted the phone, replacing the bootloader with CWM and installing AOPK milestone-5 on 4.0.4 (full wipe)
Manually installed the latest 4.0.4 Radios (FC04/05)
Installed older Radios (EK04/06)
As for some .10 versions working, it seems there are a few .10's floating out there that have existed at the launch of the product. It must be an older version .10 that does not suffer the same hardware issues that all the new ones have. I have even heard, first-hand, of people purchasing brand new GNex's and experiencing this problem, too. Therefore, I think it extends beyond just a "replacement product" problem.
:::My Solution:::
After talking with a "level two" technician at Verizon who handles dispatching replacement phones, I have requested a notation on my account to send out a baseband version I515.09 (the technician had all .09's at his disposal at the facility, so he was certain there are some in stock, as well.)
I will update this thread after I receive my new replacement, most likely this Friday.
:::UPDATE:::
Just got off the phone with Verizon/Samsung and received some troubling news. According to Verizon, it is basically impossible to know what version they are sending you. As for Samsung, the representative said she is unaware of any problems of this magnitude with the Galaxy Nexus and does not see any updates to correct it in the foreseeable future.
Looks like we are up a creek on this one. It's a sad day, but getting a different phone as a replacement may be the only option we have.
:::FINAL UPDATE:::
Just got off the phone with Samsung. I wanted to call them directly to make sure this issue was reported. After some digging, the representative saw a ticket for a known issue with some versions of the Nexus where an error in the firmware keeps causing the modem to reset, thereby creating the constant dropped signals with 4g. There was no date scheduled for fixing this problem, but he mentioned the ticket saying it would ultimately be resolved by a firmware update over the network.
In the meantime, I did discover that the phone should function properly if you run it in CDMA mode only. I recommend moving to 3g for the time being until a patch can be pushed out to us.
I did but only at my house, where coverage blows. I got a free Airave, problem solved.
Never happens when I'm out and about or at work.
Sent from my Galaxy Nexus
Sprint, the Maybe Later Network
No signal issues here. CDMA/LTE.
Sent from my AOSP Android 4.1.1 Galaxy Nexus
I was having this problem a lot when I first got the device and was running the stock 4.0.4 and I'm on the .10 baseband. I tried a couple of the cm10 ROMs and the problem seemed to persist, but then I tried paranoid android and haven't really had an issue since. I found it to be rather odd, but so far so good since this flash.. keeping my fingers crossed that I didn't jinx something.
Sent from my Galaxy Nexus using xda premium
flashed paranoid android and I am still getting drops in 4g. lemon!
I wish I could vote twice. No I do not. .09 and .10 devices here.
Have not had any drop data yet, I just got my nexus about 4 weeks ago. I'm using the jelly belly rom.
Sent from my Galaxy Nexus using xda app-developers app
adrynalyne said:
I wish I could vote twice. No I do not. .09 and .10 devices here.
Click to expand...
Click to collapse
Where do you live? I'm coming over to steal one of them. I'll get away with it too because I'm going to bribe Mrs. Adrynalyne! :beer:
Sent from my Xoom using xda premium
I am on my second Verizon Galaxy Nexus. So far, 4G has been miserably bad here in Raleigh, NC - including right inside the Crossroads Mall Verizon company store where they swapped me a new one out for my current new one. They did that because I was going on a trip that afternoon and customer service could not get me a replacement phone in time. They checked the old phone's reception in the store and 4G came up, stayed connected for a minute or two, then dropped to an x without even going back to 3G. The salesguy told me he had never seen anything like that before and got me the replacement from stock. He said that 4G reception was perfect at this store, and smiled...
The new phone seemed better at first, but I had to go before I could really check it out. Then I was in a non-4G area during most of the next week and while only 3G was available the data connectivity seemed alright. Things did not look so good though when I got home to Raleigh after that. 4G never stays connected for more than a few minutes here now on this phone either. Locking it down to 3g seems to make it so at least 3g connectivity stays up reliable, but if it is set to Network Mode LTE/CDMA then it will stay briefly in 4G, maybe, and then drop to x and then maybe come back after a while to 3g, which is iffy. Meanwhile my wife's droid3 has a solid 3G connection and my tenant's S3 is solid 4G.
I tried the *#*#4636#*#* menu this afternoon and set the preferred network type to GSM auto (PRL) which is odd because my understanding it that this phone doesn't even have GSM hardware. That sets it into a 4G that seems to maybe stay connected better, maybe because it avoids switching to 3G as easily ?
I guess I will have to get another replacement and hope the new one has a .09 radio instead of the .10 radio like both have had before ?
I am wondering if this is a network type hand-off problem between 3G and 4G or something like that.
Glenn
I am on .10 and havent had an issue. I got my gnex last month with 4.0.4 installed and it was fine. I then flashed the AOSP JB rom from muzzy and its been working great too. Stock kernels and radios.
In NYC. Rev. 9. No signal dropping issues at all. Completely stock, locked boot loader.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for all the replies. Looks like there are some good .10 versions out there after all.
Quick update on mine...I'm on replacement #6...or is it #7?...I've lost count. But, I know I still have the issue.
A couple of weird things though...this most recent phone was made in Korea, not China. When I opened it up and saw that I just KNEW I had a .09 version. But, alas, when I turned it on it is indeed .10. I thought all ones made in Korea were .09 and ones made in China were .10, but that doesn't appear to be the case.
And, another weird thing, this new replacement has IMM76Q on it, not 76K. I find that interesting because 76Q hasn't been pushed OTA yet that I am aware of. I actually called Verizon again yesterday and had to go through the same old song and dance with the tech guy and one of the questions he asked me was the build number. When I told him 76Q he informed me that 76Q was not the most recent update and it should be on 76K ( ). I just LOVE knowing more about their devices than they do. I had to inform him that no, 76K is the most recent OTA, but 76Q is actually more recent, just not pushed out yet. He went on to accuse me of rooting my phone (which I haven't yet since it's going back...again) and installing 76Q on it.
I freaking HATE getting "specialists" who do not know what they are talking about. I know more about this phone than they do it seems.
FML
Glad someone brought this back up. I'm about at my wit's end, and am seriously considering their offer to send me a RAZR. Sure I can't hack it, but at least I will have a usable phone.
Just to reduce the repetetiveness I will say I ran whatever kernel came with the ROM I was using at the time. Also, I've not experiemented with the so-called "hybrid" radio sets. All 4 phones always experienced fairly weak signal when compared to my previous phone, an OG Droid. But then again my Droid could send a text message through 3 inches of steel when I was on a ship. My work is a fringe area, so I'm going to focus on the issues I have at home, where I usually get 3-4 bars. Located in Virginia, near Virginia Beach and Norfolk.
Original Phone (bought on release day):
Reception: No major reception issues.
HW Ver: i515.09
ROM: Stock unrooted, stock rooted, GummyROM, CM9 nightlies
Radios: EK02/EK05, EK04/EK06, FA02/FA02
Replacement Phone #1:
Reception: Can hold signal for an hour or so on average. 20-40 drops per day.
HW Ver: i515.09
ROM: Stock rooted, CM9 nightlies
Radios: EK02/EK05, EK04/EK06, FA02/FA02, FC04/FC05
Replacement Phone #2:
Reception: Could not hold signal for more than 5-10 minutes. ~150 drops per day.
HW Ver: i515.10
ROM: Stock rooted, CM9 nightlies
Radios: FC04/FC05
Had the SIM card replaced at this point, while I had replacement phone #2, but it didn't make any difference.
Replacement Phone #3:
Reception: Could not hold signal for more than 5 minutes. 200+ drops per day.
HW Ver: i515.10
ROM: Stock unrooted
Radios: FC04/FC05
Most recent phone (received it yesterday) also came with IMM76Q. Couldn't tell you what the other's came with. I did try turning off 4G about an hour ago, and haven't had a single signal drop since then. <sigh> I totally don't consider this an acceptable solution. Time to call VZW again!
I do not have signal drops.
Except some random 3G drops in the past day or so but I do think it's a result from a dirty flash catching up with me.
Other than that, no issues.
i515.09
I don't have signal drop issues.
Sent from my Galaxy Nexus using XDA Premium via Verizon Wireless
I'm on my second Gnex, with no reception issues. My first kept dropping signal at least twice a day. I exchanged it after about a week of having it.
Sent from my Galaxy Nexus using xda premium
My first one had that issue brand new out of the box. Got it replaced with my current one that works flawlessly. Its a baseband .10
Sent from my Galaxy Nexus using Tapatalk 2
Worst phone yet
I was having similar LTE drops with my Bionic (after I allowed the .905 OTA update). I ended up getting another Bionic and then another SIM. Didn't fix anything. It was obviously the latest build and god knows when the next Motorola update would be, so I got a GNex replacement. That was a mistake. I'm having worse issues with this phone than the Bionic. Can't hold a 4G signal to save my life. Heaven forbid I need to make a phone call, because that's unreliable also. VZW tier 2 tech said it's a known issue and an update is needed to fix it, but the ETA is unknown. She said some of them work and others don't, based on her own personal experience (her sister has a GNex). So I'm getting another Nexus to replace my replacement. We'll see if the next one is any better.
Current Specs:
i515.10 v.FC04/FC05
Stock Kernel 3.0.8-gda6252b
build IMM76Q​
On .09 / LTE and been solid all around for 7 mo's. No matter the rom, version etc.

Brand New T-Mobile LG G3 - Just trying to update to build R

Just bought the LG G3 after having an OnePlus One for about 3 months. It's a good phone, but doesn't seem to have quite as good of reception as my Unlocked, but AT&T branded S 4 did. So I decided upgrading to a T-Mobile LG G3 might not only give me better reception, but wifi calling which I was anxious to have the option to use.
The LG G3 is pretty great. Doesn't seem to have the OnePlus One's battery life, but it could be that I've only FULLY charged it two or three times yet, and been using it a LOT during the day while setting it up. Haven't totally drained the battery in a single day yet, but I don't seem to have quite the battery life the OnePlus One had.
Anyway, after having some trouble loading web sites, and sending text messages, I thought maybe I should update the phone software. Not looking for Lollipop, I just wanted the latest version of the T-Mobile software for the Soft White D851. The LG site says D85110r is the latest and greatest, and I only have D85110m. So I tried the OTA updates, and it says I'm up to date. I then called T-Mobile, who had me clear my phone cache, and if OTA didn't pull R, they told me to call LG. Just spent 20 minutes on the phone with LG, 15 minutes of it on hold. They didn't know how to make the update available for my phone, and when their own LG update tool told me I had the latest version (while using M), and not R like their website suggested, they promised to look into it, call T-Mobile for more information, and get back to me in 3 hours.
I'm not trying to be a jerk, but with the data issues I'm having, and those seemingly having been addressed with a patch, obviously I'd like the new $500 phone to work at LEAST as well as the $350 phone that didn't have any trouble, just didn't have Wifi Calling, since T-Mobile doesn't sell a OnePlus One as "their" version of the device with T-Mobile Wifi Calling software included.
If anyone can comment on if R has helped them, and if you weren't getting it at first, what you did to get the update... it would be greatly appreciated. I heard a rumor in another thread that some stores were getting a lollipop update earlier today. That would be cool too, but I'm just trying to fix Kit Kat, before worrying about a whole new OS.
D85110R seem to be still in the rollout process. I just got it this week. I'm not aware of any major issues that it fixes, but I haven't had any significant issues.
New features
T-Mobile Free Inflight Texting support
Improvements
Bluetooth connectivity improvements
Wi-Fi connectivity improvements
UI improvements for T-Mobile Free Inflight Texting suport
I am still waiting on R also.
Thanks guys. It seems odd that more than a month after release, you can't just download this update onto any LG G3 that needs it. And my purchasing the phone for wifi calling would imply I'd like wifi to work well on the phone.
That said, the battery has been showing much longer life today, and I do like the phone. Just don't wanna wait past my 14 days, update, and have a problem ya know?
Cheers.
The M software build has WiFi calling too. Did you check your settings? The R update fixed some minor connection problems and enabled in-flight texting. Check the tmo website https://support.t-mobile.com/docs/DOC-11935
I also have the OnePlus One, but had to get the G3 when the screen shattered. I also had 10m firmware but could not auto update to 10r. I finally gave in and downloaded the flashable zip and installed through recovery. Frankly, I could not see and added improvements on daily usage.
Sent from my LG-D851 using Tapatalk
So I got this today when I checked my update center, I am still on m, not sure if this is the r update. Idk if it would be LP seeing as its only 231 mb. Anyone know how big r is? I would install but I'm not on WiFi.
Sent from my LG-D851 using XDA Free mobile app
johnny tsunami said:
So I got this today when I checked my update center, I am still on m, not sure if this is the r update. Idk if it would be LP seeing as its only 231 mb. Anyone know how big r is? I would install but I'm not on WiFi.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
The r that I got was 200 or so meg. I would say that is it. It's strange I live in a small town and I got the update months ago.
I had the updating issue too.. and the LG tool was saying my firmware was up to date on m.
The way I fixed it was going to the LG tool , going to Options then Upgrade Recovery, now I have D85110R yay!
I updated (and rooted) through TWRP.
Don't update to R if you want to disable 2G.
mingkee said:
I updated (and rooted) through TWRP.
Don't update to R if you want to disable 2G.
Click to expand...
Click to collapse
Disable 2G? How does that work exactly?? It blocks the downgrade to 2g and uses 4g only even if you run out of data?
I just got the update just now at 5am after waiting over a month too. It was definitely a very slow roll out. Even a week after it was released it still would not update even using the LG software tool. Anyways I am excited for it since I was having some very brief data connections. Also excited for in flight texting too!
gunner05 said:
Disable 2G? How does that work exactly?? It blocks the downgrade to 2g and uses 4g only even if you run out of data?
Click to expand...
Click to collapse
*#*#4636*#*#
phone information, which can access network mode to LTE/WCDMA, is disabled.
GPRS = 2G
WCDMA/HSPA = 3G/4G
LTE = 4GLTE
I just tryed that code got this
Why would you want to disable 2G. Disabling it would cause you to not have any service if you were in an area without 3G/4G or 4GLTE.
truckerdewd said:
Why would you want to disable 2G. Disabling it would cause you to not have any service if you were in an area without 3G/4G or 4GLTE.
Click to expand...
Click to collapse
HSPA/LTE is everywhere I am, but the phone simply jump to stupid 2G and the data doesn't work at all.
mingkee said:
HSPA/LTE is everywhere I am, but the phone simply jump to stupid 2G and the data doesn't work at all.
Click to expand...
Click to collapse
I can understand that but if you were out in the country somewhere that only had 2G and you had disabled it on your phone then you would have no service
10R doesn't seem to change anything to me, but its best to be on latest software!

Questions about 5.0 on LG G3.

I recently bought a used LG G3, it should be arriving later today. I had a few questions regarding 5.0 Lollipop.
Looking through the threads here, it seems to be that some folks still haven't gotten the OTA in the US. Is this still the case, or is it widely released now?
Also, are there any issues with the 5.0 update on the T-mobile G3? Any reason to stick with KK over it?
Thanks!
The original release gave some of us issues with wifi calling being stuck on enabling and blue tooth being wonky so they halted the roll out but now they have approved an updated version and is starting to roll out or should start rolling out any time. The only issue my wife and I have with the original release was the wifi calling not enabling, we have no other problems. I have the white one and she has the black one so the issue affected both.
Not all Xposed modules work for lollipop just yet but lollipop seems pretty stable to me. Wifi calling is sketchy but I have perfect signal so it doesn't bother me. Battery life is better on lollipop for sure. Backup kitkat and try Lollipop and if you don't like it you can always go back
Thanks for the quick replies!
The phone arrived yesterday and I've been busy setting it up. I checked, and it came with 5.0.1 installed. Is there a way to know if that's the original release, or the second, fixed version of Lollipop?
Thanks again!
rubejb said:
Thanks for the quick replies!
The phone arrived yesterday and I've been busy setting it up. I checked, and it came with 5.0.1 installed. Is there a way to know if that's the original release, or the second, fixed version of Lollipop?
Thanks again!
Click to expand...
Click to collapse
The first version of lollipop was 20B, while the newest version is 20E. Go into settings, general, about phone, and then click on software info and look at the software version and it will tell you if it's 20B or 20E. It's most likely 20B since the 20E just started rolling out yesterday afternoon.
Ah, okay. Thanks!
Okay, time for some more dumb questions (sorry!) First, I'll start by saying I'm apparently still on the 20B version, and checking for updates says I'm still up to date. So if this would cause my network issues, I guess I"ll just wait it out...
I got my account activated last night and all seemed well. But now I'm in a location without wifi and I see I have no data connection. When I rebooted, it came up and said I was connected to AT&T, not T-mobile. Since I'm on the $30 plan with TM, I thought I wasn't allowed roaming, or perhaps it's no roaming for data? Anyway, it was a bit odd to see AT&T to come up...
So, I'm trying to make it only connect to Tmobile. If I go into "Tethering and Networks" and "Mobile networks" in the settings, I can change the "Network operators". After doing a search I see the following:
T-Mobile
RAT: LTE
T-Mobile
RAT:WCDMA
Followed by 3 AT&T options, the same as the TM ones and a GSM option.
Should I select one of the T-Mobile ones, or set it to auto?
I checked the T-mobile coverage map site and it shows my area has having 4G coverage, so I would think I'd get a better signal than I am. Although it's hard to tell if it's 4G or LTE, as the two shades of pink are so close together.
Are there other network related settings I should be checking or changing to get it to work better?
edit:
Okay, so I'm doing some semi-answering of my own questions here..
It looks like from what I'm reading that on the $30 prepaid plan, voice roaming is certainly allowed, but not data. So connecting to AT&T isn't a problem, I just can't use data on it.
And the reason I'm getting such poor reception on T-mobile is that their signal doesn't penetrate buildings very well, by nature of the band they use. I sort of wish I had learned this before switching from Virgin Mobile, but I'm still loving my new phone so much, I'm not too upset.
I was also able to use the LG update software on my computer to get to the 20E version, and the reception is still terrible, so that wasn't the problem.
Guess I'll just to do some connection tests outside of a building to see if I actually get a 4G connection, as per their coverage map, or if I'll have to call them up and find out whats going on.

Categories

Resources