Jump to content

AgathosAnthropos

S4GRU Premier Sponsor
  • Posts

    117
  • Joined

  • Last visited

Posts posted by AgathosAnthropos

  1.  

    (Now I gotta go hide before anyone realizes I'm lurking around here..)

     

    -Mike

     

    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.

     

    Yes we will. It's cute that Mike thinks we don't have an alert set up to track his posts. lol

     

    But AgathosAnthropos if you have coding questions just throw them out some one may be able to help.

     

    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.

  2. I'm in beta but can't download

     

     

    Sent from my iPhone using Tapatalk

     

    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.

    • Like 1
  3. 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.

     

    sigmapper.jpg

    • Like 6
  4. 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.

  5. Missouri is a Ericsson/Nokia market. Nokia for B41 equipment from the start.

     

    ALU/Nokia markets still generally use ALU equipment for B41. That is the difference. We have only see one instance of the 3rd carrier in an ALU market, and it has not been repeated. That's why I am looking for verification of the 3rd carrier in the DC market, as it would be the first large ALU/Nokia market that I am aware of with the 3rd B41 carrier.

     

     

    As has been mentioned multiple times, SCP only detects 3rd B41 carrier in Samsung markets (where the GCI ends with 06/07/08). It does not yet identify the 3rd carrier in Ericsson/Nokia/ALU markets. Mike is currently working on an update for the app, see the SCP thread for more details.

     

    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.

  6. I believe that would be the first major ALU/Nokia area to have 3 carriers on air. If you could capture a GCI with 41/42/43 as the ending, that would be one way to confirm it is 3rd carrier on a Sprint site, and not perhaps a small cell using separate spectrum from the macro sites. 

     

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

     

    Screenshot_20170105-073156.png

     

    Screenshot_20170105-073409.png

  7. As I previously posted, the camera on my nexus 5X is busted (still).  I realized I have cell phone protection on my credit card so I am going that route first.  The claim is set but all they need now is a quote for a repair (or statement saying it is not worth fixing) from a repair center or the manufacturer.

     

    Will the Sprint repair center look at these?  I thought i remember reading they dont deal with them because they arent sold via Sprint.  Surely they could write a quote (regardless of how much) factoring in the hoops and stuff they would need to jump through to actually fix it.

     

    If not (and more likely) I will need to find a local shop who does repairs on these.

     

    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?

  8. These are not repeaters. They are relays. There Is no way to distinguish a relay from a macro site in a type 2 setup. It uses the same information as the macro site.

     

    Sent from my LG-H790

     

    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?

  9. I don't think the band 26 would be that easy but close. 0F(0000 1111) 10(0001 0000) 11(0001 0001) 19,1A,1B. 0F would through it off.

    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.

  10. GCI in hex is broken down by market XXX tower XXX sector XX. So MMMTTTSS 07E is chicago market band 25/26 (E=14 even) 07F is band 41(F=15 odd). For some reason they did their market GCI counting by 2 so all of the band 25 is even.

     

    There is also a 1450 hex offset between bands for the same site. Meaning 07E00100 and 07F45100 are the same site.

     

    07F clear is most likly plmn sticking and most likely an 8t8r. If my memory is correct clear should start with 00A or 00B.

     

    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.

    • Like 1
  11. 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!

×
×
  • Create New...