Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

I've never seen a tower issue like that. How long have you been having problems?

 

Sent from my Nexus 7 using Tapatalk

Since I received the phone. As soon as I leave the local area it works fine. It's a shentel tower that just isn't right. I went to the next county, a Sprint corporate market, to the closest corporate store and it works flawlessly, perfectly. There it jumps back and forth instantly from LTE to 3g and back.

 

But here there are all sorts of delays and it gets hung up... missed calls, can't dial out... major network issues trying to switch. It will sit happily on LTE and never ring. Complained at 2 Sprint stores, online chat... no resolution yet. Just hoping that the b26/b41 updates will provide a fix.

 

Sent from my SPH-L710 using Tapatalk

Link to comment
Share on other sites

The release on the 23rd was a mysterious source rumor, and the retraction is a rumor. There's still no concrete evidence about the update. All we have are the hopes and dreams of s4gru members. Well that, and the countless "click bait" articles that show up every few hours.

 

Sent from my Nexus 5

Releasing on the Friday of a 3 day weekend did seem odd.

 

Sent from Nexus 5

  • Like 1
Link to comment
Share on other sites

The release on the 23rd was a mysterious source rumor, and the retraction is a rumor. There's still no concrete evidence about the update. All we have are the hopes and dreams of s4gru members. Well that, and the countless "click bait" articles that show up every few hours.

 

Sent from my Nexus 5

The release will not be this week. Or next.

 

Sent from my Nexus 5

Link to comment
Share on other sites

The release will not be this week. Or next.

 

Sent from my Nexus 5

 

:cry: But...but...  I want it now!  :lol:

 

Honestly, I don't mind the wait.  There isn't any B41 around here, and since I was able to get B26 working with the .15 radio I don't have any complaints.  I am a little bit scared that the RF performance might not be as good with the update since they went a little backwards with the .23 radio. 

Link to comment
Share on other sites

It's soon. But not this week or next. Sorry.

 

Sent from my Nexus 5

I appreciate the honesty.  As much have mentioned, this site is a double edged sword.  We stay ahead of the curve and therefore we find out information before others.  Sometimes it is for the best, sometimes it is for the worst.  Have we confirmed that it wasn't due to Sprint Spark?  I believe it was mentioned that the radios were not the issue.

 

Thanks again.

Link to comment
Share on other sites

No Band 41 here either. Or Band 26. Or even Band 25! :P

 

Robert via Samsung Note 8.0 using Tapatalk Pro

  • Like 4
Link to comment
Share on other sites

It's soon. But not this week or next. Sorry.

Sent from my Nexus 5

How do you know? Man..that sucks though. When you say "soon," how is "soon being defined? Lol...inquiring minds want, nay NEED, to know!

 

P.s..that lone straggling tower next to my complex is ironically clearly now 4G complete as of yesterday, apparently. After a full year it's now blasting b25 right at my back door giving me a constant LTE connection with a very healthy -81 dBm signal level. #prayersanswered

  • Like 2
Link to comment
Share on other sites

It's soon. But not this week or next. Sorry.

 

Sent from my Nexus 5

 

Heh, you and I have different definitions of soon then.

 

Unless Google doesn't have a larger upgrade essentially ready to go for I/O, it's going to be strange having 4.4.3 and then whatever the next version is closely together, given the gap between 4.4.2 and 4.4.3.

Link to comment
Share on other sites

As much as I love Android, the outstanding issues with the LG Nexus 5 have me seriously questioning my loyalty. Why is it taking so long to release a maintenance release for problems dating back to November?

 

I'm beginning to think these "Android Silver" rumors are true and Google is already beginning to abandon the Nexus program.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Someone is to blame for the Nexus being so badly delayed, and it's a carrier that uses the D820. I know who to blame. It's AT&T! I bet they are trying to officially support the Nexus 5.

 

(Pure speculation. I'm just wanting to blame AT&T for everything)

 

 

Sent from Josh's iPhone 5S using Tapatalk 2

Link to comment
Share on other sites

Someone is to blame for the Nexus being so badly delayed, and it's a carrier that uses the D820. I know who to blame. It's AT&T! I bet they are trying to officially support the Nexus 5.

 

(Pure speculation. I'm just wanting to blame AT&T for everything)

 

 

Sent from Josh's iPhone 5S using Tapatalk 2

It works fine on the latest radio, I watch it go between band 4 and 17 with no issues. No texting or calling issues even on newly launched sites and/or bands. Must be them on that new test radio right? ;)

 

All in all, Google hasn't said anything about the delay or release so anything else is consider a rumor to me.

Link to comment
Share on other sites

Not to pat my own back, but I posited that they may have needed to go back to square one with LTE/radio configs.

 

I hope this doesn't jeopardize future multi carrier phones.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Not to pat my own back, but I posited that they may have needed to go back to square one with LTE/radio configs.

 

I hope this doesn't jeopardize future multi carrier phones.

 

Sent from my Nexus 5 using Tapatalk

 

Don't break your arm and it could be anything else.  We just don't know.

Link to comment
Share on other sites

I appreciate the honesty. As much have mentioned, this site is a double edged sword. We stay ahead of the curve and therefore we find out information before others. Sometimes it is for the best, sometimes it is for the worst. Have we confirmed that it wasn't due to Sprint Spark? I believe it was mentioned that the radios were not the issue.

 

Thanks again.

There have been issues with multiple carriers, including Sprint.

 

If the information is correct (I trust it) and there aren't any more setbacks, we may be looking at something around 14 days.

 

Sent from my Nexus 5

  • Like 7
Link to comment
Share on other sites

How do you know? Man..that sucks though. When you say "soon," how is "soon being defined? Lol...inquiring minds want, nay NEED, to know!

 

P.s..that lone straggling tower next to my complex is ironically clearly now 4G complete as of yesterday, apparently. After a full year it's now blasting b25 right at my back door giving me a constant LTE connection with a very healthy -81 dBm signal level. #prayersanswered

Good to hear!

 

Sent from my Nexus 5

Link to comment
Share on other sites

Don't think so. That issue is only with root app. Google doesn't care about those as they don't support root apps anyway.

 

Sent from my Nexus 5 using Tapatalk

 

I find it hard to imagine they don't care at all about root.  There's a huge community around rooting, and while they might not support it directly, they would likely lose a lot of support and take a big hit in negative publicity from the tech websites.  Wouldn't be a good idea for them to all of the sudden prevent root.

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