The same problem.

It does not work - ns.close ()

It does not work - ns.dispose ()

Tried AIR3.1, AIR 3.2, AIR 3.3

Further feedback regards this fix.  It certainly opens up video app development and allows for slick demos.

However, since videos are not freezing up I can now see clearly the buffering that's going on which seems to be another area that needs attention... Any hints/feedback regards this would be appreciated.

Specifically, I find a fair disconnect in behaviour between video playback on the desktop and on Android.  This may be because of Android design but this should be noted since it might lead another change at Adobe's end.

The behavior is as follows (note that this includes my own created videos and videos obtained from the internet -- my videos work a little bit better and I know that one thing I usually do is CBR, constant bit rate which may help things) :

on the desktop===>: 100%, all wireless network video streams buffer flawlessly... roughly speaking, about 20 seconds of video every second, plus if you seek to an unloaded part, the video patiently waits until that part is loaded

on android===>: all wireless network video streams seem to have their own signature for buffering. Although many of the streams will buffer normal, maybe half buffer normally for 100 to 250 seconds of video data and then stop and wait for the playback to catch up, after which time they buffer slowly. This stop can therefore be 100+ seconds that no buffering is occuring. A few of the videos will even forget to continue buffering ( a netstream.buffer.empty is eventually fired and game over )  The behaviours are essentially repeatable for each video (I have my worst case video) although if you seek forward sometimes it will remember to resume buffering right away.   Another symptom is that unlike the desktop, you cannot seek to an unloaded part, instead you generate a nestream.seek.invalidtime and the video simply resumes (I actually workaround this as I suspect it causes problems for me if I don't).

There are other discrepencies that I ask which is proper / better ?  ===> on desktop a pause does not interrupt buffering, while on Android a pause stops the buffering....====>   on desktop there seems to be a cache for the videos if you jump around between them while on Android everything is cleared out on the dispose()

as mentioned above, any hints/feedback would be appreciated. I'm trying to relate this to other outstanding forum and outside forum related issues and still thinking the fail part might be an Android/hardware realtionship but not sure and analyzing.

thanks.

Message was edited by: hiteck7 4:53pm Friday