WWWJDIC for Android 2.1 Released

The newest release is now live in the Android Market. The highlights of this version are improved Japanese text-to-speech (TTS) and Android 4.0 (Ice Cream Sandwich, ICS) support.

Version 2.0 introduced Japanese TTS support using the free N2 TTS speech engine, but apparently (and unfortunately) it is not available from the Android Market outside of Japan. In 2.1 I've added support for two other major Japanese TTS engines: SVOX Japanese and AquesTalk TTS. You can now switch the Japanese TTS engine in the Settings screen, check out the screenshot below. The app doesn't check if the engine is actually installed, so you should install the relevant TTS package before changing the setting (if you select an engine that is not available, Japanese TTS support will be disabled throughout the app). Another improvement in this release: the settings screen is now using an action bar, courtesy of ActionBarSherlock v3.4.0.


Unfortunately, an API to list available TTS engines was only added in ICS, so currently there is no way to automatically find installed engines that support Japanese. If you think the engine you are using should be supported, drop me a line.

Another often requested feature is TTS support for example sentences. This is now available, just press the speaker button on the action bar:


The recently announced Android 4.0, a.k.a Ice Cream Sandwich (ICS), brings a lot of features previously available only on tablets to handsets as well. The most visible change is, of course, the redesigned UI, including native action bar support and slimmer tabs. WWWJDIC now follows the ICS display style of action bar on top of tabs in portrait mode, and has been optimized to look nice on ICS. More work on this will be done when I get an actual ICS device. Here's how the main screen looks when running on ICS:



And one last thing: not to blow my own horn, but WWWJDIC for Android 2.0 was voted best Honeycomb-compatible app on the recent Android Developers Lab follow-up event at Google Tokyo. Among other things, this means I get to go to Goole I/O next year :)

Comments

Post a Comment

Popular posts from this blog

Decrypting Android M adopted storage

Image
One of the new features Android M introduces is adoptable storage . This feature allows external storage devices such as SD cards or USB drives to be 'adopted' and used in the same manner as internal storage. What this means in practice is that both apps and their private data can be moved to the adopted storage device. In other words, this is another take on everyone's (except for widget authors...) favorite 2010 feature --  AppsOnSD . There are, of course, a few differences, the major one being that while AppsOnSD (just like app Android 4.1 app encryption ) creates per-app encrypted containers, adoptable storage encrypts the whole device. This short post will look at how adoptable storage encryption is implemented, and show how to decrypt and use adopted drives on any Linux machine. Adopting an USB drive In order to enable adoptable storage for devices connected via USB you need to execute the following command in the Android shell (presumably, this is not needed if your
Read more

Unpacking Android backups

Image
One of the less known new features introduced in ICS is the ability to backup a device to a file on your computer via USB. All you have to do is enable USB debugging, connect your phone to a computer and type the adb backup command in a shell. That will show a confirmation dialog on the phone prompting you to authorize the backup and optionally specify a backup encryption password. It looks something like this: This doesn't require rooting your phone and lets you backup application data, both user installed and system applications (APK's), as well as shared storage (SD card) contents. There are some limitations though: it won't backup apps that have explicitly forbidden backups in their manifest, it won't backup protected (with DRM) apps and it won't backup some system settings such as APN's and WiFi access points. The transfer speed is limited by ADB channel speed (less than 1MB/s), so full backups can take quite some time. There is also a rather annoying
Read more

Using app encryption in Jelly Bean

Image
The latest Android version, 4.1 (Jelly Bean) was announced last week at Google I/O  with a bunch of new features and improvements . One of the more interesting features is app encryption, but there haven't been any details besides the short announcement: 'From Jelly Bean and forward, paid apps in Google Play are encrypted with a device-specific key before they are delivered and stored on the device.'. The lack of details is of course giving rise to guesses and speculations, some people even fear that they will have to repurchase their paid apps when they get a new device. In this article we will look at how app encryption is implemented in the OS,  show how you can install encrypted apps without going through Google Play, and take a peak at how Google Play delivers encrypted apps. OS support for encrypted apps The previous version of this article was based on Eclipse framework source packages and binary system images, and was missing a few pieces. As Jelly Bean sour
Read more