samsung-mobile

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 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.CONFIGURATION_CHANGED does not receive an Intent when a new font is selected in the dialog (but it does when the

On my Google Play console I see quite a lot crash reports since I started to use Dagger 2, but only on Android 7.0 and mainly on Samsung devices, some Huawai and Motorola devices and some rare Xperia devices: java.lang.RuntimeException: at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2984) at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3045) at android.app.ActivityThread.-wrap14 (ActivityThread.java) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1642) at android.os.Handler.dispatchMessage (Handler.java:102) at android.os

I am trying to preview an image after capturing it using camera from inside my app, I am sure the path is not null but I am receiving this error in this line of code Bitmap bitmap = BitmapFactory.decodeFile(fileUri.getPath(),options); and there is no image view. Note: I tested the code on another device (not Samsung) and it works. KyleCrowley In regards to the sendUserActionEvent() mView==null , it is a know bug with Samsung devices (see this and this ). If it works on non-Samsung devices, then it is not your fault, it is Samsung's. However, you should try and find a workaround if you can.

Specific scenario to avoid problems: Behaviour for Activity in Samsung devices was different in the manner that every time there was a change detected, for proximity, it resulted in a call to onPause()/onResume() ONLY on SAMSUNG devices. I was clearing the proximity sensors in onPause() which resulted in a behaviour unique to Samsung devices. Hope this saves some time for anybody who's facing this. I removed the call of clearing proximity listeners from onPause() and now it works as expected on the mentioned devices. UPDATE: What is mentioned below is not the only issue, the proximity sensor

This issue was reported several times, but still not resolved yet. I read all messages/thread which somehow related to this topic either in Samsung's developers site or in StackOverflow Let me again describe whole problem just in few words: Developers used to get list of SMS conversations through simple query like: Uri.parse("content://mms-sms/conversations/"); Cursor cursor = context.getApplicationContext().getContentResolver().query(uri, null, null, null, null); or something like this. Key point here's URI address: content://mms-sms/conversations Everyone knows that it's unofficial and one's