Create an account

Very important

  • To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
  • You will only see chat messages from people who are at or below your level.
  • More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
  • Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)


Thread Rating:
  • 413 Vote(s) - 3.5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Android - Outgoing transactions from this process must be FLAG_ONEWAY

#1
I'm facing two issues when running my Android application on Moto G6 device (on another devices or emulator there is no such problem). In my app, there is a simple LoginActivity that after successful login starts MainActivity (in onPostExecute of AsyncTask):

val intent = Intent(this@LoginActivity, MainActivity::class.java)
startActivity(intent)

However on Moto G6 (not happening on Sony Xperia), there is an error that transaction should be ONEWAY:

10-17 07:50:45.058 1878-2153/? W/Binder: Outgoing transactions from this process must be FLAG_ONEWAY
java.lang.Throwable
at android.os.BinderProxy.transact(Binder.java:736)
at android.app.assist.AssistStructure$ParcelTransferReader.fetchData(AssistStructure.java:407)
at android.app.assist.AssistStructure$ParcelTransferReader.go(AssistStructure.java:343)
at android.app.assist.AssistStructure.ensureData(AssistStructure.java:2110)
at com.android.server.autofill.Session$1.send(Session.java:200)
at com.android.server.am.ActivityManagerService.reportAssistContextExtras(ActivityManagerService.java:13475)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:2467)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3082)
at android.os.Binder.execTransact(Binder.java:674)

Any suggestion or help appreciated, thank you.
Reply

#2
I had this without reason. turn off instant run if it is on. Clean project (a few times if one is not anough) and rebuild the project
Reply

#3
**File | Invalidate Caches/Restart** worked for me
Reply

#4
For functional purposes, this is just a warning that inter-process (via binder) call is blocking, [AOSP source for this warning][1].

By default, inter-process calls are blocking but when it is marked `oneway` (via AIDL), it's executed as fire & forget (non-blocking). It is important for system processes to use non-blocking calls when calling into other (potentially unknown user code) to avoid stalling the whole system. So this warning is meant to flag dangerous calls like this: see [android developer AIDL documentation][2] regarding `oneway`.


In this example, there is a call into `ActivityManagerService` `reportAssistContextExtras` (AM runs in primary system process), which in turn invokes another IPC (inter-process) call `AssistStructure$ParcelTransferReader.fetchData`, and the latter is not marked `oneway` (which triggers this warning).

> on Moto G6 (not happening on Sony Xperia)

They might have different implementation/android versions or different call sequence (so it's not invoked)..

Bottom line, it's android implementation oversight; might be already resolved for this particular case, see latest [source of activity manager][3] .

If doesn't create functional problems, ignore the warning if it's not relevant to your code. If such call (`fetchData` in this example) resolves to your code, ensure not to block (return quickly).

However, it might lead to system watchdog kill, search for other logs to understand the consequences, like:

W Watchdog: *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on main thread (main)
W Watchdog: main annotated stack trace:
W Watchdog: at android.os.BinderProxy.transactNative(Native Method)


Ultimately, it might need to be filed with Google if it's not your code..


[1]:

[To see links please register here]

[2]:

[To see links please register here]

[3]:

[To see links please register here]

Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

©0Day  2016 - 2023 | All Rights Reserved.  Made with    for the community. Connected through