[ROM]Team OctOs Oct-MM

[Grommish]

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-MM.​

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. -​

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://forum.xda-developers.com/showthread.php?p=41545802​

Frequently Asked Questions
Q: Is this Android 6 (MarshMallow)?
A: Yes, this is Android 6.0.1

Q: What code is Oct-MM based on?
A: Starting with Oct-MM, we've rebased OctOs on the CyanogenMod 13 code. Modified to give you a smoother more stable rom.
We like to Strive on being closest to AOSP as possible but also being able to support multiple device

Q: What happened to AOSP?
A: All Android code is based on the Android Open Source Project (AOSP). Under previous releases, we tried very hard to limit the number of "Not from Google directly" repositories that we used. Unfortunately, issues with devices, the need for Code Aurora Foundation (CAF) repositories for Qualcomm devices, and compatibility issues meant fighting code more often than not. We decided that since the code-base for many repositories were the same across most ROMs, picking a starting point to build the user experience on outweighed the desire to craft code from scratch, or fix broken code to make it work with other changes we already had.

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-L.

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 MD5 file, and grab your favorite Android 6 based GApps[/URL] 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

DOWNLOADS​

Stable: https://www.teamoctos.com/supported-devices/​

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

Recomended Gapps: http://opengapps.org/​

The Oct-MM 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-MM available on our GitHub repositories.

Unless otherwise specified, all Oct-MM builds use the device's stock CyanogenMod 13 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

Special thanks to

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

Follow Us at the various websites below!


XDA:DevDB Information
Oct-MM, ROM for the Verizon Samsung Galaxy S4

Contributors
Grommish, CjKacz, canodroid15, bthorne79
Source Code: http://www.github.com/Team-OctOs

ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Baseband MDK - Non-SafeStrap
Based On: CyanogenMod 13.0

Version Information
Status: Stable

Created 2015-02-17
Last Updated 2016-08-26

 

[ShadyPossum]

just want to confirm, this is NOT SafeStrap compatible?

 

[jhr5474]

just want to confirm, this is NOT SafeStrap compatible?

It says it uses the Cyanogenmod based kernel so no it is not safestrap friendly.

 

[Grommish]

just want to confirm, this is NOT SafeStrap compatible?

It says it uses the Cyanogenmod based kernel so no it is not safestrap friendly.

Correct. If you are above the MDK baseband, you're limited to TouchWiz.

Updated ProjectDB for Firmware Requirements..

 

[Alxoom33]

Team OctOs presents Oct-L.

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 5 (Lollipop)?
A: Yes, this is Android 5.0.2

Q: What code is Oct-L based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12 code.

Q: What happened to AOSP?
A: All Android code is based on the Android Open Source Project (AOSP). Under previous releases, we tried very hard to limit the number of "Not from Google directly" repositories that we used. Unfortunately, issues with devices, the need for Code Aurora Foundation (CAF) repositories for Qualcomm devices, and compatibility issues meant fighting code more often than not. We decided that since the code-base for many repositories were the same across most ROMs, picking a starting point to build the user experience on outweighed the desire to craft code from scratch, or fix broken code to make it work with other changes we already had.

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-L.

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 MD5 file, and grab your favourite Android 5 based 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

The Oct-L 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-L available on our GitHub repositories.

Unless otherwise specified, all Oct-L builds use the device's stock CyanogenMod 12 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-L, ROM for the Verizon Samsung Galaxy S 4

Contributors
Grommish, CjKacz, bthorne79, hedwig34
Source Code: http://www.github.com/Team-OctOs

ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Baseband MDK - Non-SafeStrap
Based On: CyanogenMod 12

Version Information
Status: Testing

Created 2015-02-17
Last Updated 2015-02-17

Congratulations! Would like to try. Is there a DL link? Couldn't find it in the OP.
Thanks![emoji106]

---------- Post added at 02:27 PM ---------- Previous post was at 02:07 PM ----------

Sorry, I am not sure how to use a spoiler in TT.

 

[Grommish]

Congratulations! Would like to try. Is there a DL link? Couldn't find it in the OP.
Thanks![emoji106]

---------- Post added at 02:27 PM ---------- Previous post was at 02:07 PM ----------

Sorry, I am not sure how to use a spoiler in TT.

There isn't anything like that is the OP. If you're seeing that, its TapaTalk doing it. I'd recommend the desktop version, as I do not use TapaTalk or the XDA Mobile app.

All of our releases, license information, and known issues can be found on our website www.teamoctos.com

 

[Sir Lancelot]

I'm not finding it on the web version either.

Perhaps less subtly? I don't mean to be snarky but some of us live on our phones. I can't test what I can't access.

Sent from my rooted tri-corder

 

[Grommish]

I'm not finding it on the web version either.

Perhaps less subtly? I don't mean to be snarky but some of us live on our phones. I can't test what I can't access.

Sent from my rooted tri-corder

We even have a theme specifically for mobile devices. Check the Screenshots below for a step by step.

 

[Alxoom33]

Good to know! But nobody will go there, unless directed to do so in the OP. I suggest linking your downloads page to the OP.

 

[Grommish]

Good to know! But nobody will go there, unless directed to do so in the OP. I suggest linking your downloads page to the OP.

We've discussed it. At this point, across just the S3 and S4 devices, we've had something like 800 downloads. People are finding it.

Speaking only for myself, I'd rather anyone who either cannot or will not read the OP to move to another ROM. Flashing a device is a risky operation in the best of times. Anyone who says "I can't find" or "Why don't you just tell me", when it is literally the first thing after the logo, means that when they fail to do something and soft-brick their device (or in the case of the jfltevzw, hardbricks their device because they are safestrapped) then I have to listen to it and deal with it. Besides, it makes the entire project look bad.

I went out and got the XDA app, just to see what those who are looking at it see. See the screenshot below.

I will link you directly to a post, however, from the dev-blog entitled There be Dragons here in which I look at people's ability to treat their mobile devices like toys, rather than $700+ electronic devices. Any user who wants to be hand-held can do it in another thread. Flashing is as safe as we can make it, but I've personally had flashes go bad, and the ability to recover the device means following instructions. If anyone cannot figure out how to download the ROM, especially given the screenshot below, again, I'd rather not have them flash it.

 

[Sir Lancelot]

Well. As a usability engineer with 15 years of working on UI and websites I can only say:
1. Blaming your users gets you nowhere.
2. Your level of adoption is in your own hands.

Sent from my GT-I9505G using XDA Free mobile app

 

[maximusmullivan]

Well. As a usability engineer with 15 years of working on UI and websites I can only say:
1. Blaming your users gets you nowhere.
2. Your level of adoption is in your own hands.

Sent from my GT-I9505G using XDA Free mobile app

Just stop already. It's on us as users to educate ourselves! We've all had to do it. Don't blame the dev! Not his fault you can't navigate the internet.

Sent from my Nexus 7 2013

 

[Alxoom33]

We've discussed it. At this point, across just the S3 and S4 devices, we've had something like 800 downloads. People are finding it.

Speaking only for myself, I'd rather anyone who either cannot or will not read the OP to move to another ROM. Flashing a device is a risky operation in the best of times. Anyone who says "I can't find" or "Why don't you just tell me", when it is literally the first thing after the logo, means that when they fail to do something and soft-brick their device (or in the case of the jfltevzw, hardbricks their device because they are safestrapped) then I have to listen to it and deal with it. Besides, it makes the entire project look bad.

I went out and got the XDA app, just to see what those who are looking at it see. See the screenshot below.

I will link you directly to a post, however, from the dev-blog entitled There be Dragons here in which I look at people's ability to treat their mobile devices like toys, rather than $700+ electronic devices. Any user who wants to be hand-held can do it in another thread. Flashing is as safe as we can make it, but I've personally had flashes go bad, and the ability to recover the device means following instructions. If anyone cannot figure out how to download the ROM, especially given the screenshot below, again, I'd rather not have them flash it.

I understand your point and agree that too many users do not sufficiently educate themselves prior to flashing.

Like a safestrap user who recently twice soft bricked his phone by flashing a gpe ROM. First in a slot, and then when told that he needed a custom recovery flashed it on the stock unsafe side.

However, a DL link in the OP just makes it more convenient for users. Just my opinion.

 

[zekesamas]

Eazy enough to find for me [emoji102] thanks gonna give it a shot soon as my backup is complete. My current ? is running fine but has awful battery life so I'm hoping that this one is better.

 

[cjkacz]

We've created a poll in our Gplus Community concerning our next release. We'd like your thoughts and would appreciate your feedback! Thanks

https://plus.google.com/+DonaldHoskins/posts/PAmttsqceN1

Sent from my Shamu using XDA Free mobile app


Sent from my AOSP on Shamu using XDA Free mobile app

 

[cjkacz]

New 5.1.1 build is up on website! Op updated

www.teamoctos.com

Sent from my Nexus 6 using XDA Free mobile app

 

[Otakulad]

Hi,

Thanks for working to update the S4 to 5.1.1.

I have a question to those out there currently using this ROM. I was running Danvdh GPE ROM and I could not get Netflix to work on mobile data. When I was on my home's wireless, it worked no problem. I then changed my ROM to Hyperdrive (4.4.2) and it started to work on mobile data again.

Has anyone tried to use Netflix on mobile data with this ROM? I'm curious if it is an issue with Netflix and Lollipop not liking each other, if it is something with my phone, or potentially something with the GPE ROM.

Thanks in advance and thank you again for all of your hard work.

 

[focus242]

No BT issues so far

 

[ktraub]

BT LE (Smartwatch e.g. Moto 360) issues remain

No BT issues so far

Looks like the Bluetooth LE issues are still there as it won't see my Moto 360.

 

[cjkacz]

Looks like the Bluetooth LE issues are still there as it won't see my Moto 360.[/QUOTE

The moto 360 has always been weird as far as Bluetooth pairing. Especially when switching Roms. Once paired , it is difficult to pair to another ROM. The only way I found that works is to reset watch and I have even had to uninstall and reinstall android wear. This happened to me on various Roms and ROM versions. I think its more of a moto 360 thing than a ROM issue

Sent from my Nexus 6 using XDA Free mobile app