P2: Teacher App failure in tag: 0.9.9b2-jamsj - loses data #43
Comments
|
After a screen rotation and losing the data on the screen, I did: 02-12 12:18:31.754 8245-8245/org.smilec.smile D/dalvikvm﹕ GC_FOR_ALLOC freed 46K, 1% free 10910K/10992K, paused 11ms, total 11ms |
|
Great, this was useful. Seems like this is the error after rotating the screen? Can you confirm when the FATAL Exception occurs? exception (group=0x41a5dba8) |
|
Yes it occurs after rotating the screen but not right after. 'Start Solving Questions' works even thought students/question set data doesn't display. The FATAL EXCEPTION comes up when hitting 'Finish Show Result.' The app gets terminated but the right result is shown on the student side screen. |
|
Ok, well the problem must be happening before hitting "Finish", as the questions don't show up, so there is a problem. Can you get a complete log trace of the entire output on the teacher tablet, up to the point where you rotate sideways, and then rejoin the teacher session. |
|
I am not understanding 'a complete log trace of the entire output' yet. Am I supposed to create a trace file? Traceview? Or else? |
|
I'd start with capturing all of the logging output. If we can pinpoint the are of failure we can watch the variables in the debugger and step through. I'm guessing the application is not resuming from being paused or recreated when rotation occurs. Sent from my BlackBerry Passport. From: yukoyukoSent: Thursday, February 19, 2015 9:13 PMTo: RazortoothRTC/smile_teacher_androidReply To: RazortoothRTC/smile_teacher_androidCc: David J. KordsmeierSubject: Re: [smile_teacher_android] P2: Teacher App failure in tag: 0.9.9b2-jamsj - loses data (#43)I am not understanding 'a complete log trace of the entire output' yet. Am I supposed to create a trace file? Traceview? Or else? —Reply to this email directly or view it on GitHub. |
|
Below is the logging output starting from running the app and adding two students, until getting back to the app after rotating the device. After the rotation, the logcat stopped updating the output: 02-21 13:09:18.157 27255-27255/org.smilec.smile I/dalvikvm﹕ Enabling JNI app bug workarounds for target SDK version 7... |
|
Yuko, one of the problems I see is that the developer on this didn't use Android logging facilities. They used system.out.println. While this is ok (doesn't cause any problems with the code), it makes debugging difficult. We don't really know how to find our application in all of the output. Normally logging is done by severity and by category (name) of the programming doing the logging. |
|
Secondly, I can see that in my own testing, I can cause the data to be "lost" after locking the screen. I can't figure out what happens based on this output. I may need to modify this to improve logging. |
|
Looks like here is one thing that happens when the screen locks: I/ActivityManager( 567): Activity reported stop, but no longer stopping: ActivityRecord{65b3b660 u0 org.smilec.smile/.ui.GeneralActivity t14} |
|
Bingo: I/ActivityManager( 567): START u0 {cmp=org.smilec.smile/.ui.ChooseActivityFlowDialog (has extras)} from pid 14492 |
|
Here are a few more things from the output: D/SMILEPLUG(14492): loadItems is true |
|
It would appear that several things happen:
|
|
I'd need to run this in the debugger to know for sure. |
|
The work around might be to turn off screen lock. |
|
There is a "recover" state that works sometimes, but only if the app is killed and restarted. |
|
I will propose a work around to see if this fixes things for JAMsj:
Future work should focus on the Web Version of the Teacher App. This android version is a horribly complex code base. If we choose to fix it, someone will need to go through with a fine tooth comb in the debugger and track down the problem. |
|
Hi @truedat101 . Do you have any feedback about this workaround? I've similar issues with the WindowManager in my app. |
|
@glureau what version of the Android app and android os are you using? |
|
Android 4.2/4.4/5.1 (customized ROM and private apps) |
After some point, perhaps if the screen lock goes on and puts the app into pause state, the data in memory is lost and there is no way to recover it, other than to kill the app and restart. I can create this by leaving screen lock on for about 5 minutes, at which point something happens and the app, when returning to it, doesn't have any data in the student or question view.
The text was updated successfully, but these errors were encountered: