android-4.4-kitkat

I update android-studio 3.0 from canary 5 to canary 6 and suddenly My app gives crash on KitKat(API 19) with below stacktrace. The Main2Activity.java:10 line is the first line in my activity onCreate() method. 07-11 13:00:39.523 8913-8913/dcpl.com.myapplication E/AndroidRuntime: FATAL EXCEPTION: main Process: dcpl.com.myapplication, PID: 8913 java.lang.RuntimeException: Unable to start activity ComponentInfo{dcpl.com.myapplication/dcpl.com.myapplication.Main2Activity}: android.content.res.Resources$NotFoundException: Resource ID #0x7f070058 at android.app.ActivityThread.performLaunchActivity

I'm currently using immersive mode (API 19) for one of my Activities as follows: getWindow().getDecorView() .setSystemUiVisibility( View.SYSTEM_UI_FLAG_LAYOUT_STABLE | View.SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION | View.SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN | View.SYSTEM_UI_FLAG_HIDE_NAVIGATION | View.SYSTEM_UI_FLAG_FULLSCREEN | View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY | View.INVISIBLE); This hides the system buttons and notification bar until the user swipes for them back. This works fine, however I wish to detect when the user makes the buttons visible again. I've tried a

I have a background service which is running in kitkat always throwing Waited long enough for: ServiceRecord message in the logcat. But in the previous versions of android my app is running smoothly without any issues. also Sometimes my service is automatically killed in the Kitkat. This is caused by "Serialize running of background services" modification for ActivityServices. Implement #10744011: Serialize running of background services Added some code to the activity manager to keep track of services that are launching and limit the number that can be launched concurrently. This only comes

As of Kitkat (4.4) Android reports that my app is "High battery use". I use Network Location as well GPS. If I disable GPS, then it seems the app gets marked as "Low battery use". I'm wondering if there are any tips to using GPS while keeping the "Low battery use" label. Perhaps if you poll infrequently enough - or is it hardcoded to GPS = battery killer? EDIT: I understand that changing those parameters will conserve battery life. My question was more of whether Android will recognize these attempts at battery life conservation or will it simply brand my app as high power usage simply because

I am having an odd issue where my audio file sometimes plays and sometimes does not play. The catch is that when it decides to not play, the DDMS gives me an: E/MediaPlayer﹕ Should have subtitle controller already set Because this is one-to-one with the music not playing, I have determined that this is probably the issue... If the music is not playing and I hit the volume button it begins to play. If I wait about 30 seconds of no-play, it begins to start again (not looping). Whats going on here? I am on KitKat using player = new MediaPlayer(); AssetFileDescriptor afd = null; try { afd =

After installing the new ADT (22.3.0.v201310242005-887826) which supports Android 4.4 (KitKat), I keep getting the error as shown here: An internal error has occurred In the list of errors, I see multiple items of "RenderPreview", and when I click on any of them, I see: An internal error has occurred. After scene creation, #init() must be called When testing the new ADT on another computer, I can't see this error appearing there. This is very weird. Why do I get those errors, and what can I do to fix it? I've created a bug report . Until it gets fixed, set the API version in the UI preview to

I'm trying to take advantage of the new KitKat translucent system bars, to get a full screen image in the background of my app. I'm having problems figuring out the right settings to get the behaviour I want. Right now I have a ViewPager with three Fragment s each one composed of a RelativeLayout containing an ImageView (for the background image) and a TextView for the content. What I'm after is to have the content fit fully in the portion of the screen available for interactions, and the image to take the whole visible portion of the screen. If I just use android:Theme.Holo.Light.NoActionBar

I'm trying to encode my camera feed to VP8. The problem is: when I get the frame from the output buffer, the byte array is always different size but all entries are 0. Here's the code where I grab the frame and print it: while (true) { try { encoderIndex = mEncoder.dequeueOutputBuffer(encoderOutputInfo, timeOut); } catch (Exception e) { e.printStackTrace(); } switch (encoderIndex) { case MediaCodec.INFO_OUTPUT_BUFFERS_CHANGED: // something break; case MediaCodec.INFO_OUTPUT_FORMAT_CHANGED: // something else break; case MediaCodec.INFO_TRY_AGAIN_LATER: // something completely different break;