G14 (Dual SIM with 3G support)

Introduction

I have been a little busy lately, testing a new MT6573 based smartphone... and this time the review will focus on the G14, a clone of HTC Sensation.

Specifications

Chipset
Name:	MediaTek MT6573
CPU:	650 MHz ARM11™
GPU:	PowerVR™ SGX 531
Instruction set:	ARMv6
Software environment
Embedded:OS:	Android 2.3.4 (Gingerbread)
Body
Dimensions (width x height x depth):	126 x 65.4 x 11.3 millimetres
Weigth:	148 grams
Color:	Black
Battery
Capacity:	1500 mAh
Memory
RAM:capacity:	512 MB
ROM-capacity:	512 MB
Expansion slot:	microSD memory card, supporting up to 32 GB
Network support
Primary phone:	GSM850, GSM900, GSM1800, GSM1900, UMTS900, UMTS2100
Secondary phone:	GSM850, GSM900, GSM1800, GSM1900
Data links:	GPRS, EDGE, HSDPA, HSUPA
Display
Type:	Sharp LCD capacitive touchscreen
Size:	4.3 inches, WVGA resolution (480 x 800 pixels)
Camera
Main (rear):	8 megapixels (interpolated) with autofocus and dual LED flash
Secondary (front):	1.3 megapixels
Interfaces
Bluetooth (802.15):	Bluetooth 2.1 + Enhanced Data Rate
Wireless LAN / Wi-Fi (802.11):	IEEE 802.11b, IEEE 802.11g
USB:	USB 2.0 Client, Hi-Speed (480 Mbit/s) USB Series Micro-B (Micro-USB) connector
Satellite navigation
Built-in GPS module:	MT6620 chipset
GPS antenna:	Internal
Complementary GPS services:	A-GPS (Assisted GPS), MediaTek EPO (Extended Prediction Orbit)
Additional features
Sensors:	Gravity, Proximity and Light sensors
Analog Radio:	FM radio (87.5-108 MHz) with RDS radio receiver

Design and construction

The size of G14 is a little bit larger than other smartphones, in that it comes in at 11,3 mm thick - noticeably thicker than HD9, but still feeling comfortable in the hand.

The phone itself is encased in toughened plastic and aluminium (which feels more like plastic) through the stripe in the centre - the whole back of the phones pulls away from the main device, with the antenna and suchlike pumped into the chassis rather than on the phone itself.

The 3,5 mm headset jack and dedicated power button are located on the top edge. You'll also find an extra-large volume rocker on the left side, as you would on the G11i Pro.

The micro-USB port is located on the left edge. I usually prefer to have it at the top or bottom so that I can use the phone -while in charge- without having the cable get in the way.

The four Android buttons on the bottom are visible at all times (even when the phone display is off). On some handsets they become invisible, to make the phone “look better” and to save on backlight power consumption.

On the back side, we find the 8 megapixels autofocus camera sat next to a dual LED flash and a single loudspeaker grille.

Getting the back of the phone off through the little catch at the bottom is much harder than it looks, with the fingers needed to prise it apart almost holding it in place at the same time - wiggling and shaking is needed to get to the battery and microSD card slot.

The two SIM slots can only be accessed after removing the battery, but the microSD slot is accessible even with battery in place.

Display quality

This phone features a new LCD from Sharp. At first glance, it can be noticed a great definition.

The only thing I can point to this display is that colours don't seem too vivid, although it may be only a matter of setting the contrast (if that's possible).

Functionality

After my previous tests with the newest version of HD9, I thought that all MT6573 phones shared the same framework (which meant that in terms of features it was pretty much the same as when compared with G11i Pro features). I was happily surprised to see that G14 has a little bit different framework. 

This new framework includes some nice CyanogenMod features, such as enhanced notification widgets.

There's a new entry on the normal settings menu, that provides access to extra settings.

Under the dual SIM management menu, the user can edit the name of each SIM and also set the associated background color that will appear in call log as well as in the notification bar (behind the network strength bars). Other than that, also in the same menu, the user has the possibility to set a default card to establish all outgoing calls or set it to always ask, thus enabling the pop up that can be seen some images above showing the dialer (with the options of which SIM card should initiate the call). The same thing can be set for messaging and data connection purposes. In addition, given that G14 supports 3G networks, the option of video calls can also be noticed.

The extra settings menu includes advanced options related with application, display, input, interface and ringtones. Within extra display settings, screen-off and screen-off animations can be configured. Amazing animations, in my opinion, which imitate the CRT screen effect.

Lots of widgets can be added to the notification panel...

During the past few weeks, I noticed that battery performance is pretty good, taking into consideration the large screen size. With moderate use, I can get the battery to last 2 to 3 days, before putting it into charge.

Final thoughts

This is a good phone for people looking for an alternative to HD9. In terms of stability, speed, call quality, it is not different than the other MT65x3 clones, which means that MediaTek really did a great job.

Highs:

• Based on Android 2.3 (Gingerbread)
• Beautiful and renewed Dual SIM user interface
• Good battery life
• Dual SIM with 3G support

Lows:

• Display colours are not too vivid

Date with Googlebot, Part II: HTTP status codes and If-Modified-Since

Our date with Googlebot was so wonderful, but it's hard to tell if we, the websites, said the right thing. We returned 301 permanent redirect, but should we have responded with 302 temporary redirect (so he knows we're playing hard to get)? If we sent a few new 404s, will he ever call our site again? Should we support the header "If-Modified-Since?" These questions can be confusing, just like young love. So without further ado, let's ask the expert, Googlebot, and find out how he judged our response (code).

Supporting the "If-Modified-Since" header and returning 304 can save bandwidth.

-----------
Dearest Googlebot,
  Recently, I did some spring cleaning on my site and deleted a couple of old, orphaned pages. They now return the 404 "Page not found" code. Is this ok, or have I confused you?
Frankie O'Fore

Dear Frankie,
  404s are the standard way of telling me that a page no longer exists. I won't be upset—it's normal that old pages are pruned from websites, or updated to fresher content. Most websites will show a handful of 404s in the Crawl Diagnostics over at Webmaster Tools. It's really not a big deal. As long as you have good site architecture with links to all your indexable content, I'll be happy, because it means I can find everything I need.

  But don't forget, it's not just me who comes to your website—there may be humans seeing these pages too. If you've only got a very simple '404 page not found' message, visitors who aren't as savvy could be baffled. There are lots of ways to make your 404 page more friendly; a quick one is our 404 widget over at Webmaster Tools, which will help direct people to content which does exist. For more information, you can read the blog post. Most web hosting companies, big and small, will let you customise your 404 page (and other return codes too).

Love and kisses,
Googlebot

Hey Googlebot,
  I was just reading your reply to Frankie above, and it raised a couple of questions.
What if I have someone linking to a page that no longer exists? How can I make sure my visitors still find what they're after? Also, what if I just move some pages around? I'd like to better organise my site, but I'm worried you'll get confused. How can I help you?
Yours hopefully,
Little Jimmy

Hello Jimmy,
   Let's pretend there are no anachronisms in your letter, and get to the meat of the matter. Firstly, let's look at links coming from other sites. Obviously, these can be a great source of traffic, and you don't want visitors presented with an unfriendly 'Page not found' message. So, you can harness the power of the mighty redirect.

   There are two types of redirect—301 and 302. Actually, there are lots more, but these are the two we'll concern ourselves with now. Just like 404, 301 and 302 are different types of responses codes you can send to users and search engine crawlers. They're both redirects, but a 301 is permanent and a 302 is temporary. A 301 redirect tells me that whatever this page used to be, now it lives somewhere else. This is perfect for when you're re-organising your site, and also helps with links from offsite. Whenever I see a 301, I'll update all references to that old page with the new one you've told me about. Isn't that easy?

   If you don't know where to begin with redirects, let me get you started. It depends on your webserver, but here are some searches that may be helpful:
Apache: http://www.google.com/search?q=301+redirect+apache
IIS: http://www.google.com/search?q=301+redirect+iis
You can also check your manual, or the README files that came with your server.

   As an alternative to a redirect, you can email the webmaster of the site linking to you and ask them to update their link. Not sure what sites are linking to you? Don't despair - my human co-workers have made that easy to figure out. In the "Links" portion of Webmaster Tools, you can enter a specific URL on your site to determine who's linking to it.

  My human co-workers also just released a tool which shows URLs linking to non-existent pages on your site. You can read more about that here.

Yours informationally,
Googlebot

Darling Googlebot,
   I have a problem—I live in a very dynamic part of the web, and I keep changing my mind about things. When you ask me questions, I never respond the same way twice—my top threads change every hour, and I get new content all the time! You seem like a straightforward guy who wants straightforward answers. How can I tell you when things change without confusing you?
Temp O'Rary

Dear Temp,
   I just told little Jimmy that 301's are the best way to tell a Googlebot about your new address, but what you're looking for is a 302.
   Once you're indexed, it's the polite way to tell your visitors that your address is still the right one, but that the content can temporarily be found elsewhere. In these situations, a 302 (or the rarer '307 Temporary Redirect') would be better. For example, orkut redirects from http://orkut.com to http://google.com/accounts/login?service=orkut, which isn't a page that humans would find particularly useful when searching for Orkut***.
It's on a different domain, for starters. So, a 302 has been used to tell me that all the content and linking properties of the URL shouldn't be updated to the target - it's just a temporary page.

  That's why when you search for orkut, you see orkut.com and not that longer URL.

  Remember: simple communication is the key to any relationship.

Your friend,
Googlebot

*** Please note, I simplified the URL to make it easier to read. It's actually much more complex than that.

Captain Googlebot,
   I am the kind of site who likes to reinvent herself. I noticed that the links to me on my friends' sites are all to URLs I got rid of several redesigns ago! I had set up 301s to my new URLs for those pages, but after that I 301'ed the newer URLs to my next version. Now I'm afraid that if you follow their directions when you come to crawl, you'll end up following a string of 301s so long that by the end you won't come calling any more.
Ethel Binky

Dear Ethel,
   It sounds like you have set up some URLs that redirect to more redirects to... well, goodness! In small amounts, these "repeat redirects" are understandable, but it may be worth considering why you're using them in the first place. If you remove the 301s in the middle and send me straight to the final destination on all of them, you'll save the both of us a bunch of time and HTTP requests. But don't just think of us. Other people get tired of seeing that same old 'contacting.... loading ... contacting...' game in their status bar.

   Put yourself in their shoes—if your string of redirects starts to look rather long, users might fear that you have set them off into an infinite loop! Bots and humans alike can get scared by that kind of "eternal commitment." Instead, try to get rid of those chained redirects, or at least keep 'em short. Think of the humans!

Yours thoughtfully,
Googlebot

Dear Googlebot,
   I know you must like me—you even ask me for unmodified files, like my college thesis that hasn't changed in 10 years. It's starting to be a real hassle! Is there anything I can do to prevent your taking up my lovely bandwidth?

Janet Crinklenose

Janet, Janet, Janet,
   It sounds like you might want to learn a new phrase—'304 Not Modified'. If I've seen a URL before, I insert an 'If-Modified-Since' in my request's header. This line also includes an HTTP-formatted date string. If you don't want to send me yet another copy of that file, stand up for yourself and send back a normal HTTP header with the status '304 Not Modified'! I like information, and this qualifies too. When you do that, there's no need to send me a copy of the file—which means you don't waste your bandwidth, and I don't feel like you're palming me off with the same old stuff.

   You'll probably notice that a lot of browsers and proxies will say 'If-Modified-Since' in their headers, too. You can be well on your way to curbing that pesky bandwidth bill.

Now go out there and save some bandwidth!
Good ol' Googlebot

-----------

Googlebot has been so helpful! Now we know how to best respond to users and search engines. The next time we get together, though, it's time to sit down for a good long heart-to-heart with the guy (Date with Googlebot: Part III, is coming soon!).

As told to Chewy [Trewhella], Developer Advocate

UPDATE: Added a missing link. Thanks to Boris for pointing that out.

The anatomy of a search result

Written by Ríona MacNamara, Webmaster Tools team

When Matt Cutts, who heads up Google's webspam team, dropped by our Kirkland offices a little while ago we found ourselves with a video camera and an hour to spare. The result? We quickly put together a few videos we hope you'll find useful.

In our first video, Matt talks about the anatomy of a search result, and gives some useful tips on how you can help improve how your site appears in our results pages. This talk covers everything you'll see in a search result, including page title, page description, and sitelinks, and explains those other elements that can appear, such as stock quotes, cached pages links, and more.

If you like the video format (and even if you don't), or have ideas for subjects you'd like covered in the future, let us know what you think in our Webmaster Help Group. And rest assured, we'll be working to improve the sound quality for our next batch of vids.

GENERIC CIALIS on my website? I think my site has been hacked!

How to use "Fetch as Googlebot", part 1
Webmaster level: Intermediate

Has your site ever dropped suddenly from the index or disappeared mysteriously from search results? Have you ever received a notice that your site is using cloaking techniques? Unfortunately, sometimes a malicious party "hacks" a website: they penetrate the security of a site and insert undesirable content. Sophisticated attackers can camouflage this spammy or dangerous content so that it doesn't appear for normal users, and appears only to Googlebot, which could negatively impact your site in Google's results.

In such cases it used to be very difficult to detect the problem, because the site would appear normal in the eyes of the user. It may be possible that only requests with a User-agent: of Googlebot and coming from Googlebot's IP could see the hidden content. But that's over: with Fetch as Googlebot, the new Labs feature in Webmaster Tools, you can see exactly what Googlebot is seeing, and avoid any kind of cloaking problems. We'll show you how:

Let's imagine that Bob, the administrator of www.example.com, is searching for his site but he finds this instead:



That's strange, because when he looks at the source code of www.example.com, it looks fine:



With much surprise Bob may receive a notice from Google warning him that his site is not complying with Google's quality guidelines. Fortunately he has his site registered with Webmaster Tools, let's see how he can check what Googlebot sees:

First Bob logs into Webmaster Tools and selects www.example.com. The Fetch as Googlebot feature will be at the bottom of the navigation menu, in the Labs section:



The page will contain a field where you can insert the URL to fetch. It can also be left blank to fetch the homepage.



Bob can simply click Fetch and wait a few seconds. After refreshing the page, he can see the status of the fetch request. If it succeeds, he can click on the "Success" link...



...and that will show the details, with the content of the fetched page:



Aha! There's the spammy content! Now Bob can be certain that www.example.com has been hacked.

Confirming that the website has been hacked (and perhaps is still hacked) is an important step. It is, however, only the beginning. For more information, we strongly suggest getting help from your server administrator or hoster and reading our previous blog posts on the subject of hacked sites:

• My site's been hacked - now what?
• A quick security checklist for webmasters
• Message center warnings for hackable sites
• Best practices against hacking

If you have any questions about how to use the Fetch as Googlebot feature, feel free to drop by the Webmaster Help Forum. If you feel that your website might be hacked but are having problems resolving it, you might want to ask the experts in our "Malware and Hacked sites" category.

PS Keep in mind that once you have removed hacked content from your site, it will generally still take time for us to update our search results accordingly. There are a number of factors that affect crawling and indexing of your content so it's impossible to give a time-frame for that.

Written by Javier Tordable, Software Engineer and John Mueller, Webmaster Trends Analyst

Hard facts about comment spam

Webmaster Level: Beginner

It has probably happened to you: you're reading articles or watching videos on the web, and you come across some unrelated, gibberish comments. You may wonder what this is all about. Some webmasters abuse other sites by exploiting their comment fields, posting tons of links that point back to the poster's site in an attempt to boost their site's ranking. Others might tweak this approach a bit by posting a generic comment (like "Nice site!") with a commercial user name linking to their site.

Why is it bad?

FACT: Abusing comment fields of innocent sites is a bad and risky way of getting links to your site. If you choose to do so, you are tarnishing other people's hard work and lowering the quality of the web, transforming a potentially good resource of additional information into a list of nonsense keywords.

FACT: Comment spammers are often trying to improve their site's organic search ranking by creating dubious inbound links to their site. Google has an understanding of the link graph of the web, and has algorithmic ways of discovering those alterations and tackling them. At best, a link spammer might spend hours doing spammy linkdrops which would count for little or nothing because Google is pretty good at devaluing these types of links. Think of all the more productive things one could do with that time and energy that would provide much more value for one's site in the long run.

Promote your site without comment spam

If you want to improve your site's visibility in the search results, spamming comments is definitely not the way to go. Instead, think about whether your site offers what people are looking for, such as useful information and tools.

FACT: Having original and useful content and making your site search engine friendly is the best strategy for better ranking. With an appealing site, you'll be recognized by the web community as a reliable source and links to your site will build naturally.

Moreover, Google provides a list of advice in order to improve the crawlability and indexability of your site. Check out our Search Engine Optimization Starter Guide.

What can I do to avoid spam on my site?

Comments can be a really good source of information and an efficient way of engaging a site's users in discussions. This valuable content should not be replaced by gibberish nonsense keywords and links. For this reason there are many ways of securing your application and disincentivizing spammers.

• Disallow anonymous posting.
• Use CAPTCHAs and other methods to prevent automated comment spamming.
• Turn on comment moderation.
• Use the "nofollow" attribute for links in the comment field.
• Disallow hyperlinks in comments.
• Block comment pages using robots.txt or meta tags.

For detailed information about these topics, check out our Help Center document on comment spam.

My site is full of comment spam, what should I do?

It's never too late! Don't let spammers ruin the experience for others. Adopt security measures discussed above to stop the spam activity, then invest some time to clean up the spammy comments and ban the spammers from your site. Depending on you site's system, you may be able to save time by banning spammers and removing their comments all at once, rather than one by one.

If I spammed comment fields of third party sites, what should I do?

If you used this approach in the past and you want to solve this issue, you should have a look at your incoming links in Webmaster Tools. To do so, go to the Your site on the web section and click on Links to your site. If you see suspicious links coming from blogs or other platforms allowing comments, you should check these URLs. If you see a spammy link you created, try to delete it, else contact the webmaster to ask to remove the link. Once you've cleared the spammy inbound links you made, you can file a reconsideration request.

For more information about this topic and to discuss it with others, join us in the Webmaster Help Forum. (But don't leave spammy comments!)

Written by Adel Saoud and Paolo Petrolini

A dozen ways to discuss "webmaster help"

Written by Patrick Chapman, Search Quality Team

Our goal for the Webmaster Help Group is to be an authoritative source for accurate, friendly information and discussion. There are many terrific members of the Webmaster Groups community, and we're glad to know them all. In our English discussion group, a big Webmaster Central (WMC) thank-you to our comrades and fellow webmasters for their helpful knowledge and insight: webado, Phil Payne, JLH, cass-hacks, cristina, Sebastian, and dockarl, just to name a few.

Webado and cass-hacks both speak several languages -- thankfully, some of us do as well. We now have Googlers posting to the Google Webmaster Help Group in 12 languages! Here's a brief introduction of the Googlers, most of whom work together at our European headquarters in Dublin, in the Non-English groups (several have been posting for months, but we'd still like to give them an intro). :)


French Webmaster Help Group

Salut, I come from the French city Bordeaux where I spent most of my time, before I moved to Paris and then Dublin where I work now in Google Search Quality. When not in front of my computer, I like to go to the cinema, play chess and organize dinners
with my friends.
- Guide Google

Italian Webmaster Help Group

Ciao, my name is Stefano and I’m responsible for the Italian Webmaster Help Group. I work on search quality issues in Italian. I’m from Italy and have been living in Ireland for more than 2 years. I do love the multicultural environment you can find in Dublin and all the people from everywhere you get to know here, but sometimes it’s difficult to be so far away from my favorite football team, so now and then I really have to fly back home to get a bit of Serie A.
- Guida Google

German Webmaster Help Group

Grüss Gott! My name is Uli, and I post in the German Webmaster Help Group. I am originally from Germany but live in Ireland now. Unfortunately, I don't have my own website to show off. The German Help Group has grown into a big, vibrant community of very helpful and savvy webmasters, so if you speak German, go and check it out!
- Google Webmeister Guide

Spanish Webmaster Help Group

Hola! My name is Alvar and I'll be monitoring the Spanish Webmaster Help Group. Please join us if you speak a word or two in Spanish :-) More on the personal side, I don't own a portal or something like that but rather a tiny blog with nearly no visibility on the Internet, and I'm happy with that. I studied telecommunication engineering and my hobbies include soccer, foosball, table tennis, basically almost any other sport, traveling, photography, cinema, and technology, so I admit sitting in front of a computer can be counted as a hobby :-) Another important fact about me is that I'm from Barcelona, a city everyone should visit at least once in their life. What are you waiting for?
- Guía de Google para webmasters

Hola, I'm Rebecca. I studied to be a librarian but somehow along the way ended up being drawn into the digital side of information. So while I still snuggle up to books at night, computers take up most of my day. As for things I like to do (but wouldn't go so far as to call them hobbies…) I'm still pretty new to Dublin so I rather enjoy walking around until I'm lost and then trying to figure out how to get back home, and then when I get back home I like to play with my cat, best known for her fantastic Gollum impersonation when she gets riled up.
- Guía de Google

Dutch Webmaster Help Group

Hallo, I'm Andre. I'm very fond of Dutch music. But since living in Dublin for almost 2 years now, my taste for music has fused with the Irish sound. I like listening to live music in pubs, hanging out with the locals, have a pint or two and talking about upcoming gigs, artists, and all other topics that pass the day.
- André

Swedish Webmaster Help Group

Hejsan! My name is Hessam and I'm responsible for the Swedish Webmaster Help Group. I've been with Google for the last 2 years, working on search quality issues in Sweden. I'm originally from Sweden but moved to Dublin two years ago. My main interest is traveling and living in Dublin makes it easy to visit to all corners of Europe without blowing the budget. Thanks to cheap airlines, it takes merely a few hours from my door to the beer gardens of Munich, wine bars of Paris, ski slopes of Italy or beaches of Spain, depending on the mood. Looking forward to talking to you all!
- Google Webbansvarig Guide

Finnish Webmaster Help Group

Hei, I'm Anu and I work in the Search Quality team. I'm originally from Finland but these days I hold my umbrella high in Dublin. When I'm not online, you can catch me cycling (be it one or two wheels), playing virtual tennis or at the airport. I've been bitten by the travel bug, and try to see as many places near and far as possible. Besides all things webmaster related, I also have an interest in foreign languages, books and films. I look forward to meeting you in the Finnish Webmaster Help Group!
- Googlen Web-ylläpidon Ryhmän Opas

Polish Webmaster Help Group

Cześć, I'm Guglarz (it stands for Googler in Polish), the Googler on the Polish Webmaster Help Group. I was lucky to grow up in the city of Kraków, Poland's most beautiful city and the place where Google recently opened a research center. I've been with Google for two years now and I still love this job as much as I did the very first day. It's my favorite hobby activity in fact. If I don't work, I like to keep myself busy with general aviation, running or bowling, a sport I recently found out I was talented in. ;-)

I discovered my passion for the Internet early in school and after graduating in information science studies I was looking for a challenging position in the industry, although after the year 2000 crash there was little hope for that. It took me a couple of jobs in the established industries and some traveling around the globe before I found my dream job here at Google.

Ever since I started helping on the Polish Webmaster Help Group, it has been growing rapidly, both in terms of user numbers as much as in terms of the activity. It's really exciting to see how Polish webmasters help each other and make the web a more interesting place. Three group members, Cezary Lech, Umik and krzys in particular made an effort to vitalize the community in its early days. I'd like to say dziękuję (thank you in Polish) and please keep up the great spirit - thumbs up!
- Guglarz

Portuguese Webmaster Help Group

Olá, my name is Pedro. I'm Portuguese and I'm part of the Search Quality team. I've been working at Google since March 2006 mostly focused on the Portuguese language markets. I grew up in Tavira, a small town in the Algarve region – South of Portugal – and I always had a nerdy side, playing with computers since my very early days when memory meant 128KB. Most of my interests fall on my origins, I enjoy sailing and scuba diving, music is also on my top list. I'm based in the European Headquarters – Dublin office, and I'll be looking to strengthening contact with Portuguese webmasters (non Portuguese are also welcome).
- Ajuda a Webmasters do Google

Russian Webmaster Help Group

Привет! My name is Oxana and I come from Moldova, a teeny tiny country in Eastern Europe. My background is in mathematics and computer sciences and I have worked as a web developer for more than 7 years now. Of course I have a web site, but it features only an, unfortunately, eternal "under construction" message and a hope for a better future. :) I love to read and to travel, and at the moment I am a helpless wannabe photographer. Also, I'm a passionate WoW player and soon I'll become the best Warlock Orc on this side of Kalimdor! When I'm a grown-up person I work at Google on the Search Quality team and I primarily support the Russian market.
- Оксана

Danish Webmaster Help Group

Hej, my name is Jonas, and I am from Copenhagen, the wonderful capital of beautiful Denmark. I've been a webmaster of a blog since 2001, where I still drop a few lines every now and then. I am a jack of many trades, with a background in human geography and communication, design, and media. I've done some authoring for the web, but mostly administrative backends in PHP/MySQL, so they are not that interesting. I've been active on Usenet for awhile as well, and spent many hours there, getting smarter with the help of others.

I've been with Google for a couple of years now, working exclusively with search quality and I am now helping out in the Danish Webmaster Help Group. Looking forward to seeing you there (:
- GoogleGuide

'New software version' notifications for your site

Webmaster level: All

One of the great things about working at Google is that we get to take advantage of an enormous amount of computing power to do some really cool things. One idea we tried out was to let webmasters know about their potentially hackable websites. The initial effort was successful enough that we thought we would take it one step further by expanding our efforts to cover other types of web applications—for example, more content management systems (CMSs), forum/bulletin-board applications, stat-trackers, and so on.

This time, however, our goal is not just to isolate vulnerable or hackable software packages, but to also notify webmasters about newer versions of the software packages or plugins they're running on their website. For example, there might be a Drupal module or Joomla extension update available but some folks might not have upgraded. There are a few reasons a webmaster might not upgrade to the newer version and one of the reasons could be that they just don't know a new version exists. This is where we think we can help. We hope to let webmasters know about new versions of their software by sending them a message via Webmaster Tools. This way they can make an informed decision about whether or not they would like to upgrade.

One of the ways we identify sites to notify is by parsing source code of web pages that we crawl. For example, WordPress and other CMS applications include a generator meta tag that specifies the version number. This has proven to be tremendously helpful in our efforts to notify webmasters. So if you're a software developer, and would like us to help you notify your users about newer versions of your software, a great way to start would be to include a generator meta tag that tells the version number of your software. If you're a plugin or a widget developer, including a version number in the source you provide to your users is a great way to help too.

We've seen divided opinions over time about whether it's a good security practice to include a version number in source code, because it lets hackers or worm writers know that the website might be vulnerable to a particular type of exploit. But as Matt Mullenweg pointed out, "Where [a worm writer's] 1.0 might have checked for version numbers, 2.0 just tests [a website's] capabilities...". Meanwhile, the advantage of a version number is that it can help alert site owners when they need to update their site. In the end, we tend to think that including a version number can do more good than harm.

We plan to begin sending out the first of these messages soon and hope that webmasters find them useful! If you have any questions or feedback, feel free to comment here.

Posted by Patrick Chapman, Search Quality Team

Bringing the conference to you

Written by Susan Moskwa, Webmaster Trends Analyst

We're fortunate to meet many of you at conferences, where we can chat about web search and Webmaster Tools. We receive a lot of good feedback at these events: insight into the questions you're asking and issues you're facing. However, as several of our Webmaster Help Group friends have pointed out, not everyone can afford the time or expense of a conference; and many of you live in regions where webmaster-related conferences are rare.

So, we're bringing the conference to you.

We've posted notes in our Help Group from conferences we recently attended:

• John Müller covers SMX Stockholm
• I recap the AMA's Search Engine Marketing conference

Next month, Jonathan and Wysz will post their notes from PubCon, while Bergy and I will cover SES Chicago.

If you can make it to one of these, we'd love to meet you face to face, but if you can't, we hope you find our jottings useful.

HD9 (Dual SIM with 3G support)

Introduction

Last month, I had the chance to test a friend's new HD9. It's a recently released refresh of the "old" HD9 as it is now based on the MT6573 chipset. This means that if you like it's design, you can now enjoy a faster Dual SIM smartphone that supports 3G networks.

Specifications

Chipset
Name:	MediaTek MT6573
CPU:	650 MHz ARM11™
GPU:	PowerVR™ SGX 531
Instruction set:	ARMv6
Software environment
Embedded:OS:	Android 2.3.4 (Gingerbread)
Body
Dimensions (width x height x depth):	119 x 65 x 10 millimetres
Weigth:	150 grams
Color:	Black
Memory
RAM:capacity:	512 MB
ROM-capacity:	512 MB
Expansion slot:	microSD memory card, supporting up to 32 GB
Network support
Primary phone:	GSM850, GSM900, GSM1800, GSM1900, UMTS900, UMTS2100
Secondary phone:	GSM850, GSM900, GSM1800, GSM1900
Data links:	GPRS, EDGE, HSDPA, HSUPA
Display
Type:	Sharp LCD capacitive touchscreen
Size:	4.3 inches, WVGA resolution (480 x 800 pixels)
Camera
Main (rear):	8 megapixels (interpolated) with autofocus and single LED flash
Secondary (front):	1.3 megapixels
Interfaces
Bluetooth (802.15):	Bluetooth 2.1 + Enhanced Data Rate
Wireless LAN / Wi-Fi (802.11):	IEEE 802.11b, IEEE 802.11g
USB:	USB 2.0 Client, Hi-Speed (480 Mbit/s) USB Series Micro-B (Micro-USB) connector
Satellite navigation
Built-in GPS module:	MT6620 chipset
GPS antenna:	Internal
Complementary GPS services:	A-GPS (Assisted GPS), MediaTek EPO (Extended Prediction Orbit)
Additional features
Sensors:	Gravity, Proximity and Light sensors
Analog Radio:	FM radio (87.5-108 MHz) with RDS radio receiver

Design and construction

The body and quality of construction is pretty much the same...

The screen is a new version, though. This time, the manufacturer's choice was to use a Sharp ASV-LCD.  

Features

The new version of HD9 shares the framework with G11i Pro, so it has exactly the same features. Take a look at it's review to know more about it.

Final thoughts

This refresh brings improvements over the old one, not only for the better user experience in terms of speed, but in great part for the added 3G support and improved network reception.

Just visit my partner shop (etotalk.com), if you are interested to buy this phone.