Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

I have, but I haven't seen it since 4.4.3.

 

That's because it's "fixed" in 4.4.4, released how long ago...notice how this article, written today, talks about it like it's still 4.4.3 - at least that's how I read this:

 

 

The Android 4.4.3 update included a few tweaks to the camera code for the Nexus 5, but the next update will further optimize, and Google hopes, will finally put this bug to bed.

 

  • Like 1
Link to comment
Share on other sites

Having a problem recently (last couple of days) of going from LTE to 3G. In areas where I usually stay LTE, recently, it's been dropping to 3g and staying there until I toggle. Odd thing is, it can go back to LTE in LESS THAN 5 minutes (I hear usually it won't scan again for 5 minutes by default).

 

1) Anyone know what the problem is?

2) Where can i edit the LTE Scan Times (##3283# doesn't work and can't seem to find it in either *#*#3282#*#* or *#*#33284#*#*)

Link to comment
Share on other sites

Having a problem recently (last couple of days) of going from LTE to 3G. In areas where I usually stay LTE, recently, it's been dropping to 3g and staying there until I toggle. Odd thing is, it can go back to LTE in LESS THAN 5 minutes (I hear usually it won't scan again for 5 minutes by default).

 

1) Anyone know what the problem is?

2) Where can i edit the LTE Scan Times (##3283# doesn't work and can't seem to find it in either *#*#3282#*#* or *#*#33284#*#*)

Don't think you can edit the scan times on the nexus 5. :(

 

Sent from my Nexus 5

  • Like 1
Link to comment
Share on other sites

Don't think you can edit the scan times on the nexus 5. :(

 

Sent from my Nexus 5

Every phone does this though, correct? If it drops to 3G, any phone, any carrier will scan what in the appropriate time, correct? As in, it'll never just go back to LTE before 5minutes

Link to comment
Share on other sites

Every phone does this though, correct? If it drops to 3G, any phone, any carrier will scan what in the appropriate time, correct? As in, it'll never just go back to LTE before 5minutes

I'm not speaking for Google or anything, but my guess is they have an adaptive timer that activates an LTE scan that could probably range from a few milliseconds to 5 minutes or longer. As an example, if you just got out of LTE range and it dropped to 3G, it might scan for LTE in 10 seconds or so. After failing a couple times, it'll drop the frequency to every 1 minute or so, and after that it may go up to 5 or 10 minutes to save battery life. We don't really know what that timer is since none of us programmed the actual firmware on the phone.

Link to comment
Share on other sites

I'm not speaking for Google or anything, but my guess is they have an adaptive timer that activates an LTE scan that could probably range from a few milliseconds to 5 minutes or longer. As an example, if you just got out of LTE range and it dropped to 3G, it might scan for LTE in 10 seconds or so. After failing a couple times, it'll drop the frequency to every 1 minute or so, and after that it may go up to 5 or 10 minutes to save battery life. We don't really know what that timer is since none of us programmed the actual firmware on the phone.

 

I wish they did.  That would be highly effective.  It seems to me, and at least on my N5, whether I am on Tmo, AT&T or Sprint, if I drop LTE, it will not reconnect again on its own for several minutes.  Even when I know I am back in coverage a mere 5-10 seconds later.

  • Like 4
Link to comment
Share on other sites

I wish they did.  That would be highly effective.  It seems to me, and at least on my N5, whether I am on Tmo, AT&T or Sprint, if I drop LTE, it will not reconnect again on its own for several minutes.  Even when I know I am back in coverage a mere 5-10 seconds later.

Again, I don't know how Google's firmware works. I'm just making guesses based on what guirae was seeing with picking up LTE in less than 5 minutes.

 

Edit: To add to that, maybe Google's timer is 2 minutes at first and then 5 or 10 minutes later. Again, I don't know.

Edited by metayoshi
Link to comment
Share on other sites

I wish they did.  That would be highly effective.  It seems to me, and at least on my N5, whether I am on Tmo, AT&T or Sprint, if I drop LTE, it will not reconnect again on its own for several minutes.  Even when I know I am back in coverage a mere 5-10 seconds later.

That is exactly my experience. Is that the same on other tri-band devices?

Link to comment
Share on other sites

That is exactly my experience. Is that the same on other tri-band devices?

No. Not all. And on AT&T, the Nexus 5 is a Quad Band device. And the problem still occurs. I can be there next to a BlackBerry Z30, HTC 8X and Samsung Galaxy Mega on AT&T LTE and they will rescan and acquire LTE between 5 and 30 seconds. And the Nexus 5 will take 3-5 minutes. So neither operating system, nor band support is relevant. The common denominator is the Nexus 5. Regardless of network.

Link to comment
Share on other sites

I don't think manual would be necessary if the timer went something like;

 

10 seconds > 15 > 30 > 60 > 120 > 240 > 300 (5 minutes max rescan)

Link to comment
Share on other sites

I wouldn't want it any higher than 2 imho.

 

if you were out of a sprint lte area and your battery went kaput from constant 2 minutes scans, perhaps you would change your mind, or not.

Link to comment
Share on other sites

The one thing I have noticed that if the phone is an area that it has been on LTE on a regular basis and it gets kicked off, it will often (but not always) rescan and acquire LTE quickly. In a new area (for the phone), it just sits on 3G after the first time it looses it.

Link to comment
Share on other sites

I think the bigger issue is after all data activity has stopped the connection stays open longer than any other phone I owned. If the connection is active no scanning takes place. It's hard to see it without Signalcheck, but if you look at it the data stream stays active for a long time after the data stopped flowing.

Link to comment
Share on other sites

No. Not all. And on AT&T, the Nexus 5 is a Quad Band device. And the problem still occurs. I can be there next to a BlackBerry Z30, HTC 8X and Samsung Galaxy Mega on AT&T LTE and they will rescan and acquire LTE between 5 and 30 seconds. And the Nexus 5 will take 3-5 minutes. So neither operating system, nor band support is relevant. The common denominator is the Nexus 5. Regardless of network.

How about another Sprint device?

 

Anyone else put there take shorter than 3 minutes to go from 3G to LTE?

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