Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

It doesn't have to be a nexus. Wouldn't any triband device provide the same result? Spark update or not. Shouldn't matter.

Sent from my Nexus 5

I don't think so because it wouldn't be apples to apples, right? Because this phone really isn't triband yet. Not until the update. I may be missing something...?
Link to comment
Share on other sites

Use any Tri-band device in a sprint store. Spark is not going to solve ecsfb issues. If those devices are connecting fine to LTE then it is your device. If they aren't connecting then I would say ecsfb.

Oh OK I see.

Link to comment
Share on other sites

I don't think so because it wouldn't be apples to apples, right? Because this phone really isn't triband yet. Not until the update. I may be missing something...?

No. It's still triband, single-path device. It should be an easy, 1 minute troubleshoot in a sprint store, or a friend with a triband sprint phone.

 

Sent from my Nexus 5

  • Like 1
Link to comment
Share on other sites

Ericsson has been busy forgetting to add eCSFB to sites all over again with band 26. There are a bunch of sites now that already had eCSFB active on band 25 which are now screwed up after their band 26 additions.

 

ralph-the-paste-eater.jpg

  • Like 5
Link to comment
Share on other sites

http://www.gottabemobile.com/2014/04/28/android-4-4-3-kitkat-release-details-leak/

 

Apologies if this was posted earlier, but it looks like HTC is to blame for the 4.4.3 release delay according to this article.

I skimmed the article and I don't believe that is what its implying. It simply stated leaked HTC release dates for devices that will receive 4.4.3 updates and devices essentially being discontinued from further updates.
  • Like 2
Link to comment
Share on other sites

I skimmed the article and I don't believe that is what its implying. It simply stated leaked HTC release dates for devices that will receive 4.4.3 updates and devices essentially being discontinued from further updates.

i agree, i dont see anything linking the blame to HTC 

Link to comment
Share on other sites

I skimmed the article and I don't believe that is what its implying. It simply stated leaked HTC release dates for devices that will receive 4.4.3 updates and devices essentially being discontinued from further updates.

 

 

i agree, i dont see anything linking the blame to HTC 

 

"Software update release dates are dependent on the progress made in internal testing and at the moment, it doesn’t look like HTC has completed that testing for its Android 4.4.3 KitKat updates."

Link to comment
Share on other sites

It's kind of vague in that aspect I guess. That's what I got out of reading it, but they could just be referring to HTC specific updates. but maybe it could be part of the reason, maybe not. Just thought it would be interesting to see what you guys thought.

Link to comment
Share on other sites

"Software update release dates are dependent on the progress made in internal testing and at the moment, it doesn’t look like HTC has completed that testing for its Android 4.4.3 KitKat updates."[/size]

that's specific to HTC devices and there sense software ui overlay. Nothing to do with 4.4.3 for nexus 5 or other manufacturer releases.
Link to comment
Share on other sites

Does the One having a google play edition model come in to play with this HTC article? Perhaps that is the holdup? Or is it Nexus > GPE Handsets > Dispersed to big 4

 

EDIT - And there I go reading the entire article and figuring it out for myself. 

Edited by zippychance
Link to comment
Share on other sites

http://www.gottabemobile.com/2014/04/28/android-4-4-3-kitkat-release-details-leak/

 

Apologies if this was posted earlier, but it looks like HTC is to blame for the 4.4.3 release delay according to this article.

I don't read that in the article. Google isn't holding up the release because of HTC or any other phone manufacturer. It just says that HTC is testing the version that it has.

 

Gotta be mobile is a bad news source. All they do is sum up other information already available. They never have original content.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Oh OK I see.

 

 

I just quoted your last post, but this goes to the rest of the conversation. Everything you have post previously, and what you have posted today still confirms my thought that you have a defective device. There should be NO CSFB issues in your area. And you have been having this problem since before B26 could have even caused an issue.

 

You have a defective device.

 

Since you bought it from Sprint, you should be able to get support from them. If not, elevate to Google. You should not be having such a terrible time on the network. The Nexus 5 has the most powerful LTE reception of any device that Sprint currently offers. Anywhere another device gets LTE, you should get LTE too.

 

In the very minimal, practically null chance that it is a CSFB issue, compare against *ANY* other Tri-Band device to see if they are having issues.

 

Until you do that, no one here can help you any more than they already have.

  • Like 10
Link to comment
Share on other sites

Why is this difficult? Put into LTE Only mode. Drive around. If you are getting normal LTE signals where you go, the problem is CSFB. Also, you can compare with other Spark devices. It won't hurt anything. Because if it's CSFB, it will affect them all, not just the N5.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

  • Like 7
Link to comment
Share on other sites

Why is this difficult? Put into LTE Only mode. Drive around. If you are getting normal LTE signals where you go, the problem is CSFB. Also, you can compare with other Spark devices. It won't hurt anything. Because if it's CSFB, it will affect them all, not just the N5.

Robert via Samsung Note 8.0 using Tapatalk Pro

Whoa..relax guys. Seriously. I appreciate the input and will do as you guys say. I definitely appreciate the input for sure but not the sarcasm. Geez!! I'll report back my findings later today.
Link to comment
Share on other sites

Whoa..relax guys. Seriously. I appreciate the input and will do as you guys say. I definitely appreciate the input for sure but not the sarcasm. Geez!! I'll report back my findings later today.

 

You thought I was being sarcastic?  I was not being sarcastic.  I will have to work on my tone.  I was trying to get across fatherly and direct.

 

Robert

  • Like 5
Link to comment
Share on other sites

You thought I was being sarcastic?  I was not being sarcastic.  I will have to work on my tone.  I was trying to get across fatherly and direct.

 

Robert

Ha well thanks. I am not as tech savvy as most in this forum (which is why this has been difficult to grasp for me) but I'm still the king nerd in my circle of friends.
Link to comment
Share on other sites

Ha well thanks. I am not as tech savvy as most in this forum (which is why this has been difficult to grasp for me) but I'm still the king nerd in my circle of friends.

 

It is all relative! ;)

  • Like 2
Link to comment
Share on other sites

You thought I was being sarcastic?  I was not being sarcastic.  I will have to work on my tone.  I was trying to get across fatherly and direct.

 

Robert

 

Father Robert? :lol:

  • Like 2
Link to comment
Share on other sites

Why is this difficult? Put into LTE Only mode. Drive around. If you are getting normal LTE signals where you go, the problem is CSFB. Also, you can compare with other Spark devices. It won't hurt anything. Because if it's CSFB, it will affect them all, not just the N5.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Excuse my ignorance, but how do you do  LTE only mode? Are we talking Preferred Network types or something else?

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