android-4.4-kitkat

Immersive mode instructions reappear every time the device enters this mode

|▌冷眼眸甩不掉的悲伤 提交于 2019-11-30 11:36:13
问题 My app uses the new "immersive mode" by calling (in onCreate ): getWindow().getDecorView().setSystemUiVisibility(View.SYSTEM_UI_FLAG_HIDE_NAVIGATION | View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY); This works great, but the "how-to" popup ("Swipe down from the top to exit full screen") appears every time the Activity is launched (if the phone is being locked while the activity was showing), even though the user has acknowledged the popup. As far as I understand, the popup is automatically generated

MediaPlayer randomly stops on Android 4.4 (19)

点点圈 提交于 2019-11-30 08:59:43
My app is streaming audio fine on all devices except Nexus 5. On Nexus 5, the MediaPlayer randomly stops playing. Not sure if the changes with respect to Loudness ( http://developer.android.com/about/versions/android-4.4.html#Multimedia ) in 4.4 has broken something. Is anyone else noticing this issue? Seems to be happening to some users, but I'm unable to reproduce on my own Nexus 5. UPDATE: So I was able to reproduce the issue on my Nexus 5. It seems to actually be happening near the end of the clip. With about 1 - 5 seconds left in the clip, the OnCompletionListener.onCompletion() method is

Emulator for Android 4.4 KitKat is not starting

ぐ巨炮叔叔 提交于 2019-11-30 08:17:48
I am creating an emulator for Android 4.4 KitKat, but the emulator takes very long and isn't starting. I tried many devices like Nexus4, Galaxy Nexus, Nexus S etc. but none of that worked. Just a black screen with the android logo for long time. Any suggestions? Unfortunately the emulator does take a very long time to load. A regular complaint amongst Android developers. It sometimes helps if you go into the AVD configuration and modify your KitKat emulator and tick the checkbox that says Use Host GPU . This makes it slightly faster. Also I've found that if you use the default RAM space that

No activity found to handle Intent - android.intent.action.OPEN_DOCUMENT

孤者浪人 提交于 2019-11-30 07:07:51
问题 I am trying my hand on Storage Access Framework of android 4.4 I have developed a dummy app which fires an intent on start of the activity. Intent intent = new Intent(Intent.ACTION_OPEN_DOCUMENT); intent.addCategory(Intent.CATEGORY_OPENABLE); startActivityForResult(intent, READ_REQUEST_CODE); Also I have developed another dummy app which serves as the file-provider. <?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.example

Listening for keywords at all times, like “Ok google” on 4.4 [closed]

给你一囗甜甜゛ 提交于 2019-11-30 06:43:25
I've checked the new Kitkat libraries to make sure that I'm not missing something. I want my application to always listen to a keyword before performing an action, just like how Google Now always listens for the keywords "Ok google" on the homescreen. How did Google accomplish this? What you need is called keyword spotting . Apart from online speech API Android has offline recognizer which is a bit more sophisticated. It is not mentioned in official documentation, but you can see the sources here , for example. I'm not sure you will find keyword spotting there, but at least you will have

KitKat: How to route APDUs to the SIM

跟風遠走 提交于 2019-11-30 06:33:06
问题 I want to route APDUs I get from an NFC Reader to the SIM Card. According to the HCE documentation I thought it would be possible simply by creating an OffHostApduService with the according routing-entries (which I did). Sadly, the SIM does not seem to get any APDUs. SELECT-Commands that work when the SIM is directly attached to my workstation by a SIM-Reader return with 6a82 (File not found). In LogCat I found two interesting bits of information: Every time I shoot a select command which

Android profiler not supported for Kitkat devices/google glass in android studio 3.0

依然范特西╮ 提交于 2019-11-30 06:20:47
From android studio 3.0 Android Monitor turned to Android profiler . But, when using google glass device or other android kitkat devices it's showing below message in android profiler window: Device not supported. Android profiler requires a device with API 21(Lollipop) or higher. What's the solution for Kitkat devices to use the latest Android Profiler once android studio 3.0 available for update in stable version? It seems that the Android Device Monitor (Tools->Android->Android Device Monitor) is still available. I am having difficulty running its memory monitor, although it does seem to

Overlay action bar with a translucent status bar

南楼画角 提交于 2019-11-30 05:25:38
I'm trying to achieve the effect shown here: http://www.youtube.com/watch?v=6QHkv-bSlds&t=15m48s by Nick and the boys. I can get the action bar to be overlayed, but cannot figure out how to extend this to the status bar. I would also like to know how they managed the transparent black background behind the navigation bar (but this isn't as crucial). Any help / advice would be greatly appreciated as I currently have no idea how this is done (and am starting to worry it may just be an image rather than an actual implementation). Edit: i know how to make the bars fully transparent (thats the easy

Android 4.4 KitKat random crash

与世无争的帅哥 提交于 2019-11-30 04:40:31
EDIT: Before down-voting and implying things, please understand I cannot reproduce this error. This happens constantly on certain devices which I do not have access to, but not after a firmware reset! I recently discovered random crashes in an app I am developing for a customer. The app has roughly 100.000 active users now after 3 years. We've seen the crash on Nexus 4 and 5, both with Android 4.4 KitKat. We cannot reproduce it on our own Nexus 4 and 5 running 4.4. We've had a customer through our support. He told us the crash happens every time at the same place when invoking a new activity.

AlarmManager stops working in Android 4.4.2 (using SetExact())

感情迁移 提交于 2019-11-30 03:57:00
问题 I'm setting in my code an alarm to go off in specific time. The alarm mechanism works great on SDK < 19, but on 19 the alarms aren't fired. Here is the code where I set the alarm : public void SetAlarm(Context context, Long executionTime) { AlarmManager am = (AlarmManager) context.getSystemService(Context.ALARM_SERVICE); Intent intent = new Intent(context, AlarmReciever.class); PendingIntent pi = PendingIntent.getBroadcast(context, 0, intent, PendingIntent.FLAG_UPDATE_CURRENT); // Only one