Luckily, I am not the first one to find it, and could find a solution in an Android Group :

cp /etc/udev/rules.d/50-android.rules /etc/udev/rules.d/51-android.rules

/etc/init.d/udev reload

Just don’t forget to disconnect and plug-in the device again, and there you go.

Published on the Android Google blog, an early 1.5 API release is available. The blog warns that certain APIs may change before formal release.

What is new?

For a complete list, please refer to this list (not a formal release notes).

Highlights are:

• Soft Keyboard (finally!!!)
• UI enhancement for most of Google Applications
• Video Recording
• Stereo Bluetooth support

Can’t wait till HTC release their formal Android 1.5 binaries, and I am certain Samsung will release Android 1,5 with touch screen only. Let’s wait and see.

Google code project homepage : http://code.google.com/p/nubi/

Blog: http://nubinewsblog.blogspot.com/

The writer uses the name Mattaku Betsujin, which can be translated from Japanese to: Honestly, another person.

Android Group Japan website and Google Group are trying to bring together Japanese developers and support each other.

Twitters use the acronymos #agj for Android Related Discussions, and there many of them. 

Several books are already available:

Since I couldn’t help but test if my Android applications still work, I immediately upgraded according to the instructions: new SDK, version notes,  and instructions.

ADT plugin was not upgraded as Eclipse couldn’t find an update.

Outcome:

Applications run without any modification.

Conclusions:

1) I did not use any of the APIs that were changed .

2) Android API is “settling” down. (Or Google finally understood the pain the cause developers each time they change it).

Just bumped into zxing project, and wanted to share.

According the Project Home page:

ZXing (pronounced “zebra crossing”) is an open-source, multi-format 1D/2D barcode image processing library implemented in Java. Our focus is on using the built-in camera on mobile phones to photograph and decode barcodes on the device, without communicating with a server. We currently have production-quality support for:

• UPC-A and UPC-E
• EAN-8 and EAN-13
• Code 39
• Code 128
• QR Code

Now I have to think of an implementation that will use QR Codes…

According to Google:

Coming Soon: Internationalization and Localization are critical, but are also not quite ready yet in the current SDK. As the SDK matures, this section will contain information on the Internationalization and Localization features of the Android platform. In the meantime, it is a good idea to start by externalizing all strings, and practicing good structure in creating and using resources.

It does seem Google Android is lacking in that respect. Since the 2Chan browser is mostly about Japanese, it may force me to write some more code.

The Android Logo (AKA Droid Robot) was modified. Original logo is shared by Google and used according to terms described in the Creative Commons 2.5 Attribution License.

I am sorry to announce that the Html project is postponed to a later date.

Would like to complete the 2Chan browser as soon as possible, and although an Html parser would have been nice, it is not really necessary. For the 2chan browser, the parser required is quite simple and can be accomplished by a dedicated parser.

Again, sorry, and I do promise to continue this project at a later date.

One more comment on Nekohtml: If you are familiar with it, you know it requires Xerces, therefore the porting project should start from that. There is a guy who claimed he has done that, but I couldn’t find any link to the ported lib.

The Android Logo (AKA Droid Robot) was modified. Original logo is shared by Google and used according to terms described in the Creative Commons 2.5 Attribution License.