android-4.2-jelly-bean

I'm just trying to implement a color picker for my android application, and ran into a strange issue on Android 4.1.1. The following code does not create the expected gradients on Android 4.1.1, but it does on 2.3.7: Shader fadeInRight = new LinearGradient(0, 0, pWidth, 0, 0x00000000, 0xFF000000, Shader.TileMode.CLAMP); Shader blackToWhite = new LinearGradient(0, 0, 0, pHeight, 0xFF000000, 0xFFFFFFFF, Shader.TileMode.CLAMP); Shader whiteMask = new ComposeShader(blackToWhite, fadeInRight, PorterDuff.Mode.DST_IN); Shader blackToColor = new LinearGradient(0, 0, pWidth, 0, 0xFF000000, hue, Shader

My application was working perfectly on my Android 2.2 emulator. I then decided to test on an Android 4.1 emulator. The DatePickerDialog looks a little different and for some reason when I press on "Done", the onDateSet() listener gets called twice and causes problems in my application. I know this because the log shown below in the code is printed twice whenever I click on "Done" mDateSetListener = new DatePickerDialog.OnDateSetListener() { @Override public void onDateSet(DatePicker view, int year, int monthOfYear, int dayOfMonth) { Log.v("onDateSet", "ENTERED"); //rest of code... }}; Android

I am working on an app, which can run on Froyo as well as JellyBean . I have a class that extends PageTransformer as below: import android.support.v4.view.ViewPager.PageTransformer; import android.view.View; public class ZoomOutPageTransformer implements PageTransformer { private static float MIN_SCALE = 0.85f; private static float MIN_ALPHA = 0.5f; public void transformPage(View view, float position) { int pageWidth = view.getWidth(); int pageHeight = view.getHeight(); if (position < -1) { view.setAlpha(0); } else if (position <= 1) { float scaleFactor = Math.max(MIN_SCALE, 1 - Math.abs

In my Android app I enable my specific app-search to be triggered via the search key in a number of my activities using this mechanism from the manifest <meta-data android:name="android.app.default_searchable" android:value=".Search.SearchActivity" /> with the appropriate search activity. This all worked fine until recently. With the Jelly Bean update the Search Key now always starts Google NOW search functionality. On this site: http://www.android.com/about/jelly-bean/ I found in the "Google Search" section this statement: "For devices with a hardware search key, you can tap it to launch

Im developing an app with the latest android version (4.2.1 API-Level 17) for tablets with multiuser capabilities. I want to restrict certain features (like the access to the app preferences) to the owner of the tablet (that is the user who can add and remove other user accounts) is there any way i can find out if the current user is the owner? i read through the UserManager and UserHandle API docs but couldn't find a function that allows me to check for it. have i missed something or is there another way to do that? Similar but without reflection: static boolean isAdminUser(Context context) {

My webview app works fine with touchend events in android version older than Jelly Bean. But in Jelly Bean, the touchend events are not reliable. Especially on divs that are scrollable, the touchend events are not fired sometimes and the whole app stops responding to any touchend events and I get the Log message with the tag "webcoreglue" and text "Should not happen: no rect-based-test nodes found" Now after i scroll even little bit, it starts responding to touchend normally. Pls help. HTML <div id="srpanel" class="panel"> <div class="main sr-list"> <div class="sr-list-item-action"> </div> <

I am developing an app that needs to use both wifiLock and wakeLock so the audio streaming when the screen is off does not get disturbed. I have tried my app on Android 2.3 and wakeLock and looks like wifiLock work as expected so there is no difference between when the screen is on or off, but the same app on Android 4.2 (Jelly-bean) when the screen goes off is not working as well and the audio gets choppy which shows either wakeLock or wifiLock are not working correctly. Is there any reason for this? Here is how I acquire and release the locks, in my main activity I have: @Override public