Other than canned responses to community posts it seems like most communications travel to Samsung. How about Samsung trying to provide meaningful and current information about the beta PROCESS to beta testers- estimated time to next beta, estimated time to release of final updates. I think this would go a long way to helping create a satisfied testing base.
While what you all for sounds reasonable it really isn't. I have been around Android development for years and try and get in betas as often as I have time to actually test the beta release it. As a rule of thumb you won't get etas from developers. There are many reasons for that, not being surprised which changes to release to the beta, just release when the coding is done which kills "etas", not sure which fix will get all bugs out to call "final update", etc. Like I said, what you ask sounds reasonable but when you get into coding you realize it isn't as easy you'd think to release etas.
