Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

so it can't scan for LTE while connected to 3G?  That's interesting

when you set it to 3g/1x only mode, it wont scan for LTE
Link to comment
Share on other sites

but it actually has to disconnect from 3G to even search for LTE?

I believe so yes. Any time I had my nexus on global, or LTE(recommended) mode, It would cut off all connections so it could scan The LTE bands.

Link to comment
Share on other sites

I've never seen that happen.

 

Sent from my Nexus 5

It does so in areas where there is no LTE deployed, or in areas where LTE can not reach.

Link to comment
Share on other sites

If you guys are really that hard up for your update why don't you get the msl for your device and enable the bands yourself? Ten people a day complaining about the update is ruining this thread and will not get Google to push this any faster.

  • Like 1
Link to comment
Share on other sites

If you guys are really that hard up for your update why don't you get the msl for your device and enable the bands yourself? Ten people a day complaining about the update is ruining this thread and will not get Google to push this any faster.

band priority does not always work. It takes prl updates, radio cycling, etc. The spark update will make all this seamless and automatic.

 

Sent from my Nexus 5

 

 

  • Like 2
Link to comment
Share on other sites

band priority does not always work. It takes prl updates, radio cycling, etc. The spark update will make all this seamless and automatic.

 

Sent from my Nexus 5

Then I guess you wait.

Again. Endless nagging and bitching isn't doing anything to help the issue.

Link to comment
Share on other sites

Then I guess you wait.

Again. Endless nagging and bitching isn't doing anything to help the issue.

I don't think I've been nagging? Watch who you call out when you quote.

 

Sent from my Nexus 5

 

 

Link to comment
Share on other sites

Then I guess you wait.

Again. Endless nagging and bitching isn't doing anything to help the issue.

 

I only see one instance of nagging and bitching going on right now.  The lack of tri-band support is a persistent source of early-adopters anxiety for owners of this phone.  It's perfectly okay to express our desire to get this update promptly- after five months of waiting it has hardly gotten out of control and the conversation/statements are completely mature.  No need to bring others down.

  • Like 5
Link to comment
Share on other sites

If you guys are really that hard up for your update why don't you get the msl for your device and enable the bands yourself? Ten people a day complaining about the update is ruining this thread and will not get Google to push this any faster.

 

 

Then I guess you wait.

Again. Endless nagging and bitching isn't doing anything to help the issue.

 

People express their frustration, but hardly endless nagging. The vast majority of the posts in this thread are productive. I don't see any problems here.

 

And for you information, enabling the bands is not the end all be all. I have yet to get my N5 to connect to Band 41 in KC, an official Spark market. Even with PRL and profile updates and whatnot. 

  • Like 1
Link to comment
Share on other sites

 

And for you information, enabling the bands is not the end all be all. I have yet to get my N5 to connect to Band 41 in KC, an official Spark market. Even with PRL and profile updates and whatnot.

Exactly. So even with the update its probably not going to be the saving grace everyone is hoping for anyways. You guys are pinning a lot on this update.

Link to comment
Share on other sites

Exactly. So even with the update its probably not going to be the saving grace everyone is hoping for anyways. You guys are pinning a lot on this update.

 

If the G2 is any indication, it will at least make B41 connections reliable, and work they way they are supposed to. So yes, it is highly anticipated. 

Link to comment
Share on other sites

If you guys are really that hard up for your update why don't you get the msl for your device and enable the bands yourself? Ten people a day complaining about the update is ruining this thread and will not get Google to push this any faster.

 

 

Then I guess you wait.

Again. Endless nagging and bitching isn't doing anything to help the issue.

 

because being vocal about anticipating the spark update is ruining this thread much like those being vocal about anticipating B26 is also ruining half the other threads on this site as well.

 

:wall:

 

  • Like 2
Link to comment
Share on other sites

I agree to some point about the constant, where is the update, and the complaining about the lack of update. Honestly some of y'all have waited longer going through the NV 1.0 Process. The update will come, I just hate seeing all of the complaining about it, when you know it will be out, and when you can have steps to take, maybe not the best steps, but steps to take to circumvent the spark issues. Yes they do not work all of the time, but there is nothing else you can do. Complaining  on here will accomplish nothing but bring a negative attitude. Be positive, and keep up with being productive, and by the time you know it, the update will be out.

  • Like 2
Link to comment
Share on other sites

I would like it sooner rather than later. I know its not the same but coming from a Note 2 that never got a 800 MHz update gets me wondering if should have waited for the patch before I ordered.

 

Sent from Nexus 5

 

 

  • Like 1
Link to comment
Share on other sites

I would like it sooner rather than later. I know its not the same but coming from a Note 2 that never got a 800 MHz update gets me wondering if should have waited for the patch before I ordered.

 

Sent from Nexus 5

I have the same fear...

 

Sent from my Nexus 5

 

 

Link to comment
Share on other sites

And for you information, enabling the bands is not the end all be all. I have yet to get my N5 to connect to Band 41 in KC, an official Spark market. Even with PRL and profile updates and whatnot. 

 

 

Have you tried the .15 or .17 radios?

 

I've been using .15 for a month or 2 now with no issues (other than the known lack of CSFB) and it automatically pulls b41 where it is available and has a better signal than b25.

Link to comment
Share on other sites

Have you tried the .15 or .17 radios?

 

I've been using .15 for a month or 2 now with no issues (other than the known lack of CSFB) and it automatically pulls b41 where it is available and has a better signal than b25.

 

I know you weren't referring to me, but that's a complete non starter for me, in an area where there are a number of CSFB issues moving from tower to tower.  As much as I'd love me some B41, I can't give up the ability to get calls (and not know at any given time whether I can get them or not).

Link to comment
Share on other sites

well, .17 as I recall will allow both csfb and b41.

 

of course if all of your b41 is in areas with csfb issues, then you may well be sol since you will be stuck in 3g in those areas anyway.

Link to comment
Share on other sites

In regards to the tendency for the N5 to drop onto 3g while driving I noticed the same problem in the Fort Wayne, IN area despite upgrades basically being complete. I noticed the issue with the .17 and .23 radios but when I flashed the .15 radio it held onto LTE better and would connect to it more often and quicker. I did not notice symptoms endemic of an eCSFB issue in the area when I used the .15 radio.

Link to comment
Share on other sites

So, I was just on the phone with Sprint tech support about the Spark update.  She put me on hold and came back stating that the update was available beginning March 10th? She said the software build number is KOT49Y.  She said it should be push to our phones, but if it didn't to go in and manually update.

 

Thoughts? 

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...