1
iCam Support / Re: Issues with iCamSource 2.7 and Samsung Galaxy S4
« on: February 14, 2014, 02:28:06 PM »
Tried the "Clear Data" suggestion and it didn't resolve the issue.
Also tried out the new iCamSource 2.7.2 to see if it would work with my Galaxy S4 and it has the same issues I was having with v2.7. Viewing motion events causes the app to crash.
So I reverted back to v2.6 and it's working flawlessly.
However, I like to have the latest software updates and I don't want to be stuck at v2.6 as other enhancements are made in future versions and it seems like there was some kind of code modification made between v2.6 and v2.7 that is causing an issue. Filtering the Google Play comments for other users with my same phone show others are having similar issues:
Hugh - Shame:( keeps crashing; worthless!
Rick - Excellent Needs upgrading tho...starting to run really slow when accessing motion events
I appreciate the work you guys do and I really like the iCam software. Please let me know if there are any other suggestions for what I can do on my end or let me know if I can provide additional details about the issue so it can hopefully get resolved in later releases. Thanks!
Also tried out the new iCamSource 2.7.2 to see if it would work with my Galaxy S4 and it has the same issues I was having with v2.7. Viewing motion events causes the app to crash.
So I reverted back to v2.6 and it's working flawlessly.
However, I like to have the latest software updates and I don't want to be stuck at v2.6 as other enhancements are made in future versions and it seems like there was some kind of code modification made between v2.6 and v2.7 that is causing an issue. Filtering the Google Play comments for other users with my same phone show others are having similar issues:
Hugh - Shame:( keeps crashing; worthless!
Rick - Excellent Needs upgrading tho...starting to run really slow when accessing motion events
I appreciate the work you guys do and I really like the iCam software. Please let me know if there are any other suggestions for what I can do on my end or let me know if I can provide additional details about the issue so it can hopefully get resolved in later releases. Thanks!