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

    • I think the push for them is adding US Mobile as a MVNO with a priority data plan.  Ultimately, making people more aware of priority would allow them (and other carriers) to differentiate themselves from MVNOs like Consumer Cellular that advertise the same coverage. n77 has dramatically reduced the need for priority service at Verizon where the mere functioning of your phone was in jeopardy a couple of years ago if you had a low priority plan like Red Pocket. Only have heard of problems with T-Mobile in parts of Los Angeles. AT&T fell in between. All had issues at large concerts and festivals, or sporting events if your carrier has no on-site rights. Edit: Dishes native 5g network has different issues: not enough sites, limited bandwidth. Higher priority would help a few. Truth is they can push phones to AT&T or T-Mobile.
    • Tracfone AT&T sims went from QCI 8 to 9 as well a couple years ago. I'm pretty neutral towards AT&T's turbo feature here, the only bad taste left was for those who had unadvertised QCI 7 a couple months ago moved down to 8. In my eyes it would have been a lot better for AT&T to include turbo in those Premium/Elite plans for free to keep them at QCI 7, while also introducing this turbo add on option for any other plans or devices. As it stands now only a handful of plans can add it, and only if you're using a device on a random list of devices AT&T considers to be 5G smartphones.
    • My Red Pocket AT&T GSMA account was dropped to QCI 9 about a year ago.  Most recently 8 for the last few years prior.  Voice remains at 5.
    • https://arstechnica.com/tech-policy/2024/05/att-announces-7-monthly-add-on-fee-for-turbo-5g-speeds/ Hopefully we don't ever see T-Mobile do something like this. Based on how I was treated with my Credit Limit, it's definitely not the same company it was before the merger, and it's entirely possible they'd try it.
  • Recently Browsing

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