now this runtime added Android support library v4 for compatibility with some old devices and allow developer to use it.with the new Runtime files, .apk size has increased by ~650 kilobytes?
the application end when is sent to back from another activity, apk or sdk, pressing home button, for this some sdk like admob , etc disable this feature during this stage to avoid end the application, see that using the screen button does not end the application though, since is not real send to background is just a pause with screen off.the by default checked End application when not in foreground - with the old files the application pauses, with the updated files it must be unchecked to pause the app?
Are these activity related to CT or they are external as share, open, etc.
see that the android object have a feature called Auto End where you can disable or enable for this matters
mm not sure about this in newer devices, please drop a small mfa or point me to the step to reproduce I have android 8.1 only I will test with that to see if is something related to android 9- specific issue with Blend Coefficient, this is noticeable on newer devices of the Samsung Galaxy S series for example.
I tested with S8+ Android 9, here you can choose between navigation buttons and swipe gestures(most people prefer the gestures I guess).
If you use the swipe gestures you can dynamically zoom in/out from the current app to show all open apps and switch to another open app if needed.
Now when you have any objects in the Frame with increased blend coefficient values, you can see the phone's background through the application.
It's already enough when you accidently click on the swipable location on the screen, then the phone's background
will suddenly pop into the running Fusion app at all places with increased blend coefficient.
point me in, tell me the steps, sorry was focus in round error.The other problem wasn't fixed yet in the files you sent me Fernando, right?
Here is a .gif image with the problem in action just in case - I'm not sure if you noticed it with my .mfa file on your test device.
My position related events go nuts, when I move the Active constantly in one direction - this applies to a moving Layer as well.
mm could it be if you are not using the list object per se did you set visible OFF, show me an example pleaseAnother object related question - List object operations can easily reduce FPS on Android?
Your answer here could help me to debug an issue in my current app.
And Thanks to you for helping test these changes