WAI
Status Update
No update yet.
Comments
ra...@google.com
I see same issue and have been debugging it.
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
ls...@gmail.com
[Comment deleted]
ra...@google.com
But Google pls fix this issue, as the expected behaviors must be consistent with ICS DialogFragment + FragmentManager and support package DialogFragment + FragmentManager.
It happens with both Support Package v4 r6 and v13 r6.
It happens with both Support Package v4 r6 and v13 r6.
te...@fujifilm.com
I have this problem too.
As a workaround I use a boolean in the onActivityResult to mark the desired dialog and show the dialog in the onResume.
As a workaround I use a boolean in the onActivityResult to mark the desired dialog and show the dialog in the onResume.
Description
I have a question about pairing Link3 and Android smartphones.
The phenomenon I am asking about occurs on any Android device (it is not a phenomenon limited to specific devices).
[Questions]
Q1: When pairing notifications come from the Android OS, we have confirmed the following two patterns. (Please refer to the attached images for the pop-up pattern).
① Pattern where the notification appears at the top of the screen
② Pattern where the window appears in the center of the screen
Is it possible in principle for the pop-up in ② to occur from the beginning without the notification in ①? (My understanding is that the flow is that the screen in ② always appears after the screen in ①.
Q2: Do you know what causes the screen in ② to appear? Although the Android OS ultimately displays the pop-up in ②, I would like to conduct a separate investigation to determine the cause of this. (As a hypothesis, I thought that the Android OS may be recognizing a “signal that requests contact information” contained in the advertisement sent from our company's printer.
[Reference: Pairing/connection operation flow for our printer and Pixel series]
・If you tap “Connect” in the notification at ①, ② will be displayed.
・If you tap “Connect” in ②, the connection will be established.
・(On smartphones such as the Pixel 9) ① will be displayed again.
→If no action is taken for the second notification at ① and a certain amount of time passes, the connection will be cut.
→ If you tap “Connect” in response to the second ① notification, the connection will be established.