AdminWes wrote:If you would, please turn off any screen timeouts so that the screen remains ON for the duration of the test. // DONE (changed to 10 minutes)
Then perform the following:
- Launch MobiLinc and DO NOT interact with the screen. // DONE
- Let it sit for 60 seconds on the home screen. // DONE
- Tap My Devices. // DONE
- Tap Back. // DONE
- Tap My Settings and wait for 60 seconds. // ATTEMPTED (I waited on the settings screen without touching anything, which is when the "processing profile change" message popped up, and then the "Unfortunately, MobiLinc Pro has stopped" message popped up. It gives me the option of selecting "ok" or "report".
- Tap Lighting Controller Settings and wait for 60 seconds. // ATTEMPTED (I relaunched the application, opened settings, but the app freezes in the settings area with the message "processing profile change")
First - Many thanks to Wes for staying with this issue with me. We have been back and forth the last couple of days pouring over logcat logs to try to track this down. Wes was able to spot actions in the logs that should not be possible with the code within the application - leading us to the belief that a mysterious 'something' happened to the execution environment on my Galaxy Nexus during the 4.0.4 => 4.1.1 upgrade that did something bad to this application. I was having no issues with anything else on the phone though.
If I was rooted - I could have tried to clear the dalvik cache on the phone - chances are that's where the problem is in my opinion. But - without root all I could do is a 'Factory Data Reset'. I did this - upon reinstalling MobiLinc I no longer have the issue at all.
Based on Michael's and my findings, this is not a MobiLinc issue, but rather an upgrade to JB 4.1.1 issue. He was guessing at where the issue was in the Android OS, but was never able to prove it.
Users browsing this forum: No registered users and 1 guest