Project highway - (SC)2MS

We have open-sourced entire OS for YUREKA/YUREKA PLUS, YUPHORIA and YUNIQUE. Inviting developers to participate in (SC)2MS program and submit contributions to this YU-OPEN-OS.

Source: All the source that you need to build for the YU devices you find here. With the build instructions.

Code review: Learn what you need to do and how can you submit the patches to the sources.

Projects: Explains how you can report bugs, and request for new features on Projects

Downloads: This section let you download our freshly baked software for your devices. Also the flashing steps are present there. Use it wisely.


Alright, Let's Begin !!

Source

We have open-sourced the entire build tree and kernel sources of the YU-OPEN-OS!

GitHub organization containing all sources:

Build Instructions
YUREKA/YUREKA PLUS/YUPHORIA:https://github.com/YUTeleventures/platform_manifest/tree/yu-mm6.0.1-msm8916
YUNIQUE:https://github.com/YUTeleventures/platform_manifest/tree/yu-mm6.0.1-jalebi

Device trees
YUREKA/YUREKA PLUS: https://github.com/YUTeleventures/device_yu_tomato
YUPHORIA: https://github.com/YUTeleventures/device_yu_lettuce
YUNIQUE: https://github.com/YUTeleventures/device_yu_jalebi

Flashing Instructions: https://github.com/YUTeleventures/factory-image-flash-tools

Contribute to YU-OPEN-OS: CODE REVIEW

Code review

Participate in and contribute to YU-OPEN-OS by submitting patches on Gerrit CodeReview

Code review lets developers know what changes others are contributing.

Submitting to Code review:

After syncing sources from

  1. Create local branch and submit changes:
  2. Example
    • repo start <new branch name> --all | <project>
    • repo checkout <new branch name> [<project>...]
    • repo start yu-mm6.0.1 --all
    • repo checkout yu-mm6.0.1
  3. To verify:
  4. Example
    • repo branch [<project>...] & repo status [<project>...]
    • repo branch & repo status
  5. Add and commit changes:
  6. Example
    • rcd [<project>...]
    • edit <files>
    • git add <files>
    • git commit <files>
    • cd <root>
    • repo upload <project>
    • git add .
    • git commit -m “Bug21 Fix issue”
    • repo upload YUTeleventures/android_frameworks_base

Alternate way of submitting to Code review:

After syncing sources from

  1. Add hooks for adding commit messages in git folder
    scp -p -P 29418 <Username>@codereview.yuplaygod.com:hooks/commit-msg .git/hooks/
    Example
    • scp -p -P 29418 ShradhaV@codereview.yuplaygod.com:hooks/commit-msg .git/hooks/
  2. Add files and commit changes
    git add <files>
    git commit -m "Commit Message"
    Example
    • git add .
    • git commit -m “Bug21 Fix issue”
  3. Create remote <URL> for review using any one of below
    ssh://<Username>@codereview.yuplaygod.com:29418/YUTeleventures/[Repository Name]
    OR
    http://<Username>@codereview.yuplaygod.com/YUTeleventures/[Repository Name]
  4. Add Code review remote
    git remote add review <URL>
    Example
    • git remote add review
    • ssh://ShradhaV@codereview.yuplaygod.com:29418/YUTeleventures/android_frameworks_base
  5. Push changes
    git push review HEAD:refs/for/<branch>
    Example
    • git push review HEAD:refs/for/yu-mm6.0.1

YU Code Review Process

Internal developerdoes code review and gives +/-1
  1. +1 would allow the tester to verify the code
  2. -1 would mean that the developer has to re-work on the code submitted
Testing
  1. A tester to download the revision build and test the functionality of the code submitted
  2. +/-1 to inform whether the code is tested and if it can be merged or rejected
Final Reviewer
  1. On all the +1’s the Final reviewer would recheck the code and decide whether to merge the code or not

Projects

YU-OPEN-OS projects and bugs are tracked on http://projects.yuplaygod.com




Reporting an issue

  1. Register yourself and Sign In
  2. Select respective project
  3. Users are requested to search the issues before creating a new issue to avoid duplicity.
  4. Add issues from New Issue tab. Users are requested to provide complete steps to reproduce the issue and provide screen shots, logcat, SW Version etc. if possible and fill out all the fields mentioned in new Issue list.

Creating new feature or improvement request

Users can also create a new feature request or an Improvement request, by filling the form with all required fields with detail description.

Fixing an issue

  1. After initial analysis, issue will be available to the developers for providing solutions. Community Manager will assign the issue to developer (either internal team developer or a community developer). A mail will be sent to them automatically after assignment.
  2. As soon as develop start working on the issue , he/she should change the status to as in Progress.
  3. Once issue is fixed by developer, solution should be committed to Gerrit code review. It is must for developer to mention the issues/feature/improvement id. E.g Bug#5, Feature #35.

Flashing Instructions

  1. Flash images with Fastboot
    1. Execute below commands in terminal
    2. Connect device in fastboot mode
      adb reboot bootloader
    3. Check if device is detecting in fastboot mode
      fastboot -i 0x1ebf devices
    4. Unlock bootloader fastboot -i 0x1ebf oem unlock
    5. Format User data
      fastboot -i 0x1ebf format userdata
    6. Flash kernel
      fastboot -i 0x1ebf flash boot boot.img
    7. Flash recovery
      fastboot -i 0x1ebf flash recovery recovery.img
    8. Flash system partition
      fastboot -i 0x1ebf flash system system.img
    9. Flash data partition
      fastboot -i 0x1ebf flash userdata userdata.img
    10. Relock bootloader
      fastboot -i 0x1ebf oem lock
    11. Reboot device
      fastboot -i 0x1ebf reboot
  2. Flashing zip file with ADB sideload
    1. Connect device in recovery mode by executing below command in terminal
      adb reboot recovery
    2. Select Apply Update from ADB
    3. Check if device is detecting in sideload
      adb devices
    4. Sideload YU-OPEN-OS
      adb sideload path_to_zipfile