Team OctOs Oct-MM

[bthorne79]

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

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 T-Mobile Samsung Galaxy S 4

Contributors
bthorne79, 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: Latest Twrp, Latest Radios
Based On: CyanogenMod 13.0

Version Information
Status: Stable

Created 2016-01-17
Last Updated 2016-01-17

 

[Technojo]

Anyone tried this one yet? Feedback would be nice

 

[razpuli]

Ready to try your version of Marshmallow, but before I do, I want to know if it supports native T-Mobile Wi-Fi calling (which supposed to be embedded in Marshmallow now)? Please let me know. I appreciate your response. Thank you.

 

[nowseewhatudid]

I've been using all day and the only thing i can say wrong i have found is that when i first started the rom it told me my sim was inserted and i needed to reboot but everything seems fine since and im loving the rom THANKS

 

[supazonique]

......

 

[a103]

Ready to try your version of Marshmallow, but before I do, I want to know if it supports native T-Mobile Wi-Fi calling (which supposed to be embedded in Marshmallow now)? Please let me know. I appreciate your response. Thank you.

No it doesn't.

Sent from my GT-I9505 using Tapatalk

 

[stanwebber]

i've been setting up this ROM and i can report 2 problems so far:

problem #1: system UI crashes when pressing the + symbol while editing tiles in the quick settings menu. this effectively prevents any tiles from being (re)added. on a related note the 'reset to default layout' option under 'edit tiles' does nothing and the system UI tuner isn't accessible after holding the settings icon. none of this is a big issue for me.

problem #2: home screen grid size is locked to 4 icons per row no matter how low the lcd density is set. this is a deal breaker for me... i've tried both launcher3 and google now launchers and the grid size is stuck at 4 and i can't find any settings to alter it. i don't understand what's going on here as lcd density adjustment is built into the ROM and works just fine to all outward appearances. i'm looking into a manual workaround now, but i may have to drop this ROM if i come up empty. i'm loathe to use nova or any other launcher just for this functionality.

 

[Technojo]

So far, so good. Didn't reinstall all my stuff but I will report back. Really eager to see if bluetooth will work correctly (I have a pebble watch, BT car and speaker) ...

Update: Bluetooth not stable enough

SGH-M919V

 

[stanwebber]

i've been setting up this ROM and i can report 2 problems so far:

problem #1: system UI crashes when pressing the + symbol while editing tiles in the quick settings menu. this effectively prevents any tiles from being (re)added. on a related note the 'reset to default layout' option under 'edit tiles' does nothing and the system UI tuner isn't accessible after holding the settings icon. none of this is a big issue for me.

problem #2: home screen grid size is locked to 4 icons per row no matter how low the lcd density is set. this is a deal breaker for me... i've tried both launcher3 and google now launchers and the grid size is stuck at 4 and i can't find any settings to alter it. i don't understand what's going on here as lcd density adjustment is built into the ROM and works just fine to all outward appearances. i'm looking into a manual workaround now, but i may have to drop this ROM if i come up empty. i'm loathe to use nova or any other launcher just for this functionality.

re: problem #2
ok, dpi adjustment via the ROM is a soft adjustment--the build.prop value still reflects the default dpi of 480. modifying 'ro.sf.lcd_density=380' gets me the 5x5 grid i want so i'm happy.

i can also report that miracast functionality works without issue on my fire tv stick (i'll test my roku stick next).

my demands on bluetooth aren't that extensive, but transferring files and tethering seem to work well enough.

android pay still incompatible even after totally unrooting the ROM.

 

[stanwebber]

a few more observations on OCT-M-WEEKLY-20160116-1647-jfltetmo build:

i had to manually set some google app permissions in order to display all google now cards: settings/apps/gear icon/app permissions

lockclock weather widget fails to access location services to display local (geolocated) conditions. i verified cLock system app has location permissions under settings. for now i have the weather widget manually set to my zipcode.

after patching with OCT-M-WEEKLY-20160123-0421-jfltetmo i can get a little further when adding tiles to the quick settings menu, but system UI still crashes...progress

 

[stanwebber]

i tracked down the source of the crashes when adding tiles to the quick settings menu. whatever item is below 'screen timeout' in the list causes the system UI to crash when scrolling down to (attempt to) view it. Also, when i keep on adding tiles so that the problematic item would show up next in the initial (visible) list of tiles presented... at that point pressing the + button crashes the system UI immediately. when i remove a tile, thereby adding it back to the visible list, then i can press the + button and get the list again without crashing. of course when i scroll past 'screen timeout' the system ui then crashes immediately, as before.

now running the OCT-M-WEEKLY-20160130-0511-jfltetmo build without anything new to report

 

[AeonRelic]

I'm not able to backup anything on external sd card with Titanium Backup on this rom, is there something I'm missing about permissions? Seems like file manager and quickpic also have this problem.

 

[stanwebber]

I'm not able to backup anything on external sd card with Titanium Backup on this rom, is there something I'm missing about permissions? Seems like file manager and quickpic also have this problem.

app permissions are now very granular with marshmallow. some of my apps request missing permissions and some just assume they have them so i've had to manually set permissions for a number of apps. just tonight i had to grant hangouts permissions to use the microphone to place a call.

settings/apps/gear icon/app permissions

now running the OCT-M-WEEKLY-20160206-0542-jfltetmo build without anything new to report--nothing fixed, nothing broken

 

[AeonRelic]

app permissions are now very granular with marshmallow. some of my apps request missing permissions and some just assume they have them so i've had to manually set permissions for a number of apps. just tonight i had to grant hangouts permissions to use the microphone to place a call.

settings/apps/gear icon/app permissions

now running the OCT-M-WEEKLY-20160206-0542-jfltetmo build without anything new to report--nothing fixed, nothing broken

Oddly, this is happening even with storage permissions on. My only fix for the titanium Backup issue was to make a com.kerimidas.TitaniumBackup folder in the external, from a computer (as I couldn't make folders with any file manager I tried). It seems permission related, but turning them on doesn't fix this for me.

 

[stanwebber]

i've installed EVERY single weekly build (plus current pico gapps) as they've been released and this is still my daily ROM. nothing new has been broken and the 'edit tiles' crash on the quick settings menu was finally fixed in the last few releases. several other very minor annoyances have been addressed over time...the only glitch that i can still identify is a problem with the cLock weather widget updates, but this has been a work in progress in the last several releases switching from yahoo weather over to open weather map.

I am a heavy multi-tasking phone user. i think the most recent weekly builds qualify for stable release status.

---------- Post added at 09:42 AM ---------- Previous post was at 09:21 AM ----------

Oddly, this is happening even with storage permissions on. My only fix for the titanium Backup issue was to make a com.kerimidas.TitaniumBackup folder in the external, from a computer (as I couldn't make folders with any file manager I tried). It seems permission related, but turning them on doesn't fix this for me.

i ran into this problem as well with the loaderdroid download manager. i was able to grant app permissions to the built-in sd card memory, but not the external card. apparently, this problem (or feature) was introduced back in kitkat and was addressed with the sdfix app. the app no longer works in marshmallow and has yet to be updated. you can try manually editing the /system/etc/permissions/platform.xml file if it still exists, but i'm content to wait for the sdfix app to be updated or superseded.

 

[christoophat]

Installed latest nightly + A-Gapps, so far very impressed with this ROM. Love having a bare-bones AOSP ROM to add just what I need.
Update: BT streaming to the car works well, though noticed phone getting quite hot after a bit.

 

[christoophat]

After going to Recovery, and doing a dalvik/cache wipe , seems that temps w/ BT have settled down remarkably.

 

[stanwebber]

cLock widget weather updates working again as of OCT-M-WEEKLY-20160521-0142-jfltetmo build.

 

[Robert417919]

So I have been running this ROM for about a week and its a pretty great and stable ROM. The Tentacles extra allow some nice customization.

I have only one crash that I know of, and that was yesterday. I think it was just pure overload. I had Bluetooth running playing music, while I was using Runtascit and GPS was locked as well, then I got a phone call, all while on a low battery. But once it booted back up it was fine. Don't know who called though. Haha. & I found out that the LG Tone 730's you cant change the song via the head set.

Also I found that the speakerphone stops once you back out of the phone app back to the main launcher, but the icon is still in the notification bar. You have to turn it off and back on to get it to work again. - EDIT: This seems to have been an issues with the Google Now Launcher. I switched to Apex Launcher and it is working fine now.

Another thing I noticed but forgot to mention is that it only seems to slow charge (it says it and compared to my ATT S4 on 4.4.2).

 

[christoophat]

So I have been running this ROM for about a week and its a pretty great and stable ROM. The Tentacles extra allow some nice customization.

I have only one crash that I know of, and that was yesterday. I think it was just pure overload. I had Bluetooth running playing music, while I was using Runtascit and GPS was locked as well, then I got a phone call, all while on a low battery. But once it booted back up it was fine. Don't know who called though. Haha. & I found out that the LG Tone 730's you cant change the song via the head set.

Also I found that the speakerphone stops once you back out of the phone app back to the main launcher, but the icon is still in the notification bar. You have to turn it off and back on to get it to work again.

Another thing I noticed but forgot to mention is that it only seems to slow charge (it says it and compared to my ATT S4 on 4.4.2).

In spite of the onscreen message, it charges at the normal rate. Supposedly, the S4 doesn't support the fast charge feature, though some claim it can be enabled at the kernel level, if the kernel has it baked in.