Cupid-4-Stupid for the NOOK – Comming Soon!

I was working on Cupid-4-Stupid for the Nook Color and Nook table for a while; however, there is a big difference between testing the application in the Nook emualtor and test the application in the real device.

After coming back from my trip to Argentina, I got a wonderful surprise. My friend David gave me a brand new Nook Color!

My first step was to do the registration at the Nook developer website (

My second step was to obtain a file with the name ‘provision.cmd’. This file must be uploaded to the Nook Color in order to enable the developer mode.
The developer mode allows the ADB to detect the Nook Color and upload your application APK for testing.

To obtain the provision.cmd file normally you would go to the Developer Mode form inside the website (after login in).
You must fill the form with the serial number of your Nook and in return the form would give you a file provision.cmd.
Be aware that this file only enable your device for develop mode only for 180 days. After you must repeat the process.

I must confess that this second step didn’t work for me. The Developer Mode form was not recognising my Nook Color’s serial number.
It took me two weeks to obtain this file. First, I chat with technical support. Technical support provide me a 1-800 number.
I called the 1-800 number. I have to talk with four people until someone understood that I was trying to test my application on the Nook instead of trying to root (hack) the device.
The last person provide me an email:
After going back and forward, they were nice enough to send me the file I needed.
I hope that now the Developer Mode form is working properly in case I need to do more testing in 180 days.


Here are some pictures of how the application is looking in the Nook Color:

Leave a comment

Dealing with WebView for Android

In the application Cupid-4-Stupid that I and my partner David W. Corrigan developed, we notice that WebView stopped working properly.
When WebView stopped working as before, two important sections of our application were affected: Date Ideas and Panic Button.

I was getting exceptions such as NullPointerException produced by android.webkit.WebViewDatabase.getInstance() at
After fixing this issue, we encounter other exceptions produced by CookieSyncManager.createInstance(Context) and more.

However, after doing some research, we managed to pin point the issue and fixed.

The following is a tutorial about how to create your own browser using WebView and make it work:
We assume that the browser is going to be an activity that will be called from another activity; however, that doesn’t mean that it cannot be your main activity if you wish.

  1. In your AndroidManifest.xml:
    1.  Add the following code before or after the ‘application’ tag:
      <uses-permission android:name='android.permission.INTERNET' />
    2. Next, add your browser activity tag.
      <activity android:name='com.hourglass.applications.BrowserActivity'
      		<action android:name='com.hourglass.applications.Browser' />
      		<action	android:name='android.intent.action.VIEW' />
      		<category android:name='android.intent.category.DEFAULT' />
      		<data android:scheme='http' />
  2. Create the layout for your browser.
    Notice that we identify the root linear layout as ‘linearLayoutRootWebView’ and our WebView as ‘webview’. Both ids are important.

    <?xml version='1.0' encoding='utf-8'?>
    <LinearLayout android:id='@+id/linearLayoutRootWebView' xmlns:android=''
    	<WebView android:id='@+id/webview'
  3. In your main activity under onCreate() method, add the following line at the end:
    This is part of the solution to solve the exception created by CookieSyncManager.createInstance(Context).

  4. Here is the most important part, your browser activity:
    First, you should notice that we added CookieSyncManager.getInstance().startSync(); inside onResume() method, and CookieSyncManager.getInstance().stopSync(); inside onStop() method. Again, this is to prevent the exception created by CookieSyncManager.createInstance(Context). Plus, using this method makes the loading of our pages more efficient.
    Second, the method setUpWebView() is the most important part. We tried using webview = (WebView) findViewById(; and other examples; however, replacing the webview provided by the resources by a webview generated by code seems to work and not generate any exceptions.

    package com.hourglassapplications;
    import android.content.DialogInterface;
    import android.content.DialogInterface.OnCancelListener;
    import android.os.Bundle;
    import android.view.KeyEvent;
    import android.view.View;
    import android.view.ViewGroup;
    import android.view.Window;
    import android.webkit.CookieSyncManager;
    import android.webkit.WebChromeClient;
    import android.webkit.WebView;
    import android.webkit.WebViewClient;
    import android.widget.Button;
    public class BrowserActivity extends ActivityWithMenu {
    	private static final String TAG = 'BrowserActivity';
    	final Activity activity = this;
    	private static ProgressDialog progressBar;
    	private ViewGroup viewGroupRootWebView;
    	private View viewToRemove;
    	private WebView webview;
    	public void onCreate(Bundle savedInstanceState) {
    		this.getWindow().requestFeature(Window.FEATURE_PROGRESS); // Must be called before setContentView
    	private void setUpWebView(){
                    // Identify the webview provided by the resources and replace it with a webview generated by code
    		viewGroupRootWebView = (ViewGroup) this.findViewById(;
    		viewToRemove = viewGroupRootWebView.findViewById(;
    		int indexView = viewGroupRootWebView.indexOfChild(viewToRemove);
    		webview = new WebView(this);
    		viewGroupRootWebView.addView(webview, indexView);
    	private void setUpWebViewSettings(){
    	private WebChromeClient newWebChromeClient(){
    		return new WebChromeClient() {
    			public void onProgressChanged(WebView view, int progress){
    				activity.setProgress(progress * 100);
    				if(progress == 100){
    	private WebViewClient newWebViewClient() {
    		return new WebViewClient(){
    			public void onReceivedError(WebView view, int errorCode, String description, String failingUrl){
    				Log.e(TAG, 'onReceivedError(..., ' + errorCode + ', ' + description + ', '+ failingUrl + ')');
    			public boolean shouldOverrideUrlLoading(WebView view, String url) {
    				return true;
    			public void onPageFinished(WebView view, String url) {
    				if (progressBar != null && progressBar.isShowing()) {
            private void loadUrl(String strUrl){
    	public boolean onKeyDown(int keyCode, KeyEvent event) {
                    // If there is a web page history, go to the previous page, else follow up the system behavior
    		if ((keyCode == KeyEvent.KEYCODE_BACK) && webview.canGoBack()) {
    			return true;
    		return super.onKeyDown(keyCode, event);
    	private void setUpProgressBar(){
    		progressBar = new ProgressDialog(this);
    	private final OnCancelListener progressBarOnCancelListener = new OnCancelListener() {
    		public void onCancel(DialogInterface arg0) {
    			if (progressBar != null && progressBar.isShowing()) {
    	public void onResume(){
    	public void onStop(){
    	public void onDestroy(){

Let me know if you encounter a problem.

Leave a comment

Cupid-4-Stupid New Update – Version 1.4

Today, November 28 of 2011, we released a new update of Cupid-4-Stupid!

Some customers reported a bug that they were facing when trying to access content in Date Ideas and Panic Button sections.

This bug was produced after all the Android devices got updated.

After working around we found out what was the problem and solve it. Soon, we will release a more detail explanation of how we solve it.

Get Cupid-4-Stupid here:

Leave a comment

Adding BugSense to Cupid-4-Stupid for Android

We are adding BugSense to Cupid-4-Stupid ( for Android. 

BugSense ( is a bug tracking service for Android, iOS, and WP7 which works wonders with ACRA 4.2.3.

We added BugSense after encounter an error with ACRA in which was crashing the application.

The code was failing when trying to initialize acra:

			ACRA.init(this); // The following line triggers the initialization of ACRA
		}catch(RuntimeException e){
			android.util.Log.e(TAG, 'ACRA init crashes: ' + e.getMessage());

Getting the following error:

10-30 22:02:37.908: WARN/System.err(2709): java.lang.NullPointerException
10-30 22:02:37.918: WARN/System.err(2709):     at org.acra.ErrorReporter.init(
10-30 22:02:37.918: WARN/System.err(2709):     at org.acra.ACRA.initAcra(
10-30 22:02:37.918: WARN/System.err(2709):     at org.acra.ACRA.init(
10-30 22:02:37.918: WARN/System.err(2709):     at com.hourglass.applications.MyApplication.onCreate(
10-30 22:02:37.918: WARN/System.err(2709):     at
10-30 22:02:37.928: WARN/System.err(2709):     at
10-30 22:02:37.928: WARN/System.err(2709):     at$2900(
10-30 22:02:37.928: WARN/System.err(2709):     at$H.handleMessage(
10-30 22:02:37.928: WARN/System.err(2709):     at android.os.Handler.dispatchMessage(
10-30 22:02:37.928: WARN/System.err(2709):     at android.os.Looper.loop(
10-30 22:02:37.928: WARN/System.err(2709):     at
10-30 22:02:37.928: WARN/System.err(2709):     at java.lang.reflect.Method.invokeNative(Native Method)
10-30 22:02:37.938: WARN/System.err(2709):     at java.lang.reflect.Method.invoke(
10-30 22:02:37.938: WARN/System.err(2709):     at$
10-30 22:02:37.938: WARN/System.err(2709):     at
10-30 22:02:37.938: WARN/System.err(2709):     at dalvik.system.NativeStart.main(Native Method)

After spending long hours I found how that the error was produced when ErrorReporter class was not initialized.
For some reason ACRA 4.2.3 doesn’t pass the reference of the class (this) to ErrorReporter.

To fix it just implement the following:

ErrorReporter.getInstance().init(this); // include before ACRA.init(this);


Leave a comment