"Can you explain how a different IDE would effect how a program executes? "
Sure thing.
When you import the project from Eclipse with ADT into Android Studio and/or Visual Studio the library references will should/would probably get updated. So instead of using something like the Android 4 support library version 20.15 (or whatever) you would be using the latest version of that library whatever that happens to be. Because the problem is occurring intermittently it may not be a problem with code that the user created, but the library that Google has provided. Google does update their libraries at least once every two months and bugs do get fixed. There is also a chance that one or more of the linters or plugins provided for Visual Studio or Android Studio does a better job then the comparable version with Eclipse. When the project is imported into Android Studio, Android Studio does many checks and some things could easily fixed (or broken for that matter),
Aside from all of the above, with Android Studio and I believe Visual Studio as well, you can quickly and easily emulate different devices with different screen sizes, storage space and RAM, which you could use. This could be used to quickly see what happens when you run out of RAM, just decrease what the emulated device has available. And you can rotate the display of the device or change the resolution/DPI. I know that this functionality was included with ADT, but with
https://developer.android.com/studio/run/index.html the wait times have been drastically reduced for sending the changes to the emulated device to see your results.
Not only that Google is no longer supporting the ADT plugins with Eclipse per the announcement posted here
https://developer.android.com/studio/tools/sdk/eclipse-adt.html
"The Eclipse ADT plugin is no longer supported, as per this announcement in June 2015.
The Eclipse ADT plugin has many known bugs and potential security bugs that will not be fixed."
I personally (and I'm not expert) would think that using the IDE recommended by Google for Android development would get you the best results.
For instance, and this is just a
hypothetical here so please don't jump down my throat, but one of the files could be saved using UTF-8 instead of UTF-16. There could have been, and I'm not saying that there is, a problem with ADT or Eclipse when a file was saved or something like that. Or perhaps something was interrupted slightly wrong when the APK was created using ADT (again
hypothetical). And yes I do realize that Google and/or Microsoft can and most likely have made left some bugs in Android Studio and Visual Studio, however I personally think that it would be better to use either of those to diagnose the problem.
I know that plenty of people still use Eclipse for a lot of development, including Android development, however if you are running into seemly random recurring problems then it's possible that the IDE you are using can be part of the problem, especially when it's not supported by the company what created it for the last two years or so.
Eclipse is free, Android Studio is free, Visual Studio is free, you only cost is the bandwidth, some hard drive space and your time learning the IDE for any of them.
All that aside,
you should connect your device to your system to get diagnostic data from the Android debugger. Maybe when you get a better idea as to what is happening under the hood, thanks to the debugger, you'll see something like a variable isn't set correctly or that all of your memory is being used up for something else, etc who knows?
1
