[ROM][nicki][5.1.1_r9] Team OctOS Oct-L - Sony Xperia M

{
"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-20150807-1840-nicki
GApps
YOU MUST USE THE GAPPS LINKED IN THE THREAD
XDA:DevDB Information
OctOS, ROM for the Sony Xperia M
Contributors
vibhu0009
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-08-08
Last Updated 2015-08-08

Screenshots

You're great! Can I ask about features? I was looking in Google and official site but can't find anything. Maybe I'm just bad in searching for information.

Farron said:
You're great! Can I ask about features? I was looking in Google and official site but can't find anything. Maybe I'm just bad in searching for information.
Click to expand...
Click to collapse
u r on fire dude.. Good job.. Thanks for bringing so many official builds for Nicki

Farron said:
You're great! Can I ask about features? I was looking in Google and official site but can't find anything. Maybe I'm just bad in searching for information.
Click to expand...
Click to collapse
yeah.. i havent mentioned its features but u can always check out screenshots to know the features

kjinx01 said:
u r on fire dude.. Good job.. Thanks for bringing so many official builds for Nicki
Click to expand...
Click to collapse
just post ur review here so it will help me getting u more n more stable ROM

hi
thanks for your great work but i really don't understand: isn't it better to focus on one rom and make it the best??

ghasemi.hussein said:
hi
thanks for your great work but i really don't understand: isn't it better to focus on one rom and make it the best??
Click to expand...
Click to collapse
Not an issue I can maintain all of them together

Does this ROM support the C2005 Nicki Dual Sim model?
Since the name of this rom is [ROM][nicki][5.1.1_r9] Team OctOS Oct-L. The model used in the screenshots however, is the 1905 single sim.

Please Hit THANKS if I helped.
neelz said:
Does this ROM support the C2005 Nicki Dual Sim model?
Since the name of this rom is [ROM][nicki][5.1.1_r9] Team OctOS Oct-L. The model used in the screenshots however, is the 1905 single sim.
Click to expand...
Click to collapse
Please Hit THANKS if I helped.
I think no, it doesn't support dual sim version.
But you can use this ROM on dual sim device by flashing the stock 4.3 single sim rom and then flashing this rom.
Please Hit THANKS if I helped.

Related

[ROM][Android 6.0.1]Team OctOs OCT-M

{
"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 CyanogenMod 12.1 code. Oct-M is based on CyanogenMod 13 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 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 opengapps 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.
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-M, ROM for the Samsung Galaxy S4
Contributors
Grommish, canodroid15, 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-M R2
Created 2015-02-17
Last Updated 2016-08-26
F*ck yeah!!
Me Gusta!
Running like a dream!
Me Gusta!
Thanks, features & screenshots please!
Nice ROM
Hey, mind posting some screenshots? Oh and, is in this rom fixed the issue with "mobile radio active"? When apps like Chrome would keep mobile radio active for hours and hours if you dont force close them.
Will f2fs on cache and data work AS it does on stock cm12
compiled with sabermod?
george_shudi said:
Thanks, features & screenshots please!
Click to expand...
Click to collapse
niicoland said:
Hey, mind posting some screenshots? Oh and, is in this rom fixed the issue with "mobile radio active"? When apps like Chrome would keep mobile radio active for hours and hours if you dont force close them.
Click to expand...
Click to collapse
Screenshots are located in the Screenshot area. If your using the XDA Mobile App, you may want to request they update it. For now, you can try this link: http://forum.xda-developers.com/devdb/project/?id=8277#screenshots
As for batt life and mobile radio, You'd have to ask @Me Gusta, as he is one of the primary testers., but I've not seen it on my jfltespr build (I'm Sprint)
nadejo said:
Will f2fs on cache and data work AS it does on stock cm12
Click to expand...
Click to collapse
We use the CM12 device repositories, and then alter them after the fact. Anything in there will still apply.
fedef12evo said:
compiled with sabermod?
Click to expand...
Click to collapse
No. SaberMOD is now closed source, and the prebuilt toolchain causes issues with missing A5 libraries (libatomic.a in particular). While we still have the ability to build our own toolchain from SaberMod (grandfathered), we would be unable to post it or have others who wish to build Oct-L locally use it. Because of this, we have dropped plans on using SaberMOD's toolchains.
Just throwing this out there!
Oh, and battery life is good! I get through a day with ease and 3 hrs of screen on time.
Me Gusta!
Thank you for this but is it just me that cant find the download link?
http://www.teamoctos.com all downloads can be found here
Me Gusta!
inso420 said:
Thank you for this but is it just me that cant find the download link?
Click to expand...
Click to collapse
At the very top of the OP..
"We maintain a current release record and change-log on our website: http://www.teamoctos.com"
Just downloaded, Havent flashed yet but look like a nice clean stable rom. cant wait to reflash!
Battery Life ?
How's The Battery Life? Better Than CM ? =S I really have a problem with Battery Life On Any Android Lollipop Rom
I'm on day 1 of running the ROM...good and stable so far with good battery life...takes a day or 2 to really see what the battery life will be...give it a flash and let it settle in...you should be happy with battery life
Great rom guys keep it up!
This rom is awesome! It's very stable and fast!
The only thing that is annoying is the battery drain, but I love this rom
The battery does seem to drain really fast, but its being worked on ad far ad I know
Testing
Albeit a work in progress, after playing with this rom I can agree with the disclaimer is suitable for daily use. Cleared all data on my phone, began with a clean slate and used PA minimal gapps and it works fine. Altered the dsp from AudioFx to LolliViper and so far it's very good. Keep up the good work, being a Resurrection Remix addict this rom opens me up for something different.
Its a damn fine ROM...only issue I have is battery...but that's being looked in to

[ROM][5.1.1][FINAL][OPTIMISED][UNOFFICAL] Oct OS L [R6,2015-12-16]

{
"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​
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.
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 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
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
armani-dev for being open source.
Device specific sources - Device
Kernel
Vendor
XDA:DevDB Information
Oct OS L, ROM for the Xiaomi Redmi 1S
Contributors
aniket.lamba
Source Code: https://github.com/Team-OctOS
ROM OS Version: 5.1.x Lollipop
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: CyanogenMod
Version Information
Status: Stable
Current Stable Version: R6
Stable Release Date: 2015-12-16
Created 2015-05-28
Last Updated 2015-12-16
Reserved
Reserved
Downloads -
ROM - Oct OS L R6
GAPPS - http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
Changelogs - https://www.teamoctos.com/category/changelog/
First
Downloading
Thanks
pls share the screen shot...
sp1312 said:
pls share the screen shot...
Click to expand...
Click to collapse
See the screenshots tab.
Another gr8, downloading
Update - Oct OS L (15th June,2015)
Changelog - Updated the base to 5.1.1_r4
- Updated the base to CM12.1 R10 by armani-dev
- APN settings optimised
- Other minor fixes
Happy Flashing!
Nice Rom
Nice Rom it has all features i want but there is no network speed indicator.
Great rom. very stable and good battery backup. Xposed works fine. Thanks. keep it updated. Using it from four daays, tried many roms but finally settled with this.
New build - Oct OS L R3
And the changelog please..
Screens bro??
Sent from my HM 1S
BATVIC said:
Screens bro??
Sent from my HM 1S
Click to expand...
Click to collapse
Here - http://forum.xda-developers.com/devdb/project/?id=10029#screenshots
Rom pretty good, no problems with the play of music and open gallery which can not be read sd card
I have encountered many such things in some rom including Cyanide L
thanks
Hi devs, can add the facility to change the size of fonts and change the background in the message as in cyanide rom?
thanks
Update - Oct OS LR4
@aniket.lamba
Bro,i hided the tentacles from the notification drawer and the app drawer..
I want to go there..
Any one how to go??
Sent from my HM 1SW
BATVIC said:
@aniket.lamba
Bro,i hided the tentacles from the notification drawer and the app drawer..
I want to go there..
Any one how to go??
Sent from my HM 1SW
Click to expand...
Click to collapse
Nah,you've to unhide the app and then access it.

[ROM] [LP-5.1.1]Oct Os L[TITAN] [UNOFFICIAL][20150609]

{
"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.
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.1 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.
Download:
Team OctOs GitHub
Rom on Basketbuild
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Quote:
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
CyanogenMod
Marvin: For providing us his Server
Motorola: For making this awesome phone
notiflux
OmniROM
LiquidSmooth
motog2014devteam
Anyone else who has ever submitted Open-Source code
Follow Us at the various websites below!
XDA:DevDB Information
Oct OS L, ROM for the Moto G 2014
Contributors
Sarath280, notiflux
ROM OS Version: 5.1.x Lollipop
Based On: Oct Os L
Version Information
Status: Testing
Created 2015-06-09
Last Updated 2015-06-09
reserved
Reserved
What about features?
Sent from my Moto G 2014 using XDA Forums PRO
what?
Can't download...
Enviado do meu Moto G 2014 através de Tapatalk
djekan said:
Can't download...
Enviado do meu Moto G 2014 através de Tapatalk
Click to expand...
Click to collapse
I had this issue using Tapatalk also. Try to open this XDA thread directly in a web browser (like chrome) in your mobile and then open the link from there.
I don't know why, but when being directed by Tapatalk these links are not opening normally.
Downloading....will try later....can i flash bank gapps5.1 signed package???
---------- Post added at 11:37 AM ---------- Previous post was at 11:24 AM ----------
Downloading....will try later....can i flash bank gapps5.1 signed package???
Nice ROM. Love the idea of making an additional app for features i.e. tentacles.
Any hope for further development.....very "COOL" ROM
Great ROM! Been using it as my daily driver for almost 2 months! No lagging between animations, no redraws, and gets EVEN BETTER using Optimus Kernel. You guys should certainly try OctOS.
Ps: @Sarath280 could you please update this ROM? Perhaps OctOS team already included some newer features and stuff xD
Awsum ...just awsum in one word....back from app drawer to home page is just juicy..the animation is too smooth even in .75x speed
Hats of bro @Sarath280
@Sarath280
can u pls add network indicators arrow in status bar, battery charging animation in text mode(in status bar and header also)
BTW GREAT WORK

Team OctOs Oct-MM

{
"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-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:
Download ROM .zip file and MD5 file, and grab your favorite Android 6 based GApps[/URL] 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
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
Click to expand...
Click to collapse
Follow Us at the various websites below!
XDA:DevDB Information
Oct-MM, ROM for the 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
Soon as I get home I'm flashing this. I'm also the first ^=^.
Sent from my GT-I9505 using Tapatalk
jamboss said:
Soon as I get home I'm flashing this. I'm also the first ^=^.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
LOL !
It's running great... Data, call....
There were three threads, now two for this rom...i'm a bit lost where to post?
I flashed the latest nightly and wow its smooth as hell lol. Excellent.
Sent from my GT-I9505 using Tapatalk
Screenshots please !!

Team OctOs Oct-MM

{
"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-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:
Download ROM .zip file and MD5 file, and grab your favorite Android 6 based GApps[/URL] 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
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
Click to expand...
Click to collapse
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
Lovely
Sent from my SGH-M919 using Tapatalk
Having trouble finding/downloading this ROM. Is the ROM available for the M919 or no?

Categories

Resources