Android Marshmallow 6.0.1 Team OctOs For LG Nexus 5X BullHead Stable:
VOLTE IS WORKING!!! OctOs is a WIP. It has been evaluated as being stable, and is compatible for everyday use in general. Even as it can be considered stable, there is also unknown bugs. The development crew just isn’t in charge for any damage to your gadget or your expertise.
Team OctOs presents Oct-M.
Generally asked Questions
Q: is this Android 6 (Marshmallow)?
Q: What code is Oct-M founded on?
A: establishing with Oct-M, we rebased OctOS on AOSP code. After a short love affair with AOSP we needed to make the transfer again to CM as a base.
Q: What happened to AOSP?
A: good regardless of our efforts & our name for aid, eventually had been simply to brief staffed. We had to make use of CM as a base for our legacy CAF contraptions & preserving both branches simply grew to be overwhelming.
Q: Why is not there XXXXXXX function.
A: Shoot us a suggestion if you want to see anything introduced. While we aren’t going to promise to put into effect, we can constantly seem into it
Q: however XYZ rom and the entire others have..
A: ROM builders build whatever they need to use. The ROM developer that entails something they won’t run implies less than 100% effort to ensure it does work. As a group, we now have an identical objectives and goals. If XYZ ROM has a function you wish to have, and we don’t include (or don’t need to comprise), feel free to make use of XYZ ROM, or construct your possess customized variant of Oct-M.
Q: Superuser or SuperSU?
A: workforce OctOs uses SuperSU and is mounted mechanically.
Bugs happen. Our testers are very good at breaking matters, but no the place close as good because the leisure of the Android public. With the intention to investigate and repair disorders, we need the support of the customers who’re going to document them. The Android OS has many nifty facets to support us on this, but only if we are able to have interaction the person to support us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like another OS, Android has more than one log records which can be generated and document the goings-on of the method. As a person, you will have two common methods to view and pull these to send to us. Without the information in the logfiles, there with ease will not be a whole lot of understanding to head on.
Log file APKs
crew OctOS recommends SysLog from the Android Market. This utility will enable you to selectively prefer any (or all) of the approach logs, compress them into a .ZIP file, and allow you to avoid wasting, email, transfer to your replica/DropBox/Cloud Storage account, and many others.
The Android Debugging Bridge (ADB) is a powerful instrument to be had from Google as part of the Android software development kit (SDK). Used for a lot of matters, being ready to selectively see, in real-time, what your gadget is doing are not able to be downplayed. Whilst there’s extra setup worried, in case you are doing regular ROM flashing, you particularly will have to make investments the time to get setup competently to do it.
ADB Logcat tutorial here: How to create a logcat log
-NOTICE! Force encryption is enforced in these builds! You must flash the force encryption disable zip from the thread below
download ROM .Zip file and MD5 file, and grasp your favorite gapps package
Reboot to restoration (observe: Use Reboot to recuperation from energy Menu, Hardware-headquartered boot to recuperation, or adb reboot recuperation – ROM supervisor or an identical software shouldn’t be supported)
— TWRP is the one recovery team OctOS uses – we don’t aid flashing on CWM —
manufacturing facility Reset from TWRP
Flash ROM and GApps
if you’re no longer encrypted flash the above posted mod or a kernel that does not enforce encryption
The Oct-M ROM installation script will mechanically wipe /process, /cache, and /data/dalvik-cache. There is no have to do these earlier than or after flashing the ROM unless you’re recommended to with the aid of your GApps supplier
The groundwork of the Android OS is the truth that is it open-source. We now have all code we use internally in the production of Oct-M to be had on our GitHub repositories.
Unless otherwise specified, all Oct-M builds use the device’s stock kernel.
Team OctOs GitHub – http://www.github.com/Team-OctOs
Team OctOs Gerrit Review – http://www.teamoctos.com:8080
Team OctOs GPLv2 License – http://www.teamoctos.com/license/
Team OctOs Patreon Campaign – https://www.patreon.com/TOctOs