Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

Although I have returned my phone to Google I was curious if anyone having the problem where you cannot answer an incoming call when connected to LTE has seen any resolution to the issue yet. I was not able to get any help from either Sprint or Google. When this issue is sorted out I was going to consider buying the phone again. Thanks

Link to comment
Share on other sites

Although I have returned my phone to Google I was curious if anyone having the problem where you cannot answer an incoming call when connected to LTE has seen any resolution to the issue yet. I was not able to get any help from either Sprint or Google. When this issue is sorted out I was going to consider buying the phone again. Thanks

I just did a test few min ago.I asked my wife to call me .no issues(LTE)

Link to comment
Share on other sites

I had issues receiving calls as well. Turns out it was Google Voice. Once I disabled account integration and got rid of it, my calls work perfectly again. This was on my G2. Might be worth a shot on the N5,though.

Link to comment
Share on other sites

Is anyone having issues with Sensorly? During mapping Sensorly just closes on its own. Upon reinitiating mapping it does not collect any data.

I forgot what forum here but others are also having that issue.

 

 

 

Link to comment
Share on other sites

Is anyone having issues with Sensorly? During mapping Sensorly just closes on its own. Upon reinitiating mapping it does not collect any data.

Funny I just ran Sensorly on way to drop my kids at school 30 min ago .ran fine when I checked collected data

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

I had issues receiving calls as well. Turns out it was Google Voice. Once I disabled account integration and got rid of it, my calls work perfectly again. This was on my G2. Might be worth a shot on the N5,though.

I use Google voice only to make international calls maybe that's why I didn't have issues

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

Looks like by black 32GB N5 shows up Wednesday, ordered on the 4th. 

 

Have the SIM in-hand, hopefully I won't have any major problems what with being in a good incumbent market. 

 

Now if they would just get 800MHz LTE going around here. 

Link to comment
Share on other sites

Is anyone having issues with Sensorly? During mapping Sensorly just closes on its own. Upon reinitiating mapping it does not collect any data.

One issue I've seen with Sensorly since I got my G2 is that when I first start mapping, it is stuck on "1" point collected and I have to stop and start again and then it will start collecting data points like normal.

Link to comment
Share on other sites

One issue I've seen with Sensorly since I got my G2 is that when I first start mapping, it is stuck on "1" point collected and I have to stop and start again and then it will start collecting data points like normal.

Does anyone else cycle airplane mode while mapping? 

Link to comment
Share on other sites

Does anyone else cycle airplane mode while mapping?

 

I did at first when I had the CSFB issues the first couple of days but stopped since overall I have seen a consistent LTE signal. I just got the LTE Discovery app which has an auto rescan that you can set as low as every 20 seconds. I think I will give it a shot for those Highway drives where I drop LTE for a few hundred feet between tower handoffs.

Link to comment
Share on other sites

I am also having issues where calls and texts are not going through. I disabled and renabled google voice. hopefully that fixed it.

Keep us posted please on the results.

 

Sent from my SPH-L710 using Tapatalk

 

 

Link to comment
Share on other sites

I believe it has been mentioned before but it seems like when I am on LTE and receive a phone call it drops to 1x 1900.  However, when I am on 3g and receive a phone call it connects to 1x 800.  This stands true 100% of the time for me albeit I have only checked on a few occasions.  Any one else noticing the same or different?  Has there been an explanation posted for this yet?  It's not really a problem in the Chicago suburbs because cell spacing is pretty good...just thought it was weird that it was so consistent.

Link to comment
Share on other sites

I believe it has been mentioned before but it seems like when I am on LTE and receive a phone call it drops to 1x 1900.  However, when I am on 3g and receive a phone call it connects to 1x 800.  This stands true 100% of the time for me albeit I have only checked on a few occasions.  Any one else noticing the same or different?  Has there been an explanation posted for this yet?  It's not really a problem in the Chicago suburbs because cell spacing is pretty good...just thought it was weird that it was so consistent.

 

Mine is YMMV.  I've called voicemail twice in a row to see it drop down from LTE to 1x on channel 650 (1900) and 1 second later, call back and be on 1x channel 476 (ESMR 800).

 

I have no idea how many towers have 1x on channel 476 up but it is huge.  I hope sprint gets 1x on ESMR ASAP.

Link to comment
Share on other sites

Apologies in advance if this is the wrong forum to ask this question. I live in the Seattle area and Sensorly shows 4G is available.

 

I've have enabled LTE / Band 26 / Band 41 and priorities are set to the below:

 

Band 25 - 0
Band 26 - 0
Band 41- 1

 

Preferred network mode is set to LTE and not Global. However, I'm always on 3G and never able to pick up 4G.

 

Did I miss any setting? If not, I suspect its due to this?

 

http://s4gru.com/index.php?/blog/1/entry-357-nexus-5-and-lg-g2-experience-temporary-sprint-lte-connectivity-issues-due-to-circuit-switched-fallback-technology/

Link to comment
Share on other sites

Apologies in advance if this is the wrong forum to ask this question. I live in the Seattle area and Sensorly shows 4G is available.

 

I've have enabled LTE / Band 26 / Band 41 and priorities are set to the below:

 

Band 25 - 0

Band 26 - 0

Band 41- 1

 

Preferred network mode is set to LTE and not Global. However, I'm always on 3G and never able to pick up 4G.

 

Did I miss any setting? If not, I suspect its due to this?

 

http://s4gru.com/index.php?/blog/1/entry-357-nexus-5-and-lg-g2-experience-temporary-sprint-lte-connectivity-issues-due-to-circuit-switched-fallback-technology/

 

Seattle is in market that has the eCSFB issue.  Don't tinker with B41 and just leave it on B25 only for now until you can establish that B25 LTE starts showing up in Seattle.

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