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. -
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
FEATURES
- Android 6.0.1
- Optimized for the best efficiency (battery and performance)
- Smooth as hell!!
- Live Display
- Separate customization menu, which can be hidden
- Omniswitch
- Clear-all recents
- Immersive recents
- Status bar clock/date customization (format, colour, etc)
- Battery icon customization
- Status Bar Header Image
- QS Tiles customization
- App Circle Bar
- Buttons customization
- Volume Steps
- Gesture Anywhere
- Kernel Adiutor
- Lock Screen customization
- Toast Icon
- Power menu customization
- SuperSU
- Privacy Guard
- Status Bar Greeting
- Battery Bar
- Traffic Indicator
- Theme Engine
- More to come!
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.
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:
- Download ROM .zip file and grab your GApps package (Nano or Pico)
- 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)
- Wipe /data, /cache, /system and Dalvik-Cache
- Flash ROM and GApps files
- Reboot
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!
Source Code: http://www.github.com/Team-OctOs
XDA:DevDB Information
Oct-OS, ROM for the Sony Xperia L
Contributors
Agent_fabulous, Lorenz15
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-05-19
Last Updated 2016-09-11
Attachments
-
66.5 KB Views: 3,949
-
191.6 KB Views: 4,081
-
60.7 KB Views: 4,039
-
37.7 KB Views: 4,097
-
40.8 KB Views: 3,999
-
41.6 KB Views: 3,903
-
54.4 KB Views: 3,849
Last edited: