{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quote:
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.
Click to expand...
Click to collapse
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. -
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-M based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12 code. Oct-M is based on CyanogenMod 13.
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-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 favourite Android 6 based 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 CyanogenMod 13.0 kernel.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://review.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
Quote:
Special thanks to
arco68 for which this serrano variant would not be possible.
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
CyanogenMod
OmniROM
LiquidSmooth
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Us at the various websites below!
XDA:DevDB Information
OCT-M, ROM for the Samsung Galaxy S4 Mini
Contributors
jason972000, cjkacz, manfromgta, (Testers) Krik88, shadyasker
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Current Stable Version: OCT-M-R2-6.0.1
Stable Release Date: 2016-08-20
Created 2016-08-20
Last Updated 2017-03-17
The first weekly for GT-I9190 (serrano3gxx) can be found at https://www.teamoctos.com/weekly-builds/
Or at the basketbuild mirror found in that page.
So... Its been awhile. Our final Marshmallow release build is now available on our website!
OCT-M R3 final release https://www.teamoctos.com/release-builds/
Going forward we'll be working on Oct-N. I know a lot of you are still on M & curious about N & when your device will see it.With Oct-N we've moved back to an AOSP base. We're working on getting an AOSP-CAF branch so that we can bring our legacy devices up to N. This will take some time & some devices may not make the cut. We appreciate your patience as we work on bringing Oct-N to as many legacy devices as possible. Thank you all for your support, Stay tuned! ??
New Xda Thread for OCT-N
We have decided to try something different for OCT-N and combine each S4 Mini supported into one Xda Thread.
We are hoping it will be easier to follow rather than needing to view separate threads for each variant.
It should also help prevent users from posting in the wrong thread for their device.
Please make sure you mention which variant you have if you post in the new thread.
Here is the new thread: https://forum.xda-developers.com/gal...octos-t3567800
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Click to expand...
Click to collapse
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:
Download ROM .zip file and MD5 file, and grab your favourite Android 5 based 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-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
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
CyanogenMod
OmniROM
LiquidSmooth
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Us at the various websites below!
XDA:DevDB Information
Oct-L, ROM for the Nexus 7
Contributors
cjkacz, Grommish, hedwig34, bthorne79
Source Code: http://www.github.com/Team-OctOs
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 12
Version Information
Status: Testing
Created 2015-02-19
Last Updated 2015-02-19
Wrong thread... Post in android development Thanks.
Why you no report thread to be moved? Instead of creating a duplicate here? :silly:
http://forum.xda-developers.com/showthread.php?t=3035425
Thread closed. :good:
Thanks,
Darth
Forum Moderator
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.1.1
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:
Download ROM .zip file and MD5 file, and grab your favouriteAndroid 5.1.1 based GAppspackage
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-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.
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!
DOWNLOADS:
OCT-L-COMMUNITY-tomato
YU GApps Latest
YOU MUST USE THE GAPPS LINKED IN THE THREAD
XDA:DevDB Information
OctOS, ROM for the YU Yureka
Contributors
vibhu0009
Source Code: https://github.com/Cyanogenmod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked bootloader
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-08-08
Last Updated 2015-08-07
Screenshots:
downloading now..
I am downloading now...
vayank said:
I am downloading now...
Click to expand...
Click to collapse
Post ur review here after using it
+1
sent from my yureka
Great Rom brother
I'm using your Rom but have one problem it get heating my yureka cpu. And when we play games on it. My phone get xterm heated and when I attached charger it get xtremly heated please please fix
Javed ali said:
I'm using your Rom but have one problem it get heating my yureka cpu. And when we play games on it. My phone get xterm heated and when I attached charger it get xtremly heated please please fix
Click to expand...
Click to collapse
use custom kernels
not better than blisspop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quote:
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.
Click to expand...
Click to collapse
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. -
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-M based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12 code. Oct-M is based on CyanogenMod 13.
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-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 favourite Android 6 based 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-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-M available on our GitHub repositories.
Unless otherwise specified, all Oct-M builds use the device's stock CyanogenMod 13.0 kernel.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://review.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
Quote:
Special thanks to
arco68 for which this serrano variant would not be possible.
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
CyanogenMod
OmniROM
LiquidSmooth
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Us at the various websites below!
XDA:DevDB Information
OCT-M, ROM for the Samsung Galaxy S4 Mini
Contributors
jason972000, Grommish, manfromgta, (Testers) Jordan, Richard, Team OctOs
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: R890TYUBNE4 or R890TYUBNK1
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Current Stable Version: OCT-M-R2-6.0.1-20160
Stable Release Date: 2016-08-11
Created 2015-08-25
Last Updated 2017-03-17
Thanks , man !
One thing : is it only for SERRANOLTEUSC ?
Yes, I only have the serranolteusc so no other US Cellular version.
Sent from my SCH-R890 using XDA Free mobile app
Announcing weekly OctOs builds
Good news! We've decided to start doing weekly builds, you can find them here, https://www.teamoctos.com/weekly-builds/ we will still have our monthly milestones. Weeklies will be done every Friday night & at the latest should be up by Saturday!
Or grab the official milestone M4 release from here https://www.teamoctos.com/supported-devices/samsung/samsung-galaxy-s4-mini/uscc-galaxy-s4-mini-serranolteusc/
Hey guys & gals, we had to pull all of today's weekly builds due to a few issues. We're working on it & should have new builds up by 2moro if everything goes right. Sorry for any inconveniences guys. I'll post when new builds hit the site.
Thanks, Team OctOS ?
Sent from my SAMSUNG-SGH-I747
New builds are back up now, ENJOY! ?
New weeklies up on site!
No weekly this week. Instead We're gearing up for our 5.1.1 milestone (M5) release! LP Weekly builds will continue for all non-Nexus (CAF) devices until each device is brought up to MM. This will take time, which is why we've decided to continue our CM based weeklies for these devices. Going forward with 6.0, we've decided to return to our AOSP roots! We truly value our users & appreciate your patients while we make the transition. Thanks for all the support! Good things to come ? I'll update you guys when the builds go live!
M5 is up ENJOY! ?
New weekly is up, go get it! ENJOY! ?
11-14 weekly build up on site!
Weeklies up! go get em! https://www.teamoctos.com/weekly-builds/
Is the I9515 S4 mini supported?
liddodragon said:
Is the I9515 S4 mini supported?
Click to expand...
Click to collapse
Search for Serrano LTE EU. EU means Europe and you get the answer for your question.
liddodragon, looks like the I9515 is the value edition. I do see that there is another xda thread for that device that is cm based. OctOs 5.1 is cm based so it most likely can be build for OctOs too. The problem is that you need a dev with that phone to get it going.
Hi everyone! Hope all is well. I wanted to let you know that there will be no weekly builds this Friday/Saturday due to the Christmas Holiday. We at Team OctOs would like to wish you and your families a Merry Christmas and happy holiday season! We look forward to picking up again next week and may even have a couple surprises for you! Peace! And thanks for understanding.
There hasn't been much feedback on anyone who has tried out this rom for the SCH-R890 so here is something to ponder...
I have been trying to figure out how to eliminate an echo that callers hear when you are on a voice call (no one else has reported this issue but I can confirm it happens).
It appears that this issue is related to the libaudcal.so blob used in the rom.
It looks like we can fix the echo issue but then you cannot adjust the voice volume.
Until someone can help figure out what the issue is, what is the better setup, no echo for caller or ability to adjust to voice volume?
I think that fixing the echo is more important myself.
We should be able to change the fixed volume level and if we find it is needed and you can also just activate the speaker when on a call, if you need the voice volume louder.
Any votes?
OK guys & gals, our final LP release (Oct-L M6 Final) is live on site! Enjoy, Oct-M will be here soon! ?
I noticed that the new TWRP 3.0.0 was missing an Odin-able .tar file. Dees_Troy has build #7 going now to create it.
I did have issues flashing the .img file with the "dd" command and via TWRP 2.8.7.0 itself (it would boot into Download mode indicating that recovery was not bootable). But, I found that the TWRP Manger application installs it to a working recovery (even though it told me it had a problem installing it).
So far I did a backup and restore of an Oct-M build and it works with 3.0. I have not tried installing a fresh rom yet with 3.0.
Please PM me or post a reply here with you experiences.
Edit: The Odinable .tar file is now out on twrp.me.
Edit: Adb is working on the 3.0.0-1 now available on twrp.me.
The first OCT-M weekly build will be done tonight (2/12/16) for the serranolteusc.
Check back on the teamoctos.com website tomorrow morning for it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Click to expand...
Click to collapse
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. -
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-M based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12 code. Oct-M is based on CyanogenMod 13.
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 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 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-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 favourite opegapps package http://opengapps.org
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 CyanogenMod 13 kernel.
Kraken kernel source code can be found here: https://github.com/Oct-mm
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
OpenGapps
CyanogenMod
OmniROM
LiquidSmooth
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Us at the various websites below!
XDA:DevDB Information
Oct-M, ROM for the Moto X 2014
Contributors
canodroid15, Cjkacz, bthorne79, hedwig34
Source Code: http://www.github.com/Team-OctOs
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 13
Version Information
Status: Stable
Current Stable Version: OCT-L-M6
Beta Release Date: 2016-02-26
Created 2016-02-28
Last Updated 2016-08-26
Any screenshots???
I'm pretty sure the era of screenshots is over. Most all ROMs look stock now, and let you theme them how you want. Prior to these theme engines, a lot of developers used to theme ROMs. Now it's being left to us. The real meat and potatoes lies in the code, which screenies won't show. I always scroll through looking for screenshots too, out of habit lol.
leonardoafa said:
Any screenshots???
Click to expand...
Click to collapse
Sent from my Nexus 6 using XDA Free mobile app
I only see moto x ghost link there, not victara?
yip, dont see the download link for our phone, only Moto X (ghost)...
Klick on it, victara is there
uluf said:
Klick on it, victara is there
Click to expand...
Click to collapse
only ones there are for Moto X (ghost) our Moto X is Victara not Ghost...
Jostian said:
only ones there are for Moto X (ghost) our Moto X is Victara not Ghost...
View attachment 3664417
Click to expand...
Click to collapse
Try under weekly builds, I just found it again
https://www.teamoctos.com/weekly-builds/
uluf said:
Try under weekly builds, I just found it again
https://www.teamoctos.com/weekly-builds/
Click to expand...
Click to collapse
thanks, appreciated!
Hey guys, hope you enjoy the ROM! Any & all feedback is welcomed here, thank you for checking us out! ?
Its simple
Hey guys i like the performance, but theres no resize navigation bar? Why
luisgamma13 said:
Hey guys i like the performance, but theres no resize navigation bar? Why
Click to expand...
Click to collapse
We're looking into adding resizable nav bar in future builds! ?
I would love to see double tap to sleep on lockscreen, its the only thing missing in this rom. Everything else runs super smooth, i really like it!
Daily driver material. Got great battery life results in the first run, can't imagine how it's going to be after the battery settles...
No bugs found, at least for the kind of usage I give it.
No bugs found for me, and greater battery life. Works fine. Thanks
Waiting for more updates
Great rom! Really like the balance of stock and additional features. It absolutely flies and battery life in the time I used it has been excellent.
Great rom. I haven't tested the battery life, but it seems good. Work perfectly as well.
The only thing which is bad, like CM13 and CyanPop, (also based on CM13 sources) the sound is distorted on some games ( like Critical Ops, the game is free on PlayStore if you want to see the problem ). It need a fix.
Temple Run 2, Crossy road got also distorted sound..... Boring
I think I'll back to stock because I use this phone for playing 1rst.
Great ROM!!!
I have to ask though.. is the stock Moto X features found on 5.0~ (Active Display) not compatible on 6.0+?
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. -[/CENTER]
FEATURES
Android 6.0.1
Optimized for the best efficiency (battery and performance)
Smooth as hell!!
Live Display
Ambient 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!
(Believe me, despite all these features, the rom is still really buttery )
FAQ
Frequently Asked Questions
Q: Is this Android 6 (Marshmallow)?
A: Yes, this is Android 6.0.1
Q: What code is Oct-M based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12 code. Oct-M is based on CyanogenMod 13.
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 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 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-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 favourite opengapps package http://opengapps.org
Reboot to Recovery
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
Wipe system, cache, dalvik, and data
Flash ROM and GApps .ZIP files
Reboot
DOWNLOADS
MODERATOR EDIT - Link Removed
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.
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
[ROM][F2FS]Oct M by Team-OctOS [COMMUNITY BUILDS] [6.0.1_r52] [Offline Gestures], ROM for the YU Yureka
Contributors
darshan1205
Source Code: https://github.com/Team-OctOS
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: OCT-M-COMMUNITY-2016
Stable Release Date: 2016-05-26
Created 2016-06-28
Last Updated 2016-07-17
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks @SK83 for server
hi nice rom, really smooth.
but i m facing this one problem and it is that the file manager is not being granted root permissions even though i am using latest supersu.
any suggestions?
Can i dirty flash the new built plz reply
Thanks in advance.
Thread Closed until further notice.