Just for starters, I'm testing on a Nexus 10 using API level 17. I've run into a situation that doesn't make sense to me, and I'm hoping that someone with a lot of experience in the Binder system can help. I've got an app, which I'll refer to as the core, which two other apps talk to via AIDL methods. Some of these methods modify the UI. I was expecting everything to fail due to wrong thread exceptions but I've found that for some reason, ADIL calls from one app always seem to run on the main thread in the core. The second app has a ton of wrong thread exceptions, and it's methods run on all sorts of threads in the core. The second app's calls never seem to land on the UI thread, even if it's the only app connected to the core.
The fact that any AIDL call would appear on the UI thread makes no sense to me. I was always under the impression that they should be handled by some worker thread from a Binder thread pool. Regardless of how this happens, it turns out to be extremely convenient. I'd much prefer to see if there's a way for me to coax the second app into always making it's calls on the UI thread instead of needing to do lots of runOnUIThread calls. Any thoughts? -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
