Android Development Fundamentals: SQLite and Content Providers

The /res/raw directory is specifically designed for files that should NOT be compiled into binary format. Files placed here are copied to the device as-is. In contrast, /res/xml files are parsed and compiled into a binary XML format, and /res/layout files are also compiled into binary format during the build process.

An Intent in Android is a messaging object used to request an action from another app component, consisting of an action and associated data.

Linkify is a convenient Android utility class that helps turn regular text into clickable links, such as URLs and phone numbers, in TextView controls.

A PendingIntent wraps an Intent to be executed at a future time by another application, such as the notification manager or home screen widget manager.

In Android, the extras associated with an Intent are retrieved using the Intent.getExtras() method, which returns a Bundle containing the key-value pairs. There is no getIntentExtras() method on Intent, making Intent.getExtras() the correct choice.

When Android starts up, it scans for activities that have the CATEGORY_LAUNCHER intent filter in their manifest. These activities are the app's entry points. Android displays their icons and names on the home screen (launcher), allowing users to tap them to launch the application. This is correct behavior.

SQLite3 in Android is implemented as a compact C library that's included as part of the Android software stack. This is correct - SQLite is written in C and embedded into Android through JNI (Java Native Interface). It's not a Java library or C++ library.

In SQLite3 and Android best practices, large files like bitmaps or audio files are typically NOT stored directly within database tables as BLOBs. Instead, they're stored in the file system, and only the file path or URI is stored in the database. This approach is more efficient, avoids database bloating, and is easier to manage.

The -e option in the Android Debug Bridge (adb) command-line tool directs the command to the only running emulator instance. Conversely, the -d option is used to direct commands to a connected real USB device, making the emulator option correct.

ContentValues is a class used to store a set of values that a ContentResolver can process. When inserting new rows into database tables using SQLiteDatabase.insert(), you pass a ContentValues object containing the column names and values for the new row. This is the correct and standard way to insert data.

SQLite uses dynamic typing (manifest typing) by default, meaning that a value's datatype is associated with the value itself, not its column. You can store any datatype in any column, meaning strict type checking is not enforced, making the statement false.

Android's native content providers include Browser (for bookmarks/history), MediaStore (for audio/video/images), and Contacts (for contact information). CallIndex is not a standard Android content provider. Option F correctly identifies these three native providers.

Content providers in Android must be declared within the application's manifest file using the provider tag so the system knows about their existence and permissions.

AIDL (Android Interface Definition Language) is Android's interface-based IPC mechanism that defines the programming interface that both the client and service agree upon. It enables communication between processes with method calls similar to local Java interfaces.

In a content URI like content://contacts/people/3, the 'authority' is 'contacts'. The authority uniquely identifies the content provider and is typically the package name or a custom string. It appears after the 'content://' scheme.

Both ContentUris.withAppendedId() and Uri.withAppendedPath() are static helper methods that can append an ID to a ContentProvider URI. ContentUris.withAppendedId() is specifically designed for content URIs and is the preferred approach.

Content providers MUST be declared in the AndroidManifest.xml file to be visible to the Android system. Undeclared content providers cannot be accessed by other applications or even discovered by the system.

Both ContentResolver.query() and Activity.managedQuery() return a Cursor object and accept the same parameters (URI, projection, selection, selectionArgs, sortOrder). managedQuery() is deprecated but was commonly used in older Android code.

ContentResolver acts as a client-side API but requests are NOT automatically forwarded. The ContentResolver matches the URI's authority to the appropriate ContentProvider using the system's content provider registry, then forwards the request.

When data doesn't need to be shared between applications, you can use SQLite database directly without implementing a ContentProvider. ContentProviders add overhead and are only necessary for cross-app data sharing.