Homescreen Widget Service
try {
    FileInputStream input = new FileInputStream(file);
    bitmap = BitmapFactory.decodeStream(input);
    try {
        input.close();
    } catch (IOException e) {
        // TODO Auto-generated catch block
        Log.e(TAG, e.getMessage());
    }
} catch (FileNotFoundException e) {
    Log.e(TAG, e.getMessage());
}



If decodeStream throws an exception the stream won't be closed. A proper solution is the following:

try {
    FileInputStream input = new FileInputStream(file);
    try {
        bitmap = BitmapFactory.decodeStream(input);
    } finally {
        input.close();
    }
} catch (FileNotFoundException e) {
    Log.e(TAG, e.getMessage());
} catch (IOException e) {
    Log.e(TAG, e.getMessage());
}


Or this:

try {
    FileInputStream input = new FileInputStream(file);
    try {
        bitmap = BitmapFactory.decodeStream(input);
    } finally {
        input.close();
    }
} catch (IOException e) {
    Log.e(TAG, e.getMessage());
}


(Since FileNotFoundException is a subclass of IOException).

AQuery aq;



I guess this field could be private. (Should I always use the private access modifier for class fields?; Item 13 of Effective Java 2nd Edition: Minimize the accessibility of classes and members.)

private String roseUrl;
...
private File ext;



These field is used only in one method (onStart and sacCb). They could be local variables instead. (Effective Java, Second Edition, Item 45: Minimize the scope of local variables)

public void xml_ajax() {



This method name does not follow the usual camelCase conventions and it should be a verb. From Code Conventions for the Java Programming Language:


  Methods should be verbs, in mixed case with the first letter
  lowercase, with the first letter of each internal word capitalized.

I'd use longer and more descriptive variable names (which explains their purpose) for better readability than this ones:


XmlDom r = xml.tag("reportrose");
...
String s = status.getMessage();
int i = status.getCode();
String e = s + " | Status Code: " + i;
...
String lm = dlm.toLocaleString();



Longer names would make the code more readable since readers don't have to decode the abbreviations every time and when they write/maintain the code don't have to guess which abbreviation the author uses.

private Bitmap getRose() {
    Bitmap bitmap = null;
    try {
        FileInputStream input = new FileInputStream(file);
        try {
            bitmap = BitmapFactory.decodeStream(input);
        } finally {
            input.close();
        }
    } catch (IOException e) {
        Log.e(TAG, e.getMessage());
    }
    return bitmap;
}



You can get rid of the bitmap variable here if you return immediately:

private Bitmap getRose() {
    try {
        FileInputStream input = new FileInputStream(file);
        try {
            return BitmapFactory.decodeStream(input);
        } finally {
            input.close();
        }
    } catch (IOException e) {
        Log.e(TAG, e.getMessage());
    }
    return null;
}


See Guideline 1-2: Release resources in all cases in Secure Coding Guidelines for the Java Programming Language

String lm = dlm.toLocaleString();



This method is deprecated, you should use something else.

// TODO Auto-generated catch block



Comments like this doesn't seem like professional work. Solve the issues and remove the comments.