[ROM][7.1.2][OFFICIAL] Team OctOS Oct-N [WEEKLIES][cancro]

[aniket.lamba]

Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.

Team OctOs presents Oct-N.​

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

We have Gapps here.

http://opengapps.org
***USE Gapps of your choosing, we prefer Open Gapps***


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

Feature List

• Substratum rootless theme engine support (must install Substratum from play store)
• Tentacles settings!
• Pixel Launcher Included
• OmniSwitch
• Power menu options
• Screenshot
• Screen record
• DPI settings
• Status bar time and date options
• Status bar network traffic indicator
• Status bar notification settings
• Quick tile settings
• Volume button playback control
• Volume button wake
• DUI (fling, pulse, smartbar)
• Screen record
• And much more!!!!

Frequently Asked Questions
Q: Is this Android 7 (Nougat)?
A: Yes, this is Android 7.1.2

Q: What code is Oct-N based on?
A: This version of Oct-N is based on LineageOS 14.1

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 all the others 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-N.

Q: What about root?
A: Root is removed by default (user will be able to flash which ever root zip they want)

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:

1. Download ROM .zip file and MD5 file, and grab your favorite Open Gapps package http://opengapps.org
2. 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 ---
   The Oct-N ROM installation script will automatically wipe /system, /cache, and /dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your Gapps Provider. When dirty flashing weekly updates, you MUST reflash Gapps along with any other files, apps, custom mods or kernels etc.. (anything that resides in system partition)
3. Flash ROM, GApps and any additional .ZIP files
4. Reboot

Download
Download from Team-OctOS web site!
Change log
View change log on Team-OctOS web site!

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-N available on our GitHub repositories.

Unless otherwise specified, all Oct-N builds kernel souce can be found on github at Team-OctOS.

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
Donate to OctOS Development (PayPal)

Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions

Special thanks to

• Our testers, without which, there would be no public releases for OctOs
  
  We would also like to thank
• AOSP
• Open Gapps
• LineageOS
• Anyone else who has ever submitted Open-Source code

Follow Team-OctOS!


XDA:DevDB Information
Oct OS, ROM for the Xiaomi Mi 3

Contributors
aniket.lamba, manfromgta
Source Code: https://github.com/Team-OctOS

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: A custom recovery (TWRP preferrable),ROM and Gapps zip file,knowledge on how to flash zip files.
Based On: Lineage

Version Information
Status: Stable

Created 2015-12-26
Last Updated 2017-04-29

 

[aniket.lamba]

OctOS 6.0.1

Team OctOs presents Oct-M.

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

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

Frequently Asked Questions
Q: Is this Android 6 (Marshmallow)?
A: Yes

Q: What code is Oct-M based on?
A: Starting with Oct-M, we've rebased OctOs on Aosp code.

Q: What happened to CM?
A: Octos was originally formed as an AOSP source rom. We have returned to those roots.

Q: Why isn't there XXXXXXX 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 CM and all the others have..
A: ROM developers, including CM, 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:

1. Download ROM .zip file, and grab your favourite gapps package
2. 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 ---
3. Factory Reset from TWRP
4. Flash ROM and GApps .ZIP files
5. Reboot

* Weekly Builds

* Release Builds

* Gapps 6.0 Mini

​

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

A Special thanks to @audahadi for his device sources.

Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions




Follow Us at the various websites below!


Kernel source - https://github.com/kernel-hut/android_kernel_xiaomi_cancro
Device - https://github.com/audahadi/android_device_xiaomi_cancro
Vendor - https://github.com/audahadi/proprietary_vendor_xiaomi

 

[aniket.lamba]

Bugs/Issues

[*]You tell me

 

[marko94]

Some ss

Rom is great for now.. all basic things works .. that is for now xD

 

[gary138.138]

Trying this rom for a few hours, I observed the followings:

The rom is smooth and rather fast.
Almost everything works properly.
Xposed works on this rom without any problem.
Battery life is reasonable.

Thank you so much, aniket.lamba.:good:

 

[rajib4]

@aniket.lamba hi bro, I have a query.
But before that thanks a ton for the wonderful work you have done with this ROM :thumbup: Your Metallium ROM was my favorite LP ROM and I used it as my daily driver from the time it got released and never had to look at any other ROM after that as it was rock stable and super fast

Now for the query, was going through a post by John Cannon Jr on TeamOct G+ community where he mentioned that for non-nexus devices CM will be the base going forward. So for cancro-marshmallow will you continue the AOSP base or will change the base to CM in future? Asking this as there are lot of CM based ROMs available for cancro-marshmallow but not many AOSP based.

Cheers

 

[aniket.lamba]

@aniket.lamba hi bro, I have a query.
But before that thanks a ton for the wonderful work you have done with this ROM :thumbup: Your Metallium ROM was my favorite LP ROM and I used it as my daily driver from the time it got released and never had to look at any other ROM after that as it was rock stable and super fast

Now for the query, was going through a post by John Cannon Jr on TeamOct G+ community where he mentioned that for non-nexus devices CM will be the base going forward. So for cancro-marshmallow will you continue the AOSP base or will change the base to CM in future? Asking this as there are lot of CM based ROMs available for cancro-marshmallow but not many AOSP based.

Cheers

Initially it'll be CM based.As the ROM development progresses further,we might shift to the AOSP base.

 

[Me_Ashish_]

Some ss

Rom is great for now.. all basic things works .. that is for now xD

Are there CM themes? The app drawer shows it is, ur settings screenshot (might have missed), doesn't show that. Also the ROM is AOSP based.
No slow charging bug?

---------- Post added at 03:56 PM ---------- Previous post was at 03:48 PM ----------

Initially it'll be CM based.As the ROM development progresses further,we might shift to the AOSP base.

"might shift", does that mean it is CM based right now. The FAQ question and the 'based on' posted on the op shows AOSP atleast.

 

[aniket.lamba]

Are there CM themes? The app drawer shows it is, ur settings screenshot (might have missed), doesn't show that. Also the ROM is AOSP based.
No slow charging bug?

---------- Post added at 03:56 PM ---------- Previous post was at 03:48 PM ----------


"might shift", does that mean it is CM based right now. The FAQ question and the 'based on' posted on the op shows AOSP atleast.

For the initial stage it is CM based,this build which I've posted is an initial build (considering it still has issues) so we chose CM base as we draw more support of non-nexus devices,we'll shift the base to AOSP.I'll change the thread title so the users won't have a problem figuring out.

 

[DutchMan_1990]

I have a doubt...does ambient display has a BUG or it's not working just for me.

 

[Me_Ashish_]

I have a doubt...does ambient display has a BUG or it's not working just for me.

Never heard of someone who got Ambient Display working anytime. It just shows the, doesn't supports though.

 

[Me_Ashish_]

Is it only me or the ROM doesn't support extended partition?
I tried flashing twice, but after installing GAPPS. Xposed doesn't get installed due to no space.
Also the maximum CPU frequency doesn't change at all

 

[diongdyh]

Is it only me or the ROM doesn't support extended partition?
I tried flashing twice, but after installing GAPPS. Xposed doesn't get installed due to no space.
Also the maximum CPU frequency doesn't change at all

Apparently you're not on extended partition. Your system is only 660mb instead of 1.2gb which means you're on stock partition. Did u flash MIUI recently? It might've reverted your partition to stock.

Sent from my MI 4 using Tapatalk

 

[Me_Ashish_]

Apparently you're not on extended partition. Your system is only 660mb instead of 1.2gb which means you're on stock partition. Did u flash MIUI recently? It might've reverted your partition to stock.

Sent from my MI 4 using Tapatalk

That's not the case. Some ROMs work at stock even though you are on extended partition. Though I knew it's not my phone I still anyways re flashed extended partition ZIP leading in same result.
BTW installing MIUI or any other ROM via recovery doesn't make you loose ur extended partition.

 

[diongdyh]

That's not the case. Some ROMs work at stock even though you are on extended partition. Though I knew it's not my phone I still anyways re flashed extended partition ZIP leading in same result.
BTW installing MIUI or any other ROM via recovery doesn't make you loose ur extended partition.

If you've flashed the extended partition and it's still in 660mb means that you've failed. I know only flashing miui through fastboot gets you to stock partition. The point is you're on stock partition.

Sent from my MI 4 using Tapatalk

 

[Me_Ashish_]

If you've flashed the extended partition and it's still in 660mb means that you've failed. I know only flashing miui through fastboot gets you to stock partition. The point is you're on stock partition.

Sent from my MI 4 using Tapatalk

Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.

 

[diongdyh]

Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.

Ooh did u mean that after flashing this ROM your system partition got reset to default (660mb)?
Cuz in the screenshot you attached it shows that you only have 660mb.

Sent from my MI 4 using Tapatalk

 

[marko94]

Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.

yeah,same happened to me.. I am also on extended , but after flashing this rom , my partition go back to stock.. easy fix for that, go to recovery, backup rom, restore rom,reboot and now all is fine xD

 

[mallik_raj]

yeah,same happened to me.. I am also on extended , but after flashing this rom , my partition go back to stock.. easy fix for that, go to recovery, backup rom, restore rom,reboot and now all is fine xD

I too faced the same issue and with other ROMs too. There is an easy fix. If you are using twrp, go to Wipe->advanced Wipe Select "System" and click "repair or Change File system" below. Then Select "Resize". The issue will now be fixed.

If you are flashing ROM and Gapps, do the above step after flashing ROM before installing the Gapps.

 

[Manu11]

Is this rom cm based or aosp based?