---
# System prepended metadata

title: Review time! Let us have your feedback on how your device actually performs when plugged into a display -  'desktop' user experience for $device

---


| The "Test and support" section will appear with every device aimed at non-tech users, to help get them involved with the porting process. The idea is that they will start 'small', working from bug feedback (which anyone can do) and building up to active contributions. |
|------|
![](https://i.imgur.com/ciD7eha.png) |
| Things to consider |
|   |


# Review time! Let us have your feedback on how your device actually performs when plugged into a display -  'desktop' user experience for $device

Did the porter say that feature 'works' but you know from doing it that it really doesn't? Uh-oh... Well it is time to let the porter and everyone else know about the fail and send the tech magic back to the workshop for a makeover.

Except that if you are person 37 in that reporting queue, better go grab a Cappuccino instead. Three or four users waving their arms in the air will do. So to get started, go to ['UT Issues'](https://) and see if anyone got there first. If it is blank where the bug report should be you are definitely onto something! Or maybe not. Everyone can mess up so if there is only one report from #heyimconfused you better add a "Yep I saw that too". If you are first in line, know that a thing not working is a 'bug'. A bug report is easy. "Erm, I fell down a hole. Hey, I should be able to walk safely and not fall into holes. Okay, so I was wearing a blindfold and riding a horse backwards but.." 

1. Read '[Bug Reporting](https://docs.ubports.com/en/latest/contribute/bugreporting.html)' section in UBports docs
2. Then (this time), head to [$device Issues](https://) and submit it, so $porter knows about it.
3. Thank you so much for your report! 

Feels so good to help, am I not right? Here is more feelgood for you [more](https://)

## Help make our community shine!
Some things are just so important that they need to be tested every day, every week, every month. Just hang around in [QA group](https://) and try out the stuff that gets flagged. Backspace three times. Does the keyboard really freeze?!?! It may seem like you are doing almost nothing but you are the clue factory (you see what I did there?) and without your help the developers may sit there for days more, trying to figure out the puzzle. Just say hello and of course do let them know what device you have. maybe you just got very unlucky with yours.

"**Hi, my name is X, and I own Z. How can I help?**" that will do fine.

Unless that is you want to take a step up to [Proactive Tester](HTTPS://), but that is a whole different story.

## Proactive tester
This means you are going to push your devices to the max so others can enjoy theirs without a blip. Actually it isn't scary at all, but some testing comes around regularly and some needs a response like right now!

1. **OTA releases** once in a while, a new OTA [that means Over The Air btw] is announced by the core team, and (sometimes) things get broken, because things do. Shining a light on them now won't get an immediate fix but it means they will be tidied up later
2. **Experimental features** Maybe a developer is trying to add a feature by ~~stealing~~ re-using some code from another place


Are you up for it? If you are, reach out to $porter, tell him/her/them you are totally on board with checking out if their great new idea flies or is a dud. [You should know that as you are the first to test it may go horribly wrong. Switch to a new channel and everything will go back to where it should be but maybe don't mess with this stuff too much on your daily driver phone!] 








