rwong48

While it looks like the app surely collects info while it is running, if you switch to any other app or even press Home, it looks like it stops collecting data and is even sometimes killed. This prevents me from playing music or using navigation and still mapping while I drive automatically.

There's an option in Menu/Parameters/General called "Flush app from memory". I disabled it but I'm not sure if that's the exact behavior I am/you are looking for.

When I drive, I hit Map Trip and Start. Data collection still occurs even if I switch to another app (just don't turn the screen off.)

To add on what I just found a few hours ago.. looks like someone just added light coverage on the 101/87 interchange.

Tried to expand on some of the new dots that appeared in the past few days:

1. Montague/101: didn't find anything.
    
   
2. Central Expy/N Fair Oaks Ave: didn't find anything again.
   

But to my surprise, there was 4G LTE on Central Expy from Oakmead Pkwy to SJC airport (and up Trimble a bit.)

I've uploaded the results onto Sensorly!

(I believe Central/Bowers was one of the first mentions of the South Bay on this site, here.)

It's just a block away from my office (which doesn't have working WiFi!!!)... so close yet so far.

PS: I made a post about E Capitol Expy in San Jose here, before I found this thread. I'm not sure whether I should "report your LTE connection here" in this thread or in that thread.

Glad I'm not the only one noticing the new colors. It's really hard to spot things in the Bay Area now (what used to previously be darker purple and a good signal.) I hope this is temporary, or even reverted. The colors become way darker once I zoom in enough, which is also inconsistent.

BTW, thanks to Sensorly for adding descriptions ("2G-3G", "WIMAX", and "LTE") to the 3 Sprint items in the coverage map list. This makes it much more convenient to find the LTE map.

I'm glad they renamed one of the "4G"s to "WiMAX", but I'd also like the remaining "4G" to say "LTE" or "4G LTE", for clarity's sake. Am I the only one who thinks so?

Though it would probably have to be changed for all carriers, for consistency's sake, if Sensorly decided to do so.

Just found some LTE in East San Jose! Capitol Expy between 680 and Tully. So excited that I couldn't wait until I got home to post. Was not expecting this today.

Yes, I was running Sensorly. So the results should be up soon. I checked the map just now and it looks like someone already recorded a tiny amount of the area (Adrian Way between Story Road and Ocala Ave.)

It also looks like a LOT of other Bay Area coverage has showed up since the last time I checked (every day?)

edit: My results are up now!

Just wanted to say that I finished a full week in Manhattan (Chinatown mainly) and I regret a bit not switching back to my WiMAX phone. I was switching between a T-Mobile USB stick and Sprint 3G as my primary internet connection for surfing and some Skype.

I was pretty impressed with 3G. I don't recall the exact speeds in the past (since I had always been on WiMAX), but this week, I was able to pull 1-1.7Mbps around the clock. During peak hours, I've seen it drop to around 600-700Kbps, but pick back up within a few minutes. I hope I'm not just talking crazy, but it seems like backhaul may have increased on these towers (NV). Even during peak hours the speeds generally stayed over 50% of maximum.

Salinas/Monterey and all of Monterey County are in Sprint's South Bay market.

I stand corrected. Thanks.

However, as a South Bay local, I can't really consider those as South Bay. But if Sprint wants to include those as their South Bay market, then so be it.

Specificially for Salinas, CA and King City CA (zip codes: 93905,93906, 93901,93930)

I don't think Salinas counts as South Bay. King City definitely doesn't. You can probably expect to get LTE there after South Bay gets LTE.

And yes, there are some live sites by 280 by the Cupertino/Sunnyvale area. I've posted some results in the "report your LTE connection here" thread. You could check Sensorly to see the exact spots, though I haven't been there myself since I started using it to report coverage.

Once you have a 4G LTE connection, open the app. Click on "Map Trip" in the lower right hand corner. In the next screen, click the start button. Let it run and collect 4G data points. After a few minutes, you can press stop. It will then log all your 4G connection points to the Sensorly server and it will appear on their maps in an hour or two.

 

You can view other Sensorly uploads here: http://sensorly.com/...t/lte_310sprint I contributed most of the data around the Waco area.

 

It would be great if you could start it again the next time you are out an about in Fredericksburg, so it can log all the places around town that have a signal. Thanks for contributing!

 

Robert

I just wanted to say thanks for the note about Sensorly. I haven't read about it anywhere else on the site until this post.

Now I run it on every drive, and I like the idea so much that I even busted out my WiMAX phone to generate some coverage maps. I feel like everyone on this site should at least know about it (they don't have to contribute though.)

That's also what I'm expecting. LTE is just starting to be completed on the very first sites in the market.

 

Robert

I'm now heading to NYC (Chinatown mostly, some Midtown) for the last week of Sept. It's wishful thinking to have LTE..

WiMAX was decent, I don't want to go through the hassle of going back to my old phone..

I can confirm on the galaxy nexus, I am able to use a hacked Verizon-only prl (00001) to be on Verizon Evdo and Sprint LTE simultaneously. I can also be a dummy and try any other prl if needed.

Thanks, saved me some time.

When I first found Sprint LTE, I was on 00001, so I was confused. I stopped roaming anyways, but now I'm gonna start again.

CSV results from another Cupertino visit (note that SpeedTest doesn't refresh the location for every test):

Date,ConnType,LatLon,Download,Upload,Latency,ServerName
"2012-09-01 15:00","Lte","37.31244,-122.02969",7696,564,45,"San Jose, CA"
"2012-09-01 14:59","Lte","37.31244,-122.02969",13187,5465,42,"San Jose, CA"
"2012-09-01 14:59","Lte","37.31244,-122.02969",12912,8014,51,"San Jose, CA"
"2012-09-01 14:58","Lte","37.31244,-122.02969",6670,4560,40,"San Jose, CA"
"2012-09-01 14:58","Lte","37.31244,-122.02969",3680,1834,40,"San Jose, CA"
"2012-09-01 14:57","Lte","37.31244,-122.02969",14312,7564,49,"San Jose, CA"
"2012-09-01 14:57","Lte","37.31244,-122.02969",11358,5193,42,"San Jose, CA"
"2012-09-01 14:56","Lte","37.31244,-122.02969",8491,5026,52,"San Jose, CA"
"2012-09-01 14:56","Lte","37.31244,-122.02969",7679,4314,56,"San Jose, CA"
"2012-09-01 14:55","Lte","37.31244,-122.02969",15112,7363,48,"San Jose, CA"
"2012-09-01 14:55","Lte","37.31244,-122.02969",7466,7677,52,"San Jose, CA"
"2012-09-01 14:54","Lte","37.31244,-122.02969",9388,4791,54,"San Jose, CA"
"2012-09-01 14:54","Lte","37.31244,-122.02969",6116,3717,57,"San Jose, CA"
"2012-09-01 14:53","Lte","37.31244,-122.02969",8365,5736,51,"San Jose, CA"
"2012-09-01 14:53","Lte","37.31244,-122.02969",8297,4335,49,"San Jose, CA"
"2012-09-01 14:52","Lte","37.31244,-122.02969",5281,3362,46,"San Jose, CA"
"2012-09-01 14:52","Lte","37.31244,-122.02969",7192,4531,57,"San Jose, CA"
"2012-09-01 14:49","Lte","37.31110,-122.04305",7941,4213,36,"San Jose, CA"
"2012-09-01 14:47","Lte","37.31363,-122.03189",8565,5100,53,"San Jose, CA"
"2012-09-01 13:34","Lte","37.31244,-122.02969",3740,1122,54,"San Jose, CA"
"2012-09-01 13:20","Lte","37.31382,-122.03192",5433,4489,38,"San Jose, CA"
"2012-09-01 13:18","Lte","37.33049,-122.03237",6370,4501,55,"San Jose, CA"
"2012-09-01 13:17","Lte","37.33049,-122.03237",6027,4756,43,"San Jose, CA"
"2012-09-01 13:17","Lte","37.33049,-122.03237",8336,7731,36,"San Jose, CA"
"2012-09-01 13:16","Lte","37.33049,-122.03237",17173,6002,39,"San Jose, CA"
"2012-09-01 13:16","Lte","37.33049,-122.03237",18884,9436,40,"San Jose, CA"
"2012-09-01 13:15","Lte","37.33049,-122.03237",18542,9421,38,"San Jose, CA"
"2012-09-01 13:15","Lte","37.33049,-122.03237",19239,9634,48,"San Jose, CA"
"2012-09-01 13:15","Lte","37.33049,-122.03237",17090,7305,40,"San Jose, CA"
"2012-09-01 13:14","Lte","37.33049,-122.03237",13309,8096,48,"San Jose, CA"
"2012-09-01 13:14","Lte","37.33049,-122.03237",10402,8182,49,"San Jose, CA"
"2012-09-01 13:10","Lte","37.31927,-121.98947",14131,4546,53,"San Jose, CA"

The highest (17-19Mbps) results were on De Anza Blvd @ Stevens Creek Blvd.

Also, I noticed this on the side of the freeway.. not sure if it is anything.

https://maps.google.com/maps?ie=UTF8&ll=37.324714,-122.002659&spn=0.033274,0.066047&hnear=0x808fca832e82d3f1:0x9b09ee338f640613,%2B37°+19'+9.32",+-121°+59'+22.11"&gl=us&t=m&z=15&layer=c&cbll=37.324605,-122.002452&panoid=AgNZll_b-Q7_1eouPTo-Jw&cbp=12,355.67,,0,-4.11

I'm in North San Jose and I don't go out much, but as I went towards Cupertino on Thursday (I was on Verizon PRL) I noticed that my data dropped on 280. I checked status and it showed LTE (on 00001 PRL - WTF?)

 

I updated profile and PRL to switch to Sprint, and was actually on LTE by 280/DeAnza. However, it would not connect to data for some reason. I had it sit for about 2 hours wondering if it would ever connect. Screenshot attached.

 

My network mode is LTE/CDMA and I have all the data services/data roaming options checked.

 

On my way back, once I wasn't in an LTE area, I had eHRPD almost everywhere but had no data connection.

 

In both situations I had to force network mode to CDMA/EvDo in order to get data (via 3G).

 

I didn't get a chance to test Central Expy @ Bowers like a previous poster, but I suspect that I'll run into the same problem (signal, but no data over signal.)

Update:

Went back to stock ROM and I was able to connect to eHRPD! Did not see LTE at Central/Bowers though.

So I figured since I was seeing the same problem with LTE, this fix (switching back to the stock ROM) would've let me connect to LTE as well.

So I went back to 280/DeAnza and connected to 4G LTE for the first time!

Did a bunch of speed tests and got 10Mbps both ways.

Traced my route backwards and kept testing, and maintained my connection all the way to 280/880. I peaked at 22Mbps on 280 around Wolfe.

Running FD02 with FG01 radio; haven't updated my stock ROM to FG01.

I also need to test if eHRPD/LTE work after restoring my daily ROM (euroskank cm10 kangs)

I'm in North San Jose and I don't go out much, but as I went towards Cupertino on Thursday (I was on Verizon PRL) I noticed that my data dropped on 280. I checked status and it showed LTE (on 00001 PRL - WTF?)

I updated profile and PRL to switch to Sprint, and was actually on LTE by 280/DeAnza. However, it would not connect to data for some reason. I had it sit for about 2 hours wondering if it would ever connect. Screenshot attached.

My network mode is LTE/CDMA and I have all the data services/data roaming options checked.

On my way back, once I wasn't in an LTE area, I had eHRPD almost everywhere but had no data connection.

In both situations I had to force network mode to CDMA/EvDo in order to get data (via 3G).

I didn't get a chance to test Central Expy @ Bowers like a previous poster, but I suspect that I'll run into the same problem (signal, but no data over signal.)