android-4.4-kitkat

Google added a new ART runtime with Android 4.4. How can I determine whether ART or Dalvik is the current runtime? Update At least, as early as June 2014 Google has released an official documentation on how to correctly verify the current runtime in use : You can verify which runtime is in use by calling System.getProperty("java.vm.version"). If ART is in use, the property's value is "2.0.0" or higher. With that, now there is no need to go through reflection and simply check the corresponding system property: private boolean getIsArtInUse() { final String vmVersion = System.getProperty("java

When using the translucent status and navigation bars from the new Android 4.4 KitKat APIs, setting fitsSystemWindows="true" and clipToPadding="false" to a ListView works initially. fitsSystemWindows="true" keeps the list under the action bar and above the navigation bar, clipToPadding="false" allows the list to scroll under the transparent navigation bar and makes the last item in the list scroll up just far enough to pass the navigation bar. However, when you replace the content with another Fragment through a FragmentTransaction the effect of fitsSystemWindows goes away and the fragment

Hi in my application I am accepting pass code from user and storing it in shared preferences. And, I have provided pass code on/off functionality. If user checked on , app will ask user to enter pass code at the time of launch every time and will be off on checked of Off button. Everything is working fine on android's ICS, Jellybean version and below. But it never works on Kitkat. Unfortunately, I don't have a Kitkat device to debug my app. Below is the my code I am using for shared preferences:- SharedPreferences sharedPreferences; //sharedPreferences = getActivity().getSharedPreferences(

I am working on an Android tablet application that is being used by law enforcement. I had the tablet backup all the data to an external SD card. I wanted to be able to recover data from the card in case the tablet got destroyed while the police officers were fighting crime. I used this code to store the backup: File file = new File("/mnt/extSdCard/" + NewOrLoad.directoryName + "settings.dat"); try { bW = new BufferedWriter(new FileWriter(file)); Gson gson = new Gson(); String json = gson.toJson(dreform); bW.write(json); bW.close(); } catch (IOException e) { e.printStackTrace(); }

I am passing image url to the following method private void performCrop(Uri imageUri){ try { Intent intent = new Intent("com.android.camera.action.CROP"); // intent.setType("image/*"); intent.setDataAndType(imageUri, "image/*"); List<ResolveInfo> list = getActivity().getPackageManager().queryIntentActivities( intent, 0 ); int size = list.size(); if (size >= 0) { intent.setData(imageUri); intent.putExtra("crop", "true"); intent.putExtra("aspectX", 0); intent.putExtra("aspectY", 0); intent.putExtra("outputX", 150); intent.putExtra("outputY", 150); intent.putExtra("scale", true); intent.putExtra(

I am using two phones, Galaxy Nexus(JellyBean) and Nexus 5(KitKat). I am trying to execute a script which exists in /data/folder/scripts/run.sh I use Process.Builder to build the command. This command is built by getting Environment.getDataDirectory().toString() + "/folder/scripts/run.sh" There are no issues running this on the Galaxy Nexus but when I run it on the Nexus 5, I catch an exception when I run the process.start(). The output which I get contains: Error running exec(). Command: [/data/folder/scripts/run.sh, "param"]. Working directory: null Environment: [ADNROID_ROOT=/system ... ]

I would like to create NFC Payment Application based on Android Kitkat 4.4 which now support the NFC Card Emulation Mode for both not involving secure element and involving secure element. I would like to let My Application involve a secure element. So, I have a question. The Android KitKat can let my application access to the java card applet which is installed into a secure element? No, while the Android HCE documentation lists the possibility to use secure element-based card emulation, there are several problems hindering the use of a secure element in current devices: Nexus devices have a