[Nexus 5 Android Development] cjkacz:
​

Team OctOs presents Oct-M.​

We maintain a current release record and change-log on our website: http://www.teamoctos.com

Weekly Marshmallow builds found here:

https://www.teamoctos.com/weekly-builds

We have Gapps here.

Mini (239 mb)

http://opengapps.org/?download=true&arch=arm&api=6.0&variant=mini

Micro (136.2 mb)

http://opengapps.org/?download=true&arch=arm&api=6.0&variant=micro

Nano (100.3 mb)

http://opengapps.org/?download=true&arch=arm&api=6.0&variant=nano

Pico (58.1 mb)

http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico

These are fully working 6.0 MM gapps built and maintained by OpenGApps. All credit goes to Opengapps, please show them some support!

- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -​

Team OctOs would like to thank Team Blackout for the use of their Blacked Out Nexus Launcher & for saving eyes one app at a time!

You can get all the TBO goodies here as well as the TBO Updater http://teamblackedout.com/ #whiteuimustdie

TBO thread http://xdaforums.com/showthread.php?p=41545802​

Frequently Asked Questions

Q: Is this Android 6 (Marshmallow)?

A: Yes, this is Android 6.0

Q: What code is Oct-M based on?

A: Starting with Oct-M, we rebased OctOs back to AOSP code. After a short love affair with AOSP we had to return to CM as a base.

Q: What happened to AOSP?

A: All Android code is based on the Android Open Source Project (AOSP). Those of you who have been here from the beginning know Octos originated as an AOSP based rom. In order to support our legacy "CAF" devices we had to use CM as a base. In the end we were just to short handed to maintain both branches. So we had to return to CM for all devices.

Q: Why isn't there XYZ feature?

A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it

Q: But XYZ and all the other roms have..

A: ROM developers build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-M.

Q: Superuser or SuperSU?

A: Team OctOs uses SuperSU and is installed automatically.

Bugs:

Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.

Logs, Logcat, and the Android Debugging Bridge (ADB)

Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.

Log file APKs

Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.

ADB Logcat

The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.

ADB Logcat tutorial here: How to create a logcat log

Basic Instructions:

Download ROM .zip file and MD5 file, and grab your favorite gapps package

Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)

--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---

Factory Reset from TWRP

Flash ROM and GApps .ZIP files

Reboot

The Oct-M ROM installation script will automatically wipe /system, /cache, and /data/dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your GApps Provider

The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-M available on our GitHub repositories.

Unless otherwise specified, all Oct-M builds use the device's stock kernel.

Team OctOs GitHub - http://www.github.com/Team-OctOs

Team OctOs Gerrit Review - http://www.teamoctos.com:8080

Team OctOs GPLv2 License - http://www.teamoctos.com/license/

Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs

Want To Build Your Own?

Check out the ReadMe on our GitHub for Instructions

Follow Us at the various websites below!

XDA:DevDB Information

Oct-M, ROM for the Google Nexus 5

Contributors

cjkacz, canodroid15, hedwig34, bthorne79

Source Code: http://www.github.com/Team-OctOs

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.10.x

Based On: CyanogenMod 13

Version Information

Status: Testing

Created 2015-02-20

Last Updated 2016-08-26