-
Posts
1,846 -
Joined
-
Last visited
Content Type
Profiles
Blogs
Articles
Media Demo
Gallery
Downloads
Events
Forums
Posts posted by SpenceSouth
-
-
Actually on second glance there is 1x800 but the Ec/Lo is ridiculously high causing the Nexus to not grab it. Very odd.
Sent from my Nexus 5 using Tapatalk
-
Well I have picked up several 1x800 towers on the drive over, but no 1x800 or B26 off of the two Belleview towers. Bummer lol. Only able to hold a -104 to -106dbm 1x1900 signal where I am.
Sent from my Nexus 5 using Tapatalk
-
I have a site that's about two miles from my house I'm picking up 1x 800 but the signal is about 3db better from the same site as 1x 1900.
Could there be too much down tilt on it at the moment?
Very likely but it could be by design to reduce interference. I think the truth of the matter is that we really shouldn't be observing a wildly stronger 1x800 signal unless we are in an area that is really needing it. Like rural areas with distant tower placings. Or perhaps inside concrete buildings.
I don't know the technical details behind 1x interference but it makes sense that Sprint would intentionally hold back on some of 1x800's potential range to limit interference with adjacent sites that are spaced for 1x1900.
In urban areas like Jax I think that the only advantage we will regularly encounter will be better building penetration.
Feel free to agree or disagree. Just throwing something out there.
Sent from my Nexus 5 using Tapatalk
-
1
-
-
I believe all of those people left a longgggg time ago to tmobile . Lol
Sent from my iPhone 5s using Tapatalk
Lol
Sent from my Nexus 5 using Tapatalk
-
Best sprint band 26 speed test
Sent from my Nexus 5 using Tapatalk
I'm going to be in the area this weekend and am really hoping to have some B26 on the Belleview site. My parents house is in the void between two sites and I always get cut off from the world when I am there lol. With any luck I'll have some coverage now!
Sent from my Nexus 5 using Tapatalk
-
Hmmm I've been working a lot in the area and was hoping for some local testers with Android SVLTE devices.
Sent from my Nexus 5 using Tapatalk
-
Interesting theory.. certainly seems plausible to me, and would explain why some of us are experiencing more of a problem than others. If you are correct, then I would expect the problem to disappear when disabling Band 26. I just did that to see if it changes anything.. I'll keep an eye on it.
-Mike
I believe someone in the Tampa thread had the same assertion and disabling B26 worked wonders for him.
Sent from my Nexus 5 using Tapatalk
-
Any of you guys sporting any non-triband devices?
Sent from my Nexus 5 using Tapatalk
-
Hey my -110dbm to -125dbm signals are still pulling me at least a few mb's down so I'm happy with them until b26 shows up more in my area(or I move to an area that has it). I flash back and forth depending on if I'm at home or going out and about lol.
Sent from my Nexus 5 using Tapatalk
I concur with this... It works better for me. Plain and simple.
Sent from my Nexus 5 using Tapatalk
-
Thinking of switching from the iPhone 5s, want to switchback to android. Which device should I get HTC One (M7), HTC One (M8), LG G2, Moto X or Nexus 5? I live in a rural/fringe area, so signal is important
Sent from my iPhone using Tapatalk
You should limit your selection to just the tri-band devices of the group to get the best experience overall. If you are in a fringe area you will greatly benefit when Band 26 is rolled out to your area, if it isn't already, so you don't want to miss out on that.
Between the HTC One (M8), LG G2, and Nexus 5 you really couldn't go wrong with any of them. I really like HTC's Sense and what they have done with their phones, but the camera can be a disappointment in less than favorable circumstances. The G2 gets raving reviews from many members of this site, but personally I find the UI to be quite unattractive. If signal is important above all else, then your choice is the Nexus 5 hands down. It is the current RF performances champ.
-
1
-
-
How are you flashing the radio.img? Can you flash it using a custom recovery (I use CWM), or do you have a flashable .zip file?
Using one of the flash able zips posted on XDA. I keep all of them available go me to flash as needed.
Sent from my Nexus 5 using Tapatalk
-
Well I am on .15 again lol. My phone refused to drop the -130dBm B41 signal in Publix and wasn't usable. Flashed .15 in store and was on a great B25 signal.
Sent from my Nexus 5 using Tapatalk
-
Does the nexus 5 have the spark logo like the other tri band phones do when they connect to spark?
Thankfully, it does not.
Sent from my Nexus 5 using Tapatalk
-
Has anyone successfully had a sprint spark connection and experienced spark speeds yet on a nexus 5?
Many have, many times over.
Sent from my Nexus 5 using Tapatalk
-
My priorities are B25 - 1, B26 - 2, B41 - 3. This is the default on 4.4.3, I haven't touched these values.
What did you set yours at in the "edit" menu to get that result?
Set B25 to 0 and everything else to 1.
Sent from my Nexus 5 using Tapatalk
-
My experience does not support these conclusions. While I was running .15 for a while before 4.4.3 dropped, I did load up .23 for a couple of days in anticipation of 4.4.3, and I have run that radio in the past. On .23, I had a fine Band 25 connection at my office and in the downtown area (dense urban). I was connecting as expected to all accepted and live band 25 towers. However, with .13, as soon as I enter downtown, my phone drops to 3G and camps there, even though I am around several active towers. For example, right now I am sitting in my office next to 4 live towers, and I am camped on 3G. If I toggle airplane mode, I will connect to LTE, but after about 2 to 30 minutes, my phone switches back over to 3G and will not move off it unless I toggle airplane mode again.
In the suburban area, less dense, .13 is behaving just like .23 on Band 25.
As for Band 41 and Band 26, I have been able to connect to Band 26, but my phone has yet to hold on to a Band 41 connection on .13. I sat underneath a known active band 41 tower for 15 minutes but the phone would not connect to Band 41, even with an airplane toggle (it sat on Band 25).
I would expect Sprint to get complaints from unwitting Nexus 5 users, as this radio has completely nuked my Band 25 connection in the downtown area. I went from LTE full time on .23 to 3G full time on .13.
By the way, did a factory wipe and re-install; that did not change the problem.
Opposite experience here. Mine holds onto B41 far longer than I would like it to. I noticed on my run this morning that once I was a mile and a half away from the tower the .13 radio would still hold a very weak B41 signal. Normally I get switched over to a stronger B25 signal.
Are your band preferences updated in the *#*#DATA#*#* menu? I keep mine at B25- 3 B26- 1 B41- 2.
Sent from my Nexus 5 using Tapatalk
-
Yeah, that is just it. Even with the radio performing worse than before, it is still pretty much on par or a little bit better than most devices. We were just spoiled before. I would say with the new .13 radio the N5 is about on par with the G2 for B25 and B26. No B41 around here for me to test, but from what I have heard the G2 beats the N5 pretty easily. Unless we get a new radio at some point, I will probably re-activate my G2 once B41 starts popping up around here.
Still nice to be able to easily go back to the .15 radio if I am in a dead spot. Takes a minute and then I have a useable signal if needed. In my testing, B26 on the .13 radio is pretty much equal to B25 on the .15 radio!
I said this before, but I wish they would've been able to keep B25 performance around where it is (and was on the .23 radio) and also have kept B26 performance where it was on the .15 radio. Would've been an absolute beast of a performer.
I keep all the radio zips on my phone just for that reason. There don't seem to be any drawbacks to .15 in a eCSFB matured area so I imagine I'll end up back on that before long.
Sent from my Nexus 5 using Tapatalk
-
there are 4 or 5 that need flashed via fastboot from the factory image;
bootloader-hammerhead.img
(reboot bootloader)
radio-hammerhead.img
(reboot bootloader)
(then inside the image-hammerhead zip)
boot.img
system.img
optionally
recovery.img (if you want the stock recovery)
fastboot erase cache
fastboot format cache
if you did did not get all 5 of those, then you will not be able to take the next OTA (differential update), and will have to again fastboot flash all the individual images.
if you read the update-all.bat file, its very apparent how to do it, just skip the cache/userdata/recovery as needed.
Pretty sure it is the same bootloader that was on 4.4.2. You shouldn't need to flash it.
Sent from my Nexus 5 using Tapatalk
-
I have yet to see the OTA update.zip or an untouched unrooted stock flashable zip go up yet, so the ROM you flashed from XDA was most likely Pre-rooted, so you didn't have to do anything.
TWRP will reinstall root if it notices that you lose it after a flash, so the zip probably didn't include it. TWRP even restored my root and I flashed via fastboot.
Sent from my Nexus 5 using Tapatalk
-
Looks like MX Player is another 4.4.3 casualty.
Sent from my Nexus 5 using Tapatalk -
So I was bored. My boredom could turn into gain. What I'm going to describe may tick some peeps off but in the end open up maybe a way to get back the voice/data centric options and LTE band priority selection.
I performed the permanent SIM unlock as described on another site. I was successful in unlocking my phone not only for international GSM service but also domestic GSM service. I have an active AT&T prepay SIM and can use the Sprint LS980 phone on AT&T in the states all day long, make and receive phone calls on that number, send texts and even have HSPA+ data. The reason I did this is irrelevant.
However, in while performing this hack, it requires editing a build.prop string. I went as far to do the hack on a custom ROM which I lost the ability of using 5689#*980# to access the IOT menu that was crippled in the ZVC update. Guess what, when a certain build.prop entry is changed which tells the handset what carrier it identifies with, the items in the IOT menu change. In custom ROM's the IOT menu is accessed with 277634#*#. With the build.prop identified as OPEN instead of SPR (sprint), a lot of options presented including the ability to select LTE bands. So I learned that the items that show in the IOT menu are somehow enabled based on the RO.TARGET.OPERATOR string. In the case of being set to OPEN, I could select band 1, 2, 3, 4, 5, 7, 8, 17, 20 or 40. No band 25, 26 or 41 but I have inclination that if the right conditions were set that those bands would present.
I'm posting this on XDA as well. Anyone that's in to the inner workings of Android, want to take a crack at getting access to the old IOT settings from within the ZVC/KK ROMs?
I'd like to follow this. Post the link when you post it on XDA
Sent from my Nexus 5 using Tapatalk
-
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
-
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
-
I used to access the LTE engineering screen with the nexus 5 field test app, but it doesn't seem to be working after the update... Can anyone else verify?
Sent from my Nexus 5 using Tapatalk
Works fine here.
Sent from my Nexus 5 using Tapatalk
Network Vision/LTE - Jacksonville Market (including Gainesville/St. Augustine/Ocala)
in Markets
Posted
Probably a mile and a half from the nearest one. I think poor downtilt is to blame, especially when the 1x800 is worse than the 1x1900.
Sent from my Nexus 5 using Tapatalk