Announcement

**FadeFx** · 09-16-2014, 06:18

Word!!! even thou i dont have a device i did even post more often in this subforum than many of the beta testers. Too bad you can not know this before sending out the devices. Next time maybe include killswitches into the beta devices and firmwares ;-)

**roolmapool** · 09-16-2014, 06:48

I agree.

Same problem with donations for devs.... Seems a few users do that... Sad.

**oman** · 09-16-2014, 08:08

Thanks ,Tom,you said out what I am confusing now..

But But,I must admit our R89 is not perfect enough,not fresh now times,just more powerful CPU/GPU or so-called 4k, Giga-Ethernet? It's just a Android MediaPlayer,you may see many kinds of such devices.

Maybe you are a little tired of such devices,or because of the custom fees,the lacking of accessories?The case shape,or the package style?I dont know..

My beginning starting point here is launching a more stable and powerful device according to users' expectations ..but now I dont know..there are so many rk3288 boxes around market..But I'll do what I can do here..

**FadeFx** · 09-16-2014, 08:23

Oman, just dont give up, you know you do a good job here...

**Talas** · 09-16-2014, 08:51

Originally posted by oman View Post

Thanks ,Tom,you said out what I am confusing now..

But But,I must admit our R89 is not perfect enough,not fresh now times,just more powerful CPU/GPU or so-called 4k, Giga-Ethernet? It's just a Android MediaPlayer,you may see many kinds of such devices.

Maybe you are a little tired of such devices,or because of the custom fees,the lacking of accessories?The case shape,or the package style?I dont know..

My beginning starting point here is launching a more stable and powerful device according to users' expectations ..but now I dont know..there are so many rk3288 boxes around market..But I'll do what I can do here..

Beelink and Oman need and deserve all the help users and Testers can give them as they did a very rare thing they trusted a team of people to use and test a device they would to improve on to give the customers the best device they could and trust them on there word..its a fantastic approach and so rare for company to hand over there devices to such a public group.
Got to take my hat of to Beelink for there wisdom and if you need a company who you can trust to not only sell you a device but listen to the end user and there problems and issues and help to resolve them put your money Beelink / Nexteons way..you wont regret it.

**Arbelzapf** · 09-16-2014, 09:31

A couple of things:

1.
The R89 is already pretty damn good. Maybe, for some people, there "just isn't much to test". If you aren't affected by the AV-Receiver sound issue, this beta unit works better than something a competitor would sell to the masses & charge 150$ for.

I'm aware that the R89 is now sold as well, but I think we beta testers all expected something that's completely and utterly broken, much more than what we sadly have come to expect when buying Android TV boxes.

So it's been a very pleasant surprise how well this thing runs. That may be part of the reason it's rather quiet around here.

2.
I believe a public subforum is not a good place to pull off the majority of this test. Sure, we need it for stuff like new firmware releases, announcements, stuff that everyone needs to see. But some sort of issue tracker or at least a couple of google docs would have helped organize feedback, as well as given some way of tracking it. "Tracking" is not a nice word, but you could have seen at a glance who's never/hardly been active and you could have PM'd them on the forums or something. If they ran away and don't respond, that sucks ....and it's probably part of how these things go. But now it's almost impossible to get some hard numbers about user activity without going through a number of multi-page threads and counting by hand.

Also, forum threads often tend to bury important information under loads of petty arguments and off-topic discussion. The only way to track what's going on here is to memorize it.

Please don't get me wrong, I don't want to put the blame on oman. This is all meant as constructive feedback. You decided to be very open about this test, which I greatly appreciate. Maybe people wouldn't have been using those tools I mentioned and we'd have ended up with even less activity. I don't know.

I'm probably not good at predicting human behaviour. But I suspect that a more rigid setup might have created a sense of urge among testers. "We gave you these devices, and we expect you to fill out these forms".

Now it's "just another subforum" where people post when they feel like it.
As I said, I could be wrong. I just think this could be part of the problem and if you choose to do this again, it might be worth a shot to try out something else. I remember that this was suggested and discussed before the units were sent out.
If you're serious about it, be serious about it.

3.
I think it's not as bad as no_spam makes it out to be. There are more than 5 people regularly posting here from that list. I can't say it's much more,so his points are still very valid, but I think we have 8-9 testers that regularly post here, some more often than others, of course.
That's not amazing, but it's absolutely something we can work with. 15 would have been a good number, since there's always stuff going wrong and there always are a few bad apples. "Less than half" active testers sounds terrible, and it probably is. But given how few problems this device actually has left, we should be able to help oman on the last steps to a device that's not just "very good", but "great".

**Smokez** · 09-16-2014, 09:57

I kind of have to agree here, the nail on the head for me was, once the initial sound issue was resolved, bearing in mind I don't have any kind of AV receiver, it's a struggle to find anything to report on after my initial hardware compatibility tests and stability/performance testing.. otherwise the threads would be filled with, works great, yeah no problems, works fine, running perfect etc etc etc! As time goes on we might see more involvement from some testers that have been inactive, but there's at least a 95% chance some have had there freebie and run.... Unfortunate but true.. as for me I'm here, I've got 2 RK3288 boxes now including a 32GB/4GB RAM model that needs some attention, way more than the R89 does, and I flick between the 2 in between working 5 days a week, decorating my new house, being a Dad to a 2 year old little girl, and keeping my pregnant Mrs happy who's ready to bring me another daughter any day now, so naturally my hands can be quite full at times, but I still make the effort to report back when needed and test anything omans asking..

Just my 2 cents

**oman** · 09-16-2014, 10:26

Originally posted by Arbelzapf View Post

But some sort of issue tracker or at least a couple of google docs would have helped organize feedback, as well as given some way of tracking it.

Totally agree with this,but at the beginning I didnt follow this advice..Now I realize this's important..Anyway,next time we should try this.

**FadeFx** · 09-16-2014, 10:35

Still its a learning by douing process, finally you are a still young small company doing this. However, there is much to learn from projects like cyanogenmod...

**Talas** · 09-16-2014, 12:04

Originally posted by oman View Post

Totally agree with this,but at the beginning I didnt follow this advice..Now I realize this's important..Anyway,next time we should try this.

You could get a bugs/issues thread and break it down to specifics if you wish then at least you have a cohesive look at where things stand at this moment.

**goldenrod** · 09-16-2014, 13:19

Aside from the HDMI audio issue, the R89 works very well -- better than the S89 from the time I got it. The S89 is a good box, too, but it doesn't compare in several key areas.

The R89 has faster, more stable wifi than the S89.
The R89 has much faster performance than the S89.
The R89 has a cleaner launcher/interface than the S89.
Several apps (like Xfinity Go) work with the R89 that don't work with the S89.
All the peripherals I have (mouse/keyboard combos, flash drives, hard drives etc.) work well with the R89.

The only lingering issue for me is the AVR HDMI audio problem. Once that's settled, there will be nothing to complain about with the R89.

**sweup** · 09-16-2014, 13:41

For me the hard part is that i got no sound thru my AV-setup (yes, logcat dropped in forum). It's really hard to switch directly to TV when doing test, if the sound part worked for me it would be easier to evaluate on daily basis.

Most impressing so far is boot up time, really fast comparing to X8. Navigation is working smothly.

**no_spam_for_me** · 09-16-2014, 14:22

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.

**FadeFx** · 09-16-2014, 15:08

AW: Some critical words about the beta-tester engagement

Originally posted by no_spam_for_me View Post

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.

Osmonitor is also a good tool to catch logs on device, as well as catlog

Announcement

Announcement

Some critical words about the beta-tester engagement

Some critical words about the beta-tester engagement

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

What's Going On