android-4.4-kitkat

SSLException - Connection closed by peer on Android 4.x versions

限于喜欢 提交于 2019-12-01 06:33:53
The issue is not occurring on higher OS versions. Is there a known problem on Android 4.x versions? If yes, how can this issue be addressed? Should there be a change on the mobile app or on the backend side? sticky I actually don't have the full stack trace. This is what's visible to me. IOException:Connection closed by peer EXCEPTION class: class javax.net.ssl.SSLException EXCEPTION cause: null EXCEPTION message: Connection closed by peer RESPONSE: SSLException The issue was due to TLSv1 being disabled on backend. Depending on the case there can be two approach to address this issue. 1.

WebView difference in android 4.3 to 4.4 [closed]

社会主义新天地 提交于 2019-12-01 04:23:59
I implemented a WebView with images taken from the web. On Android 4.3 there's no problem. On Android 4.4 kitkat, the displayed images are too big. How do I solve that? Kitkat Behavior changes https://developer.android.com/about/versions/android-4.4.html For Webview Please Refer.. https://developer.android.com/guide/webapps/migrating.html Android 4.4 (API level 19) introduces a new version of WebView that is based on Chromium. This change upgrades WebView performance and standards support for HTML5, CSS3, and JavaScript to match the latest web browsers. Any apps using WebView will inherit

On Android API 19 (4.4) the intent.createChooser method causes IntentServiceLeak

你。 提交于 2019-12-01 04:22:42
Running my app on the new Android KitKat device (API 19, 4.4) I get "Copied to Clipboard" everytime I try to create an Intent chooser. This is happening on Youtube, Tumblr and various other apps on Android KitKat. Looking at the logs I'm seeing the following exception: com.android.internal.app.ChooserActivity has leaked IntentReceiver com.android.internal.app.ResolverActivity$1@4150aac8 This used to be an issue caused when a device didn't have multiple apps to Intent to (see Why does Intent.createChooser() need a BroadcastReceiver and how to implement? ). However, this is not the case on my

Android Studio can't run application on device: stuck on “Waiting for process: <project>”

我与影子孤独终老i 提交于 2019-12-01 03:13:32
When trying to debug my application on my Samsung Galaxy S4, I get this output: Waiting for device. Target device: samsung-samsung_sgh_i337-8c8aa2c7 Uploading file local path: C:\Users\awebberley\AndroidStudioProjects\Contacts\app\build\apk\app-debug-unaligned.apk remote path: /data/local/tmp/org.intracode.contacts Installing org.intracode.contacts DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/org.intracode.contacts" pkg:/data/local/tmp/org.intracode.contacts Success Waiting for process: org.intracode.contacts It just stays on the "waiting for process" message without running the

How to set SELinux to 0 or permissive mode in android 4.4.4 and above?

江枫思渺然 提交于 2019-12-01 03:06:11
I want to set the SELinux (Security Enhanced Linux) mode to Permissive or (0) on android 4.4.4 (and above if possible). I use the following command: setenforce 0 , setenforce permissive and setenforce Permissive under root (my device is rooted). But the output of getenforce is always Enforcing . Now I am exhausted with this problem. Can any one give me a solution? Thanks in advance. Apparently Google has removed the CONFIG_SECURITY_SELINUX_DEVELOP kernel flag from many of their Stock kernels. Thus the standard trick mentioned by William (below) probably doesn't work. An example of these

WebView difference in android 4.3 to 4.4 [closed]

夙愿已清 提交于 2019-12-01 02:58:21
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 years ago . I implemented a WebView with images taken from the web. On Android 4.3 there's no problem. On Android 4.4 kitkat, the displayed images are too big. How do I solve that? 回答1: Kitkat Behavior changes https://developer.android.com/about/versions/android-4.4.html For Webview Please Refer.. https://developer.android

Android 4.4 http api bugs?

风流意气都作罢 提交于 2019-12-01 02:58:19
I decided to start testing my app with Android 4.4 and noticed that the Android HTTP connection APIs are much stricter than before? I have never had this issue and I assume it is some type of bug. I'm connecting to SHOUTcast broadcasts that contain the particular icy header response. Has anyone seen this issue? How can I get around it? URL used for this test: http://50.117.121.162:80 Logcat of exception: 11-01 23:47:57.299: E/ConnectHelper(3081): java.net.ProtocolException: Unexpected status line: ICY 200 OK 11-01 23:47:57.299: E/ConnectHelper(3081): at com.android.okhttp.internal.http

On Android API 19 (4.4) the intent.createChooser method causes IntentServiceLeak

让人想犯罪 __ 提交于 2019-12-01 01:56:23
问题 Running my app on the new Android KitKat device (API 19, 4.4) I get "Copied to Clipboard" everytime I try to create an Intent chooser. This is happening on Youtube, Tumblr and various other apps on Android KitKat. Looking at the logs I'm seeing the following exception: com.android.internal.app.ChooserActivity has leaked IntentReceiver com.android.internal.app.ResolverActivity$1@4150aac8 This used to be an issue caused when a device didn't have multiple apps to Intent to (see Why does Intent

How to set SELinux to 0 or permissive mode in android 4.4.4 and above?

怎甘沉沦 提交于 2019-11-30 23:15:08
问题 I want to set the SELinux (Security Enhanced Linux) mode to Permissive or (0) on android 4.4.4 (and above if possible). I use the following command: setenforce 0 , setenforce permissive and setenforce Permissive under root (my device is rooted). But the output of getenforce is always Enforcing . Now I am exhausted with this problem. Can any one give me a solution? Thanks in advance. 回答1: Apparently Google has removed the CONFIG_SECURITY_SELINUX_DEVELOP kernel flag from many of their Stock

Try to Video Record using adb shell screenrecord Android 4.4

不想你离开。 提交于 2019-11-30 23:01:32
问题 I am try to create a video from terminal but I can't succeed. It gives error on terminal like this. adb shell screenrecord /sdcard/screenshotyyyy.mp4 ERROR: unable to create encoder input surface (err=-38) WARNING: failed at 320x480, retrying at 720x1280 ERROR: unable to create encoder input surface (err=-38) 回答1: The screenrecord feature doesn't work in the AOSP emulator, because the software AVC encoder doesn't support the necessary features. As noted in this bug, the screenrecord binary