Q2: what will happen if i just leave it as <uses-sdk android:minSdkVersion="4"/>. I have done so in the past without any obvious problem. But I need some comments.
If that is the case, shouldn't the targetSdkVersion in my manifest set to android:targetSdkVersion="19" instead of "17" or even "14". (Aside: I read elsewhere "14" is recommended as it has been thoroughly tested).
But why not "19" in order to match the android.jar file which I assume is version 19. What dictates the final number? That is what I am a little unclear.
Hello,
You can point to a higher Sdk because it is backward compatible (compatible with versions above).
So you don't have to change the path each time but only its target in the Manifest (if required). I have already seen people using a targetSdk numbered 99 without any problems (I don't know if they are other effects).
I have noticed occasional "lags" when reading data from sql db. The lag is noticeable by observing the progressdialog spinning round in circle taking quite
long to load data (~ 10 sec).
The occasional lag happened was when I have the manifest set to android:minSdkVersion="4" android:targetSdkVersion="14" or even "19".
But the lags disappear when I set the manifest to android:minSdkVersion="4" and no target value. And data got loaded fast (~ 1 sec).
I don't understand why and is it wrong to leave out targetSdkVersion?
The problem is now solved by not using Doevents in the loading data routine. But the only downside is that the progressdialog box "spinning" circle freezes. Can anything be done to solve that new problem?