Trying to answer FAQ questions about MIUI, can't find the right place.

Discussion in 'Question & Answers' started by David Tr, May 24, 2012.

  1. David Tr

    David TrMembers

    May 24, 2012
    21
    0
    11
    1. What is the difference between: www.miui.us and www.miuiandroid.com
    2. When using the "User Feedback" item for MIUI which sends reports via E-mail, where do those bug reports go, (other than the obvious (fc@miui.com)?
    3. If I wanted to help out with MIUI US where would I do that, where's their bug tracker and managing user feedback and getting that to dev's?
     
  2. iBotPeaches

    iBotPeachesScript Gatekeeper

    Oct 31, 2011
    3,811
    1,115
    335
    Kansas
    1) Preference I guess. We both do the same thing. Translate MIUI ROM into English and post ROMs. I guess you could say we have a closer tier to Xiaomi.

    2) The default is yes fc@miui.com, we used to allow people to send them to us, but there was SOO many reports it was insane. So the best thing to do is to send the report to yourself, then post that report in the bug section here. If you take the time and do that, I'll take the time and look at your bug.

    3) Well this is MIUIAndroid, not MIUI US. So I don't know where you can help there.
     
  3. David Tr

    David TrMembers

    May 24, 2012
    21
    0
    11
    Thanks for the reply Connor!

    1) Where's the main repo you guys work/develop/build against? SVN, github etc? So I guess Xiaomi is the company/organization that works on the original asian MIUI tree, and then you have a translation branch you build? Sub-branches for the different hardware handsets? I thought miui.com was the primary source of all MIUI site, miui.us was the english version of that primary entity. I was trying to figure out how here (miuiandroid.com) is a closer tier to Xiaomi (which I'm guessing are the people that maintain miui.com?)

    2) So you use this forum to track bugs, is there not an actual bug tracker (Bugzilla, sourceforge account etc.)? I would think it would be much more difficult to use a forum for tracking bugs. Administrative nightmare comes to mind :) There's bugs I've submitted in the past for MIUI, and more I'll submit in the future but I'm willing to track and followup on trying to get those fixed. (Volunteering to do some admin legwork if you need it).

    3) Well, I've worked with other open source projects in the past testing/tracking bugs etc and I'd want to make sure that I was working on the source tree that was going to contribute down to the main MIUI repo. Not some little used, branched offshoot. I'll post my latest bug report to the bug branch and go from there.
     
  4. iBotPeaches

    iBotPeachesScript Gatekeeper

    Oct 31, 2011
    3,811
    1,115
    335
    Kansas
    1) We have a public REPO here: https://github.com/miuiandroid/MI-ONE-ICS. I think the last commit was over 2 months ago though. We were in process in moving over to a new build system and the idea to publish stuff to the public has just fallen down the list of importance. Rest assured, we'll get back to that soon. We post daily XML changes via twitter though, if your curious about it.

    2) We use our Bug forum to relay bugs to Xiaomi to their bug tracker here: http://www.miui.com/forum.php?mod=forumdisplay_bug&fid=16
    You can't add bugs there unless your running the latest version of their software or have a staff role on their site. Since the English builds change the Updater to align with our OTA, China doesn't know what version your on so you cannot post on their bug tracker. The staff here also has staff accounts at Xiaomi, so we repost bugs once there confirmed here and are actual bugs. (We don't like posting stuff that isn't a bug). That embarrasses us :/

    3) No one really has access to the "source" of MIUI. Its a closed source product :/ Otherwise we'd be attempting some fixes. That right lies with the software team at Xiaomi. If you want to report bugs with our translations, I'll work on getting our REPO public. Its just one of those things were we currently have some "secret" build tools/methods contained in our translation. So we need to clear those out before we make em public. I'll try and do that this weekend. It'll be on bitbucket though, instead of github.
     
  5. emaz

    emazMembers

    Oct 14, 2012
    181
    19
    28
    IbotPeaches what do you mean with "Its a closed source product" ?

    i'm curious about
     

Share Our Site