Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

We talking sprint here. BTW I run my on T-Mobile occasionally and it just stays in the - 110 lte signal range. Sprint beats T-Mobile signal wise in my city hands down.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Just got the update via OTA... 2.5 MB install?  Other than a new radio, what does it fix or new features?

Security fix for openssl and one other general fix. A few changed proprietary blobs, but we can't find out what changed in those.

  • Like 1
Link to comment
Share on other sites

Um so has anyone had texts not come through?  So the phone will be on LTE, but no texts come through, it takes an Airplane cycle or restart and then all the texts flood in.

 

Not sure what's going on.  It's not an ecsfb issue

Link to comment
Share on other sites

Um so has anyone had texts not come through? So the phone will be on LTE, but no texts come through, it takes an Airplane cycle or restart and then all the texts flood in.

 

Not sure what's going on. It's not an ecsfb issue

Text or hangout?

 

Sent from my LG-LS980 using Tapatalk

Link to comment
Share on other sites

I will say, that at first, QPST did not list any ports let alone the port my Nexus was connected on.  If that is the case, dont worry.  Simply click Add port to add it manually and then once you do that it will show up and you can continue on with the steps just the same.

 

I finally just got around to flashing my N5 with QPST and wanted to mention something that might help others in the future..

 

On the 'Ports' screen in QPST Configuration, not only did I have nothing listed, but when I clicked "Add New Port.." the proper one was not showing. I had to uncheck the "Show Serial and USB/QC Diagnostic ports only" option, which was enabled by default. Some additional ports will appear, and the one to manually add will be listed as "USB/Unknown - (LGE AndroidNet USB Serial Port, xxxx)". This is with QPST 2.7 Build 411.

 

-Mike

  • Like 2
Link to comment
Share on other sites

So the flash-all script lists:

 

./fastboot -w update image-hammerhead-ktu84m.zip

 

which is actually (images):

system, userdata, boot, recovery, cache

 

correct? My real question is which ones are required to update to 4.4.4, can I mix and match from 4.4.3 or is it best to just do them all?

 

I guess it's worth noting that doing a diff on the two versions shows that only recovery.img and system.img are different - so are those the only two that need flashed?

Edited by AgathosAnthropos
Link to comment
Share on other sites

So the flash-all script lists:

 

./fastboot -w update image-hammerhead-ktu84m.zip

 

which is actually (images):

system, userdata, boot, recovery, cache

 

correct?  My real question is which ones are required to update to 4.4.4, can I mix and match from 4.4.3 or is it best to just do them all?

 

I just updated from 4.4.2 to 4.4.4, and only flashed the radio and system partitions. Flashing userdata will wipe out your data, and the bootloader has not changed in the last few updates so it is unnecessary. Flashing recovery will wipe out TWRP or whatever custom recovery you might have installed.

 

You can mix and match whatever you want; many people are using older radios with everything else updated. The system partition is the actual OS.

 

-Mike

Link to comment
Share on other sites

Received OTA today, upon restart it did not connect to Sprint until I powered off and on, airplane mode toggle did nothing. Once I restarted, noticed stronger LTE signal in the city (Washington DC) but weaker signal at home (suburbs). Will have to investigate whether this is related to tower work or not, signal check is reporting I'm connecting to towers miles away.

Link to comment
Share on other sites

So I've been running .15 again since about two days after the new radio came out. The past two days or so I hadn't been able to get my n5 to pick up 3g at all, it just flopped back and forth between 1xrtt and 1x800. I flashed the newest radio about a minute ago and instantaneous -88dbm Ehrpd signal upon reboot. Anyone else notice issues like this before with .15? Its going to be a pain reflashing every time I leave and come home lol.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I didn't see a dedicated thread for my question yet. Does anyone know the details of Sprint's announced voice over WiFi capability and whether the Nexus 5 will be supported?

Link to comment
Share on other sites

In the press release that announced international calling and SMS over WiFi coming in two weeks, they were silent on what devices would support this. Curious what to expect.

Link to comment
Share on other sites

So I've been running .15 again since about two days after the new radio came out. The past two days or so I hadn't been able to get my n5 to pick up 3g at all, it just flopped back and forth between 1xrtt and 1x800. I flashed the newest radio about a minute ago and instantaneous -88dbm Ehrpd signal upon reboot. Anyone else notice issues like this before with .15? Its going to be a pain reflashing every time I leave and come home lol.

 

Sent from my Nexus 5 using Tapatalk

 

I ended up flashing back to the .15 radio a few days ago for the extra coverage (mainly the 5-8 dBm boost on B26).  I don't have anymore issues connecting to eHRPD on the .15 radio than I do on the newest .16 radio.

Link to comment
Share on other sites

I ended up flashing back to the .15 radio a few days ago for the extra coverage (mainly the 5-8 dBm boost on B26). I don't have anymore issues connecting to eHRPD on the .15 radio than I do on the newest .16 radio.

Yeah its been spotty with the new radio now...so I'm thinking maybe they're finally doing the rest of the upgrades to the two towers closest to me.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I didn't see a dedicated thread for my question yet. Does anyone know the details of Sprint's announced voice over WiFi capability and whether the Nexus 5 will be supported?

 

Wifi calling requires software modifications to the device. Since Sprint cannot modify the software of a Nexus device (no one can) then it will likely never get wifi calling. 

Link to comment
Share on other sites

Wifi calling requires software modifications to the device. Since Sprint cannot modify the software of a Nexus device (no one can) then it will likely never get wifi calling. 

 

If you had asked me a year ago if Apple would ever support carrier-specific Wi-Fi calling on iPhone, I would have said you were crazy. Let's hope Google follows suit.

Link to comment
Share on other sites

Why couldn't it just be an app?

 

Wifi calling requires software modifications to the device. Since Sprint cannot modify the software of a Nexus device (no one can) then it will likely never get wifi calling.

  • Like 1
Link to comment
Share on other sites

Nexus 5 developer images for Android "L" come tomorrow! :)

I think it is actually today! Can't wait to begin implementing material design into my applications.

 

Edit: Actually it's the SDK that goes live today. My bad, got too excited lol.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

nexus has had 'wifi' calling built in for some time...

 

dialer > settings > internet call settings > accounts > receive incoming calls + add sip account

 

All sprint has to do is enable some type of sip service.

  • Like 2
Link to comment
Share on other sites

aha6umeq.jpg

Finally got my OTA. I didn't even know it was downloading until I saw the notification saying I could install it (I didn't know what it was until I checked lol).

 

Sent from my Nexus 5 using Tapatalk

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