Jump to content

Network Vision/LTE - North Wisconsin Market (Wausau/Green Bay/Appleton)


n9ovreric

Recommended Posts

I'm having the same problem with data and dropped calls. Seen more conduit being worked on thru town here in Wausau

 

Yeah I've been having an abnormally amount of dropped calls lately too. Just driving downtown where I normally get full bars. I'll take it as long as I know lte is coming!

Link to comment
Share on other sites

I have seen 2 towers along highway 54 east of Green Bay putting out an LTE signal on and off, but so far it looks like I get kicked off it shortly after, so it is probably still being tested. 

 

Hmm, a Kewaunee, WI tower has recently been listed as 4G complete - so I suppose it is possible I was getting 1XRTT off those towers and LTE off the Kewaunee tower. I'm not sure how to tell that in the SignalCheck app.

 

P.S. The towers I've been getting signs of upgrade from are identified on sponsor maps as MLXXXXXXX and MLXXXXXXX. I haven't gotten around to trying to take a picture to post to the in progress threads.

Link to comment
Share on other sites

Nice!  Hopefully spots continue to pop up near and in Green Bay.

 

I have seen 2 towers along highway 54 east of Green Bay putting out an LTE signal on and off, but so far it looks like I get kicked off it shortly after, so it is probably still being tested. 

 

Hmm, a Kewaunee, WI tower has recently been listed as 4G complete - so I suppose it is possible I was getting 1XRTT off those towers and LTE off the Kewaunee tower. I'm not sure how to tell that in the SignalCheck app.

 

P.S. The towers I've been getting signs of upgrade from are identified on sponsor maps as MLXXXXXXX and MLXXXXXXX. I haven't gotten around to trying to take a picture to post to the in progress threads.

Link to comment
Share on other sites

Wish Wausau had at least one tower with 4g

 

Sent from my EVO using Tapatalk 2

 

First site in the Wausau area had LTE accepted yesterday.  It's between Edgar and Marathon City, along the freeway.

 

Robert

  • Like 2
Link to comment
Share on other sites

Very cool thanks Robert. I see most of the sites around me are 3g just to the north and East of me. Still keeping my eye on the sites around me here tho.

 

Sent from my EVO using Tapatalk 2

 

 

Link to comment
Share on other sites

 

 

Wish Wausau had at least one tower with 4g

 

 

Sent from my EVO using Tapatalk 2

 

 

First site in the Wausau area had LTE accepted yesterday. It's between Edgar and Marathon City, along the freeway.

 

Robert

I should be going to Edgar today, I'll load up Sensorly and tag it if I do.

 

Sent from my Tricorder aboard the Enterprise

 

 

  • Like 2
Link to comment
Share on other sites

post-4392-0-88409500-1370724348_thumb.jpg

 

post-4392-0-58826000-1370724437_thumb.jpg

 

post-4392-0-64517100-1370724472_thumb.jpg

 

Well, I got a real up close and personal look at the tower on I-39 just south of the 51 truck stop.  There's fiber to the tower, and some empty boxes (Samsung).  Looks like the work is all down here, Sprint needs to turn it on!

  • Like 1
Link to comment
Share on other sites

Should be really nice when the network is complete. Even with a weak signal I got around 10 meg's up and 8 meg's down. Facebook and a few other apps just fly along.

 

Sent from my EVO using Tapatalk 2

 

 

Link to comment
Share on other sites

Should be really nice when the network is complete. Even with a weak signal I got around 10 meg's up and 8 meg's down. Facebook and a few other apps just fly along.

 

Sent from my EVO using Tapatalk 2

Where did you get that at?  Marathon City?  I drove through Fondulac yesterday and connected to LTE.....it was awesome!

Link to comment
Share on other sites

Marathon to Edgar should be mapped. Not sure where it switched back. I turned it in pulling out of Marathon and turned it off by Colby.

 

There is a site on hwy 10 by Marshfield I've seen pop LTE off and on, and a couple more by Point. I even saw my phone bounce LTE shortly by Wisconsin Rapids.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...