android-runtime

Jumping straight to the topic, Android L introduces a ART as default runtime. I have a Sample Application, basically a document viewer. Most of the document viewing code including back buttons, Search,etc are written in C and the Android App uses JNI interface. I updated my code to make it build for Android L and it seems to open the document just fine. However, when pressing back button and closing the document, the Application seem to crash and the following backtrace is seen: I/DEBUG ( 1390): Abort message: 'art/runtime/check_jni.cc:65] JNI DETECTED ERROR IN APPLICATION: JNI CallIntMethodV

I am heard that now Google start using ART, a new run-time for executing Android app and its come with Android 4.4 (in some devices). Now I am just want to confirm that, is pro-grammatically any changes are required or not in existing application or their is any criteria for making new application i.e. run on Dalvik but also compatible with ART ? I am heard that now Google start using ART, a new run-time for executing Android app and its come with Android 4.4 (in some devices) ART is not enabled by default on Android 4.4. It is enabled by default on the "L" Developer Preview. It probably will

After recent update of my application in Google Play, I started receiving lot of crash reports, all of them are from Samsung devices with Android 5. Lower android versions work fine and devices of other manufacturers with Android 5 work fine too. I don't have any device where I could reproduce the issue, so I can't bisect. I am trying to deduce what could be wrong from the crash report and from list of changes since my last working version (which is unfortunately long). All the crash reports look like this (just the addresses slightly vary between devices): Build fingerprint: 'samsung/kltektt

Is .apk file based installation supported on Tizen Os ? The native applications of both are entirely different, .apk for android coded in Java and .tpk for Tizen coded in C++. So its impossible to directly instal .apk files in Tizen. But OpenMobile has created an application named ACL for Tizen which will run almost any android applications in Tizen platform. First you will have to install the application in the Tizen device and you have to load the apk within the ACL application. No it is not supported directly, although there are some third-party emulators. Tizen supports its own format .tpk

I've got a warning in my logcat: W/art: Verification of void com.myapp.LoginFragment$override.lambda$logIn$5(com.myapp.LoginFragment, java.lang.Throwable) took 217.578ms Here's the code: subscription = viewModel.logIn() .observeOn(AndroidSchedulers.mainThread()) .subscribe( this::showStudioSelection, error -> { ErrorResponse errorResponse = ErrorResponseFactory.create(error); if (errorResponse.code() == ApiResult.BAD_REQUEST) { Snackbar.make(getView(), R.string.login_bad_credentials, Snackbar.LENGTH_LONG) .setAction(android.R.string.ok, v -> {}) .show(); } else { Snackbar.make(getView(),

We know that Dalvik uses APK, DEX, and ODEX files. And we know this abbreviation means via AOSP source or Developers site. (like this - https://source.android.com/devices/tech/dalvik/dex-format.html ) DEX means Dalvik EXcutable file. ODEX means Optimized Dalvik EXcutable file. APK means Android PacKage. ART (Android RunTime) uses OAT and ART, but they do not explain the meaning anywhere. Does anyone know the meaning of these shortened words? It’s O f A head Time , a silly reordering of A head O f T ime. We went with that because then we say that process of converting .dex files to .oat files