droidStory

At the height of the Mobile Map War, a small French company called Sensorly just launched an Android app that maps out wireless and Wi-Fi network coverage. This comes in handy to look-up ahead of time, whether or not a certain area has 3G coverage.

The way the app works is that your own phone reports its network experience, combined with location information (GPS and/or cell tower) back to Sensorly’s servers. The more people participate the more detailed maps get built.

Frankly, I’ve been wondering for a while why the wireless providers are not using this kind of technology to map out their problem spots.

It is not clear how many data samples are required and what statistical algorithms are being used for building a map. Also, problem phones like the Nexus One could potentially skew results by reporting insufficient 3G coverage for areas that in fact are working with other phones.

The app itself is a basic map viewer with a color coded overlay, with each color and shade representing a specific network and signal strength level.

The Android version currently maps only GSM and some Wi-Fi networks – sorry Droid users, but CDMA (Verizon and Sprint) maps are planned to be rolled-out in the coming weeks.

The company also plans to release versions for the iPhone and Windows Mobile.

The following maps are now available for free:

Thanks for dropping by! Feel free to join the discussion by leaving comments, and stay updated by subscribing to the RSS feed. See ya around! Thanks for visiting!

I figured this now warrants an extra post after there’s been much discussion on the Google support forum. It is absurd that Google keeps trying to put the blame on T-Mobile. The video below clearly shows that 3G network connectivity is fine until you firmly hold your phone in your hand.

Here’s an excerpt from my recent forum post.

I’ve been saying all along that this is a RF issue. I noticed this right away when I got my phone and even posted this video on Jan 9 to show how the N1 drops 3G as soon as you hold it in your hand.

The problem occurs only when you are in an area with a weak 3G signal, anything less than -80dBm. (Higher negative numbers mean weaker signal.)

Basically, if you have -90dBM or less signal strength with the phone sitting on your desk, holding it in your hand will push it down to -100dBm or less. At that point all bets are off. Before the update it would switch to Edge around -100dBm, now it seems to hold on until about -105dBm.

The “dBm” (dB-milliwatt) is a logarithmic measurement of signal strength, and dBm values can be easily converted to and from mW values. So a decrease of roughly 3dBm yields a change of roughly HALF in the mW value.

1mW = 0dBm
-96dBm = 0.0000000002511mW

In essence, the difference between a -80dBm signal and a -100dBm signal is HUGE. Check it out yourself here.

So here is my big question: Why is the N1 getting such a weak signal in solid 3G territory, and why does the signal degrade that much more when holding the phone in your hand?

IMHO the recent update just tweaked the switching thresholds, while the actual problem may be rooted deeper in the RF guts of the Nexus One.

See bottom of post for latest video. The Nexus One 3G saga continues. Kevin has a great post over at his jkontherun blog.

So over the span of the last three days, I’ve been testing my handset using the SpeedTest application from Xtreme Labs — available for free in the Android Market — and also watching the data indicator on the phone. Aside from testing in Philadelphia, I’ve also tested in various San Francisco neighborhoods and in Phoenix. Every single testing location used was squarely in a solid T-Mobile 3G coverage area — no fringe areas, for example.

And in every location, I saw either miserable 3G speeds, signals bouncing between 3G and EDGE, or — even worse –both.

He also setup this poll to track how many people still experience this problem, and whether the OTA Update provided a fix for some.

I can’t wait for Verizon to release the Nexus One or any of the other new HTC and Motorola Android phones that are in the pipeline. Having been on Verizon for so many years I started to take their excellent network coverage for granted.

Update: I created this short video clip to better illustrate how the OTA Update has not fixed the 3G problem, and how this problem can be easily reproduced. Just cover the  bottom / backside of the phone – you know the way you might hold your phone when answering a call – and a perfectly fine 3G signal disappears.

I installed the firmware update on my Nexus One last night with high hopes that the 3G connectivity problems would be fixed. After some simple tests I have to say that I did not notice any significant improvements. Although the phone seems to try holding onto a 3G connection a bit longer, the result is the same.

No real improvement after the update. 3G Signal strength -97dBm 8asu on Desk — dropping to -111dBM 1asu while holding in hand, barely holding onto 3G. Ooops it just switched to Edge -83dBm 13asu. #FAIL

How come 3bars of 3G just disappear every time you pick up the phone??? I also had a number of crashes when answering calls. Swiping the green answer button just stopped mid way and the phone hung. Perhaps this is related to temporarily losing network connection when switching to Edge after I pick up the phone. This is infuriating to say the least!

Motorola Droid + Verizon: 1
Nexus One + T-Mobile: 0

Google, now what?

After weeks of frustration in waiting and much heated discussion voiced in more than 1,500 posts to Google’s support forums, there is now a glimmer of hope that a fix to the “Spotty 3G” issue is in the works.

As posted previously here, the Nexus One is having some trouble holding onto a steady 3G connection under certain conditions.  Interestingly, similar problems occurred with the first iPhone 3G and were later addressed with a software fix. Following Apple’s playbook, Google has been mum on the issue until now.

Google finally posted the following statement to the forum today:

Hi Folks,

I wanted to post an update to the Nexus One Help Forum to let you know what we’ve been working on to help address the 3G issues some of you have been facing. I also wanted to thank you for being patient as we work to investigate the problem, an effort which has included our hardware partners.

The data from that investigation tells us that the majority of reported cases appear to be the result of being in low 3G coverage areas.  However, our engineers have also uncovered specific cases for which a software fix should improve 3G coverage for some users.  We are testing this fix now, initial results are positive, and if everything progresses as planned, we will provide an over-the-air software update to your phone in the next week or so.

Thanks again for your patience and for your feedback, and we will continue to keep you informed.

Thanks,

Ravi

I’m glad there’s finally an update on this. I’m really enjoying my Nexus One overall, but having weak or no 3G access takes a lot of fun out using it or showing off its great features.

Stay tuned for an actual date on the OTA update.

I’ve been using the Nexus One on t-mobile for a few days now, and while a LOVE this phone overall, I have not been impressed with its 3G performance.

Metro-Boston and surrounding suburbs supposedly have very good 3G coverage, at least according to t-mobile’s map, so I was hopeful being spoiled by Verizon’s excellent network performance and coverage. I noticed right away that the phone kept switching networks and didn’t seem to hold onto the 3G signal very well, regardless of my location.

A quick check of the Google support forum revealed that a number of people are experiencing the same problem.

It’s hard to tell what is causing this, and if this is a hardware or a software problem. I did notice one thing though. My phone is connected to 3G in my house and I can use data services at 3G speeds as long as I keep it on my desk. As soon as I pick-up the phone and hold it in my hand, 3G disconnects and the phone falls back to Edge.

Here’s a short video:

Update: Apparently there is a configuration screen that allows you to select network preferences. Some people suggest that forcing 3G (pick WCDMA only) will remedy the problem. You can get to the configuration screen by simply dialing the following number *#*#4636#*#*. Proceed at your own risk. I tried different settings and did not notice any improvement.

Update2 – From the T-Mobile Forum: Google and T-Mobile are investigating this issue and hope to have more information for you soon. We understand your concerns and appreciate your patience.