Just installed the new Android SDK - 2.3 and wondering where's "ADB"? Don't worry it's there.

In there recent release of the Android 2.3 codenamed "Gingerbread" the SDK's directory was a little restructured. In particular the ADB (Android debug bridge) the tool that is used to communicate with the Android emulator instances and connected device has been moved. Previously you could find it in the

path_to_your_Android_SDK_installation/tools

folder.

But since the Android 2.3 (or API 9) the /tools folder was renamed to /platform-tools folder, so if you are wondering why suddenly your >adb command does not work - this is the reason and updating the PATH should fix it.

Problem:

You are getting the following error:

android Error generating final archive: Debug certificate expired on ...

One day when you opened your Eclipse with Android tool chain installed, suddenly you see this error, which may seem weird because you know that Eclipse uses just some random certificate for debugging and so why is it expired and what to do.

The Solution:

Simply delete the keystore file which is located in

%USERHOME%/.android/debug.keystore (on Windows)

or

~/.android/debug.keystore (on Linux and OS X)

Restart your eclipse and you are all set.

Why this happens:

The reason to this is that the debug certificate is set to expire every year or 365 days.

If you do not wish to be bothered by this again in a year, you can use the keytool executable from the Android tool chain to generate a certificate with a longer expiration period.

In the following video, the web experience on the BlackBerry Playbook is compared to the web experience on the iPad. It is clearly shown (the video is made by RIM) that PlayBook significantly outperforms the iPad. While these tests are definitely subjective since they are performed by RIM, so they could choose website favorable to the PlayBook and otherwise objectively-subjectively give the PlayBook some edge, the interesting thing to note is that the PlayBook uses the open source WebKit browser initially developed by Apple. It is a very interesting camparo nevertheless.

Would be very interesting to see the Samsung Galaxy Tab running Android participate in this comparison, especially since it has the same 7" form factor as the PlayBook and it has Flash enabled of course.

Enjoy the video and let me know what you think!

Blackberry PlayBook vs. Apple iPad comparison:

After recent upgrade to my DokuWiki installation (I jumped from Mulled Wine straight to the latest release - Anteater)

I was getting this weird error:

call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'Doku_Renderer_metadata::section_edit' was given

the solution was to disable all the plugins and re-enable them again. Not sure why it worked, but it worked and the error is gone now! So if you experience the same error - try this. If it doesn't help, another good idea could be gradually re-enable plugins and see which one is the offender. Good Luck!

This is a great comics I came across, very  concise and true!

I especially liked the dinosaur. BlackBerry are dinosaur outdated both in the features and especially from the development perspective. I covered this before in my [intlink id="75" type="post"]Android vs. BlackBerry development post[/intlink].

Today, at the annual PDC10 conference, Microsoft is showing love for its developers and promoting its coming Windows Phone 7 by giving all the attendees a free Windows Phone 7. This follows in the steps of similar giveaways by Google at Google/IO 2009 and Goole/IO 2010, Motorola and Adobe giveaway at Adobe Max 2010. With many companies following Google's example, Google so far is by far the leading company on these giveaways.

Microsoft is expected to spend more than 400 millions on the promotion of its Windows Phone 7 . Here's hoping that registered and published developers will get a free phone or at least discounted phones since as of now, it is quite hard to get your hands on a a phone and this is obviously crucial to testing the apps in real live scenarios, on real hardware.

I needed recently to basically remove my app installation from the Windows Phone 7 emulator. I could not find how you can remove the app from the emulator, but I found a way to reset and force the Windows Phone 7 emulator to cold boot.

You can clear the windows phone emulator state, by deleting the saved state file in:

%ProgramData%\Microsoft\XDE\*.dess

You can just hit the windows key on your keyboard and paste this "%ProgramData%\Microsoft\XDE\" and you will be taken to the right location.

Delete the *.dess files. This will force the emulator to reset and run the cold boot sequence.

Too bad, it's not possible to do simulator reset right from the development tools. Here's hoping that Windows Phone Tools development team will improve that situation in the future releases.

Please share your thought in comments.

In a recent blog post, Google announced that it is significantly expanding payment support both for developers and the users.

Developers in 29 countries will be able to sell their apps and users from 32 countries will be able to buy paid apps. The most recently added countries in which the Android users will be able to buy apps are: Argentina, Belgium, Brazil, Czech Republic, Denmark, Finland, Hong Kong, India, Ireland, Israel, Mexico, Norway, Poland, Portugal, Russia, Singapore, Sweden, and Taiwan.

Addition to support of paid application distribution is expanded to the developers in the following countries: Argentina, Australia, Belgium, Brazil, Canada, Denmark, Finland, Hong Kong, Ireland, Israel, Mexico, New Zealand, Norway, Portugal, Russia, Singapore, South Korea, Sweden, Switzerland and Taiwan.

Android is closing the paid application gap with the iPhone quite fast, while BlackBerry still lags behind.