Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

Excuse? The negativity gets old here. Do you want the update and then have it jack up your phone?

  • Like 3
Link to comment
Share on other sites

I'm not trolled easily jeffcarp. Its an excuse because they should have said so immediately after they pulled the update.

 

That's customer service.

 

Sent from my Nexus 5 using Tapatalk

  • Like 2
Link to comment
Share on other sites

It probably harmed performance on another network. Sprint had no issues with the last iteration they tested. Someone else other than Sprint had to have balked. It may be even something Google discovered themselves.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

  • Like 2
Link to comment
Share on other sites

Transparency.. That's all we wanted (and knew we weren't getting) when they told us for 3-4 days it was rolling out.

 

 

 

Sent from my Nexus 5 using Tapatalk

Whoa don't start talking crazy now

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

This is bull. I can't stand it anymore that I can't use my phone at this place because there is no signal and my WiFi constantly locks up.

 

I really tried not to complain but this update is really needed for me because its unusable. I hoped before 1st quarter (April 1st), then the 14th, 21st, and now we don't know when. It could be the 24th but who knows... It could be may 15th.

 

 

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

I agree. But there is something that I noticed that can make the G2 battery life seem not that great its called band 41.

My wife and I both have the G2. I never let my phone run until it shuts off. My wife does all the time, though. Last week I went over 100 hours on battery and last night I went 57 hours before charging. My wife generally gets only 18-20 hours on her battery. Not very scientific, but I keep telling her that letting it die is a bad idea and overall it seems even when I use mine really hard it lasts longer than hers.

Link to comment
Share on other sites

I agree. But there is something that I noticed that can make the G2 battery life seem not that great its called band 41.

 

Imagine that! :)  I wonder if the "issues" with the OTA enabling Spark was the high battery drain on our relatively small Nexus 5 battery?  Anyone know how much, if any, battery life is affected in any other Spark enabled phones in Spark markets?  

Link to comment
Share on other sites

Imagine that! :)  I wonder if the "issues" with the OTA enabling Spark was the high battery drain on our relatively small Nexus 5 battery?  Anyone know how much, if any, battery life is affected in any other Spark enabled phones in Spark markets?  

Battery life is perfectly fine on this phone and my girls G2 here in NYC

  • Like 1
Link to comment
Share on other sites

This is bull. I can't stand it anymore that I can't use my phone at this place because there is no signal and my WiFi constantly locks up.

 

I really tried not to complain but this update is really needed for me because its unusable. I hoped before 1st quarter (April 1st), then the 14th, 21st, and now we don't know when. It could be the 24th but who knows... It could be may 15th.

 

 

 

Sent from my Nexus 5 using Tapatalk

 

Obviously, you didn't read back the last few pages and seen my post here. So let me repost it for you.

 

We're going to put this thread on ice for a few hours. You all can continue your rants where they're beneficial to you and S4GRU:

 

https://community.sprint.com/baw/community/buzzaboutwireless/phones-and-devices/lg/nexus-5

 

 

You folks have 3 options: Either you can move your rants to Sprint to complain about the Nexus 5 update, move on to the next subject or you can take a vacation. I hear Bandlandia is nice this time of year. Last chance.

  • Like 7
Link to comment
Share on other sites

My phone doesn't pickup band 26 like some have said it will. Is 26 a guarantee without the update, and the band enabled? Or do we still not know. I'm stock with the .23 radio

 

Sent from my Nexus 5

Link to comment
Share on other sites

Or you can put the person on ice.

 

Sent from my Nexus 5 using Tapatalk

 

Hence option #3. Vacation.

Link to comment
Share on other sites

I've had good performance overall with .15, but not much over .17 but I'm not in a spark area. I would hope that generally at least where I am in a Samsung market the csfb issues have largely been mitigated.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

My phone doesn't pickup band 26 like some have said it will. Is 26 a guarantee without the update, and the band enabled? Or do we still not know. I'm stock with the .23 radio

 

Sent from my Nexus 5

Running the 23 radio and it was switching to B26 by itself. I did check to see if the band was enabled and it was along with B41.

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

    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
    • So how does this whole direct to satellite thing fit in with the way it works now? Carriers spend billions for licenses for specific areas. So now T-Mobile can offer service direct to customers without having a Terrestrial license first?
  • Recently Browsing

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