Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

Waiting for this Spark update is frustrating :(

 

This.

 

It's the main reason I bought this phone. I mean it is getting to the point of ridiculous. The phone will be outdated before you can use it like it was designed.

  • Like 2
Link to comment
Share on other sites

This.

 

It's the main reason I bought this phone. I mean it is getting to the point of ridiculous. The phone will be outdated before you can use it like it was designed.

I bet that well see the update within a month. Some of the source that say its a "few weeks away" are known for being reliable. Plus they were correct when it came to previous updates.

 

Sent from my Nexus 5 using Tapatalk

 

 

  • Like 1
Link to comment
Share on other sites

I bet that well see the update within a month. Some of the source that say its a "few weeks away" are known for being reliable. Plus they were correct when it came to previous updates.

 

Sent from my Nexus 5 using Tapatalk

 

update coming=yes, spark included in the update=nobody knows

  • Like 1
Link to comment
Share on other sites

I only have connected to LTE on 1900 MHz and know about the 2600 issue the Spark update will fix but is 800 working well or will that have to wait for the update too.

 

Sent from Nexus 5

 

Link to comment
Share on other sites

I only have connected to LTE on 1900 MHz and know about the 2600 issue the Spark update will fix but is 800 working well or will that have to wait for the update too.Sent from Nexus 5

800 voice or band 26 LTE? In regards to voice people have been reporting trouble getting connected to 800. Partly because the n5 is a rf beast, and partly due to the new prl's favoring 1900.

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

800 voice or band 26 LTE? In regards to voice people have been reporting trouble getting connected to 800. Partly because the n5 is a rf beast, and partly due to the new prl's favoring 1900.

 

Sent from my Nexus 5 using Tapatalk

No trouble with 800 voice on my end. I seem to connect this way very often in the last week. Posted Image
Link to comment
Share on other sites

No trouble with 800 voice on my end. I seem to connect this way very often in the last week. Posted Image

That's a ridiculous signal level! You must be in a poor 1900 area. All I've seen is 1900 everywhere I go excluding one cave where 800 kicked in.

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

http://www.myce.com/news/nexus-7-also-receives-android-4-4-3-update-3-day-old-build-ktu83-spotted-70973/

 

I think we'll be seeing an update very soon, considering there is a new build of 4.4.3 in the wild. Previous build was KTU72B and now we have KTU83, which was apparently created on March 21.

Link to comment
Share on other sites

I live in San Antonio TX. I just got a text from Sprint saying the new network is complete in my area. I did a PRL and Profile update and rebooted. After reboot all bands were enabled with 26 and 41 on priority 1. Have not been able to verify band 41 yet as I am not currently in San Antonio.

Link to comment
Share on other sites

I live in San Antonio TX. I just got a text from Sprint saying the new network is complete in my area. I did a PRL and Profile update and rebooted. After reboot all bands were enabled with 26 and 41 on priority 1. Have not been able to verify band 41 yet as I am not currently in San Antonio.

 

have you entered your MSL code and enabled B26 or B41 ever?

Link to comment
Share on other sites

Yes. But each time I did PRL and profile update it reverted back to only 25. They were at stock settings before this time. I stopped enabling after the second time while reading this thread. I did not want to do the radio change and try again

Link to comment
Share on other sites

Yes. But each time I did PRL and profile update it reverted back to only 25. They were at stock settings before this time. I stopped enabling after the second time while reading this thread. I did not want to do the radio change and try again

I got the exact same message you did(just in an email) so I went ahead and did what you said you did, except I disabled both bands before I started. It didn't turn b41 or 26 on for me...so I just re-enabled them.

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

That's a ridiculous signal level! You must be in a poor 1900 area. All I've seen is 1900 everywhere I go excluding one cave where 800 kicked in.

 

Sent from my Nexus 5 using Tapatalk

I was making a call out in a public shopping area late in the evening hours and I found it strange since I'm idling on 1xRTT 1900 90% percent of the time.
  • Like 1
Link to comment
Share on other sites

I live in San Antonio TX. I just got a text from Sprint saying the new network is complete in my area. I did a PRL and Profile update and rebooted. After reboot all bands were enabled with 26 and 41 on priority 1. Have not been able to verify band 41 yet as I am not currently in San Antonio.

The message is a generic message and not an indicator of any actual network status. That message has gone out to virtually the entire country over the past 6 weeks. Updating your profile will keep bands enabled, but re-prioritize them at the default Sprint priorities...

Link to comment
Share on other sites

You can call Care and have them re-provision Voicemail on your account, or you could activate Google Voice (and de-activate it again if you don't want it). Make sure you listen to any important voicemail first, as they will be deleted either way.

I added Google voice (full integration) last month and still get the messages. I'll try calling customer care, I tried webchat before and they didn't really have any information about what the messages were let alone how to stop them. Thanks for the info, the texts have been driving me nuts.

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

I have a question when im on lte.  Place a call the time goes back an hour.  Doesn't fix it self till ten minutes after i hang up.

 

 

 

Sprint was testing band 41 at NASCAR i believe on nexus 5.   Could be a beta phone

Link to comment
Share on other sites

Sprint seems to have some widespread Daylight Saving Time bugs in their NV deployments.  Several of us have experienced the 1 hour off time when your phone is set to acquire time automatically from the network.  It seems to have started with the "Spring Forward" a few weeks ago.  It is possible that the 3G/1x connection that you are moving back to when talking on the telephone has a different time than the LTE network that you are normally on due to this bug.  If your time is off and the tower and band you are on has been accepted, you should contact Sprint so they can fix the automatic time in that area.

  • Like 3
Link to comment
Share on other sites

Sprint seems to have some widespread Daylight Saving Time bugs in their NV deployments. Several of us have experienced the 1 hour off time when your phone is set to acquire time automatically from the network. It seems to have started with the "Spring Forward" a few weeks ago. It is possible that the 3G/1x connection that you are moving back to when talking on the telephone has a different time than the LTE network that you are normally on due to this bug. If your time is off and the tower and band you are on has been accepted, you should contact Sprint so they can fix the automatic time in that area.

Yep I've gotten this a few times driving between Orlando and Jacksonville. It can be very frustrating if you don't catch that your phone went back an hour.

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

so no mention of sprint triband.if it isn't not in this update, its highly likely that the next android release doesn't come until 4.5/5.0 at IO

 

IMVHO

 

sooooooo baseband (radio) version still the same  :td:  :td:  :td:  :td:  :td:

Link to comment
Share on other sites

sooooooo baseband (radio) version still the same  :td:  :td:  :td:  :td:  :td:

We don't know whether the baseband has changed or not because the source blacked out the rest of the version string. M8974 is merely the number for the Snapdragon 800 family (MSM8974), so all of our baseband versions should start with that.

  • Like 4
Link to comment
Share on other sites

We don't know whether the baseband has changed or not because the source blacked out the rest of the version string. M8974 is merely the number for the Snapdragon 800 family (MSM8974), so all of our baseband versions should start with that.

 

oh good good!

Link to comment
Share on other sites

Everyone needs to chill and stop worrying about the spark update. We already know it is coming. Furthermore, Google knows what they are doing and they do talk to Sprint because otherwise there would be no sprint nexus 5.

 

Sent from my Nexus 5 using Tapatalk

 

 

  • Like 3
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...