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

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their BRS/EBS licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well.  — — — — — Edit: Turns out this is a spectrum swap where T-Mobile is basically giving them DoD spectrum in a bunch of markets in exchange for all of SoniqWave's BRS/EBS. SoniqWave will likely turn around and sell the DoD spectrum to AT&T whenever the FCC removes the 40MHz cap.
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
  • Recently Browsing

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