Develop Bugs

[ROM][D851][LMY47V][5.1.1] Team OctOS Oct-L - T-Mobile LG G3

{
"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.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 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!
Above is our hidden menu. It can be accessed 3 different ways: "Tentacles" in app drawer, quick settings tile, or by pressing settings/about phone/OctOS build date.
MORE PICS OF OUR FEATURES: https://copy.com/9V9skpmRVsRaa6mx
Click to expand...
Click to collapse
XDA:DevDB Information
Oct-L, ROM for the T-Mobile LG G3
Contributors
red3razor, cjkacz, bthorne79, canodroid15
Source Code: http://www.github.com/Team-OctOs
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 12
Version Information
Status: Testing
Created 2015-05-06
Last Updated 2016-01-17

Changelog here: http://www.teamoctos.com/category/changelog/

seeing this
"Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically."
is there an actual benefit to using the other to using Superuser or not ? dont they accomplish the same thing in the end ?

thelgog said:
seeing this
"Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically."
is there an actual benefit to using the other to using Superuser or not ? dont they accomplish the same thing in the end ?
Click to expand...
Click to collapse
Some think that is more stable, less hiccups. Just a preference.

pics (of features) added

need more servers...
Taking a solid 30-40 minutes to download and I have 60mb Speed here I'm Silicon Valley...
Will post screenshots and report back in a bit

First (Rough) impression off the bat
Took about 35 minutes to download ROM from http://www.teamoctos.com
Once I got into TWRP the flash took between 10-15 minutes.... I went ahead and flashed the same 5.1.X gapps i use on Res and Bliss......
Once I got to setup is where I ran into my first IN rom issue.. I BELIEVE the initial APN is messed up because I got the screen (in the attachment), so essentially all i could do was set up my "device" with my first and last name.
After i changed APNs It allowed me to sign into google and everything seems good from there..
Attaching variety of screenshots below ​

Attaching variety of screenshots below ​[/QUOTE]

Been using OctOS for awhile now. Glad to see a thread here for it.
First experience wasn't so great. CPU usage was always high and things lagged terribly. Wasn't sure what was going on.
About week or so later I clean flashed again with a newer gapps. Runs pretty well so far but not so snappy. Nice none-the-less.
Sent from my LG-D851 using Tapatalk

yanowman said:
Attaching variety of screenshots below ​
Click to expand...
Click to collapse
[/QUOTE]
Strange, regarding the download time. Yes the boot time started as a long endeavor on 5.1.x. I can say from experience, the newer test builds have improved a ton with twrp flash speed. Coming soon! As for the other items, I'll ask our T-Mobile testers. Thanks for giving us a try!

marcdw said:
Been using OctOS for awhile now. Glad to see a thread here for it.
First experience wasn't so great. CPU usage was always high and things lagged terribly. Wasn't sure what was going on.
About week or so later I clean flashed again with a newer gapps. Runs pretty well so far but not so snappy. Nice none-the-less.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Thanks!

Removed dead end PA gapps link. Added BaNkS gapps.

are you guys providing anymore support for the ROM, i see the only build for it is from a couple weeks ago for the d851 (4/23/15). i like to see new builds every now and then and flash and test

techfreak243 said:
are you guys providing anymore support for the ROM, i see the only build for it is from a couple weeks ago for the d851 (4/23/15). i like to see new builds every now and then and flash and test
Click to expand...
Click to collapse
Yes we are. Testing is very active behind the scenes. Features + stability is being worked on. We do apologize for the wait. I plan to ask some of my team members today if we can release to our website soon. (All of our g3 builds are back a couple weeks atm)

www.teamoctos.com updated with new builds. Changelog here: http://www.teamoctos.com/category/changelog/
Most notably, data handoff between WiFi/3g/lte much improved.

Milestone 3 release, and here is the changelog: https://www.teamoctos.com/category/changelog/
Downloads also on our website under "Devices Supported." Enjoy! Thanks for looking!

I know this has been asked in a few ROM threads but... do you have wifi calling in this ROM..? I'm looking for a new ROM to come to with decent battery life and performance. I'm on Skydragon at the moment.
Also, can we play with voltages/clockspeeds with your kernel?

maddangerous said:
I know this has been asked in a few ROM threads but... do you have wifi calling in this ROM..? I'm looking for a new ROM to come to with decent battery life and performance. I'm on Skydragon at the moment.
Also, can we play with voltages/clockspeeds with your kernel?
Click to expand...
Click to collapse
Practically not possible to find "working" WiFi Calling in an AOSP/CM based ROM.
Only Stock TMO LG based ROMs can contain the required files- at the moment.

graphreak said:
Practically not possible to find "working" WiFi Calling in an AOSP/CM based ROM.
Only Stock TMO LG based ROMs can contain the required files- at the moment.
Click to expand...
Click to collapse
Ah ok. That is what I've seen so far, but I didn't see anything about not having it here. Thanks

New builds up at https://www.teamoctos.com/supported-devices/lg/lg-g3/

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-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 base 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 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.
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 T-Mobile Samsung Galaxy S III
Contributors
bthorne79, CjKacz, canodroid15, 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

Reserved
Known Issues
A full list of Known Issues resides on our website. *In order to avoid confusion for people who skimmed the OP,
NONE REPORTED FROM TESTERS

Thanks OP
downloading now..
:good:

bthorne79 said:
Known Issues
A full list of Known Issues resides on our website. *In order to avoid confusion for people who skimmed the OP, the biggest Known Issue with the Galaxy S3 (d2lte) platform is the Camera. *It could cause Force Close issues. *This is an upstream issue, and we are working to correct it.
Click to expand...
Click to collapse
Please put this info and list other bugs in the OP so that people won't be misled. Not everyone reads past OP.

goldentequila said:
Please put this info and list other bugs in the OP so that people won't be misled. Not everyone reads past OP.
Click to expand...
Click to collapse
Sorry but the inability to read is the users issue. Half the time they don't even read the OP. Go right to the download link. I posted in the 2nd post and there is a link in op to site with bug list and change log
Sent from my SPH-L720 using XDA Free mobile app

Running nicely right now. Had a hard time getting WiFi to connect on first boot but its working now

We put the information on the website because its easier to keep track of across the multiple devices we develop for. We develop the ROM for the simple fact we want to run it, not for you, or anyone else. The ability to be cognizant on what you're doing is a primary requirement for flashing ROMs, and the inability for you to apparently read and comprehend the very simply formatted OP means you are not willing to rise to the level we seek in a user.
It would be better for everyone involved if you don't flash Oct-L. You have many ROMs to choose from, you shouldn't choose ours.
ROM Development is not a service or product industry. You are neither a customer, or a client. Your demands mean exactly nothing and we have better things to do than hold your hand.
Now, if you feel like running what we build, by all means, do so. However, your continued patronage to the thread is directly proportional to your ability to be civil and not condescending.
Enjoy, or not at your leisure, but unless you have something constructive to say, please wander to another ROM.
Toodles!

Running smooth. ^.^

lol bitter much? Don't ruin this for the rest of us who rely on devs like these guys to continue providing up to date software for our aging phones.
I'm definitely trying this ROM out.

From the Moderator
To all in this thread........
Please all remember, the Devs do this for free and out of their love for developing....
....So being rude and poor mannered...... gets you nothing but maybe one less Dev making Roms for your phone
Keep that in mind when you feel like you have some lame commentary or demand to make...
........To the trolls, rather than complaining...... show us your skills and make a ROM for us to critique.......
........oh yeah...... you have no skills other than running yer mouth and making personal demands in a thread.......
~~~ oka1

The strangest thing is him talking about the OP not listing a Buglist. The Rom that he his visiting the most does not either. With that said I'm done. Mod can in and slammed the hammer down on that issue.
Please any one using this rom if you do see anything and and are able to catch a log please report and send log to us.
Thanks for supporting Team OctOS
Sent from my SM-T217S using XDA Free mobile app

Is the nav bar included in this release? Working?

allendj81 said:
Is the nav bar included in this release? Working?
Click to expand...
Click to collapse
Sure! About the only thing that doesn't work is the camera!?

Installed this Rom and turned on wifi but after login to my account wifi stopped and grayed in off position
Rebooted device and wifi got on but every time failed to login
Again rebooted and it started working correctly
Reached office but again failed to connect to wifi
It is just an information as I read same thing happening with other cm12 build too so this may be with the cm12

anil2653 said:
Installed this Rom and turned on wifi but after login to my account wifi stopped and grayed in off position
Rebooted device and wifi got on but every time failed to login
Again rebooted and it started working correctly
Reached office but again failed to connect to wifi
It is just an information as I read same thing happening with other cm12 build too so this may be with the cm12
Click to expand...
Click to collapse
What firmware is your phone on I've noticed that the newest modems and firmware is needed for lollipop to work correctly. These builds have been in test for quite some time. Our testers have put this build through the ground with not one hick-up just camera which we have been working on getting fixed.
If you can get a log of the WiFi issue you are having we will look at it. My suggestions is to update to the latest modem firmware for d2tmo.
Sent from my SPH-L720 using XDA Free mobile app

allendj81 said:
Is the nav bar included in this release? Working?
Click to expand...
Click to collapse
canodroid15 said:
Sure! About the only thing that doesn't work is the camera!
Click to expand...
Click to collapse
The Navbar will cover the "Clear All Recents" button if you select the lower right or left position. This already has been corrected for the next release.

Thanks a lot for this amazing rom, i´ll install it as soon as it finish downloading, but one question, it´s the same instaling it in cwm? i mean, does it makes a diference like more bugs or things like that, i hope you understand Thanks a lot!

vick007 said:
Thanks a lot for this amazing rom, i´ll install it as soon as it finish downloading, but one question, it´s the same instaling it in cwm? i mean, does it makes a diference like more bugs or things like that, i hope you understand Thanks a lot!
Click to expand...
Click to collapse
Our d2tmo user still uses CWM as the team we suggest TWRP only cause CWM is almost a dead recovery and has been know to cause bad flashes..
Sent from my SPH-L720 using XDA Free mobile app

vick007 said:
Thanks a lot for this amazing rom, i´ll install it as soon as it finish downloading, but one question, it´s the same instaling it in cwm? i mean, does it makes a diference like more bugs or things like that, i hope you understand Thanks a lot!
Click to expand...
Click to collapse
Also, CWM has had historical issues with actually wiping the partitions effectively. The "Wipe system, data, cache, dalvik x3" was a reality in the past because of CWM. Those issues don't happen with TWRP.

I noticed a couple of things:
1) When flashing the ROM it takes a while. Compared to other lollipop rom's, this one takes about 3-4 minutes to flash, while others flash in like 15 seconds. Is that normal?
2) Installing apps from the play store are taking a long long time. Each app takes about 2 minutes to install, longer if it's a bigger one like youtube. I've noticed it takes long across all lollipop rom's, but one this one it seems to be longer.
3) Kernel Tweaker crashes when I try to view read-ahead and IO scheduler. This doesn't happen with any other ROM so I'm thinking there's something going on with oct os.
Any thoughts?

{
"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 /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 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
TeamBlackout
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 AT&T Samsung Galaxy S III
Contributors
bthorne79, CjKacz, canodroid15, hedwig34
Source Code: http://www.github.com/Team-OctOs
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: UCUFNJ2
Based On: CyanogenMod 13
Version Information
Status: Stable
Current Stable Version: OCT-M R2
Created 2015-02-17
Last Updated 2016-08-26

Reserved
Known Issues
A full list of Known Issues resides on our website. *In order to avoid confusion for people who skimmed the OP,
NONE REPORTED BY OUR TESTERS

Dare I say it, FIRST! This ROM rocks! Get it while its hot! @Grommish, @bthorne79 @hedwig34 @cjkacz & the whole team, Thanks guys! Team OctOs FTW!

Battery life
I am getting an hour and 38 minutes left of battery power when on 60%

Just got this all loaded up and everything working awesome! Gotta love those Octos wallpapers and live wallpapers

innocent25 said:
I am getting an hour and 38 minutes left of battery power when on 60%
Click to expand...
Click to collapse
Run a logcat & send it in, I get AMAZING battery life on this ROM, always have! Its best to use better battery stats & see what's causing it could be a rouge app, wakelocks etc... No way to tell without logs.... Screenshot is my 170 some odd app setup!

innocent25 said:
I am getting an hour and 38 minutes left of battery power when on 60%
Click to expand...
Click to collapse
Did you Factory Reset in TWRP prior to flashing? Also, feel free to post some screenshots of your Power usage, or email them to me [email protected]

Grommish said:
Did you Factory Reset in TWRP prior to flashing? Also, feel free to post some screenshots of your Power usage, or email them to me [email protected]
Click to expand...
Click to collapse
canodroid15 said:
Run a logcat & send it in, I get AMAZING battery life on this ROM, always have! Its best to use better battery stats & see what's causing it could be a rouge app, wakelocks etc... No way to tell without logs.... Screenshot is my 170 some odd app setup!
Click to expand...
Click to collapse
innocent25 said:
I am getting an hour and 38 minutes left of battery power when on 60%
Click to expand...
Click to collapse
I'm guessing he's talking about the battery predictor. I find it's completely incorrect in how much time it predicts. I had 60% left and it gave me something like 7 hours once and 1.5 hours the other time.

tdotdot said:
I'm guessing he's talking about the battery predictor. I find it's completely incorrect in how much time it predicts. I had 60% left and it gave me something like 7 hours once and 1.5 hours the other time.
Click to expand...
Click to collapse
Battery is a YMMV depending on use I never really look at battery issue unless I see I have a drain and with this being an S3 when I had mine still I had battery life always between 4-12 hrs depend on SOT, apps running, radio connection (4g-lte).
Sent from my SM-T217S using XDA Free mobile app

Kernel Auditor & Device control work flawlessly on tho ROM, no probs at all. Kernel tweaker & others need to be updated.

Day 2 running this and it's settled in quite nicely WiFi and signal were touch and go at first, now running extremely well. This is now my daily driver and I couldn't be happier Great work! Looking forward to the updates.

jondroid2 said:
Day 2 running this and it's settled in quite nicely WiFi and signal were touch and go at first, now running extremely well. This is now my daily driver and I couldn't be happier Great work! Looking forward to the updates.
Click to expand...
Click to collapse
AGREED! Best damn ROM out for our aging old school device! No disrespect to any others, this ones just MY personal favorite! Plus the devs behind it are kick ass as well!???

Running the Shift-D2-SE kernel @rogersb11 with default scheduler and governor settings. Not a full day on it yet but already a noticeable improvement in battery life Going to try out the Shift-D2-3.0 later and compare.

Running Shift-3.0 kernel now. After a full day everything running great! Already getting good battery life and running smooth. Just noticed it's running default at 1881 MHz. Backed it down a little and expecting even better battery life As far as ROMs go, this one is still top dog IMO:thumbup:

jondroid2 said:
Running Shift-3.0 kernel now. After a full day everything running great! Already getting good battery life and running smooth. Just noticed it's running default at 1881 MHz. Backed it down a little and expecting even better battery life As far as ROMs go, this one is still top dog IMO:thumbup:
Click to expand...
Click to collapse
You might want to change the governor

jondroid2 said:
Running Shift-3.0 kernel now. After a full day everything running great! Already getting good battery life and running smooth. Just noticed it's running default at 1881 MHz. Backed it down a little and expecting even better battery life As far as ROMs go, this one is still top dog IMO:thumbup:
Click to expand...
Click to collapse
Agreed sir!
Yeah OctOs is TOP DOG for sure! Just wait till the next update! You ain't seen nothing yet! This ROM is unbelievably stable & smooth for a beta release, & has a lot of features! But no where near what it's gonna become.... Beware the KRAKEN!!!?

canodroid15 said:
Agreed sir!
Yeah OctOs is TOP DOG for sure! Just wait till the next update! You ain't seen nothing yet! This ROM is unbelievably stable & smooth for a beta release, & has a lot of features! But no where near what it's gonna become.... Beware the KRAKEN!!!?
Click to expand...
Click to collapse
KRAKEN!!!....Brilliant! This should be added to the ROM sometime in the near future!

jondroid2 said:
KRAKEN!!!....Brilliant! This should be added to the ROM sometime in the near future!
Click to expand...
Click to collapse
Lol! Not sure about that but... Stay tuned tho! ??

hopefully a CDMA version will be made! I really want to try a lollipop for my d2mtr....
willing to test!!
already tried flashing all the lollipop roms on this board with no success!

coyotefiveoh said:
hopefully a CDMA version will be made! I really want to try a lollipop for my d2mtr....
willing to test!!
already tried flashing all the lollipop roms on this board with no success!
Click to expand...
Click to collapse
Pm me
Sent from my SPH-L720 using XDA Free mobile app

{
"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. -​
Team OctOs would like to thank Team Blackout for the use of their Blacked Out Nexus Launcher & for saving eyes one app at a time!
You can get all the TBO goodies here as well as the TBO Updater http://teamblackedout.com/ #whiteuimustdie
TBO thread http://forum.xda-developers.com/showthread.php?p=41545802​
Frequently Asked Questions
Q: Is this Android 6 (MarshMallow)?
A: Yes, this is Android 6.0.1
Q: What code is Oct-MM based on?
A: Starting with Oct-MM, we've rebased OctOs on the CyanogenMod 13 code. Modified to give you a smoother more stable rom.
We like to Strive on being closest to AOSP as possible but also being able to support multiple devices.
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-MM.
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
!NOTE! This ROM is for the standard d2spr! The d2refreshspr or "SPARK/Tri-band" has its own thread!​
DOWNLOADS​Stable: https://www.teamoctos.com/release/​Weekly: https://www.teamoctos.com/weekly-builds/​Recomended Gapps: http://opengapps.org/​
The Oct-MM ROM installation script will automatically wipe /system, /cache, and /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.
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
AOSP
TeamBlackout
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 Sprint Samsung Galaxy S III
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
Version Information
Status: Stable
Current Stable Version: OCT-M R2
Created 2015-02-18
Last Updated 2016-08-26

Reserved
Known Issues
A full list of Known Issues resides on our website. *In order to avoid confusion for people who skimmed the OP.
NONE REPORTED BY TESTERS

Device Varents
For The Spark S3
For users of the Spark S3 there is a D2bst. Please for the alternative carriers(Boost,Virgin) use your approprate zips needed.
Virgin mobile: use this till we can get it merged
http://androidforums.com/threads/mo...pn-fix-wip-cm-aosp-4-4-x.840298/#post-6516416

I Got It
Downloading now!

Thx for supporting the SPH-L710T! You guys are awesome and now I have something asop for my spark! I would be happy to test it and report back any bugs. THX AGAIN!!

Nice job on the OP.
I look forward to giving this a try.

glad i was able to test this and the TWRP for the T model you should probably post the TWRP links unless i missed where you did

stable outside of the cam gents and ladies.. use Open Camera and Viva Video .. there's workarounds.. this bad boy is excellent

I am on sprint prepaid and I flashed the d2bst and everything seems to work but rotation is upside down.

stolikat said:
I am on sprint prepaid and I flashed the d2bst and everything seems to work but rotation is upside down.
Click to expand...
Click to collapse
Do you have the spark s3 or regular
Sent from my SPH-L720 using XDA Free mobile app

The spark S3

OK yes our tester have noticed the reversed rotation also and it is in the works of being fixed. The Spark S3 device repository had to be built from scratch so a few things to work out.
Sent from my SPH-L720 using XDA Free mobile app

Ok thanks if there is anything I can do I would be glad to help out. This ROM is smooth as silk other than that issue so far. Great work team!!

I' pretty sure he has the sprint spark s3 which is the pre paid model (SPH-L710T) Same one I got! THX for this rom guyz!

jerryz16 said:
I' pretty sure he has the sprint spark s3 which is the pre paid model (SPH-L710T) Same one I got! THX for this rom guyz!
Click to expand...
Click to collapse
Yes I do. Have to add no 4g connectivity either.

stolikat said:
Yes I do. Have to add no 4g connectivity either.
Click to expand...
Click to collapse
You check your network settings, preferred network should be lte, there's also a lte toggle in quick settings but you have to add it

stolikat said:
Yes I do. Have to add no 4g connectivity either.
Click to expand...
Click to collapse
OK I got the link from our testers for the virgin mobile
Use this till we can get it merged
http://androidforums.com/threads/mo...pn-fix-wip-cm-aosp-4-4-x.840298/#post-6516416
Sent from my SPH-L720 using XDA Free mobile app

(I have the sprint spark SPH-L710T) The only problems I have are is that it says I'm on boost but I'm really on sprint (prob not a problem idk), the camera can't connect, and the rotation is wrong. IDK if the network is actually working though since I need to refill. Great rom though! Thanks

jerryz16 said:
The only problems I have are is that it says I'm on boost but really on sprint (maybe not a problem idk), the camera can't connect, and the rotation is wrong. IDK if the network is actually working though since I need to refill. Great rom though! Thanks
Click to expand...
Click to collapse
OK are you boost virgin or sprint. And if you are sprint is your phone the L710T. Me and the team have been talking about the spark s3 this morning. And the camera is know about so no need to mention a bug that has been posted.
Sent from my SPH-L720 using XDA Free mobile app

I have the SPH-L710T Sprint. This rom is great. The only bugs I've found is backwards rotation and IDK if 4G and Data works. I checked and it is set to LTE and I have a signal so I think it works. Thx for your speedy response.

{
"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 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 favorite Open Gapps 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
Open Gapps
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 T-Mobile Samsung Galaxy Note II
Contributors
hedwig34, canodroid15, bthorne79, CjKacz
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: Testing
Current Stable Version: OCT-M R2
Created 2015-02-20
Last Updated 2016-08-26

Yes. Netflix works.
http://www.teamoctos.com/supported-devices/samsung/samsung-galaxy-note-2/

Screenshots would be appreciated!

GodLik3 said:
Screenshots would be appreciated!
Click to expand...
Click to collapse
Added some to the OP

This looks great does GPS work, and also is there still an issue with music playing on speaker when headset connected. Thanks

illest_one_7777 said:
This looks great does GPS work, and also is there still an issue with music playing on speaker when headset connected. Thanks
Click to expand...
Click to collapse
GPS works.
No issues with the speaker playing while headphones are plugged in.
Sent from my SCH-I605

Thank you very much. Flashing now. Will let you know if there are any issues.

Flashing now...will report any bugs found.
Thanks for another 5.0 offering for our device...certainly keeps me from dropping money on a new phone

Ok. Netflix doesn't work, for me at least. The app loads up and I see all my stuff but it does not play my shows. Other than that, everything works fine.

Reboot and try Netflix again.
Sent from my SCH-I605

Netflix confirmed working here. (t889)
---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------
Is there DPI control built in the settings? or should I use Build prop editor?

There is no built in DPI control.
Sent from my SCH-I605

Rom is smooth. The only bug I've encountered so far is google now doesn't recognize my voice or the ok google command. I haven't installed any sound mods yet but it didn't work from the beginning. Any advice? Oh, I also have the voice detection enabled.

Why is my battery screen showing WiFi is on even though it's off? Did a restart now, let's see if it fixes it.
Edit: aaaaand the restart fixed the problem.
Sent from my SGH-T889 using XDA Free mobile app

bluetooth audio plays for 1 second then stops streaming to bluetooth device (speakers, headphones, car stereo)
Edit: couple reboots got it working

So far so good!
Thank you, Team OctOs!
I had tried the other two 5.0.2 ROMs and the biggest issues I had was the device not coming back from a deep sleep (or basically the device not powering back on for some reason, requiring a batt pull. This got so annoying that I had to jump back to a KitKat ROM, until I saw this thread and how promising it looked.
So far, (and I rebooted a few times after everything was installed, after seeing some of the posts) I am happy to say that the main issues I had seen with the Lollipop ROMS for this device isn't seen on this one.
- Netflix - Works!
- Not powering on after some time with the display off (maybe deep sleep?) - Not seen so far after 24 hours (saw it within a couple of hours on other ROMs).
Minor issues still seen:
- Volume seems to be low on calls, but this is remedied by just pressing the volume down once, and if necessary back up and the volume is fine after that.
- On Bluetooth, when I stream music through it, the volume drops every few seconds for a split second then is fine again. I had figured that when I don't max out the volume on BT on the phone, it seems to work better, almost never seeing this issue so it's just a minor annoyance.
More info regarding battery: So far, the battery drain on this is amazingly low! I paired this with the PA Micro gapps pack and after 4 hours of it unplugged, streaming music on LTE, I was maybe down just 15%.
So far so good and thank you again!

So after a few days I have not encountered any major problems at all.
As far as minors:
-a freeze here and there, had to do maybe one battery pull
-goo manager doesn't seem to work
-cant get one of my favorite games to function(puzzles and dragons) , after doing some research it seems it an issue with custom roms in general and this game.
Thank you all who put your time and effort into making this ROM, its awesome.

more lollipop!!! :good:

Looks Great
Downloading now

This is a great rom! I've been away from a computer that is able to compile from source for a while, but now I'm back in business. I would love to help If I can.

{
"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. -​
Team OctOs would like to thank Team Blackout for the use of their Blacked Out Nexus Launcher & for saving eyes one app at a time!
You can get all the TBO goodies here as well as the TBO Updater http://teamblackedout.com/ #whiteuimustdie
TBO thread http://forum.xda-developers.com/showthread.php?p=41545802​
Frequently Asked Questions
Q: Is this Android 6 (MarshMallow)?
A: Yes, this is Android 6.0.1
Q: What code is Oct-MM based on?
A: Starting with Oct-MM, we've rebased OctOs on the CyanogenMod 13 code. Modified to give you a smoother more stable rom.
We like to Strive on being closest to AOSP as possible but also being able to support multiple device
Q: What happened to AOSP?
A: All Android code is based on the Android Open Source Project (AOSP). Under previous releases, we tried very hard to limit the number of "Not from Google directly" repositories that we used. Unfortunately, issues with devices, the need for Code Aurora Foundation (CAF) repositories for Qualcomm devices, and compatibility issues meant fighting code more often than not. We decided that since the code-base for many repositories were the same across most ROMs, picking a starting point to build the user experience on outweighed the desire to craft code from scratch, or fix broken code to make it work with other changes we already had.
Q: Why isn't there XXXXXXX feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But CM and all the others have..
A: ROM developers, including CM, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-L.
Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
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 AT&T Samsung Galaxy S4
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
Current Stable Version: OCT-M R2
Created 2016-01-17
Last Updated 2016-08-26

Installed and working great
Except Icons not updating for themes on the launcher.
Version installed is
OCT-M-WEEKLY-20160116-2058
Steps I took,
Factory Reset
installed Rom
Installed GApps nano 32bit
ran Loki Doki
After boot up,
Installed BusyBox to allow various apps to work properly, like Root Explorer
THanks for the Rom

Anyway you can add support for the jfltecri version of the S4? Its the Cricket Version that operates on the ATT network.

Themes With Icons can't install
Themes with Icons crash Launcher during install (not when switching to them, they can't install)
with the
OCT-M-WEEKLY-20160123-1208 Rom
to_jflteatt-userdebug 6.0.1 MMB29T c271ef53a1 test-keys

Is a version for i337m (jfltecan) coming soon?

Fantastic thanks for your work!

The jfltecri is the i337Z, let me know if you need any other info.

Have installed the latest weekly build and is running good. I don't know If it is just me but I have a problem updating SU binary. Have checked with root checker and I'm having root but when I tried going to root folders it can't get root access\permission. Other root apps also can't get root permission. Already tried installing Latest SU thru twrp but same result. Any help or hint is appreciated.

gorgy76 said:
Have installed the latest weekly build and is running good. I don't know If it is just me but I have a problem updating SU binary. Have checked with root checker and I'm having root but when I tried going to root folders it can't get root access\permission. Other root apps also can't get root permission. Already tried installing Latest SU thru twrp but same result. Any help or hint is appreciated.
Click to expand...
Click to collapse
I'm with you on this

I got it installed on my jfltecri, I just changed the ATT version's updater script. So far everything is running good.

Also, sometimes I'll make or receive phone calls and I can't hear them and they can't hear me, even though the call goes through

awakener777 said:
Also, sometimes I'll make or receive phone calls and I can't hear them and they can't hear me, even though the call goes through
Click to expand...
Click to collapse
Same here can't even hear my voicemail. I just restored my backup. Can't get SU binary to update too.

How do I enable battery percentage?

Also I am unable to change screen lock.

How did you guys install twrp? I've read that bootloader in i337 is locked and there is no way to make it work.

exodius887 said:
How did you guys install twrp? I've read that bootloader in i337 is locked and there is no way to make it work.
Click to expand...
Click to collapse
You need to be on an older bootloader, AMDL or earlier. If you are, you can use Loki to install a ROM with a custom kernel. If you're on a bootloader that's newer, you have to stick with TW ROMs and SafeStrap as you can't flash the custom kernel required. It sucks having to deal with a locked bootloader even with Loki and that's why I'm never buying a carrier-branded phone ever again.

Just curious, how does Bluetooth work on this?
Sent from my TARDIS

Just installed OCT-M-WEEKLY-20160130-0425-jflteatt.zip. Everything works great so far, no problem with phone calls at all. Thank you so much!!!

exodius887 said:
How did you guys install twrp? I've read that bootloader in i337 is locked and there is no way to make it work.
Click to expand...
Click to collapse
I have the I337z which is the Cricket version. I was able to get TWRP installed via Odin and flashed the ROM that way.
Sent from my SGH-I337 using Tapatalk

Is it safe to dirty flash the weekly builds over?