[ROM] [COMMUNITY][MM 6.0.1] OctOS (Z00A) - Updated September 15, 2016

[OfficerJimLahey]

[ROM] [COMMUNITY][MM 6.0.1] OctOS (Z00A) - Updated September 15, 2016

Another build, compiled from source. But before I get too far...

#include 
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and
 * YOU acknowledge you are doing so at your own risk.
 */

Now that that's out of the way, this is a build of OctOS, using the device tree, kernel and advice from @jrior001 and @crpalmer.

NOTICE:

Final build for the LP bootloader is here.

As work with Nougat begins, I will need to switch over to the MM bootloader. I won't be going back (downgrading) to check builds using the old bootloader. For OctOS, as that is MM anyway, I can begin special builds (reliant on the MM bootloader) once I become established. For Carbon LP, it means the end of the road.

The September Android Security Bulletin arrived for MM a few days ago. I have cranked out the final build, tested, and posted it. Device-identity-wise, the only difference between this build and the one previous is the fix to the "off-path TCP" exploit. The ASB had other fixes, but to the ROM instead. Plus, there were sweet enhancements to the OctOS UI since the last build.

Thank you for all the support, and if it applies to you yet, check out the MM build using the latest bootloader. Cheers.​

WHAT WORKS:

• Powers on
• Phone calls tested (SIM 1)
• Mobile data
• Torch
• Camera
• MTP (Linux users be sure you are using libmtp version 1.1.10 - or greater)
• Charges
• Play Store

WHAT DOES NOT WORK:

• M-Bootloader edition(s) do not come with SuperSU, due to (I suppose) the BL's expectations of a signed boot image (that the SuperSU install otherwise screws up).
• GPS and NFC still to test.
• As this ROM shares the same device tree as CM, (and a lot of projects) this will share the same flaws. Otherwise, please tell me.

DOWNLOAD:

• via AndroidFileHost
• For the L Bootloader (if your stock remains 5.0)
• For the M Bootloader (if you took the 6.0 upgrade)

GAPPS:

• OpenGApps

INSTRUCTIONS:

• Prerequisites: An unlocked boot loader and TWRP 3.x installed
• Download ROM above, and a GApps package
• Save/push files to your (External) SD card (preferably in the root folder where you can find it later)
• Reboot into recovery ("adb reboot recovery")
• Nandroid/Back up device (optional, but highly recommended)
• Wipe cache and data/factory reset (unless updating from previous OctOS version)
• Install ROM and GApps
• Wipe Dalvik cache
• Reboot
• Enjoy!

CREDITS:

• jrior001
• crpalmer
• CyanogenMod
• OctOS (incl. Don Kaczmarek)

XDA:DevDB Information
[ROM] [COMMUNITY][MM 6.0.1] OctOS (Z00A), ROM for the Asus ZenFone 2

Contributors
OfficerJimLahey
Source Code: https://github.com/carbon-z00a

ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod

Version Information
Status: Beta
Beta Release Date: 2016-06-11

Created 2016-06-11
Last Updated 2016-09-15

 

[OfficerJimLahey]

Other Info...

For those following along....

Project GitHub: https://github.com/carbon-z00a

Branches for L Boot Loader:

• oct-mm (Device Tree)
• cm-13.0 (All other identity projects)

Branches for M Boot Loader:

• oct-mm-M (Device Tree)
• cm-13.0-M (All other identity projects)

LOCAL MANIFEST:
Currently a part of the Community builds section of OctOS...no local manifest required! :cowboy:

CHERRY PICK(S):

None at this time.

Make a new folder for and then initialize the build tree:

mkdir octos-mm
cd octos-mm
repo init -u https://github.com/Team-OctOS/platform_manifest.git -b oct-mm && repo sync

Complete all the normal steps (". build/envsetup.sh && brunch") at this point. :cowboy:

CHANGE LOG:

Besides the project git hub...

• CyanogenMod upstream
  • ZF2-BringUp-Related Commits
• AOSP upstream

 

[Russiamen]

Good job.Build for Z008?

 

[ephexxis]

WELCOME BACK!

Sent from my ASUS_Z00A using XDA Labs

 

[EypCnn]

Thanks Reserved

 

[OfficerJimLahey]

Good job.Build for Z008?

Thanks.
I don't have a Z008, so not comfortable with building that one.

 

[quick05]

Thank you and welcome back

 

[salvoza96]

This ROM is not affected by the network bug?

Inviato dal mio ASUS_Z00A utilizzando Tapatalk

 

[kenbo111]

Nice. So what features does this rom have? Can't find a list on their site.

Sent from my ASUS_Z00A using Tapatalk

 

[OfficerJimLahey]

This ROM is not affected by the network bug?

Mean like Wi-Fi dropping (and hesitant - although it gets there - to reconnect)? I saw that happen a little bit, but it does that for another device of mine as well (across a couple 6.0 ROMs), so I figure it is an AOSP thing waiting to be squashed.

Nice. So what features does this rom have? Can't find a list on their site.

Quoted from the Moto G 2015 OctOS thread:

FEATURES

• Android 6.0.1
• Optimized for the best efficiency (battery and performance)
• Smooth as hell!!
• Live Display
• Ambient Display
• Separate customization menu, which can be hidden
• Omniswitch
• Clear-all recents
• Immersive recents
• Status bar clock/date customization (format, colour, etc)
• Battery icon customization
• Status Bar Header Image
• QS Tiles customization
• App Circle Bar
• Buttons customization
• Volume Steps
• Gesture Anywhere
• Kernel Auditor
• Lock Screen customization
• Toast Icon
• Power menu customization
• SuperSU
• Privacy Guard
• Status Bar Greeting
• Battery Bar
• Traffic Indicator
• Theme Engine
• More to come!

Hope this helps.

 

[EdgeVibration]

So the battery life on this will be good you reckon? I am really just looking for a ROM to handle my all day 4G use and just whatsapp in general. Do you reckon i can get about maybe 3/4 hours of SOT while having 4G on?

 

[abner albuquerque]

aosp based?

 

[basdriver62]

aosp based?

Yes, but it runs CyanogenMod 13's Fig API.

 

[abner albuquerque]

great, big thanx

 

[OfficerJimLahey]

So the battery life on this will be good you reckon? I am really just looking for a ROM to handle my all day 4G use and just whatsapp in general. Do you reckon i can get about maybe 3/4 hours of SOT while having 4G on?

As with all things, your mileage may vary. With that out the way...

Just booted from a fully charged state (without SIM), and let it drop to 99% (since booting puts a little more load, and untracked SOT in the test). I then timed, with screen on (brightness around 60%), how long it would take to go from 99% to 98%. Took a little over three minutes, by then the phone estimated I had five hours of battery life left (as a result of having the screen always on). Three minutes for a percent also works out to five hours for 100% of battery life. Toss in 4G in a good service area, some idle (screen off) time, and a day's use for 4 hour SOT sounds about right.

Why I mentioned earlier YMMV: My ZF2 has been used as a daily driver (light to moderate daily usage), until very recently, for almost a year (I believe it was this day last year that I purchased it). For the first 8 months, aside from being plugged in for adb/fastboot purposes (or a charge after a lot of work done in TWRP), I would charge it every second day. For the last 4 months, I needed to charge it at least some amount on a daily basis. So my battery is starting to show some wear after 240 to 250 (or more) charges (it is noted on third party battery packaging that the product will show their wear after 300 charges - I imagine the real deal is not all that different). Contrast this to my new ZF2 Laser which on 5.0.2 stock gives me two days (Saturday morning to Sunday evening) from 100% to 56% (so I could have squeezed another day out of it) though I did not check the SOT.

Hope this helps.

 

[EdgeVibration]

As with all things, your mileage may vary. With that out the way...

Just booted from a fully charged state (without SIM), and let it drop to 99% (since booting puts a little more load, and untracked SOT in the test). I then timed, with screen on (brightness around 60%), how long it would take to go from 99% to 98%. Took a little over three minutes, by then the phone estimated I had five hours of battery life left (as a result of having the screen always on). Three minutes for a percent also works out to five hours for 100% of battery life. Toss in 4G in a good service area, some idle (screen off) time, and a day's use for 4 hour SOT sounds about right.

Why I mentioned earlier YMMV: My ZF2 has been used as a daily driver (light to moderate daily usage), until very recently, for almost a year (I believe it was this day last year that I purchased it). For the first 8 months, aside from being plugged in for adb/fastboot purposes (or a charge after a lot of work done in TWRP), I would charge it every second day. For the last 4 months, I needed to charge it at least some amount on a daily basis. So my battery is starting to show some wear after 240 to 250 (or more) charges (it is noted on third party battery packaging that the product will show their wear after 300 charges - I imagine the real deal is not all that different). Contrast this to my new ZF2 Laser which on 5.0.2 stock gives me two days (Saturday morning to Sunday evening) from 100% to 56% (so I could have squeezed another day out of it) though I did not check the SOT.

Hope this helps.

Hey thanks a lot for that. I have been using the ROM and I have to say it really is amazing. I don't really have any bugs to report, everything is working nice and smooth. Battery does last quite long, maybe gets me through the day with moderate use. I even use FlareM 17.6 and I have optimized it. I get around 4 hours while on heavy use + 4G so yeah, great ROM.

 

[ephexxis]

As with all things, your mileage may vary. With that out the way...

Just booted from a fully charged state (without SIM), and let it drop to 99% (since booting puts a little more load, and untracked SOT in the test). I then timed, with screen on (brightness around 60%), how long it would take to go from 99% to 98%. Took a little over three minutes, by then the phone estimated I had five hours of battery life left (as a result of having the screen always on). Three minutes for a percent also works out to five hours for 100% of battery life. Toss in 4G in a good service area, some idle (screen off) time, and a day's use for 4 hour SOT sounds about right.

Why I mentioned earlier YMMV: My ZF2 has been used as a daily driver (light to moderate daily usage), until very recently, for almost a year (I believe it was this day last year that I purchased it). For the first 8 months, aside from being plugged in for adb/fastboot purposes (or a charge after a lot of work done in TWRP), I would charge it every second day. For the last 4 months, I needed to charge it at least some amount on a daily basis. So my battery is starting to show some wear after 240 to 250 (or more) charges (it is noted on third party battery packaging that the product will show their wear after 300 charges - I imagine the real deal is not all that different). Contrast this to my new ZF2 Laser which on 5.0.2 stock gives me two days (Saturday morning to Sunday evening) from 100% to 56% (so I could have squeezed another day out of it) though I did not check the SOT.

Hope this helps.

i wish my analytical recall was this good. i guess it's one thing if you always meant to keep track and had it in your head to keep of your charging schedule but it sounds like you were just considering it in real time given the question, haha.

my life would likely be very different if i could track reach a year back and consider with clarity my actions

Sent from my ASUS_Z00A using XDA Labs

 

[A_Bunny]

Nice ROM. Just want to let you know that GPS works great on my end (so no need to test it). Not sure about NFC however as I don't use it myself.

 

[puppetminds]

Everything working for me, calls, 4G,Wifi,SOT is 4hrs with my usage,GPS working, ALARM(thank goodness) is working. Thanks for the effort. I wonder if this Zenfone 2 can break anymore battery barriers compared to using other ROMs. Nonethless great job. Will be using this as daily driver

P.S: Previously used RR, CM Nightly, AOKP, BeanStalk(recently changed to OctOS).
Not using GApps, stock kernel

 

[grendude]

ROM works great. GPS works!

One issue: when looking at photos or a pdf the screen occasionally goes black. This lasts for 3-8 seconds before it comes back and I can interact.

Disabling hardware overlays in Developer Options seems to fix the problem, but it eats more battery.

Any better ideas?