Hi,
I have persistently been troubled by not being able to stop the virtual device started through AVD (or called by B4A to the AVD).
Anyway... the situation is very simple: everything works and I can do all I want with coding and testing, until... I am done and want to close the virtual device...
That never closes: it just simply "hangs" and is being unresponsive.
anything else still works and I can do all I want but that VD simply stays hanging to the point when I want to shutdown my PC: which it never does, while that VD windows is still hung!
Btw: I am using XP-SP3
Now the question: I found on several forums that there is a known bug with AVD that has the above effect and can be solved by adding -noaudio to the command line when starting the virtual device.
Is there a place in B4A where a can add/insert that option?
Cheers,
Poul DK.
I have persistently been troubled by not being able to stop the virtual device started through AVD (or called by B4A to the AVD).
Anyway... the situation is very simple: everything works and I can do all I want with coding and testing, until... I am done and want to close the virtual device...
That never closes: it just simply "hangs" and is being unresponsive.
anything else still works and I can do all I want but that VD simply stays hanging to the point when I want to shutdown my PC: which it never does, while that VD windows is still hung!
Btw: I am using XP-SP3
Now the question: I found on several forums that there is a known bug with AVD that has the above effect and can be solved by adding -noaudio to the command line when starting the virtual device.
Is there a place in B4A where a can add/insert that option?
Cheers,
Poul DK.