Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

Finally the backspace fix ! Haha
Link to comment
Share on other sites

So I got switched out to a note 3 today and noticed I have 1x800 a lot more often than I did on my N5.

Does anyone have any ideas as to why my nexus wouldn't be picking up on it as frequently?

 

Because it doesn't "need" it. If there is a reason, it's because the Nexus 5 is such a strong RF performer, and happens to find more usable 1900 MHz signals than the Note 3 has so far.

 

I feel like a lot of people are starting to believe that being connected to 800 is "better" than being connected to 1900, and I do not feel that is correct. The general benefit of 800 is better signal penetration. If you are already connected to a usable 1900 signal, there is no need to switch to 800. It's not any faster. You're not missing anything.

 

-Mike

  • Like 3
Link to comment
Share on other sites

Because it doesn't "need" it. If there is a reason, it's because the Nexus 5 is such a strong RF performer, and happens to find more usable 1900 MHz signals than the Note 3 has so far.

 

I feel like a lot of people are starting to believe that being connected to 800 is "better" than being connected to 1900 , and I do not feel that is correct. The general benefit of 800 is better signal penetration. If you are already connected to a usable 1900 signal, there is no need to switch to 800. It's not any faster. You're not missing anything.

 

-Mike

Which makes sense but I noticed a lot more static and other network noise being on rtt than on 800. Wouldn't sprint want to prioritize 800 over rtt for a better network experience?
  • Like 1
Link to comment
Share on other sites

Which makes sense but I noticed a lot more static and other network noise being on rtt than on 800. Wouldn't sprint want to prioritize 800 over rtt for a better network experience?

 

If you're suffering from lousy call quality, that isn't specifically because you are connected on 1900 MHz. Something else is wrong. Absent all other factors, 1900 and 800 calls should sound the same. Sprint has not once indicated that 800 service is expected to be of a higher call quality.

 

-Mike

Link to comment
Share on other sites

If you're suffering from lousy call quality, that isn't specifically because you are connected on 1900 MHz. Something else is wrong. Absent all other factors, 1900 and 800 calls should sound the same. Sprint has not once indicated that 800 service is expected to be of a higher call quality.

 

-Mike

So what else could I do to help my calls? Not like it matters too much since I have the note now, but when and if I switch back what can I do?
Link to comment
Share on other sites

If you're suffering from lousy call quality, that isn't specifically because you are connected on 1900 MHz. Something else is wrong. Absent all other factors, 1900 and 800 calls should sound the same. Sprint has not once indicated that 800 service is expected to be of a higher call quality.

 

-Mike

Great points you've made. And how many times have we seen people certain that CDMA 800 had lower sound quality or static or buzzing?

 

Robert via Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

Which makes sense but I noticed a lot more static and other network noise being on rtt than on 800. Wouldn't sprint want to prioritize 800 over rtt for a better network experience?

Mike, you might have to come up with some different SignalCheck abbreviations. Otherwise, you are going to condition an entire group of newbs to believe that "1xRTT" and "1x800" are two different airlinks -- as evidenced above.

 

AJ

Link to comment
Share on other sites

Mike, you might have to come up with some different SignalCheck abbreviations. Otherwise, you are going to condition an entire group of newbs to believe that "1xRTT" and "1x800" are two different airlinks -- as evidenced above.

 

AJ

 

Yeah I noticed that immediately too, <facepalm>..

 

-Mike

Link to comment
Share on other sites

Looks like a new Android update is coming out soon..

 

KVT49L

 

http://www.androidpolice.com/2014/02/14/android-4-4-2_r2-kvt49l-shows-up-in-aosp-heres-the-changelog/

This is the update that enables Verizon compatibility on the nexus 7 2013 lte. Nothing to see here...

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

Yesterday I went to take a call, signal check was reporting I was on 1xrtt 800 but the phone status bar said roaming. Anyone else notice this? I haven't been able to duplicate it, I didn't even think Syracuse had any 800 deployed. I'll be back on that side of town later today to try again.

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

Yesterday I went to take a call, signal check was reporting I was on 1xrtt 800 but the phone status bar said roaming. Anyone else notice this? I haven't been able to duplicate it, I didn't even think Syracuse had any 800 deployed. I'll be back on that side of town later today to try again.

 

Sent from my Nexus 5 using Tapatalk

I see that all the time. I'll grab a screenshot when I can
Link to comment
Share on other sites

Yeah I noticed that immediately too, <facepalm>..

 

Yes, we have people now who unfortunately think that "RTT" somehow signifies PCS 1900 MHz. It is not the fault of SignalCheck. They just jumped to the wrong conclusion.

 

AJ

Link to comment
Share on other sites

There currently is no 'sparkle' icon for any nexus 5 phones.

 

while you can enable band 26 and 41, there is apparently still a future update that has not yet been released for full spark compatibility.

 

The LTE engineering screen will indicate what band you are currently connected.

Even more, the sparkle icon does not mean you are on the Spark network. It just means you are on LTE. At least that is how it works on my LG Flex.

 

Sent from my LG-LS995 using Tapatalk

 

 

Link to comment
Share on other sites

Which makes sense but I noticed a lot more static and other network noise being on rtt than on 800. Wouldn't sprint want to prioritize 800 over rtt for a better network experience?

Doesn't the Nexus have HD voice capability? Once you hear that, everything from every other phone is garbage!

 

Sent from my LG-LS995 using Tapatalk

 

 

Link to comment
Share on other sites

Mine almost always says roaming when making/receiving a call. But I don't think it is actually roaming as per my Sprint account page.

 

Android's telephony structure doesn't deal with the "fallback from LTE to CDMA 1X for calls" concept very well yet. If you put your N5 in LTE-only mode and check your notification pulldown, you will see it shows "Searching for Service" instead of "Sprint", even though you are on Sprint's network. A lot of the CDMA code in place now essentially assumes a 1X connection is always present. I'm sure the false roaming indicator appearing is because of something along those lines; I have also seen it.

 

-Mike

  • Like 2
Link to comment
Share on other sites

Doesn't the Nexus have HD voice capability? Once you hear that, everything from every other phone is garbage!

 

Sent from my LG-LS995 using Tapatalk

It does but it doesn't always connect that way. When I call my manager it does sound crystal clear though. Both being sprint phones obviously.
Link to comment
Share on other sites

Bought a nexus 5 for the wife, and it's driving us both nuts. When trying to place an outgoing call it would take multiple (up to 6) attempts before call would complete. (This while at home, connected to Wi-Fi and global selected for mobile network). I've been reading and understand the fallback issues, but no one mentions outgoing issues... by setting network mode to 3g only seems to help. (Obviously unsatisfactory workaround)

 

Had a devil of a time just getting it activated on the network... is it possible something it's wrong with this particular device?

 

Or do I just need to wait like everyone else and hope the update comes through and helps...

 

Sent from my SPH-L710 using Tapatalk

 

Edited by liner81
  • Like 1
Link to comment
Share on other sites

I just pulled my N5 out of my pocket and it was doing an Android update that I did not instigate. Came out of nowhere and seemed to download and run itself automatically! Kind of pisses me off.

 

171 updates total. Just finished booting up. It says Build 49H. Was that the latest before or is this something new?

 

uploadfromtaptalk1392487781534.jpg

 

Robert via Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

I just pulled my N5 out of my pocket and it was doing an Android update that I did not instigate. Came out of nowhere and seemed to download and run itself automatically! Kind of pisses me off.171 updates total. Just finished booting up. It says Build 49H. Was that the latest before or is this something new?attachicon.gifuploadfromtaptalk1392487781534.jpgRobert via Nexus 5 using Tapatalk

49h is what is currently out. 49L is supposed to be the new
Link to comment
Share on other sites

Bought a nexus 5 for the wife, and it's driving us both nuts. When trying to place an outgoing call it would take multiple (up to 6) attempts before call would complete.

 

Did the calls actually fail?  Or did you just grow impatient and redial?  Outgoing calls on e/CSFB devices connected to LTE often take 15-20 seconds to initiate because of the fallback to CDMA1X.  Conversely, incoming calls on e/CSFB devices connected to LTE can ring several seconds earlier.

 

AJ

Link to comment
Share on other sites

Did the calls actually fail? Or did you just grow impatient and redial? Outgoing calls on e/CSFB devices connected to LTE often take 15-20 seconds to initiate because of the fallback to CDMA1X. Conversely, incoming calls on e/CSFB devices connected to LTE can ring several seconds earlier.

 

AJ

On my Nexus 5, it sits on lte and cdma goes through a different non lte tower. Takes an instant to call out, although sometimes after takes a while to pick up a tower after ending a call

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...