android.os.TransactionTooLargeException in AppWidgetManager.updateAppWidget
I receive report about android.os.TransactionTooLargeException from my widget users:
android.os.TransactionTooLargeException
android.os.BinderProxy.transact(Native Method)
com.android.internal.appwidget.IAppWidgetService$Stub$Proxy.updateAppWidgetIds(IAppWidgetService.java:611)
android.appwidget.AppWidgetManager.updateAppWidget(AppWidgetManager.java:378)
android.appwidget.AppWidgetManager.updateAppWidget(AppWidgetManager.java:445)
com.alonedroid.ooswitcher.animationRunnable.run(ProvidersShared.java:1804)
java.lang.Thread.run(Thread.java:841)
That exception occurs when I try to update my widget in separate thread
through AppWidgetManager.updateAppWidget(widget_id, RemoteView). I read from documentation about TransactionTooLargeException, and, first, i thought - it is because of size of RemoteViews instance. So I start to set more layouts inside my RemoteViews instance, but never saw this error on my device.
Did somebody faced that problem too and maybe even solve it? And how to
reproduce that error to debug application?
android exception widget edited Nov 22 '13 at 10:10
DontVoteMeDown
15k85084
asked Nov 22 '13 at 9:51
alonedroidalonedroid
162
add a comment |
I receive report about android.os.TransactionTooLargeException from my widget users:
android.os.TransactionTooLargeException
android.os.BinderProxy.transact(Native Method)
com.android.internal.appwidget.IAppWidgetService$Stub$Proxy.updateAppWidgetIds(IAppWidgetService.java:611)
android.appwidget.AppWidgetManager.updateAppWidget(AppWidgetManager.java:378)
android.appwidget.AppWidgetManager.updateAppWidget(AppWidgetManager.java:445)
com.alonedroid.ooswitcher.animationRunnable.run(ProvidersShared.java:1804)
java.lang.Thread.run(Thread.java:841)
That exception occurs when I try to update my widget in separate thread
through AppWidgetManager.updateAppWidget(widget_id, RemoteView). I read from documentation about TransactionTooLargeException, and, first, i thought - it is because of size of RemoteViews instance. So I start to set more layouts inside my RemoteViews instance, but never saw this error on my device.
Did somebody faced that problem too and maybe even solve it? And how to
reproduce that error to debug application?
android exception widget edited Nov 22 '13 at 10:10
DontVoteMeDown
15k85084
asked Nov 22 '13 at 9:51
alonedroidalonedroid
162
add a comment |
I receive report about android.os.TransactionTooLargeException from my widget users:
android.os.TransactionTooLargeException
android.os.BinderProxy.transact(Native Method)
com.android.internal.appwidget.IAppWidgetService$Stub$Proxy.updateAppWidgetIds(IAppWidgetService.java:611)
android.appwidget.AppWidgetManager.updateAppWidget(AppWidgetManager.java:378)
android.appwidget.AppWidgetManager.updateAppWidget(AppWidgetManager.java:445)
com.alonedroid.ooswitcher.animationRunnable.run(ProvidersShared.java:1804)
java.lang.Thread.run(Thread.java:841)
That exception occurs when I try to update my widget in separate thread
through AppWidgetManager.updateAppWidget(widget_id, RemoteView). I read from documentation about TransactionTooLargeException, and, first, i thought - it is because of size of RemoteViews instance. So I start to set more layouts inside my RemoteViews instance, but never saw this error on my device.
Did somebody faced that problem too and maybe even solve it? And how to
reproduce that error to debug application?
android exception widget edited Nov 22 '13 at 10:10
DontVoteMeDown
15k85084
asked Nov 22 '13 at 9:51
alonedroidalonedroid
162
I receive report about android.os.TransactionTooLargeException from my widget users:
android.os.TransactionTooLargeException
android.os.BinderProxy.transact(Native Method)
com.android.internal.appwidget.IAppWidgetService$Stub$Proxy.updateAppWidgetIds(IAppWidgetService.java:611)
android.appwidget.AppWidgetManager.updateAppWidget(AppWidgetManager.java:378)
android.appwidget.AppWidgetManager.updateAppWidget(AppWidgetManager.java:445)
com.alonedroid.ooswitcher.animationRunnable.run(ProvidersShared.java:1804)
java.lang.Thread.run(Thread.java:841)
That exception occurs when I try to update my widget in separate thread
through AppWidgetManager.updateAppWidget(widget_id, RemoteView). I read from documentation about TransactionTooLargeException, and, first, i thought - it is because of size of RemoteViews instance. So I start to set more layouts inside my RemoteViews instance, but never saw this error on my device.
Did somebody faced that problem too and maybe even solve it? And how to
reproduce that error to debug application?
android exception widget android exception widget edited Nov 22 '13 at 10:10
DontVoteMeDown
15k85084
asked Nov 22 '13 at 9:51
alonedroidalonedroid
162
edited Nov 22 '13 at 10:10
DontVoteMeDown
15k85084
asked Nov 22 '13 at 9:51
alonedroidalonedroid
162
edited Nov 22 '13 at 10:10
DontVoteMeDown
15k85084
edited Nov 22 '13 at 10:10
DontVoteMeDown
15k85084
edited Nov 22 '13 at 10:10
DontVoteMeDown
15k85084
15k85084
asked Nov 22 '13 at 9:51
alonedroidalonedroid
162
asked Nov 22 '13 at 9:51
alonedroidalonedroid
162
asked Nov 22 '13 at 9:51
alonedroidalonedroid
162
162
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Looking at the implementation of RemoteViews, it looks like this can happen if too many operations are done on a single RemoteViews instance.
For example calling setTextViewText 1000 times with the same parameters will add 1000 operations to the RemoteViews which will have to be transferred across processes and applied as an update.
Making sure that the same RemoteViews object is not reused for an insane amount of operations seems to fix this.
answered Nov 25 '18 at 12:47
ErikErik
1
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f20141764%2fandroid-os-transactiontoolargeexception-in-appwidgetmanager-updateappwidget%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Looking at the implementation of RemoteViews, it looks like this can happen if too many operations are done on a single RemoteViews instance.
For example calling setTextViewText 1000 times with the same parameters will add 1000 operations to the RemoteViews which will have to be transferred across processes and applied as an update.
Making sure that the same RemoteViews object is not reused for an insane amount of operations seems to fix this.
answered Nov 25 '18 at 12:47
ErikErik
1
add a comment |
Looking at the implementation of RemoteViews, it looks like this can happen if too many operations are done on a single RemoteViews instance.
For example calling setTextViewText 1000 times with the same parameters will add 1000 operations to the RemoteViews which will have to be transferred across processes and applied as an update.
Making sure that the same RemoteViews object is not reused for an insane amount of operations seems to fix this.
answered Nov 25 '18 at 12:47
ErikErik
1
add a comment |
Looking at the implementation of RemoteViews, it looks like this can happen if too many operations are done on a single RemoteViews instance.
For example calling setTextViewText 1000 times with the same parameters will add 1000 operations to the RemoteViews which will have to be transferred across processes and applied as an update.
Making sure that the same RemoteViews object is not reused for an insane amount of operations seems to fix this.
answered Nov 25 '18 at 12:47
ErikErik
1
Looking at the implementation of RemoteViews, it looks like this can happen if too many operations are done on a single RemoteViews instance.
For example calling setTextViewText 1000 times with the same parameters will add 1000 operations to the RemoteViews which will have to be transferred across processes and applied as an update.
Making sure that the same RemoteViews object is not reused for an insane amount of operations seems to fix this.
answered Nov 25 '18 at 12:47
ErikErik
1
answered Nov 25 '18 at 12:47
ErikErik
1
answered Nov 25 '18 at 12:47
ErikErik
1
answered Nov 25 '18 at 12:47
ErikErik
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f20141764%2fandroid-os-transactiontoolargeexception-in-appwidgetmanager-updateappwidget%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
