Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

No band 26 in the normal places I had it with the .15 radio. I did get band 41 while out and then a -122 signal at home that still pulled ~5/.5Mbps.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I don't like the new radio. No LTE at my desk at work now and I lost it completely when I got near a B41 site and it stayed gone until I toggled airplane mode in the parking lot at work.

 

Sent from my Nexus 5 using Tapatalk

Same i'm not a big fan of it so far

 

Sent from my Nexus 5 using Tapatalk

Fortunately it is an easy fix to go back to the .15 radio if you preferred that. I'm going to test drive .13 for a week but I may go back as well.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I want to admit this isn't scientific or anything, but yesterday I took readings at different places on my desk and left post-it notes so I would be able to put the phone in the exact same spot today.  Same tower from the same sector. (Yes, that big of a wireless nerd now... thanks to this site)

Here are my findings:

.15 Radio Spot #1     .23 Radio Spot #1     .13 Radio Spot #1
   B25 - 108-109           B25 - 113-115            B25 - 110-114
   B26 - 101-103              B26 - N/A                B26 - 105-107

.15 Radio Spot #2     .23 Radio Spot #2     .13 Radio Spot #2
   B25 - 107-108           B25 - 113-114            B25 - 112-113
   B26 - 100-103              B26 - N/A                B26 - 105-106

.15 Radio Spot #3     .23 Radio Spot #3      .13 Radio Spot #3
   B25 - 103-104           B25 - 110-111              B25 - 109-112
    B26 - 99-100               B26 - N/A                 B26 - 104-105
 

Sorry if the formatting goes crazy...  Tried putting in an HTML table, but I don't have that option on here?  Worked fine in my Premier thread...

  • Like 5
Link to comment
Share on other sites

I flashed the update last night. Everything seems to work but band 25 LTE reception does seem worse. I used to pick it up at home and haven't seen it yet. Also dropping to 3G at work. I'm not sure how I feel about it yet, I bought the nexus for its LTE reception but I haven't had any data issues yet on the new baseband. As long as data continues to work when I need it I might not go back to .15.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I always found that the older radio, the one that shipped with the initial N5 (think that was 17?) held on to LTE way too long before dropping to 1x/EV.  I would end up in places with hanging on to LTE that wasn't usable and texting would end up not working plus inbound calls would fail.  And this wasn't a CSFB issue.

  • Like 2
Link to comment
Share on other sites

The debug/engineering one doesn't work, I haven't pulled the logcat yet to see what it is doing. The Nexus field app was updated today and that one opens the LTE engineering screen just fine though. My Quickshortcut stopped working so I figure I just need to do a root script on my home screen to fix it.

 

Liking this radio a bit better. The transition to and from B4 from 17 wasn't bad before but I see they've tweaked it a bit better.

I'm afraid to upgrade since I'm on AT&T. I like being able to access Engineering screens on AT&T. Only device I know that does. :td:

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

RSRP (dBm) alone is a pretty useless measure of a modem firmware; there are plenty of other important numbers on the engineering screen too. What really matters is the performance on that firmware.

 

I said this before the 4.4.3 update was released -- my own testing shows that, while the .17 radio shows higher dBm readings on LTE, the .23 radio connects to LTE in less places because of poor fringe performance.

 

That said, I upgraded last night directly from the .23 radio, and I can tell you that the new 2.0.50.1.13 radio is absolutely giving me much better band 26 performance. I previously found it impossible to reliably hand off from site to site while connected to band 26 (the device would drop to eHRPD instead and park there for a long time); now I'm seeing my device idle on band 25 and correctly move to band 26 either when necessary -- either when the cell site tells it to (for capacity) or when approaching the edge of the band 25 cell (for coverage). And I'm actually seeing hand-offs across band 26 sites now.

 

I'm also seeing the device grab onto band 26 in more places than before (for instance, in elevators and parking garages) where it would previously give up and fall back to eHRPD. And on a fringe signal, I'm seeing better speed tests.

 

At home, where I have a good signal on either band, I'm seeing better behavior -- the device will camp out on band 25 while I'm on Wi-Fi, and it will immediately move to band 26 when I disable Wi-Fi. I tested that several times, and it moved after every toggle with no issues. And even at my desk at work, where I get a poor signal, I've been on band 26 all morning and haven't dropped to eHRPD once. Previously the device would move between band 25, band 26, and eHRPD all day in this spot.

 

I'm starting to think some of you just have defective devices.

Link to comment
Share on other sites

I'm afraid to upgrade since I'm on AT&T. I like being able to access Engineering screens on AT&T. Only device I know that does. :td:

 

Robert via Samsung Note 8.0 using Tapatalk Pro

No issues with the upgrade here. Works well. Just use this for the shortcut for now.

 

https://play.google.com/store/apps/details?id=com.cellmapper.nexus5fieldtestmode

  • Like 1
Link to comment
Share on other sites

Anyone having good luck with 0.15 radio on 4.4.3? May flash it soon here. Anyone strongly prefer a different one?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I'm starting to think some of you just have defective devices.

 

I could never get B26 on the .23 radio.  The .15 radio gave me all of the benefits of B26.  The switching between bands was perfect.  Switching from B26 site to B26 site was flawless.

 

The ONLY couple things I didn't like about the .15 modem was that it would tend to stay on B25 a little bit too long, and I couldn't get B41.

 

Going to give this modem a fair chance though.  I will admit that I am pulling in pretty good speeds and useability on fringe signals.  I just wish that the B25 performance was like the .23 radio (which it appears so), while the B26 performance was like the .15 radio.  But you can't always get what you want!  :D

Link to comment
Share on other sites

Hope this doesn't get buried in all of the update discussions, but for those of you that have used Dalvik optimizations and ART... Which do you find provides better battery life?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

No issues with the upgrade here. Works well. Just use this for the shortcut for now.

 

https://play.google.com/store/apps/details?id=com.cellmapper.nexus5fieldtestmode

That's good. I use that app already to access screens. I thought I read that that app doesn't work any longer on AT&T after the update. Thanks for the clarification.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

Hope this doesn't get buried in all of the update discussions, but for those of you that have used Dalvik optimizations and ART... Which do you find provides better battery life?

 

Sent from my Nexus 5 using Tapatalk

 

ART, hands down.

  • Like 1
Link to comment
Share on other sites

I got band 41 on the way to work, as well as band 26 in a couple of spots that had fringe band 25 before.

 

Unfortunately I did have a couple of hand off issues where my n5 dropped all signal and came back on 3g. I'm doing a profile and prl update and will see how it works on the way home.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I am becoming very disappointed with this 'update', after experiencing *working* spark on the m8, I am starting to suspect that the nexus 5 is plagued with some kind of hardware issue on b41. I haven't seen any b41 yet where I can get consistently with the m8.

 

The m8 'just worked', albeit with sometimes odd hand-off behavior.

 

I am also finding myself missing the spinning walmart sign, it made it extremely trivial to see when data was actually transferring.

 

ugh.

Link to comment
Share on other sites

That's good. I use that app already to access screens. I thought I read that that app doesn't work any longer on AT&T after the update. Thanks for the clarification.

 

The app change log indicates that you now must be rooted.  So, have you gotten back to your root(s)?

 

AJ

Link to comment
Share on other sites

I am becoming very disappointed with this 'update', after experiencing *working* spark on the m8, I am starting to suspect that the nexus 5 is plagued with some kind of hardware issue on b41. I haven't seen any b41 yet where I can get consistently with the m8.

 

The m8 'just worked', albeit with sometimes odd hand-off behavior.

 

I am also finding myself missing the spinning walmart sign, it made it extremely trivial to see when data was actually transferring.

 

ugh.

I have had very reliable band 41 connection with my nexus 5 using .15, so it's not a hardware problem. Have you tested the nexus 5 and m8 at the same time in the same location?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

If this was a Spark upgrade you would think it would work well on B41 with the radio it shipped with. I lasted half a day before going back to 0.15.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I agree with the 3G/1xRTT performance being noticeably better. Here at work in southwest Denver, I'm buried in legacy land and have been spending most days with my N5 perpetually hunting for a signal. With the .13 radio, I consistently at least have a data connection, albeit a slow one.

 

Too soon to see much difference at home in Colorado Springs where B25 and B26 are pretty much everywhere.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

The debug/engineering one doesn't work, I haven't pulled the logcat yet to see what it is doing. The Nexus field app was updated today and that one opens the LTE engineering screen just fine though. My Quickshortcut stopped working so I figure I just need to do a root script on my home screen to fix it.

Is SignalCheck granted root access on your device? As others have stated, looks like the FTM update references a change in 4.4.3 that requires root to trigger the shortcut now. I hope to find time to update by the end of this week so I will mess around with it and see what I can do. Most others say its still working in the app but I'm guessing it's a root permissions issue.

 

-Mike

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

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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