alternative for package

by ashish » Thu, 12 Mar 2009 06:54:50 GMT

Sponsored Links
 hello everybody,

does anybody know what  is alternative package for because this is not supported on sdk1.0.

i am unable to find it??
please help...


Other Threads

1. ERROR:- no such table: TABLE: , while compiling: SELECT _id, network, url FROM TABLE


I have followed the instructions from this site to the letter
but to no avail. Each time I run the code suggested, the Eclipse de{*filter*}
keep throwing the following error
no such table: TABLE: , while compiling: SELECT _id, network, url FROM

I created the database using SQLite Browser and ran the emulator's shell and
can see that the database was there.

Here is the code that I am implementing to manage the database:
package com.rodney.IET_Events_Widget;


import android.content.Context;
import android.database.Cursor;
import android.database.SQLException;
import android.database.sqlite.SQLiteDatabase;
import android.database.sqlite.SQLiteException;
import android.database.sqlite.SQLiteOpenHelper;

public class DataBaseHelper extends SQLiteOpenHelper {

     //The Android's default system path of your application database.
    private static String DB_PATH             =
    private static final String DB_NAME     = "local_network_db";
    private static final String DB_TABLE     = "local_network";
    public static final String KEY_NETWORK     = "network";
    public static final String KEY_URL         = "url";
    public static final String KEY_ROWID     = "_id";
    private SQLiteDatabase myDataBase;
    private final Context myContext;

     * Constructor
     * Takes and keeps a reference of the passed context in order to access
to the application assets and resources.
     * @param context
    public DataBaseHelper(Context context) {

        super(context, DB_NAME, null, 1);
        this.myContext = context;

     * Creates a empty database on the system and rewrites it with your own
     * */
    public void createDataBase() throws SQLException{

        boolean dbExist = checkDataBase();

            //do nothing - database already exist

            //By calling this method and empty database will be created into
the default system path
            //of your application so we are gonna be able to overwrite that
database with our database.

            try {


            } catch (IOException e) {

                throw new Error("Error copying database");



     * Check if the database already exist to avoid re-copying the file each
time you open the application.
     * @return true if it exists, false if it doesn't
    private boolean checkDataBase(){

        SQLiteDatabase checkDB = null;

            String myPath = DB_PATH + DB_NAME;
            checkDB = SQLiteDatabase.openDatabase(myPath, null,

        }catch(SQLiteException e){

            //database does't exist yet.


        if(checkDB != null){



        return checkDB != null ? true : false;

     * Copies your database from your local assets-folder to the just
created empty database in the
     * system folder, from where it can be accessed and handled.
     * This is done by transferring bytestream.
     * */
    private void copyDataBase() throws IOException{

        //Open your local db as the input stream
        InputStream myInput = myContext.getAssets().open(DB_NAME);

        // Path to the just created empty db
        String outFileName = DB_PATH + DB_NAME;

        //Open the empty db as the output stream
        OutputStream myOutput = new FileOutputStream(outFileName);

        //transfer bytes from the inputfile to the outputfile
        byte[] buffer = new byte[1024];
        int length;
        while ((length =>0){
            myOutput.write(buffer, 0, length);

        //Close the streams


    public void openDataBase() throws SQLException{

        //Open the database
        String myPath = DB_PATH + DB_NAME;
        myDataBase = SQLiteDatabase.openDatabase(myPath, null,


    public synchronized void close() {

            if(myDataBase != null)



    public void onCreate(SQLiteDatabase db) {


    public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion)


     * Return a Cursor over the list of all notes in the database
     * @return Cursor over all notes

    public Cursor fetchAll() {
        return myDataBase.query("local_network", new String[] {KEY_ROWID,
KEY_NETWORK,KEY_URL}, null, null, null, null, null);


And here is the code for the implementation in my ListView Activity:

public void onCreate(Bundle savedInstanceState) {
        mDbHelper = new DataBaseHelper(this);
        Intent intent = getIntent();
        Bundle extras = intent.getExtras();
        if (extras != null) {
            mAppWidgetId = extras.getInt(


private void fillData() {
            // Get all of the rows from the database and create the item
            mNetworkCursor = mDbHelper.fetchAll();

            // Create an array to specify the fields we want to display in
the list (only TITLE)
            String[] from = new String[]{DataBaseHelper.KEY_NETWORK};

            // and an array of the fields we want to bind those fields to
(in this case just text1)
            int[] to = new int[]{};

            // Now create a simple cursor adapter and set it to display
            SimpleCursorAdapter iet_networks =  new
SimpleCursorAdapter(this, R.layout.ln_rows, mNetworkCursor, from, to);

Any clues or help will be greatly appreciated, let me know if more detail is

Many thanks in advance



2. You should use query bindings with "?" in SQLite

I found this error message interesting.  I have only seen it on an
Android 2.2 device.

"Reached MAX size for compiled-sql statement cache for database /data/
data/; i.e., NO space for this
sql statement in cache: UPDATE cse SET updatetime=? WHERE
slug='My_slug'. Please change your sql statements to use '?' for
bindargs, instead of using actual values."

Guess I have some re-writing to do...


3. Galaxy S Video Out on Action.

4. Market question about copy protection

5. review SAMDROID TURBO (backported DVM 2.2)

6. Blepak TSel Galaxy

7. File operations extremely slow on emulator - emulator is unusable.