samsung-galaxy

Prevent automated starting of Android app due to “machine learning” (Samsung's PkgPredictorService)

一曲冷凌霜 提交于 2021-02-08 01:22:37
问题 I am the developer of an app and it's available and working well since about two years. Only on recent Samsung devices the app gets randomly started by the system after the user closed it via its exit button. This exit button stops all services and activities and kills the app via Android's "killProcess"-method,so it's not a simple restart of a crashed app. It's an utility-app which runs in the background and if the user closes it, it must stop and stay closed because it produces a lot of

Prevent automated starting of Android app due to “machine learning” (Samsung's PkgPredictorService)

生来就可爱ヽ(ⅴ<●) 提交于 2021-02-08 01:20:59
问题 I am the developer of an app and it's available and working well since about two years. Only on recent Samsung devices the app gets randomly started by the system after the user closed it via its exit button. This exit button stops all services and activities and kills the app via Android's "killProcess"-method,so it's not a simple restart of a crashed app. It's an utility-app which runs in the background and if the user closes it, it must stop and stay closed because it produces a lot of

Prevent automated starting of Android app due to “machine learning” (Samsung's PkgPredictorService)

末鹿安然 提交于 2021-02-08 01:17:48
问题 I am the developer of an app and it's available and working well since about two years. Only on recent Samsung devices the app gets randomly started by the system after the user closed it via its exit button. This exit button stops all services and activities and kills the app via Android's "killProcess"-method,so it's not a simple restart of a crashed app. It's an utility-app which runs in the background and if the user closes it, it must stop and stay closed because it produces a lot of

How to read the pressure sensor?

老子叫甜甜 提交于 2020-04-28 22:42:06
问题 Physical home button press can be detected easily on most of the devices: ... public class ExampleAccessibilityService extends AccessibilityService { ... @Override protected boolean onKeyEvent(KeyEvent event) { if (event.getKeyCode() == KEYCODE_HOME && event.getAction() == ACTION_DOWN) Log.d("Example", "The home key is pressed."); return super.onKeyEvent(event); } } But the code above doesn't work on some devices that have a pressure-sensitive virtual home button. I suppose these Samsung

Galaxy S10, S10+ Full Screen Mode

让人想犯罪 __ 提交于 2020-02-02 10:18:57
问题 How can achieve full screen mode with Samsung Galaxy S10 and S10+, the following code do not work for me: getWindow().getDecorView().setSystemUiVisibility( // Set the content to appear under the system bars so that the // content doesn't resize when the system bars hide and show. SYSTEM_UI_FLAG_LAYOUT_STABLE | View.SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION | View.SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN // Hide the nav bar and status bar // | View.SYSTEM_UI_FLAG_HIDE_NAVIGATION | View.SYSTEM_UI_FLAG

Why is video made with MediaCodec garbled for Samsung Galaxy S7?

回眸只為那壹抹淺笑 提交于 2020-01-05 06:51:08
问题 When I encode a video via Surface -> MediaCodec -> MediaMuxer, I get a very strange result when testing on the Samsung Galaxy S7. For other devices tested (emulator with Marshmallow and HTC Desire), the video comes out correctly, but on this device the video is garbled. Using MediaCodec to save series of images as Video had a similar output of video, but I don't see how the solution could apply here because I am using a Surface as input and set the color format to COLOR_FormatSurface. I also

Why is video made with MediaCodec garbled for Samsung Galaxy S7?

有些话、适合烂在心里 提交于 2020-01-05 06:51:05
问题 When I encode a video via Surface -> MediaCodec -> MediaMuxer, I get a very strange result when testing on the Samsung Galaxy S7. For other devices tested (emulator with Marshmallow and HTC Desire), the video comes out correctly, but on this device the video is garbled. Using MediaCodec to save series of images as Video had a similar output of video, but I don't see how the solution could apply here because I am using a Surface as input and set the color format to COLOR_FormatSurface. I also

Connecting Samsung S7 to AndroidStudio

谁说胖子不能爱 提交于 2019-12-25 18:25:17
问题 I like to start my app directly on Samsung S7 with AndroidStudio. I have already enabled debugging mode in the developer option by tapping 7 times on build number, but still I don't see the device when starting the app and getting the "Select Deployment Target" Dialog. What else do I have to do ? 回答1: In developer options at bottom of setings menu, ensure USB debugging is ticked. Then start again, restart windows and S7 to make sure and try again. With one of my devices, tapping seven times

CSS background-blend-mode not working on Samsung S9

你。 提交于 2019-12-24 14:34:06
问题 Using ´background-blend-mode´, it works on most mobile devices and browsers, but on the Samsung S9 it doesn't. S9: Others: My CSS code: .home-section-hero { -webkit-background-size: 100% 100%; -moz-background-size: 100% 100%; -o-background-size: 100% 100%; background-size: 100% 100%; background-blend-mode: multiply; } 来源: https://stackoverflow.com/questions/55500046/css-background-blend-mode-not-working-on-samsung-s9

TransactionTooLargeException on Samsung S7

喜你入骨 提交于 2019-12-24 00:57:07
问题 one of my apps is throwing the following exception on an Samsung S7: java.lang.RuntimeException: at android.app.NotificationManager.notifyAsUser (NotificationManager.java:342) at android.app.NotificationManager.notify (NotificationManager.java:292) at android.app.NotificationManager.notify (NotificationManager.java:276) at org.mypapp.test.service.NotificationReceiverRemoteViews.updateNotification (NotificationReceiverRemoteViews.java:202) at org.mypapp.test.service