AgathosAnthropos

Yup, that thanks

Thanks. To be honest, my original idea was to just use your exported database and generate a Google Map of the data, but I figured I wouldn't be allowed to do such a thing via Google Play (read in another app's DB, even if it's been exported to a shared directory) so it has since expanded into tracking the data myself. The biggest coding question I'll likely have is band identification issues pre availability of EARFCN in the API's. I'm a software engineer by trade (though I don't use or particularly like Java); my biggest issue thus far has been getting enrolled in Google Play developer console and doing Beta releases.

Does it give you any kind of error message? Looking at my developer console it appears some of the others have been able to download. I've tried removing and re-adding you to the Beta list, so try again (may have to opt-in again, not sure). Sorry for the issues but this is my first app on Google Play.

It's not on play because I haven't fully released it from beta to production.

SigMapper.

Hey all, I know I know, you all have SCP, LTE Discovery, CellMapper, etc. but I've been working on my own signal status Android App for the past bit now. I've "published" it to Google play (it's free) but I'm the only one who's ever used it. I don't intend to ever make money on it but if anyone is interested, feel free to PM me and I'll invite you to the beta group. It does personal (not crowd sourced) signal mapping, doesn't use a lot of data, and hopefully correctly identifies band information.

If it is S8 the limitless/infinite everyone is referring to could be the "infinity display" Samsung is using to describe their design. http://www.samsung.com/global/galaxy/galaxy-s8/design/

But, but, my e-peen... Anyway it was mostly a joke. I get the idea, massive capacity upgrade is a massive win for normal use cases, so I'm far from complaining.

Is Sprint going to start zero-rating speed tests or are people going to be deprioritized after a single 20+GB @700+Mbps speed test?

Why not just aggregate B41 as an SCC to 25(or even 26) as a means to get people off those lower frequencies quicker. I know this also requires new handsets but is FDD/TDD CA of 25/41 something they are still possibly looking at.

Just glancing back at my SCP logs I have multiple 57XXX4X from at least the last week of October for the St. Louis area, implying to me that it's at least rolling out in this market. Since I've switched back and forth between OG Nexus 5 and Nexus 5X in that timeframe I don't see all right now but I can add the info to the premiere thread later if interested in tracking.

In Festus MO (I believe NSN market) eating breakfast with my daughter I noticed this...

Not sure if anything like this is elsewhere but I saw this on Slashdot, and having a Nexus 5X and a couple of cables for A-to-C I was intrigued. Thought others might be interested: http://hardware.slashdot.org/story/16/02/05/2241255/some-reversible-usb-c-cablesadapters-could-cause-irreversible-damage

Just a heads up, I was having the same issue after flashing in 6.0.1 MMB29K (and going straight to rooted), and just updated to 6.0.1 MMB29P - unrooted and the camera started working again. Rooted (flashed boot img and twrp recovery img and supersu), and it was broken again. Going back to base (non-rooted/stock) MMB29P and it seems to be working again - guess I'll stick with unrooted until I can play with it more. Which version are you on? Maybe trying updating to latest again?

Can they be configured from a LTE Relay to be a eNB if they ever do get dedicated backhaul? It seems like a great short-term solution to increase bps/Hz due to getting better SINR on the cell edge, but in the long term if it is in a high-enough traffic area it seems like it would make sense to make them dedicated eNB. Although I don't know how necessary because relaying 2 3x20MHz carriers seems like plenty of capacity (in lieu of adding some number of carriers). Also, would the initial solution only need power - since the bandwidth for Tx/Rx comes from the current macro network - making it much easier to deploy than a traditional micro/pico/femto cell?

I can't wait to be deprioritized for using too much bandwidth on my home internet connection.

Usability, even during peak hours (also, assuming all from same location), would have been my third option... But anything under 100M is hardly usable.

The max or the variability?

Order doesn't matter. As long as you save Return of the How It Should Have Ended (http://www.howitshouldhaveended.com) until you've seen them all.

Sorry, I'm confused on what you mean. Is 0F a possible B25 sector? My logic would make it B26. As it would also mark 19, 1A, and 1B as B26. I'm in an Ericcson market so I am not familiar if other markets use a different sector format either.

Here is my simplistic algorithm for band determination: if (provider_.equals("Sprint")) { ///@todo Will RRPP B12 be native "Sprint" coverage? if ((getPlmn() == 311870) || (getPlmn() == 311490)) { ///@todo add more "Clearwire plmn" return 41; // Clear 41 } else if((getGci() & 0x00100000) != 0) { //market code byte has lsb set return 41; } else if((getGci() & 0x8) == 0x8) { //sector id has 4th bit set return 26; ///@todo also check 5th bit? } return 25; } One thing I'll add is that the GCI is technically only 28 bits so it's only 7 hex digits and not 8 - so the most significant nibble (i.e. 0 in the 07E or 07F in the examples) will always be zero - http://developer.android.com/reference/android/telephony/CellIdentityLte.html#getCi%28%29 MikeJeep or SpenceSouth (or anyone really) can chime in with fixes/changes for this. This also doesn't account for the "Sticky" PLMN mentioned above.

Took a few calls - one to the number a few pages earlier and they said I wasn't eligible, one to the regular customer support 1-5-5-5 number and they tried to teach me how to enable WiFi calling, and finally back to the number a few pages back and they said they got it all submitted. Thanks for the tips and phone numbers everyone!

RRPP activity?

Now if Sprint can just finish NV1.0 between Festus and Cape G. on I-55 and get B25 going. Its sad going south (from Festus) and losing LTE when going north has such a great (tri-band) experience.

As some of you have guessed, it sounds like they are only allowing Nexus 6 (not even the N5) onto the service at least initially. http://www.wsj.com/articles/google-wireless-plan-has-one-catch-1425598890