Jump to content


Honored Premier Sponsor
  • Content Count

  • Joined

  • Last visited

  • Days Won


mdob07 last won the day on February 2

mdob07 had the most liked content!

Community Reputation

847 Trusted

About mdob07

  • Rank
    Member Level: 4G WiMax
  • Birthday 03/01/1991

Profile Information

  • Phones/Devices
    Galaxy S9+
  • Gender
  • Location
    Shepherdsville KY
  • Here for...
    4G Information
  • Twitter Handle

Recent Profile Visitors

7,783 profile views
  1. Quick, somebody go dig up the dead horse so we can beat it some more. https://www.koin.com/amp/news/civic-affairs/5g-cell-tower-critics-post-health-warning-signs/2017340977 https://www.wafb.com/2019/05/19/homeowner-focused-organization-host-public-meeting-address-att-small-cell-towers/?outputType=amp
  2. 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
  3. 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
  4. 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
  5. Churchill Downs iDas. I must be the only one on this sector. Sent from my SM-G965U using Tapatalk
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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!
  11. 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.
  12. 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.
  13. 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+.
  14. 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.
  15. 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.
  • Create New...