apostolakisl Posted September 23, 2010 Posted September 23, 2010 I just recently had my iphone crash and had to reinstall from scratch and thus now have 4.1 iOS. I had to reinstall mobile linc pro of course. When I run it for the first time after a phone restart, it works perfectly. If I close the application and then go back to it, it will be frozen on the first page. It does flash up a communication error first (a switch I had to RMA to SH for defective paddle), but once I clear that error it is frozen. Rebooting the iphone fixes it until I exit the app and go back to it at which time the process repeats. Everything did work fine back before I was forced to upgrade (a term I use loosely as I liked 3.2 better).
fitzpatri8 Posted September 23, 2010 Posted September 23, 2010 What happens if you turn off the iPod (hold the Sleep button until Slide to power off appears, then follow the direction), turn it back on, then go to the iPod Settings app, MobiLinc Pro and turn off Display Device Errors? Then when you restart MobiLinc, does it work as expected? What versions of ISY firmware and MobiLinc Pro are you using?
apostolakisl Posted September 23, 2010 Author Posted September 23, 2010 Mobile linc pro v 2.17.00 ISY 2.7.15 Shutting off the error notification seems to have stopped it from freezing on the "second run" after boot (and for that matter all subsequent runnings of the app). Odd that it only freezes on the second run after booting even though the error messages pop up just the same on the first run. And I did uninstall and reinstall mobile linc pro which resulted in no change.
InsteonNut Posted September 30, 2010 Posted September 30, 2010 Hi Apostolakisl, This communication error is being reported by the ISY to MobiLinc. It means that the ISY can't talk to that particular device. When you log into the ISY java console how many of these communication errors pop up? I've seen a case where a large number of ISY com errors does actually cause a lockup condition in MobiLinc. I'm investigating a solution. Another temporary solution is to go into the java console and disable those devices that the ISY can't communicate with. Wes
Recommended Posts
Archived
This topic is now archived and is closed to further replies.