We've been playing with both our new 64 GB iPod Touch, which we got a couple of weeks ago on an employee discount :-), and the HT-03a running Android 1.5 "cupcake". As we expected, the Android OS is not yet as refined as the iPhone OS 3.1 running on the Touch.
Android version 1.6 "Donut" will add several improvements, including global search (equivalent to Apple's spotlight), a much-needed task manager (which is unnecessary on the iPhone OS), and a redesigned Android market.
Overall, we are happy with the performance of the phone. We like the notification system, which displays everything in the task bar. The task bar can be swiped down like a windowshade to see details, such as previews of SMS, email notifications, and what song is playing. The ability to install apps from anywhere is just! fricken! awesome! Widgets are also very useful because they add soft buttons to the desktop to perform common tasks such as toggling wifi or the ringer (see below)
There are, however some caveats that we will list, in no particular order, below. Some of these are problems we were aware of prior to purchasing. Some of these are general problems with Google services. But, most of these probably come with the territory of a relatively immature operating system and are things that we expect to see resolved in time.
- Mail is not up to what is expected in Japan.
- It is PC mail, so you will need to be whitelisted by people with strict filtering.
- There is currently no emoji.
- Google and Docomo have a bug in their push system which can (but not always) delay push notification. A work around is to manually check with the browser-based version of Gmail that is optimized for Android. There is no reported time frame for resolution, meaning neither Google nor Docomo has a clue about what is broken or how to fix it.
- Integration with Google services is not as tight as we expected. The iPhone OS Google Maps app is better integrated than the Android app.
- There are several issues with language localization that are not related to the Android OS per se, but rather with Google's seemingly haphazard approach to localization.
- Navigation in Android is not as "snappy" as in the iPhone OS. This may be due to the iPod Touch/iPhone's slightly speedier processor or better code optimization in the more mature iPhone OS. Or both.
- The Android market is truly a mess. Paid apps are not available in the Japanese market. A reasonably usable version of Google Maps (for someone in Tokyo) is also not available in the Japanese market (though we know where to find and install it).
- Closing apps is a bit confusing because of the way Android allows background user processes to run and its built-in resource management. Hitting the home key may or may not actually kill the app; 3rd-party taskmanager is recommended.
- Many commonly performed tasks require navigating the settings menu. There is no quick way to enable what we commonly consider "manner mode". The "silent mode" function is truly silent, killing the vibrator as well. 3rd-party widgets provide these functions.
- Plugging in the headphones (through the included USB adapter - no headphone out on this hardware) does not necessarily kill the external speakers. It does on a case by case basis. Doom 3 even started playing sounds when the phone was in full silent mode.
- USB headphone adapter has what we call the "bimyou button" because we aren't quite sure exactly what it does. Pushing it once toggles play and pause. A long push does one of three things: 1) nothing, 2) skip to next song, 3) open the music player app.
- Taking screenshots (like the ones in this post) requires rooting your phone (which we did not do) or 1) installing the SDK, 2) a Java development environment like eclipse, 3) enabling debugging on the phone, and 4) connecting by USB (all of which we did do). Neither are viable options for those who are not comfortable with a command line. (It gets even more fun if you are running a 64 bit OS because the SDK requires a 32 bit version of SWT. But as you can see it can be done with some changes to the code and to Mac OS 10.6 snow leopard's Java prefs.)
From what we understand, Android automatically kills tasks and restarts them as resources are needed. Developers of individual apps may or may not code in a quit function. The typical way of closing an app seems to be simply returning to the home screen. But this does not always immediately kill the app. In fact, we can find no discernible pattern of behavior. Probably, if system resources are largely unused, the app is allowed to continue running. This is why a task manager is needed. We have been trying out both Advanced Task Killer (icon in task bar in above screen shot) and TasKiller (widget in upper right). Apple is probably right when they say that background apps eat battery power.
Google services integration
There are times when we wonder if we are supposed to use the dedicated app or the browser-based service to access Gmail or to get train directions. In the case of Gmail, we are at times forced to use the browser-based version due to push issues. With maps and directions, things get even murkier. First of all, there are currently two separate Google Map apps, Google Maps and My Maps Editor. Google Maps gives you directions, but does not allow you to place markers or view "my maps". Google Maps Editor lets you place markers and view my maps but does not give you directions. No one has any idea why these two apps are not combined into one. The only plausible explanation we can think of is that the memory footprint would be too large and cause other background services to be shut down (like the notification service for example).
For getting directions, the Google Map app available to Japanese users only provides driving directions, which is of no use to many that live in large cities. There is no way to get train or walking directions. To get this, the browser-based version must be used. However, there is a new mobile app available outside of Japan, v. 3.1.2. This app adds access to train, car, and/or walking directions. And It works in Japan (if you can download/find it). Japanese users reported that switching the system to English, removing the sim card, and connecting to the market over wifi, enabled finding and downloading the app. This no longer works (may work with a US proxy). If you are an android user looking for it, from your phone search for
And v 3.1.0 should be the first hit. This version has the improved functionality I mentioned. (DISCLAIMER: we don't know the checksum for the app on the market, so download at your own risk since you cannot verify it has no malware payload - it seems to come from a trustable source, but you never know. The MD5 sum for the app we downloaded is 50a394656d92b85d7671ea13e2a5b8aa) After downloading, click to install (you may need to allow installation from untrusted sources)
There are annoyances that anyone who has their phone set to an English environment will experience while using the Maps app to search Japan. This is not a problem with android itself but with Google. Compare the results for these two searches. In each one, 東京 (Tokyo) and 品川 (Shinagawa) were input.
search of google.co.jp and search of google.com
If we search from google.com, we start out in Fukuchu City (on the other side of Suginami Ward, in western Tokyo) from the parking lot of a rental mansion called Palace Mell (or was that Palace Smell). We end up at Shinagawa Station. In the Android example below, we started out at the Tokyo Prefectural Government building and ended up at Shinagawa Ward Hall.
Two work arounds exist, 1) setting your Android system language to Japanese, or 2) appending the kanji for station - eki 駅 - to the station name. The former always works. The later sometime picks up names of stores that contain "eki-mae" (駅前). Perhaps a savvy developer and write a nice piece of code that will force maps to access google.co.jp?
Gmail has a bug that causes names in Kanji to be ordered randomly. There is no fix for viewing properly ordered contacts on the PC version - even if you set your Gmail language to Japanese, the order will be wrong. (interestingly, though, the order changes but is still wrong.) This problem occurs in spite of having correctly entered phonetic readings - furigana 振り仮名. Google serves up this incorrect order to any device synced with it, including Apple Address Book. In the case of Apple Address Book, the phonetic readings are not received, which is probably why Address Book cannot properly sort the contacts. In the case of Android, the phonetic readings are indeed served to the phone, but if you system language is set to English, the order is random. Setting your system language to Japanese on the phone WILL fix the problem. Otherwise, you'll need to live with it or perhaps create a listed of starred contacts that you frequently call.