Can you add some logs and figure out the exact sequence of lifecycle calls (e.g. onStart(), onStop(), etc.) in your scenario? Also include the relevant IOIO logs so we can see whether a connection is closed properly before switching.
On Mon, May 18, 2015 at 3:15 PM, Tiffany Hwu <[email protected]> wrote: > I have a main activity that extends IOIOActivity. Within this main > activity I have function called scan(), which calls > startActivityForResult() to open up a new activity to scan a QR code using > the Android phone. The usual life cycle for main activity in this case is > to pause, stop, let the QR activity scan, start, then resume. Accordingly, > I think the > > IOIOAndroidApplicationHelper should reestablish the IOIO connection at the > start stage. However, this doesn't happen and the IOIO connection is gone > when the main activity resumes. Any ideas on why this is happening? I can > post some code if more clarity is needed. Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/ioio-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
