Jump to content


Honored Premier Sponsor
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by mdob07

  1. I've noticed the radio info screen has added a BW field to it in a recent update on my S9 plus. Haven't seen it populated with anything yet though. Hopefully it's a sign that Samsung is implementing those routines in their code, but I'm not sure if this is a Samsung specific screen or standard android screen. Sent from my SM-G965U using Tapatalk
  2. Looks like AT&T and Verizon share the DAS here based on what I see. I can't tell if CA is active or not since Samsung locks out those screens. Sent from my SM-G965U using Tapatalk
  3. I wish I could see the radio equipment, all I can see are the antenna cans sticking out. Sent from my SM-G965U using Tapatalk
  4. Churchill Downs iDas. I must be the only one on this sector. Sent from my SM-G965U using Tapatalk
  5. I'm finally starting to see 5MHz B29 pop up in KY. I've only seen it in rural areas so far but the license covers my entire area. They only have Lower D block here, Dish has E block for now.
  6. It has been extremely accurate in my testing on both AT&T and Verizon. It's more reliable than RSRP value alone for identifying cell sites for me.
  7. It's been up in Louisville KY since my phone updated to show it, but I haven't seen it yet in Lexington KY. From what I've read on HoFo it's set by TAC. When enough cell sites within the TAC have been upgraded to current standard they set the TAC to show it. Its definitely not 100% as one of the sites by my office shows 5Ge and its still B4/B12 only.
  8. Its AWS1. 2120MHz-2140MHz DL. That leaves 10 MHz below and 15MHz above it in AWS1. I'd have to check my log to confirm but I believe AT&T has that throughout the Cincinnati area. Where I live in Louisville KY AT&T has 15MHz, but its separated. 10MHz centered at 2115MHz, then Verizon has 10MHz centered at 2125MHz, then AT&T has 5MHz centered at 2132.5MHz, then T-Mobile has 10MHz centered at 2145MHz, and Verizon finishes AWS1 out with 10MHz centered at 2150MHz. AT&T also has 10x10 J block AWS3 here, but I'm not sure who has the other 3 5x5 AWS3 blocks. Edit: I'd love to see AT&T trade their 5x5 AWS license to Verizon in return for Verizon's single 5x5 PCS license here. It would allow V to expand their lower AWS carrier to 15x15 and allow T to expand their secondary PCS carrier to 10x10. Not sure if anything like that ever happens because of the differences in licensing between the 2 bands but it would benefit both.
  9. 4.514b has been stable all day on both of my phones. I haven't seen any issues out of either of them all day. Also I got the alerts setup the way I want and thats working great too!
  10. I wonder if Samsung has a place to point out issues like android does? I'd love to get that working on my Verizon s9+ since Verizon locks out the engineering screens. Hopefully we'll see it in one of the upcoming patches.
  11. Hey Mike, Looks like your changes worked. On 4.514b I'm now seeing W-CDMA info and SNR is back on both of my devices. Don't worry about the status bar icon in the GSM shot, I think I took the screen shot a soon as I cycled airplane mode. I'm 99.9% sure it was populated as I was watching it switch from GSM to HSPA. I've also got a question on the custom alerts, I have one set for 67086 to get an alert when I connect to J Block AWS as the primary carrier since AT&T is just starting to open it up here for uplink connections. I hadn't gotten an alert for it all day until after I installed 4.514b. Now I'm getting the alert everytime I connect to the Shepherdsville tower even though I don't show that I have ever connected to it yet except as downlink with CA. Is that the way it is supposed to work? If so that's fine, I just wanted to know. It shows up in the neighbor cell list.
  12. Just sent a diagnostic report, still getting no connection when on HSPA+. Edit: I'm also no longer seeing SNR reported on either my AT&T or Verizon S9+.
  13. I found a new AT&T iDAS installation last week at the Belterra Casino in Indiana. It has been installed since my last stay there back in October. It was only broadcasting B12/B66, no MFBI for B17 or B4. My dad's older phone wouldn't see it or connect to it at all, and when I locked my phone to only B4 I couldn't see it or connect to it. There was also no CA between the two bands. The iDAS covered the 15 floor hotel as well as the entry, restaurant, and shopping area up to where you actually get on the casino boat. They did not install it on the boat itself, I could barely get an HSPA+ connection while on the boat. The setup used the same GCI and PCI sector throughout the entire facility. The nodes are very inconspicuous and almost look like round ceiling speakers. They were installed about every 30-40 feet in the hotel area. Speed was impressive, and much better than the < .5mbps I got on the hotel wifi. The B12 carrier was 5x5, the B66 carrier was 20x20.
  14. Mike, for the "-Added LTE bandwidth (BW) value on Android 9+ devices." I'm not seeing anything on either of my S9+'s. Is this supposed to show the channel width? If so that would be awesome for devices like my Verizon S9+ where they lock out the engineering screens. Both are running Android 9, one has the March 1st security update and the other has February 1st update if it matters. I'm also still seeing no connection when on anything other than LTE with my AT&T S9+. I've also noticed with my Verizon phone that while on B4 the 2nd carrier notation works, but when connected with B66 MFBI to the same sector it doesn't. Not sure if that is something you want to carry over to B66. oDAS and iDAS notations also have this issue with AT&T B66. They are using the same GCI pattern just broadcasting with B66 EARFCN. Sometimes I'll be on B4 and sometimes I'll get B66 from the same site. One more thing, any plans to add the TA value to the log with the closet value saved with coordinates like how RSRP is done now? This would be very helpful when identifying sites using my log files. For instance, I was almost passing under the site from the below screenshot, but RSRP level is still in the -90's. I think adding the TA value would be helpful to identify sites especially when not getting all the way up to a site. From what I've seen by watching it on both my AT&T and Verizon phones its been usually spot on for distance.
  15. Mike, just noticed on my S9+ that SCP showed no connection in both the app and task bar when connected to HSPA+. Cycled airplane mode and its showing everything for LTE with no issues. I'll try to get it back to HSPA+ to do more testing later. Sent from my SM-G965U using Tapatalk
  16. I got the Android Pie update on my S9+ last night. Everything looks good with SCP. Sent from my SM-G965U using Tapatalk
  17. Got the Android Pie update for my AT&T S9+ just now, it's a big one. Taking forever to download. Sent from my SM-G965U using Tapatalk
  18. New update looking good on my S9+ so far.
  19. I have recently noticed my Verizon work phone (Note 4) roaming on Sprint 1x while still on Verizon LTE. I assume this is due to the CDMA thinning Verizon is doing around here. My phone said extended network while I was on Sprint 1x.
  20. Definitely a unique setup, I've never seen anything like that.
  21. Is it a 6 sector site by chance? I've noticed on all of the recent 6 sector conversions around me that there are at least 5 or 6 different GCIs for the site now. 4 sector sites usually have 3 GCIs and upgraded 3 sector sites have two. Not sure what the reason is for multiple GCIs, unless its some limitation on the amount of sectors that can be addressed on the hardware. On sites around me with 10 LTE carriers on 7 bands, that makes 30 unique sectors on a 3 sector site, and 60 on a 6 sector site. Seems crazy. Edit: I've also seen new sites and new bands on existing sites have different GCIs for each band, but usually gets sorted out within a few days then resembles a normal site.
  22. Pretty much everything around me already had B30 deployed, so I can't really tell if they are slowing down/stopping deployment for now. I have noticed that since it was reduced to 5x5 that I don't connect to it as the primary carrier much anymore, but still see it active in CA all the time. I figure that is because the uplink suffers so much at only 5MHz. From other peoples posts on the HoFo speed test thread it looks like most of the country is still 10x10 on B30. Hopefully they can get something figured out with it and go back to 10x10 here, which would give them 170MHz deployed spectrum in Louisville. Also discussed this a little bit here (post #4 links a map of SiriusXM repeaters): https://www.howardforums.com/showthread.php/1909330-AT-amp-T-Band-30-shrinking-from-10mHz-to-5mHz-Channel
  23. I came across this article today, has some interesting info and some cool pics of AT&T's lab setup. https://www.zdnet.com/article/at-t-5g-behind-the-scenes-in-texas-as-the-new-mobile-network-goes-live/
  24. I received the below email today about Google shutting down its Fusion Tables tool. I know many of us have and still use fusion tables for our market maps here on S4GRU. Looks like we've got a year to migrate to a new platform. Sent from my SM-G965U using Tapatalk
  25. Hey Mike, would it be possible to change SCP to identify AT&T B14 by EARFCN vs GCI pattern? After doing some analysis on my log, looking the the B14 thread on Howard Forums and the netmapper map it appears to wildly vary by market what AT&T used for B14 sectors. The EARFCN should be consistent across the country. This would keep you from having to set several different patterns for B14. Here is what I found: Louisville KY, Lexington KY, and Nashville TN use BF-C4 Louisiana, Ohio, Texas - D7-D9 Alabama - C4-C6 some of California, North Carolina, South Carolina, New Hampshire, Vermont, Washington St,: AB-AD New York, New Jersey - D2-D3 Chicago & Northern Indiana, 2B- 2D Oklahoma and Missouri - D4-D6 Some California - C2- C5 I've also noticed that in NYC the B2 2nd carrier is AB-AD, which is the same as my B4 2nd carrier here in Louisville and the same as B14 in several markets.
  • Create New...