Some critical words about the beta-tester engagement

[encore2097]

I was a bit late to the party and offered to help test but oman said the beta program was full.

I got in touch with another design house and we received an RK3288 box and have been in constant communication regarding issues and bugs. I even submitted some patches to increase stability and performance of the RK3288 box and I think that really impressed them.

I think the beta program is great idea but you have to make sure the beta testers are excited to help improve the product and know what they are signing up for and the expectations.

[FadeFx]

AW: Some critical words about the beta-tester engagement

I was a bit late to the party and offered to help test but oman said the beta program was full.

I got in touch with another design house and we received an RK3288 box and have been in constant communication regarding issues and bugs. I even submitted some patches to increase stability and performance of the RK3288 box and I think that really impressed them.

I think the beta program is great idea but you have to make sure the beta testers are excited to help improve the product and know what they are signing up for and the expectations.

I partially agree with this, but i think oman wanted to have endusers as testers so that was what he was looking for.

However, he should have had acloser look at the candidates and not just pick the first twenty.

[Finless]

Next time I will make a forum that ONLY the testers can post in. Everyone can read but cannot post. This will help keep it clean. That's what I can offer up as far as the forum goes.

In fact I could make this change right now. Move all the posts to a new test forum and lock posting to the testers. But what I would not have time to do it go through the posts and remove unneeded posts.

Bob

[FadeFx]

I am sorry and shut up already... ;-)

[Talas]

Next time I will make a forum that ONLY the testers can post in. Everyone can read but cannot post. This will help keep it clean. That's what I can offer up as far as the forum goes.

In fact I could make this change right now. Move all the posts to a new test forum and lock posting to the testers. But what I would not have time to do it go through the posts and remove unneeded posts.

Bob

Sounds a wise thing to do and people can still look and see all the Results/Stats/Information without the mess of unneeded posting.

[no_spam_for_me]

Next time I will make a forum that ONLY the testers can post in. Everyone can read but cannot post. This will help keep it clean. That's what I can offer up as far as the forum goes.

In fact I could make this change right now. Move all the posts to a new test forum and lock posting to the testers. But what I would not have time to do it go through the posts and remove unneeded posts.

Bob

not really need because "spam" isn't a problem... the problem had I described... it's the less engagement at some "tester" (and I talk about more than 50% of them)... and that wishes from oman will be ignored (e.g. get logs at HDMI issue)...

[no_spam_for_me]

... However, he should have had acloser look at the candidates ...

+1

[4WheelSpyder]

I am one of the guilty ones over the last few weeks, had a really tough time at the old salt mine -- 7 days a week (had to cancel a short vacation etc). Will hopefully taper off by the end of this week. (but we said that 2 weeks ago too)

Any time that we can see a new load? Waiting for the audio pass through to be fixed.

[no_spam_for_me]

... Waiting for the audio pass through to be fixed.

nice that you wait for it, but maybe oman need the logs to fix the issue???

[4WheelSpyder]

nice that you wait for it, but maybe oman need the logs to fix the issue???

I must have missed the post where oman requested the logs from everyone. Can you kindly point me to the "how to". I will glady do.

[4WheelSpyder]

BTW:
Logcat only document the application action!
If there exist some hw related issues like at HDMI at minimum a dmesg is indispensable!
(anyway it's also good to have a dmesg every time)

1. I wrote a little howto install ADB:
=> http://www.freaktab.com/showthread.p...l=1#post221238

2. If you don't know how to catch log files:
=> http://forum.xda-developers.com/show....php?t=2185929
=> http://forum.xda-developers.com/show....php?t=1123129

3. If you don't like to work via OTG with ADB:
=> http://forum.xda-developers.com/show....php?t=2621852
=> http://www.xda-developers.com/androi...r-wifi-helper/

All these points I suppose, if you enroll as a tester.

Okay, I have the adb basic setting going to extract the log files.

Where is the dmesg.log located and what process do I need to do to get the correct "window" from the log to pinpoint the HDMI issue?

Do I need to try and play a video file with surround sound etc.- is there some preferable sequence?

I suggest that oman or some of the developers create a "formal test request" thread wher the first post provide an index for all specific tests that needed pointing to posts where there is some test procedure described together with the required configuration - external equipment etc and where the results should be posted.

It has been a pretty free for all up to now which I believe it has something do with the lack of testing, because testers just don't know what is needed. This is pretty much what I have suggested before the testing started. Maybe I am just from a too formal testing environment. I think peanut butter finger testing is great for catching the unexpected but if you need specific data you have to have a procedure. This is key. (Our SQA guy will kiss me if he sees this coming from me - so please don't show this to him)

Someone has to take the lead here - no_spam_for_me?

[Finless]

not really need because "spam" isn't a problem... the problem had I described... it's the less engagement at some "tester" (and I talk about more than 50% of them)... and that wishes from oman will be ignored (e.g. get logs at HDMI issue)...

Well it is needed but I fully agree with you that some people that got the free device have not put in to help Beelink like they should as part of the deal to get a free device!

HELL... even the Dev's here have not gotten a device yet so you takers..... consider yourself on warning!

I will tell you this, Oman will probably ignore people in the future that have not contributed and "took the freebee and ran".

All I can say.... "Don't be a looser taker and not give back"!

Maybe I will help manage this in the future....

Bob

[oman]

Okay, I have the adb basic setting going to extract the log files.

Where is the dmesg.log located and what process do I need to do to get the correct "window" from the log to pinpoint the HDMI issue?

Do I need to try and play a video file with surround sound etc.- is there some preferable sequence?

I suggest that oman or some of the developers create a "formal test request" thread wher the first post provide an index for all specific tests that needed pointing to posts where there is some test procedure described together with the required configuration - external equipment etc and where the results should be posted.

It has been a pretty free for all up to now which I believe it has something do with the lack of testing, because testers just don't know what is needed. This is pretty much what I have suggested before the testing started. Maybe I am just from a too formal testing environment. I think peanut butter finger testing is great for catching the unexpected but if you need specific data you have to have a procedure. This is key. (Our SQA guy will kiss me if he sees this coming from me - so please don't show this to him)

Someone has to take the lead here - no_spam_for_me?

Because it's the first time we do such things,so many unexpected obstacle..
And I'm not have much time to engage the whole me into this,so..
But also say thank you to all of you..
And I agree with what you said

[ssspacman]

If some specific information is needed there should be clear instructions how to get that information as not everyone knows to for example get a logfile. I found a reboot bug (wifi internet charing) uploaded 2 videos to youtube showing device very warm and all cores at full speed, also a video about hdmi dolby problem. The device is very good and not many bugs have been found, my Minix X8H has many more bugs. I have reported every bug I found, even full screen problem in svtplay.

I think it is not how many times you post but what you post that should be important.

[Shomari]

Well it is needed but I fully agree with you that some people that got the free device have not put in to help Beelink like they should as part of the deal to get a free device!

HELL... even the Dev's here have not gotten a device yet so you takers..... consider yourself on warning!

I will tell you this, Oman will probably ignore people in the future that have not contributed and "took the freebee and ran".

All I can say.... "Don't be a looser taker and not give back"!

Maybe I will help manage this in the future....

Bob

..just briefly, as an observer: this is a worthy experiment.

But, for next time, assuming there is one, you should refine the process and part of that should include all of the above from Bob.