samsung-mobile

Android Usage Access for Android 5 Samsung devices

不问归期 提交于 2019-11-28 08:11:41
As you might know, since Android 5 was launched, accessing the recent tasks (usage stats) of your device requires the user to enable this feature manually (Settings->Security->Usage Access). My app checks if the device uses Android 5, and if so, then it offers the user the possibility of opening the settings screen for enabling usage access: Intent intent = new Intent(Settings.ACTION_USAGE_ACCESS_SETTINGS); startActivityForResult(intent, 12345); The problem comes when I try to do this in a Samsung device running Android 5... I got this error when the line shown above is executed: android

java.lang.NullPointerException with Nougat

拜拜、爱过 提交于 2019-11-28 07:35:56
My app has been humming along nicely through various Android versions. I have users running it on Android 4.3, 5.0, 5.1 and 6.0 with no problems. However a user with a S7 Edge has just updated with Android 7.0 and the app is crashing when text is pasted into an EditText field (This is the first and only thing you do with this app - it starts you paste in text into a box and then the app parses the text). I have looked at many threads on Null Pointer Exceptions and I have looked at the source for Editor.java but nothing is obvious. The stack trace below shows no problems with my code. Any ideas

Compass readings on SGS III

穿精又带淫゛_ 提交于 2019-11-28 06:47:57
问题 My app needs to show the current bearing of the device using its compass. The code I'm using (below) works perfectly fine on my Galaxy Nexus and Galaxy One, but the compass is spinning around wildly on a Samsung Galaxy S III. I've tried doing a figure-8 to recalibrate the device, but that doesn't change anything. The weird thing is that other compass apps downloaded from Google Play work just fine on the SIII. What could be the issue here? float[] mGravity; float[] mGeomagnetic; public void

Phonegap on Galaxy S3 ignores touch events

放肆的年华 提交于 2019-11-28 05:50:32
问题 I am having a really odd issue. I have a Phonegap 2.0 app that is basically completed. It is working on iPhone and iPad and I ported it over to Android in a day, testing it on my Galaxy S. Everything worked perfectly. Then I tried to run it on my brand new S3 and none of the touch events worked. Clicks work, but not touch. If I run this code document.addEventListener('touchstart', function (e) { console.log('touch start')}, false); document.addEventListener('click', function (e) { console.log

Samsung Galaxy S4 , Image gets corrupted while taking from camera

杀马特。学长 韩版系。学妹 提交于 2019-11-28 05:10:14
问题 I'm using camera on my app. Camera is working perfect on all devices upto Samsung S3 even. Image is correct from all other devices. While taking image from S4 , image gets corrupted and image gets saved with some lines in horizontal. I tried changing resolution and everything but still issue is there . Any help 回答1: I've been pulling my hair out over this and I think I found the issue, at least with regards to my app - it's got something to do with the aspect ratio of the preview image versus

Samsung Galaxy s3 emulator settings

荒凉一梦 提交于 2019-11-28 04:20:13
Can anyone with galaxy s3 access confirm the below emulator settings for Galaxy s3? Target: Google APIs - API Level 15 Skin: Built-in WXGA720 Hardware Back/Home: yes Abstracted LCD density: 320 Keyboard lid support: no Max VM application heap size: 48 Device ram size: 1024 I had to set the device ram to 512 in emulator. Above configs were the best possible match I could get after comparing with the real Galaxy S3 device. It work for me with 768MB RAM. On Windows, emulating RAM greater than 768MB may fail depending on the system load. 来源: https://stackoverflow.com/questions/10804619/samsung

Android :android:configChanges value for Font Style change in Samsung Device

倖福魔咒の 提交于 2019-11-28 01:49:59
问题 Want to handle the Font Style Change myself.what will be the value? Using the below values now.But the system kills the app and restarts . android:configChanges="orientation|keyboardHidden|fontScale|locale|layoutDirection|screenSize|screenLayout|mnc|mcc|uiMode|navigation|smallestScreenSize" Thanks Nitz 回答1: I don't think this is possible, unfortunately. This seems to be using a different mechanism instead of configuration changes. Setting up a service to listen for android.intent.action

Serial number from Samsung Device running Android

五迷三道 提交于 2019-11-27 22:11:12
I have a Samsung Galaxy Tab 2.0 (7") On the back of this device is a serial number of the format RF3C6000MNA When I go into settings on my device, and choose About Device->Status->Serial Number, this number also appears. I can't, however, find a way of extracting this number programmatically. I've seen loads of articles about extracting the serial number, but this returns a completely different number. (using android.os.Build.SERIAL) I've already extracted the IMEI, and MAC address, so I don't need code for this. dev public static String getManufacturerSerialNumber() { String serial = null;

appcompat-v7 v21.0.0 causing crash on Samsung devices with Android v4.2.2

北城余情 提交于 2019-11-27 17:29:07
We just changed our application to use the appcompat-v7 support library in order to take advantage of the support actionbar and support Material themes. Using v21.0.0 of appcompat-v7 (and v21.0.0 of support-v4) , we are now seeing crashes in Google Play and Crashlytics only from Samsung devices running Android v4.2.2 . Here is the stack trace from Google Play and the app appears to crash as soon as the actionbar` is shown and/or invalidated. java.lang.NoClassDefFoundError: android.support.v7.internal.view.menu.MenuBuilder at android.support.v7.app.ActionBarActivityDelegateBase

Adding Samsung multi-window support to Android application

放肆的年华 提交于 2019-11-27 17:00:00
I went and tried to add Samsung's multi-window support for my app following this link . My app did appear in Samsung's multi-window applications tab, and I was able to drag and drop it into the screen, however my app did not behave as multi-window supported app should behave, but instead expanded to full screen. I think there are some other changes that are need to be made to get it work properly, but I have no idea what. Does anyone have any ideas what could be the problem causing this behaviour? Paul Lammertsma This xda-developers forum post contains a step-by-step guide, which I've