Jump to content

Google Nexus 5 by LG Users Thread!

nexgencpu

By nexgencpu
in Google

 Share

Recommended Posts

MacinJosh Member Level: LTE Advanced

MacinJosh

Posted
Posted

Google is just a company full of idiots apparently since they've had over 5 months to figure this Spark thing out.

 

 

Sent from my Josh's iPad using Tapatalk 2

Link to comment
Share on other sites
  • Replies 9.8k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

S4GRU
S4GRU

I had a Sprint product development employee reach out to me this morning after reading this thread. His message says:   Robert via Samsung Note 8.0 using Tapatalk Pro

MacinJosh
MacinJosh

I am now the proud owner of a Nexus 5!       Sent from Josh's iPhone 5 using Tapatalk 2

S4GRU
S4GRU

Mine just arrived!!!  

Posted Images

khammondnm Member Level: eHRPD

khammondnm

Posted
Posted

Google is just a company full of idiots apparently since they've had over 5 months to figure this Spark thing out.

 

 

Sent from my Josh's iPad using Tapatalk 2

We don't know that spark is the reason for the hold up. I would bet that it isn't and that some other bug is holding up the update, the planned delivery method for spark.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites
MacinJosh Member Level: LTE Advanced

MacinJosh

Posted
Posted

Sorry, but they shouldn't have done it that way. That's my official stance on Google. I think some other carrier paid them off to cripple the Spark update so Sprint users don't have access.

 

 

Sent from my Josh's iPad using Tapatalk 2

Link to comment
Share on other sites
EvanA Member Level: 4G WiMax

EvanA

Posted
Posted

Google is just a company full of idiots apparently since they've had over 5 months to figure this Spark thing out.

 

 

Sent from my Josh's iPad using Tapatalk 2

Please, tell me how you would do it faster and better than full time experienced software engineers. Also, the modem software is most likely handled by LG/Qualcomm engineers, not Google.

 

Sent from my Nexus 7 using Tapatalk

  • Like 2
Link to comment
Share on other sites
though Member Level: 4G WiMax

though

Posted
Posted

I said it earlier this week and I still think another carrier is complaining about some insignificant "bug" to Google and intentionally holding up this update. Specifically to keep the Spark enhancements away from Sprint users.

 

They have succeeded.

 

this is wrong

Link to comment
Share on other sites
Fubie Member Level: 3G EVDO

Fubie

Posted
Posted

Since I've been away from Sprint and the forums would someone help bring me back up to speed on something.  In order to "quickly" connect to LTE data on the towers around my home town I had to toggle airplane mode before it would connect LTE.  This was on known good LTE towers.  Later this evening while driving into another town nearby it took 5-10 minutes after I was inside of the coverage of another good LTE tower before my phone switched to LTE.  I really don't think the N5 is the problem.  While on AT&T I rarely dropped to HSPA and there was little to no lag time when connecting to a known LTE towers.  No airplane mode toggling needed.

Link to comment
Share on other sites
EvanA Member Level: 4G WiMax

EvanA

Posted
Posted

Since I've been away from Sprint and the forums would someone help bring me back up to speed on something. In order to "quickly" connect to LTE data on the towers around my home town I had to toggle airplane mode before it would connect LTE. This was on known good LTE towers. Later this evening while driving into another town nearby it took 5-10 minutes after I was inside of the coverage of another good LTE tower before my phone switched to LTE. I really don't think the N5 is the problem. While on AT&T I rarely dropped to HSPA and there was little to no lag time when connecting to a known LTE towers. No airplane mode toggling needed.

The reason why there is a long delay sometimes is the scan time for LTE being set to 30 min intervals (at least on sprint). This means that the phone is only going to look for LTE every 30 minutes. I have a feeling this will be shortened in the future once sprint has more widespread LTE coverage.

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites
Destroyallcubes Member Level: 4G LTE

Destroyallcubes

Posted
Posted

The reason why there is a long delay sometimes is the scan time for LTE being set to 30 min intervals (at least on sprint). This means that the phone is only going to look for LTE every 30 minutes. I have a feeling this will be shortened in the future once sprint has more widespread LTE coverage.

 

Sent from my Nexus 7 using Tapatalk

The scan times vary by phone model/manufacturer , and are not set at 30 minutes. 

Link to comment
Share on other sites
JonnygATL Member Level: 4G WiMax

JonnygATL

Posted
Posted

So please don't attack me for being new to some of this but I got my MSL from Sprint today (they were way sketched out that i asked for it) so that I could manually enable bands 26 and 41 on my phone. I also have signal check pro installed on my phone. How do I know which band I'm connected to via signal check pro or some other means? And..as I've mentioned before.. my N5 has a VERY hard time finding an LTE signal in areas with excellent LTE coverage so my encounters with it are a bit fleeting. But...still..I would like to know.

Link to comment
Share on other sites
EvanA Member Level: 4G WiMax

EvanA

Posted
Posted

So please don't attack me for being new to some of this but I got my MSL from Sprint today (they were way sketched out that i asked for it) so that I could manually enable bands 26 and 41 on my phone. I also have signal check pro installed on my phone. How do I know which band I'm connected to via signal check pro or some other means? And..as I've mentioned before.. my N5 has a VERY hard time finding an LTE signal in areas with excellent LTE coverage so my encounters with it are a bit fleeting. But...still..I would like to know.

Signal check should tell you the band by adding B41 or B26 after the sprint designation.

 

Sent from my Nexus 7 using Tapatalk

  • Like 1
Link to comment
Share on other sites
JonnygATL Member Level: 4G WiMax

JonnygATL

Posted
Posted

Signal check should tell you the band by adding B41 or B26 after the sprint designation.

Sent from my Nexus 7 using Tapatalk

OK thanks. And I'm amused right now because I'm on 19th street in midtown Atlanta.. an area with wall to wall outdoor LTE coverage..and my N5 is stuck in 3G. Next time I can force it to latch onto LTE I will see what band I'm on. Will it mention b25 or no? You said it would indicate bands 26 and 41 but will it also say b25 where applicable?
Link to comment
Share on other sites
EvanA Member Level: 4G WiMax

EvanA

Posted
Posted

OK thanks. And I'm amused right now because I'm on 19th street in midtown Atlanta.. an area with wall to wall outdoor LTE coverage..and my N5 is stuck in 3G. Next time I can force it to latch onto LTE I will see what band I'm on. Will it mention b25 or no? You said it would indicate bands 26 and 41 but will it also say b25 where applicable?

There might be CSFB issues in your area, which is why the N5 won't connect. If you are on B25 there won't be anything extra to indicate that.

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites
Mr.Nuke Member Level: LTE Advanced

Mr.Nuke

Posted
Posted

I said it earlier this week and I still think another carrier is complaining about some insignificant "bug" to Google and intentionally holding up this update. Specifically to keep the Spark enhancements away from Sprint users.

 

They have succeeded.

First you'd have to believe Google would delay said release based on the report. This is possible if they want more time to investigate it, but I'm assuming they already soak tested the release on all 3 North American carriers and didn't find an issue (if you are going this route). The bigger problem is if you buy into this line of thinking AT&T or Magenta are using google to screw with Sprint. That in itself may sound ok (it doesn't to me...).  Google isn't going to go for that, and the Uncarrier doesn't want to screw up any relationship they have with google. The logic here is massively flawed.

Link to comment
Share on other sites
JonnygATL Member Level: 4G WiMax

JonnygATL

Posted
Posted

There might be CSFB issues in your area, which is why the N5 won't connect. If you are on B25 there won't be anything extra to indicate that.

Sent from my Nexus 7 using Tapatalk

My understanding of eCSFB issues was that it only applied to non NV upgraded 3g towers. Thankfully those don't exist anywhere around here and so I'm inclined to believe that it has nothing to do with eCSFB issues. I took my phone to Sprint and they were about to close and had zero interest in actually having the tech look at it. I was pissed. And not in the British way
Link to comment
Share on other sites
EvanA Member Level: 4G WiMax

EvanA

Posted
Posted

My understanding of eCSFB issues was that it only applied to non NV upgraded 3g towers. Thankfully those don't exist anywhere around here and so I'm inclined to believe that it has nothing to do with eCSFB issues. I took my phone to Sprint and they were about to close and had zero interest in actually having the tech look at it. I was pissed. And not in the British way

CSFB is an issue for upgraded towers, not old ones.

 

I am almost certain you're seeing eCSFB issues. How long have you experienced this issue?

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites
lilotimz Member Level: LTE Advanced

lilotimz

Posted
Posted

CSFB is an issue for upgraded towers, not old ones.

 

I am almost certain you're seeing eCSFB issues. How long have you experienced this issue?

 

Sent from my Nexus 7 using Tapatalk

 

eCSFB / CSFB issues occur when the base station firmware are not updated to enable eCSFB / CSFB functionality. NV 3G =/= eCSFB. Ericsson network management still has to push the update to the individual sites and they take their sweet sweet time to do so. 

Link to comment
Share on other sites
Jackietreehorn Member Level: 1x Advanced

Jackietreehorn

Posted
Posted

I guess anything is possible, but all of this "other carriers are out to get Sprint" talk just seems kind of...I don't know, tinfoil hat ish?  I don't think the other carriers care all that much about what Sprint is doing at current, especially an update that's going to effect such a small number of users.

 

Regardless, I guess this at least definitively answers the question of whether it's Sprint or Google that's the hold up, so we've got that going for us.

  • Like 7
Link to comment
Share on other sites
JonnygATL Member Level: 4G WiMax

JonnygATL

Posted
Posted

CSFB is an issue for upgraded towers, not old ones.

I am almost certain you're seeing eCSFB issues. How long have you experienced this issue?

Sent from my Nexus 7 using Tapatalk

Ah...OK. Wow I hope you're correct. That would mean that there is a light at the end of the tunnel, never mind how distant. But I'm sooooooo extremely frustrated because I went from a great 4g phone (galaxy s4) to what FEELS LIKE a 3g phone. I can't with this!! Oh...and I've experienced these issues since I bought this phone one month ago.

  • Like 1
Link to comment
Share on other sites
S4GRU Member Level: LTE Advanced

S4GRU

Posted
Posted

I guess anything is possible, but all of this "other carriers are out to get Sprint" talk just seems kind of...I don't know, tinfoil hat ish? I don't think the other carriers care all that much about what Sprint is doing at current, especially an update that's going to effect such a small number of users.

 

Regardless, I guess this at least definitively answers the question of whether it's Sprint or Google that's the hold up, so we've got that going for us.

It's not ALL this talk. Not very many people have subscribed to the idea at all, really.

 

Robert via Nexus 5 using Tapatalk

  • Like 5
Link to comment
Share on other sites
S4GRU Member Level: LTE Advanced

S4GRU

Posted
Posted

There is no technical Spark issues remaining to be resolved. Sprint has soak tested and approved. The ball is completely in Google's court. Spark is not the reason for the delay in Google holding the OTA. We will get it when Google is darn ready.

 

Robert via Nexus 5 using Tapatalk

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

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • dkyeager
      Dish Network/Boost Mobile cell/5G buildout thread

      By dkyeager · Posted

      Yes! That does keep it from wandering off Dish and most importantly, reconnecting immediately (at least where their is n70). Thanks!
    • Trip
      Dish Network/Boost Mobile cell/5G buildout thread

      By Trip · Posted

      I have my Dish phone locked to NR-only.  That keeps it on Dish and only occasionally will it see T-Mobile NR SA for brief periods before going to no service. I also don't have mine band locked beyond that, except that I have some of the unused bands turned off just to try to reduce scan time.  Fortunately, my Dish phone is the one with the MediaTek chipset, so it has NR neighbor cells, and I can usually see n71, n70, n66, and sometimes n29 (market-dependent) through those regardless of which band it's connected to as primary. - Trip
    • dkyeager
      Dish Network/Boost Mobile cell/5G buildout thread

      By dkyeager · Posted

      Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • cooltech6597
      Official Tmobile-Sprint merger discussion thread

      By cooltech6597 · Posted

      Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • 4GHoward
      Official Tmobile-Sprint merger discussion thread

      By 4GHoward · Posted

      This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  

  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...