SashilKapur

I still have not received a shipping notification for my 64GB Aluminum.

 

Sent from my Nexus 5 using Tapatalk

It's simply supply and demand.  The aluminum 32g was under the least demand, so it ships fastest.  Use the cloud people, use the cloud! 

It's surprising about the 128gb frosts.  I preordered mine only nine days ago and I got word today that it is shipping (albeit I ordered 32gb aluminum).  Yes, I was quite surprised to get the shipping notification as I was expecting mid-November.

I just replaced the battery on my N5 with an OEM battery.  While it's definitely an improvement, it's not as marked as others are stating on this thread.  It still doesn't last the whole day, but then again, it rarely did when it was new.  It was definitely worth the $15.

My GPS is somewhat flaky as well.  Sometimes it just stops working and I have to power cycle the handset.  Sometimes, it stops working for a few seconds.

While I love the N5, I'm ready to ditch it as soon as Bullhead is available this fall.  I'd love a better battery, GPS, and camera.

Anyone have a tri-band device yet? I want to see what's going on with TD-LTE with respect to to the Chicago market

I have an N5 but have been lazy obtaining my MSL to change my band priorities.

I think most of us have been surprised at how quickly speeds have gone down here as usage has increased. But Sprint is currently limited to only 10 MHz of LTE spectrum in the Chicago market, where the other guys all have more. When USCC is gone, I believe Sprint will get another 30 MHz of PCS spectrum, and I think the Nextel shutdown yielded at least 10 MHz of 800 SMR, thus at least 40 MHz of new capacity. I don't know how much of that will be re-farmed into LTE, but a lot of it will be. I am not counting the former Clearwire spectrum, as deployment is going to be too sparse to be useful for quite a while.

 

In any event, within a few months, Sprint's capacity issues in Chicagoland will take a dramatic turn for the better.

 

Now if they'd just finish my backhaul and fix the SNR . . .

I remember how much I drooled when I first heard about that deal way back when.  Now I am remembering the reason I was drooling.  Capacity.

For clarification it is 20MHz of spectrum is most midwest areas concerned except for 10 Mhz for St. Louis.

Also I just read that the USCC network was to be closed Oct 31st.

Your screen shots show capacity limitations, which are becoming more common as more people get on LTE in Chicagoland. This will improve when Sprint can activate 1 or more LTE carriers on USCC spectrum in January, and when 800 LTE becomes available starting (hopefully) any day now (although you will need an iPhone 5c or 5s or a tri-band phone or hotspot to see 800 LTE). And it's probably not backhaul related, as Sprint won't turn on LTE until either fiber or microwave backhaul is in service, as both mhammett and I know all too well from our experience in Dekalb and Crystal Lake.

 

Other people are reporting signal-to-noise ratios very close to zero, even with strong RSRPs: This is likely caused by something electrical or electronic actually interfering with the LTE signal, and likely has little or nothing to do with traffic or capacity.

 

That's why I asked in an earlier post if anyone in the city itself had seen SNR improvements, or if things were just as bad. Certainly Sprint's network engineers are completely aware of the problem, and if it is caused by another carrier (either TMO or USCC), they would know who is causing the problem, and Sprint would contact the other carrier, and the problem would go away quickly, before the hypothetical other carrier faced fines and sanctions from the FCC.

 

(Your screen shots also show that Sensorly routes its speed tests through France or Uzbekhistan or someplace like that, hence the ridiculous pings.)

Ahh, I keep equating capacity and backhaul when they in fact are not equal.  I should know better.

I think I was fooled by the fact that I wasn't expecting capacity issues this quickly after NV was launched in Chicago.  Pretty naive.  Can't wait for that USCC spectrum to kick in.

What you are seeing is just a capacity issue. 

Which is what I was thinking.  Of course I noticed the much healthier upload rate.

So basically it all comes back around to backhaul.  As it always has.  Stoopid temporary backhaul.

Are we absolutely sure this is a SNR issue? I haven't been looking at it before but when I look now, I'm getting a healthy 30dB in Humboldt Park. However my speed tests are still pretty bad. Not unusable though. Also, I haven't been having issues with dropped calls or call quality.

Sent from my Nexus 5 using Tapatalk

I also have been getting quite poor LTE performance around the city for the last month or two. Are we saying this is only a city thing? It appears as though there are some suburban issues too such as Oakbrook. FWIW I was out at my parents' in Hoffman Estates and the LTE was flowing like the nectar it is:

Sent from my Nexus 5 using Tapatalk

In OS X, Terminal is the UNIX command line app.

 

AJ

Of course.  I'm running windows 7, should have realized that.

Just to make sure, the sim we need is the 3FF model, right?

Correct

I had that problem earlier this afternoon.  But once I opened a Terminal window, navigated to the appropriate directory, and typed a valid command, I was then prompted for the RSA key.

 

AJ

By terminal window do you just mean the command prompt?

Everyone else able to unlock their bootloaders?

When I plug in USB to my laptop, it does not ask me for my computer's RSA key.  I've tried all sorts of things including manually deleting adb_key, adb kill-server, plugging and unplugging countless times.  I think the problem is the USB driver, device manager says I have no drivers installed for Nexus 5.

The Google USB Driver is for Windows only and provides the necessary drivers for the following devices:

ADP1 / T-Mobile G1*

ADP2 / Google Ion / T-Mobile myTouch 3G*

Verizon Droid*

Nexus One

Nexus S

Nexus 4

Nexus 7

Nexus 10

The drivers are included in the android SDK: http://developer.android.com/sdk/index.html

I know I went through all of that.  Apparently the N5 drivers are not included right now, I found some others who were having the same problem.  I went into device manager and tried updating manually and windows said nope.

I finally got mine activated through chat and seem to have no problems connecting to LTE.  I have not been out and about so I will report on that tomorrow.  I have not looked at the engineering screens because I spent some hours trying to unlock the bootloader without success.  I can't install the google USB drivers for some reason.  Anyone else have this problem?

32GB black

I just read that the 32gb N5 will not be allowed on TEP at Sprint.  What are people doing for insurance? None?

No insurance for me.  Never needed it once in eleven years.  Cancelled it for good last year.  Also if you can afford to replace your device, insurance is useless.  Thirdly, this device is relatively inexpensive.  What's the deductible for TEP, $200?  $150?  Not worth it in my mind.

Mine changed from 3-4 weeks to 2-3 weeks this morning.

I was a 2-3 weeker when I ordered, yet it is arriving today.  That's over two weeks early.  Hopefully that will be true for everyone else.

My 32GB black as well as my spanking new SIM will be arriving sometime this morning.  Thank goodness the MEID issue was resolved.

I don't understand how people are still having problems obtaining the SIMs.  We have already established that the international chat works like a charm.

Just used the chat to order the SIM, took all of 60 seconds, piece of cake.

Just got my shipping confirmation also even though it said it would not ship until November 15.

 

Google learned their lessons from the Nexus 4 launch. They were probably waiting for the LG to manufacture enough units before release.

I was told mine would not ship until Nov 22nd but I also got a shipping confirmation email today.  Woohoo!  Guess I gotta get off my ass and get that SIM pronto.

I finally got approval from the boss(my wife) to spend this much money on a phone. Has anyone ordered it since the timeframe changed to 3-4 weeks? 

Just did, see above.  Oh well.  If the boss makes me return it, I have extra time to put up an argument!

"Leaves warehouse 11/22/13."  

Hold down the power button along with the vol down button to reset if it freezes or won't turn back on. It's been happening to me more often in the past few months for some reason.

In the same vein, you guys know how the power saver feature works? I tried it one day (when I had Google Now on btw) and my phone died in 4-5 hours. I was so pissed off. Maybe it was just Google Now but regardless, I haven't turned on power saver since.

I also think Google Now is pretty spiffy. I turn it on now and then, esp when I know I will be having a reliable signal.