Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - colby908

Pages: [1]
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!





2
iCam Support / Issues with iCamSource 2.7 and Samsung Galaxy S4
« on: October 29, 2013, 09:07:26 AM »
I recently switched from an iPhone to a Galaxy S4 and immediately had issues when viewing Motion Events on the S4 (i.e. it would crash the app almost immediately). I was running iCamSource v2.7 on Windows 8 and it was working fine with the iPhone so there is something about Android or the S4 in particular that isn't compatible with iCamSource v2.7.

After trying a few different things I decided to switch back to iCamSource v2.6 and this has solved the issue. So, I'm not sure what was changed from v2.6 to v2.7 but just wanted to post about the issue so people were aware and so that hopefully the issue can be resolved in future releases of iCamSource.

Pages: [1]