Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

My CDMA roaming mode was already set to Automatic, so even if that could help it won't help me, but thanks for trying.

 

After looking into this more I think it may be a network handoff issue.  Maybe someone with more knowledge of how the network works can let me know, but when I place a voice call Signal Check reports that I am on 1x800.  According to the NV Complete maps in the sponsor section there is a tower near me that has 1x800 but not LTE and there is a tower near me that has LTE but not 1x800.  My theory is that my phone is switching between these towers depending on what signal type i'm requesting and there is an issue with the handoff.  Does that sound reasonable?

Turn off LTE while in your home. Assuming you have WiFi. 

  • Like 1
Link to comment
Share on other sites

My CDMA roaming mode was already set to Automatic, so even if that could help it won't help me, but thanks for trying.

 

After looking into this more I think it may be a network handoff issue.  Maybe someone with more knowledge of how the network works can let me know, but when I place a voice call Signal Check reports that I am on 1x800.  According to the NV Complete maps in the sponsor section there is a tower near me that has 1x800 but not LTE and there is a tower near me that has LTE but not 1x800.  My theory is that my phone is switching between these towers depending on what signal type i'm requesting and there is an issue with the handoff.  Does that sound reasonable?

 

If one site has been NV cluster launched and the other site hasn't, you will get dropped. I work in a place that has been cluster launched and live in a place that hasn't so any phone call I'm on when I cross the threshold gets dropped.  I'm not sure if that's your issue but if your house is near that boarder that's most likely what is happening.

  • Like 1
Link to comment
Share on other sites

Re the Spark update. I'm pretty convinced that Sprint is not at fault here. I believe they had it ready to go several weeks ago, but Google, for whatever reason, decided to throw the update in with another update (4.4.3). However, Google's release schedule on that update was not in line with Sprint's anticipated release schedule on the Spark update (early 2014). Moreover, once the update was finalized and released for internal beta testing, they discovered an issue and the has been held back even longer. That's what I think happened. 

 

I wonder if this will make Sprint hesitant to offer an open, cross-carrier device like the Nexus 5 in the future. 

Link to comment
Share on other sites

I think the point has been made, the posy was deleted, lets move on and continue talkon ways we can help our situations. You can argue all you want it will not get the post back. Just post something that others have known to try,but if it only works for one person it sounds kind of irrelevant. And continued arguing with staff is a good way to end in bannedlandia :P

  • Like 1
Link to comment
Share on other sites

Don't know if anyone noticed a substantial increase in stability with full blown Gvoice integration enabled. Calls are coming in swiftly and outgoing calls have 0 delay.

 

Lots will be ecstatic to hear that. 

Link to comment
Share on other sites

Lots will be ecstatic to hear that.

 

This could have something to do with the way the calls are being routed. Considering that hangouts got a nice update yesterday, I would not put it past Google doing some much needed upgrades to address these nagging issues before fully integrating hangouts and Gvoice.
  • Like 1
Link to comment
Share on other sites

Don't know if anyone noticed a substantial increase in stability with full blown Gvoice integration enabled. Calls are coming in swiftly and outgoing calls have 0 delay.

 

as in something has changed VERY recently?  can anyone else confirm or deny this?  i have always found full GV integration unusable on the N5.

  • Like 1
Link to comment
Share on other sites

Don't know if anyone noticed a substantial increase in stability with full blown Gvoice integration enabled. Calls are coming in swiftly and outgoing calls have 0 delay.

 

I've never had an issue with full GV integration. I've used it pretty much since it was first offered across a suite of devices. Guess I've been lucky.

  • Like 1
Link to comment
Share on other sites

I've never had an issue with full GV integration. I've used it pretty much since it was first offered across a suite of devices. Guess I've been lucky.

Same. Never had an issue with integration. Been using it since it first came out.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I've wanted to use Integrated GV, but I still have mine as separate since I have a second number I use with it and I don't think you can have your Sprint number and GV number fully integrated simultaneously.

Link to comment
Share on other sites

I've wanted to use Integrated GV, but I still have mine as separate since I have a second number I use with it and I don't think you can have your Sprint number and GV number fully integrated simultaneously.

I had a gv number before integrating and Google had an option when I was switching over to pay 20 dollars and keep my Google voice number. I doubt much has changed just based on how little other aspects of Google voice have changed since I integrated.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I've wanted to use Integrated GV, but I still have mine as separate since I have a second number I use with it and I don't think you can have your Sprint number and GV number fully integrated simultaneously.

 

Nope, it's one or the other. I choose to integrate my Sprint number, and kept my old GV number on the side just in case. Can't make calls with it, but can receive calls and texts to that number on my phone.

Link to comment
Share on other sites

Nope, it's one or the other. I choose to integrate my Sprint number, and kept my old GV number on the side just in case. Can't make calls with it, but can receive calls and texts to that number on my phone.

I stand partially corrected.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I stand partially corrected.

 

Sent from my Nexus 5 using Tapatalk

 

No you're still correct, his post doesn't contradict yours.

Link to comment
Share on other sites

You do still have to pay to keep the GV number. But I chose to not integrate it, rather than keep it as an extension and integrate my Sprint number.

Can you make outbound calls that show up as the non integrated number?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Can you make outbound calls that show up as the non integrated number?

 

Sent from my Nexus 5 using Tapatalk

 

I still can, but I have mine set up for my Sprint calls to be forwarded there for VM. It handles it well.

Link to comment
Share on other sites

I still can, but I have mine set up for my Sprint calls to be forwarded there for VM. It handles it well.

I meant with one integrated and one non integrated number on the same account. Per dkoellers comment.

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

I've always had a slight delay making and receiving calls with full Gvoice integration (but perfectly usable), as of last night it has been lightning fast with outgoing and incoming calls. As if they upgraded the Gvoice backend.

Link to comment
Share on other sites

as in something has changed VERY recently?  can anyone else confirm or deny this?  i have always found full GV integration unusable on the N5.

Google just upgraded Hangouts, so could be related, not a fact, but it sure seems that way considering the performance difference.

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